C
ONFIGURATION
C
OMMAND
S
ET
- F
IRMWARE
R
EVISION
2.4.0_
BETA
-
V
ERSION
1.0.0
Comment
System triggers can be used as an option to enable or disable the execution of various alarms. It is
possible to define a Trigger as e.g. “control mode”, which allows you to simply change the system
behaviour by setting this trigger to high or low state. To load the saved state of a trigger, use the first alarm
configuratin. The storage index 2 is used to store the value of trigger 0. Whenever the device is started
again form a sleep mode, the Trigger0 loads the stored value from storage 2.
To store the state of the current Trigger use alarm AL1 (i.e. when using eShutdown event) or via PFAL
input message (i.e. sent the input message via SMS or TCP packet to the device).
Note:
Please, prevent saving of states or configurations periodically (in a short period) as the number of
configuration updates is restricted to several 100000 operations after which the device has to be replaced.
6.11.3.3 Counter
6.11.3.3.1 Limit the number of automatically sent SMS
Example
$PFAL,Sys.Counter0.set=25;Sys.Counter0.save1
AL0=Sys.Device.eStart:Sys.Counter0=load1
AL1=GSM.SMS.eSent:Sys.Counter0.Decrement=1
AL2=GSM.SMS.eIncoming.Number=“+491234567“
&
GSM.SMS.eIncoming.Text=“req.pos“
&
Sys.Counter.s0
>0:GSM.SMS.Send,“+491234567“,8,“requested position:“
Comment
In order to configure the MAMBOII device to set up a limited number of SMS reporting messages, firstly
send the PFAL commands to the device). The PFAL command consists of two commands, which are sent
to the device at once. The first command sets the maximum value of the used counter, and the next one
stores this counter into the storage 1. Thereafter, configure two alarms AL0 and AL1: Whenever the device
starts up, the AL0 loads the counter 0 with the contents of the storage 1 (the stored counter state).
Whenever the MAMBOII device delivers a SMS, the AL1 decrement the current value of counter 0 by 1.
System counters do not automatically increment or decrement itself, to reach an assumed value of a
counter, an alarm that decrements/increments the used counter should be each time called until the counter
reaches the assumed value (it also depends on the set value of the counter).
After the AL0 and AL1 are sent to the device, now simply declare a new alarm (AL2) to control the events of
incoming SMS and the state of counter 0. Each time (limited to 25) the MAMBOII device receives a SMS
including the text “req.pos” from the mobile number “+491234567”, it responds a SMS message to the
sender including the text “
requested position
:“ and the RMC protocol. After the value of the counter 0 is less
then 1, the MAMBOII stops SMS responses even if the MAMBOII will receive such messages from the
“+491234567” phone number. To continue SMS responses, the value of the used counter must be changed
and its state must be saved, too.
6.11.3.4 Actions based on distance
6.11.3.4.1 Report a position each 1000 metres via SMS
Example
AL0=GPS.Nav.Position.s0>=1000:GPS.Nav.Position0=current
&
GSM.SMS.Send,“+491234567“,8,“current
position:“
Comment
If the current position of the MAMBOII is at least 1000 metres away from position 0 THEN store the current
position of the device into position 0 AND send a SMS including the text “current position:“ and the current
position to the “+491234567“ phone number.
6.11.3.5 History for combined conditions
Please, refer to the basic history examples too.
Combining of conditions to define complex history behaviour is quite easy. Basically,
each condition can be used to store an entry record inside the history.
In combination with Geofence zones, the History entries can be even reduced to
several areas under certain conditions.
Currently up to 5 different conditions can be combined using the logical ‚AND‘ to
specify under which conditions the system should write a history entry.
To combine conditions with logical ‚OR‘ simply a new alarm can be used.
This confidential document is a property of FALCOM and may not be copied or circulated without previous permission.
Page 266 of 271
