sigK periodically puts out faulty values when using USB-CAN converter

[Alpenskipper]

Hi!

I finally installed the USB-CAN adapter to OP. I receive a lot of data in sigK diagnostics. The values seem to be correct.

When using the data (e.g. speed.overground) in node red, there are periodically faulty values shown.
The same, when I use the sigK websocket - the values "jump".

Even sensor data (Temp, Hum), that does not come over the USB-CAN converter begin "jumping around", when the USB-CAN adapter is active. When I power off the USB-CAN adapter, the sensor data is ok again.

When I look on the values in OP sig K diagnostic, the values do not "jump".

Does anybody have this behavior?

best regards,

Martin

[e-sailing]

It sounds like you have same signalk values from different inputs. You can try to sort by signalk key in diagnostic to see double signalK keys.
In kplex you can filter these values in canboat not.

[Alpenskipper]

It sounds like you have same signalk values from different inputs. You can try to sort by signalk key in diagnostic to see double signalK keys.
In kplex you can filter these values in canboat not.

Thank you, that was the right hint. In deed I have navigation.speed.overground twice. And one of them produces faulty values.

How can I filter the signalK key in OP 0.17 ? I am a noob with sigK.

EDIT: Could you please give a an example, how the syntax for a filter could be?

   

EDIT2: In N2K input, there is only one SOG, the correct one. In sigK there is the second, faulty one. Where does is come from? There is no GPS Stick sctive.

   

[RedRyder]

*bump* Any progress? I'm interested in this.