XBOX Controller Triggers is an axis but which one?

[JohnFogarty]

Thanks for all your help I hope to try this out at Palmetto.

Just another quick Question. when I wired axis 3 into a True False Selector the true and False changed to 1 and 0 which i put my true code in 1, and my false code in 0. see attached pictures tell me if im doing this right. If the button is true then set the motor speed to the percentage of the button press, for variable control. If the button i...s false, then I made another true/false case for the sensor. In the false case, I set the motor speed to 0.1. In the true case, I set the motor speed to 0.

This way, when the button is NOT being hit, it looks for the sensor, and it spins it around REALLY SLOWLY until the sensor is tripped, and then it stops there.



and another

[Chris Hibner]

Originally Posted by John_1102

Thanks for all your help I hope to try this out at Palmetto.

Just another quick Question. when I wired axis 3 into a True False Selector the true and False changed to 1 and 0 which i put my true code in 1, and my false code in 0. see attached pictures tell me if im doing this right. If the button is true then set the motor speed to the percentage of the button press, for variable control. If the button i...s false, then I made another true/false case for the sensor. In the false case, I set the motor speed to 0.1. In the true case, I set the motor speed to 0.

I would recommend that you delete the wire from axis 3 and change your case structure back to TRUE and FALSE. Test axis three against "> 0.5" and if it's greater than 0.5, it will tigger the TRUE case, and if it's less than 0.5 it will trigger FALSE.

The problem with using the 0 and 1 cases is that it is possible that you cannot get to the 1 case if your XBox controller is out of calibration. If you use the 0.5 compare, you will be covered.