We tried a new ESC, Modalai M0138-1, and that was detected. We are replacing the hardware and will resume testing.
Posts made by Alexander Saunders
-
RE: Motor issues when running ESC calibration
-
RE: Motor issues when running ESC calibration
Also to confirm, I followed the README from dev branch to update.
-
RE: Motor issues when running ESC calibration
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)
-
RE: Motor issues when running ESC calibration
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.
-
RE: VOXL 2 issue connecting with RC
We were able to resolve the issue. We went to /etc/modalai/voxl-px4.conf and changed the RC params to Spektrum.
-
VOXL 2 issue connecting with RC
Good afternoon team,
I am running into an issue with VOXL 2 communicating with the RC, transmitter, and QGC. The hardware being used is the Spektrum AR6210 DSMX and DXS RC controller. The RC and transmitter are bound and is utilizing the J19 port: https://docs.modalai.com/voxl2-rc-configs/ I have followed the documentation: https://docs.modalai.com/qgc-wifi/ https://docs.modalai.com/sentinel-user-guide-pre-flight-setup/#rc-radio-setup and video from https://docs.modalai.com/voxl-m500-quickstart/ with no luck. Could you point me to documentation that allows the drone to still connect to QGC while the RC and transmitter is bound? Any help is greatly appreciated.
-
RE: 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?
-
RE: Motor issues when running ESC calibration
To add to Ryan response for params, we have the value of zero for the params kp and ki.
-
RE: Motor issues when running ESC calibration
Using the script from this post: https://forum.modalai.com/topic/2522/esc-calibration I plugged in the one calibration test we ran before trying to troubleshoot the motor issues.
-
RE: Motor issues when running ESC calibration
The values I sent was the output. I did not send the visual plot of the feed curve because we turned our attention to debugging why the motor was not behaving as inspected. We are ssh into the voxl when running the test. I haven't done the steps of moving calibration_results.html to plot yet.
-
RE: Motor issues when running ESC calibration
@Alex-Kushleyev Good morning Alex,
The plot before the motor burned was as follows:
Quadratic fit: motor_voltage = a2rpm_desired^2 + a1rpm_desired + a0
pwm_vs_rpm_curve_a0 = 5.03240880692
pwm_vs_rpm_curve_a1 = 5.75204182026
pwm_vs_rpm_curve_a2 = -0.000365638113773We stopped testing for other motors because of the issues faced which is why there's only 1 instead of 4.
Also we changed the params/tune used by the motors to more closely correspond to the T-motor F2203.5 and zeroed out the kp and ki params based off of this response: https://forum.modalai.com/topic/3179/seeking-assistance-with-motor-heating-and-burnt-smell-issue-on-new-drone
-
Motor issues when running ESC calibration
Good afternoon team,
My team and I are currently trying to run ESC calibration for a quadcopter drone. The equipment is a T-motor F2203.5 which has a rating of 3 -6s LIPO battery, a 4s LIPO battery, VOXL 2, and VOXL FPV ESC 4 in 1. When running the calibration on outlet power and following these documentation: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/master/voxl-esc-tools/calibration.md and using the command:$ ./voxl-esc-calibrate.py --id 0 --pwm-min 10 --pwm-max 95 the motor will run to completion and return the pwm vs rpm curve. When following the same procedure on battery power, the motor will reach about ~58 PWR before burning out.
My question is what differences between the two power sources could potentially be causing this and could you point me to any additional documentation to troubleshoot?
Any help is appreciated!