PilotAware
British Forum => General Discussion => Topic started by: bnmont on March 28, 2016, 01:26:09 pm
-
Short story. Took part in the adsb trial with nats and the return from my transponder was ok when fed nmea data from a handheld garmin etrek walking gps.
I have been having trouble since connecting my PAW to feed the transponder.
Today I decided to see if I could work out what was happening. The transponder when put into test mode displays a P indicating it is getting positional data from the PAW device.
However I fail to get the plane displayed on Skydemon.
As you can see from the screen shots my plane 406CB1 G-CIJO is shown in the logging screen however it does not display on skydemon. Is this correct behaviour? when the plane is on the ground not moving no display?
SILS SIL and SDA all zero which is required.
-
Skydemon display
-
Hi Brian
I see the problem, what you are looking at is a Mode S, but there is no ES (extended squitter)
The giveaway is that the relative barometric height is displayed '92'
But the relatve distance is '-', this indicates that there is no DF18 (extended squitter) data
Question is why ..
You can display the data being sent to the transponder, go to the configure page select trp for transponder, then go to the logging page. This will display the data being sent down the RS232
Thx
Lee
-
Hi Brian,
I wonder if the DF18 data is only sent while moving for the trt800.
I think I asked before, but what is the FW revision on the trt800 ?
Thx
Lee
-
Hi Lee,
Thanks for the reply, I will try and dig out the firmware version.
Brian
-
I hope this is not a silly question, but have you entered your licence key as it is showing all 0000000000. When the key is entered should it not be displaying?
I apologise if I'm incorrect.
-
I hope this is not a silly question, but have you entered your licence key as it is showing all 0000000000. When the key is entered should it not be displaying?
I apologise if I'm incorrect.
Normally you would be correct 👍
But in this instance Brian was a very early beta user, and his mac address is hard coded into the software, (note to self to take that out)
If you look on the same screen it says the expiry date
Thx
Lee
-
Dont you have to set Funke 4800 in USB port 1 ?
I didnt think you could see your own Mode S as their is a filter set on your own Hex code not to display your own position on Skydemon/RunwayHD.
John
-
Dont you have to set Funke 4800 in USB port 1 ?
I didnt think you could see your own Mode S as their is a filter set on your own Hex code not to display your own position on Skydemon/RunwayHD.
John
John is right, I missed that.
You need to configure which usb port is outputting to your transponder.
The main document describes which port is which.
Regarding the ICAO code, PilotAware does filter its own code, but it looks as though in this case the transponder ICAO code has not been entered, it currently has the automatic value entered
Thx
Lee
-
I may not have made this clear. The ipad logging screen is a second unit nearby hence the auto generated hex code.
The list of planes seen includes my plane 406CB1/G-CIJO ( highlighted red spot) but the plane is not displayed on Skydemon wheras others in the list are.
Does this help
Brian
-
I may not have made this clear. The ipad logging screen is a second unit nearby hence the auto generated hex code.
The list of planes seen includes my plane 406CB1/G-CIJO ( highlighted red spot) but the plane is not displayed on Skydemon wheras others in the list are.
Does this help
Brian
OK, that makes sense.
The main issue is that the transponder does not appear to be outputting any co-ordinate information.
this can be seen from the line in your traffic screen
406cb1, GCIJO, -, -, 92, 213, 1, 0, 0, 0, 0, 0
^
This field should contain the distance caclulated from the local and remote GPS positional information.
The fact that it is not shown, means it does not have positional information for ICAO address 406cb1.
I think what you would need to do, is to take a look at the messages being sent to the transponder.
You can do this in the following way for the PilotAware connected to the transponder
From web address 192.168.1.1
1. go to configure page and select 'trp', press save
2. go to logging page
This will display the NMEA messages being sent to the transponder, we need to capture these to evaluate
if they are legal (valid) messages.
If they are, then we need to know why the TRT-800 is not including this data in the Extended Squitter.
Thx
Lee
-
Thanks Lee,
I will investigate further.
Brian
-
Lee am I correct in assuming that 92 is the airfield elevation. If so this would be correct.What is the red highlighted number refering to?
Brian
-
92 should be the relatve height in ft, Red highlighted number is signal strength
Thx
Lee
-
Todays log screenshot.
I assume the highlighted lines is where the issue lies?
No message going to the transponder?
Although when in test mode P for position info appears.
Strange thing is I thought it was working correctly in the past.
-
I am using a chepo chinese usb to rs232 converter. Can anyone tell me the correct pins to be using in the 9pin plug?
-
Hi Brian
This is actually correct, the errors are ser-trx, which is the bridge you do not have.
There is a reference on the web for the dsub9, i also run 2 connected using a crossover, then connect to pc, to see messages streaming
Thx
Lee
-
Hi Lee, I have been using a converter. I just wanted to make sure i was using the correct pins to feed the transponder.
Thanks Brian
-
Hi Brian,
Did you eventually get the ADS-B Out functioning correctly? I have a feeling you did post something on another thread to that effect, but I can't find it. How was the problem solved?
The reason I ask; I have a friend that has a Funke TRT800H transponder (SW version 5.3) that he would like to connect to a PAW once they go on sale, but the aircraft is an Autogyro on a CAA Permit, so there will be different certification hoops to jump through.
Thx
-
Hi Moffrestorer,
The answer is I think it is now working OK, this is after trying several different usb to rs232 cables and semingly getting nowhere, despite being able to see a P when the transponder is in test mode.
After changing mt coax cable to the transponder antenna it now appears to be working.
Lee was able to see me on PAW(adsb) when I flew into Hinton last Sunday to do some air testing of PAW. And my track also showed up both ways on Flight radar24, however only my flight to Hinton showed on Planfinder.net. So yes working probably!
Regards Brian
-
Hi Brian,
I'm glad you now seem to have everything working.
Is there anyway you could post a link to the USB-RS232 cable you now use? Also, which D plug pin numbers are used to connect the GPS + and - signal to the transponder wire tails (which presumably connect to pin 12 and pin 1/9 respectively, of the TRT800)?
Thx,
Chris
-
Hi Brian,
I'm glad you now seem to have everything working.
Is there anyway you could post a link to the USB-RS232 cable you now use? Also, which D plug pin numbers are used to connect the GPS + and - signal to the transponder wire tails (which presumably connect to pin 12 and pin 1/9 respectively, of the TRT800)?
Thx,
Chris
I have at last got round to tidying up my installation and taking a few photos.
The USB to RS232 I used is this one. Its not the cheapest but as all the "gubbins" is in the usb plug and it comes with a long cable it seemed easiest to use.
http://uk.farnell.com/ftdi/usb-rs232-we-1800-bt-0-0/cable-usb-a-rs232-serial-convertor/dp/1686450?CMP=i-bf9f-00001000
The wires which appear to work correctly are:- Black from the converter to ground on the Funke external memory module and Orange to black on the Funke connector.
-
Hi Brian,
Thanks very much for the link and info. Very helpful to me and I'm sure, to others.
I prefer the layout of this cable but had dismissed it because there was no obvious compatibility with PL2303 chipset that Lee recommends. If it works for you it must be OK with the Pi B+.
Regards,
Chris
-
Hi Brian (and Chris)
out of interest what is the chipset reported for the cable you are using ?
you will see this reported by looking at
http://192.168.1.1
listed as
USB xxxx:yyyy | Description
thx
Lee
-
Will find out and report back.
Brian
-
Hi Brian (and Chris)
out of interest what is the chipset reported for the cable you are using ?
you will see this reported by looking at
http://192.168.1.1
listed as
USB xxxx:yyyy | Description
thx
Hi Lee,
This is what is shown.
USB 0404:6001 FTDI USB-RS232 Cable
Brian
Lee
-
Hi All,
New here after purchasing shiney new PAW at the LAA Rally. I have followed this conversation with interest as I would like to connect it to my TRT800 to utilise the ADSB-Out function.
I see Brian has posted some very useful information about his installation and a link to the cable he's used but there seems to be a question regarding the chipset not being as recommended. Perhaps Lee or someone could comment and set me straight as to which cable I need to buy or if it would be OK to use the one Brian has.
Many thanks and regards,
Matt
-
Hi All,
New here after purchasing shiney new PAW at the LAA Rally. I have followed this conversation with interest as I would like to connect it to my TRT800 to utilise the ADSB-Out function.
I see Brian has posted some very useful information about his installation and a link to the cable he's used but there seems to be a question regarding the chipset not being as recommended. Perhaps Lee or someone could comment and set me straight as to which cable I need to buy or if it would be OK to use the one Brian has.
Many thanks and regards,
Matt
I recall that Funke *may* try to sell you a cable for £100 or so in order to connect your RS232 wire :o
One of the other forum members can give you some advice on this, I will send him a PM, and ask to contact you directly
I dont think he wants his method publicised, for fear of getting into trouble
-
I recently enabled ADS-B on my Trig TT31 through PAW.
Trig recommended the Farnell USB-RS232-WE cable, costing about £12. The connections are, TXD (orange wire) to transponder serial input, Ground (black wire) to transponder ground.
This worked fin for me.
Regards.
Martin
-
Thanks for your help and advice and for the private messages which also helped enormously.
In case anyone else finds it useful this is what I did in the end.
I went with the open ended FTDI Chip Interface Converter Cable which was £15 from RS as my TRT800 Transponder cable came with tails ready for connection.
http://uk.rs-online.com/web/p/kvm-mixed-cable-assemblies/6877828/ (http://uk.rs-online.com/web/p/kvm-mixed-cable-assemblies/6877828/)
From reading this thread and from other advice plus information from the cable Data Sheet (which can be downloaded) and from the Transponder manual the connections I had to solder were:-
Transponder Cable Black (Rx) to USB Cable (Tx) Orange
Transponder Shield (Ground) to USB Cable Black (Ground)
All very simple and finished off with heatshrink to make the finished cable assembly. Note: I did not have to download any drivers for the USB.
There is one more step on the PAW configuration page which has to be done and that is to set the appropriate USB port to “Funke Transponder”. I initially forgot to do this despite already being advised I needed to do it and it caused a fair bit of head scratching as to why I couldn’t see CSA on the traffic page. Changed the settings and voila.
Also check the transponder setup page to make sure you have set NMEA 4800 baud and you are in receipt of a valid GPS signal as evidenced by the POS field.
I have chosen to permanently install the PAW unit behind the dash panel with the ADSB aerial screw mounted on top of the wooden combing. To do this I first removed the base magnet so it can’t interfere with the compass then I moulded a rubber base from SUGRU which can be screwed down and works well (Photo attached.)
For the P3i aerial I made up an RG400 aerial extension cable and mounted it to the panel itself via a bulkhead coupling so it is still visible to the sky through the bubble canopy but stays pretty much out of my eyeline. (Photo attached)
Hope this is of help to someone.
Matt(http://forum.pilotaware.com/C:\Users\Matt\Desktop\Pilot Aware\ps2\Inst.jpg)
(http://forum.pilotaware.com/C:\Users\Matt\Desktop\Pilot Aware\ps2\Aerial Base.jpghttp://)