| name | about | title | labels | assignees |
|---|---|---|---|---|
pynmeagps Bug Report |
Create a report to help us improve |
semuadmin |
Describe the bug
A clear and concise description of what the bug is. Please include:
- The pynmeagps version (
>>> pynmeagps.version) - The complete Python script. Embed your code here (please do NOT attach *.py, *.zip, *.tgz or other executable / zipped files) ...
your code here
- The error message and full traceback.
- A binary / hexadecimal dump of the NMEA/UBX data stream.
To Reproduce
Steps to reproduce the behaviour:
- Any relevant device configuration (if other than factory defaults).
- Any causal UBX command input(s).
Expected Behaviour
A clear and concise description of what you expected to happen.
Desktop (please complete the following information):
- The operating system you're using [e.g. Windows 11, MacOS Sequoia, Ubuntu Noble].
- The type of serial connection [e.g. USB, UART1, I2C].
GNSS/GPS Device (please complete the following information as best you can):
- Device Model/Generation: [e.g. u-blox NEO-9M].
- Firmware Version: [e.g. SPG 4.03].
- Protocol: [e.g. 32.00].
This information is typically output by the device at startup via a series of NMEA TXT messages. It can also be found by polling the device with a UBX MON-VER message. If you're using the PyGPSClient GUI, a screenshot of the UBXConfig window should suffice.
Additional context
Add any other context about the problem here.