Visit our Popular Forums

GreenHeaven · 11-09-2021, 05:52

Anything??
anything that will parse and display numbers from a wireless router feed

Lake-Effect · 11-09-2021, 06:39

More info needed about what you want. Many apps and projects exist. Google SignalK, "linux marine distro", OpenCPN, Open Plotter...

wsmurdoch · 11-09-2021, 06:50

Perhaps NavMonPc

GreenHeaven · 11-09-2021, 07:19

Quote:

Originally Posted by Lake-Effect

More info needed about what you want. Many apps and projects exist. Google SignalK, "linux marine distro", OpenCPN, Open Plotter...

Not a chart plotter. Just a raw data display. OpenCPn handles gps, ais, etc etc
Its the rest of the data I need to see, like engine data

Lake-Effect · 11-09-2021, 07:52

Quote:

Originally Posted by GreenHeaven

Not a chart plotter. Just a raw data display. OpenCPn handles gps, ais, etc etc
Its the rest of the data I need to see, like engine data

NMEA0183 is a basic talker/listener serial data stream. Wired NMEA0183 can be read using a RS232 to USB dongle and any number of serial terminal programs. You said your data stream is already wireless; please describe it (hardware & software). Chances are, if it's one of the popular arrangements, there will be many options for receiving and displaying it. The next question is whether there's any applications that decode those engine messages to something more useful like virtual gauges, graphs, etc.

Be Free · 11-09-2021, 07:57

Assuming that the "wireless router feed" has NMEA 0183 data that represents your engine data it can easily be imported into SignalK and displayed on any browser.

The only standard NMEA 0183 sentence I'm aware of that deals with engine data is RPM. Is this in a proprietary NMEA sentence? What engine data do you have in your "wireless router feed" and how did it get there?

Tehani · 11-09-2021, 10:12

Quote:

Originally Posted by GreenHeaven

Anything??
anything that will parse and display numbers from a wireless router feed

Do not complicate your life.
Try NKE instruments and SeaWi (for tablet and smatphones). There are many more, but these are free and very easy to use.

stevead · 11-09-2021, 10:58

Quote:

The only standard NMEA 0183 sentence I'm aware of that deals with engine data is RPM. Is this in a proprietary NMEA sentence?

The most recent NMEA 183 standard v4.11 standardized transducer names for the XDR sentence. For example

Code:

$ERXDR,P,370000,P,ENGINEOIL#0,C,82.3,C,ENGINE#0,U,23.86,V,ALTERNATOR#0,V,50,P,FUEL#0*33

is a valid NMEA 183 4.11 sentence for transmitting engine oil pressure, engine coolant temperature, alternator potential and fuel level.

