-
Notifications
You must be signed in to change notification settings - Fork 43
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
Self Check Improvements #208
Comments
I would like to have a tool to automatically spin each thruster in sequence to confirm that they are indexed correctly and spinning in the right direction. I'm currently looking at @jpanikulam's attempts at something like this. |
That's a good idea. Would save time when we have problems or have to change out a thruster. |
It would be fairly straight forward to write an RQT plugin for this. |
What's the advantage of a RQT plugin over just a text based tool? |
I didn't realize this was just a request to the existing system, sorry. It should be pretty simple to set ROS parameters for the path to each device in /dev and check if the file exists from Python. |
@DSsoto suggested creating alarms so that we are notified of any changes. |
Also makes self check return the name of lost thrusters (uf-mil#208)
Addresses part of issue uf-mil#208, RS485 checks still need to be done for other peripheral devices
Also makes self check return the name of lost thrusters (uf-mil#208)
Addresses part of issue uf-mil#208, RS485 checks still need to be done for other peripheral devices
Also makes self check return the name of lost thrusters (uf-mil#208)
Addresses part of issue uf-mil#208, RS485 checks still need to be done for other peripheral devices
I addressed the 2 first points @duggerd made and also created the thruster_spin_test utility, Some of these diagnostic tests should be reported to the alarm server though, I will put that on the back burner. BTW, should we make the self_check run automatically when we launch the sub? Thoughts? |
As long as the sub is still in a totally inert and killed state for the test, this is fine. I don't want Ken getting any thruster surprises if someone forgets that this is a default launch behavior. |
Also makes self check return the name of lost thrusters (#208)
Addresses part of issue #208, RS485 checks still need to be done for other peripheral devices
We should also add to the self check:
Modified @duggerd's initial post so we can track progress from the issues tab |
The text was updated successfully, but these errors were encountered: