RS485 USB - SignalK NMEA Serial input log

[jamos.tan@gmail.com]

you should add ONE serial input ONLY to ONE App!

I'll make sure that this is the case.

1.
Before kplex the only way to include serial input was SignalK.Server. The setting seems okay, but be shure to set the config there to "NMEA0183". I am not shure if the BAUD rate will matter, but 4800 is the lowest Standard here. If you get correct Data it is okay. For USB-GPS i use 4800 or 19200 normally. Most USB-devices set the Rate someway automatically.

The dongle supports more baudrate, but it only shows the data with cad or screen when I set it to 4800.

2.
Your Depth NMEA Data looks some way disturbed, the Depth Numbers should be readable as Numbers in the Data, in your date there are empty ", , ,7, ,M ". It should look as something like: "xxx,1,4,M,yyy" for 1,4 Meter.
Otherwise the $SDDxxxand the Checksum at the End is correct, so your Baudrate is ok. Is your Boat swimming or on Drydock?

Good one! It's on a dry dock, I thought it might be broken or something, does it need to be in the water to work optimally?

3.
I would alias your USBxxx to something more readable in OP-Serial: usb.depth.
Then in OP-Serial connect it with NMEA0183 with 4800Baud to signalk. 
No setting in kplex. No other connections to this port.

Will try it!

If you see the Dxxx Strings in OpenCPN NMEA Monitor all is correct. 
If you don´t see the Depth Data then the Problem is in the Sensor itself (No Water, dirty etc.)

I hear the sensor clicking, but the data usually doesn't come up with numbers as in your example. And if it does, it's a wrong number. But, maybe this has to do with the fact I am on drydock at the moment.

Good Look

Thanks for your answers! I'll keep trying and report back.

---

I've tried all the suggestions. I only have the serial connection in SignalK, I tried the serial connection for the OP friendly name and the USB path with the 4800 baudrate. When saving the connection the "claim error" still came, even after restarting SignalK. Only after a reboot of the raspberry does the error go away. It doesn't give the error after that, but it doesn't report a plugin status also, only the connection activity is shown but no plug-in status.

There is no number of deltas/second for the connection reported, so I guess no signalk sentence is created.
In OpenCPN when adding the depth, it constantly says 999m and sometimes 63m. In the OpenCPN NMEA stream I cannot see any depth sentences coming through.

Starting to have the idea the sensor might be broken, or that it doesn't work on shore. I'll try to fill a bucket with water then

---

Jup, it was the fact that it doesn't work on land... duuh!
Bucket with water and sentences come through immediately. You can hear also a more constant tick sound. The slow ticks are more of a probing thing i think, more constant ticks are real soundings coming through. Feel a little bit stupid...