New Plugin NmeaConvertor

[rgleason]

Look in the manual, for Nmea0183 all sentences are listed there.

[Persistent]

Originally Posted by rgleason

Look in the manual, for Nmea0183 all sentences are listed there.

I have tried looking thru the manual but no luck explaining the RSA sentence for instance. i did find the pitch and roll info.

Any further info on the correct sentence would be much appreciated. I have tried a number of variations to the sentence but still cannot get it to show up in the tactics dashboard.

[Hakan]

For tactics I don't know..
O-Dashboard use RSA:

** RSA - Rudder Sensor Angle
   **
   **        1   2 3   4 5
   **        |   | |   | |
   ** $--RSA,x.x,A,x.x,A*hh<CR><LF>
   **
   ** Field Number: 
   **  1) Starboard (or single) rudder sensor, "-" means Turn To Port
   **  2) Status, A means data is valid
   **  3) Port rudder sensor
   **  4) Status, A means data is valid
    **  5) Checksum

For my own test run I've used it like this:
$IIRSA,2,A,,*33
$IIRSA,0,A,,*31
$IIRSA,-2,A,,*1E

[rgleason]

Originally Posted by Persistent

I have tried looking thru the manual but no luck explaining the RSA sentence for instance. i did find the pitch and roll info.

Any further info on the correct sentence would be much appreciated. I have tried a number of variations to the sentence but still cannot get it to show up in the tactics dashboard.

Well, I had that partly wrong. OpenCPN has no use for Rudder Angle, however Dashboard does. Dashboard does support RSA looking at the list under Dashboard we see that RSA is supported.

Looking at the Eric S. Raymond NMEA Revealed website provided at the top, we find the RSA Sentence definition
which is also supported in the same way, by Tactics and DashboardTactics (released version) because they are simply significant extensions of Dashboard.

Please see this screenshot running Dashboardtactics with VDRplayer playing Tactics sample files in the Tactics Wiki which has the Rudder Indicator working. Please take the pdf off the Tactics zip file and unzip it and use it with VDRplayer to test your setup for rudder indicator.

Here is one example of the RSA sentence in that file.

$IIRSA,-4.0,A,,V*50

[pa391as]

Originally Posted by rooiedirk

Made another push to the git source.
Now it is possible to use wildcards in the identifiers. So you could make it talkerid independent bij using something like .....$??XXX3.... , and whatever character on the ? position will cause a hit.
And maybe more important, you might use it for special transducers sending the something like $OWXDR,H,....or $OWXDR,C.... sentence. Note that field 1 is part of the indentifier. As the comma is the nmea separator, you can not use it as an identifier string, but by using a wildcard it works. For example ....$OWXDR?H2... or $??XDR?H2.... will work.
If there will be no bug reports the next few weeks, I do request for a final 1.0 status.
Dirk

The wildcard suggestion worked GREAT!!! to distinguish between sentences using the same header but containing different data!

$IIXDR,P,$ERXDR?P2*100000,P,MAIN,C,$ERXDR6,C,MAIN, G,$ERXDR10,H,MAIN

$IIXDR,U,$ERXDR?U2,V,STRT

[pa391as]

I'm using the NMEA Converter plug-in with the Engine Data Dashboard plugin - https://www.cruisersforum.com/forums...in-226092.html. This plug-in uses a specific transducer ID when decoding the NMEA sentence. In my setup, the ShipModul Miniplex is converting NMEA2000 PGNs to NMEA0183 sentences using different transducer IDs than the Engine Data Dashboard is reading. So I'm using the NMEA Converter plug-in to attempt to translate between the two. Further complicating the situation is that the miniplex converts PGNs that contain multiple data elements and distributes them into 4 NMEA0183 sentences, one of which contains multiple data elements. Here is what I get from the NMEA0183 log:

$ERRPM,E,0,2324.00,,A*69
$ERXDR,P,4.04,B,ENGOILP0,C,75.25,C,ENGTEMP0,G,2024 .1,,ENGHRS0*01
$ERXDR,U,13.75,V,BATVOLT0,I,0.8,A,BATCURR0*4D
$ERXDR,U,13.27,V,BATVOLT1*14

The first sentence is engine RPM. converts easily with the NMEA Converter plug-in using this:

$IIXDR,T,$ERRPM3,R,MAIN

The second sentence contains oil pressure, coolant temp, and engine hours. using wildcards, I can convert that using this:

$IIXDR,P,$ERXDR?P2*100000,P,MAIN
$IIXDR,C,$ERXDR?P6,C,MAIN
$IIXDR,G,$ERXDR?P10,H,MAIN

