Collecting data from Furuno SC-70
Hey I would like to collect data from a Furuno SC-70 Satelitte compass. Can I use the Shipboard network (AMS, etc.)
(IEC61162-450) connector to connect it directly to my laptop with a ethernet cable and read the data with Signal K?
Link to full SC-70 manual:
https://www.furuno.com/files/Manual/198/upload/OME72820K_SC70_130.pdf
15 Replies
You can use Shipboard network to access IEC61162-450 data. Is J1 free or connected network switch and used other bridge devices?
If that sensor is already used on bridge sensor network, I would recommend to use datadiode to restrict uplink access.
So to say, been there, done that with Furuno bridge systems 👍
The SC-70 isn't connected to anything currently beside the screen that came with it, so the J1 is free. I'm wondering if it's possible to directly connect it to a laptop and collect the data with Signal K or do I need additional software and or equipment? When i connect my computer to it with a Ethernet cable my computer don't recognize the Ethernet cable as connected.
Try with network switch between. Are you familiar with 450 standard, multicast addresses and ports?
I made client plugin some years ago, that should work. Used this to collect data from real and simulated bridges.
https://github.com/KEGustafsson/signalk-iec61162-450-nmea0183-client
@Karl-Erik Gustafsson that link is dead, do you still have that client somewhere?
@Fabian Sorry, it was private earlier, now public.
Thanks 🙏!
Let me know if you need any help with it. E.g ports and which msg are included there.
Life safer
Will do
I’ll install and see if we can figure it out
Everything seems well; no errors, nothing on the debug UDP, but there’s no data. Also no data on the UDP out (10111)
Any ideas what we may be doing wrong?
This is the input we were sent by the bridge people:
From To Port Data Descr.
172.31.16.1 239.192.0.3 60003 HDT Heading
172.31.16.101 239.192.0.4 60004 ZDA GPS Time
172.31.16.101 239.192.0.4 60004 GGA Location
172.31.16.1 239.192.0.2 60002 VDM AIS
172.31.16.101 239.192.0.4 60004 DDPT Depth
172.31.16.21 239.192.0.2 60002 RATLB Dead Man Alarm
172.31.16.1 239.192.0.4 60004 INGLL Location
Multicast addr and ports seems to be in line with 450, OK.
Are you connected bridge swicth directly (via data diode)?
Or via additional switch or router?
Firewall?
SK in docker and docker running host mode?
https://github.com/codekilo/nmea0183-iec61121-450-server
With 450 server you can emulate sender? With Data Fiddler you can send e.g. AIS VDM msg and server is outputting it on multicast UDP.
If you setup another PC to test-send multicast messages to verify that you can receive those. If that is OK then you know that receiver or switch/router is not blocking it.
I'll setup once again my own 450 server-client setup.
SK on windows, no docker. I’ll check out the other things
Two Linux machines working OK, upper server - lower client.
Client subscribing 239.192.0.1 60001 = HDM & HDT messages
We got it to work
It turned out that the multicast broadcast address was routed to WSL2, for some weird windows reason
What was the changes/tunings to Windows?
I tried with Windows 11, Docker Desktop and SK from WSL2 Ubuntu . I was not able to receive anything to WSL2 then. Would be nice to know and test too.
WSL/2 are wierd pieces of Linux. Almost good but still no go for some purposes...