C
ONFIGURATION
C
OMMAND
S
ET
- F
IRMWARE
R
EVISION
2.4.0_
BETA
-
V
ERSION
1.0.0
3.2.25.1.1.4 IO (IO states and events)
3.2.25.1.1.4.1
IO.Motion (Motion states and events)
STATES
-
are checked every second
State notification code
Meaning
IO.Motion.sStanding
True when the device detects that device is standing for longer than 5 seconds, exactly when
the motion of device is less than the <
> value. This state is
parameter configuration dependant. See also section
IO.Motion.sMoving
True when the device is moving for longer than 5 seconds, exactly when the motion of device
is greater than the <
> value. This state is
, page
EVENTS
-
are evaluated just when the event occurs
Event notification code Meaning
IO.Motion.eStanding
Occurs when the device is standing for longer than 5 seconds. This event is
configuration dependant. Counting starts when the motion is less than the
specified value on the <
> entry.
IO.Motion.eMoving
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)
configuration dependant . Counting starts when the motion is greater than the specified value
on the <
> entry. See also section
, page
Table 26:
Motion states and events.
3.2.25.1.1.4.2
IO.BTN (Button states and events)
STATES
-
are checked every second
State notification code
Meaning
IO.BTN.sID=<
id
>
It can be used to identify the device (MAMBOII, Keyfob or Headset) that
caused a specific
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 -
as reference.
<
id
>
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 (
because
more than
one Keyfob may be in use, combine this state with an event below to identify
the button of one Keybob that is pressed)
.
100
= The sender of the event was MAMBOII
200
= The sender of the event was Bluetooth Audio Headset.
EVENTS
-
are evaluated just when the event occurs
Event notification code
Meaning
IO.BTN.e<
index
>=short
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.
IO.BTN.e<
index
>=long
Occurs when the Button <
index
> is pressed and after 2 seconds released.
Example:
IO.BTN.sID=1
&
IO.BTN.e2=long
IO.BTN.e<
index
>=double
Occurs when the Button <
index
> is double pressed within 500 milliseconds.
<
index
>
Identifies which button the user pressed. See also chapter
. You can use the
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 (
combine these events
with the state above to identify the device at the time of the event)
.
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.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 220 of 271
