Author Topic: Flashing LEDs on RS232 classic to Trig transponder  (Read 181 times)

GGVSL

Flashing LEDs on RS232 classic to Trig transponder
« on: November 14, 2021, 06:00:34 pm »
My Trig transponder said not receiving and ADSB out data today whilst flying. Also couldn’t connect to wifi.
Thought it was a power failure to PA but on landing checked and everything seemed ok. Question, what colour should the led in the RS232 cable be flashing? It’s rapid red at the moment.

Admin

Re: Flashing LEDs on RS232 classic to Trig transponder
« Reply #1 on: November 15, 2021, 09:19:12 am »
Hi
Can you provide a pointer to the datasheet for the USB/RS232 device ?
This should indicate what this means, every device is different

Also can you post a screenshot of your PilotAware Configure page

Thx
Lee

GGVSL

Re: Flashing LEDs on RS232 classic to Trig transponder
« Reply #2 on: November 17, 2021, 08:51:17 am »
Have checked the data sheet and all it says is the leds indicate tx and rx does say which colour does what

exfirepro

Re: Flashing LEDs on RS232 classic to Trig transponder
« Reply #3 on: November 17, 2021, 10:15:43 am »
Hi GGVSL,

Sorry, I must have missed this thread earlier.

I wrote the original text for connecting 'Flarm In' to PilotAware via an FTDI RS232 Serial to USB cable, which is now on the Pilotaware website and have also been instrumental in connecting 'the other way' to provide GPS Data from PilotAware to transponders for a number of users to provide Mode S-ES ADSB Out.

Assuming you are using the recommended FTDI cable for your application (which sounds likely), the correct connectivity for ADSB-Out is 'Orange' - 'Data Out' wire to Pin 5 'GPS Input' of the Transponder Multi-pin connector and the 'Black' - 'Ground' wire to Pin 4. The LED should flash RED to indicate that Data is being transmitted from the PAW to the Transponder. (It flashes GREEN to indicate that data is being supplied to the PAW by an external source such as a Flarm Receiver using the Yellow and Black wires in the FTDI cable - which you don't use for ADSB-Out).

As your system was presumably running properly in the past - and assuming nothing has been changed physically or in the PAW setup - the most likely reason for the dropout would be a loss of GPS position reports, though there could be several reasons for this happening. A quick check would be to make sure the FTDI cable is in the correct USB Port and that both that Port and the Transponder are set to the same Baud Rate (9,600 Baud Recommended). I can talk you through this if needed.

A screenshot of your PAW Configure screen ( as requested by Lee) and also your Home Screen would help us to check what is going on, though if the GPS loss was temporary or intermittent, the reason might be difficult to identify. More extensive checks would require access to the PilotAware track log for the flight in question.

Hope this helps

Regards
Peter
« Last Edit: November 17, 2021, 10:19:49 am by exfirepro »