C
ONFIGURATION
C
OMMAND
S
ET
- F
IRMWARE
R
EVISION
2.4.0_
BETA
-
V
ERSION
1.0.0
The
GF3
belongs to the three areas
GF.AREA
2
,
GF.AREA
3
and
GF.AREA
4
, so that
the set value of
area
> is a sum of hexadecimal values of
GF.AREA
2
(^=4
),
GF.AREA
3
(^=8
)
and
GF.AREA
4
(^=10) corresponding to
area
1C
.
The
GF4
belongs to thefour areas
GF.AREA
1
,
GF.AREA
2
,
GF.AREA
3
and
GF.AREA
4
,
so that the set value of
area
> is a sum of hexadecimal values of
GF.AREA
1
(^=2),
GF.AREA
2
(^=4),
GF.AREA
3
(^=8)
and
GF.AREA
4
(^=10) corresponding to
area
1E
.
The
GF5
belongs to the areas
GF.AREA
1
and
GF.AREA
4
, so that the set value of
area
> is a sum of hexadecimal values of
GF.AREA
1
(^=2)
and
GF.AREA
4
(^=10) corresponding to
area
12
.
Figure 9:
Covering up a driving route using several Geofences allocated in different areas
This is only a classification of areas and Geofences. The areas boundaries
1
to
4
are
outlined in different colours, and their colour is given on the left side of the diagram.
While the device is moving in or out an area or Geofence the corresponding event
of that area and Geofence always are occurred.
However, depending on your application to be implemented only some of
area/GeoFence events can be set as condition to execute actions.
Notes
•
The
GF0
should not be used as a standard Geofence zone, if the parking are
for more details). Based on the user
GF0
is automatically set up and attached to
the
GF.AREA
0
executed.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 205 of 271
