Which NMEA sentence for Heel instrument

[MattStibbs]

I'm sure I'm missing something in the documentation here, but I promise I've tried to find it!

I have an Orca Core which outputs outputs pitch, roll, and yaw via NMEA. I can see OpenCPN is receiving the sentences, but the Heel instrumnet doesn't seem to display a value.

Can anyone point me to the docs that describe what data OpenCPN is expecting for the Heel instrument to work please?

Thanks!

[Hakan]

OCPN Dashboard Heel instrument is looking for:
NMEA0183; $xxXDR. Type: "A", Name: "ROLL", Data: +-XX
NMEA2000; PGN 127257
SignalK: path: "navigation.attitude" , value: "roll"

[markcouz]

My NMEA compass puts out an XDR sentence with "AS08_ROLL" and "AS08_PITCH" which OpenCPN didn't understand.

I used NmeaConverter_PI plugin to create a new sentence with the correct descriptor and it works fine.

You may have a similar issue.

[rgleason]

Markcouz
Can you provide us with the formula you used. As an example.

[markcouz]

Originally Posted by rgleason

Markcouz
Can you provide us with the formula you used. As an example.

Here are a couple of screenshots...

The 1st pic is my NMEA steam with the original XDR sentence and my modified sentences highlighted. The 2nd pic is my formulas in NmeaConverter_pi.

A couple of notes...

1. In the manual explaining the use of formulas it seems to show a space after each comma, I put these into the original formulas but had to delete them to work correctly.

2. I created separate sentences for PITCH and ROLL, but this could be a single sentence if preferred.

3. There is some maths in my formulas (+5 for PITCH and +1.5 for ROLL) which I added for calibration of my output, others may require different calibration or none at all.

[markcouz]

...and a pic of the dashboard showing the output.

[Schnapsy]

@markouz

Your formula only works if and only if you have only one XDR sentence as input...
It is therefore not suitable...

[markcouz]

Works for me, by all means make corrections and post the suitable formula.

[Schnapsy]

@markcouz
Re-read what I wrote..
I know this formula works, I had also written and tested it several months ago.
The problem lies in the IIXDR header.

Personally, in addition to Quark-Elec, I also have other sentences that start with IIXDR, such as "$IIXDR,P,1.02481,B,Barometer*0D" or "$IIXDR,U,12.56,V ,BATTERY1*1F", etc...
And in this case, the transcription by Nmeaconverter generates errors.

I had bought the Quark-Elec QK-AS08 which is a stupid instrument since its nmea sentences are unusable as it is...
After trying - in vain - to use Nmeaconverter, I wrote a small arduino program which translates the Quark-Elec proprietary sentence into a standard nmea sentence.
But of course, if you only have one IIXDR source, using nmeaconverter is the easiest way.

[stevead]

What would be useful is for NMEA Converter to have a regular expression parser and an equivalence function.

Thst way it would be able to differentiate sentences based on field values.

[markcouz]

Originally Posted by Schnapsy

@markcouz
Re-read what I wrote..
I know this formula works, I had also written and tested it several months ago.
The problem lies in the IIXDR header.

Personally, in addition to Quark-Elec, I also have other sentences that start with IIXDR, such as "$IIXDR,P,1.02481,B,Barometer*0D" or "$IIXDR,U,12.56,V ,BATTERY1*1F", etc...
And in this case, the transcription by Nmeaconverter generates errors.

I had bought the Quark-Elec QK-AS08 which is a stupid instrument since its nmea sentences are unusable as it is...
After trying - in vain - to use Nmeaconverter, I wrote a small arduino program which translates the Quark-Elec proprietary sentence into a standard nmea sentence.
But of course, if you only have one IIXDR source, using nmeaconverter is the easiest way.

I understand, if I come across the issue in future I will look you up and ask for the arduino code.

[markcouz]

Originally Posted by stevead

What would be useful is for NMEA Converter to have a regular expression parser and an equivalence function.



Thst way it would be able to differentiate sentences based on field values.

Add my vote for a feature request.

[Hakan]

One obvious patch for OCPN Dashboard would be to look for a XDR that {Contains("PITCH")} and {Contains("ROLL")} instead of specifically "PITCH" and "ROLL" ?
I'll se if that change may be accepted for next OCPN release.