Cross track error precision in NMEA 0183 XTE message

[Polyman]

I am trying to work with some old navigation hardware that seem to accept
NMEA 0183 XTE sentences with only 2 decimal digits for the cross track
error parameter instead of 3 used by OpenCPN.

Is this something that can be configured?

Best
Tony

[Karanga]

A few years ago, I used the plugin "nmea converter" to add the letter M to an nmea data stream from an old flux gate compass, so that opencpn could know my heading for radar operation. It took a bit of fiddling to learn how to do the programming. It worked well for me.
I am sure that it would also be possible to modify number of decimals in a data stream.

[Polyman]

Thank you for the suggestion.

The NMEA converter plugin was in fact my first stab at this. It is a very useful
little plugin that saved my bacon a couple of times already but my understanding,
confirmed by some quick tests, is that the plugin is designed to use the same
precision used in the original sentence. I tried the age old trick of multiplying, taking
the integer and then dividing by the right amounts to eliminate the least significant
digit, but the plugin just adds a trailing 0 to go back to the same precision it started.

I have not yet found a way to coerce it to use a different precision than the input data.

Cheers!
Tony