Most of the gateway equipment vendors such s Maretron, Actisense, Shipmodul are now supporting this standard as do most of the display vendors (MFD's, etc). You will need to determine whether your gateway/multiplexer similarly supports standardized names.

Given that you don't want a chartplotter, just some UI for visualizing engine data then my guess is that the "Engine Dashboard" plugin for OpenCPN isn't going to meet your requirements, so I shan't have to worry about creating an Android build.

There are plenty of solutions out there as others have mentioned, both native UI and browser based. Just make a decision.

Be Free · 11-09-2021, 11:27

Quote:

Originally Posted by stevead

The most recent NMEA 183 standard v4.11 standardized transducer names for the XDR sentence. For example

Code:

$ERXDR,P,370000,P,ENGINEOIL#0,C,82.3,C,ENGINE#0,U,23.86,V,ALTERNATOR#0,V,50,P,FUEL#0*33

is a valid NMEA 183 4.11 sentence for transmitting engine oil pressure, engine coolant temperature, alternator potential and fuel level.

You learn something new every day (at least I try to)! Thanks.

GreenHeaven · 12-09-2021, 08:26

Quote:

You said your data stream is already wireless; ... there will be many options for receiving and displaying it.

YES wireless. Its a NMEA 0183 feed that OpenCPN readds just fine. as explained in this thread:
https://www.cruisersforum.com/forums...209706-14.html
The data baud rate and format are configurable, but as set, work with OpenCPN no problem for GPS and AIS data

Quote:

The next question is whether there's any applications that decode those engine messages to something more useful like virtual gauges, graphs, etc.

That was the topic of this thread:
https://www.cruisersforum.com/forums...id-255381.html
The answer is no, hence this thread.

Quote:

Google SignalK,

I am not clear what to download that is free to trial, how it connects to wifi router, what format it requires of the data feed, what software is required to convert the NMEA 0813 feed to signak K, what plugin is required to see data parsed out, is hardware required ... Its just a rabbit hole for a neophyte...

Quote:

Perhaps NavMonPc

This looks promising, but driver failed to start on win 10... need a deep dive on that

Quote:

Try NKE instruments and SeaWi (for tablet and smatphones).

already own perfectly good hardware. The software is whats problematic

Quote:

is a valid NMEA 183 4.11 sentence for transmitting engine oil pressure, engine coolant temperature, alternator potential and fuel level.

This is what I have:

<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGSA,A,3,20,30,02,16,06,07,09,04,,,,,2.23,1.15,1 .91*05<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGSV,3,1,12,02,36,282,31,03,03,128,40,04,25,069, 45,05,01,310,*71<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGSV,3,2,12,06,41,227,42,07,75,157,27,09,60,048, 43,11,44,276,30*7E<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGSV,3,3,12,16,13,049,36,20,31,309,32,30,42,203, 38,39,41,162,43*7E<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGLL,4113.07639,N,01334.39432,E,153437.00,A,A*68 <0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIDBT,15.0,f,4.6,M,2.5,F*20<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIMTW,6518.0,C*19<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIMTW,0.0,C*23<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIVHW,,T,,M,0.00,N,,K*4B<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIVHW,,T,,M,0.0,N,,K*7B<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPRMC,153438.00,A,4113.07635,N,01334.39438,E,0.14 8,,120921,,,A*7C<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPVTG,,T,,M,0.148,N,0.274,K,A*2F<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGGA,153438.00,4113.07635,N,01334.39438,E,1,08,1 .15,3.6,M,42.1,M,,*5B<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGSA,A,3,20,30,02,16,06,07,09,04,,,,,2.23,1.15,1 .91*05<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGSV,3,1,12,02,36,282,37,03,03,128,40,04,25,069, 46,05,01,310,*74<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGSV,3,2,12,06,41,227,43,07,75,157,32,09,60,049, 42,11,44,276,*78<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGSV,3,3,12,16,13,049,28,20,31,309,33,30,42,203, 44,39,41,162,43*7B<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGLL,4113.07635,N,01334.39438,E,153438.00,A,A*61 <0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) !AIVDM,1,1,,B,13ccJ`PP00Pv7iFGUVGGgww<2D0b,0*08<0x 0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $IIMTW,0.0,C*23<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $IIMTW,6518.0,C*19<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $IIDBT,15.1,f,4.6,M,2.5,F*21<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPRMC,153439.00,A,4113.07634,N,01334.39442,E,0.14 8,,120921,,,A*71<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPVTG,,T,,M,0.148,N,0.275,K,A*2E<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGGA,153439.00,4113.07634,N,01334.39442,E,1,08,1 .15,3.7,M,42.1,M,,*57<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGSA,A,3,20,30,02,16,06,07,09,04,,,,,2.23,1.15,1 .91*05<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGSV,3,1,12,02,36,282,38,03,03,128,41,04,25,069, 46,05,01,310,*7A<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGSV,3,2,12,06,41,227,44,07,75,157,33,09,60,049, 41,11,44,276,*7D<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGSV,3,3,12,16,13,049,28,20,31,309,36,30,42,203, 45,39,41,162,43*7F<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGLL,4113.07634,N,01334.39442,E,153439.00,A,A*6C <0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $IIVHW,,T,,M,0.0,N,,K*7B<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $IIMTW,0.0,C*23<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $IIVHW,,T,,M,0.00,N,,K*4B<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $IIMTW,6518.0,C*19<0x0D><0x0A>
<GREEN>17:36:19 (TCP:192.168.1.100:2000) $IIDBT,15.1,f,4.6,M,2.5,F*21<0x0D><0x0A>

That is a mutiplexed feed from:
1 AIS
2 GPS
3 seatalk depth and and speed
4 NMEA 2k engine data digitizer

All feeding over wifi in NMEA 0183 format and being displayed very nicely in OpenCPN (except the engine data)

I am trying to display
RPM
Oil Pressure
Coolant Temp

from this

https://www.ebay.co.uk/itm/NMEA-2000...-/174387508815

https://www.aliexpress.com/item/1005002024152862.html

Assuming this device is actually working, it would seem to be a fairly simple matter to add a simple display option to OpenCPN, but no.

Their manual states
PGN 059395 ISO Ack
PGN 0599904 ISO Request
PGN 060928 Address Claim
PGN 126996 Product Info
PGN 126998 Config Info
PGN 127505 Fluid Level
PGN 127245 Rudder
PGN 127488 Engine parameters
PGN 127489 Engine parameters
(port and starbord presumably)

So, I must look for ANOTHER app to display this infor even if it is just numbers.

GreenHeaven · 12-09-2021, 09:01

Quote:

Given that you don't want a chartplotter,
just some UI for visualizing engine data then my guess is that the "Engine Dashboard" plugin for OpenCPN isn't going to meet your requirements, so I shan't have to worry about creating an Android build.

OpenCPN is serving well in the role of chartplotter.
Assuming this device is actually working, it would seem to be a fairly simple matter to add a simple display option to OpenCPN, but not sure if you guys are willing to do it
[/QUOTE]

smac999 · 12-09-2021, 09:07

It looks like you are turning analog engine data to nmea 2000.

Why are you trying to convert the nmea 2000 engine data to nmea 183? That is Likly your issue. I have never seen 183 engine data before. Although it appears to be a thing now based on above. But your 2k to 183 device needs to handle that. Why not put the n2k data direct to a pc or wireless. Instead of trying to convert it to 183 first

Kelkara · 12-09-2021, 09:23

Quote:

Originally Posted by GreenHeaven

This is what I have:

<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGSA,A,3,20,30,02,16,06,07,09,04,,,,,2.23,1.15,1 .91*05<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGSV,3,1,12,02,36,282,31,03,03,128,40,04,25,069, 45,05,01,310,*71<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGSV,3,2,12,06,41,227,42,07,75,157,27,09,60,048, 43,11,44,276,30*7E<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGSV,3,3,12,16,13,049,36,20,31,309,32,30,42,203, 38,39,41,162,43*7E<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $GPGLL,4113.07639,N,01334.39432,E,153437.00,A,A*68 <0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIDBT,15.0,f,4.6,M,2.5,F*20<0x0D><0x0A&g t;
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIMTW,6518.0,C*19<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIMTW,0.0,C*23<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIVHW,,T,,M,0.00,N,,K*4B<0x0D><0x0A>
<GREEN>17:36:16 (TCP:192.168.1.100:2000) $IIVHW,,T,,M,0.0,N,,K*7B<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPRMC,153438.00,A,4113.07635,N,01334.39438,E,0.14 8,,120921,,,A*7C<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPVTG,,T,,M,0.148,N,0.274,K,A*2F<0x0D><0 x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGGA,153438.00,4113.07635,N,01334.39438,E,1,08,1 .15,3.6,M,42.1,M,,*5B<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGSA,A,3,20,30,02,16,06,07,09,04,,,,,2.23,1.15,1 .91*05<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGSV,3,1,12,02,36,282,37,03,03,128,40,04,25,069, 46,05,01,310,*74<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGSV,3,2,12,06,41,227,43,07,75,157,32,09,60,049, 42,11,44,276,*78<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGSV,3,3,12,16,13,049,28,20,31,309,33,30,42,203, 44,39,41,162,43*7B<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $GPGLL,4113.07635,N,01334.39438,E,153438.00,A,A*61 <0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) !AIVDM,1,1,,B,13ccJ`PP00Pv7iFGUVGGgww<2D0b,0*08 <0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $IIMTW,0.0,C*23<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $IIMTW,6518.0,C*19<0x0D><0x0A>
<GREEN>17:36:17 (TCP:192.168.1.100:2000) $IIDBT,15.1,f,4.6,M,2.5,F*21<0x0D><0x0A&g t;
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPRMC,153439.00,A,4113.07634,N,01334.39442,E,0.14 8,,120921,,,A*71<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPVTG,,T,,M,0.148,N,0.275,K,A*2E<0x0D><0 x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGGA,153439.00,4113.07634,N,01334.39442,E,1,08,1 .15,3.7,M,42.1,M,,*57<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGSA,A,3,20,30,02,16,06,07,09,04,,,,,2.23,1.15,1 .91*05<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGSV,3,1,12,02,36,282,38,03,03,128,41,04,25,069, 46,05,01,310,*7A<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGSV,3,2,12,06,41,227,44,07,75,157,33,09,60,049, 41,11,44,276,*7D<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGSV,3,3,12,16,13,049,28,20,31,309,36,30,42,203, 45,39,41,162,43*7F<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $GPGLL,4113.07634,N,01334.39442,E,153439.00,A,A*6C <0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $IIVHW,,T,,M,0.0,N,,K*7B<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $IIMTW,0.0,C*23<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $IIVHW,,T,,M,0.00,N,,K*4B<0x0D><0x0A>
<GREEN>17:36:18 (TCP:192.168.1.100:2000) $IIMTW,6518.0,C*19<0x0D><0x0A>
<GREEN>17:36:19 (TCP:192.168.1.100:2000) $IIDBT,15.1,f,4.6,M,2.5,F*21<0x0D><0x0A&g t;

