You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Came across an issue when I put a pneumatic solenoid cable on the three wire expander, the piston is powered and is not controllable via code. Putting the pneumatic on the brain directly has no issue.
In opcontrol, I simply use buttons to toggle the piston.
voidopcontrol() {
while(1) {
if (ctrler.get_digital(E_CONTROLLER_DIGITAL_A)) {
piston1.extend();
piston2.extend();
}
if (ctrler.get_digital(E_CONTROLLER_DIGITAL_B)) {
piston1.retract();
piston2.retract();
}
delay(10);
}
}
I used this test code to see the action of the pistons. The one directly on the brain's ADI has no issue and properly functions, however, the piston on the three-wire expander become powered and no longer responds to the program. Toggling the piston via the brain when the program is off works for both pistons, which would rule out a bad solenoid, expander hub, and cables.
This was on PROS 4.1.1 on a Windows laptop. A friend tried on a Mac and the same issue exists. Let me know if any other details are needed.
The text was updated successfully, but these errors were encountered:
Came across an issue when I put a pneumatic solenoid cable on the three wire expander, the piston is powered and is not controllable via code. Putting the pneumatic on the brain directly has no issue.
This is the code used to initialize the pistons.
In opcontrol, I simply use buttons to toggle the piston.
I used this test code to see the action of the pistons. The one directly on the brain's ADI has no issue and properly functions, however, the piston on the three-wire expander become powered and no longer responds to the program. Toggling the piston via the brain when the program is off works for both pistons, which would rule out a bad solenoid, expander hub, and cables.
This was on PROS 4.1.1 on a Windows laptop. A friend tried on a Mac and the same issue exists. Let me know if any other details are needed.
The text was updated successfully, but these errors were encountered: