USB FTDI LEDs

[Steve6443]

Thanks, Peter, for your input.

The size of the Flarm Eagle is about the size of a pack of paper handkerchiefs.....

Thanks for that Steve, definitely helps picture the size, but I can't get the picture of Ian M with his paper handerchiefs out of my head now    (sorry Ian)

I am trying to 'justify' buying yet another device at present, but am torn between the potential ease and reliability of LXNav's PowerMouse with its USB and 2 x Data Ports and the the Eagle's Dedicated Power supply (I used to have PFC but never liked the idea of supplying the power via a data lead). I already run ADSB, via a TT21 with dedicated GPS (installed pre-PAW), PilotAware with FlarmMouse (I actually have 2 x FlarmMouses...(Mice?) as that was the only way I could carry out my initial testing when we were trying to integrate it with PilotAware) and a Zaon MRX (used since 2009, but not so often these days - except for comparison, so will be interested to hear how you get on.

Best Regards

Peter

I don't understand the reference to the Flarm Eagle power - yes, it can supply 12v to an external display but the 12v isn't going elsewhere in my setup so I don't see what benefit that would be.

Coming back to Ian's point about the PAW being able to transmit to the Flarm - I'm  reading references to about (e.g.) the FLARM View II from LX Nav (not to be confused with the makers of Flarm Eagle, LXNavigation being able to display ADS-B traffic from (eg) a PCAS system. Imagine the following:

If I input the data from the Flarm into PAW, would PAW combine it and output it to a display - without the need for Wifi? If so, I can now see everything on a display without needing to output it to Wifi. What intrigues me most is that the Flarm View II can also be used for navigation, can display way points, airspace, differentiate between airstrips with grass and with tarmac runways etc.

My thoughts are to reengineer the FTDI cable such that it terminates in 2 x RJ12 cables - i.e. cut an RJ12 cable in half, reconnect the 12v pins and ground pins together to ensure continuity - that way the Flarm View is powered directly by the Flarm Eagle. 

One end of the RJ12 would be deemed input to PAW - I would then connect pin 3 and 4 of that RJ12 socket to the Data In / ground of the FTDI, this end of the RJ12 I would connect to the Flarm Eagle. The other end would be output - I would then connect pin 3 and 5 of the other end of the RJ12 cable to the Data out of the FTDI and connect this to the Flarm View 2.

If the PAW outputs all traffic on the TX line, then I have a complete system displaying Flarm / PAW / ADSB on a display without the need for any wifi, so I could remove that dongle. The only question I am left with is the airspace - apparently it accepts CUB files for this, but I haven't a clue where I would get them from and keep them updated.....

Concerning PCAS, I also have been using the MRX since 2012, it ran alongside PAW but as the Flarm Eagle needs to use the 12v socket, it might be consigned to the cupboard....

[exfirepro]

Thanks, Peter, for your input.

The size of the Flarm Eagle is about the size of a pack of paper handkerchiefs.....

Thanks for that Steve, definitely helps picture the size, but I can't get the picture of Ian M with his paper handerchiefs out of my head now    (sorry Ian)

I am trying to 'justify' buying yet another device at present, but am torn between the potential ease and reliability of LXNav's PowerMouse with its USB and 2 x Data Ports and the the Eagle's Dedicated Power supply (I used to have PFC but never liked the idea of supplying the power via a data lead). I already run ADSB, via a TT21 with dedicated GPS (installed pre-PAW), PilotAware with FlarmMouse (I actually have 2 x FlarmMouses...(Mice?) as that was the only way I could carry out my initial testing when we were trying to integrate it with PilotAware) and a Zaon MRX (used since 2009, but not so often these days - except for comparison, so will be interested to hear how you get on.

Best Regards

Peter

I don't understand the reference to the Flarm Eagle power - yes, it can supply 12v to an external display but the 12v isn't going elsewhere in my setup so I don't see what benefit that would be.

We seem to have got our 'wires' crossed a bit here Steve (sorry for the pun). My comment had nothing to do with the Flarm Unit supplying power to other devices (though they will generally do so), I simply meant that I really like the fact that LX Navigation supply power to their device(s) via a separate dedicated cable. With most FLARM devices (including the 'Flagship' PFC) you need to supply the power via the data cable(s) - albeit using dedicated pins. I personally like the idea of keeping a '12 - 30+ volts at potentially up to 3 Amps' power supply and low voltage data cables separate - especially in an aircraft!

Coming back to Ian's point about the PAW being able to transmit to the Flarm - I'm  reading references to about (e.g.) the FLARM View II from LX Nav (not to be confused with the makers of Flarm Eagle, LXNavigation being able to display ADS-B traffic from (eg) a PCAS system. Imagine the following:

If I input the data from the Flarm into PAW, would PAW combine it and output it to a display - without the need for Wifi?

PAW will certainly combine its own data and that received from FLARM (including 1090MHz data from a PFC) and send the combined and filtered data via PAW's WiFi Hotspot to compatible Nav Systems, but (to my knowledge) we have never tried feeding this data via cable to a Flarm View II or similar device. Data can certainly be transferred by cable to systems such as Dynon and Oudie, so this might be possible, but Lee would need to advise as to the practicality. At the present time BTW, PilotAware is NOT configured to transmit data to Flarm units, though it was suggested in the early days that the 'Orange' wire be connected when making up the USB to Flarm leads 'just in case we found a need to use it'.

If so, I can now see everything on a display without needing to output it to Wifi. What intrigues me most is that the Flarm View II can also be used for navigation, can display way points, airspace, differentiate between airstrips with grass and with tarmac runways etc.

As can most navigation systems and generally on a larger, more readable screen.

My thoughts are to reengineer the FTDI cable such that it terminates in 2 x RJ12 cables - i.e. cut an RJ12 cable in half, reconnect the 12v pins and ground pins together to ensure continuity - that way the Flarm View is powered directly by the Flarm Eagle. 

One end of the RJ12 would be deemed input to PAW - I would then connect pin 3 and 4 of that RJ12 socket to the Data In / ground of the FTDI, this end of the RJ12 I would connect to the Flarm Eagle. The other end would be output - I would then connect pin 3 and 5 of the other end of the RJ12 cable to the Data out of the FTDI and connect this to the Flarm View 2.

If the PAW outputs all traffic on the TX line, then I have a complete system displaying Flarm / PAW / ADSB on a display without the need for any wifi, so I could remove that dongle. The only question I am left with is the airspace - apparently it accepts CUB files for this, but I haven't a clue where I would get them from and keep them updated.....

One flaw here - the PAW USB ports can't (at least at present) be configured as 'Input' and 'Output' at the same time, though IRC Lee did give this some thought in the past, but I'm pretty sure the general consensus was that there was no significant benefit in trying to do so as that's not really how PAW is designed to operate. Such decisions can of course change. I'm not trying to be negative by the way, just want you to know how things are.

Concerning PCAS, I also have been using the MRX since 2012, it ran alongside PAW but as the Flarm Eagle needs to use the 12v socket, it might be consigned to the cupboard....

Pretty much the same with me, except that I could never get mine to run on the aircraft 12 volt supply. I tried that when I first installed it and it completely wiped out my comms with white noise. I remember telephoning Zaon in the States about the problem after several attempts to fix it and their 'best suggestion' was to run the Zaon off my aircraft's 'second power supply' to keep it separate from the one supplying the other comms gear. In my case that turned out to be the two 'AA' batteries 

Best Regards

Peter

[Steve6443]

If so, I can now see everything on a display without needing to output it to Wifi. What intrigues me most is that the Flarm View II can also be used for navigation, can display way points, airspace, differentiate between airstrips with grass and with tarmac runways etc.

As can most navigation systems and generally on a larger, more readable screen.

Yes but the Flarm View II isn't a navigation system, it's just a screen - and (in aviation terms) cheap. Usually a screen would just display traffic. This would display traffic and position and airspace etc...

Concerning PCAS, I also have been using the MRX since 2012, it ran alongside PAW but as the Flarm Eagle needs to use the 12v socket, it might be consigned to the cupboard....

Pretty much the same with me, except that I could never get mine to run on the aircraft 12 volt supply. I tried that when I first installed it and it completely wiped out my comms with white noise. I remember telephoning Zaon in the States about the problem after several attempts to fix it and their 'best suggestion' was to run the Zaon off my aircraft's 'second power supply' to keep it separate from the one supplying the other comms gear. In my case that turned out to be the two 'AA' batteries 

No problems from my side, the MRX worked perfectly, no interference whatsoever.....