2020-07-06, 07:56 AM
(2020-07-06, 07:19 AM)tkurki Wrote: You configuration looks correct to me. Could you share your settings.json. located at $HOME/.signalk for doublechecking? You can also make sure that the values for the events do not contain any extra characters like spaces in them.
People often recommend activating signalk-to-nmea0183 plugin, but the ground rule is that if you are dealing only with NMEA0183 input data you practically never need signalk-to-nmea0183 plugin, as the input data is in always in NMEA0183 format already.
As for better diagnostic tools I agree. If you have specific ideas on what to improve in Signal K server please share them at https://github.com/SignalK/signalk-serve...ssues/1077
I do not understand this sentence?
"You can also make sure that the values for the events do not contain any extra characters like spaces in them."
Any values are standard NMEA0183 sentences. I have no control over how they are formatted. What are 'events' in this sentence? All connection labels are free of any spaces or odd characters. I only have AISGPS OPENCPNOUT and APREPEAT.
It will be the weekend now before I can get back to the boat to do the next round of diagnostics. But as I said I am at a loss to understand why this simple use case is not working. Do I need to use the serial app? I can't see why as SK server seems to have no issue reading the GPSAIS stream which is a 38400 serial NMEA data stream as an input.
The only data I am working with at present is NMEA data from the GPSAIS stream and the OPENCPNOUT stream from OpenCPN and of course the failing APREPEAT stream.
Cheers
Spart