This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
GPS longitude error
#1
I seem to have GPS issue with kplex and signalk. 

I get a correct fix, but then every 30s or so longitude goes to 0 degrees. Then jumps back to my correct position. 

This is not the fault of the GPS unit (BU-353), as it also happens when I have signalk process the output from my Simrad NSS8 GPS.

Interestingly blocking GPS sentences in OpenCPN doesn't remove the issue. 

Any suggestions?

Code:
<MAROON>11:00:32 (TCP:192.168.8.251:10110) $IIGLL,3638.6111,N,00627.1660,W,100028.020,A*33<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRMC,090028,A,3638.6111,N,00627.1660,W,6.2,302.2,180619,1.3,W*73<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $IIHDG,299.06,-1.32,E,,*0B<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKROT,-54.10,A*13<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRSA,2.14,A,,*00<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRMC,090028,A,aN0000NaN,N,NaN0000NaN,E,6.2,302.2,180619,1.3,W*14<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $INMWV,281.00,R,4.73,M,A*32<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $IIVWR,79.00,L,9.19,N,4.73,M,17.03,K*5D<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRSA,2.14,A,,*00<0x0D><0x0A>
<MAROON>11:00:32 (TCP:192.168.8.251:10110) $SKGGA,090028,3638.6111,N,00627.1660,W,GNSS Fix,10,0.9,-3.29,M,-0.01,M,,*29<0x0D><0x0A>
<MAROON>11:00:32 (TCP:192.168.8.251:10110) $IIGLL,3638.6111,N,00627.1660,W,100028.020,A*33<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRMC,090028,A,3638.6111,N,00627.1660,W,6.2,302.2,180619,1.3,W*73<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $INMWV,NaN,R,4.73,M,A*46<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $IIVWR,NaN,R,9.19,N,4.73,M,17.03,K*02<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $IIHDG,298.99,-1.32,E,,*0C<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKROT,-49.29,A*15<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRSA,2.14,A,,*00<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRSA,2.14,A,,*00<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $INMWV,NaN,R,4.73,M,A*46<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $IIVWR,NaN,R,9.19,N,4.73,M,17.03,K*02<0x0D><0x0A>
<MAROON>11:00:32 (TCP:192.168.8.251:10110) $SKGGA,090028,3638.6111,N,00627.1660,W,GNSS Fix,10,0.9,-3.29,M,-0.01,M,,*29<0x0D><0x0A>
<MAROON>11:00:32 (TCP:192.168.8.251:10110) $IIGLL,3638.6111,N,00627.1660,W,100028.020,A*33<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRMC,090028,A,3638.6111,N,00627.1660,W,6.4,302.3,180619,1.3,W*74<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $IIHDG,298.95,-1.32,E,,*00<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKROT,-38.22,A*18<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRSA,2.14,A,,*00<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $INMWV,NaN,R,4.73,M,A*46<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $IIVWR,NaN,R,9.19,N,4.73,M,17.03,K*02<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $INMWV,NaN,R,4.73,M,A*46<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $IIVWR,NaN,R,9.19,N,4.73,M,17.03,K*02<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRSA,2.14,A,,*00<0x0D><0x0A>
<MAROON>11:00:32 (TCP:192.168.8.251:10110) $SKGGA,090028,3638.6115,N,00627.1667,W,GNSS Fix,10,0.9,-3.29,M,-0.01,M,,*2A<0x0D><0x0A>
<MAROON>11:00:32 (TCP:192.168.8.251:10110) $IIGLL,3638.6115,N,00627.1667,W,100028.020,A*30<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $SKRMC,090028,A,3638.6115,N,00627.1667,W,6.4,302.3,180619,1.3,W*77<0x0D><0x0A>
<GREEN>11:00:32 (TCP:192.168.8.251:10110) $IIHDG,298.96,-1.32,E,,*03<0x0D><0x0A>
  Reply
#2
This issue is typpical when having more than one source for gps.
The working gps sends many data.
The other one tells you that it doesn't get a fix -> 0 but not so often.
When you mix both data it will show up as you said.

You can try to find double Signal K paths in "Signal K diagnostic". The wrong data has to come from somewhere.
In kplex you can filter nmea0183. In Signal K sentences can be filtered in node red (this will be easier in v2.x.x).
  Reply
#3
I have been having the same problem outside of openplotter (bad GPS fixes).
Thanks for the insite. I have a Garmin 152H that is solid and smooth when underway.
My class B AIS also sends GPS strings, but it is erratic by a few meters, so I prefer the Garmin.
But both are connected to opencpn and that must be where the bad fixes com from. I'll filter the AIS fixes and see if the problem goes away.
Thanks!
--
Larry - s/v Katie Lee Passport 45 Ketch (For Sale) - somewhere in Taiwan
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)