Now here's what things go south. the next sentence has House Battery voltage and shunt amperage. I try to convert with this:

$IIXDR,U,$ERXDR?U???????V?BATVOLT0?I2,V,HOUS
$IIXDR,U,$ERXDR?U???????V?BATVOLT0?I?6,A,STRT

the last sentence has Starter Battery voltage and shunt amperage. I try to convert with this:

$IIXDR,U,$ERXDR?U???????V?BATVOLT12,V,STRT

Both battery sentences start with U, so I have to get to the source (BATVOLT0/1) to distinguish

The converter is showing "NoData" for these last three elements.

Any help??

[pa391as]

Originally Posted by pa391as

I'm using the NMEA Converter plug-in with the Engine Data Dashboard plugin - https://www.cruisersforum.com/forums...in-226092.html. This plug-in uses a specific transducer ID when decoding the NMEA sentence. In my setup, the ShipModul Miniplex is converting NMEA2000 PGNs to NMEA0183 sentences using different transducer IDs than the Engine Data Dashboard is reading. So I'm using the NMEA Converter plug-in to attempt to translate between the two. Further complicating the situation is that the miniplex converts PGNs that contain multiple data elements and distributes them into 4 NMEA0183 sentences, one of which contains multiple data elements. Here is what I get from the NMEA0183 log:

$ERRPM,E,0,2324.00,,A*69
$ERXDR,P,4.04,B,ENGOILP0,C,75.25,C,ENGTEMP0,G,2024 .1,,ENGHRS0*01
$ERXDR,U,13.75,V,BATVOLT0,I,0.8,A,BATCURR0*4D
$ERXDR,U,13.27,V,BATVOLT1*14

The first sentence is engine RPM. converts easily with the NMEA Converter plug-in using this:

$IIXDR,T,$ERRPM3,R,MAIN

The second sentence contains oil pressure, coolant temp, and engine hours. using wildcards, I can convert that using this:

$IIXDR,P,$ERXDR?P2*100000,P,MAIN
$IIXDR,C,$ERXDR?P6,C,MAIN
$IIXDR,G,$ERXDR?P10,H,MAIN

Now here's what things go south. the next sentence has House Battery voltage and shunt amperage. I try to convert with this:

$IIXDR,U,$ERXDR?U???????V?BATVOLT0?I2,V,HOUS
$IIXDR,U,$ERXDR?U???????V?BATVOLT0?I?6,A,STRT

the last sentence has Starter Battery voltage and shunt amperage. I try to convert with this:

$IIXDR,U,$ERXDR?U???????V?BATVOLT12,V,STRT

Both battery sentences start with U, so I have to get to the source (BATVOLT0/1) to distinguish

The converter is showing "NoData" for these last three elements.

Any help??

Ok. After RTFM'ing a bit more and reading more of this thread, I learned that the wildcard must evaluate a non-numeric before the fieldnum. So updating the code I am now displaying BATT01 and BATTCURR values just fine.

Now I'm getting values for BATT1 displaying into BATT0. I believe this is because there is no non-numeric differentiation between these two NMEA0183 sentences. No non-numeric way to differentiate BATVOLT1, Correct?

$ERXDR,U,13.75,V,BATVOLT0,I,0.8,A,BATCURR0*4D
$ERXDR,U,13.27,V,BATVOLT1*14

[rgleason]

pa391as

Are there some clarification notes needed in the plugin wiki about the wildcard specifically?
Would you be interested in writing up your Use Example to be added to the wiki? It would be very helpful to others.

[rooiedirk]

The plugin is looking for text and a number as ID.
In your:
$IIXDR,U,$ERXDR?U???????V?BATVOLT0?I2,V,HOUS
try to replace the 0 from BATVOLT0 by a ?.
also:
$IIXDR,U,$ERXDR?U???????V?BATVOLT??I2,V,HOUS
Dirk

[pa391as]

Originally Posted by rooiedirk

The plugin is looking for text and a number as ID.
In your:
$IIXDR,U,$ERXDR?U???????V?BATVOLT0?I2,V,HOUS
try to replace the 0 from BATVOLT0 by a ?.
also:
$IIXDR,U,$ERXDR?U???????V?BATVOLT??I2,V,HOUS
Dirk

Thanks for the suggestion. I'm able to convert the BATVOLT that is part of this sentence

$ERXDR,U,13.75,V,BATVOLT0,I,0.8,A,BATCURR0*4D

just fine using this:

$IIXDR,U,$ERXDR?U??????????????????I2,V,STRT

