Difference between revisions of "Template:FM36YX SMS events"
m (→Configuration) |
m |
||
| Line 22: | Line 22: | ||
High level, with priority High and configured to generate event on both range enter and exit(figure below "IO" section), then the sent SMS is:<br /> | High level, with priority High and configured to generate event on both range enter and exit(figure below "IO" section), then the sent SMS is:<br /> | ||
''“2016/1/20 12:00:00 Digital Input 1”'' | ''“2016/1/20 12:00:00 Digital Input 1”'' | ||
| − | |||
[[File:FM36YX SMS event DIN1.png]] | [[File:FM36YX SMS event DIN1.png]] | ||
| − | |||
The SMS Text field can be altered and any text can be entered. Maximum message length is 90 | The SMS Text field can be altered and any text can be entered. Maximum message length is 90 | ||
| Line 46: | Line 44: | ||
[[File:FM36YX_SMS_event_Scenarios.png]] | [[File:FM36YX_SMS_event_Scenarios.png]] | ||
| − | |||
| − | |||
| − | |||
When any of the scenarios events occurs, a text message will be sent to the predefined number. | When any of the scenarios events occurs, a text message will be sent to the predefined number. | ||
| Line 59: | Line 54: | ||
exceeds the speed in Start Speed (ex. 5 km/h) and when Trip stops, that is ignition is turned off | exceeds the speed in Start Speed (ex. 5 km/h) and when Trip stops, that is ignition is turned off | ||
longer then the time written in Ignition Off Timeout (ex. 60 seconds). | longer then the time written in Ignition Off Timeout (ex. 60 seconds). | ||
| − | |||
[[File:FM36YX_SMS_event_TRIP.png]] | [[File:FM36YX_SMS_event_TRIP.png]] | ||
| − | |||
| − | |||
| − | |||
'''Geofence''' | '''Geofence''' | ||
| Line 73: | Line 64: | ||
events. If several zones are created then SMS events can be turned on separately for each zone | events. If several zones are created then SMS events can be turned on separately for each zone | ||
entering different text message. | entering different text message. | ||
| − | |||
[[File:FM36YX_SMS_event_Geofence.png]] | [[File:FM36YX_SMS_event_Geofence.png]] | ||
| − | |||
| − | |||
| − | |||
'''AutoGeofence''' | '''AutoGeofence''' | ||
| Line 85: | Line 72: | ||
Features -> Auto geofencing (figure 44), for SMS events configuration, go to GSM -> SMS -> SMS | Features -> Auto geofencing (figure 44), for SMS events configuration, go to GSM -> SMS -> SMS | ||
Events (figure 45). | Events (figure 45). | ||
| − | |||
[[File:FM36YX_SMS_event_AutoGeofence.png]] | [[File:FM36YX_SMS_event_AutoGeofence.png]] | ||
| − | |||
| − | |||
'''I/O events''' | '''I/O events''' | ||
| Line 97: | Line 81: | ||
generate event, so SMS event could not be configured). Every IO element SMS event can be | generate event, so SMS event could not be configured). Every IO element SMS event can be | ||
configured to send individual message to different numbers. | configured to send individual message to different numbers. | ||
| − | |||
[[File:FM36YX_SMS_event_I-O_events.png]] | [[File:FM36YX_SMS_event_I-O_events.png]] | ||
Revision as of 12:35, 1 June 2018
SMS events functionality allows FM36YX to send a configured SMS when an event is
triggered. This event can be triggered by:
- Green Driving
- Over Speeding
- Authorized driving
- Immobilizer
- Trip start/stop
- Geofence
- Autogeofence
- I/O event
When any of the above events is triggered, FM36YX sends a configured SMS message to a defined phone number. If SMS events is activated, but there are no numbers defined in SMS events PreDefined Numbers list (figure below), then the device will not send any messages.
The sent SMS messages format is according to:
“Date Time EventText”
For example, if FM36YX is configured to send an SMS (figure below "SMS Events" section), when Digital Input 1 reaches
High level, with priority High and configured to generate event on both range enter and exit(figure below "IO" section), then the sent SMS is:
“2016/1/20 12:00:00 Digital Input 1”
The SMS Text field can be altered and any text can be entered. Maximum message length is 90 symbols (numbers, letters and symbols in ASCII, except for comma “,”).
|
ATTENTION! If FM36YX is in Deep Sleep mode and SMS event occurs with LOW priority (which does not wake up FM36YX), then the device does not send the message. It is saved in device memory until it wakes up from Deep Sleep mode and GSM modem starts working normally. After it wakes up, all the messages that are saved in memory will be sent, but keep in mind that only 10 messages can be saved in memory – all other messages will not be saved, until there is room in device memory. |
Configuration
Scenarios
To configure SMS events for scenarios, open Scenarios window and Enable desired scenario. Then go to GSM ->SMS -> SMS events window and activate SMS event for Enabled scenario. Figure 38 shows how to enable Green Driving and Immobilizer SMS Events.
When any of the scenarios events occurs, a text message will be sent to the predefined number.
TRIP
In order to configure Trip SMS events click on Trip window and Enable Trip feature (figure 40). Then go to GSM -> SMS -> SMS Events settings and Enable Trip SMS event. After enabling SMS Events (figure 41), trip event will be triggered and message sent, when Trip starts (GNSS speed exceeds the speed in Start Speed (ex. 5 km/h) and when Trip stops, that is ignition is turned off longer then the time written in Ignition Off Timeout (ex. 60 seconds).
Geofence
Geofence SMS event is triggered and message sent when the device exits and/or enters a configured Geofence zone. The Geofence zone must be configured to generate an event On Exit, On Enter or On Both (figure 42). If No Event is selected, then it is not possible to turn on SMS events. If several zones are created then SMS events can be turned on separately for each zone entering different text message.
AutoGeofence
SMS events for AutoGeofence are configured the same as in Geofence. AutoGeofence is in Features -> Auto geofencing (figure 44), for SMS events configuration, go to GSM -> SMS -> SMS Events (figure 45).
I/O events
FM3612 sends SMS event message when a configured I/O property enters and/or exits its configured High/Low boundaries or Hysteresis event generation is chosen (Monitoring does not generate event, so SMS event could not be configured). Every IO element SMS event can be configured to send individual message to different numbers.
