2021-07-06, 09:12 PM
(2021-07-06, 02:19 PM)sebba Wrote: yes, I tried it once, not very impressed
also, another problem is the "Output Events" and "Sentence Event" fields, which are always overwritten.
I have a nmea0183 connection for charplotter, named garmin. For this connection, I set the "Sentence Event" field as "garmindata".
Similar for autopilot, "Sentence Events" is set to "pilotdata", for AIS connection is "aisdata" and so on.
In garmin's connection, as "Output Events", I tried to set "pilotdata" (or "pilotdata, aisdata", to have data from autopilot and from ais)
In pilot's connection, as "Output Events", I tried to write "garmindata", because garmin's data should arrive in autopilot.
But when i set "garmindata" into pilot's connections, the garmin's "Output Events" field is overwritten with "garmindata" instead the initially entered "pilotdata".
The "hardware" is a Pi4/8Mb, Kingston SSD on USB3.0 port, running latest versions of SK and OP's apps.
Thanks for your time
Tried some of that on a windows laptop and raspberry pi zero but can't recreate any of those issues. With an arduino putting out an AIS message and wind message, as a serial data connection fill in the sentence event as "serial" and restart signalk and the field stays the same, data comes out of "signalk-server:eventserial" in the server log. Set nmea to nmea plugin to input event serial and output event serial2 and the data show in signalk-server:eventserial2 in the server log.
Haven't checked serial output but outputting serial2 to a tcp connection viewed in node red works fine.
Looks like your issues might be local, afaics signalk does exactly what it should do on 2 different installations.
ISTR something about server event fields not being saved but can't remember what the cause was, might be false memory as well, sorry can't help more, tried to break it but it won't break. maybe try a fresh card/install and do one bit at a time? The sksim app can be useful for creating data to play with.