input/devices/iforce-protocol.rst

7 Home page at `<http://web.archive.org/web/*/http://www.esil.univ-mrs.fr>`_
16 specify force effects to I-Force 2.0 devices.  None of this information comes
25     send data to your I-Force device based on what you read in this document.
30 All values are hexadecimal with big-endian encoding (msb on the left). Beware,
31 values inside packets are encoded using little-endian.  Bytes whose roles are
35 ------------------------
54 First, I describe effects that are sent by the device to the computer
64     00 X-Axis lsb
65     01 X-Axis msb
66     02 Y-Axis lsb, or gas pedal for a wheel
67     03 Y-Axis msb, or brake pedal for a wheel
84     03 Address of parameter block changed (lsb)
86     05 Address of second parameter block changed (lsb)
90 ------------
111 	    Bits 4-7: Val 2 = effect along one axis. Byte 05 indicates direction
115 	    Bits 0-3: Val 0 = No trigger
119     03-04 Duration of effect (little endian encoding, in ms)
123     06-07 Minimum time between triggering.
125     08-09 Address of periodicity or magnitude parameters
126     0a-0b Address of attack and fade parameters, or ffff if none.
128     08-09 Address of interactive parameters for X-axis,
130     0a-0b Address of interactive parameters for Y-axis,
133     0c-0d Delay before execution of effect (little endian encoding, in ms)
137 ---------------------
146     00-01 Address where to store the parameters
147     02-03 Duration of attack (little endian encoding, in ms)
149     05-06 Duration of fade.
159     00-01 Address
169     00-01 Address
173     05-06 Period (little endian encoding, in ms)
176 ----------------------
182     00-01 Address
196 --------
210 ----
300 Sends back 3 bytes - major, minor, subminor
348 ----------------
354  - period : 0c
355  - magnitude : 02
356  - attack and fade : 0e
357  - interactive : 08
370 At first glance, this software seems, hum, well... buggy. In fact, data appear with a
381 I-Force is trademark of Immersion Corp.