![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#10
|
|||
|
|||
![]()
On Aug 12, 1:02*pm, Andy wrote:
On Aug 11, 5:58*pm, Andy wrote: Anyone else see this amber LED after loading? If so, do you have an explanation? The amber led was caused by the command $PFLAC,S,PCASRANGE,9656 This command is documented in the data port addendum which states its max value is 65535m. However, experimentation has shown that the max value is between 9250 and 9300. *9250 gives a green LED after loading but 9300 gives an amber LED after loading. It appears that the amber LED indicates that a command line was not parsed correctly but that does not seem to be stated in the documentation. GY Mine behaves differently (but good catch!). If I set pcas and adsb range to 9600m, the file loads with ten or so green flashes, one red flash, amber very briefly then steady green. If I set both ranges to 9000m, I get only green flashes, amber briefly, then steady green. Too bad I have no way to inspect the settings. I'm also wondering what "XPDR Alarm" and "Farm UI" options do in the display setup. The first, presumably, turns on the warning chime for PCAS (and ADSB?) traffic. The default, oddly, seems to be "off". Up til now, all I've gotten from pcas contacts has been a single chirp. Totally useless as "warning". But I thought that perhaps I just hadn't been bold enough to let a pcas contact close enough to trigger the warning alarm. Now I have it turned on, I guess we'll see. I would like to know what the warning algorithm is for adsb and pcas. The "Flarm UI" default is also off. The docs make reference to this (flarm external display instructions, pg 11) but give no clues as to what might happen if I turn it to "on". I don't recall seeing this option before I did the 2.40 update. It may have been there... scratches head... there's just so very much about this device that isn't (well enough) documented. Opinion: We should not be having to experiment with a device this expensive (and this difficult and potentially hazardous to test in flight) in order to figure out what it does and what the optimum settings are. -Evan Ludeman / T8 |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Powerflarm Brick feedback | Ramy | Soaring | 7 | August 10th 12 01:02 AM |
Measured current draw, PowerFlarm Brick | Evan Ludeman[_4_] | Soaring | 4 | July 16th 12 12:03 AM |
PowerFlarm Brick - Can it send GPS sentences to SN10B? | WaltWX[_2_] | Soaring | 11 | June 17th 12 05:33 PM |
PowerFLARM 'brick' progress? | Frank Paynter[_2_] | Soaring | 5 | November 13th 11 07:28 PM |
Display for PowerFLARM brick | Andy[_1_] | Soaring | 4 | May 10th 11 02:32 PM |