Skip to content

Jazzy 2.3 Release #189

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 19 commits into from
Apr 11, 2025
Merged

Jazzy 2.3 Release #189

merged 19 commits into from
Apr 11, 2025

Conversation

tonybaltovski
Copy link
Member

No description provided.

roni-kreinin and others added 13 commits April 8, 2025 14:06
* Fix: Robust puma initialization
* Updated pumas to use platform/motors namespace
* Added comments to puma driver
* pass arguments by name for consistency

* Add remap for diagnostic topic

* Remove obsolete parameter

* Removed remaps for topics that don't exist anymore

* Add remap for soc topic

* Fix power status default rate

* Increase rate monitoring window on slow topics
* Add new categories and expected names

* Remove MCU, it will be populated in the generator

* Add additional motor drivers for the future

* Added diagnostic remapping for additional motor drivers

* Loosen rate tolerance on BMS State rate
* Add the fixposition launch file, add default ROS parameters to the config file. Add a section to document source-only drivers that we support but cannot explicitly depend on

* Specify the specific version of the fixposition driver that builds on jazzy, fix a copy & paste error in the launch file

* Add odometry topic to the core sensors API
* Create a new platform-extras.service to contain the platform.extras.launch instead of including that launch as part of the sensors service

* Install the new service

* Rename *_extras -> *_provider_files for clarity, fix installation of new service

* Add a new function to handle replacing the username in systemd jobs to reduce code duplication
This should make Production's life easier, as it will automatically make the testing package available after setting up the robot
* Diagnostics don't publish stale data

Clear out data in diagnostics when the respective topic becomes stale

* Don't publish diagnostics that are "not applicable"
* Add emergency stop topic to stop status diagnostics

* E-stop should just be a warning

* Improve estop diagnostic wording
* Add diagnostics for Lynx firwmare update process

* Update Lynx diagnostics frequently during update process

* Add firmware update cancelled status message
…user.target.wants` (#187)

* Add clearpath-robot.servce symlink to multi-user.wants, add a new provider to create symlinks in clearpath-robot.wants

* provider -> Provider

* Fix moving the symlink

* clearpath-robot.target -> clearpath-robot.service

* Update the post-install instructions to add systemctl-enable

* Fix the symlink generated by the RobotProvider
luis-camero and others added 6 commits April 8, 2025 15:09
* Add a postinstall file to automatically update the services when the package is installed/updated

* Restart the clearpath-robot service if necessary
* Update CAN script

* Wrap all in conditional
Send CAN messages rather than queue
@tonybaltovski tonybaltovski marked this pull request as ready for review April 11, 2025 16:41
@tonybaltovski tonybaltovski requested a review from a team as a code owner April 11, 2025 16:41
@tonybaltovski tonybaltovski requested review from mikehosmar and civerachb-cpr and removed request for a team April 11, 2025 16:41
@tonybaltovski tonybaltovski merged commit 53830d6 into jazzy Apr 11, 2025
3 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants