|
11-09-2024, 12:00
|
#2
|
Registered User
Join Date: Mar 2011
Posts: 768
|
Re: Problem with reading NMEA 0183 from N2K gateway ONWA KC-2W
An entry from your log:
$GPGLL,5216.8286,N,10419.8796,E,,V,N*56
The last two fields 'V' and 'N' indicate "data invalid" and "no valid fix" respectively.
So not surprising that OpenCPN is not reporting a valid position.
Either you really do not have a valid fix or the gateway device is not faithfully converting the NMEA 2000 messages to the equivalent NMEA 0183 sentences.
|
|
|
11-09-2024, 12:36
|
#3
|
Registered User
Join Date: Oct 2021
Posts: 503
|
Re: Problem with reading NMEA 0183 from N2K gateway ONWA KC-2W
Quote:
$GPGLL,5216.8347,N,10419.8833,E,,V,N*5A
$GPGGA,,5216.8347,N,10419.8833,E,,,,,M,,M,,0000*68
$GPRMC,100238.00,V,5216.8347,N,10419.8833,E,0.1,255.1,110924,87.0,N*7B
$GPVTG,255.1,T,,M,0.1,N,0.1,K,A*0E
$GPZDA,100238.09,11,09,2024,,*6A
|
+1 on stevead's comment. Both your GLL and RMC sentences are indicating no valid fix and mode indicator of no valid data.
You might get OpenCPN to display your position if you turn off GLL and GMC, the position indication is also in GGA, but the quality field is left empty. Since a '0' there = bad quality I don't know what OpenCPN will do with it being blank (if it assumes a zero for a missing value then you are in the same boat).
This reference I find to be pretty good at clear NMEA 0183 documentation.
|
|
|
11-09-2024, 18:30
|
#4
|
Registered User
Join Date: Aug 2009
Location: between the devil and the deep blue sea
Boat: a sailing boat
Posts: 20,688
|
Re: Problem with reading NMEA 0183 from N2K gateway ONWA KC-2W
Programs may handle the optional fields differently.
Test the receiver by plugging it into a N2K network.
A faulty n183 can be fixed up on the fly, but I would not go this way.
Perhaps you did not give enough time for the receiver to get a fix. This happens with cold receivers, long stored receivers, and especially indoor. So try giving it some extra time. Plug in, go get a coffee and see if it helps.
gl
b.
|
|
|
11-09-2024, 20:20
|
#5
|
Registered User
Join Date: Sep 2012
Location: Baikal
Posts: 606
|
Re: Problem with reading NMEA 0183 from N2K gateway ONWA KC-2W
Thanks to everyone for the answers!
I suspected that the problem was the lack of satellite signal strength status and apparently CPN is configured to receive FIX status to start working.
I also associate this problem with cyclical location losses with CPN-connected AIS transponders, where there is also a lack of GPS status, and again, other programs do not have this problem.
Question to the developers: Is it possible to add ignoring satellite signal quality to nmea0183 processing to allow location updates?
|
|
|
12-09-2024, 01:10
|
#6
|
Registered User
Join Date: Mar 2011
Posts: 768
|
Re: Problem with reading NMEA 0183 from N2K gateway ONWA KC-2W
Without seeing the original NMEA 2000 messages it is impossible to determine whether you genuinely do not have a valid fix or whether your gateway is incorrectly performing the conversion.
Until that is determined it would be premature to consider any changes.
My response to your proposal is not fit to print, but as I am not a developer....
|
|
|
|
Thread Tools |
Search this Thread |
|
|
Display Modes |
Rate This Thread |
Linear Mode
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
Advertise Here
Recent Discussions |
|
|
|
|
|
|
|
|
|
|
|
|
Vendor Spotlight |
|
|
|
|
|