Hi there,
we have a device that defines a couple of custom message types:
- $PS,... for pressure and temperature information, and
- $IMU,... for data from an inertial measurement unit
Since these have less than 4 characters for the talker/sentence (?) field and don't follow the P<manufacturer> pattern, pynmea2 is currently unable to parse these. I'm not sure what a good solution would be, but maybe one of these would work:
- use the
ProprietarySentence types as a general fallback instead of enforcing a pattern
- introduce a
NonstandardSentence type as a fallback
- make parse a
@classmethod to allow overrides for custom parsing
Hi there,
we have a device that defines a couple of custom message types:
Since these have less than 4 characters for the talker/sentence (?) field and don't follow the
P<manufacturer>pattern, pynmea2 is currently unable to parse these. I'm not sure what a good solution would be, but maybe one of these would work:ProprietarySentencetypes as a general fallback instead of enforcing a patternNonstandardSentencetype as a fallback@classmethodto allow overrides for custom parsing