That is a mutiplexed feed from:
1 AIS
2 GPS
3 seatalk depth and and speed
4 NMEA 2k engine data digitizer

All feeding over wifi in NMEA 0183 format and being displayed very nicely in OpenCPN (except the engine data)

I don't see any engine data in the above feed, just GPS, transducer, and AIS.

stevead · 13-09-2021, 00:13

There is no engine data in the sample you posted.

Understand that you have an engine sensor gateway that converts analogue engine sensor data to NMEA 2000.

However you haven't described what gateway/multiplexer you have that combines AIS, GPS, seatalk depth & speed and NMEA 2k data and transmits NMEA 183 over WiFi.

My guess is that your gateway/multiplexer is not converting the NMEA 2k engine data into NMEA 183 engine data.

BTW

Quote:

Assuming this device is actually working, it would seem to be a fairly simple matter to add a simple display option to OpenCPN, but no.

Their manual states
PGN 059395 ISO Ack
PGN 0599904 ISO Request
PGN 060928 Address Claim
PGN 126996 Product Info
PGN 126998 Config Info
PGN 127505 Fluid Level
PGN 127245 Rudder
PGN 127488 Engine parameters
PGN 127489 Engine parameters
(port and starbord presumably)

I think you don't understand the difference between NMEA 183 (ASCII data) and NMEA 2000 (binary data over a CAN bus). The two are not interchangeable, you require a gateway to convert one from the other.

