Signal K Implementation

[verkerkbr]

Originally Posted by verkerkbr

I have looked at the data stream from O back to the SignalK server.

If you look at the Tactic plugin there is the Bearing Compass. Gives the distance and bearing to a waypoint. Don't know what data is used for this the gauge. But it get its data from O. How ?

Looked at the server input but no SignalK data to be seen for this purpose.

Next I did a try with an older setup.

Added in O an outgoing connection: UDP localhost and port 2000 and restricted the output to RMD and RMC. Then opened in the SignalK server an incoming NMEA183 signal: UDP localhost and port 2000.

Then I get the course and bearing from O in SignalK and can show this in the MXTommy SignalK display.

Regards,

Bram

Here the screenprint.

[verkerkbr]

If I make a route in OpenCPN and activate the route. The Bearing Compass and the data in MXTommy point from the start to the first waypoint of my route with distance and heading.


Bram

[Hakan]

In present O master we've added a function to use the AIS ship name hash file MMSINAMES also for AIS targets streamed via the SignalK connection.

Dave also added a connection time out and reconnect able to handle a SK server restart.

Some tweaks to parse XDR messages used in Dashboard instruments are also added. So far tested using the SK plugin for XDR with Air temp., pitch and roll.

Please test if you like.
Håkan

[verkerkbr]

I cannot try this here at home.

I just found a list with NMEA183 sentences compared to NMEA2000 PGN's

There is a command NMEA183 called HDC = 127237 in NMEA2K (Heading steering command)

Looking at my O connections settings outgoing UDP port 2000 in the list of settings the HDC is not available. So, I added HDC to the list.

Then looked at the MXTommy settings (SignalK) and I can make a setting with with this HDC:

(self.navigation.courseRhumbline.nextPoint.velocit yMadeGood).

Setting can be Default or EC as source. Do not understand what this mean.

The mentioned list is perhaps interesting. It covers nmea183 > nmea2K and the reverse nmea2K to NMEA183. I can make a copy of the list, dated May 2014.

Is this HDC the command the control of the autopilot ?

Bram

[verkerkbr]

Originally Posted by verkerkbr

I cannot try this here at home.

I just found a list with NMEA183 sentences compared to NMEA2000 PGN's

There is a command NMEA183 called HDC = 127237 in NMEA2K (Heading steering command)

Looking at my O connections settings outgoing UDP port 2000 in the list of settings the HDC is not available. So, I added HDC to the list.

Then looked at the MXTommy settings (SignalK) and I can make a setting with with this HDC:

(self.navigation.courseRhumbline.nextPoint.velocit yMadeGood).

Setting can be Default or EC as source. Do not understand what this mean.

The mentioned list is perhaps interesting. It covers nmea183 > nmea2K and the reverse nmea2K to NMEA183. I can make a copy of the list, dated May 2014.

Is this HDC the command the control of the autopilot ?

Bram

So it looks like in SignalK. Lower right dial.

[Hakan]

And SignalK can also use RMC as source:
(Speed => m/s, Degrees => radians.)

[verkerkbr]

Originally Posted by Hakan

And SignalK can also use RMC as source:
(Speed => m/s, Degrees => radians.)

Hi Hakan,

The signalK conversion of the RMC needs:

127250 129025 129029 are available and missing are 126902 127258 129033

and for HSC 127237 is also not available.

Bram

[verkerkbr]

Originally Posted by verkerkbr

Hi Hakan,

The signalK conversion of the RMC needs:

127250 129025 129029 are available and missing are 126902 127258 129033

and for HSC 127237 is also not available.

Bram

There is an update available of the SignaK server to release 1.21.0. Works well here on the RPI and 64.

The Bearing Compass in the RPI Tactical display points in the right direction.

The one in OpenCPN Tactical display on my Linux 64AMD points in the wrong direction and has no graphic display of the heading in degrees on the dial.

[Hakan]

Bram..
We have not looked into N2K messages at all when updating the inbound Dashboard, DB, to receive SignalK, SK, data for existing instruments. I assume the data that now use NMEA0183 as source will be found at the same SK-data path when originating from a N2K source. And though will show up on our existing DB instruments as it does now.

We also haven't looked into tactics plugin at all. There are experts for that plugin.

[rgleason]

Where are these available? Is there a web link?

127250 129025 129029 are available and missing are 126902 127258 129033
and for HSC 127237 is also not available.

I would like to add them to this page NMEA2000 GNSS

[verkerkbr]

Originally Posted by rgleason

Where are these available? Is there a web link?

I would like to add them to this page NMEA2000 GNSS

Hi Rick,

The conversion set from SignalK to NMEA2K is still restricted to:

AIS (129794, 129038, 129041)
Battery (127506 & 127508)
Battery Mapping
COG & SOG (129026)
Depth (128267)
Temperature, exhaust (130312)
Engine Mapping
Engine Parameters (127489,127488)
Engine Mapping
Location (129025,129029)
Heading (127250)
Speed (128259)
System Time (126992)
Tank Levels (127505)
Outside Temperature (130312)
Inside Temperature (130312)
Engine Room Temperature (130312)
Refridgerator Temperature (130312)
Wind (130306)

Attached you find the list of NMEA183 to NMEA2000 and the other way around.

List is from Actisense. Gives an indication what NMEA183 codes are NPG's in NMEA2K.


Bram

[rgleason]

Thanks Bram, will add these.

[verkerkbr]

Small problem here on my RPI: No recogtion of signalK in OpenCPN.



Works again after switching off the Automatic discovery.

[bdbcat]

Bram...


More information and detail required, please.


Thanks
Dave

[verkerkbr]

Originally Posted by bdbcat

Bram...


More information and detail required, please.


Thanks
Dave

Hi Dave,

just tried the SignalK on my Linux Mint Tricia 64 AMD and with this version there is no problem with the automatic setting to on.

The problem only occurs with my RPI 4 Raspian 64 bits.

I use the compilation made by Tdan version 5.0522. It is only a small problem if you know the cause.

With automatic set to on, then there is no SignalK input in O.. Setting this to off then it works again. There must be a small difference in the sources that Tdan uses.

In the RPI I use the NMEA2K input in SignalK with the setting canbus(canboatjs).

This setting however does not work in the Linux 64 system. Then I must use canbus(canboat).

I'am using this mall canbus adapter called Canable.

Regards,

Bram