SOG/COG Problem?

[Dsanduril]

If I didn't make any typos or other mistakes this should be your test file with the Vs fixed and the checksums recalculated.

NMEATest2.txt.pdf

[Jurien72]

I tried running the sentences you posted earlier, and it still doesn't show up on the SOG/COG display.

[Dsanduril]

That pesky extra space is in the RMC sentence here on the forum. Works for me if I copy it back off the forum and remove the extra space.

[Jurien72]

I tried running your corrected file and it still does the same exact thing. No SOG/COG, signal light blinks from green to red. I did contact the creator of the converter, but no response from him yet.

[Dsanduril]

Interesting, I played the file back into my 4.8.4 installation and it seemed to work fine. I put a 100ms delay between each sentence.



I'll try 5.0 a little later and see what happens differently

[Jurien72]

How did you do the delay? And what is that box in the lower left?

I didn't attempt it with the dashboard- I was looking at the display on the bottom of the screen

[Dsanduril]

The box in the lower left is my serial playback tool, RealTerm. I also have com0com installed so I can pair two virtual comports, the RealTerm plays the file into one serial port, it is received by the other in O.

I tried in 5.0, all worked the same. Worked in both the dashboard and the status bar.

Tried the original file you uploaded in 5, the wind and heading data plays back fine, but the COG/SOG/Position not so much.

So, I feel comfortable that the "V" to "A" corrects those (with the recalc of the checksum).

So, I guess the next question is how your playback is running/connected. You're seeing data in the debug window, so not sure why it won't accept stuff that it accepts for me.

I'll load the NMEA converter plugin in 5.0 and see if that can be used to massage things.

[Jurien72]

I did notice something earlier- when I first connect to the converter, I get 2 or 3 sets of sentences that have the A in them and it did display correctly. Then the V messages began and it stops working. I hope the writer of the converter responds to me at some point, I do believe the problem lies there somewhere.

Very possible that I don't have something configured correctly. I also don't understand why turning off the checksum makes no difference.

[Dsanduril]

I managed to get the NMEA Converter running in 5.0. Used the config below:

$XXGLL, $??GLL1, $??GLL2, $??GLL3, $??GLL4, $??GLL5,A
$XXRMC,$??RMC1,A,$??RMC3,$??RMC4,$??RMC5,$??RMC6,$ ??RMC7,$??RMC8,$??RMC9,,,

Played back your original file. Got this in the logfile:

8:29:20 PM: MEH.NMEA Sentence received...$XXGLL,4626.838, N,8416.1876, W,4222.054,A*30

8:29:20 PM: PostProcess NMEA with valid position
8:29:20 PM: MEH.NMEA Sentence received...$GPGGA,004222.054,4626.838,N,8416.1876, W,6,4,0,0,M,,,,*2F

8:29:20 PM: PostProcess NMEA with valid position
8:29:20 PM: MEH.NMEA Sentence received...$IIVHW,312,T,312,M,2.6,N,5,K*4A

8:29:20 PM: MEH.NMEA Sentence received...$IIHDT,312,T*3C

8:29:20 PM: MEH.NMEA Sentence received...$XXRMC,4212.601,A,4626.838,N,8416.1876, W,2.7,-45,240320*02

8:29:20 PM: PostProcess NMEA with valid position

Note that the GGA comes through fine because it doesn't have a void flag. The "XX" messages are coming from the converter and being processed properly.

Later in the log you can see the originals come in:

8:29:21 PM: MEH.NMEA Sentence received...$GPRMC,004222.054,V,4626.838,N,8416.187 6,W,2.7,-45,240320,,,*2B

8:29:21 PM: MEH.NMEA Sentence received...$GPGLL,4626.838,N,8416.1876,W,004224.69 4,V*3C

8:29:21 PM: MEH.NMEA Sentence received...$GPGGA,004224.694,4626.838,N,8416.1876, W,6,4,0,0,M,,,,*23

8:29:21 PM: PostProcess NMEA with valid position

Notice that the GLL and RMC don't have a "PostProcess" entry like the XX above and the GGA in original form.

So, looks like NMEA Converter can be used to do what you want.

There are a few other sentences that should be massaged. Also, if you can make adjustments to what SailAway sends I'd recommend only getting one sentence with each kind of data. Right now you're getting three sentences that contain position, better to just get one if you can.

[Jurien72]

Oh sweet! I'll try that and see how it works on my end. I couldn't figure out what to put in the NMEA converter plugin, but now I see how it works. Thanks so much!

[Jurien72]

The NMEA Converter Plugin just causes OpenCPN to crash.

[Dsanduril]

I had the same problem in 4.8.4 and 5.0. It's not something I use regularly so can't comment much.

In the end, when I got it working, I stopped my playback so there was no data coming in, then opened the plugin preferences, configured the conversions, closed everything, then started the data stream. That seemed to work, although I only had it running for a few minutes and may just have gotten lucky.

[Edit] so it had been running for half an hour, but without data because I stopped the playback. At one point I had set the conversions to run every 2 seconds rather than on change (just as a test). As soon as I set them back to on change O crashed.[/edit]

[Jurien72]

I looked on the page showing the known bugs, and it shows where the ignore checksum isn't working. Seeing how its listed as a low priority, I don't expect much joy out of that.

[Dsanduril]

So I was reading the NMEA Converter manual and I think I see the reason for the crash. The setup I posted earlier uses wildcards for the input, which was just copying stuff I found in the manual. But that means that when "on change" is used the new XX sentence created by the converter will be fed back in, it will go around in a loop, and lock things up. Should be able to make it work by removing the wildcards and using the "GP" talker ID that is in your test file, that way it won't create a loop. Going to test now.

[Edit] that fixed the converter crash, sorry about that, remove the "??" wildcards and replace with the specific "GP" identifier.[/edit]

[rgleason]

Don and Jurien,



Please add your example to the Examples at the bottom of the wiki, for others, a couple of screenshots are often helpful. Thanks.



Also Don, a big welcome to the O Community of Editors. Thanks.