Because our current implementation on the F310 uses a two-button enable and one of those buttons is also the disable button, button bounce or the order of depression of buttons can sometimes cause an immediate enable/disable sequence on this controller (also reported on the G29). One of three actions should be taken:
- Make sure that neither of the two enable buttons are used for any other function, including disable.
- Add a debounce timer after an enable before a disable can be processed.
- Go back to single-button enable and use different buttons for enable and disable.
Because our current implementation on the F310 uses a two-button enable and one of those buttons is also the disable button, button bounce or the order of depression of buttons can sometimes cause an immediate enable/disable sequence on this controller (also reported on the G29). One of three actions should be taken: