Io (Io States And Events); Io.motion (Motion States And Events); Io.btn (Button States And Events) - FALCOM MAMBOII User Manual

C C
ONFIGURATION OMMAND

3.2.25.1.1.4 IO (IO states and events)

3.2.25.1.1.4.1
STATES-are checked every second
State notification code
IO.Motion.sStanding
IO.Motion.sMoving
EVENTS-are evaluated just when the event occurs
Event notification code Meaning
IO.Motion.eStanding
IO.Motion.eMoving
3.2.25.1.1.4.2
STATES-are checked every second
State notification code
IO.BTN.sID=<id>
<id>
EVENTS-are evaluated just when the event occurs
Event notification code
IO.BTN.e<index>=short
IO.BTN.e<index>=long
IO.BTN.e<index>=double
<index>
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
S - F R
ET IRMWARE

IO.Motion (Motion states and events)

Meaning
True when the device detects that device is standing for longer than 5 seconds, exactly when
the motion of device is less than the <min_abs> value. This state is
parameter configuration dependant. See also section 3.2.16.1, page
True when the device is moving for longer than 5 seconds, exactly when the motion of device
is greater than the <min_abs> value. This state is
dependant. See also section 3.2.16.1, page
Occurs when the device is standing for longer than 5 seconds. This event is
MOTION.FILTER configuration dependant. Counting starts when the motion is less than the
specified value on the <min_abs> entry.
Event that occurs when the device is moving for longer than 5 seconds (attempts to move it
in any direction, either up or down, or left or right). This event is
configuration dependant . Counting starts when the motion is greater than the specified value
on the <min_abs> entry. See also section 3.2.16.1, page 171.
Table 26: Motion states and events.

IO.BTN (Button states and events)

Meaning
It can be used to identify the device (MAMBOII, Keyfob or Headset) that
button event. It is typically needed only when you are using more than one Keyfob. In such
cases, this identifier (state) can then be used with a button-event to determine the sender of
the event.
Example: IO.BTN.sID=0&IO.BTN.e0=short -
Identifies which device caused a specific button event. It is used as a device identifier at the
time of the event.
0 .. 99 = The sender of the event was Keyfob 0,1, 2 ... and so on
one Keyfob may be in use, combine this state with an event below to identify
the button of one Keybob that is
100 = The sender of the event was MAMBOII
200 = The sender of the event was Bluetooth Audio Headset.
Meaning
Occurs when Button <index> is pressed and within 2 seconds released. In the following
example, an application accepts a short-press event occurred from the button 1 only if it
comes from the Keyfob 1.
Occurs when the Button <index> is pressed and after 2 seconds released.
Example: IO.BTN.sID=1&IO.BTN.e2=long
Occurs when the Button <index> is double pressed within 500 milliseconds.
Identifies which button the user pressed. See also chapter
following index to identify which button was pressed.
0, 1 =MAMBOII's left or right button is pressed respectively.
2, 3, 4 = Corresponding button (1,2 or 3) on the Keyfob is pressed
with the state above to identify the device at the time of the
5 = Call button on the Bluetooth Audio Headset is pressed (supports just short press).
X = Any button is pressed.
Table 27: Button states and events.
2.4.0_ -
EVISION BETA
MOTION.FILTER
171
See chapter
pressed).
V 1.0.0
ERSION
MOTION.FILTER
171
parameter configuration
MOTION.FILTER
caused a specific
4.3 as reference.
(because more than
6.10 page 262. You can use the
(combine these events
event).
Page 220 of 271