Skip to content
This repository has been archived by the owner on Oct 27, 2020. It is now read-only.

Blocks setDualVelocity is not a function #248

Closed
slylockfox opened this issue Jun 15, 2020 · 3 comments
Closed

Blocks setDualVelocity is not a function #248

slylockfox opened this issue Jun 15, 2020 · 3 comments

Comments

@slylockfox
Copy link

in 5.4, using blocks, you can add a dual-motor set block, and change the property from Power to Velocity. When I ran an opmode like this, the opmode crashed. The RC log contains this error:

06-14 20:48:56.099 5054 5432 E RobotCore: BlocksOpMode - "Velocity-Test-2" - main/JavaBridge - caughtException - message is TypeError: motorLAsDcMotor.setDualVelocity is not a function

The single-motor blocks seem to work correctly.

@lizlooney
Copy link

Yikes. Looks (from the code) that setDualTargetPositionTolerance might also crash. Thanks for the bug report!

@lizlooney
Copy link

lizlooney commented Jun 15, 2020

Actually, I think setDualTargetPositionTolerance is OK. Just setDualVelocity is broken.

@ftctechnh
Copy link
Contributor

@slylockfox This will be fixed in a future release of the FTC SDK software. A change was introduced, tested, and merged into the private repository. This change will be included with the next release of the software. Thank you for reporting this issue.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants