Reliable way to detect disconnected controller

[heydowns]

Mike,

You're right, that does make detection a bit more plausible.

The description was a little confusing at first, but makes more sense after re-reading.

Not sure if we'll have a chance to try this before ship, but we'll revisit after competition season; we've moved all functionality off the analog-in-digital space (we didn't need the extra buttons after doing a recalibration/reconfiguration).

Maybe someone else using this can post results.

Either way, it'd be nice to see this information (the summary of it, anyway) in a future rev of the user's manual.

Thanks for looking into this and sharing the details!

[Mike Copioli]

Originally Posted by heydowns

Mike,

You're right, that does make detection a bit more plausible.

The description was a little confusing at first, but makes more sense after re-reading.

Not sure if we'll have a chance to try this before ship, but we'll revisit after competition season; we've moved all functionality off the analog-in-digital space (we didn't need the extra buttons after doing a recalibration/reconfiguration).

Maybe someone else using this can post results.

Either way, it'd be nice to see this information (the summary of it, anyway) in a future rev of the user's manual.

Thanks for looking into this and sharing the details!

We have tested the code on our robot and it works great. It would be a good idea to make the ranges defines and adjust them based on the specific Chicklet you are using. Also you must ensure that the Chicklet is calibrated and verify the outputs with dashboard to ensure you are not excluding a valid state.