EXAMPLE 1 |
||
Send an SMS message when they change latitude or longitude, saving the current value in memory variables every minute and comparing it with the current value. We can also give memory variables a meaningful name: V10=lat MEMORY VARIABLE NAME 1 = lat V20=lon MEMORY VARIABLE NAME 2 = lon |
||
|
|
SCH**** SCHEDULED AT **:** |
|
$G01!$V11 LATITUDE ! MEMORY VARIABLE 1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
lat=$G01 |
|
|
AT+SMS=police,"$D01 location: $G01 $G02" |
|
|
|
|
|
|
|
|
|
|
TRIGGER EVENT occurs every minute (****). The first condition to check is that the current latitude value is different from the content of variable 1. The first action stores the current latitude in variable memory expression 1, equivalent to V21=$G01 or var1=$G01. The second action contains the command that sends an SMS message to all users belonging to the police group reporting the device name ($D01) followed by the text "location" and the geographic coordinates ($G01 latitude and $G02 longitude). |
|
|
SCH**** SCHEDULED AT **:** |
|
$G02!$V21 LONGITUDE ! MEMORY VARIABLE 2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
lon=$G02 |
|
|
AT+SMS=police,"$D01 location: $G01 $G02" |
|
|
|
|
|
|
|
|
|
|
TRIGGER EVENT occurs every minute (****). The first condition to check is that the current longitude value is different from the content of variable 2. The first action stores the current longitude in variable memory expression 2, equivalent to V22=$G02 or var2=$G02. The second action contains the command that sends an SMS message to all users belonging to the police group reporting the device name ($D01) followed by the text "location" and the geographic coordinates ($G01 latitude and $G02 longitude). |
EXAMPLE 2 |
||
With GNSS we check every minute if the positioning is valid (parameter G14) and the geographic coordinates, sending them to the server if they have changed. As in the previous example we do this by saving the current value in memory variables and then comparing it with the current value. We can also give memory variables a meaningful name: V10=lat MEMORY VARIABLE NAME 1 = lat V20=lon MEMORY VARIABLE NAME 2 = lon |
||
|
|
SCH**** SCHEDULED AT **:** |
|
$G01!$V11 LATITUDE ! MEMORY VARIABLE 1 |
|
|
$G14>0 HDOP > 0 |
|
|
|
|
|
|
|
|
|
|
|
lat=$G01 |
|
|
AT#SMAP=G01,G02 |
|
|
|
|
|
|
|
|
|
|
TRIGGER EVENT occurs every minute (****). The first condition to check is that the current latitude value is different from the content of variable 1. The second condition to check is that the value of parameter G14 (HDOP) is greater than zero, that is, the GNSS has obtained a valid position. The first action stores the current latitude in variable memory expression 1, equivalent to V21=$G01 or var1=$G01. The second aCTION contains the command that updates the parameters G01 (latitude) and G02 (longitude) on the SMM Server. |
|
|
SCH**** ORA SPECIFICA **:** |
|
$G02!$V21 LONGITUDE ! MEMORY VARIABLE 22 |
|
|
$G14>0 HDOP > 0 |
|
|
|
|
|
|
|
|
|
|
|
lon=$G02 |
|
|
AT#SMAP=G01,G02 |
|
|
|
|
|
|
|
|
|
|
TRIGGER EVENT occurs every minute (****). The first condition to check is that the current longitude value is different from the content of variable 2. The second condition to check is that the value of parameter G14 (HDOP) is greater than zero, that is, the GNSS has obtained a valid position. The second condition to check is that the value of parameter G14 (HDOP) is greater than zero, that is, the GNSS has obtained a valid position. The first action stores the current longitude in variable memory expression 2, equivalent to V22=$G02 or var2=$G02. The second aCTION contains the command that updates the parameters G01 (latitude) and G02 (longitude) on the SMM Server. |