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
Is your feature request related to a problem? Please describe.
As of the new vexos 1.1.3 release, it seems like motors can now report their type (5.5W vs 11W) to the brain and be read by the SDK. I'm not sure if the PROS team has access to the newer SDK yet, but it'd be a nice thing to see added once its available.
What is the behavior that isn't addressed by the existing API?
There's seemingly no way to tell a 5.5W and 11W motor apart at runtime.
OPTIONAL Describe any solutions you've considered
Once the partner SDK has the new functionality a Motor::get_type getter would do the trick.
Additional context
VEXCode's getter:
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As of the new vexos 1.1.3 release, it seems like motors can now report their type (5.5W vs 11W) to the brain and be read by the SDK. I'm not sure if the PROS team has access to the newer SDK yet, but it'd be a nice thing to see added once its available.
What is the behavior that isn't addressed by the existing API?
There's seemingly no way to tell a 5.5W and 11W motor apart at runtime.
OPTIONAL Describe any solutions you've considered
Once the partner SDK has the new functionality a
Motor::get_type
getter would do the trick.Additional context
VEXCode's getter:
The text was updated successfully, but these errors were encountered: