search

antipole2 / WhoGoesThere

For WhoGoesThere JavaScript
GNU General Public License v3.0
0 stars 0 forks source link

Cannot decode NMEA 2000 from Actisense NGT-1 #7

Open torrmundi opened 1 month ago

torrmundi commented 1 month ago

Issue with v0.2: hardware gateway: Actisense NGT-1, OpenCPN serial, in/out, NMEA 2000, COM3, 115200 baud 59904 are in the Debug Window, from src ids: 3 (NF80), 12 (Precision-9), 21 (IS40), 22 (IS40) But in this case, src id should be 1 (NGT-1)? NGT-1's Tx PGN List includes 59904 and Rx PGN List includes 126996. WhoGoesThere reports "NMEA2000 stations responding to PGN126996 request Source ProdCode ModelId SoftwareVersionCode ModelSerialCode Certification LoadEquivalency NMEA2000 byte count in data does not match actuality"

antipole2 commented 1 month ago

NMEA2000 byte count in data does not match actuality

That's curious. I have disabled that check in the latest version of the NMEA2000 object constructor. It is just possible that the installer has screwed up. Please check you have the latest version of the JavaScript plugin. Open the plugin tools and select the diagnostics tab and click on Dump. Please let me see the dump output down to the first line starting —————Console If you have a long list of N2K pgn registrations, just includ the first few and stop there.

torrmundi commented 1 month ago

Tony, Apparently, I had 3.02a. I updated the catalog, uninstalled v3.02a and installed v3.05c (after taking all the attached logs with v3.02a).

Today, I'm not getting that error with v3.02a. Go figure. I'm attaching outputs from iKommunicate for SK, N2K, and 183.
I never get the 126996 responses, since PGN 59904 is never sent through. UDP N2K cannot be tested bidirectionally, as OpenCPN won't allow a bidirectional UPD N2K port, and WhoGoesThere won't support two N2k ports.

iKommunicate WhoGoesThere v0.2.zip