Messages

16

General Discussion / Re: USB FTDI LEDs

« on: January 20, 2018, 10:02:32 am »

PAW has aircraft profiles, so if you change ship, then PAW profile change can write the correct hex ID and reg to the Flarm Eagle. quickly done and no need to find a PC. Whether there are sufficient Flarm devices out there connected to a PAW to be work Lees time to finish that side-task

I will only be using it in one aircraft so that's not something that needs to be done...... even so, interesting.

Flarm Eagle also claims to be working on an ADS-B detection system, if that's the case, I might retrofit that such that I can remove the ADS-B dongle (one less antenna). Any thoughts on whether removing the TV dongle / antenna would have any negative impact on the functionality of PAW? As far as I see it, PAW integrates the Flarm data into the PAW system. If Flarm is sending data including ADS-B and Mode A / C / S, then that would seem to obviate the need for the additional antenna?

17

General Discussion / Re: USB FTDI LEDs

« on: January 20, 2018, 08:37:01 am »

For some reason, the LEDs now flash. Weird. No wiring defect - pin 4 went to yellow (which on my RJ was green), pin 3 to black (which on my RJ was yellow). Could just be that the thick clouds and location of the GPS antenna on the dashboard of my car last night was blocking a fix and it only flashed when data was received (I didn't check to see whether the LEDs flashed when the PAW booted.....

However I didn't wire the orange to pin 5 - what functionality could the PAW give to the Flarm Eagle?

Am off away for a week or so, when I get back and find some flying weather, will fit it in and take the old kite flying and report back.

18

General Discussion / Re: USB FTDI LEDs

« on: January 20, 2018, 12:10:23 am »

Yes, Port 1 (top left) is set to Flarm, 19200 baud but no LEDs on the USB connector are lighting up hence I was wondering whether I had an issue with either my soldering or whether the LEDs were just not working or whether my unit is defective.

Just out of curiosity, what colour should I expect to see? I bought the USB-RS232-WE-1800-BT 0.0 from RS electronics.

19

General Discussion / USB FTDI LEDs

« on: January 19, 2018, 08:43:47 pm »

Good evening, I have just packed out my soldering iron and soldered up some cables. Rather than go down the route of Flarm Mouse, I have elected to go for the Flarm Eagle (Power Flarm based) and it's booted up ok (at least I think so.) However the LEDs on the FTDI are resolutely blank. When should they start transmitting? If it's set for GPS and Traffic on Flarm Tools, shouldn't I see these blinking when the satellites have got a fix?

20

General Discussion / Re: Flarm mouse

« on: November 19, 2017, 07:32:48 am »

If you could send me one of the earlier ones, I'd appreciate it.

21

General Discussion / Re: Flarm mouse

« on: November 18, 2017, 02:24:14 pm »

So, anyone got an idea of when the documentation on how best to connect a Flarm Mouse or similar to PAW would be available? Thanks

22

General Discussion / Re: Flarm mouse

« on: November 05, 2017, 05:56:46 pm »

Rather than starting a new thread, I'm going to tag onto this thread. I'm currently thinking of purchasing one of these products:

http://www.lx-avionik.de/produkte/powermouse/ (Powermouse)

or

http://de.lxnavigation.com/ (Flarm Eagle)

instead of a Flarm Mouse.

What interests me is the fact that the two devices mentioned are both based on PowerFlarm technology so should be similar to (e.g.) fitting PowerFlarm Core - anybody have any ideas whether this would be better than (e.g.) adding a Flarm Mouse? My first thoughts are that detecting ADS-B is not something necessary as PAW can do this, so should I go for either the Mouse as it's cheaper?. Or are there benefits to using PowerFlarm technology in conjunction with PAW I'm not aware of?

23

Technical Support / LX Flarm Mouse

« on: August 20, 2016, 11:27:22 pm »

Hi Lee,

I'm interested to hear that you are looking at decoding FLARM signals by using a Flarm Mouse - would the above mentioned unit be suitable? If so, how would the total power requirements look like? I see that the Flarm Mouse is looking for a 3A connection, the Pi needs a 2A connector so that excludes the use of a battery pack, correct? At the same time, assuming the need to use an onboard power sockets, are there any thoughts of taking the Flarm Mouse connector and 'adopting' it to ensure that cable can connect to the Pi providing that with power as well, coming from a typical cigarette lighter socket? Or are we looking at getting our own soldering irons out?

Secondly, what are your thoughts on cabling and space on the top of the glare shield? My thoughts would be to secure the units under the seats, out of sight but use antenna extenders to place these in an area where they have decent views outside - would this be possible?

24

Technical Support / Re: Mode S Targets in Sky Map

« on: August 20, 2016, 10:33:07 pm »

Thanks Lee, I confirm that it's now working with coloured rings including the height difference. In a number of instances, the distance is so close, the SkyMap shows the warning and announces the proximity of any possible intruders.

25

Technical Support / Re: Mode S Targets in Sky Map

« on: July 26, 2016, 09:16:42 pm »

Hi Lee,

strangely enough it works when configured as (e.g.) EasyVFR but just doesn't supply the traffic data as Sky Map expects it to be delivered..... Would it be possible to having the system provide that code itself then switching to Sky Demon mode for Sky Map, or is that a repetitive command it's expecting?

26

Technical Support / Re: Mode S Targets in Sky Map

« on: July 26, 2016, 04:25:16 pm »

That has made it worse. If I plug in 6000, the whole system just dies on me. I've tried rebooting. I've disconnected and tried a new WLAN adapter - they get bloody hot.....

Logging I see:
(16:22:41) NAV-TCP   : Connected to NAV_SKYDEMON=28
(16:22:41) NAV-TCP   : NAVMSG='6000'
(16:22:39) NAV-TCP   : Disconnected Descriptor=29
(16:22:39) NAV-TCP   : NAV MSG=
(16:22:39) NAV-TCP   : recvData() Timeout
(16:22:39) NAV-TCP   : Listening for Connection
(16:22:39) NAV-TCP   : Connected Descriptor=28
(16:22:26) NAV-TCP   : Connected to NAV_SKYDEMON=23
(16:22:26) NAV-TCP   : NAVMSG='6000'
(16:22:24) NAV-TCP   : Listening for Connection
(16:22:24) NAV-TCP   : Connected Descriptor=23
(16:22:24) NAV-TCP   : Disconnected Descriptor=28
(16:22:24) NAV-TCP   : NAV MSG=
(16:22:24) NAV-TCP   : recvData() Timeout
(16:22:11) NAV-TCP   : Connected to NAV_SKYDEMON=29
(16:22:11) NAV-TCP   : NAVMSG='6000'
(16:22:09) NAV-TCP   : Listening for Connection
(16:22:09) NAV-TCP   : Connected Descriptor=29

ad nauseum.......

I can see there is something wrong because I am setting the unit to use the GPS of Pilotaware and when I have the code at 6000, it doesn't receive any data.....

Change to 6001 and it connects immediately.


EDIT: If I use the internal GPS, it just shows: NO TRAFFIC DATA and looking at the logging page it shows NAV_SkyDemon connecting and timing out.

27

Technical Support / Re: Mode S Targets in Sky Map

« on: July 26, 2016, 02:27:11 pm »

version 20160708

28

Technical Support / Re: Mode S Targets in Sky Map

« on: July 26, 2016, 12:38:58 pm »

6001, port 2000

29

Technical Support / Mode S Targets in Sky Map

« on: July 26, 2016, 11:15:32 am »

Good Morning,

I have been running trials with my unit, all seems to be ok except for Mode S traffic being exhibited in Sky Map.

This is how Sky Map would display traffic, IF it conforms to the Flarm V6.0 guidelines:



As we can see, transponders are shown as a circle around the own position, in varying colours, with the height noted.

However in my system, I am seeing the following:



The traffic only appears when it's extremely close, the system ignores the green and orange circle and transposes itself above my position with info on height.

I talked to the developer on the phone about this, he says the issue is an incompatibility with Flarm Protocol V6.0. The strange thing is - it works with EasyVFR (ok, no circles but it shows the green, orange and red bars). Any ideas?

Thanks.

30

General Discussion / Re: Air nav pro flarm not connecting

« on: November 17, 2015, 06:14:58 pm »

Better yet, just dump ANP and move to another Moving Map software. I turned my back on that program after they continuously kept introducing the same bug on repeated updates (the system would delete the links to all installed maps - they were physically there, but the software didn't know and the only way to have the maps reappear was to download them again. Three times they released an update to fix the bug and 3 times they released a new version which reintroduced this bug - worse, due to iTunes security, if an update was available, you HAD to install it or the software wouldn't start.

The final time this happened I was in Hungary and had to pay a fortune to download the maps via Data Roaming and all Xample said was "not our problem" even though they knew the flaw was of their own making. I don't trust their programming capabilities and continuously having to enter those details on each start is something I would not accept, especially as there are other options out there......