Closed danka74 closed 3 months ago
I think I may have the same problem. Did you find a solution @danka74 ?
My Garmin 527xs plotter is not able to receive AIS targets from the RPi over NMEA2000. The RPi is not listed among network devices. I too get a connection momentarily after booting the plotter, with 2-3 AIS targets displayed briefly, but they soon disappear.
My system:
RPi 4 with Pican-M hat OpenPlotter 3 beta Garmin 527xs plotter SignalK version 1.44.0 canboatjs
@fymmot sorry, I did not, but I'm "lucky" that I got one working plotter (Garmin 62cv). As a matter of fact, I haven't tried this season, but might do later. It's in the boat in its box.
Ah that's too bad! But at least I'm a little closer to understanding what the cause might be. Your 721xs and my 527xs are from the same Garmin series, it doesn't feel like a coincidence.
This issue is still affecting my installation and preventing my Garmin 527xs plotter from receiving any data over N2K.
Would anyone be willing to look at it for me? I would be very grateful!
I incurred in the same issue attempting to connect a Garmin GMI20 display connected via NMEA2K to a canboatjs device (driven by SignalK hosted in a rock-4se SBC -an alternative to RaspberryPI Single Board Computer I bought during RPI4 shortage - ). In the "NMEA2000" config page of the Garnmin display the canboatjs device appears as "unknown device". Going into the device menu the Garmini repeatss "device unknown" and states "seral number= invalid" . Very rarely I can see the GPS position received from Garmin, but it is quicly "discoonected" and recorded in the event register as "lost GPS connecction". I investigated furtherly and I found in the trace obtained typing in a linux terminal the command pipe "candump can0 | candump2analyzer | analyzer" that the CANbus Address Claim phase is repeated many times. I suppose that Garmin dev is attempting to request many times the product info of the canboatjs counterpart, obtaining unsatisfactory replies (in its "opinion"). I suppose that this behavior is depending on the firmware release of Garmin devices that is doing a more strict control on "compatible" N2K counterparts (this should explain why "older" Garmin or older fw release are less choosy). I was wondering if it is possible to "hack" the canboatjs in order to fool the choosy Garmin, e.g. hardcoding a different "serial" sent inside the product info PGN. The actual serial appears in the trace as "123456". Hereafter there are some pictures taken from GMI20 (sorry for the italian) 202307291232 - candump can0 %7C candump2analyzer %7C analyzer %7C grep Claim- trace.txt 20230729-analyzer_debug_output.txt
So far I have not been able to figure what Garmin doesn't like here. I plan on playing more with this next week...
I suppose looking at the analyzer output that Garmin dislike the response canboatjs give to its product info query. I tried to play with no joy 'hacking' serial number in candevice.js. Now I've to dismount my test plant. Maybe in three to four days I'll we back ...
Closing because of inactivity. I think some recent changes may have fixed it. Please let me know...
After an update of openplotter 2 earlier this year my plotter (Garmin 721xs) no longer received NMEA 2000 data from my Raspberry with PICAN-M NMEA 2000 interface. Sorry, I don't have details of previous version as I didn't expect to have to debug this issue...
The Raspberry/openplotter shows up briefly (2 seconds) on the device list of the Garmin plotter but disappears quickly. Showing logs when swithcing the plotter on (the plotter seems to request info and the Raspberry is sending, but the plotter sends nothing back).
Any thoughts?
Current version info: canboatjs@1.21.0 signalk-server@1.39.0
Output from debug of canboatjs:candevice switching on 721xs:
vs. when I have a second plotter (Garmin 62cv, receives NMEA 2000 data from Raspberry just fine!):