When FabMo loses connection to G2, it should be a less painful process
Currently, when FabMo loses connection to G2 (G2 dies) it requires a reboot. Not really sure what this improvement entails, or how much it can be improved. Can be triggered by setting an input to "initiate G2 panic mode" then use that input.
I think we could use bossac or other interface to tell the g2 card to reboot, and at the same time reboot the pi or just restart node/fabmo. Or give fabmo the ability to reset g2 card and then to try again for the usb connection.
Revisit https://github.com/FabMo/FabMo-Engine/pull/944 when working on a solution. Seems like it only works sometimes.
What's the "right" G2 codebase for the fabmo's G2 controller?
https://github.com/synthetos/g2/blob/edge-preview/g2core/controller.cpp#L284 suggests that sending a single character CAN command will force the G2 card to reboot.
https://github.com/synthetos/g2/blob/edge-preview/g2core/asciitable.txt#L27 (CAN is ASCII code 24 (decimail)
@obra the correct code base is https://github.com/FabMo/FabMo-G2-Core main branch.
@kyle-kingsbury Thanks! It looks like the same codepath is there, so you may be ok to use that same solution.
Awesome. Thanks for the info!