ESC.Err in AM32

Can anyone explain what the ESC.Err is telling me? The wiki says it’s the Error rate in %, but what does that mean in a practical sense? And how should I interpret this:

Skystar 40a individual ESCs on AM32. Dshot 600. Bidirectional Dshot. Brotherhobby 2812-900KV motors. 4S. Matek H743-Wlite
Loop rate 400hz. Dshot Rate 800hz. (Double loop-rate)

Maybe a bad wire or joint to that ESC??

Probably unrelated, but I would use SERVO_DSHOT_RATE,0 for 1kHz or SERVO_DSHOT_RATE,3 for triple looprate (more than 1kHz)

1 Like

It just means the %age of telemetry reads that were corrupted. The process is inherently noisy and there is an ECC to check packet validity, but you will still get packet errors.

1 Like

Thanks @xfacta and @andyp1per

This is from one of my student’s builds, and I would have assumed a wiring issue but I’ve looked at four or five of them and they’re all doing the same thing. The last ESC on each of them has that same error signature, with the same ~5 second pulse. I was wondering about the loop rate/Dshot rate and I was considering bumping those up to 1k or 1200hz and see what that does.

The reason I’m looking into this is we’ve had a string of crashes in Autotune. It looks to me like desyncs. We’ve been building the same kits for a few years and the only hardware change is ESC firmware. The same Skystar ESCs now have AM32.

Here’s an example: Proton Drive

Yeah that 5s drop is deeply suspicious. My guess would be that something is pegging the CPU every 5s causing the dshot updates to be failed - or maybe something is taking over the DMA channel, although this seems unlikely.

I agree it’s odd, but 5 seconds seems like a life time on system working at 400hz.

Looking at the hardware report CPU load is below 25%, and generally everything looks clean. There are only two things I noticed and I don’t know if they’re related or not:

The GPS data transfer has the same 5 second pulse

The clock drift seems to be a lot (but I’ve noticed this before so I’m not so sure here)

BTW AM32 has historically been unhappy with low update rates, you should definitely pick something above 1KHz

2 Likes

If I pick triple loop rate and my loop drops to say 300hz does that mean the esc update will also drop to 900hz?

kind-of but not exactly

Also getting this 5s drops and some error rate on bdshot and speedybee f405 v4 with stock 55a esc. I have extended dhsot telemetry enabled. bluejay 0.21