Ok, I saw this once but can no longer reproduce it - works fine with and without logging. Iām pretty sure that this is again down to RAM usage - unfortunately the order in which things are initialized is a little bit random from an allocation perspective and memory can get fragmented in different ways from run to run, so I think what you need to do is get your accels properly calibrated and set FRAME_CLASS 1 and then reboot and run the compass cal. If that doesnāt work reboot and try again - Iām pretty sure it will eventually work. Here is the firmware I was using just for reference:
Thanks a lot for all your help!
I will try this tonight and let you know how it behaves.
By the way, when I ran the first tests, I was using ELRS 3 and it was fine (telemetry, etc.). I had to change the radio and I installed a Frsky R-xsr and Sbus works, but telemetry does not work no matter whatā¦ I tried Uart3 (TX) and changed all possible settings. Also tried uninverted pin on the receiver, but no luckā¦
Do you have any hints? Should I open a new topic?
Thanks again for all your efforts!
Rgds,
Andre
SBUS and Fport both require inversion - there is no software inversion on this board so I think you would need to attach to the pads labelled sbus and telem
This receiver uses Sport. SBUS is attached to SUS pad on the board and is working fine. I understand there is no inversion, so I am using the uninverted pad from the receiver and soldered it on T3, which I assume is serial3. I tried changing every parameter possible with no luckā¦
very often the uninverted internally grabbed (ie DIY) on an RX cannot drive the UART input protection circuitry on some boards since it is not buffered and often is clamped by the next devices it drives on the boardā¦happens oftenā¦I have even had issues with RXs that intentionally expose the uninverted on a pad with some autoplilots that have input protection circuits on their UARTS and expect healthy drive coming inā¦
Here is what I did:
Tried your firmware. Didnāt work again.
Loaded latest stable available (I am attaching to this message), disabled logging and compass calibration was normal. latest-stable.zip (652.1 KB)
.
Loaded your firmware again. Compass went crazy and could not recalibrate it.
Put back latest stable ā compass worked again and there was no need to recalibrate!
This is really crazy!
Tried your new firmware. Same problem. Even after disabling logging.
I am trying to attach the log here, but I got error msg stating itās too big (only 2mbā¦).
Please send me your e-mail and I will mail it to you!
Tks
Iām not seeing anything wrong in the logs other than very high offsets. What compass is this? Can you send a similar log for the stable firmware version?
Probably the offsets are high because I was moving the craft trying to calibrate the compass.
Itās a BN880 Gps unit.
I donāt think I will be able to send you a log for the stable firmware because I have to disable logging in order to get the compass calibrated. Unless you want me to calibrate it, then reenable logging to get you a log after calibration (I donāt know if this is going to work).
Please let me know what you prefer.
Tks
One final one before I go to bed. There is a bug on the send side which this fixes - but I am still occasionally seeing baro glitches, so not sure this will sort things.