PilotAware
British Forum => Technical Support => Topic started by: AndrewButler on October 03, 2023, 09:18:32 pm
-
Hello - New to the forum seeking assistance.
I have hardwired my Rosetta to my Advanced Flight Systems EFIS using a FTDI USB cable plugged into USB Port 1. Is GDL90 enabled on the Rosetta as I see a (TBD) beside GDL90 in the configuration page? I am asking because I can’t get the EFIS to acknowledge a connection to the Rosetta.
See pics attached of options on the EFIS.
Thank you all for your help.
Andrew Butler.
EI-EEO.
-
At a guess, you would set Traffic/Serial 0 if that's your port 1 to be GDL90/NMEA115K on your EFIS, and then set the Rosetta port driving it to GDL90 in the protocol list and also to the right baud in the speed drop down, which would be 115,200 then be sure to save the changes made.
-
Thank you Steve.
Do you know what the (TBD) after the GDL90 and MAVLINK options mean? The reason I ask is because in the EFIS manual it states that the ADSB settings means the GDL90 protocol. Assuming that to be true then using the one of the three ADSB settings matched with the PAW GDL90 output at a matching speed should work..... but it doesn't.
Andrew.
-
Thank you Steve.
Do you know what the (TBD) after the GDL90 and MAVLINK options mean? The reason I ask is because in the EFIS manual it states that the ADSB settings means the GDL90 protocol. Assuming that to be true then using the one of the three ADSB settings matched with the PAW GDL90 output at a matching speed should work..... but it doesn't.
Andrew.
I think you can ignore the ADS-B settings - you need to set the serial port to do traffic, then within the settings for traffic choose GDL90/NMEA115. Then you need to set the PAW to do GDL90 out, at a baud rate of 115,200 baud.
I've not seen TBD before but which model of Advanced Flight Systems EFIS is it?
In both pictures it looks to me like you are choosing a role for the Serial Port 0, then choosing settings within that role to make it work. So Traffic needs to be green, then within Traffic make your settings as needed.
-
Andrew,
My guess would be that TBD means ‘To Be Done’ - i.e. work in progress - but Lee would have to advise.
As Steve says, if you can give us some more info about your unit, or a link to the installation/setup manual(s), we can take a better informed look for you.
I take it you are using the Orange and Black wires in the FTDI to supply Data Out and Ground respectively. Also as Steve has said, matching baud rates both ends is Critical.
Best Regards
Peter
-
Thank you Peter. Yes, if TBD means that, which is what I suspect, then it just won't work. Hence my query.
Yes, I have taken the FTDI Tx wire and attached it to the applicable Rx pin in the EFIS. Black is connected to ground (EFIS casing).
The Traffic and ADSB photos above are the relevant available EFIS settings for the EFIS serial ports of which there are five available (0 to 4) on the AFS 5400.
How do we get Lee to respond to this query TBD? If it is To Be Done, the next question would be an ETA for its enablement.
Thanks all for your help.
Andrew.
-
I would try Flarm Out (115K Baud rate) and link it to the GDL90/NMEA serial traffic input.
Flarm Out is used for the Dynon EFIS (who I think make the AFS systems) and I believe the correct information is sent from the Flarm Out USB in the Pilot Aware.
My Dynon HDX uses this set up, albeit with a lower baud rate.
http://forum.pilotaware.com/index.php/topic,2282.msg23780.html#msg23780 (http://forum.pilotaware.com/index.php/topic,2282.msg23780.html#msg23780)
-
Thank you Paul. Just back from the field (EIMH). I tried that setting pairing. No joy :(
On the plus side, I am nearly finished the hard wired install of my PAW. I am replacing a TrafficWatch unit that was installed just above my EFIS so I can reuse the audio 3.5mm plug and external antenna. I will install a 768Mhz external antenna probably at next annual. I will put the mouse GPS antenna on the dashboard. Nice it is black and low profile. I am placing the PAW under the dash where the TrafficWatch was velcroed to the top of the EFIS. Being so light, not an issue.
Dyon actually bought AFS a few years back, with AFS slowly moving in the Dyon compatibility direction.
My aircraft is EI-EEO a Vans RV7 first flight Feb 2011.
Andrew.
-
Hi Andrew,
Can you send a link to the USB/RS232 converter you are using ?
Thx
Lee
-
Thank you for the reply.
I may be using an incompatible cable.... I have just ordered this one:
https://ie.farnell.com/ftdi/usb-rs232-we-1800-bt-0-0/cable-usb-a-rs232-serial-convertor/dp/1686450 (https://ie.farnell.com/ftdi/usb-rs232-we-1800-bt-0-0/cable-usb-a-rs232-serial-convertor/dp/1686450)
This look okay?
I'll let you know how I get on.
Best regards,
Andrew.
-
That one is correct
Thx
Lee
-
Guess what. Using the correct cable worked. I am now connected to the AFS using GDL90 at 115K baud.
Apologies for the time wasting.
I took a test flight last night. I have some tweaking to do. I was getting incessant "Traffic" alarms coming through on the audio and couldn't seem to be able to turn them off no matter what I changed in the config settings. Will test more.
Also, on the EFIS, the Aircraft Image was accompanied with an arrow and a couple of sets of 0000s. What are these, and is there a way to remove them from the feed to the EFIS? When I zoom out, they are merged with the aircraft image and when I zoom in as shown in the image they move back and forth in front of the aircraft image. See attached:
Any ideas how to remove?
Once again thank you all for your help and apologies for using the wrong cable!
Andrew.
-
I was getting incessant "Traffic" alarms coming through on the audio and couldn't seem to be able to turn them off no matter what I changed in the config settings. Will test more.
Where is the audio being generated? In the EFIS or in the PAW? If in the PAW and audio to your intercom then simply adjust the ranges on the PAW Radar screen.
If in the EFIS, then you need to adjust ranges in the EFIS whilst leaving the PAW ones fully open/no limits. If you are desperate, then you can reduce the amount of warnings (by discarding the ones further away) by reducing the limits of reports in the PAW Radar Screen. This is not the correct way to do it, you should leave the Radar screen unlimited and cut back on warning in the EFB/EFIS. I know as I write this that Peter R will be flagging up warnings about doing things the correct way.
Also, on the EFIS, the Aircraft Image was accompanied with an arrow and a couple of sets of 0000s. What are these, and is there a way to remove them from the feed to the EFIS? When I zoom out, they are merged with the aircraft image and when I zoom in as shown in the image they move back and forth in front of the aircraft image. See attached:
Any ideas how to remove?
Is the image the one of your aircraft or other aircraft? If it's of other aircraft then it looks like there is some configuration to be done in your EFIS. Again without the exact model of EFIS it's hard to tell or for others with the same to recognise it and help.
-
Thankyou Steve. It's an Advanced Flight Systems 5400.
It never occurred to me that the EFIS was generating the audio. The only word coming through was "Traffic". I will review the EFIS documentation and traffic audio alerting options.
For the picture, the yellow aircraft is me. Not sure what is generating the accompanying zeros and yellow arrow. I'll dig further on the configuration aspects of the EFIS.
Andrew.
-
The other thing to check is that the firmware is up to date. Worth comparing the firmware installed in the unit and latest version on the manufacturer's web site.
-
The "Traffic" audio alert was coming from the EFIS. I could only disable it by turning off the GDL90 Tx on the PAW.
The EFIS was alerting to Traffic at a time when only ONE traffic item was being picked up by the PAW, a C/S Transponder. See here:
https://photos.app.goo.gl/bEdAAyG78d6aCtYK7 (https://photos.app.goo.gl/bEdAAyG78d6aCtYK7)
Question 1: Are C/S transponder traffic contacts transmitted in the GLD90 Tx data stream?
Question 2: If yes, how can they be filtered out of this stream or would using one of the other Tx settings do this by default?
If the answer to Question 1 is yes, I suspect this C/S traffic data arriving at the EFIS may be the cause of the NULL traffic being displayed under the aircraft icon.
See full transcript of query to Advanced Flight Systems below.
Thanks again for your help.
Andrew.
RV7
EI-EEO
----------------------------
ADSB Nuisance audio "Traffic" warnings
Hello,
I have this week hardwired a PilotAware (https://www.pilotaware.com/) unit into EI-EEO. It has ADSB traffic reception amongst its many capabilities. I have successfully connected it to the EFIS using one of the serial ports set to ADSB 115k.
The EFIS picks up the PilotAware Traffic and displays it correctly. Only issue is that it incessantly reports an audio "Traffic" warning - this may be because the EFIS is receiving traffic that has no bearing or range data (raw Mode C/S Transponder signals). See real example here that the EFIS was reporting as "Traffic". This was the only traffic the PilotAware was picking up at the time, and the EFIS was reporting an audio "Traffic" alert. The only way to stop the "Traffic" alert was to break the Tx GDL90 data stream from PilotAware.
https://photos.app.goo.gl/bEdAAyG78d6aCtYK7 (https://photos.app.goo.gl/bEdAAyG78d6aCtYK7)
Q1. Is there a way to filter the audio "Traffic" warning for this scenario?
Q2. If I cannot filter, can I disable the warning, or outright delete the audio file?
Secondly and related, on the EFIS I see some NULL data showing up behind the self yellow aircraft ICON. See below photo for a maxed zoom of what it looks like. In this maxed zoom level, the Yellow Circle and two sets of noughts are not stationary, they are moving forward slightly in a cyclical manner, starting from behind/underneath the aircraft icon every three seconds or so.
Could this NULL traffic data be caused by traffic data records received that have null fields for bearing and range? i.e. the Mode S traffic shown above?
https://photos.app.goo.gl/rC1yYnUPxN4WFiaV9 (https://photos.app.goo.gl/rC1yYnUPxN4WFiaV9)
Q3. Is there a way to filter this out, as I am about to resize my aircraft ICON (make it smaller), and this NULL traffic signal around it will be a distraction.
I am in contact with PilotAware about this to see if it does indeed Tx all Traffic types as shown above and if so, whether it can be filtered in some fashion.
The reason I am going to all this trouble is that AFS is now supporting Airmate mapping/charts & plates and I have just purchased a subscription from them - though I am having issues with this too that Ken Chard is working directly with Airmate. Another topic
Thank you for your help,
Andrew.
RV 7
EI-EEO
-
If it's anything like the Dynon SkyView, I am 99% sure I only get a 'Traffic' visual warning when it sees Mode C (possibly Mode S). I have got traffic warning audio switched off, as I get that from SkyDemon via Bluetooth iPad to headset.
I am pretty certain I don't get a 'Traffic' banner when it sees ASDB/PilotAware traffic. In other words, positional traffic good, non-positional traffic bad.
You could reduce your Mode C/S filters in your PAW or, of course, you could set it so it doesn't show non-positional traffic. This way the traffic will not get passed (or is it parsed......I don't know the jargon) to your EFIS and will, therefore, not appear on the EFIS and will not set off any warnings.
You might be able to see the two targets on the map below. One is Sandown's ATOM station and the other is ADSB/PAW. Note there is no 'Traffic' banner. The same thing on the PFD but I can't attach that because of the daft photo size restriction.
-
A couple of daft questions:
Have you got a transponder? If so, can you check that you have set the ICAO code correctly in both the PAW and the transponder. If the code does not tally in them both there'll an aircraft constantly warning close by...
For a mode S transponder, it is not enough to set the call sign - the ICAO code must also be set. Can't remember what to do for mode C.
Also, are you sure you are not flying with SafeSky or another Internet based form of EC on your phone? If you are, you'll get a ghost aircraft all the time.
Paul makes some very good points about Mode C/S notifications. PilotAware advises you do not turn on the Mode C/S alerts without reading through the detailed briefing to ensure you are ready for the situation it will put you in.
In my previous post I suggested how you could limit the amount of traffic alerts, by changing the ranges in the PAW radar screen. As Paul says, you can bin all Mode C/S alerts by looking in the config page. You will need to read the Mode C/S briefing page.
It's here:
The PilotAware Mode-S/3D October 2020 (https://global-uploads.webflow.com/5d56c24810fbfdbe08b488cd/603d4af5086dc120a59e56d4_201012%20Mode-S3D%20Introduction%20New974ff381e05bcfdafef1c9c167ec471743db7d8b560da181aefa11812daadc6d.pdf)
-
Also, are you sure you are not flying with SafeSky or another Internet based form of EC on your phone? If you are, you'll get a ghost aircraft all the time.
Very good point. We had a EuroFOX customer who did exactly that. It took ages to figure out why he was chasing his own tail, because all of his settings etc were spot on. It's only when he mentioned a new product he'd heard about that the lightbulb came on.