Skip to content

Latest commit

 

History

History
52 lines (32 loc) · 1.63 KB

bug_report.md

File metadata and controls

52 lines (32 loc) · 1.63 KB
Raw
name about title labels assignees
PyGPSClient bug report
Create a report to help us improve
semuadmin

PyGPSClient Bug Report Template

NB: Please raise any general queries in the pygpsclient Discussions Channels in the first instance.

Describe the bug

A clear and concise description of what the bug is.

Please specify the pygpsclient version (`pygpsclient -V) and, where possible, include:

  • A screenshot of the error.
  • The error message and full traceback.
  • A binary / hexadecimal dump of the UBX data stream (e.g. from PuTTY or screen).

To Reproduce

Steps to reproduce the behaviour:

  1. Any relevant device configuration (if other than factory defaults).
  2. 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 Ventura, Ubuntu Kinetic]
  • The version of Python you're using (e.g. Python 3.11.1)
  • The type of serial connection [e.g. USB, UART1]

GNSS/GPS Device (please complete the following information as best you can):

  • Device Model/Generation: [e.g. u-blox ZED-F9P]
  • Firmware Version: [e.g. HPG 1.32]
  • 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.