That is a copy/paste issue, sorry about that! I will try again (via email)
Edit: I have sent the copy/pasted file again (via email) however on examination of the fragment that you previously received, I noticed that at the point it cuts off there is an unprintable character in the original file. Chances are that the second version I emailed will cut off at the same spot.
This brings up an interesting question - should there be non printable characters in a NMEA 0183 data stream ? The original file is peppered with them. They only show up in the data portion of the stream (ie every sentence has a properly formed '$xxxxx,' bit followed by the data). The non-printable character does not show up in a particular NMEA sentence of a particular sender. From the same sender, one string might be ok, the other has the non printable character in it.
It would seem to me that there is data corruption going on ......
I have another NMEA to USB converter that I can try out. Also, it could be that I did not correctly hook up the existing converter. I will investigate when I am on the boat next.
Thank you for your help !
Edit 2: The unprintable character seems to show up in place of an expected comma rather than any actual data so although it appears random as far as when it shows up, it only seems to replace the comma character. I only have the original file in ASCII and not hex so I don't know if it substitutes the same hex data all the time or what ..... weird !
Although I obviously need to get to the bottom of this corruption, I wonder if the signalK engine should not handle this error more gracefully during data validation ....
Edit: I have sent the copy/pasted file again (via email) however on examination of the fragment that you previously received, I noticed that at the point it cuts off there is an unprintable character in the original file. Chances are that the second version I emailed will cut off at the same spot.
This brings up an interesting question - should there be non printable characters in a NMEA 0183 data stream ? The original file is peppered with them. They only show up in the data portion of the stream (ie every sentence has a properly formed '$xxxxx,' bit followed by the data). The non-printable character does not show up in a particular NMEA sentence of a particular sender. From the same sender, one string might be ok, the other has the non printable character in it.
It would seem to me that there is data corruption going on ......
I have another NMEA to USB converter that I can try out. Also, it could be that I did not correctly hook up the existing converter. I will investigate when I am on the boat next.
Thank you for your help !
Edit 2: The unprintable character seems to show up in place of an expected comma rather than any actual data so although it appears random as far as when it shows up, it only seems to replace the comma character. I only have the original file in ASCII and not hex so I don't know if it substitutes the same hex data all the time or what ..... weird !
Although I obviously need to get to the bottom of this corruption, I wonder if the signalK engine should not handle this error more gracefully during data validation ....