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
I am trying to write a MAX MSP program that can read the gyro and acc data over bluetooth.
The program has the ability to make HID and serial connections.
From the documentation it sounds like I can send Subcommand 0x03 to set input report mode
to x30 for Standard full mode over serial. Will this enable the gyro and acc data sending over HID or will it need to be read from serial? Can this be done as a standalone command over serial or do I need the driver code? Trying to make this platform agnostic to avoid wrapping the driver code up for each platform as I can't use code directly in MAX MSP.
When connecting over Bluetooth is the handshake procedure also required (changing the baud rate). Assuming the Bluetooth baud rate is the same as when over pins.
I have read through Issue "HID Protocol for Bluetooth / USB #7" but didn't quite find what I was looking for.
The text was updated successfully, but these errors were encountered:
I am trying to write a MAX MSP program that can read the gyro and acc data over bluetooth.
The program has the ability to make HID and serial connections.
From the documentation it sounds like I can send Subcommand 0x03 to set input report mode
to x30 for Standard full mode over serial. Will this enable the gyro and acc data sending over HID or will it need to be read from serial? Can this be done as a standalone command over serial or do I need the driver code? Trying to make this platform agnostic to avoid wrapping the driver code up for each platform as I can't use code directly in MAX MSP.
When connecting over Bluetooth is the handshake procedure also required (changing the baud rate). Assuming the Bluetooth baud rate is the same as when over pins.
I have read through Issue "HID Protocol for Bluetooth / USB #7" but didn't quite find what I was looking for.
The text was updated successfully, but these errors were encountered: