This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Reliably connect a SignalK data source
#11
(2021-06-05, 08:08 AM)tkurki Wrote: Hmm. Strike that, in my local test setup everything works: no matter if the master server is up or down when the client server starts it connects automatically.

You can debug the client's behavior by entering signalk-js-sdk/* in Server / Server Log debug value and check Remember debug setting to keep the value over restarts.

How recent is your server - when did you last update it?

It is the version supplied in the latest "openplotter" 1.37.3

I tried it again with the debug setting and this time I could see the "back off and reconnect" process running ... we are installing it on the boat today, so after this, debugging will be a bit more difficult as we don't have internet on the boat .. but I shall use the debug filter you mentioned and try to capture the data when it does it again.

Thank you for your assistance.
Reply
#12
Just for info, at the moment the only thing I can see in the log that looks like an error is:

Jun 05 08:52:02 signalk-to-nmea2000:TypeError: Cannot read property 'length' of undefined

Jun 05 08:52:02 TypeError: Cannot read property 'length' of undefined at hasAnyKeys (/home/pi/.signalk/node_modules/signalk-to-nmea2000/conversions/ais.js:379:52) at Object.callback (/home/pi/.signalk/node_modules/signalk-to-nmea2000/conversions/ais.js:61:25) at FullSignalK.app.signalk.on (/home/pi/.signalk/node_modules/signalk-to-nmea2000/index.js:238:55) at FullSignalK.emit (events.js:203:15) at FullSignalK.addDelta (/usr/lib/node_modules/signalk-server/node_modules/@signalk/signalk-schema/dist/fullsignalk.js:52:8) at doProcess (/usr/lib/node_modules/signalk-server/lib/deltachain.js:10:13) at DeltaChain.process (/usr/lib/node_modules/signalk-server/lib/deltachain.js:6:16) at Function.Server.app.handleMessage (/usr/lib/node_modules/signalk-server/lib/index.js:172:28) at Simple.result.pipeElements.(anonymous function).on.msg (/usr/lib/node_modules/signalk-server/lib/pipedproviders.js:36:17) at Simple.emit (events.js:203:15) at addChunk (_stream_readable.js:288:12) at readableAddChunk (_stream_readable.js:269:11) at Simple.Readable.push (_stream_readable.js:224:10) at Simple.Transform.push (_stream_transform.js:151:32) at Simple._transform (/usr/lib/node_modules/signalk-server/node_modules/@signalk/streams/simple.js:83:8) at Simple.Transform._read (_stream_transform.js:190:10) 

I think it was in the "host alive but did not connect" state at this point.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)