Motor issues when running ESC calibration
-
-
We ran the calibration script and failing to see where/which directory the html file is being stored. Could you point me to the location?
-
B blue referenced this topic on
-
@Alexander-Saunders , the file should be saved in the same directory where you are running the calibration script from (current directory). here is the line of code in the calibration script, which saves the figure right before trying to plot it in a browser.
-
here is the calibration result i got with my setup (and the a0, a1, a2 params are already in the xml file i linked before):
-
@Alex-Kushleyev after uploading the new params you sent the ESC no longer communicates with the VOXL2.
The ESC board is no longer recognized by VOXL2. All hardware is set up properly.
Screenshot 2024-04-17 110112.pngvoxl_uart_read_byte bus 12 is not initiated
Please point us in the right direction.
-
@rdjarvis , the latest params switched baud rate from 250k to 2mbit, but that should not be an issue. You should make sure voxl esc param in px4 is 20000000.
Please try voxl-esc python tools directly and make sure px4 is disabled when you run them (instead of running the voxl-esc wrapper like you did).
Sometimes stopping px4 gets the dsp in a weird state, in which case you can disable px4 from autostart, reboot and then do a voxl-esc-scan.py
-
@Alex-Kushleyev Copy all, we will try. Thank you.
-
For the esc tools, we were running the commands from /usr/share/modalai/voxl-esc-tools. To clarify, for the baud rate changes, do you want 2,000,000 or 20,000,000. We will try the tools again and confirm px4 is stopped via systemctl stop voxl-px4.
-
@Alexander-Saunders, my bad too many zeros. 2,000,000 (2Mbit)
-
The screen shot in earlier post today shows running “voxl-esc” which is a wrapper for the python tools, sometimes it is easier just to use python tools directly, but make sure they are latest version. the version in /usr/share/modalai is probably not latest. Normally you dont need to update the tools but if something is not working as expected, it is good to try the latest.
-
-
No worries. We also verified if the issue was with the particular param file and ran the command to upload a different one. No luck with that and we still receive the same error (Bus 12, ESC not detected, etc)
-
Can you please try voxl-esc tools from dev branch on github? Instead of /usr/share/modalai/voxl-esc-tools
-
Also, which SDK are you using? i am surprised to see this issue.
Also, can you please double check the ESC bootup sequence:
- apply power
- 4 blue leds flash quickly for 1 second, then turn off
- 4 blue leds blink twice
- motor makes a quick chirp (three tones based on the latest params that provided)
-
@Alex-Kushleyev ESC gave
4 LEDs quickly flashing
4 LEDs flash 3 times
Motor chirps -
-
One more suggestion, it often helps to use a direct connection between the ESC and your linux PC and run the voxl-esc tools there. This way you can see the plots instantly during testing and also if there are some issues with communication to the ESC, you can always connect it to the PC and check the ESC that way.
Do you have a USB to serial adapter cable that plugs into the ESC <-> PC ?
-
@rdjarvis said in Motor issues when running ESC calibration:
@Alex-Kushleyev ESC gave
4 LEDs quickly flashing
4 LEDs flash 3 times
Motor chirpsOK that is good!
-
@Alex-Kushleyev, yes we have the USB/Serial connector.
-
@rdjarvis , ok great. Lets take a step back and just make sure you can talk to the ESC from the PC.
I will test SDK 1.2.0 to make sure it works fine with voxl-esc tools with my esc.
