|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |
Launch files
Messages
Services
Plugins
Recent questions tagged ublox_dgnss_node at Robotics Stack Exchange
|
ublox_dgnss_node package from ublox_dgnss repontrip_client_node ublox_dgnss ublox_dgnss_node ublox_nav_sat_fix_hp_node ublox_ubx_interfaces ublox_ubx_msgs |
ROS Distro
|
Package Summary
| Version | 0.7.3 |
| License | Apache License, Version 2.0 |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aussierobots/ublox_dgnss.git |
| VCS Type | git |
| VCS Version | main |
| Last Updated | 2026-03-31 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
| Contributing |
Help Wanted (-)
Good First Issues (-) Pull Requests to Review (-) |
Package Description
Additional Links
Maintainers
- Nick Hortovanyi
Authors
Changelog for package ublox_dgnss_node
0.7.3 (2026-03-29)
- Added UBX_RXM_SFRBX and fixed bug for param set being sent to usb device upon change
- fix uncrustify formatting
- fix: handle concurrent access to parameters and remove deadlock risk
- Merge pull request #60 from SayedMuhamad/fix/rtcm-callback-resize-to-reserve fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes
- fix(rtcm_callback): replace resize() with reserve() to prevent leading zero bytes In rtcm_callback(), the output buffer was built using: data_out.resize(N); // pre-fills N zero bytes at indices [0..N-1] for (auto b : msg.message) data_out.push_back(b); // appends real bytes at indices [N..2N-1] This produced a 2N-byte buffer starting with N zero bytes, which corrupts SPARTN/RTCM3 framing. The u-blox F9P USB parser scans for the 0x73 (SPARTN) or 0xD3 (RTCM3) preamble at byte 0; with leading zeros it never found a valid frame start and silently discarded every correction message. Fix: replace resize() with reserve(). This pre-allocates capacity without filling, so push_back() places the real data at indices [0..N-1] and the resulting buffer is exactly N bytes with the preamble byte at index 0. Fixes: corrections delivered via /ntrip_client/rtcm having zero effect on receiver positioning accuracy.
- Merge pull request #59 from wentasah/fix Fix missing include with GCC 14
- Fix missing include with GCC 14 Without this, the compiler complains with: include/ublox_dgnss_node/ubx/utils.hpp:188:8: error: 'reverse_copy' is not a member of 'std'
- Contributors: Michal Sojka, Nick Hortovanyi, Sayed Muhammad
0.7.2 (2026-03-19)
- uncrustify fixes
- Add flags for LPP and has correction used
- Add lpp_corr_used and has_corr_used to flags
- Contributors: Nick Hortovanyi
0.7.1 (2026-03-18)
-
fixed uncrustitfy comment space
-
reverted fix for warning as not supported jazzy & humble
-
fix c++ header include for crustify
-
Fixed iterator bug and case labels
-
Fix deprecation warning
-
Merge remote-tracking branch 'refs/remotes/origin/main'
-
Merge pull request #57 from stan-guer/fix/nav-status-parsing fix nav-status decoding
-
fix nav-status decoding According to u-blox 20 HPG 2.00 , the status bits in the fixStat and flag2 fields in the ubx-nav-status message are not always consecutive, there are padding bits in there that are not accounted for in this decoding logic. Fix that. An obvious outcome is that the ubx-nav-status now properly shows RTK float or int status, the same status value that is in the (correctly decoded) ubx-nav-pvt message.
-
sync write lock scope changed
-
Merge pull request #56 from BravoBravoIX/fix/usb-timeout-handling
-
Improve USB write stability: 250ms timeout and mutex protection
- Set timeout_ms_ to 250ms instead of 0 (blocking) for hang safety
- Add write_mutex_ to serialize write_buffer() calls
-
Fix USB timeout crash in rtcm_callback Add exception handling for USB write failures in RTCM callback to prevent node crashes when USB bulk transfers timeout. Changes:
- Wrap write_buffer() call in try/catch in rtcm_callback()
- Change timeout_ms from 45ms to 0 (blocking) to match v0.6.1 behavior The 45ms timeout was too tight for slower USB 1.1 devices (F9P) causing intermittent LIBUSB_ERROR_TIMEOUT exceptions that crashed the node. Setting timeout to 0 restores blocking behavior consistent with write_buffer_async() and the previous stable release.
-
Fixed X20P parameters
-
build: Remove libtoml11-dev from package dependencies
-
build: Remove toml11 dependency from CMakeLists
-
feat: Replace toml11 with embedded SimpleTomlParser Implement custom
File truncated at 100 lines see the full file
Package Dependencies
System Dependencies
| Name |
|---|
| pkg-config |
| libusb-1.0-dev |
Dependant Packages
| Name | Deps |
|---|---|
| ublox_dgnss |