GreenHeaven · 13-09-2021, 02:19

Quote:

Originally Posted by Kelkara

I don't see any engine data in the above feed, just GPS, transducer, and AIS.

Ah. Well thats what I suspected. THe instructions say just connect it to the nmea backbone. No power. But it has a voltage input, which I assume is not just measuring the voltage, but powerin the unit then.

Quote:

My guess is that your gateway/multiplexer is not converting the NMEA 2k engine data into NMEA 183 engine data.

I think you don't understand the difference between NMEA 183 (ASCII data) and NMEA 2000 (binary data over a CAN bus). The two are not interchangeable, you require a gateway to convert one from the other.

THe multiplexer is bi directional 0183 <-> 2K (so is seatalk to both nmea formats) and its working fine. The problem is in the analog encoder. probaby just needs power.

Thank you for the 0183 / 2k description.

Is there any possibility that you will support minimal engine data within the OpenCPN dashboard for ANDROID plugin, even if the transcoded 2k data is not in the format you identified?
I have no other guages and must make a long journey to where they are waiting.
The data could just be displayed a numbers...

Visit our Popular Forums

The Fleet

Cruising Business

Life Aboard a Boat

Seamanship, Navigation & Boat Handling

Engineering & Systems

Photo Categories

Recent Photos

Listing Categories