Closed virgilvox closed 9 years ago
Was missing EXTENDED_ANALOG (pin higher than 15) handling.
Pushed a new version, give it another shot.
Excellent! PWM works, but only one channel it seems.
If I'm setting it up to talk to wiring pin 24 and wiring pin 26 I get weirdness.
At first triggering pin 24 makes one of the servos move, trigger pin 26 to 0 makes the same servo stop, but then when i go to press for pin 24 again I get attempt to write to a destroyed prehipheral
SYSEX_REQUEST[EXTENDED_ANALOG] pin 26 value 90
error handling sysex [Error: Attempted to write to a destroyed peripheral]
handled
remote data in <Buffer f0 6f 1a 5a 00 f7> 6
handling sysex <Buffer f0 6f 1a 5a 00 f7> <Buffer 6f 79>
SYSEX_REQUEST[EXTENDED_ANALOG] pin 26 value 90
error handling sysex [Error: Attempted to write to a destroyed peripheral]
handled
remote data in <Buffer f0 6f 18 00 00 f7> 6
handling sysex <Buffer f0 6f 18 00 00 f7> <Buffer 6f 79>
SYSEX_REQUEST[EXTENDED_ANALOG] pin 24 value 0
handled
remote data in <Buffer f0 6f 18 0f 00 f7> 6
handling sysex <Buffer f0 6f 18 0f 00 f7> <Buffer 6f 79>
SYSEX_REQUEST[EXTENDED_ANALOG] pin 24 value 15
handled
remote data in <Buffer f0 6f 18 00 00 f7> 6
handling sysex <Buffer f0 6f 18 00 00 f7> <Buffer 6f 79>
SYSEX_REQUEST[EXTENDED_ANALOG] pin 24 value 0
handled
remote data in <Buffer f0 6f 1a 5a 00 f7> 6
handling sysex <Buffer f0 6f 1a 5a 00 f7> <Buffer 6f 79>
SYSEX_REQUEST[EXTENDED_ANALOG] pin 26 value 90
error handling sysex [Error: Attempted to write to a destroyed peripheral]
handled
Are you setting pinMode at all?
I dont automatically set pin modes, so you might need to manually do it first.
Was a raspi-io issue that has been fixed.
Raspi-io PWM was fixed in latest 2.0.6, tested with basic analogwrite with success, except...
When sending message to servowrite or analogwrite returns this.