9 AUTHORIZED DRIVING CHANGES (NEW IN 31.03.00) ........................................................... 8
10 IMPORTANT NOTES ........................................................................................................................ 8
11 CUSTOM SCENARIO (UPDATED IN 31.03.00) ............................................................................ 8
11.1 CUSTOM SCENARIOS CAN BE ENABLED TO: ................................................................................. 10 ALL THREE SCENARIOS CAN BE ACTIVE AT THE SAME TIME. ..................................................................... 10 11.2 CUSTOM SCENARIOS SOURCES .................................................................................................... 10 11.3 INDEPENDED CUSTOM SCENARIO SMS EVENT ............................................................................ 11 11.4 OPERATIONAL LOGIC .................................................................................................................. 11
11.4.1 Custom for DOUT1 .......................................................................................................... 11 11.4.2 Custom for DOUT2 .......................................................................................................... 11
11.4.3 Custom for Eventual ......................................................................................................... 11 11.4.4 Examples .......................................................................................................................... 11 11.4.5 SMS Configuration Multiple Params (NEW in 31.03.00) ................................................ 12
12 AIN FUEL LEAK FUNCTIONALITY ........................................................................................... 12
12.1 CONFIGURATION ID .................................................................................................................... 13 12.2 EVENT ........................................................................................................................................ 13 12.3 CONFIGURATION VIA SMS.......................................................................................................... 14
13 REVISION HISTORY ...................................................................................................................... 14
1 AssistNow Online and AssistNow Autonomous
1.1 Configuration via configurator
Assisted GPS configuration can be found in Features->Assisted GPS (figure 1). Three modes can be selected:
None. This mode will disable A-GPS functionality;
AssistNow Autonomous. This mode will enable AssistNow Autonomous functionality and will configure U-Blox module to work in this mode. No need for additional configuration parameters;
AssistNow Online. This mode will enable AssitNow Online functionality. Additional configuration parameters are needed for assist data request from remote server:
o Server name. A domain name or IP address of the remote server from which assist data will be received. Default value agps.u-blox.com.
o Server port. A port number the remote server from which assists data will be received. Default value 46434.
o Login. A user name. If using default server (agps.u-blox.com), this must be a valid Email Address, as important server maintenance messages will be sent to this address.
o Password. If using default server (agps.u-blox.com), passwords are assigned by u-blox and are only valid for a given Email address.
Note: To apply for a free u-blox Assist Now account, please send an e-mail to: agps-
Server name 211 Domain name has to be shorter than 50 symbols.
Server port 212 Port number has to be in the range [0-65535].
Login 213 Login name has to be shorter than 30 symbols
Password 214 Login name has to be shorter than 30 symbols
1.3 AssistNow Online implementation in FM1200
AssistNow Online data purpose is to provide GPS receiver with satellites data. Before
FM1200 can request for AssistNow Online data it must know an approximate position
(latitude and longitude). Online data in FM1200 is requested on 3 situations:
FM1200 was restarted by software or by cutting power supply off for a short time of
period (back up information is still valid in Battery Ram of FM’s microcontroller). In
this situation, if FM1200 had a GPS Fix before restart it will have last position saved on
Battery Ram and will use it for AssistNow Online data request. In this case it can take
some time getting AssistNow Online data because GSM modem has to initialize, connect
to GSM tower and make GPRS context. In other case if power supply for FM1200 was
off for a longer time period (more than ~ 10 s) there will be no valid coordinates in
Battery Ram and GPS module will have to start from Cold Start (Assist Online data will
be unavailable).
FM1200 woke up from Deep Sleep. In this case FM1200 calculates GPS OFF duration
during Deep Sleep. If GPS receiver was OFF less than 3 hours it most likely will start
from Hot Start because satellites information saved in GPS receivers Battery Ram are
still valid so AssistNow Online data will not be requested instantaneously. But FM1200
monitors GPS Fix status for 60 s. If GPS receiver doesn’t have Fix after 60 s it initiate
AssistNow Online data request.
If GPS receiver was OFF more than 3 hours it most likely start from Warm Start
meaning that acquisition data in GPS receiver will be not valid, so AssistNow Online
data will be requested instantaneously.
After Deep Sleep it can take some time getting AssistNow Online data because GSM
modem was OFF, so it has to initialize, connect to GSM tower and make GPRS context.
FM1200 woke up from Sleep (GPS receiver OFF mode). If GPS receiver was OFF less
than 3 hours it most likely will start from Hot Start because satellites information saved
in GPS receivers Battery Ram are still valid so AssistNow Online data will not be
requested instantaneously. But FM1200 monitors GPS Fix status for 60 s. If GPS
receiver doesn’t have Fix after 60 s it initiate AssistNow Online data request.
If GPS receiver was OFF more than 3 hours it most likely start from Warm Start
meaning that acquisition data in GPS receiver will be not valid, so AssistNow Online
data will be requested instantaneously.
After FM1200 Sleep getting AssistNow Online data will be a lot faster than in first two
cases.
1.4 AssistNow Autonomous implementation in FM1200
When AssistNow Autonomous functionality is selected in configuration, FM1200 configures u-blox GPS receiver to work in this mode.
The AssistNow Autonomous orbit is an extension of a broadcast ephemeris. It provides a long-term orbit for the satellite for several revolutions. Although this orbit is not perfectly precise it is a sufficiently accurate representation of the true orbit to be used for navigation.
The AssistNow Autonomous data is automatically and autonomously generated from downloaded ephemerides. Data for approximately twenty satellites are stored automatically in the on-chip battery backup RAM.
The operation of the AssistNow Autonomous feature is transparent to the user and the operation of the receiver. All calculations are done in background and do not affect the normal operation of the receiver.
The AssistNow Autonomous subsystem automatically invalidates data that has become too old and that would introduce unacceptable positioning errors.
The calculations required for AssistNow Autonomous are carried out on the receiver. This requires energy and users may therefore occasionally see increased power consumption during short periods (several seconds, rarely more than 60 seconds) when such calculations are running.
FM1200 delays power-down of GPS receiver (before Sleep or Deep Sleep) until all calculations of AssistNow Autonomous functionality on GPS receiver are done.
More about u-blox AssistNow features read in u-blox 6 Receiver Description Including Protocol Specification.
Note: if power supply for FM1200 was cut off u-blox receiver will lost all AssistNow Autonomous calculation data and will start from Cold Start.
AssistNow do not work with other GPS modules except u-blox.
2 GPRS Commands Description It is possible to send commands to FM1200 using GPRS. When FM1200 sends records
periodically to a server, a message could be sent from the server and FM1200 will reply to it.
FM1200 has to be connected to the server in order to receive commands.
Command Description
#GET DATAORDER Get info about records sorting parameter
#SET DATAORDER=X Set records sorting parameter, X – value (0/1).
#GET RECTO Get info about records refresh timeout parameter
#SET RECTO=X Set records refresh parameter, X = records refresh timeout
#GET VERSION Receive firmware version
#GET NETWORK Get GSM operator to which device is connected
#GET IMSI Get IMSI of the device
#GET OUT Get DOUT values
#SET OUT=X,Y X – DOUT1 State, Y – DOUT2 State
#DO REPORT Save a record
#DO RESET=XXX Reset FM1200 or GPS module, XXX – FM12 or GPS
#GET ROAMING=Y Get operator from the list, Y – operator number in a list
#SET ROAMING=Y,”Z” Set operator to the list: Y – operator number in a list, Z – operator code
#GET REMIP Get IP and port number from the configuration of a certain profile
#SET REMIP=Y:Z Set IP and port number to the configuration, Y – IP or domain, Z – port number
#GET AUP Get APN, user login and password from the configuration
#SET AUP=”Y”,”Z”,”W” Set APN, user login and password to the configuration,Y – APN, Z –, user login W – password. PAramters must be eneterd between quoutes
#GET REPRTX Get MinPeriod from the configuration, X – mode
#SET REPRTX=Y Set MinPeriod to the configuration, X – mode, Y – MinPeriod value
#GET REPDISTX Get MinDistance from the configuration, X – mode (1,3,5 available)
#SET REPDISTX=Y Set MinDistance to the configuration, X – mode (1,3,5 available), Y – MinDistance value
#GET REPANGX Get MinAngle from the configuration, X – mode (1,3,5 available)
#SET REPANGX=Y Set MinAngle to the configuration, X – mode (1,3,5 available), Y – MinAngle value
#GET SENDPERIODX Get SendPeriod from the configuration, X – mode
#SET SENDPERIODX=Y Set SendPeriod to the configuration of, X – mode, Y – SendPeriod value
#GET REPMRX Get MinRecords from the configuration, X – mode
#SET REPMRX=Y Set MinRecords to the configuration, X – mode, Y – MinRecords value
#GET IBTN Get iButton IO element (Enabled/Disabled) configuration value
#SET IBTN=Y Set iButton IO element Y – 0/1
#GET EXTERR Get extended errors value
#SET EXTERR=X Set extended errors value, X – 0/1
3 Loading default configuration using SMS SMS with body “format” is used to load default configuration into device.
Note! After SMS is received FM1200 is restarted for proper reconfiguration. Restart is
performed after 10 seconds in order to send response SMS.
Default configuration can be created using FM12 configuration as usual but pressing “Save
Spec Default profile” button instead of “Save”. Device will load default configuration after
receiving described SMS.
4 Google Link request SMS Google link request SMS “getgpslink” added. The response to SMS is following:
All active GPS parameters are inserted in corresponding brackets.
PANIC! Digital Input 1 Event at 2012/06/13 HH:MM:SS [X] [Y]
HH – hour MM – minutes SS – seconds [X] – Latitude [Y] – Longitude If SMS event number index is 0 -> SMS will be sent to all configured numbers.
6 Scenarios DOUT1 changes DOUT1 is not controlled by Eco Driving. It is controlled by Jamming or OverSpeeding
Scenario. Eco Driving can work in parallel with OverSpeeding Scenario. Jamming Scenario can work in parallel with Eco Driving but not with OverSpeeding. Jamming Scenario event is saved on JAMMING END (Event ID:249, value:0, LOW
priority). SMS example if Jamming is configured to send SMS on Event: „LOW! Jamming Ended at 2012/11/16 6:16:36 546995904 252619632” DOUT1 setting over SMS/GPRS is not allowed if any of Eco Driving, OverSpeeding
or Jamming Scenario is enabled. Configuration values via SMS “setparam 1600“: Table 1 DOUT1 Scenarios
7 Stop Detection Timeout Parameter name Parameter ID Available values
Stop Detection Timeout 215 Min Value – 0 seconds
Max Value – 600 seconds
Default Value – 0 seconds
Stop Detection Timeout Depends on Stop Detection Source parameter.
For example:
Stop Detection Source is Ignition & Stop Detection Timeout is 30 seconds. Mode will change from Moving to Stop after Ignition is off for 30 seconds.
Debug Log: [Mode.Change]->Timeout is active: 30 …….. [Mode.Change]->Timeout is active: 20 Sleep & Deep Sleep depends on Stop Detection Timeout timeout too. Only after timeout is reached & no ignition/movement is detetcted Sleep timeout takes part.
8 Immobilizer changes Immobilizer Event is not saved in this spec FW version. But SMS Event can be configured and will be sent to configured numbers.
9 Authorized Driving changes (NEW in 31.03.00) Immobilizer Event is not saved in this spec FW version. But SMS Event can be configured and will be sent to configured numbers.
10 Important notes
Jamming functionality works with TM11Q_T_02.XX.XX, TM11Q_R_01.XX.06 or higher modem versions.
11 Custom Scenario (Updated in 31.03.00) In order to allow all 3 custom scenarios be active at the same time configuration is
different from 31.02.xx version. After FW Updated These values must be
All three scenarios can be active at the same time.
a) Control OUT1
b) Control OUT2
c) Generate event with ID: 248
11.2 Custom scenarios sources
Custom Scenario Configurable parameters ID
Custom Scenarios DOUT1
Control
Event Source 1 Configuration ID: 1665
Event Source 2 Configuration ID: 1666
Event Source 3 Configuration ID: 1667
Priority Configuration ID: 1668
AVG Constant Configuration ID: 1669
Custom Scenarios DOUT2
Control
Event Source 1 Configuration ID: 1725
Event Source 2 Configuration ID: 1726
Event Source 3 Configuration ID: 1727
Priority Configuration ID: 1728
AVG Constant Configuration ID: 1729
Independed Custom Scenario
Event Source 1 Configuration ID: 1606
Event Source 2 Configuration ID: 1607
Event Source 3 Configuration ID: 1608
Priority Configuration ID: 1609
AVG Constant Configuration ID: 1660
Index:0 is for DIN1
Index:20 is for Dallas temperature
Index:-1 is for DIN2 but this is ignored.
11.3 Independed Custom scenario SMS event
Custom scenario index for SMS event is 37 Only in depended Custom Scenario can be configured to Send SMS.
11.4 Operational logic
Selected IO element for “Custom scenario source” must be enabled in the IO table.
When element value is
IO Low Level <= Actual IO value <= IO High Level
It is considered to be in range.
For custom scenario to work all 3 sources must be “in range”.
If “ignore” is selected for algorithm configured IO value is always “in range”.
11.4.1 Custom for DOUT1
Out range => DOUT1=OFF
In range => DOUT1=ON
Averaging constants affects lock/unlock time when all conditions all met
Priority will propagate to DOUT1 IO element so this element must be enabled for event with required priority to be generated.
11.4.2 Custom for DOUT2
Out range => DOUT2=OFF
In range => DOUT2=ON
Averaging constants affects lock/unlock time when all conditions all met
Priority will propagate to DOUT1 IO element so this element must be enabled for event with required priority to be generated.
11.4.3 Custom for Eventual
Generated event ID: 248 Priority is configurable with configuration ID: 1609 Averaging constant is configurable with configuration ID:1660 Min: 1; Max: 1000. Units seconds.
In range => Out range => Eventual record with ID:248:Value:0
Out range => In range => Eventual record with ID:248:Value:1
11.4.4 Examples
11.4.4.1 Custom Scenario is enabled for OUT1.
1. Event source is 0. Low Level 1, High Level 1
2. Event source is -1 3. Event source is -1
If DIN1=1 => DOUT1=ON If DIN1=0 => DOUT1=OFF
11.4.4.2 Custom Scenario is enabled for Event.
1. Event source is 0. Low Level 1, High Level 1 2. Event source is 3. Low Level 14000, High Level 16000 3. Event source is 1. Low Level 0, High Level 0
Actual values: DIN1=0; DIN2=0, AIN1= 12V. Device startup: No event. Actual values: DIN1=1; DIN2=0, AIN1= 12V. No event. Actual values: DIN1=1; DIN2=0, AIN1= 15V. Event.248 Value:1 Actual values: DIN1=0; DIN2=0, AIN1= 15V. Event. ID:248 Value:0
11.4.5 SMS Configuration Multiple Params (NEW in 31.03.00)
Event Sources for Custom Scenarios can be configured via single SMS.
