ACTIVE TRACKER FM2 G2 MANUALS
INSTALLATION GUIDE
1. PURPOSE
2. REQUIREMENTS
3. SIM CARD INSTALLATION
3.1 SIM CARD INSTALLATION
3.2 INTERNAL BATTERY CONNECTION
3.3 CLOSE THE HOUSING
4. DEVICE INSTALLATION
4.1 CORRECT ORIENTATION AND INSTALLATION
4.2 MOUNTING RECOMMENDATIONS
4.2. 1 CONNECTING WIRES
4.2. 2 CONNECTING POWER SOURCE
4.2. 3 CONNECTING IGNITION WIRE
4.2. 4 CONNECTING GROUND WIRE
5. GUIDE REVISIONS
FAQ
There aren’t any so far. If you encounter any problems with your iMETOS® Active Tracker FM2 G2, contact our support team at: support@metos.at.
1. PURPOSE
Purpose of this document is to describe the instalation of the SIM card and installation of the iMETOS Active Tracker FM2 device on a tractor.
2. REQUIREMENTS
In order to do the installation, you will need:
- Activated SIM card into the tracker (with no PIN lock), SIM size: micro
- Small Philips screwdriver
- Zip ties
If you want to check the settings and iMETOS Active Tracker FM2 status via SMS message:
- You need to know the phone number of the SIM card
- Mobile phone from which you will send out the SMS
3. SIM CARD INSTALLATION
3.1 SIM CARD INSTALLATION 3.2 INTERNAL BATTERY CONNECTION 3.3 CLOSE THE HOUSING
Make sure you have an active micro-SIM card which has a data transfer data plan with the gsm network provider and that the SIM card PIN lock is disabled.
SIM card sizes:
3.1 SIM CARD INSTALLATION
Step 1: open the iMETOS Active Tracker FM2 housing. Unscrew the 6 screws on the bottom side of the housing using the Phillips screwdriver.
Step 2: Insert the SIM card into the SIM card holder. Be sure to use the correct SIM card orientation and size. SIM card needs to be MICRO size.
3.2 INTERNAL BATTERY CONNECTION
Step 1: Connect the cable of the internal battery into the corresponding battery input on the board
3.3 CLOSE THE HOUSING
Step 1: carefully close the housing, make sure no cable gets between the upper and lower part and screw the screws back into their positions.
4. DEVICE INSTALLATION
4.1 CORRECT ORIENTATION AND INSTALLATION 4.2 MOUNTING RECOMMENDATIONS
4.1 CORRECT ORIENTATION AND INSTALLATION
This is the correct orientation of the iMETOS Active Tracker FM2 device:
Internal GNSS antenna device should be mounted with the sticker view to the open sky (metal free) with not less than ¾ of metal free area as shown in Picture 8:
iMETOS Active Tracker needs to be oriented correctly – the GPS antenna needs to be pointed upward to the sky in order to ensure the best GPS position acquirement with no metal parts above the tracker.
Example of a bad installation (wrong orientation, GPS antenna facing down, under the metal bonnet, exposed to high vibrations…) resulting in bad quality data and GPS position acquiring:
Deviation of the axis of the vehicle should be max 3 to 5%:
4.2 MOUNTING RECOMMENDATIONS
4.2. 1 CONNECTING WIRES 4.2. 2 CONNECTING POWER SOURCE 4.2. 3 CONNECTING IGNITION WIRE 4.2. 4 CONNECTING GROUND WIRE
The iMETOS Active Tracker already comes with preinstalled 12V input connector and fuse redady to be connected to the power outlet in the tractor. If you wish to connect the wires to a different power source, follow the steps below and make sure to stay safe.
4.2. 1 CONNECTING WIRES
- Wires should be connected while module is not plugged in.
- Wires should be fastened to the other wires or non-moving parts. Try to avoid heat emitting and moving objects near the wires.
- The connections should not be seen very clearly. If factory isolation was removed while connecting wires, it should be applied again.
- If the wires are placed in the exterior or in places where they can be damaged or exposed to heat, humidity, dirt, etc., additional isolation should be applied.
- Wires cannot be connected to the board computers or control units.
4.2. 2 CONNECTING POWER SOURCE
- Be sure that after the car computer falls asleep, power is still available on chosen wire. Depending on car, this may happen in 5 to 30 minutes period.
- When module is connected, be sure to measure voltage again if it did not decrease.
- It is recommended to connect to the main power cable in the fuse box.
- Use 3A, 125V external fuse.
4.2. 3 CONNECTING IGNITION WIRE
Connecting the ignition wire (yellow color is not absoultely needed as the tracker detects the movement and therefore can asses when the tracktor is turned on also without this wire). For bettter accurate results, the connection of ignition wire is recommended.
- Be sure to check if it is a real ignition wire – power does not disappear while starting the engine.
- Check if this is not an ACC wire (when key is in the first position, most electronics of the vehicle are available).
- Check if power is still available when you turn off any of vehicles devices.
- gnition is connected to the ignition relay output. As alternative, any other relay, which has power output, when ignition is on, may be chosen.
4.2. 4 CONNECTING GROUND WIRE
- Ground wire is connected to the vehicle frame or metal parts that are fixed to the frame.
- If the wire is fixed with the bolt, the loop must be connected to the end of the wire.
- For better contact scrub paint from the place where loop is connected.
PAY ATTENTION! Connecting the power supply must be carried out in a very low impedance point on-board vehicle network. These points in the car are the battery terminals. Therefore, we recommend connecting the power of iMETOS Active Tracker FM2 (wire GND and POWER) directly to the battery terminals. Another valid option is to connect the wires to the main POWER cable inside the fuse box (if there is none, then to the power supply where the fuses of vehicle’s computer are), wire GND must be connected in a special point, designed to connect GND vehicle computer. Connecting the GND at an arbitrary point to the mass of the car is unacceptable, as static and dynamic potentials on the line GND will be unpredictable, which can lead to unstable iMETOS Active Tracker and even its failure.
5. GUIDE REVISIONS
| GUIDE VERSION | MODIFICATION |
| 1.00 | First release of the document |
SMS SETTINGS GUIDE
1. PURPOSE
2. REQUIREMENTS
3. SMS COMMANDS, PARAMETERS AND EXAMPLES
3.1 SMS COMMANDS
3.1. 1 GETINFO
3.1. 2 GETVER
3.1. 3 GETSTATUS
3.1. 4 GETGPS
3.1. 5 GGPS
3.1. 6 CPURESET
3.1. 7 GETPARAM #
3.1. 8 SETPARAM #:# AND SETPARAM #:#;#:#;
3.1. 9 COUNTRECS
3.1. 10 BATTERY
3.2 PARAMETERS
3.2. 1 SYSTEM PARAMETERS
3.2. 2 GPRS PARAMETERS
3.2. 3 SMS/CALL PARAMETERS
3.2. 4 DATA ACQUISITION MODES
4. RECOMMENDED / DEFAULT SETTINGS
4.1 RECOMMENDED DEFAULT VALUES
4.2 DEFAULT SETTINGS VIA SMS COMMANDS
4.2. 1 GET GENERAL INFO
4.2. 2 APN SETTINGS (EXAMPLE FOR METOS LIECHTENSTEIN SIM CARD)
4.2. 3 DATA ACQUISITION SETTINGS (EXAMPLE FOR SENDING A LOT OF DATA)
5. FREQUENTLY NEEDED SETTINGS
6. GUIDE REVISIONS
FAQ
There aren’t any so far. If you encounter any problems with your iMETOS® Active Tracker FM2 G2, contact our support team at: support@metos.at.
1. PURPOSE
Purpose of this document is to describe the settings available via the SMS messages on the iMETOS Active Tracker FM2 device.
This document includes example SMS settings sent from an iPhone.
2. REQUIREMENTS
In order to set up or change available settings, you need to:
- Insert an activated SIM card into the tracker (with no PIN lock)
- Know the phone number of the SIM card
- Mobile phone from which you will send out the SMS
3. SMS COMMANDS, PARAMETERS AND EXAMPLES
3.1 SMS COMANDS 3.2 PARAMETERS
3.1 SMS COMMANDS
3.1. 1 GETINFO 3.1. 2 GETVER 3.1. 3 GETSTATUS 3.1. 4 GETGPS 3.1. 5 GGPS 3.1. 6 CPURESET 3.1. 7 GETPARAM # 3.1. 8 SETPARAM #:# AND SETPARAM #:#;#:#; 3.1. 9 COUNTRECS 3.1. 10 BATTERY
Every SMS starts with username password and then command.
Example: we would like to read out APN name set on the device. The SMS content is “imao agro1 getparam 2001” (without the “ “ signs).
3.1. 1 GETINFO
Command: getinfo
Description: device runtime system information
Response: yes
| RESPONSE DETAILS | DESCRIPTION |
| RTC | RTC Time |
| Init | Device initialization time |
| UpTime | Total up time (in seconds) |
| PWR | Last restart reason |
| RST | Total restarts count |
| GPS | GPS receiver state. 0 – OFF, 1 – ON without fix, 2 – ON with fix, 3 – In sleep mode. |
| SAT | Average satellites |
| TTFF | Time To First Fix |
| TTLF | Time To Last Fix |
| NOGPS | How much time no GPS fix (h:min) |
| SR | Number of Sent Records |
| FG | Failed GPRS counter |
| FL | Failed link counter |
| SMS | Sent SMS Counter |
| REC | Records Found – number of records in the memory. |
| MD | Data Mode state. 0 – Home and Stop, 1 – Home and Moving, 2 – Roaming and Stop, 3 – Roaming and Moving, 4 – Unknown and Stop, 5 – Unknown and Moving |
Example:
3.1. 2 GETVER
Command: getver
Description: returns code version, device IMEI, modem app version, RTC time, Init time, Uptime and BT MAC address
Response: yes
| RESPONSE DETAILS | DESCRIPTION |
| Ver | Firmware version |
| GPS | Version of GPS module |
| Hw | Version of hardware |
| Mod | HW version modification |
| IMEI | Device IMEI |
| Init | Device initialization time |
| Uptime | Total up time (in seconds) |
| BT | Device MAC address |
Example:
3.1. 3 GETSTATUS
Command: getstatus
Description: modem Status information
Response: yes
| RESPONSE DETAILS | DESCRIPTION |
| Data Link | Indicate module connection to server at the moment: 0 – Not connected, 1 – connected |
| GPRS | Indicate if GPRS is available at the moment |
| Phone | Voice Call status: 0 – ready, 1 – unavailable, 2 – unknown, 3 –ringing, 4 – call in progress, 5 – asleep |
| SIM | SIM Status: 0-ready, 1-pin, 2-puk, 3-pin2, 4-puk2 |
| OP | Connected to GSM Operator: numerical id of operator |
| Signal | GSM Signal Quality [0-5] |
| NewSMS | Indicate if new message received |
| Roaming | 0 – Home Network, 1 – roaming |
| SMSFull | SMS storage is full? 0 – ok, 1 – SMS storage full |
| LAC | GSM Tower Location Area Code |
| Cell ID | GSM Tower Cell ID Code |
Example:
3.1. 4 GETGPS
Command: getgps
Description: current GPS data, date and time
Response: yes
| RESPONSE DETAILS | DESCRIPTION |
| GPS | Indicates valid (1) or invalid (0) Gps data |
| Sat | Count of currently available satellites |
| Lat | Latitude (Last good Latitude) |
| Long | Longitude (Last good Longitude) |
| Alt | Altitude |
| Speed | Ground speed, km/h |
| Dir | Current date |
| Time | Current GMT time |
Example:
3.1. 5 GGPS
Command: ggps
Description: returns location information with Google maps link
Response: yes
| RESPONSE DETAILS | DESCRIPTION |
| D | Date |
| T | Time |
| S | Actual Speed |
| C | Latitude (Last good Latitude), Longitude (Last good Longitude) |
| Url | Google Maps Link |
Example:
3.1. 6 CPURESET
Command: cpureset
Description: resets device
Response: no
Example:
The command cpureset does not return anything back therefore it is advised to send another sms with command get status to the device approx 1 minute after the cpureset sms is sent.
3.1. 7 GETPARAM #
Command: getparam #
Description: returns selected parameter value, # param ID
Response: yes
Example:
List of all supported parameters and their IDs is in chapter 4.
3.1. 8 SETPARAM #:# AND SETPARAM #:#;#:#;
Command: setparam #:#
Description: Sets selected parameter value:
1.# — first ID value
2.# — New first Parameter Value
3.# — second ID value
4.# — New second Parameter Value
5.# — third ID value
6.# — New third Parameter Value
SMS command of limited to 160 characters.
Response: yes
Example:
In the first example, we set parameter 2001 which is APN name to value ‘a1’.
In the second example, we set parameters 2001 (APN name) to value a1, 2002 (APN username) to value user and 2003 (APN password) to value pass.
List of all supported parameters and their IDs is in chapter 4.
3.1. 9 COUNTRECS
Command: countrecs
Description: returns records number
Response: yes
Example:
3.1. 10 BATTERY
Command: battery
Description: returns battery state info
Response: yes
| RESPONSE DETAILS | DESCRIPTION |
| BatState | Battery connected (1) or disconnected (0) from device |
| FSMState | Current battery state |
| ChargerIC | Battery charging status |
| ExtV | External Voltage |
| BatV | Battery voltage |
| BatI | Battery charging current |
Example:
3.2 PARAMETERS
3.2. 1 SYSTEM PARAMETERS 3.2. 2 GPRS PARAMETERS 3.2. 3 SMS/CALL PARAMETERS 3.2. 4 DATA ACQUISITION MODES
3.2. 1 SYSTEM PARAMETERS
| PARAMETER | ID | DESCRIPTION |
| Sleep timeout | 103 | Sleep timeout is time after which the device goes to GPS sleep, Deep Sleep or Online Deep Sleep if other requirements are met. It is measured in minutes. |
| GNSS Source | 109 | This parameter sets Satellite System, available values: 0 – Undefined 1 – Beidou only 2 – Glonass only 3 – Galileo + Beidou 4 – Galileo only 5 – Galileo + Beidou 6 – Galileo + Glonass 8 – GPS only 9 – GPS + Beidou 10 – GPS + Glonass 12 – GPS + Galileo 13 – GPS + Galileo + Beidou 14 – GPS + Galileo + Glonass 15 – GPS,Galileo, Glonass and Beidou and not allowed |
| Led indication | 108 | Sets led indication: 0 – disabled, 1 – enabled |
| Synchronization settings | 900 | Settings used for device internal time synchronization: 0 – GPS only 1 – NITZ and NTP 2 – NTP 3 – NITZ |
| NTP Resync | 901 | Periodical time synchronization. If not zero device will resynchronize time once set period expires. |
| NTP server 1 | 902 | |
| NTP server 2 | 903 | |
| Battery charge mode | 110 | Sets when charging is allowed: 0 – On Need 1 – After Ignition ON |
3.2. 2 GPRS PARAMETERS
| PARAMETER | ID | DESCRIPTION |
| Open Link Timeout | 1000 | Defines for how many seconds device will keep connection to the server after successful data transfer while waiting for a new record. |
| Server Response Timeout | 1001 | Defines time period (in seconds) for server response to sent records. |
| SIM GPRS content activation | 2000 | Parameter allows or does not allow GPRS usage with SIM1. If GPRS is not allowed value is 0, if GPRS is allowed value is 1. |
| SIM APN Name | 2001 | Parameter defines SIM GPRS Access Point Name. |
| SIM APN username | 2002 | Parameter defines SIM APN username. In case operator does not use username for login, value should be empty. |
| SIM APN password | 2003 | Parameter defines SIM APN password. In case operator does not use password for login, value should be empty. |
| Domain | 2004 | Parameter defines AVL data destination server IP address. |
| Target Server Port | 2005 | Parameter defines AVL data destination server port number. |
| Protocol | 2006 | Parameter defines GPRS data transport protocol. Module can use TCP or UDP transport protocol to send data to server. For TCP protocol value is 0, for UDP protocol value is 1. |
3.2. 3 SMS/CALL PARAMETERS
| PARAMETER | ID | DESCRIPTION |
| GSM Predefined Numbers | 6000 — 6009 | In this field GSM numbers are written, to which will be sent “Event SMS” text message. |
| SMS Event Time Zone | 3006 | Time zone which will be used in eventual SMS messages. |
3.2. 4 DATA ACQUISITION MODES
Home Network GSM operator code “Vehicle on STOP” parameters:
| PARAMETER | ID | DESCRIPTION |
| Min Period | 10000 | This parameter indicates time interval in seconds in order to acquire new record. If value is 0 it means no records by min period will be saved. |
| Min Saved Records | 10004 | This parameter defines minimum number of records in one data packet that can be sent to server. It has higher priority than Data Send Period (ID=10005). |
| Send Period | 10005 | This parameter indicates frequency (time interval in seconds) of sending data to server. |
Home Network GSM operator code “Vehicle MOVING” parameters:
| PARAMETER | ID | DESCRIPTION |
| Min Period | 10050 | This parameter indicates time interval in seconds in order to acquire new record. If value is 0 it means no records by min period will be saved. |
| Min Distance | 10051 | This parameter indicates distance in meters in order to acquire new record. Record is stored when the distance between previous records is greater than parameters value. If value is 0 it means no records by min distance will be saved. |
| Min Angle | 10052 | This parameter indicates angle in degrees in order to acquire new record. If angle difference between last recorded coordinate and current position is greater than defined value, new record is stored. This parameter is operational, when speed is higher than 10km/h. If value is 0 it means no records by min angle will be saved. |
| Min Speed Delta | 10153 | This parameter indicates speed difference in order to acquire new record. If speed difference between last recorded coordinate and current position is greater than defined value, new record is stored. If value is 0 it means no records by min speed delta will be saved. |
| Min Saved Records | 10154 | This parameter defines minimum number of records in one data packet that can be sent to server. It has higher priority than Data Send Period (ID=10105). |
| Send Period | 10155 | This parameter indicates frequency (time interval in seconds) of sending data to server. |
Unknown Network GSM operator code “Vehicle on STOP” parameters:
| PARAMETER | ID | DESCRIPTION |
| Min Period | 10200 | This parameter indicates time interval in seconds in order to acquire new record. If value is 0 it means no records by min period will be saved. |
| Min Saved Records | 10204 | This parameter defines minimum number of records in one data packet that can be sent to server. It has higher priority than Data Send Period (ID=10205). |
| Send Period | 10205 | This parameter indicates frequency (time interval in seconds) of sending data to server. |
Unknown Network GSM operator code “Vehicle MOVING” parameters:
| PARAMETER | ID | DESCRIPTION |
| Min Period | 10250 | This parameter indicates time interval in seconds in order to acquire new record. If value is 0 it means no records by min period will be saved. |
| Min Distance | 10251 | This parameter indicates distance in meters in order to acquire new record. Record is stored when the distance between previous records is greater than parameter’s value. If value is 0 it means no records by min distance will be saved. |
| Min Angle | 10252 | This parameter indicates angle in degrees in order to acquire new record. If angle difference between last recorded coordinate and current position is greater than defined value, new record is stored. This parameter is operational, when speed is higher than 10km/h. If value is 0 it means no records by min angle will be saved. |
| Min Speed | 10253 | This parameter indicates speed difference in order to acquire new record. If speed difference between last recorded coordinate and current position is greater than defined value, new record is stored. If value is 0 it means no records by min speed delta will be saved. |
| Min Saved Records | 10254 | This parameter defines minimum number of records in one data packet that can be sent to server. It has higher priority than Data Send Period (ID=10105). |
| Send Period | 10255 | This parameter indicates frequency (time interval in seconds) of sending data to server. |
4. RECOMMENDED / DEFAULT SETTINGS
4.1 RECOMMENDED DEFAULT VALUES 4.2 DEFAULT SETTINGS VIA SMS COMMANDS
4.1 RECOMMENDED DEFAULT VALUES
System:
1. Movement source: movement
2. Records saving: after Position Fix
3. GNSS Source: GLONASS + GPS
4. Battery charge mode: on need
Static navigation:
1. Static navigation: enabled
2. Static navigation source: movement sensor
Sleep mode: deep sleep
Ignition source: Accelerometer + Power voltage
Time synchronization: NIZ + NTP
GPRS settings (example for Metos SIM card):
1. APN: metos.at
2. APN username: metos
3. APN password: metos
4. Nomal (PAP) protocol
Records settings:
1. Open link timeout: 30 s
2. Response timeout: 30 s
3. Sort by: newest
Data acquisition:
1. On Stop
| HOME | ROAMING | UNKNOWN | |
| Min period | 3600 | 3600 | 3600 |
| Min Saved Records | 1 | 1 | 1 |
| Send Period | 120 | 120 | 120 |
2. Moving
| HOME | ROAMING | UNKNOWN | |
| Min period | 300 | 300 | 300 |
| Min distance | 100 | 100 | 100 |
| Min angle | 10 | 10 | 10 |
| Min speed delta | 10 | 10 | 10 |
| Min saved records | 1 | 1 | 1 |
| Send period | 120 | 120 | 120 |
4.2 DEFAULT SETTINGS VIA SMS COMMANDS
4.2. 1 GET GENERAL INFO 4.2. 2 APN SETTINGS (EXAMPLE FOR METOS LIECHTENSTEIN SIM CARD) 4.2. 3 DATA ACQUISITION SETTINGS (EXAMPLE FOR SENDING A LOT OF DATA)
4.2. 1 GET GENERAL INFO
1. GET INFO AGAIN
Send SMS with content: «imao agro1 getinfo»
Explanation: it should send back basic info from the iMETOS Active Tracker — username and password works
Response: you should get the response with something similar to: «RTC:…»
Note: no double spaces in this and next SMS messages
4.2. 2 APN SETTINGS (EXAMPLE FOR METOS LIECHTENSTEIN SIM CARD)
2. SET UP APN NAME
Send SMS with content: «imao agro1 setparam 2001:metos.at»
Explanation: we set up APN name to «metos.at»
Response: you should get response with «New value 2001:metos.at;»
3. SET UP APN USERNAME
Send SMS with content: «imao agro1 setparam 2002:metos»
Explanation: we set up APN username to «metos»
Response: you should get response with «New value 2002:metos;»
4. SET UP APN PASSWORD
Send SMS with content: «imao agro1 setparam 2003:metos»
Explanation: we set up APN username to «metos»
4.2. 3 DATA ACQUISITION SETTINGS (EXAMPLE FOR SENDING A LOT OF DATA)
1. HOME
Vehicle on STOP:
Min Period (example: set to 30 sec): «imao agro1 setparam 10000 30»
Min Saved Records (example: set to 1): «imao agro1 setparam 10004 1»
Send Period (example: set to 60 sec): «imao agro1 setparam 10005 60»
Vehicle MOVING:
Min. Period (example: set to 30 sec): «imao agro1 setparam 10050 30»
Min. Distance (example: set to 10 m): «imao agro1 setparam 10051 10»
Min. Angle (example: set to 10 deg.): «imao agro1 setparam 10052 10»
Min. Speed delta (example: set to 30 km/h): «imao agro1 setparam 10053 30»
Min Saved Records (example: set to 1): «imao agro1 setparam 10054 1»
Send Period (example: set to 60 sec): «imao agro1 setparam 10055 60»
2. Roaming
Vehicle on STOP:
Min Period (example: set to 30 sec): «imao agro1 setparam 10100 30»
Min Saved Records (example: set to 1): «imao agro1 setparam 10104 1»
Send Period (example: set to 60 sec): «imao agro1 setparam 10105 60»
Vehicle MOVING:
Min. Period (example: set to 30 sec): «imao agro1 setparam 10150 30»
Min. Distance (example: set to 10 m): «imao agro1 setparam 10151 10» Min. Angle (example: set to 10 deg.): «imao agro1 setparam 10152 10»
Min. Speed delta (example: set to 30 km/h): «imao agro1 setparam 10153 30»
Min Saved Records (example: set to 1): «imao agro1 setparam 10154 1»
Send Period (example: set to 60 sec): «imao agro1 setparam 10155 60»
3. Unknown
Vehicle on STOP:
Min Period (example: set to 30 sec): «imao agro1 setparam 10200 30»
Min Saved Records (example: set to 1): «imao agro1 setparam 10204 1»
Send Period (example: set to 60 sec): «imao agro1 setparam 10205 60»
Vehicle MOVING:
Min. Period (example: set to 30 sec): «imao agro1 setparam 10250 30»
Min. Distance (example: set to 10 m): «imao agro1 setparam 10251 10»
Min. Angle (example: set to 10 deg.): «imao agro1 setparam 10252 10»
Min. Speed delta (example: set to 30 km/h): «imao agro1 setparam 10253 30»
Min Saved Records (example: set to 1): «imao agro1 setparam 10254 1»
Send Period (example: set to 60 sec): «imao agro1 setparam 10255 60»
5. FREQUENTLY NEEDED SETTINGS
5.1 APN SETTINGS
Setting up the APN settings can be easy with sending the correct SMS message to the SIM card’s phone number which is inserted in the iMETOS Active Tracker.
Parameters for APN values are:
2001 – for APN name
2002 – for APN username
2003 – for APN password.
Each parameter can be set in its own SMS or all 3 parameters can be set at once in 1 SMS.
Note: Make sure the length of the SMS does not exceed 160 characters!
In the first example, we set parameter 2001 which is APN name to value ‘a1’.
In the second example, we set parameters 2001 (APN name) to value a1, 2002 (APN username) to value user and 2003 (APN password) to value pass.
6. GUIDE REVISIONS
| GUIDE VERSION | MODIFICATION |
| 1.01 | Added recommended default settings for production |
| 1.00 | First release of the document |