-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define a new Servo 2.0 interface that is decoupled from AnalogWrite #78
Comments
I would like to see multiServo that allows me to pass a position for each member in a group of servos in a single message (see multiStepper). |
It just occurred to me that I think |
Also worth noting that not all servos are 180 degrees so you'd have to be able to pass in the physical range of the servo as part of a configuration command in firmata. If that happens, I want to be able to specify radians as a configuration option because radians are better than degrees for IK work. Having to convert back and forth slows things down. |
I would suggest to add an optional feature ID for servo usage, SERVO_OPERATION for example. Like what I2C_REQUEST having done, the existing servo interface servoWrite(pin, degree) would be one mode of it. However, servoWrite() function can only make servo move as we requesting, we also need to know the state of servo in some cases. So, I think it would be nice to add servoRead() function, which would be one mode of SERVO_OPERATION as well. |
The current Servo interface uses the Firmata Analog message to set it's value. This creates tight coupling between ServoFirmata and AnalogWrite and AnalogOutputFirmata.
We need a new Servo interface that uses Sysex. Does anyone have an opinion on changes to the existing firmata servo interface?
The text was updated successfully, but these errors were encountered: