Difference between revisions of "Connect-165 OSC Input"
| Line 18: | Line 18: | ||
|} | |} | ||
| − | + | Example: | |
| + | |||
| + | "/USB-microDig_0123/Output_01 64" will set an actuator output configured for a PWM actuator to output a pulse with a width that's half of the configured range, so in case of the default PWM configuration (ie. 1 ms range, from 1 to 2 ms) that would be 1.5 ms. | ||
Sending the same message while the actuator output is configured for an I2C actuator will set the actuator method of the I2C actuator to 64. | Sending the same message while the actuator output is configured for an I2C actuator will set the actuator method of the I2C actuator to 64. | ||
Revision as of 21:37, 8 March 2022
If the OSC messages match (case insensitive) the format /<digitizer_name>/<output_name> <set_value>, where digitizer_name is the name of a connected digitizer, and set_value is in {.. -128, 0 .. 127, 128 .. }, the set_value will be mapped to a SET OUTPUT message (see the firmware pages).
The following OSC messages can be sent:
| set_value of OSC Message | Action |
| 0 .. 127 | enable and set pulse width modulation (if implemented) or set the I2C actuator method as per OSC message value |
| -128 (or less) or "off" (case insensitive) | turn output off |
| 128 (or more) or "on" (case insensitive) | turn output on |
Example:
"/USB-microDig_0123/Output_01 64" will set an actuator output configured for a PWM actuator to output a pulse with a width that's half of the configured range, so in case of the default PWM configuration (ie. 1 ms range, from 1 to 2 ms) that would be 1.5 ms.
Sending the same message while the actuator output is configured for an I2C actuator will set the actuator method of the I2C actuator to 64.
