Network API - Revision history

Matlo at 19:49, 28 August 2019

2019-08-28T19:49:27Z

2018-10-25T20:48:54Z

‎Send report

2018-10-24T22:16:09Z

‎Send report

2018-10-24T21:51:16Z

‎Send report

2018-10-24T21:29:10Z

‎Send report

2018-07-11T06:00:57Z

‎Send report

2018-06-19T15:42:02Z

‎Send report

2018-06-19T15:40:59Z

‎Send report

2018-02-04T12:10:14Z

‎Send report

2018-02-04T09:35:55Z

‎Send report

@@ Line 109: / Line 109: @@
 *  127   = 0x0000007f => value = 0x00, 0x00, 0x00, 0x7f
 *  32767 = 0x00007fff => value = 0x00, 0x00, 0x7f, 0xff
 =Protocol for versions up to 6.11=

@@ Line 94: / Line 94: @@
 |}
 |-
-| 3-6 || axis value (unsigned 32-bit integer, network byte order)
+| 3-6 || axis value (network byte order, see below)
 |-
 | ... || repeat 2 and 3-6 for each axis to update

@@ Line 102: / Line 102: @@
 To compute the axis value, take the int value stored as two's complement, and store it using the network byte order, which is big endian.<br />
 Examples:
-* -32767 = 0xffff8001 => value = 0x01, 0x80, 0xff, 0xff,
+* -32767 = 0xffff8001 => value = 0xff, 0xff, 0x80, 0x01
-* -127   = 0xffffff81 => value = 0x81, 0xff, 0xff, 0xff
+* -127   = 0xffffff81 => value = 0xff, 0xff, 0xff, 0x81
 * -1     = 0xffffffff => value = 0xff, 0xff, 0xff, 0xff
 *  0     = 0x00000000 => value = 0x00, 0x00, 0x00, 0x00
-*  1     = 0x00000001 => value = 0x01, 0x00, 0x00, 0x00
+*  1     = 0x00000001 => value = 0x00, 0x00, 0x00, 0x01
-*  127   = 0x0000007f => value = 0x7f, 0x00, 0x00, 0x00
+*  127   = 0x0000007f => value = 0x00, 0x00, 0x00, 0x7f
-*  32767 = 0x00007fff => value = 0xff, 0x7f, 0x00, 0x00
+*  32767 = 0x00007fff => value = 0x00, 0x00, 0x7f, 0xff
 =Protocol for versions up to 6.11=

@@ Line 102: / Line 102: @@
 To compute the axis value, take the int value stored as two's complement, and store it using the network byte order, which is big endian.<br />
 Examples:
-* -32767 = 0x0180ffff => value = 0xff, 0xff, 0x80, 0x01
+* -32767 = 0xffff8001 => value = 0x01, 0x80, 0xff, 0xff,
-* -127   = 0x81ffffff => value = 0xff, 0xff, 0xff, 0x81
+* -127   = 0xffffff81 => value = 0x81, 0xff, 0xff, 0xff
 * -1     = 0xffffffff => value = 0xff, 0xff, 0xff, 0xff
 *  0     = 0x00000000 => value = 0x00, 0x00, 0x00, 0x00
 *  1     = 0x00000001 => value = 0x01, 0x00, 0x00, 0x00
 *  127   = 0x0000007f => value = 0x7f, 0x00, 0x00, 0x00
-*  32767 = 0xff7f0000 => value = 0x00, 0x00, 0x7f, 0xff
+*  32767 = 0x00007fff => value = 0xff, 0x7f, 0x00, 0x00
 =Protocol for versions up to 6.11=

@@ Line 102: / Line 102: @@
 To compute the axis value, take the int value stored as two's complement, and store it using the network byte order, which is big endian.<br />
 Examples:
 *  0     = 0x00000000 => value = 0x00, 0x00, 0x00, 0x00
 *  1     = 0x00000001 => value = 0x01, 0x00, 0x00, 0x00
 *  127   = 0x0000007f => value = 0x7f, 0x00, 0x00, 0x00
 *  32767 = 0xff7f0000 => value = 0x00, 0x00, 0x7f, 0xff
 =Protocol for versions up to 6.11=

@@ Line 66: / Line 66: @@
 Use this request to update the axes of the remote GIMX instance.<br >
 The [[Controller_Maps|Controller Maps]] page describes the axes and the value ranges corresponding to each controller type.
@@ Line 81: / Line 80: @@
 | 2 ||
 {| class="wikitable" style="text-align: center;"
-|width="90"|bit 7
+|bit 7
-|width="60"|bit 6
+|bit 6
-|width="60"|bit 5
+|bit 5
-|width="60"|bit 4
+|bit 4
-|width="60"|bit 3
+|bit 3
-|width="60"|bit 2
+|bit 2
-|width="60"|bit 1
+|bit 1
-|width="60"|bit 0
+|bit 0
 |-
 |0 for rel_axis<br />
 for abs_axis
-|colspan="7"|axis index<br />e.g. 0 for abs_axis_0 or for rel_axis_0
+|colspan="7"|axis index<br />X for abs_axis_X or rel_axis_X
 |}
 |-
-| 3-6 || axis value
+| 3-6 || axis value (unsigned 32-bit integer, network byte order)
 |-
 | ... || repeat 2 and 3-6 for each axis to update

@@ Line 65: / Line 65: @@
 ==Send report==
-All axes are unsigned 32-bit integers (network byte order).
+Use this request to update the axes of the remote GIMX instance.<br >
+All axes are unsigned 32-bit integers (network byte order).<br />
 The [[Controller_Maps|Controller Maps]] page describes the axes and the value ranges corresponding to each controller type.