Could you help our German testers to reproduce this? Would be fantastic to have them validate the result.
Which att p gains do you mean?
it is a zmr250 that flys with the naze just fine.
Today installed the latest qgroundcontrol and flashed the latest master.
it ist generic 250 racer.
Multicopter attitude control are like this
ptchrate-d 0.005, -i .2; max 500 -p 0.1
rollrate-d 0.005; -I 0.1; rollrate_max 500; rollrate_p 0.1
When I now try to lower the Pitch_p it tells me “Paramter write failed:comp:1 param:MC_PITCH_P”
When reconnecting, the changes are lost.
That’s really odd - we believe its a Wifi issue with the ESP8266 since we see packet loss there, but not via USB. Could you try setting your gains with USB and a computer?
In general we noticed that dropping the ROLL_P gain and increasing the ROLLRATE_P gain is better for racing - could you help us testing that?
One experiment to try is to drop ROLL_P to 3 and increase ROLLRATE_P to 0.25 (same for pitch). You still need to tune, that’s just a starting point. I would be interested to know if you get that to a satisfactory result, because then rate mode should be a lot more stable.
Everything was done via USB and the Computer.
I will try to Flash a complete new Firmware and will Report.
I’ve posted my ACRO gains for PixRacer here: https://gitter.im/kd0aij/dual_FC_S250AQ?utm_source=share-link&utm_medium=link&utm_campaign=share-link
IMHO, acro mode performance of PixRacer on my dual FC S250AQ is as good as Naze32 now.
I just flew the S250AQ again using CleanFlight/Naze32, and the Acro mode orientation hold with default PID gains was not better than my current tuning for PixRacer. I tried P gains from 1.0 to 1.4 and D gains of 15 and 30. So, in my opinion, PixRacer can easily compete against Naze32 for Acro mode flight.
And both ALTCTL and POSCTL modes performed well on the S250 today under the trees in my yard. Position accuracy was not great, but it stayed within a roughly 3m radius circle and movements were smooth. Altitude held within 2m of starting altitude over the test (< 1 minute).
I’m looking forward to test the new values. Unfortunately your gitter link doesn’t work.
Sorry. Still not working, even after signing in
oh well… my latest tuning for the S250AQ:
dose anyone fly the pixracer as a racer in a regular basis? I’m still looking for the right pid’s, for the right frame, to set the oneshot preopperly (pwm_disarm/min/max - 100/125/250).
At the moment at very low throttl it dosen’t have any osciations but if I rase the stick to the middle then it start shaking. Both slider are set to the right for pitch and roll.
I’m sure I’ll finde my setup for my raceblade 5" one day
Hi everybody - I pushed the 1.3.0 release out, which has much better racer support (just better default gains, in fact). Please update your QGC version, flash the latest stable and RESET your airframe configuration (which will keep your RC calibration, but reset your gains to our recommended defaults).
Make sure to use the QAV250 or 250 generic (if you fly something other than a QAV 250) config and give us some good feedback.
The 1.3.0 release is in a “soft release” state, which means we might still make amendments - so any flight testing you can contribute will help us a lot in ensuring we made the progress we wanted to make.
What version of QGC should be used to flash this 1.3.0 release?
Suggestion, when there are new releases, be it QGC or PX4, could you also include what version of the accompanying sw/fw is required/suggested. I personally never know if I should be using the latest, released, beta?
The latest release as per the website or the last Android beta as auto-installed if you are a tester. I still owe you the flight mode docs, they will come on the weekend.
- MANUAL / STABILIZED: The same thing on multi rotors, on fixed wing manual = like manual RC and stabilised is attitude control
- ACRO: Rate control, for quads only right now
- RATTITUDE: Stabilized around center, rate control on the edge of the stick range
- ALTITUDE: Altitude hold, attitude stabilisation
- POSITION: GPS and altitude control, you move the system around with the sticks. Planes fly a straight line with zero stick input, quads hold position
- AUTO: Pre-programmed missions
- TAKEOFF: Standard takeoff & holding position (circling for a plane)
- LAND: Land at the current location (not tested with planes yet, but would work in general)
- HOLD: Keep the current position, stick inputs disabled. You can update the current hold location via the tablet / GCS
I hope that’s good enough to get you off the ground initially.
With all due respect to the dev’s, is there a reason why questions like this and this (two questions with not one answer) get overlooked? I though it was just me but its looks as though others are confused about QGC flight mode assignment as well. For those new to PX4 FM or QGC SW, wouldn’t some well written documentation (or better yet, a video HOW TO from start to end) on how to set these flight modes up with QGC and TX be beneficial? It would help the forum in two ways, less questions to the dev’s, (more time to develop) and this forum (less clutter)? Any video that I have found is either about MP/ardupilot or some outdated PX4 video and isn’t useful at all. Could someone please help with this matter?
This is the rate loop impulse response for the AquaQuad, calculated from 20 seconds of log data containing one roll and one flip (gains are in the plot header):
These gains are substantially higher than the defaults for a DJI F450, but they are probably too high to be optimal for operation in stabilized mode.
Could you post your Settings for a F450?
Since the log muncher won’t accept the ulog format I’m using, I think this is the best I can do:
I want to share my experience of using Pixracer as a RACER.
That is my first experience of using Pixracer board and this experience was not great at all (compared to Pixhawk and Naze32)
- The first thing is that bundled ESP8266 WiFi never worked for me. (I was able to connect to wifi hotspot, but QGC never detected the board).
- Pixracer board and ACSP4 don’t seems to be designed for racers
- These 2 boards can’t be aligned the way to use short power cable and still fit into spacious ZMR250 frame
- Pixracer board has 2 telemetry ports, CAN and GPS connectors. This all takes extra space and weight which is critical for the racer and will not be used in 99.9% cases.
- There are a lot of connectors on the outer sides of the board and they are the first that will be teared off from it. The first one for be was debug port, second - FrSky telemetry port.
- All the stock settings for frames are
stabilized modeoriented and have very low
Irate gains. The most critical here is
Igain, in my case it end up slightly higher
Pgain. I have spent a lot of time trying to figure out how to tune it right. I was trying to follow the tuning manual from the px4.io, but it is totally not-relevant for tuning racer (ACRO mode in general). This article helped me greatly on tuning http://myfirstdrone.com/tutorials/how-to-tune-a-quadcopter/
- PID tuning with QGC is a pain, especially if you have to use USB connection:
- The biggest issue is that there is no PID tuning screen, you have to look them up in the general parameters table. So I have developed a PID screen for QGC (will post PR some time soon)
- If you connect USB while board is powered via the battery QGC will fail to recognize board in 99% of the cases and you will have to restart it. So EVERY single time you need to adjust PID you have to unplug battery and connect USB wait for board to boot, change settings, connect battery back and wait again. This takes enormous amount of time. With Naze32/Cleanflight you can connect USB and GC recognizes it and shows last screen in 1 second or less. It makes tuning very enjoyable. To workaround this I am trying to get BT connection to the board working.
- Another issue with PX4 stack in general for ACRO flight is that there is no Expo mode in the flight controller itself and no “Super-expo” or its analogy. It is critical as racers use Expo of 65-85 and having such a big expo on the Tx side significantly reduces sticks resolution. More details on this can be found here https://oscarliang.com/rc-roll-pitch-yaw-rate-cleanflight/
- Low throttle flight (20-40%) is very unstable with PX4. It starts to fall to one of the sides or back/front. It might be because of lack of
I gainat this throttle. So I am going to play with TPA and gains.
Conclusion - Pixracer and PX4 are not RACER ready but definitely heading this way. If I manage get a replacement boards I might continue contributing to this stack and will implement Expo and Super-expo for the px4, if not I will switch to Cleanflight.