TI Launch Pad Button Not Working

[billbo911]

We ran into a minor issue yesterday with the LaunchPad.
If we boot the DS with the LaunchPad connected, Windows recognizes it and it is displayed on the DS along with the Joysticks. Although, button presses are not sensed or displayed.

Now if we connect the Launchpad after Windows has booted, everything works correctly. This would be a major issue if the LaunchPad was buried inside our Drives's Station, or access to the USB connectors on the laptop were not easy to access. Fortunately, the portion of our Driver's Station where the LaunchPad is is a separate box and won't be plugged in until the laptop is booted.

[Christopher149]

Originally Posted by billbo911

We ran into a minor issue yesterday with the LaunchPad.
If we boot the DS with the LaunchPad connected, Windows recognizes it and it is displayed on the DS along with the Joysticks. Although, button presses are not sensed or displayed.

Now if we connect the Launchpad after Windows has booted, everything works correctly. This would be a major issue if the LaunchPad was buried inside our Drives's Station, or access to the USB connectors on the laptop were not easy to access. Fortunately, the portion of our Driver's Station where the LaunchPad is is a separate box and won't be plugged in until the laptop is booted.

Does F1 still refresh joysticks, and does that help?

[wt200999]

I was able to replicate this in a VM. In addition to your description, I also tried 'soft' disconnecting the device from the Windows VM (board itself stays powered) and reconnecting it, and I still was unable to get button inputs. So in this case the device requires a full reset.

On that note, and while not optimal, you can use the RST button or pin to force a reset. That seemed to work on my end to get the button inputs responding again.

Also rescanning or using F1 did not work to get the buttons responsive again.

I've submitted a bug for this on Github and we will take a look at it.

[billbo911]

Originally Posted by wt200999

.....
On that note, and while not optimal, you can use the RST button or pin to force a reset. That seemed to work on my end to get the button inputs responding again.

Also rescanning or using F1 did not work to get the buttons responsive again.

I've submitted a bug for this on Github and we will take a look at it.

Thanks for submitting the Bug!

Accessing the RST button on our Co-Pilot console is not an option. The LaunchPad is buried inside a closed 14" X 14" button box.
So, until a fix comes out, we will just not plug the box in until the Laptop is fully into Windows.

[BitTwiddler]

Originally Posted by wt200999

I was able to replicate this in a VM. In addition to your description, I also tried 'soft' disconnecting the device from the Windows VM (board itself stays powered) and reconnecting it, and I still was unable to get button inputs. So in this case the device requires a full reset.

On that note, and while not optimal, you can use the RST button or pin to force a reset. That seemed to work on my end to get the button inputs responding again.

Also rescanning or using F1 did not work to get the buttons responsive again.

I've submitted a bug for this on Github and we will take a look at it.

Guess we'll plan to make the reset button accessible from outside the box. Thanks for the "heads-up".

[billbo911]

Originally Posted by BitTwiddler

Guess we'll plan to make the reset button accessible from outside the box. Thanks for the "heads-up".

Just make sure the button isn't too easily accessed. The last thing you want to do is accidentally hit it right in the middle of a match!