Dronecan dataflash log esc[n].err

Hi @rmackay9 ,

Thanks for reply, and for taking the time to add this to the issues list!

Pls note, I’m just testing this because the esc’s used offer this option, and it already seems to work. I can interrupt the can or bdshot signal line in any order and the motor keeps running nicely. The only issue that I can see so far, are the strange .err readings that look like bdshot related instead of the dual signal path related.

The esc’s do not offer parallel can inputs, so attempting parallel can busses would be difficult with this hardware setup. But that would be more logical I agree. The reason I tested bdshot instead of pwm is that I would like to keep rpm filtering going also on the ‘backup’ signal line if at all possible.

The main reason we are pursuing this is to reduce the chance of losing a system without a way to really find the cause / getting hold of the .bin file… ( we had an incident like that a couple of weeks ago, with most likely cause that we can find ‘that something went wrong in the signal path from fc to esc’, that system was running bdshot600, no can yet, just .tlog link to help request for this incident ).

Improving reliability by choosing an octa-quad ( or hex ) configuration was certainly a consideration, but in our experience, is hard to combine with (very) long endurance. So we went for a ‘simple’ quadrotor, a classic engineering tradeoff I guess.

Thanks for the help!