However, I cannot get BATVOLT1 to convert, because it's sent in a sentence where the only differentiating character between BATVOLT0 and BATVOLT1 is a number (1), and the plug-in doesn't recognize numeric.

When I try this,

$IIXDR,U,$ERXDR?U?????????????????2,V,HOUS

it matches on the BATVOL0 sentence due to the wildcard, and BATVOLT0 value is displayed for both HOUS and STRT.

Would be good if the last char before it picks up the field match could be a numeric, or the regex match could be encased in control chars, something like this:

$IIXDR,U,$ERXDR?U????????"BATVOLT0"2,V,HOUS
$IIXDR,U,$ERXDR?U????????"BATVOLT1"2,V,SRTR

[pa391as]

Originally Posted by rgleason

pa391as

Are there some clarification notes needed in the plugin wiki about the wildcard specifically?
Would you be interested in writing up your Use Example to be added to the wiki? It would be very helpful to others.

Sure thing. I'm assuming this would go under 10. Using Wildcards.

Using wildcards is also useful when the data to be matched is in the data payload rather than the header. In the example below, we have engine data coming from the NMEA stream which contains the correct sender transducer ID, however is not the format required by the Engine Dashboard plug-in. Here is the original NMEA sentences:

// Engine RPM
$ERRPM,E,0,2324.00,,A*69
// Oil Pressure, Coolant Temp, and Engine Hours
$ERXDR,P,4.04,B,ENGOILP0,C,75.25,C,ENGTEMP0,G,2024 .1,,ENGHRS0*01
// Battery0 (Starter) Voltage and Shunt Current
$ERXDR,U,13.75,V,BATVOLT0,I,0.8,A,BATCURR0*4D
// Battery1 (House) Voltage
$ERXDR,U,13.27,V,BATVOLT1*14

You can see that the two battery voltages are distinguished using different transducer IDs, BATVOLT0 and BATVOLT1

The following NMEA Converter plug-in code converts to sentences so that the Engine Dashboard can read them. For the sentence that contains multiple data elements, we can us the wildcard "$ERXDR?P2" to match on the particular sentence that has the data we need.

To get battery voltage and current, we need to make liberal use of the wildcard to match out to the "I" in order to distinguish from the BATVOLT1 sentence. this gets us the battery0 voltage and the DC shunt current.

For battery1, I have not figured out how to convert this because the only character that distinguishes it from battery0 is the "1" at the end.

RPM
$IIXDR,T,$ERRPM3,R,MAIN
ENGINE OIL PRESSURE
$IIXDR,P,$ERXDR?P2*100000,P,MAIN
ENGINE COOLANT TEMP
$IIXDR,C,$ERXDR?P6,C,MAIN
ENGINE HOURS
$IIXDR,G,$ERXDR?P10,H,MAIN
HOUSE BATTERY VOLTAGE
$IIXDR,U,$ERXDR?U??????????????????I2,V,HOUS
DC AMPERAGE
$IIXDR,U,$ERXDR?U??????????????????I6,A,STRT

[pa391as]

Originally Posted by rgleason

pa391as

Are there some clarification notes needed in the plugin wiki about the wildcard specifically?
Would you be interested in writing up your Use Example to be added to the wiki? It would be very helpful to others.

I could not figure out how to become a wiki editor, can you advise, or post my example to the wiki?

[rgleason]

pa391as Thank you for sharing!

I have added your example and created an Outline at the beginning of the wiki
https://opencpn.org/wiki/dokuwiki/do...nmea_converter


We are always looking for good editors who are willing to contribute their skills to the wiki. It has been built and maintained by the users.


PM me on rgleason (see upper left?) click on it and send me a message with the user name you would like to use (most often the same as CF, your real name and your email.) I will enter you and an automatic Pw will be sent to you.


Thanks!

[Topodom]

Hi, I want to use NmeaConvertor but i am blocked on a simple issue.

if i type the folwing formula it's working perfectly :

$XXMWV_formula,$WIMWV1,  $WIMWV3 + $WIMWV3,pi*3.1111

and return

00:20:47 (Virtual:) $XXMWV_formula,298.8,25.2,9.7738*73<0x0D><0x0A>

But this one

$XXMWV_formula,$WIMWV1,  cos ($WIMWV3 + $WIMWV3), int(pi*3.1111) 
return

<GREEN>00:22:59 (Virtual:) $XXMWV_formula,298.8, cos (12.6 + 12.6), int(pi*3.1111)*43<0x0D><0x0A>

Where am i wrong ?

[rooiedirk]

I think (At this moment I can't test it myself) that you should remove the spaces.
" cos" is not recognized as "cos".