PilotAware Rosetta- Trig TT21- Wiring Loom - F I X E D

[Gramac]

next.

[Gramac]

 

[Gramac]

 

[Gramac]

 

[Gramac]

Nearly there....

[Gramac]

Last one.

Thanks for looking.

[exfirepro]

Hi again Graham,

I can’t see anything in your settings that would cause the ‘No Position’ warning, but you need to change Mode CS Select to ‘Mode CS + Filter’ to avoid false alerts from the Mode C transmissions from your transponder.

Your ‘Ultra short range’ setting will also be very restricting and should only be used if in regular proximity to lots of high power ‘CAT’ Mode-S aircraft.

Are you seeing a flashing LED on the board in the FTDI lead ? - it should flash Red if data is being transmitted from your PilotAware. If not, try swapping it with the SDR in Port 2 and reconfigure both ports on the PAW accordingly. Let me know how you get on.

Regards

Peter

[Gramac]

Thanks again Peter. I am away for a fortnight now so will check what you’ve said when I return.

Best wishes

Graham

[Gramac]

Peter,

Just returned and had a test flight. I moved the Trig to port 2 and reconfigured to 9600 on both that and the Trig setup. I moved the GPS to the top left (port one) and set this to ’Auto’ in the configurations.

I still get ‘Warning no ADBS signal’.

I can confirm I am seeing a flashing red on the Trig USB cable connector and a flashing green and a constant red LED on the GPS device.

I am presuming that when using the PilotAware through my SkyDemon that there is no conflict with the Trig. The GPS reports my position correctly on my scrolling chart on SkyDemon.

Do you have any other ideas please ? Deeply frustrating these things unless they’re working right 😂

Many thanks

Graham

[Ian Melville]

Where is your aircraft based Graham?

[Gramac]

It’s just north of Derby.

[exfirepro]

Hi again Graham,

There is no conflict between using SkyDemon and supplying data to the transponder at the same time. One is via WiFi and the other is via the USB to serial RS232 converter, which are completely separate paths. We have lots of users running both at the same time without issues.

I’m starting to wonder if there is a problem with the FTDI lead (though I’ve never come across a faulty one) or with its integration into the transponder loom. I’m not sure how easy it will be to check this as this will depend on how it has been integrated. The only bit you could check is that the correct colour wires go to the correct pins on the Trig 25 pin connector. To do this you would have to remove the connector from the main Trig unit and open it up to check which wires go to which pins. Referring to the pin layout diagram in the TT21 Installation Manual (on Page 59 in my copy). I would expect to find the black ‘Ground’ wire connected to pin 4 on the Trig connector and the orange ‘Data Out’ wire connected to pin 5. If the coloured wires aren’t directly connected, you would need to track them back from the pins. If this is going to be too difficult let me know and I can give Danny at Mendelssohn’s a call.

Regards

Peter

[Gramac]

I can access the 25 pin connector quite easily by removing my seat and undoing it to look at the connectivity.  I will pop up again tomorrow to check the connector and report back. Thanks Peter

[Gramac]

Peter,

It was Danny at Mendelssohns who,-revised the wiring loom.  Let me check tomorrow and I will come back to you.

Appreciate your kind help.

[Gramac]

Peter,

Please find attached a close up photo of the inside of the 25 pin connector. 

The cable to the USB connector is sheathed in black. It looks correct, in that the black wire is connected to pin 4 and the yellow (not orange) is connected to pin 5.

Any views?

Should all baud rates be either 4,800 or 9,600. The Trig is set at 9,600 whereas the other ports at 4,800. Not sure if this has any potential effect.  The Trig settings are 9,600 to match that of the PA.

Could there be a connectivity issue at the USB end?

Officially confused now, so really appreciate your continued support.

Thanks

Graham