PilotAware
British Forum => General Discussion => Topic started by: Wadoadi on May 11, 2017, 11:01:42 am
-
Hi All,
I have been having trouble with my ubox GPS for sometime, I even spoke to someone from Pilotaware at the Flying Show last year as it has always been very slow to get a fix even outside and indoors it would seldom work, I was told by the PAW team member that it would not work indoors. Now it has also let me down twice in flight, requiring a reboot to get it back, which is less then ideal.
So having always had a good experience with Globalsat GPSs in the past I ordered a ND-105C it connects via a micro USB port but comes with an adaptor.
Trying it on my PC indoors it got a fix first time and straight out of the packet in around 5 seconds.
It doesn't auto detect when plugged into PaW however i manually set the port and it came up with a fix in around 2 seconds. Great time for a flight test!
the location was working great however the altitude seems around 800ft off comparing it with the inbuilt GPS on both the iPad (Cellular) and iPhones inbuilt GPS which both were close to the altimeter.
Any ideas?
-
Sounds very strange, I have found the ublox receivers to be very good, but there could be a fault here.
Is this a PilotAware Classic ?
Which GPS, is this - the Dongle or Mouse ?
and finally, which software release are you using (reported on home page) ?
There was an issue in an earlier software version which was erroneously reporting there was no satellite fix, when in fact there was - if you have not updated this could be the case.
If this is a Classic, we would be happy to provide an alternate GPS to see if this is the source of the problem.
So having always had a good experience with Globalsat GPSs in the past I ordered a ND-105C it connects via a micro USB port but comes with an adaptor.
...
the location was working great however the altitude seems around 800ft off comparing it with the inbuilt GPS on both the iPad (Cellular) and iPhones inbuilt GPS which both were close to the altimeter.
This would be very concerning, because of course the relative altitude when reporting surrounding traffic using a GPS reference would be way off.
Also its strange that the GPS was close to the Altimeter, but depends totally on the Pressure setting you selected, and the pressure on that particular day
Thx
Lee
-
That's odd, that GPS is supposed to be WAAS/EGNOS capable. Maybe leave it outside with a good clear view towards the south for a while to allow it to get the EGNOS satellite and maybe calibrate itself.
Lee - the altimeter will have been set to the pressure setting, so the GPS and pressure altitudes should be similar. It's showing altitude, not flight level. The calibration/compensation will be done by twiddling the altimeter knob. Using my PAW GPS tends to get me within about 20ft of what my altimeter reads.
-
Lee - the altimeter will have been set to the pressure setting, so the GPS and pressure altitudes should be similar. It's showing altitude, not flight level. The calibration/compensation will be done by twiddling the altimeter knob. Using my PAW GPS tends to get me within about 20ft of what my altimeter reads.
Duuuurrrh
re-engage brain - yes, this is what happens when you spend so much time thinking about comparing Pressure Altitude at 1013.25mb versus GPS Altitude !
Thx
Lee
-
Thanks Lee and Paul,
this the USB UBox VK172 not the usb mouse. no not part of a classic kit, I was one of the originals using the wireless thing and then traded it in for the PaW bridge board...
I do also have the USB Ubox mouse which is better but still not as quick as the GlobalSat and doesn't get a fix indoors...
The height did improve over the duration of the flight but I can't remember where it ended up.
PaW version is 20170223
extract from the GlobalSat taken from indoors with the gps connected to my laptop not Paw.
$GPGSV,4,3,15,30,13,312,15,01,11,248,,07,10,276,26,15,09,029,13*75
$GPGSV,4,4,15,28,04,329,,32,02,127,,26,01,169,*47
$GPRMC,194152.000,A,5244.4711,N,00033.0033,E,0.23,354.70,110517,,,A*67
$GPGGA,194153.000,5244.4711,N,00033.0033,E,1,8,1.47,4.3,M,47.0,M,,*5D
$GPGSA,A,3,08,11,07,27,21,18,10,15,,,,,1.70,1.47,0.85*0E
$GPGSV,4,1,15,27,72,125,19,08,67,291,30,10,57,104,36,18,41,064,27*7E
$GPGSV,4,2,15,11,25,266,20,16,25,179,,36,23,142,,21,15,072,27*77
$GPGSV,4,3,15,30,13,311,15,01,11,248,,07,10,276,26,15,09,029,13*76
$GPGSV,4,4,15,28,04,329,,32,02,127,,26,01,169,*47
$GPRMC,194153.000,A,5244.4711,N,00033.0033,E,0.16,354.70,110517,,,A*60
$GPGGA,194154.000,5244.4710,N,00033.0032,E,1,8,1.47,4.3,M,47.0,M,,*5A
$GPGSA,A,3,08,11,07,27,21,18,10,15,,,,,1.70,1.47,0.85*0E
$GPGSV,4,1,15,27,72,125,19,08,67,291,30,10,57,104,36,18,41,064,27*7E
$GPGSV,4,2,15,11,25,266,21,16,25,179,,36,23,142,,21,15,072,27*76
$GPGSV,4,3,15,30,13,311,15,01,11,248,,07,10,276,26,15,09,029,13*76
$GPGSV,4,4,15,28,04,329,,32,02,127,,26,01,169,*47
$GPRMC,194154.000,A,5244.4710,N,00033.0032,E,0.14,354.70,110517,,,A*65
$GPGGA,194155.000,5244.4710,N,00033.0032,E,1,8,1.47,4.3,M,47.0,M,,*5B
$GPGSA,A,3,08,11,07,27,21,18,10,15,,,,,1.70,1.47,0.85*0E
-
Made the same trace from my PC with the uBlox it seems to have corruption every so often, or is this normal for uBlox?!
$GPZDA,205744.00,11,05,2017,00,00*67
$GPGBS,205744.00,4.9,5.5,17.8,,,,*72
µb0¼ ¨/
!* #
H« :üÿÿ
): âÿÿÿÿ :
2 »
Î ÿÿÿ $ 99êÿÿ
h ‚ x È | š
~ – Á ¥ Ä ¥ Å ¥ 7صb ¨/Ý Ü tË ;ê$GPRMC,205745.00,A,5244.47159,N,00033.00500,E,0.137,,110517,,,A*7B
$GPVTG,,T,,M,0.137,N,0.253,K,A*22
$GPGNS,205745.00,5244.47159,N,00033.00500,E,AN,06,1.37,13.5,45.8,,*49
$GPGGA,205745.00,5244.47159,N,00033.00500,E,1,06,1.37,13.5,M,45.8,M,,*6C
$GPGSA,A,3,01,10,32,22,18,08,,,,,,,2.55,1.37,2.15*03
$GPGSV,3,1,09,01,42,267,33,08,72,171,20,10,41,058,20,11,58,278,*75
$GPGSV,3,2,09,18,15,050,27,22,31,206,31,27,36,141,08,28,28,313,11*75
$GPGSV,3,3,09,32,27,104,20*43
$GPGLL,5244.47159,N,00033.00500,E,205745.00,A,A*64
$GPGRS,205745.00,1,0.3,-0.3,1.3,-1.3,1.9,-9.7,,,,,,*64
$GPGST,205745.00,42,,,,4.9,5.6,18*79
$GPZDA,205745.00,11,05,2017,00,00*66
$GPGBS,205745.00,4.9,5.6,18.0,,,,*77
µb0¼ 3
!* ;
H« Žûÿÿ
): eÿÿÿ :
2 ‹
Î nÿÿÿ
$ Âõÿÿ 9?ñÿÿ
h wÿÿÿx È | š
~ – Á ¥ Ä ¥ Å ¥ –µb 3Ý Ü \Ï R$GPRMC,205746.00,A,5244.47167,N,00033.00492,E,0.168,,110517,,,A*75
$GPVTG,,T,,M,0.168,N,0.310,K,A*2E
$GPGNS,205746.00,5244.47167,N,00033.00492,E,AN,07,1.18,13.4,45.8,,*40
looks like it could be uBlox binary protocol is on, how do i turn it off?
-
@Lee does the out from Ublox look correct or is there a way to turn off the binary message assuming that is what it is?
interestingly when plugged into the PC and using the Ublox software it gets a fix inside my house and very quickly which is greatly different from when its pluged into my PaW!
Also do the messages from the ND-105C look ok?
thanks
-
@Lee does the out from Ublox look correct or is there a way to turn off the binary message assuming that is what it is?
I'm sorry I have no idea, you could try the uBlox tech support.
interestingly when plugged into the PC and using the Ublox software it gets a fix inside my house and very quickly which is greatly different from when its pluged into my PaW!
That does not make sense.
How do you determine 'fix' ?
do you mean 2D/3D and how many satellites ?
I cannot see how this is any different to the data it provides to PilotAware - the NMEA messages are the same.
Also do the messages from the ND-105C look ok?
I think that is covering all the required messages - difficult to know if the content is OK
I would need to get out the NMEA spec and decode.
Thx
Lee
-
That binary data is the U-Blox AssistNow Aiding Messages packets, they start 0xB5 which is the ASCII "µ" you see in the data. So you need to look at the commands to disable that feature in the module. You might be able to turn it off in the UBlox config tool and save it to the flash in the GPS module.
-
Further to my last post, it looks like they enable the dumping of almanac data every so often so their app can display the various sat positions etc. I doubt this can be disabled I'm afraid.
-
Thanks Lee and Jeremy,
Lee the fix is indicated in the UBlox software and says 3D, as attached. I think this was about 40 - 60 secs after I plugin it in to the laptop in the center of my home and where it doesn't get a fix when plugged into the Pi.
Thank you Jeremy for your input too, I assume this is therefore the the same for all and thus nothing to do with the poor reception of the GPS.
May be it is interference from the Pi!?
-
Can you try an experiment on your pc ?
Rather than connecting using the ublox utility, try connecting using putty
Settings are
9600 baud
8 bits
1 stop bit
No parity
Would be interested in what you see
Thx
Lee
-
sure no problem...
taken from Putty at 9600,8,1,N
$GPVTG,,T,,M,0.138,N,0.255,K,A*2B
$GPGNS,210018.00,5244.47035,N,00033.00790,E,AN,09,1.07,27.8,45.8,,*44
$GPGGA,210018.00,5244.47035,N,00033.00790,E,1,09,1.07,27.8,M,45.8,M,,*61
$GPGSA,A,3,11,08,10,22,01,27,18,28,32,,,,2.63,1.07,2.40*0A
$GPGSV,3,1,12,01,50,272,27,03,12,215,,08,63,165,26,10,33,055,25*75
$GPGSV,3,2,12,11,66,277,14,14,24,118,25,18,08,050,14,22,39,208,34*76
$GPGSV,3,3,12,24,01,026,,27,28,144,28,28,31,305,22,32,32,096,30*7F
$GPGLL,5244.47035,N,00033.00790,E,210018.00,A,A*6F
$GPGRS,210018.00,1,8.3,-5.2,-0.9,-0.1,3.7,-4.5,39.5,-1.8,4.6,,,*72
$GPGST,210018.00,44,,,,5.1,4.4,19*7F
$GPZDA,210018.00,15,05,2017,00,00*69
$GPGBS,210018.00,5.1,4.4,19.5,,,,*72
▒b0}▒
\
?▒▒▒▒▒
!7K▒▒▒
B
v
`▒x▒▒
▒▒▒▒▒▒▒▒}▒ ▒!*-7▒▒$GPRMC,210019.00,A,5244.47031,N,00033.00795,E,0.209,,150517,,,A*7A
$GPVTG,,T,,M,0.209,N,0.387,K,A*24
$GPGNS,210019.00,5244.47031,N,00033.00795,E,AN,09,1.07,28.0,45.8,,*43
$GPGGA,210019.00,5244.47031,N,00033.00795,E,1,09,1.07,28.0,M,45.8,M,,*66
$GPGSA,A,3,11,08,10,22,01,27,18,28,32,,,,2.63,1.07,2.40*0A
$GPGSV,3,1,12,01,50,272,27,03,12,215,,08,63,165,25,10,33,055,25*76
$GPGSV,3,2,12,11,66,277,12,14,24,118,24,18,08,050,14,22,39,208,35*70
$GPGSV,3,3,12,24,01,026,,27,28,144,28,28,31,305,21,32,32,096,30*7C
$GPGLL,5244.47031,N,00033.00795,E,210019.00,A,A*6F
$GPGRS,210019.00,1,10.5,-5.9,-1.8,0.3,0.9,-4.5,38.5,-1.9,4.8,,,*6B
$GPGST,210019.00,48,,,,5.1,4.4,19*72
$GPZDA,210019.00,15,05,2017,00,00*68
$GPGBS,210019.00,5.1,4.4,19.4,,,,*72
▒b0▒▒
-
?▒▒▒
!7▒▒▒▒
B▒
v
`▒x▒▒
▒▒▒▒▒▒E▒b▒ ▒!17▒#$GPRMC,210020.00,A,5244.47028,N,00033.00799,E,0.222,,150517,,,A*7D
$GPVTG,,T,,M,0.222,N,0.411,K,A*25
$GPGNS,210020.00,5244.47028,N,00033.00799,E,AN,09,1.07,28.1,45.8,,*4C
$GPGGA,210020.00,5244.47028,N,00033.00799,E,1,09,1.07,28.1,M,45.8,M,,*69
$GPGSA,A,3,11,08,10,22,01,27,18,28,32,,,,2.63,1.07,2.40*0A
$GPGSV,3,1,12,01,50,272,27,03,12,215,,08,63,165,25,10,33,055,25*76
$GPGSV,3,2,12,11,66,277,10,14,24,118,24,18,08,050,13,22,39,208,35*75
$GPGSV,3,3,12,24,01,026,,27,28,144,28,28,31,305,21,32,32,096,29*74
$GPGLL,5244.47028,N,00033.00799,E,210020.00,A,A*61
$GPGRS,210020.00,1,4.5,-3.9,-1.0,0.0,0.5,-0.6,40.4,-1.5,6.6,,,*5C
-
Well there is defiantly some binary data in there, but without a hex dump it's hard to pick out the actual data being sent. It can be ignored though.
Note the dongles whilst they say UBlox are very probably clones, the one I was supplied defiantly is, they also have a small cell battery in them to maintain almanac data for faster acquisition, I don't think its rechargeable, and if that gets low it will be doing a full cold start each time. Depends on the quality of the cell when it was put together. If I get time I'll open mine up again and see what's what.
-
There is a problem in the setup there for sure.
The dongles we have do not generate the binary data, no idea what is happening there, but would upset the NMEA parser in Pilotaware
In fact if you look at tge logging page, I would guess there would be sone error messages
I think you have identified your issue
Thx
Lee
-
Worth a try, with it connected up via PuTTY to the PC can you enter the following command, need to ensure PuTTY is setup to send CR/LF at the end. Best to cut and paste the line in rather than type then hit enter at the end.
$PUBX,41,1,0003,0001,9600,0,*3A
Now, in theory this will disable the UBX protocol being sent from the unit. If it doesn't work, try the two below, that set different ports with the same config.
$PUBX,41,0,0003,0001,9600,0,*3B
$PUBX,41,3,0003,0001,9600,0,*38
Does it make any difference?
-
Hi Jeremy, thanks for the codes, the first 2 seemed to make no difference the third one changed it all to binary (my assumption that it is binary), however it did not save the setting as unplugging it returned it to the original behavior.
I will ask on the Ublox forum and report back.
-
Ah, I think the mask must be inverted then, try this one...
$PUBX,41,3,0003,0002,9600,0,*38*1A
-
thanks again...
this appears to have changed the issue!
$GPGBS,104149.00,11.4,7.7,14.3,,,,*4A
▒b0▒▒▒
b
Z
▒▒▒
*▒▒▒▒
4C▒▒▒x▒
|
▒▒▒▒▒▒▒4p▒b▒▒
▒E=▒▒L$GPRMC,104150.00,A,5244.47655,N,00033.00813,E,0.724,,160517,,,A*7C
-
Playing now in the Ulbox application i have the Hex of the messages I don't want to see.
10:49:28 0000 B5 62 01 30 C8 00 F8 9C 9F 0C 10 03 00 00 09 06 µb.0È.ø.........
0010 0D 04 1C 08 57 00 CA 01 00 00 07 0A 0D 04 14 0E ....W.Ê.........
0020 0A 01 64 FD FF FF 00 0C 0D 07 20 52 DC 00 D7 FF ..dýÿÿ.... RÜ.×ÿ
0030 FF FF 0D 0E 04 01 00 10 3E 01 00 00 00 00 06 0F ÿÿ......>.......
0040 0D 04 13 13 AF 00 68 00 00 00 05 11 0D 04 18 15 ....¯.h.........
0050 28 00 E8 FE FF FF 0A 12 0C 01 00 05 F3 00 00 00 (.èþÿÿ......ó...
0060 00 00 02 13 0D 04 19 24 3A 00 89 FC FF FF 01 18 .......$:..üÿÿ..
0070 0D 04 1E 47 76 00 B5 FF FF FF 08 19 0D 04 17 23 ...Gv.µÿÿÿ.....#
0080 F0 00 23 02 00 00 03 20 0D 04 18 22 32 01 B2 01 ð.#.... ..."2.².
0090 00 00 04 78 10 01 00 1C C8 00 00 00 00 00 0B 7C ...x....È......|
00A0 10 01 00 1B 9A 00 00 00 00 00 0C 7E 10 01 00 1A ...........~....
00B0 96 00 00 00 00 00 0E C4 10 01 00 A5 00 00 00 00 .......Ä...¥....
00C0 00 00 0F C5 10 01 00 A5 00 00 00 00 00 00 BB 7D ...Å...¥......»}.
10:49:28 0000 B5 62 01 03 10 00 F8 9C 9F 0C 03 DD 00 00 5D 10 µb....ø....Ý..].
0010 00 00 19 33 03 00 EF 5D ...3..ï].
-
OK, how about...
$PUBX,41,3,0002,0002,9600,0,*38*1B
Basically this command sets the protocols and baud rate, sent in NEMA format. If you have the UBLOX control app then you should be able to turn it off in that too.
The reference for this is
https://www.u-blox.com/sites/default/files/products/documents/u-blox6_ReceiverDescrProtSpec_%28GPS.G6-SW-10018%29_Public.pdf?utm_source=en%2Fimages%2Fdownloads%2FProduct_Docs%2Fu-blox6_ReceiverDescriptionProtocolSpec_%28GPS.G6-SW-10018%29.pdf
So you should be able to generate commands, just need to calculate the checksum for the command you are sending, as it will be different on every command.
That binary data is GPS info in binary form.
-
OK, digging out my GPS dev kit I can turn these binary messages off, but only by sending a UBX binary command to do it. It's the UBX-CFG-PRT command.
It is just how to send it...
B5 62 06 00 14 00 03 00 00 00 00 00 00 00 00 00 00 00 03 00 02 00 00 00 00 00 22 A8
...then that should do the trick!
Does PuTTY support sending hex data?
*edited hex to leave UBX commands to unit working*
-
If not you can use realterm
I would have thought that in the ublox tool, you could configure the dongle to not provide binary.
Thx
Lee
-
If not you can use realterm
I would have thought that in the ublox tool, you could configure the dongle to not provide binary.
Thx
Lee
Yes, will the full uCentre you can set a config and in theory write that back to flash in the device, but it's handy to know the hex codes should it ever need to be incorporated into any kind of setup/init string in the future.....
-
I think more interesting, how did this mode get enabled in the first place ?
I am pretty sure the device does not ship with this mode enabled, otherwise we would have seen this issue many times before
Thx
Lee
-
well send the hex didn't work or it did not send!
turning off the PUBX & UBX stops it switching to Putty confirmed this, however unplugging the GPS and re connecting it and it is back to the original issue.
Lee, I 'm not 100% sure that this is the issue, if i plug the Ublox into the PaW it gets a gps fix showing on the home screen
As can be seen from PaW log below.
The issue was why it was dropping the fix in flight and why it doesn't get a fix in the house when connected to the Pi but does when in does when plugged in to a PC? I'm thinking it may be EMF from the PI?
Log from Pi
(15:40:28) GPS-NMEA : GPS-USB: $GPGSV,3,2,12,21,53,164,22,23,09,304,18,25,16,123,22,26,69,287,39*77
(15:40:28) GPS-NMEA : GPS-USB: $GPGSV,3,1,12,05,16,047,29,09,07,335,,16,39,297,30,20,20,096,32*75
(15:40:28) GPS-NMEA : GPS-USB: $GPGSA,A,3,26,21,29,31,16,20,25,05,23,,,,1.68,0.93,1.40*0A
(15:40:28) GPS-NMEA : GPS-USB: $GPGGA,154030.00,5244.47620,N,00033.00795,E,1,09,0.93,12.8,M,45.8,M,,*65
(15:40:28) GPS-NMEA : GPS-USB: $GPVTG,,T,,M,0.060,N,0.111,K,A*24
(15:40:28) GPS-NMEA : GPS-USB: $GPRMC,154030.00,A,5244.47620,N,00033.00795,E,0.060,,160517,,,A*7A
(15:40:27) GPS-NMEA : GPS-USB: $GPGLL,5244.47619,N,00033.00784,E,154029.00,A,A*63
(15:40:27) GPS-NMEA : GPS-USB: $GPGSV,3,3,12,27,11,253,,29,46,068,34,31,38,204,28,39,26,150,30*77
(15:40:27) GPS-NMEA : GPS-USB: $GPGSV,3,2,12,21,53,164,22,23,09,304,18,25,16,123,22,26,69,287,39*77
(15:40:27) GPS-NMEA : GPS-USB: $GPGSV,3,1,12,05,16,047,28,09,07,335,,16,39,297,29,20,20,096,34*7A
(15:40:27) GPS-NMEA : GPS-USB: $GPGSA,A,3,26,21,29,31,16,20,25,05,23,,,,1.68,0.93,1.40*0A
(15:40:27) GPS-NMEA : GPS-USB: $GPGGA,154029.00,5244.47619,N,00033.00784,E,1,09,0.93,12.6,M,45.8,M,,*69
(15:40:27) GPS-NMEA : GPS-USB: $GPVTG,,T,,M,0.113,N,0.209,K,A*2B
(15:40:27) GPS-NMEA : GPS-USB: $GPRMC,154029.00,A,5244.47619,N,00033.00784,E,0.113,,160517,,,A*7D
-
Now I am confused
If you connected via PuTTY on your PC, and you saw binary data, this same binary data will be sent to the PI.
I cannot recall, but the messages you are seeing _may_ only be the ones which are successfully parsed.
If binary data is being sent to PilotAware - that will cause a problem, because it is unexpected by the parser.
Thx
Lee
-
Me too! In fact I'm very confused!
Is PaW filtering it out?
-
I think the goal should be
- disable the binary output
- see the effect on Pilotaware
How about this ?
https://forum.u-blox.com/index.php?qa=1202&qa_1=it-possible-to-configure-the-gps-order-not-to-send-binary-data
Thx
Lee
-
Ok I can turn off these messages in CFG-CFG_revert or by disabling the messages however it is not saved when I unplug the GPS and plug it back in two messages are always returning which is UBX_Nav, staus and service info.
CFG-CFG-Save doesn't help either
I have asked on the uBlox forum.
could some one plug a VK-172 in to a laptop and run the uBlox software go to message view window and see if you have the UBX message in bold?
-
I think Lee was intending to write the commands into the boot sequence for the PAW. Partly to avoid issues, but also increase the list of supported devices. As the GPS is unlikely to be removed while in normal use, that should be sufficient.
-
I think Lee was intending to write the commands into the boot sequence for the PAW
Hi Ian
Did you mean to say this ?
I wasn't intending to add this to the PAW Boot sequence, because these commands are ublox specific.
So if we were to use an alternate device, the other device would get pretty upset.
What I don't understand is how this device got into this 'state' in the first place, none of the ublox devices we have procured are in this state.
This was a homebuild, and hence the ublox was procured from another source.
Thx
Lee
-
Sorry Lee, I got that wrong, it was Jeremy that suggested that in reply #23
-
Progress, I think, although it doesn't address the root issue!
So this got very odd I have 2 uBlox GPS the mouse type and the USB dongle. Both send the UBX messages when connected to my personal laptop.
These messages are seen in Realterm, Putty and the uBlox software.
I connect it to a second laptop and neither GPS send UBX data or the binary data is not visible.
So here it is, my personal laptop has the uBlox data center installed so that I could test the GPS fix issue (my root issue) it installed the uBlox device driver too.
The second laptop has the generic Microsoft generic USB serial drive Usbser.sys
I have in device manager selected the USB serial driver on my personal laptop and I now do not see the binary data.
So i believe the Ublox driver is sending a command at connection time to enable it.
Also as an FYI, on the uBlox forum I was told that these devices cannot save configuration changes.
-
so coming back to the original issue.
you say you think that the GPS is not performaing as well in the PAW as it does in the PC ?
Can you confirm that on the PC which is using the standard driver.
And if you think there is an RF issue, do you see the same issue with the mouse, as per the dongle ?
If there was an RF issue, I would expect the mouse to perform better.
All this being said, we knwo performance indoors is poor due to modern windows etc.
Thx
Lee
-
Thanks Lee, I will test and time this tomorrow all being well and update all here.
-
In my playing around (I think it's officially called testing... ;D) I've noticed that the PAW does interfere with the GPS. It's not a problem for me in my aeroplane though, I get sufficient reception for everything. But the GPS does work better on a USB extension to take it further away from the Wifi and SDR dongles, as seen in a less GPS-friendly environment such as at my living room window. Using a GPS mouse (VK-162) also solves this RFI issue.
-
Though I use a USB mouse type GPS all the time now, Pauls post reminded me that I found that I got a more reliable GPS, when I used a USB extension lead with the original GPS. Mine is no more than 200mm long and made a big difference.
-
thanks guys, I was hoping to test out the fix times today but had to much work on, I hope to do it tomorrow...
-
OK just wanted to update you all on this. I did do a fix time and my USB ublox was around 186 secs whereas all my other GPSs ( I seem to be collecting them!) were between 8 and 30secs in doors.
I order a new USB GPS From HK and it came in a bag not the blister pack that the original one came in, so i thought this is not good, however it gets a fix in the house in around 20secs.
I then had issues with intermittently losing the wifi connection in flight, which required a reboot of the PI. I changed the lead for a 20SWG one and Sunday 2nd July flew to North Coates and back, around 1 hour each way with no issues.
So I'm hoping that my issues were down to a bad GPS and a power cable.
On the flight we saw other traffic including one at the same high on SD long before we made visual contact so all working well once more for me now. Thanks for your help.