Garbage attitude control
-
Hmm, that's really interesting. Looking back at the parameters from those tests, the UART_ESC_CONFIG was set to 1. I'll set it to 0 and see what happens.
@Tamas-Pal-0 go into qgroudcontrol parameters and set UART_ESC_CONFIG to 0. please post your results! -
Guys, I'm actively looking at this and will report what I find, it's my top priority.
-
Thank you @modaltb , much appreciated. I look forward to your findings. I disabled the modal_esc driver and it didn't help. Here is a log of the VOXL as flight controller, and one with a Pixhawk 4 as flight controller, with identical parameters. Both were mounted to the aircraft the whole time, all we did was swap wires around between flights.
Obviously there's still room for improvement with the Pixhawk 4 but for the most part it flew really well with default PID gains, whereas we couldn't even get the VOXL2 stable.VOXL2:
https://logs.px4.io/plot_app?log=25afc87c-37cd-4693-9318-df62be99e4bdPixhawk 4:
https://logs.px4.io/plot_app?log=4b8a4762-8f59-49ca-a7fc-af41d38c466b -
@Patrick-Hinchey I also have same experience like you. After disabling modalai_esc driver. I set UART_ESC_CONFIG to 0 also. It didn't help.
-
I'm still actively looking into this! One area that caught my eye is here:
https://github.com/modalai/px4-firmware/blob/voxl-dev/boards/modalai/rb5-flight/voxl-px4.config#L187
Out testing has been on a Sentinel setup and am wondering if there's some settings not propagating correctly.
This file can be edited on target to adjust, I'm going through some testing now.
-
I saw something similar with PX4 version 1.13.1; I don't have a VOXL2, but I had an issue where with VOXL 1 Flight Deck with PX4 1.13.1 did not work well for me on a standard airframe.
I downgraded to 1.11.3 sub-version 0.2.3 - I think this is a Modal AI sub-version? - and had better luck, maybe try an earlier version of px4
-
No smoking gun, but here's a commit I have going that uses params instead of hard coded values that we could give a try.
https://github.com/modalai/px4-firmware/commit/a0317b59e72eeb90126788e71093726dafe70708
File changed is here: https://github.com/modalai/px4-firmware/blob/pr-m0065-mr1/boards/modalai/rb5-flight/voxl-px4.config
On monday, I did fly the default Sentinel params with this VOXL2 IO board, it oscillated like crazy and we did a quick dirty tune and got it reasonable.
I'm going to request that we do a full tune on our Sentinel here to ensure we can get same perf as expected with this setup so we have a ground truth. Will report back when I have info.
-
Also, any chance you could post a link to a video of a flight to help us understand the failure mode even more?
-
Thank you for looking into this.
Here is a video
https://drive.google.com/file/d/1qPXFrxluE-MyOOpnfHQJ5eT4XOLYvGNu/view?usp=share_link
I'll try with the new config file tonight. However the Pixhawk4 parameters are very similar - min=1075, maz=1950 so I would be surprised if that mad all that much difference.
Also, regarding tuning the VOXL2, I'm curious to hear your opinion on why the same gains on the same machine would work great on the Pixhawk4 but not on the VOXL2. The Pixhawk4 is running the latest stable release -
Hey @Patrick-Hinchey ,
Thanks for the video, I'm gonna get some teammates to help early this week who are much more versed in this area.
Here's my setup, it's VOXL2 with VOXL2 IO, as you can see it's flyable but a little rough, I too initially had a wobble that prevented me from flying and changed params a bit from our default Sentinel settings to get it airborne:
https://www.youtube.com/watch?v=1INto92k-v0I'll get some members of the team early this week to better answer your second question and we'll keep cranking away.
-
Hi @Patrick-Hinchey, we are actively working on figuring out the answer your question about "why the same gains on the same machine would work great on the Pixhawk4 but not on the VOXL2." There are several differences between the PX4 code running on VOXL2 compared to Pixhawk4. Specifically, the path of the PWM commands to the motors including the px4io setup is different on VOXL2 compared to Pixhawk4. Additionally, VOXL2 uses a different IMU than Pixhawk4 and that IMU is configured differently. We will keep you posted on what we are able to figure out.
-
I hope all is well!
I'm sorry you're dealing with this - I know it can be frustrating.
I'm jumping here a little late and may have missed something. I was wondering, can you confirm that you have the correct motor mapping:
Also, were you able to successfully run through a PWM ESC calibration using these Instructions? Which specific ESCs are you using? Did you hear the expected chimes (maybe firmware not accepting)?
-
Thank you for your insight everyone,
We have an important milestone coming up in 2 weeks so we're going to use the external flight controller until then and then resume troubleshooting this issue after that - trying all the suggestions above.
Thanks, see you in 2 weeks!
-
Hi, I have the same problem. I have VOXL 2 I/O and every time I try to take it off it wobbles and crashes. I have a quad x, I have done the ESC calibration and I have followed all the instructions. Is there any solution to this problem?
-
@Chad-Sweet @xav04 I have had a chance to get our new ModalAI x T-motor F55A ESCs out of the box and plug them in. I can communicate with them over FTDI converter on my laptop, but the VOXL2 doesn't recognise them.
There's not much troubleshooting I can do as the tutorial just says to plug it in and set the correct PX parameters. Do I remember correctly that I read somewhere the MAVLink console doesn't work on VOXL2? It certainly doesn't work on mine.
The motors don't spin when I arm, and I'm not getting any telemetry info from them.
I followed the tutorial for VOXL EXC V2. IS there anything special I need for the F55A? -
Hey @Patrick-Hinchey I can get on the phone with you tomorrow if easier just let me know.
It's likely the baud rate on the VOXL2 side that needs to be updated. There's a param
UART_ESC_BAUDthat by default is 250kbitI believe the default baud on this F55A config is going to be 2Mbit (
2000000as the param).When you mentioned you are talkin' to them over FTDI, is this through the voxl-esc python tools?
As for the MAVLink console, we don't have the plumbing going for some of the commands over the UDP link from QGC to VOXL2.
That said, you can get to the nuttx like shell via command line if you SSH onto target or adb (captured here, as a work around )
-
@modaltb Sorry for not replying. Is there an option to set up email notifications?
Yep I was talking to the ESC with voxl-esc python tools. And I believe it was indeed at 2Mbaud.We've decided to use the FlightCore V2 as the flight controller going forward, with VOXL2 acting only as companion computer. We may revisit this sometime in the future as a weight-reduction exercise, but not any time soon
-
OK thanks for the info, we are still looking at the main issue at hand in this thread still.... it's slow progress right now, but we will update here when I have positive movement to share.
-
@Patrick-Hinchey
hi patrick
did you manage to solve the tune problem ?
we king of facing same problem with our drone
any help will be appreciate
