-
Notifications
You must be signed in to change notification settings - Fork 121
Add interface for automatic motor reversion detection #2760
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
Add interface for automatic motor reversion detection #2760
Conversation
35c49b5 to
286ef98
Compare
131e967 to
c6656a1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the vehicle fails to arm before a motor test because it is not in manual mode, there should be a button option to switch to manual mode (instead of just giving an error message). Alternatively the "arm" toggle could be reconfigured to automatically switch to manual mode as part of the arming process.
During the test it would be good if we can display the MAVLink INFO and WARNING status texts that get generated.
If the test fails, it would be good to display the following to help with troubleshooting:
Motor testing will fail due to any unexpected motions of the vehicle. Here are some common failure causes, and potential solutions:
| Cause | Solutions |
|---|---|
| no movement | - ensure the vehicle is in the water - ensure the ESC is powered and receiving valid signals - ensure the thruster is connected to the ESC |
| external movement | - ensure the vehicle is in calm water |
| poor movement estimation | - ensure the sensors are well calibrated - ensure the vehicle is not too close to large magnetic disturbances |
| incorrect frame selection | - choose the frame that matches your vehicle (or make a custom one) - ensure the frame's motion contribution factors suit the positions and orientations of your thrusters relative to the vehicle's centers of mass and volume (you may need to trim with ballast and/or buoyancy) |
| incorrect motor mapping | - ensure the thrusters are connected to the correct output channels of the flight controller, and in the correct order to match the frame numbering |
If necessary it is possible to manually test and set the motor spin directions instead.
c6656a1 to
81d5c58
Compare
ed5ad80 to
d44ee6b
Compare
patrickelectric
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
d44ee6b to
ee61179
Compare
|
Is it possible to finish this before tomorrow ? We kind of need it for the stable release. |
yep, planning to wrap it up today |
62c3656 to
0f194f0
Compare
| }, | ||
| disarm() { | ||
| this.armDisarm(false, true) | ||
| armDisarm(false, true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing await here, right ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we dont have to have an await there, unlike python, js will run the code regardless. as (now) there's nothing after it, I don't see the need. it would probably require a bunch of ther asyncs around the code. but I can do it if you want.
I did realise there was duplicated logic and removed the timeout, though, as we do have a timeout in the helper functions
0f194f0 to
2f16481
Compare
ES-Alexander
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SMS color requests
2f16481 to
395f776
Compare
ES-Alexander
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I still can't see the image (including in incognito mode)
- Patrick also mentioned this in an earlier review
- The status updates are inconsistent / sometimes get missed:


- The status text looks a bit too 'normal', especially when the test fails (at which point it just kind of looks like a description)
- it would be nice if we could colour it based on severity (e.g.
--successfor steps that work,--warningfor bad thrust, and--criticalfor failure)
- it would be nice if we could colour it based on severity (e.g.
395f776 to
14c2055
Compare
7593843 to
7f4be9d
Compare
ES-Alexander
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work! :D
I've confirmed the image is appearing now, and I was unable to replicate the earlier issue where some of the status text was getting missed :-)
Some minor suggestions around clarity and neatness. Feel free to merge afterwards :-)
d59340c to
b3ce1b0
Compare

fix #1840
Screen.Recording.2024-06-29.at.00.17.43.mov