PilotAware
British Forum => Technical Support => Topic started by: Gary Nelson on August 08, 2022, 12:22:31 pm
-
I just received a new Wifi dongle from PAW. However the expected new lower part of the Network page is not showing. NB: I was very careful to insert the dongle fully into the only remaing free USB port on my Rosetta (one of the 4 is used to input a Flarm mouse). I attach the following screenshots and any help would be appreciated:
1. Network Page - showing the lack of the expected new "hotspot" part of this screen at the bottom
2. Interface screen - showing PAW version 20220805
3. Configure Page.
-
Hi Gary
I see ports 2 and 4 are configured for Trig and FLM
can you post a picture of the dongles plugged into the unit I am sure you have it correct, but lets start there.
Also as a test could you unplug the Trig and FLM, and set them back to Auto
remember to record your settings so you can revert correctly after the test
thx
Lee
-
See 2 x photo of the USB part (normal and close up). The Rosetta is normally velcroed but I peeled it off its mounting to access it to fit the dongle
-
Hi Gary,
Your WiFi dongle is in the bottom right USB port, which is Port 4, so that needs to be reconfigured to ‘Auto’ not ‘GPS’ and the change saved.
Port 1 is your GPS, but it will run fine with that port set to ‘Auto’.
Best Regards
Peter
-
Thanks Peter and will do that
I would like to correctly label on the configure page what each USB port is being used for. I can see from another post that the numbering is 1 top left 2 bottom left 3 top right 4 bottom right? So 4 is the Dongle which I will change to Auto. That leaves one being Flarm and one being GPS and I cant remember what the last one is for. Any idea from the photo. Also any idea from the photo which is which. I can't remember and would have to open the access hatch to find out but there are 50 or so small bolt screws to unscrew ???
-
I think the other is your Pilotaware Wi-Fi!
-
I'd go with
1 GPS - 2 SDR
3 FLARM - 4 Wifi
-
Hi again Gary,
Post edited for clarification and after finding a mistake re my understanding of the reason for the FTDI lead in Port 2 - See Reply #13
Sean - nearly correct, but the ports are numbered 1 & 3 on the top then 2 & 4 on the lower row (so numbered 'vertically' starting from from the top of the left hand column next to where the Ethernet Port is).
Gary - You don't 'Label' the ports on the Configure Screen. You 'select' appropriate settings to enable the transfer of specific data for a specific task - such as the one you have which is set to 'Transponder Funke'. This setting ensures that the correct data is transferred via the port at the correct speed (Baud rate) for your Funke Transponder. If it was a Trig Transponder, this port would instead be set to 'Transponder Trig' at 9600 Baud, or if the lead was being used to integrate Flarm from a Flarm device into the PilotAware - it would need to be set to 'Flarm-In' - each with their appropriate 'Baud Rate'. The other ports should simply be left as 'Auto' unless they need to be configured for a specific task -
For the avoidance of doubt, from your photos...
Top Left is Port 1 - which is your remote Mouse GPS.
Bottom Left is Port 2 - which is the FTDI RS232 Serial to USB converter for directly integrating Flarm data to PilotAware from your FlarmMouse.
Top Right is Port 3 - which is the 1090 Receive SDR
Bottom Right is Port 4 - which is your new WiFi Dongle.
All ports which don't specifically need particular settings should be left / set to 'Auto'. In your case this means all ports except Port 2, which should be reset to Flarm-In.
Best Regards
Peter
-
From the manual, port identification
https://www.pilotaware.com/knowledgebase/configuration
Also Gary you say this
one of the 4 is used to input a Flarm mouse
Do you really have a flarm mouse, or a gps mouse ?
Thx
Lee
-
Hi Lee,
From memory I recalled previous confusion about a 'Flarm Mouse', so checked back Gary's previous posts just to be sure. As I suspected, Gary has a GPS Mouse (in place of the standard Rosetta GPS - as the Rosetta is mounted in the 'preferred' Eurostar position - inside the aircraft bodywork between the dash and engine firewall) and a Funke Transponder (hence the FTDI converter). We established in the earlier thread (back in January) that there is NO Flarm Mouse installed in Gary's plane, just the equipment I have listed above, so presumably resetting Port 4 to Auto and 4800 Baud should allow the WiFi dongle to be recognised.
Regards
Peter
-
Thanks for advice to date:
As per attached screenshot of the PAW Configure page, I have now changed the USB port labels so Ports 1, 3, 4 are set to Auto and Port 2 is set to the Funke transponder. However, this has not cured the problem. I still cant see the lower part of the Network Screen to input the hotspot password from my phone. :-\
NB: As per second attachment, a photo of the sill above my instruments, you will see, as I have labelled on this photo, that I do in fact have (1) a FLARM mouse (2) a PAW GPS and (3) a Karnardia Horis 57 GPS. I believe it is this Horis GPS that the Funke is connected to for position data and so I guess Port 2 is ?? :-\
-
Hi Gary
did you try my experiment of the following ?
(remembering to save your current settings)
only plug in the following
- SDR
- GPS
- WiFi dongle
configure all to Auto/4800
Reboot
What does the display show
If this fails - it sounds like a fault
thx
Lee
-
Lee I will try your experiment when next at airfield and report back. It means I have to again unscrew 50 odd small bolts to take off the access panel on my Eurostar and then all have to be screwed back on (I only did it last week to fit the new dongle) :(
-
Hi Gary,
Sorry, I have to eat Humble Pie and apologise profusely - Having spent a full day re-reading all of your many previous posts and threads, I now realise I got things completely confused re your Flarm Mouse and Funke Transponder connections, so have adjusted my posts above accordingly.
For the avoidance of doubt, the correct response to your photos should have been: -
Port 1 (Top Left) is your remote Pilotaware GPS Mouse (Settings should be - Auto and 4,800 Baud)
Port 2 (Bottom Left) is the FTDI USB to RS232 Serial Converter - which in your case is being used 'in reverse' to connect your FlarmMouse to your Rosetta to allow direct integration of directly received Flarm data from the FlarmMouse into Pilotaware. This port should therefore (of course) be set to 'Flarm-IN' and '19,200 Baud'
Port 3 (Top Right) is the 1090 Receive SDR (Settings again - Auto and 4,800 Baud)
Port 4 (Bottom Right) is your new iGRID WiFi Connectivity Module (Settings again - Auto and 4,800 Baud)
If you want to avoid removing all the screws (yet again) to get to the Rosetta, you could try resetting the USB ports to the above settings, then 'SAVE' the settings, reboot the PilotAware and see whether the WiFi Connectivity Module comes on line. If not, then you need to try Lee's setup (i.e. unplug the FTDI connection and set all 4 ports (temporarily) to 'Auto' and 4,800 Baud).
Again, my apologies for any confusion caused.
Best Regards
Peter
-
Hi Gary
If I recall correctly, you should not require a gps mouse, the flarm mouse will provide gps messages
Thx
Lee
-
Lee,
You are of course correct - Gary’s FlarmMouse will supply GPS messages if the external GPS mouse is disconnected, but when we did the initial Flarm Integration trials, I recall that we found that using the FlarmMouse GPS data for PilotAware proved extremely unreliable - not least because the FlarmMouse GPS antenna is much smaller than either of the PilotAware ones in use at the time (uBlox6 mouse or uBlox7 dongle). We were sufficiently concerned that we (you) communicated with LXNav about this at the time, but although they accepted our evidence they were pretty non-commital about discussing the matter further, so we resolved to recommend the use of a dedicated PilotAware GPS on the basis that if/when connected, PilotAware would always prioritise this over any other GPS source..
From that point, I myself continued to run my PilotAware with a GPS mouse during FlarmMouse Integration and would have openly suggested that to others in similar situations, so wasn’t surprised to find Gary doing the same.
Hope this helps.
Best Regards
Peter
-
Hi Peter
Your memory serves you well !
Having 2 gps is not a problem, if for instance one loses a lock, messages from the other will continue to be used
Thx
Lee
-
It is now working and thanks for all the advice. If of interest, what I did was as follows:
As Peter correctly "corrected" with his last message, my USB connectors were indeed as follows:
(1) PAW GPS (3) 1090
(2) Flarm (4) iGrid Wifi (not working)
As Lee suggested, I totally unplugged the Flarm Mouse, which was in position (2) and using the opportunity to make sure the iGrid wifi dongle was firmly in place in position (4). However, this didn't make any difference and I still could not get the Network page to display the new bottom half-screen with my phone hotspot.
I then swapped things around and moved the iGrid Wifi dongle from postion (4) to position (1) and noticed a small purple LED light on the dongle, which I had not seen before but perhaps as it was rather hidden when it was at bottom right position (4). I then put the Flarm feed into position (4) as the USB input for the Flarm has an LED that goes on and off as data feeds and so a good one to see if position (4) appears working. That left the PAW GPS so I put that into remaining position (2). Amazingly now the USB's are being so used (also as below), the hospot functionality is displaying on the Network screen. Very very mysterious ??
(1) iGrid Wifi (3) 1090
(2) PAW GPS (4) Flarm
PS I have to check Flarm is still working in it's new USB position (4). I will do a few flights and then use the Pilot Aware VECTOR app to test this.
-
Hi Gary
Glad to hear its working, but still a bit odd right ?
It shouldn’t matter which port the wifi dongle is used
Nonetheless, lets see how you get on
Thx
Lee
-
Hi Gary,
Definitely weird! The only thing I can think of is that in the Port 4 position, the WiFi dongle was somehow getting blocked by one or more of the other devices, or something close by in the compartment. Glad to hear you have got things working now. please let us know how it goes.
Best Regards
Peter
-
As part of testing, on the Configure page (as per first screenshot below) I set Bearingless Contacts to long range and vertical +/- 50,0000 feet and I set Postional Contacts to display all for horizontal and vertical. I then saw lots of traffic on my Traffic Page (also below). However, none of this traffic shows on the Radar page, even with the (as also below) Radar page set to 97km H and 50,000 V
Any ideas why the Radar screen should be blank?
-
Hi Gary,
Simple - you need to select 'TFC' (Traffic) from the list of options in blue at Top Left on the RADAR Screen by 'ticking' (clicking or touching in) the relevant blank box...
The Radar Screen will then display the traffic or whatever item(s) you have selected. (You can tick any or all of them, but if you select all your screen may get a bit crowded).
For info, the other setting options are... MET = METARs , RAIN = Rainfall Radar , POI = Places of Interest , and AIRFIELD is self evident.
Once selected, you can hide or display the Options List by toggling using the HIDE /DISP (Display) buttons to keep the screen clear.
Once selected and on display, you can then touch on an individual aircraft (or METAR) to bring up a window containing details of that aircraft or site METAR. Touching the screen again away from the detail window closes it again.
p.s. For the benefit of other users, I have adjusted the Main Thread Title to indicate that this issue has now been resolved, though users can of course still continue to post observations..
Best Regards
Peter