It should be possible to just:

* install the signalk node.js windows server,
* pipe out data from Expedition (most likely in NMEA0183) over the network,
* set up that feed as a data source in the signalk server and
* finally consume the signalk data feed through one of the web interfaces.

The challenge is to handle performance oriented data such as target data, polar% etc as signalk previously lacked some sentences for that kind of data.

The best way would be if Expedition had signalk as a network option. Not that hard technically to develop but that codebase is open source and can't be utilized by Nick.

I did some development for an application taking data from the Expedition dll and piping out signalk delta messages. Not fully compliant with the signalk specs but potentially useful. I'll try to dig that up.

That would be good - my ideal would be for you to find a way to add SignalK as an instrument type and expose all the channels back into it. Using the DLL to expose the expedition channels would be the next best solution, I guess. The tools and power of the signalK environment are becoming really impressive, and complement Expedition nicely. The Mayara Radar API would allow multivendor radar support, for example, and more generally it could expose Exp derived values for use in other systems/processes and displays.  

Last edited by TomH (10/17/2026 1:23 pm)

Yup obviously the radar stuff is hacked together through reverse engineering the protocols. I tried it out the other week not expecting much, esp as my Furuno radar was on the should work but not tested list. I was quite startled at how user friendly and simple it was. It really did just work with no configuration - it auto discovered and identified the radar. Now if only I could overlay it on the absolutely gorgeous Reveal X charts ;-)