a) Watchdog monitor memory increased (may have caused watchdog reset)
b) Compass ordering fix when COMPASS_PRIOx_ID is 0
c) Hex CubeOrange 2nd current sensor pin correction
d) Hott telemetry fix
e) Lightware I2C driver fix when out-of-range
f) MatekF765-Wing voltage and scaling fixed
g) MatekH743 baro on I2C2 bus
h) Proximity (360 lidar) ignore zone fix
Flight controller support:
a) Bitcraze Crazyflie 2.1
b) CUAV Nora V1.2
c) Holybro Pix32v5
d) mRo Pixracer Pro
a) Benewake RangeFinder parameter descriptions clarified
b) Pre-arm check of attitude ignores DCM if multiple EKF cores present
A number of these fixes come from issues raised by Beta testers so we really appreciate the help you give us by flying these beta versions.
All feedback positive or negative is more than welcome. Feel free to post below or create a new thread and prefix the title with “AC4.0.4” (or something similar). Thanks!
Thanks for the report. It looks like the EKF is very very upset. Do you have an onboard log? And did this start as soon as the SCR_ENABLE parameter was set to “1” or does it happen even after a reboot?
My log disarmed was off. Yes. The error was there even after multiple reboots. I think it has to do with something related to scripting. I’m using neopixel LEDs on servo14 and it works fine if i use function=120 to 123. Error pops when i set the function to scripting. i.e, 94 to 107. Yes, It did start as soon as i enabled scripting.
In the vid it looks like scripting had stopped and the servo outputs are not set to to neopixel in the RCout message. So it cant be related to the neopixel output code but something in the setup code. Can you share your script and params I will try and reproduce.
4.0.4 does not detect my compass. An LIS3MDL.
I tried resetting all my parameters to default, but still, not detected.
This is a Kakute f7 mini.
Omnibus nano w/ 5883 is working.
Edit to add a couple details:
Compass enable is 1, enabled
Compass use is 1, enabled
Compass Typemask is 0, all
Nothing is detected in the list of hardware ID’s.
Although on one boot, it was! No other time, though, and I’ve been messing w/ this for hours now.
going back to 4.0.3 always works, so it’s not a loose wire or anything physical.
Do you have logs of 4.0.3 vs 4.0.4-rc2 showing it working on 4.0.3? I wonder if perhaps the difference is that with 4.0.4 you’ve somehow got the 1M limit version of the firmware loaded while with 4.0.3 the full version is being loaded. So the issue may be with which version is being automatically loaded onto the board.
Thanks for the report. Do you have a log so we can see what the actual rotation of those compasses is? I also wonder if this is how it appeared when you first opened the screen or was it after things were moved around?