16
Technical Support / Re: The latest version and FLARM
« on: December 07, 2016, 10:55:17 pm »
Peter,
In theory this sounds a dead simple solution and maybe at this RS232 level would work wonderfully! My formal life involved controlling robots with RS232 and splitting caused all sorts of issues, however we were using handshaking as well RTS etc.
FLARM somewhere in its documents says that the signal should not be split, but of course that could just mean Air Avionics worried they may not be able to rip off customers. After all it is already split because the Air Connect can send to WiFi and RS232 to MGL as there are two ports!. In my simple mind this is already split!
I can of course thinking about this logically and having had a couple of glasses of red wine resolve this simply - MAYBE The Butterfly RS232 WiFi is no longer used as the iPAd now is dedicated to the PAW. SO Spare PAW port needs a USB / RS232 converter and Connect FLARM TXD to PAW RCD plus GND.
Only slight (hopefully) issue is the Power FLARM also throws out ADS-B stuff which means I would be duplicating data arriving at the PAW. Also I would not be getting mode C & S in the MGL as it is only taking data from the POwer FLARM.
So here is another possible.
Power FLARM TXD to Spare PAW port via RS232 RCD then using same RS232 connector, TXD output MGL iEFIS. Theory says the PAW becomes the source of both data sets to WiFi and also RS232 to MGL. Sounds sound, but not sure from a PAW software aspect.
In theory this sounds a dead simple solution and maybe at this RS232 level would work wonderfully! My formal life involved controlling robots with RS232 and splitting caused all sorts of issues, however we were using handshaking as well RTS etc.
FLARM somewhere in its documents says that the signal should not be split, but of course that could just mean Air Avionics worried they may not be able to rip off customers. After all it is already split because the Air Connect can send to WiFi and RS232 to MGL as there are two ports!. In my simple mind this is already split!
I can of course thinking about this logically and having had a couple of glasses of red wine resolve this simply - MAYBE The Butterfly RS232 WiFi is no longer used as the iPAd now is dedicated to the PAW. SO Spare PAW port needs a USB / RS232 converter and Connect FLARM TXD to PAW RCD plus GND.
Only slight (hopefully) issue is the Power FLARM also throws out ADS-B stuff which means I would be duplicating data arriving at the PAW. Also I would not be getting mode C & S in the MGL as it is only taking data from the POwer FLARM.
So here is another possible.
Power FLARM TXD to Spare PAW port via RS232 RCD then using same RS232 connector, TXD output MGL iEFIS. Theory says the PAW becomes the source of both data sets to WiFi and also RS232 to MGL. Sounds sound, but not sure from a PAW software aspect.