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
I am able to use a CRServoImplEx instance to use setPwmEnable/Disable.
However, isPwmEnabled crashes the app with the following: E EventLoopManager: com.qualcomm.robotcore.exception.RobotCoreException: EventLoop Exception in loop(): IllegalArgumentException - invalid pwm channel: 4
Steps:
crsix.setPwmDisable();
...do other stuff...
if(crsix.setPwmDisable) crsix.setPwmDisable();
I was able to do a work around by keeping a local variable of pwm energize state when I call disable - to avoid calling enable on an already pwm energized port.
ServoControllerEx with port number parameter seemed to give same results.
Activity
Windwoes commentedon Nov 13, 2021
Looks to be a bug in the
LynxGetServoEnableCommandconstructor...It reads
But it should be
Windwoes commentedon Dec 21, 2021
This will be fixed in the next release of the SDK.
Windwoes commentedon Jan 17, 2022
Fixed in 7.1
Merge pull request FIRST-Tech-Challenge#233 from FTCLib/dev