Another methodic review, this user was more methodic and accurate:
2 Likes
I’ve been using your Annotation script and it’s working really well. Do you have (or know of) a script that will pull all the non-default parameters from a full parameter file? I know MP has an option to show non-default parameters but it won’t extract just those to a file.
1 Like
Currently, I extract the default by amilcarlucas from a bin file and use a software to compare it, I see the changes make to the default values.
1 Like
I have scripts that do that, but they are not open source.
1 Like
@amilcarlucas Hey i saw there is something like.
Z vibrations are caused by the downwash of each blade hitting the arm and the forward traveling propeller hitting the oncoming air when moving.
how i could fix that?
Stiffen the frame, use stiffer props.
1 Like
I open sourced it in the form of a PR for ArduPilot extract_default_params.py.
Enjoy
1 Like
I installed bluejay then went to install the bd firmware and discovered there isnt a bdshot fimware for hte speedybeef405mini or the JHEMCU-GSF405A that I have. Is there a reason those boards dont support it?
They both support bidirectional DShot. It’s the opposite - there is no firmware version for them, which does not support BDShot.
1 Like
what should SERVO_DSHOT_ESC be set for to use bluejay escs on blheli-s?
I don’t really know whether the answer is right, but it seems from experience that Bluejay understands options 2 and 4 for SERVO_DSHOT_ESC (that is, both related to blheli_s).
At least they work well in flight, and option 4 enables extended telemetry. There is not really much coming via extended telemetry in the case of typical hardware running Bluejay, but I am working on supporting Extended DShot Telemetry v2 in Ardupilot, which will bring some status information about how much an ESC struggles to keep it going.
3 Likes
The RPM is coming through now thank you.
1 Like
The process can be automated with the new ArduPilot Methodic Configurator available from ArduPilot Methodic Configurator github repository
3 Likes
2 or 4. The reason the settings are different is because BLHeli_S/BlueJay use MCUs that are not able to leverage some of the newer features of 32-bit MCUs (e.g. DMA) and thus are quite timing sensitive (they use bit-banging instead). The settings change the calculation of the high/low period for dshot in a way that these firmware’s seem happier with. Why don’t they follow the standard you might reasonably ask? Well first off there isn’t really a “standard” for dshot timing. The output bitrates are fixed, but the duty cycle within that is not. Second off, blame BetaFlight - my suspicion is that many ESC manufacturers only test against BetaFlight in development - so if it works in BetaFlight they assume “job done” and move on. But BetaFlight itself also has some variability in timing because it also uses bit-banging in many instances. So what this boils down to is us trying to replicate BetaFlight timings on a very different platform, without a standard - and surprise, surprise, not everything works as expected.
4 Likes
FETtec is a better protocol in that regard. the checksum is not the best, but at least the timing is a lot simpler.
The GUI tool can now replace the text editor even when no flight controller is connected to it.
2 Likes
Did a temperature calibration step by step , but had different results
Reason for redoing was because the first time I left the FC in freezer only for few mins was a bit hesitant. And second calibration I thought my dog had entered the room and must have pushed the table where the FC was kept.
Total did 3 calibrations and all had different results. I understand tmin can be different depending on how long we keep the FC in freezer but tmax behaved quiet different in all 3 calibrations and all results are quiet different. Could you have a look.
Also the drone might have to operate in temp ranging from -10C to 55c .
Pixhawk orange cube+
Attempt 1- temp cal1 - Google Drive
Attempt 2 temp cal 2 - Google Drive
Attempt 3 temp cal 3 - Google Drive
1 Like
The second one looks the best. Use that one.
2 Likes
I have a drone with pixhawk cube orange FC in which temp calibration wasn’t done previously. The drone is tuned and have been flying it for a time now. Is it possible to do just the temp cal now? Will it hamper my pids? Or tuning ?