Fix issue #122

[dcrowe]

pyubx2 Pull Request Template

Description

Fixes #122

Testing

Tests have been run, but there don't appear to be any tests covering this change. Would you like a regression test added?

Checklist:

• [x] I agree to abide by the code of conduct (see CODE_OF_CONDUCT.md).
• [ ] My code follows the style guidelines of this project (see CONTRIBUTING.MD).
• [x] I have performed a self-review of my own code.
• [x] (if appropriate) I have cited my u-blox documentation source(s).
• [ ] I have commented my code, particularly in hard-to-understand areas.
• [ ] I have made corresponding changes to the documentation.
• [ ] (if appropriate) I have added test cases to the tests/test_*.py unittest suite to maintain >= 99% code coverage.
• [x] I have tested my code against the full tests/test_*.py unittest suite.
• [x] My changes generate no new warnings.
• [x] Any dependent changes have been merged and published in downstream modules.
• [ ] I have signed my commits.
• [x] I understand and acknowledge that the code will be published under a BSD 3-Clause license.

[semuadmin]

@dcrowe

Thanks for the contribution - much appreciated. I've merged your PR into RC 1.2.30. There is already a test of MON-RF parsing in test_stream.py (testMONLOG) but unfortunately it contains a jammingState value of 0 so didn't show up the issue.

I note also that the attribute currently defined as jamInd is referred to as cwSuppression in later versions, but I'll retain the existing name to minimise regression impact.

If you happen to have a real raw binary datastream containing a UBX MON-RF with a jammingState > 1, I'd be grateful if you could send me it and I'll add it to the test scripts - otherwise I can synthesize one. Thanks.