OpenPlotter / signalK / Actisense

[juancho38]

Hi Everybody,

I am not sure it's a bug, but it used to work as far as I remember, I need some help to troubleshoot for my first post !
Since last openplotter update, I get an error with the signalK server NMEA2000 connection to Actisense using serial (Actisense NGT-1 (canboat))
For each incoming messages, I will get a checksum error :

Code:

Aug 16 14:03:11 openplotter signalk-server[1846]: ERROR 2019-08-16T14:03:11.659Z [actisense-serial] Ignoring message with invalid checksum

I am getting used to openplotter with a NMEA simulator.
The same configuration works with NMEA0183, say NMEA 0183 / serial (NMEA 0183 Source: Serial, Validate checksum is set)
If anybody can help or give me ideas on where to search ...
Opeplotter 1.2 alpha / RPT3b+
Cheers.

[juancho38]

Some update ...
I realized, I had it to work with "Actisense NGT-1 (canboatjs)" NMEA2000 connection.
I found this error in Node Red :

17 Aug 07:14:34 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
17 Aug 07:14:34 - [info] Starting flows
17 Aug 07:14:34 - [info] Started flows
17 Aug 07:14:34 - [info] Server now running at http://127.0.0.1:1880/

I am not familiar at all with Node Red, how to "set your own key using the 'credentialSecret' " as stated ... ?
Cheers.

[juancho38]

Can somebody tell me what is this error message ?

Aug 17 13:50:11 openplotter signalk-server[23347]: DLE followed by unexpected char , ignore message

[tkurki]

The error messages sound like you are trying to handle non NMEA2000 data as NMEA2000.

The Node-RED messages are not related to your data format problem.

Can you describe what kind of a setup you have.


Sent from my iPhone using Tapatalk

[juancho38]

The error messages sound like you are trying to handle non NMEA2000 data as NMEA2000.

The set-up is a NMEA2000 simulator (Windows 10) on COM port, Com0com (virtual COM port pair on WINDOWS), socat command send it over network.
On Raspi, socat read it and send it to a virtual serial (pty)
Openplotter configured on above pty.
I didn' search a linux NMEA2000 simulator ... may be I should
I finally made it work by interverting input/output COM on windows ...
Don't really understand why !

Well, it works for my needs, fair enough !
Cheers.