[karla]

Hi,
I have an Event warning coming on and off along with a Red MASTER CAUTION in the PFD.
Not sure if its so important but gets me little worried.
I think it started after I enabled Autotune and set up a SmoothQuick nob on accessory1.
Really great function by the way.
Any tips here?

[TheOtherCliff]

Only in AutoTune mode or in other flight modes?  FYI, AT is partially active even in other flight modes.

I assume this is not a Nano (which has a slower CPU).  Do you have extra features running (besides AT)?  INS13?  GPS?

I2C aux mags can cause issues (many do not communicate cleanly without extra pullups).  Do you have an I2C mag?

What is the CPU usage while it is happening?  Do you have more info on the warning?  Are there any other system health issues?

I would consider increasing the telemetry data rate / air rate, at least for a test.  If it still happens, I would completely remove AutoTune and see if it goes away.  (Remove AT from FMS.  Disable AT in System -> Settings -> HwSettings -> Modules if you enabled it there.)

[karla]

When I disable the AutoTune module the warnings goes away. Turn it back on and they come back.
Isn't this related to the speed of telemetry and the meta data setting of telemetry update speed? Set too high?

I found a similar thread here
https://forum.librepilot.org/index.php?topic=3238.msg22343#msg22343

But really not sure what setting to tamper with in the case of AT.

[TheOtherCliff]

I would consider increasing the telemetry data rate / air rate, at least for a test.

Also, there are many UAVOs that are sent that are not needed at all.  You could turn all those off in the metadata.  Here is a post that talks about that.  Only turn off UAVOs that you don't need to see in the log. 
https://forum.librepilot.org/index.php?topic=4020.msg27201;topicseen#msg27201

[karla]

thanks Cliff,
Will check the list of items.
For the data rate its already very high, at 100Kbaud.

[TheOtherCliff]

100K in next is actually the same as 57600 in 16.09 (from what I hear)

Anyway, reduce data sent and/or increase max data rate.  Good luck.

[f5soh]

I think it started after I enabled Autotune and set up a SmoothQuick nob on accessory1.
Any tips here?

Try using the FMSx3 instead of using the Accessory1 as input for SmoothQuick change if the EVENT alarm still.

[TheOtherCliff]

FYI: there is 2% hysteresis in the use of Accessory channel for SmoothQuick.  Any normal amount of channel jitter will not cause constant SQ changes.  If I recall, it also only does SystemIdentSettingsSet() at most twice a second.

[f5soh]

Can you try flashing the attached revo firmware without erasing the board and test if the event issue still ?
Accessory should not have jitter, or no more than ~20µs jitter.

[karla]

Thanks Cliff and Laurent.
I am a bit rusty on flashing bootloaders.
I should go to GCS Firmware and press Halt (when Revo is connected) and then load the file you uploaded. Then just let it reboot right?

[karla]

I think I did it correct.


The alarm is still there.
Its complaning there is a system version mismatch

[f5soh]

Mismatch is normal. This is not a bootloader flashing, but firmware.
We need to find this issue, maybe tomorrow / this week-end

[karla]

Okay. No hurry
Attached is the uav file, if needed.

@Cliff, Yes increasing the air data rate only from 100k to 128kBaud made all Event warnings go away. The corrections are a bit larger from afc -1 -3 kHz to -4 -6. But seems stable.