PilotAware
British Forum => Technical Support => Topic started by: crisisguy on March 08, 2017, 06:20:29 pm
-
Ive purchased a serial to USB connector https://www.amazon.co.uk/gp/product/B00QUZY4WO/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1
Ive connected the Transmit out to a serial input on the skyview and tried various settings on both the PA (which recognises the USB-serial adaptor) and the Skyview but nothing is happening - no packets are being received by the skyview.
I know the serial input works on the skyview as a gps puck was connected on this channel before and worked.
How can i test if the usb converter is sending data?
any other things i can try?
thanks
David
-
Hi
Please take a look and post here
http://forum.pilotaware.com/index.php/topic,819.0.html
The only way to test that the output from the rs232, is to connect to another rs232 cable into a terminal program, eg putty
Thx
Lee
-
thanks Lee
i read this post and did as the OP suggested
Is putty freeware?
David
-
Is putty freeware?
Yes, you can use any terminal emulator you wish, PuTTY, RealTERM, HyperTERM ...
Thx
Lee
-
thxs Lee
Ive noticed the USB port settings only list a FLARM -IN , is this the correct one to use?
-
No, you want the 'Traffic Dynon' option.
-
Ive purchased another serial - usb cable, have connected the 2 together (both are recognised by the PC and the PA box). Ive set putty to serial connection and same com port on the PC but nothing is showing on the putty screen
im attached a log file of the pilot aware
pilot Awre is running latest version PilotAware Version(20161222) and ive attached a grab of the home page
any further suggestions?
thxs for the help as would be great to get this working on the skyview
-
Silly question, but you have set the correct port to Dynon haven't you?
All baud rates correct?
-
Looks like you have configured the wrong port ?
All those errors mean it is unable to send data
can you post your config page, and tell us which of the 4 USB sockets you have connected your USB/RS232 dongle
Thx
Lee
-
thxs Lee
I tried the cable on both USB ports 1 and port 4 (does it make a difference?) - that said i've used the port the PA shows on the config page - as attached
The baud rates were set the same on both output on PA and the PC - I tried various baud rates, matching them on botht he PA and the PC
i set the output on the PA to dynon traffic and also tried auto
config page attached
thxs again Lee and others
-
hers ascreen shot with the cable on usb port 4
-
David can you supply a photo of the USB/RS232 cable in the port, so we can see which port you are using. Also a screen shot of the config page showing the USB ports?
Can you also confirm which colour wires you connected together to link the two cables. They must cross-over.
We will get there in the end!
-
David,
We need to see which port you have the USB / RS232 cable in. With the ethernet port on the left hand side, the PilotAware ports are numbered as follows: -
Ethernet 1, 3
Ethernet 2, 4
This is NOT THE SAME order as the port numbering shown on the quick start setup instructions.
You need to know the correct numbering to allow you to configure the ports on the PAW 'Configure' Page, which is why we need a screenshot of that to tell us which ports are configured as what settings - the USB Port reporting on the PilotAware 'Home' Page - which you have posted twice - tell us what is connected, but NOT in which port - as the order they are listed in doesn't bear a direct resemblance to the actual USB port numbering.
Also, you need to connect the Paw Tx to your Dynon (or PC) input, hence why Ian has asked for details of which pins/wires you have used. Simply connecting two Serial cables together by for example using a double male adaptor, doesn't ensure connection of the correct wires between the two devices.
Regards
Peter
-
thanks Peter and Ian - i got it working through putty
2 things i did wrong - i used a gender changer connector for the 2 cables, I didn't appreciate i needed to crossover the Tx and Rx pins
I had configured port 4 as the Dynon traffic and not appreciated the usb assignments as per Peter's post. The usb serial cable is actually plugged into port 1 (top left next to the Ethernet plug)
Ill take it down to the plane later today and check it there, however, this is now looking promising as lots of data is flowing into the putty screen where as before there was nothing
David
-
Hi David,
Well done and thanks for posting your 'mistakes'. That really helps everyone else avoid them! Glad you have now got the data flowing via PuTTY. It should work fine in the plane now. Please let us know.
Regards
Peter
P.s. just edited my earlier post as I noticed I was talking about 'transponders' instead of Dynon systems. One of the hazards of replying to multiple Forum posts when you should really be in bed :-[ Fortunately the principles are the same, so no harm done. ;)
-
I think in modern times we've lost the art of RS232 communication! ;D
When testing my USB-serial adaptors when they were first used on the PAW, I used an old "null modem" cable I had to connect the two dongles together. You can probably still buy them if you look. Just keeps things neat while experimenting.
-
Bit of trivia/nostalgia for you Paul
https://youtu.be/CDlj0jBtYmQ
-
;D
As someone who spent a year designing RS232 data link installations in telephone exchanges for my sins.
-
Nice one Bob,
Maybe Paul and Ian could get together and record a version 8) - unless of course they already have..... ;D ;D ;)
Still useful kit though!
P
-
;D
As someone who spent a year designing RS232 data link installations in telephone exchanges for my sins.
Still designing and building RS232 & RS485 today, lots of gear still uses it.
-
Just to let you know all worked well in the skyview, whilst the skyview gives a traffic warning, it doesnt give the more detailed audio details of where the target is so im keeping the audio output from the PA into the music input on the Garmin GMA 240. On take off and landing i mute the music input, the skyview only gives traffic alerts when airborne.
Thanks for the great support and great product, wish it were made mandatory for all GA aircraft as am surprised how many aircraft i see visually have no conspicuity device.
-
Hi again David,
Thanks for the update. Glad you have got it all working.
....wish it were made mandatory for all GA aircraft as am surprised how many aircraft i see visually have no conspicuity device.
Unfortunately unless it becomes mandatory, this situation is likely to remain. All we can do is try to make sure we can 'see' as many of those aircraft / systems that are transmitting position data as possible and keep spreading the word. Oh...and make sure we don't allow ourselves to become too engrossed in our screens and ALWAYS maintain regular and effective visual scans.
Best Regards
Peter
-
Tried to connect a PAW to Dynon Skyview with a USB RS232 port on a friends plane. All configured and works a treat. Skyview has been configured as FLARM and the traffic is showing up on the display with direction of travel. The only issue I have is next to the traffic symbol is +99 and not the relative height. Has anybody else encountered this problem and is there a fix anywhere....I can't see any user configurable areas anywhere on the Dynon.
Kind regards
Brinsley
-
I have just connected up my Skyview, and have the same display as Brinsley(i.e. +99 showing against traffic).
Any progress/explanation on this point ( I have tried a search with no other hits)
BobD
-
99 I am guessing is 9900ft, I wonder if traffic above 9900 is reported as 9900 as this is the highest can be represented. Are you able to compare against RADAR or a nav tool ?
-
Could be, as I am testing it in my garage, and picking up traffic around 36K feet. As I don't live near an airfield, I seldom see traffic lower than this.
It is impressive that I pick up anything with the aircraft in the garage, and the PAW buried in the panel.
I read in some old posts that there may be plans to use Dynon Skyview GPS feed for PAW. Any progress on this ?
BobD
-
Apologies if I am hijacking this thread but I'm also having problems connecting PAW to Dynon SV, albeit different circumstances.
I've read previous posts and connected/configured likewise.
SV shows 'Traffic Fail' message on map. Looking at stats for the SV serial port:
-RX continuously increments and quite rapidly
-Sentence errors: 0
-Good sentences: 0
-Group errors: increments slowly
I tried posting on the Dynon forum but they were less than helpful saying only that PAW was not speaking the same language as SV. As others have successfully connected, this cannot be the problem.
PAW is configured as 'Traffic Dynon'.
SV is configured to serial3 as 'Garmin TIS Traffic'. I have also tried 'Flarm Traffic' but, in addition to above stats, that also gives a 'Flarm offline' caution message.
I've tried various baud settings; each matching.
I suspect the incrementing 'group errors', and zero 'good sentences' mean something but not sufficiently savvy to know what.
Any help appreciated. Thanks
-
Have you checked you are running the latest PilotAware version? A significant part of the 20170619 update was to deal with SV issues. The latest version is 20170721 - see http://forum.pilotaware.com/index.php/topic,948.0.html. Lee may be able to give further advice when he comes on.
Regards
Peter
-
Apologies if I am hijacking this thread but I'm also having problems connecting PAW to Dynon SV, albeit different circumstances.
I've read previous posts and connected/configured likewise.
SV shows 'Traffic Fail' message on map. Looking at stats for the SV serial port:
-RX continuously increments and quite rapidly
-Sentence errors: 0
-Good sentences: 0
-Group errors: increments slowly
I tried posting on the Dynon forum but they were less than helpful saying only that PAW was not speaking the same language as SV. As others have successfully connected, this cannot be the problem.
PAW is configured as 'Traffic Dynon'.
SV is configured to serial3 as 'Garmin TIS Traffic'. I have also tried 'Flarm Traffic' but, in addition to above stats, that also gives a 'Flarm offline' caution message.
I've tried various baud settings; each matching.
Hi skyboy
The Traffic format should be 'FLARM' not Garmin.
Some questions.
1. Can you supply a reference to the USB/RS232 device you are using
2. How have you configured the USB port in PAW(a screenshot would be useful)
Thx
Lee
-
Skyboy, I can confirm that my connection between PAW and Skyview Touch is working fine. I followed Carlp101's previous instructions. I set up Skyview port 1 as FLARM and 57600 baud. I plugged the USB/Serial cable into PAW port 1, and set it at 57600 baud also. I am running the latest PAW hotfix, and Skyview v15
It does look as though the 99 signifies traffic above 10K, as I spotted a Ryanair flight descending this afternoon below 10K, and the Skyview display started to reduce (i.e 94)
Just to repeat the question from my earlier post, any plans to use the Skyview GPS for a PAW feed ?
-
Hi Lee
Configuration:
PAW:
Version 20170223
Port 3: Traffic Dynon, 9600 baud
SV:
Version 15
Serial port 3: Flarm Traffic, 9600 baud
USB/Serial lead: http://www.maplin.co.uk/p/usb-to-ttl-serial-cable-cable-n74de
Thanks
-
Hi Skyboy
USB/Serial lead: http://www.maplin.co.uk/p/usb-to-ttl-serial-cable-cable-n74de
I think this could be your problem.
Does the Dynon want serial TTL or RS232 ?
Most systems want RS232, which is +/-12v, TTL is 0/+5v, the logic is also inverted
Logic 0 - RS232=+12v TTL=0v
Logic 1 - RS232=-12v TTL=5v
Can anyone else confirm if the Dynon requires TTL or RS232 ?
thx
Lee
-
Hi Skyboy
USB/Serial lead: http://www.maplin.co.uk/p/usb-to-ttl-serial-cable-cable-n74de
I think this could be your problem.
Does the Dynon want serial TTL or RS232 ?
Most systems want RS232, which is +/-12v, TTL is 0/+5v, the logic is also inverted
Logic 0 - RS232=+12v TTL=0v
Logic 1 - RS232=-12v TTL=5v
Can anyone else confirm if the Dynon requires TTL or RS232 ?
thx
Lee
As they state RS-232 in all the manuals then it will be full RS-232 and not TTL Serial - so a USB->RS-232 lead is needed rather than the TTL given above.
-
I wired mine with a USB RS232 +-12v adapter....Works perfectly
http://uk.farnell.com/ftdi/usb-rs232-we-5000-bt-3-3/cable-usb-rs232-ft232r/dp/2419948?ost=USB-RS232-WE-5000-BT_3.3&scope=partnumberlookahead&exaMfpn=true&searchref=searchlookahead&searchView=table&iscrfnonsku=false&ddkey=http%3Aen-GB%2FElement14_United_Kingdom%2Fw%2Fsearch
-
.....The same cable we recommend for connecting FLARM-In to PilotAware or PilotAware GPS Data Out via RS232 to most (if not all) Transponders, Brins.
Regards
Peter
-
Thanks Guys, not surprised it's me being daft. I'll get the correct cable and try again. Easy when finally you find someone who understands these things.
-
Now working. Initially, same as before at 9600 baud but works fine once changed to 57600.
Thanks all.
-
Now working. Initially, same as before at 9600 baud but works fine once changed to 57600.
Thanks all.
Great News!
-
Ive given up with the PA - Dyon connectivity. Even when working the display is no where near as readable as the ipad Skydemon setup.
I run my ipad connected to the PA and i share the flight plan with my iphone over airdrop and then have the iphone connected to the Dynon systema nd sent it over the Dynin wifi. that way i have 2 independent GPS crosschecking location.
Only issue is the SD shows loss of internet connectivity pop ups unless i set connectivity to offline.
-
Hi crisisguy
Ive given up with the PA - Dyon connectivity. Even when working the display is no where near as readable as the ipad Skydemon setup.
Do you mean you have given up because you cannot get it working, or because the Dynon display is not useful ?
Thx
Lee
-
It works intermittently and then drops out occasionally Lee
that said, even if it worked flawlessly i am still going witht he SD as the display is much better
-
I have just posted this on the Dynon Forum and I'm guessing that Skyboy999 is Steve-D over there
Just bumped this thread to see if there is any additional information.
I am just in the process of snagging my new aircraft, and have a similar problem to the OP. My Skyview is connected to PilotAware via the RS232 connection, and on original startup, traffic shows as expected. However, after a few minutes, the Traffic Fail message appears. My PilotAware is connected to my android phone, and that appears to be still operational in flight (although I can't swear it has "seen" other traffic in the short flights I have made, but the aircraft icon doesn't disappear).
I haven't looked at the RX or sentence counter yet (as suggested in Reply #1), and will do next time I visit the airfield, but just wondered if anyone else had experienced a similar problem, or if the OP found a solution ?
On another point, Crisiguy's tip for having two devices connected between PilotAware, Skydemon and Skyview is good, in his case Iphone and Ipad. I decided to do something similar so I can transfer my Skydemon Flight Plan to Skyview using WiFi, but retain my PilotAware Wifi connection to SkyDemon. I use an Android phone, and an Android Tablet. The problem is you can only connect your phone or tablet to one WiFi source at a time. To get around this, I found an Playstore App that allows you to prioritise the WiFi source on the phone and tablet, called (surprisingly!) WiFi Prioritizer I simply prioritise the phone to PilotAware, and the tablet to Skyview.
-
My friend Paul has reported some issues with his Skymap V running from the PilotAware via RS232. He said it reports "no GPS position" or similar. I give him a GPS mouse to try. However on further questioning, he said that it's completely stable on a tablet connected through Wifi, so I don't think it's the GPS.
He said that the connection is at 9600 baud currently. He thought this might be too high and that data might be getting corrupted. I suggested it might be too low and that it might be a buffering problem.
Any suggestion to the amount of data being send and the most suitable baud rates to use?
-
9600 baud is way too low, you need at least 57600 baud, and preferably, as high as it will go
Thx
Lee
-
Hello,
I don't succeed to connect PAW to the dynon.
I make all that you say. I've a ugreen cable of 3 meters. I am asking if the cable is the problem.
I have seen somebody buy this type of cable. Is he properly work ?
Thanks
Nicolas
-
Can you provide a link to the cable you are using
Also post a screenshot of your configure page
-
I assume I use pins 7&8 serial port 3 from the Dynon D37 EMS harness. However I guess I need to wire them into a serial 9 port female RS232 so I can plug into the recommended USB / serial lead.
-
The following posts have been merged from a separate thread initially started by JDevoy titled 'Mobile dongle (as an iGRID Hotspot) instead of iPhone'.
Do you know the pin outs for the usb to serial cable. I have the 2 TX/RX identified from the Skyview I was wondering what pins on serial connector end I need to wire them into.
Cheers
James
Hi James,
If you're using the recommended FTDI cable, the colour codes are:
Black = Ground
Orange = Data Out (from Pilotaware)
Yellow = Data In (To PilotAware)
Sorry, I'm not familiar with the Dynon side.
Regards
Peter
-
Got the cable I know the pins on the Dynon EMS that are TX which I assume as it’s TX from Dynon it’s data in on PAW and opposite for RX. Dynon has a bunch of grounds available on the EMS37 so will use one of those. Assuming as you know the colours you chopped the end of the serial cable and directly connected.
-
You only need to wire up the orange and black wires, since you're just receiving the PAW Tx into your Skyview.
UNLESS we're able to transmit GPS info from the Skyview to the PAW now. I don't think I've read a conclusive answer to that question.
-
Got the cable I know the pins on the Dynon EMS that are TX which I assume as it’s TX from Dynon it’s data in on PAW and opposite for RX. Dynon has a bunch of grounds available on the EMS37 so will use one of those. Assuming as you know the colours you chopped the end of the serial cable and directly connected.
As Paul has stated, you should (for the moment) only be using the Orange and Black wires, but I'm confused by your statement about 'chopping the end of the serial cable - which makes me suspect you are not using the recommended FTDI cable - in which case our colour coding advice may well be inappropriate.
To clarify - the FTDI USB to RS232 Serial Cables that we recommend (e.g. Mfr. Part No. USB-RS232-WE-1800-BT 0.0 - RS Stock No. 687-7828, or the 5 metre long equivalent - which is Mfr. Part No. USB-RS232-WE-5000-BT 0.0 - sorry, I don't have the RS Stock No. to hand for the longer cable) both have a USB plug (containing the circuit board and indicator LEDs) on one end, which plugs directly into a spare USB port in the PilotAware. The other end of the cable is supplied as 'bare wire ends', so you don't need to 'chop' anything.
You are trying to send traffic data from Pilotaware to your Dynon - so you need to use the 'Data Out' wire in the FTDI - which is the Orange one - and connect this to 'Data In' (or Rx) in the Dynon - the colour of which depends on which Dynon serial port you are using, plus the Black 'Ground' wire from the FTDI to whatever colour your Dynon port uses for Ground - (Edit: from later research, Dynon also use Black for their Common Ground.) I don't recommend cutting back the unused tails in case you need to re-configure your setup later due to future developments - Just be sure to insulate any 'unused' bare ends from each other and from anything else.
You then have to set your chosen PAW USB Port to 'Flarm Out' and set a fairly high Baud rate (115,200 Baud IIRC) in both devices.
Edit: It also apparently works with both units set to 57,600 Baud - thanks Bob (my brain was struggling a bit at 2am :-\)
For the avoidance of doubt, the PAW USB Ports are numbered from the left - 1 then 3 on the 'top' row and 2 then 4 on the 'bottom' row when viewing the unit with the End Cover removed and the 'Ethernet' Port to the left. If you are unsure about this, please ask.
Best Regards
Peter
-
I plan on fixed installation of PAW with serial connection to Dynon SkyView. Thus displaying all traffic on the SkyView map. So theoretically do not need my iPhone, or do I?
Would that also display the wx on the Dynon or do I still need an iPhone/iPad running SkyDemon for that?
Displayed traffic on Skyview is by symbols, and not as informative as the traffic displayed from PAW on say Skydemon.
To get weather, you need Skydemon, so I would say yes, you still need your iPhone or Android device.
Regarding the cabling and setup of the connection between PAW and Skyview, CarlP was the pioneer of this, and his and subsequent posts can be found here.
http://forum.pilotaware.com/index.php/topic,819.msg9849.html#msg9849
-
Thanks Bob,
I was struggling a bit when I posted the above at going on 2am - and freely admit to never having actually wired PAW up to a Dynon - Yet!
I had, however just been reading some back-posts on the Stratux-Europe Forum from a couple of Stratux Users who (after similar struggles) had managed to connect their Stratux devices to their Dynons back in December 2020 (which uses pretty much exactly the same methodology). This was of course well after CarlP had reported achieving his installation from his PAW (Classic) on our Forum back in March 2017.
James - as per CarlP's original post linked to by Bob, you can of course use other USB serial cables such as the one recommended by CarlP. If that's what you are doing, please follow Carl's advice re pinouts or if using the FTDI, you can of course add an appropriate connector.
Please let us know how you get on.
Best Regards
Peter
-
Which serial device do you have?
This should be bare wire not a db9 connection
-
Lee,
Unfortunately James seems to have us chasing each other round the Forum a bit here. He also started another thread, initially to ask for advice on using a mobile dongle in place of his iPhone as his iGRID access point, but went on to ask a similar question about Dynon connectivity on that thread.
Unaware that he had asked a question here, I and others have been trying to help him over there - in my case, like yourself, based on the 'expectation' that he was using our recommended bare-wire ended FTDI lead, but from his subsequent comments, it now seems likely that he is not, but is instead using a serial cable (possibly off eBay, but not necessarily the one recommended by CarlP back in 2017) - with a db9 male connector already on the end.
James,
If you are using a lead with a DB9 male connector, it should be fairly simple to identify and connect the requisite wires from your Dynon into the corresponding pins of a female DB9 connector, but to clarify the position can you please post a photo of the cable or link to where you purchased it from.
Regards
Peter
-
OK James,
I have been doing a bit of reading and research on your behalf. As I now understand it, the situation is as follows...
Assuming you are NOT using the bare-ended FTDI cable and are instead using a USB to RS232 Serial Converter Cable with a male db9 connector already fitted (which I'm pretty sure you are), the PAW Tx (Out) from your USB to RS232 Serial converter cable should be on the Male Pin 3 (TxData) and Ground on Pin 5 of your Male db9 connector - see attached photo of male db9 plug.
From the Dynon Installation Manuals (obtainable online from https://dynonavionics.com/documentation-overview.php), the Dynon Serial Port wires normally come as 'twisted Tx/Rx Pairs' - yellow with orange stripe / yellow with violet stripe for Serial Port 2, green with orange stripe / green with violet stripe for Serial Port 3, and blue with orange stripe / blue with violet stripe for Serial Port 4. (Serial Ports 1 and 5 are for specific uses, so should NOT be used). Note: These twisted pairs each comprise a Transmit Data and a Receive Data wire. We aren't using the Transmit Data wire, but DO need to add a Ground Wire back to the common Dynon Ground (normally solid black wires) to complete the circuit.
This means that you need to obtain a female db9 RS232 socket, then decide which Dynon Serial Port you are going to use - (normally Port 2 or Port 3 - your choice, but take a careful note of which port you decide on - you will need this to configure the port later). Wire the Dynon Rx Data wire from your selected Serial Port - so 'yellow with violet stripe' for Dynon Serial Port 2 or 'green with violet stripe' for Dynon Serial Port 3 - to Pin 3 of your Female db9 socket and add a 'solid black' (Ground) wire from Pin 5 of the Female socket back to the Dynon common ground. - see attached photo of Male/Female db9 sockets.
Once all the connections have been made, you then need to configure your chosen Serial Port in the Serial Port Setup Menu (SETUP MENU > SYSTEM SETUP > SERIAL PORT SETUP) - refer to your Dynon Manual.
According to the Dynon Manual, SkyView serial ports have four parameters that must be defined:
• Input Device
• Input Function
• Baud Rate
• Output Device
Note that sometimes a parameter will be defined as NONE on the screen. For example, when a serial port is configured as only an input device (as in our case), the output device will be set to NONE.
You need to select your chosen Serial Port, then set the SERIAL IN DEVICE to FLARM TRAFFIC, the INPUT FUNCTION to TRAFFIC and the SERIAL IN/OUT BAUD RATE to a minimum 0f 57600 Baud (though 115200 Baud is probably better) and the SERIAL OUT DEVICE to NONE.
You then need to connect to your PilotAware (via the PAW WiFi and 192.168.1.1 / Configure) and set your chosen PAW USB Port to 'Flarm Out' with the same Baud Rate as you have set in your Dynon.
Don't forget to 'SAVE' the new PAW Configuration
After rebooting both units and allowing a sufficient period for PilotAware to establish a GPS fix, you should start to see Traffic Data on your Dynon Screen (providing there is traffic in range / within any set altitude filters.
If in doubt, check the screenshots in the earlier thread here... http://forum.pilotaware.com/index.php/topic,819 ...note that Bob has used Dynon Serial Port 2.
Hope this helps.
Again, please let us know how you get on.
Best Regards
Peter
-
I am in the throes of designing my panel upgrade and would like to connect a Dynon SkyView HDX to my PAW, both to receive traffic into the HDX and receive GPS into the PAW.
Traffic, all understood and well documented. GPS from HDX to PAW, not quite so well documented but there's still a lot of info around. I just wanted to clarify one point, really.
I'll use another USB to serial converter to connect to a separate serial port on the HDX for GPS. So one serial port will have traffic IN from the PAW and another serial port will have GPS position OUT to the PAW. I know on the traffic that the orange Tx wire is used (in addition to a ground) but on the GPS connection do you just have just the yellow Rx wire or do you need Rx and Tx to the GPS (in addition to ground)? I suspect it is only the Rx but I just wanted to check.
Thank you.
-
Like you, I suspect only the Rx and ground connection is used, but I don't see any downside in connecting both the Tx and Rx wires, as if ever the PAW becomes capable of using one USB for both Rx/Tx, you can " save" a USB port for another use.
I considered going firbthe Dyjon GPS input after RussP explained the procedure in the 6th post down of this thread
http://forum.pilotaware.com/index.php/topic,1765.msg23431.html#msg23431
but in the end continued to use the PAW mouse for GPS, as having both the PAW GPS and the Dynon GPS into separate devices gave me a level of redundancy I was happier with.
-
Hi Bob,
I definitely read Russ's post before I posted (and sent him a PM, but no joy). I understand that I need two FTDI USB to serial connectors (one for traffic from PAW to HDX and one for GPS from HDX to PAW). But he does say he wired it in the 'exact same way' as traffic, to get GPS from HDX to PAW. That doesn't make sense to me as the orange wire transmits RS232 (from PAW to HDX) but we're receiving GPS into the PAW and, therefore, I would have thought you'd need the yellow 'receive' wire.
My reason for asking about both for GPS is sometimes these things 'handshake' to make sure components are present and, for that reason, I thought you might need Tx and Rx. As you say, there's probably no harm in connecting both......unless someone can say otherwise.
-
Hi again Paul / Bob,
If you are using two FTDI USB to RS232 adaptors (which unless I haven't been told of changes you still need to do - i.e. separate ones for data in and data out - as the PAW ports still can't be configured to do both at the same time), then the 'Data Out one needs to use the FTDI Orange and Black wires, and the Data In (whether Flarm or GPS) needs to use the FDTI Yellow and Black wires.
I am not aware of any specific technical problem arising from both 'Data In' and 'Data Out' wiring being connected at the same time, on the same cable, though I have never actually done this myself in any of the installations (mainly Flarm In or Data Out to various Transponders) I have done personally - mainly because of the fact that AFAIK it doesn't achieve anything worthwhile, other than potentially 'future-proofing the installation as you say Bob!
Best Regards
Peter
-
Thank you, Peter. It's good to know that I don't HAVE to connect the orange wire for the GPS from the SkyView but it shouldn't do any harm if I do. :)
-
It took me a while to get PAW and SV talking nicely to one another but worthwhile. One thing though, despite setting 'Show Tail Numbers' to 'Yes' on SV, I never see any (only traffic symbol/relative height/direction) although they show fine on iPad running SkyDemon. Is this same for everyone, or just me?
-
Thanks everyone, apologies if I messed anyone about by posting twice. I was getting really confused as I had followed the original advice and bought the cable with the D9 connector attached. I have however today managed to get to aircraft and followed all the advice given and it's still not working so now wondering if I have a 'fake' cable. Just ordered the version with bare ends from RS. When that arrives I will connect the Orange cable straight to the Yellow/Violet Dynon RX Serial Port 2, and the black onto a spare Dynon D37 Black. The USB end of the cable will go into the lower middle USB (port 2) on PAW.
Then configure as advised setting PAW Port 2 to 'Flarm Out' and set initially 115,200 Baud IIRC), dropping to 57600 if I can't see anything. I will configure Skydemon as SERIAL IN DEVICE to FLARM TRAFFIC, the INPUT FUNCTION to TRAFFIC and the SERIAL IN/OUT BAUD RATE to a minimum 0f 115,200 Baud ( and the SERIAL OUT DEVICE to NONE.
I think this is what you have all now advised,
Cheers
James
-
Hi James,
I think you mean configure SkyView as... in the bottom paragraph. Oh, and remember you need to configure Dynon Serial Port 2 if that is the wiring set you use.
Other than that all looks fine.
Please keep us posted.
Best Regards
Peter
-
Is anyone (else) having issues with Skyview when iGrid is connected? Seem to work great with no iGrid .. with iGrid connected Shyview is continually telling me Flarm is disconnected .. then ok.. then disconnected.. and on and on. I've replaced every cable and the Raspberry Pi - it now has to be a software problem ..
-
Well it never worked. Done exactly as I stated, and as it was confirmed to be correct.
Now defo have the right authentic 'USB to bare wire'cable direct from RS.
Still Nada. Just noticed another post saying similar with the iGrid wifi installed. I have that in as well. Going to take that out tomorrow and try again.
Cheers
Thanks everyone, apologies if I messed anyone about by posting twice. I was getting really confused as I had followed the original advice and bought the cable with the D9 connector attached. I have however today managed to get to aircraft and followed all the advice given and it's still not working so now wondering if I have a 'fake' cable. Just ordered the version with bare ends from RS. When that arrives I will connect the Orange cable straight to the Yellow/Violet Dynon RX Serial Port 2, and the black onto a spare Dynon D37 Black. The USB end of the cable will go into the lower middle USB (port 2) on PAW.
Then configure as advised setting PAW Port 2 to 'Flarm Out' and set initially 115,200 Baud IIRC), dropping to 57600 if I can't see anything. I will configure Skydemon as SERIAL IN DEVICE to FLARM TRAFFIC, the INPUT FUNCTION to TRAFFIC and the SERIAL IN/OUT BAUD RATE to a minimum 0f 115,200 Baud ( and the SERIAL OUT DEVICE to NONE.
I think this is what you have all now advised,
Cheers
James
-
Without wishing to sound patronising, have you enabled traffic in the set up menu?
My iGrid works perfectly and traffic shows on my HDX map and PFD.
Also, please confirm you do not have a SkyView SE. These cannot display traffic.
The USB end of the cable will go into the lower middle USB (port 2) on PAW.
. 'Lower middle'? Just checking that you mean lower, left of the USB ports:
Ethernet Port USB 1 USB 3
Ethernet Port USB 2 USB 4
-
Woo Hoo It Works!
Didnt make any physical changes, update Sktview HDX to the new firmware, updated PAW to the latest. Then turned the igrid PAW port to automatic. Once everything rebooted PAW came alive. So I cannot say which of teh above did teh trick. All my formware is regularly updated, so its not like I was on archaic versions.
Dont care - it works. Thanks all for trying to help over these painful months.
-
Hi James,
Great to hear you have finally managed to get PAW and your Dynon talking to each other!
It would of course be good to know which of the reported updates actually made the difference, though I have my suspicions.
I assume by 'Then turned the igrid PAW port to automatic' you are talking about the USB Port that your iGRID dongle is plugged into? That inevitably begs the question - what was it set to before - AND WHY? My guess is that's what was causing the iGRID to malfunction, which might also explain what was going wrong elsewhere (or at least in part).
The important thing, however, is that it is now working !!! :D :)
Best Regards
Peter
-
The iGrid was set at 57600. My bad as instructions clearly say Auto. I think it was becasue I had changed the PAW onto that port at some time during my battle. Amazing how something so simple can be the cause of so much pain. I was spending all time concentrating on the main PAW setup, not considering the iGRID.