PilotAware
British Forum => Technical Support => Topic started by: ibelmore on June 05, 2017, 07:47:46 pm
-
I have read through the forum and the many posts about this. I think I have followed all the instructions and advice correctly but I cannot get position data on the Transponder.
The FTDI cable is connected on port 1 (top left ) I have confirmed this as changing port 1 data settings in the config page stops the RED LED flashing on the USB clear plug.
Orange wire on FTDI cable to pin 5 on TT21, Black wire to pin 4 (triple checked!!) The FTDI plug is flashing red so it appears to be sending data (I saw someone said it would flash green but mine only does that whilst booting).
Using recommended Anker cig lighter plug and heavy duty power cable.
I have tried a different FTDI cable, second PilotAware box and even another TT21, all to no avail
Latest software on both
Settings are NMEA, 9600 on Trig and Transponder Trig, 9600 on the PilotAware.
PilotAware are bought bridges on Pi b+ with a current licence.
Pilotaware Home page shows everything working and all green tabs and correct USB info. I am getting position data on skydemon (ipad) and its showing ADS b traffic.
I am sure its something simple but I can't see what it is.
Any advice greatly appreciated
Ian
-
Hi Ian
You say you have a second ftdi cable, can you connect the two back to back (crossover)
Then connect one usb to a laptop running putty or realterm.
We then need to see what messages are received by the laptop
Is this possible for you to try ?
Thx
Lee
-
Ian,
Was just about to post when I saw Lee's.
I'm confused !!
Assuming you can confirm that this is a genuine FTDI USB to Serial Level (NOT TTL level) cable, FTDI part number USB-RS232-WE-1800-BT-0.0, and that it was bought from a reliable source, such as CPC Farnell or RS Components (some advertised on fleabay are cheap copies - often sold at 'normal' prices), Orange to Pin 5 on the Trig 25 pin connector and Black to pin 4 is correct.
It's worth double - OK 'quadruple' checking that you have definitely counted the pins leftwards from the top right looking at the wiring side of the 25 pin plug. Also worth doing a continuity test from the outside of each pin through to the bare ends of the FTDI cable on the back of the connector just to make sure the joints are sound.
Other than that the settings in your PAW and transponder seem OK. I'll double check against mine next time I'm down at the plane - probably Wednesday.
The only other issue I can think of is whether the fact that you're using a Pi 1B+ could be a problem. I'm pretty sure all the ones I've done have been Pi2Bs and can't remember if it works using a Pi 1B+ - Lee will be able to advise.
Regards meantime
Peter
-
Ian,
Is your Trig TT21 firmware at the appropriate release? Earlier releases of firmware needed updating.
Tony
-
He says it is Tony
Latest software on both
Peter
-
Hi Ian
You say it may be something simple. Could it possibly be as simple as the configuration settings under Chapter 6 of the TT21 installation manual that you have overlooked the setting 6.1.8 GPS Input.
you also have to consider item 6.1.10 to set the correct SDA/SIL level.
Sorry if you have already done this based on your reading of the documentation you mention in the opening post but thought it was just worth a thought.
Regards
Alan
-
Says he's set it to NMEA Alan. I was going to go through the rest of the settings once Ian has done the checks I suggested above. Although critical to obtain formal mod approval, the 'uncertified' SDA/SIL setting shouldn't be critical to getting the ADSB to transmit.
Peter
-
Thanks for all the replies everyone, Ive been without power up til now today so only just had a chance to read them.
Lee - I will hook up the cables and report back.
Peter - Yes, genuine cables from Farnell. Went thru the pins again this morning and definitely correct with good continuity all the way through.
Tony - Yes latest software on TT21
Alan - Yes, TT21 set to NMEA input, 9600 baud and uncertified GPS.
I will report back on the messages from the FTDI crossover hookup
Cheers
Ian
-
Hi Lee
Crossover test done and I can see the NMEA sentences going through.
back to check the Transponder wiring again............
Cheers
Ian
-
Still no Luck
I have completely redone the data wires to the TT21 with new wires and pins
Tested the output via crossover RS232 cable and PuTTY on my computer
But still no position reported on the TT21
Can someone confirm that it is just 2 pushes on the FN button to display the output when the transponder is in ALT mode, I just get dashes instead of numbers
Not sure where to go now
Ian
-
Ian
I apologise if you have done this. But when you updated the tt21. Did you update the tt21 head display too?
I have the same setup as you describe but I can not remember about pushing the FIN button twice, I will have to check the next time I'm at the airfield. Another simple thing that may have been overlooked, do you have a GPS lock or connection to satellites when seeing the ---- ? Sorry if you already Covered this.
-
Hi Richard
No need to apologise, all suggestions gratefully received.
Yes the head is up to date (1.12) The unit is at 2.7 (not 2.10) but it shouldn't affect this issue. I think I will get it all back to Trig for an update and check anyway as I have run out of ideas.
GPS signal is good and the PilotAware is sending it to my iPad
Cheers
Ian
-
Ian
It is looking like your firmware version (possibly) I will also check my version at the weekend to see which I have. I had a similar problem as it did not display the GPS position. Another thing to check is, can you see your own aircraft in the PAW traffic table displaying ACS-- that will indicate that you are transmitting ADSB?
-
Hi Richard
I've checked the Traffic page and, No, Its not transmitting ADSB.
I don't think it will until it gets a valid position fix to the transponder.
I have tried with another TT21 Transponder which does have the very latest software and Its not getting the position data either.
Cheers
Ian
-
Ian
Mmmmm......
Reading above it sounds like you have everything correct....... Thinking....... :o
Ian,
When you did the computer test did you get the green flashing light in the USB cable? My cable flash green when connected to PC or PAW.
........ still thinking.......
-
From the FTDI cable manual, Red LED is the Received LED, you should be seeing green if you are transmitting from the PAW to the TT21.
You seem to have wired and configured it as I would expect. Can you attach a photo of the cables in the 25-way connector? Also the label on the FTDI cable?
Note that by connecting the two cables back to back you have not proved the version of cables you have TTL or Serial. If they are both the same version it will work in crossover
-
Hi Ian
The flashing red concerned me too. When I connected the PilotAware to a Computer with 2 FTDI leads the lead on the PilotAware flashed Red and the one on the Computer flashed Green and the NMEA data was sent across ok.
Pic of the Cable attached, it was ordered from Farnell.
Unfortunately I can't get to the 25 pin for a pic til next week but I am now 100% certain it is wired correctly.
Cheers
Ian
-
Certainly the right lead Ian. I have one here in front of me, and you have the correct colour wires for ADSB Out. Definitely something strange going on. Needs further investigation.
Regards
Peter
-
Thanks Peter
I think my next move is to get the units back to Trig.
Still concerned about the flashing red LED on the FTDI cable when Ian says it should be green for Tx. Having said that it does send out the data.
Ian
-
Yup, that is the correct cable. As you have proved with the back to back test that MNEA sentences are getting through to the PC terminal, I would conclude the issue is withe TT21, or the way it has been cabled at the 25 pin connector.
Don't worry about the colour of the LED. I worked in telecoms for years and always associate red with transmit and green with receive. I wonder if the manual is wrong? Need to find my FTDI cable to have a look tonight. What does matter is that it works.
-
Thanks Peter
I think my next move is to get the units back to Trig.
Still concerned about the flashing red LED on the FTDI cable when Ian says it should be green for Tx. Having said that it does send out the data.
Ian
Give Trig a call. They are very good and can usually turn the units round in a few days.
I'm heading down to the airfield shortly so will check out the FTDI LED colours rather than speculate.
Regards
Peter
-
Thanks for all the help and advice, I will let you know the outcome.
Cheers
Ian
-
Mine also flashes red on transmit. Don't have a transponder, let alone a TRIG so unable to do a comparison test
-
Ian (ibelmore)
I'v been doing a little home work for you.....I have tried to Attach my settings for the TT21 but the file is too large can you PM me you email and I will send them on to you .... as earlier in this thread it seems your wiring is correct and the correct USB to RS 232 are being used. This is all good.
The TT21 Version is also correct as it is the same as my TT21. and is what I updated to after sending back to Trig. (there is a newer version now but the one you have is OK)
The Bound rate I have may be different to what you are using too. As my GPS is direct into the TT21 and not through PAW (But it should just work the same. Try different Bound Rates)
Another little thing.... The GRD from the GPS (PAW) is connected direct to my GRD BUSS and not to pin 4 or 6
I hope this helps ?
-
Next Page
I Hope this helps
-
Thanks Richard
PM sent
Ian
-
Ian
this is what mine shows with no GPS signal and the second one with,
ivor
-
photos came out back to front but i'm sure you get the picture ;D
-
Richard / Ian,
With the exception of the GPS input (NMEA 0183) and Baud rate (both must be set to the same rate, but 9,600 as quoted by Ian previously should be fine), none of the other settings on the TT21 should be critical to getting it to transmit (though some of course would lead to 'illegal' transmissions).
The PAW settings are simply 'Transponder Trig' and the Baud Rate for the correct USB port.
Having assisted with setting up several of these units for ADSB Out via PAW, The two most common issues I have come across are...
1. Setting up the wrong USB port in PAW. The numbering is NOT as shown on the Quick Start Guide. Lookin at the PAW with the Ethernet port to the left, the USB ports are numbered:
Ethernet 1 3
Port. 2 4
2. Misreading the pin numbering in the 25 pin connector - remember the pins are numbered from the top right looking at the BACK i.e. CABLE SIDE of the plug, NOT the connecting face.
If both of these are definitely correct Ian, I am frankly stumped.
If you still can't get it working after rechecking your wiring, let me know and I will pop down to Trig and have a chat with the technicians for you.
Regards
Peter
-
Ivor,
Thanks for the pics, interestingly, i only get dashes where the position should be and no warning.
I will have to look at it again next week.
Richard
Yes, definitely correct port and wiring, like you, I'm stumped.
I've had a couple of weeks away from it so I will go down next week afresh and go through it again, one last time before sending the unit back to Trig to rule that out.
Thanks again
Ian