Multiple session on N2K?
SignalK set up to send data to my B&G setup for the performance plugin by @HansT. When I reboot, this happens more often than not. How do I avoid?
17 Replies
So it looks like it's connected to uniqueNumber missing in settings.json.
@Scott Bender I thought this was fixed already? If not, probably enough to add uniqueNumber to the variables to write to settings.json? It's already part of the can interface, so a secondary interface can get it's own number.
I’m not sure what the number being displayed there is. But if uniqueNumber is not in the setting (it should be), then it uses a random number.
There was also recently a change to the way the serial number is generated.
And possible more important, this fix
https://github.com/canboat/canboatjs/pull/268
So how do I implement?
Update your server with “sudo npm install -g signalk-server”
And check your connection in settings.json for uniqueNumber.
It should look something like ``` {
"type": "providers/simple",
"options": {
"logging": true,
"type": "NMEA2000",
"subOptions": {
"type": "canbus-canboatjs",
"interface": "can0",
"providerId": "can0",
"uniqueNumber": 920606,
Changed manually, but when reatarting the can connection is gone. When I add it and restart - this is what I get
very strange. I just created a new connection and it looks like this
try deleting your data connection via the admin ui, restart, then create a new one ?
@Runar did you upgrade the server as Scott mentioned?
Yes. I did. Restarted my pi and then screenshot my setting.json
I also notice 'providers/simple' in Runar's screenshot - that looks odd
\ /
Did a new upgrade with browser closed. Restarted my pi. Checked settings.json. Still no "uniqueNumber"
Did you deleted and recreate the data connection?
not on purpose as far as i know...
I asked you to do that above
try deleting your data connection via the admin ui, restart, then create a new one ?
Only the can or all?
Got it when removing and adding
Ok, so now look at the B&G Device list and restart signalk. This should now not result in a new SignalK entry and the old one becoming (invalid)