skypatrol evolution - tt8740at001 - at commands - revision 1

7/31/2019 Skypatrol Evolution - TT8740AT001 - At Commands - Revision 1

1/65


2/65

Document Title: SkyPatrol EvolutionAT Command Set Reference

Version: 1.09

Date: 03/14/08

Status: Released

Document Control ID: TT8740AN001

General

All efforts have been made to ensure the accuracy of material provided in thisdocument at the time of release. However, the items described in this document aresubject to continuous development and improvement. All specifications are subject to

change without notice and do not represent a commitment on the part of SkyPatrolLLC. SkyPatrol, Inc. will not be responsible for any loss or damages incurred related tothe use of information contained in this document.

This product is not intended for use in life support appliances, devices or systemswhere a malfunction of the product can reasonably be expected to result in personalinjury. SkyPatrol, Inc. customers using, integrating, and/or selling this product for use insuch applications do so at their own risk and agree to fully indemnify SkyPatrol LLC. forany damages resulting from illegal use or resale.

Copyright

Complying with all applicable copyright laws is the responsibility of the user. Withoutlimiting the rights under copyright, no part of this document may be reproduced, storedin or introduced into a retrieval system, or transmitted in any form or by any means(electronic, mechanical, photocopying, recording or otherwise), or for any purpose,without the express written permission of SkyPatrol LLC.

SkyPatrol may have patents, patent applications, trademarks, copyrights or otherintellectual property rights covering subject matter in this document. Except asexpressly provided in any written license agreement from SkyPatrol, the furnishing ofthis document does not give you any license to these patents, trademarks, copyrights orother intellectual property.

2005 -2007 Skypatrol, LLC. All rights reserved.Enabler is a registered trademark of Enfora in the United States.


3/65

Regulatory Compliance FCC

The EVOLUTION has been tested and found to comply with the limits for aClass B digital device, pursuant to part 15 of the FCC rules. These limits aredesigned to provide reasonable protection against harmful interference in a

residential installation. This equipment generates, uses and can radiate radiofrequency energy and, if not installed and used in accordance with theinstructions, may cause harmful interference to radio communications.However, there is no guarantee that interference will not occur in a particularinstallation. If this equipment does cause harmful interference to radio ortelevision reception, which can be determined by turning the equipment offand on, the user is encouraged to try to correct the interference by one ormore of the following measures:

- Reorient or relocate the receiving antenna- Increase the separation between the equipment and receiver

- Connect the equipment into an outlet on a circuit different from that towhich the receiver is connected

- Consult the dealer or an experienced radio/TV technician for help.

Disclaimer

The information and instructions contained within this publication complywith all FCC, GCF, PTCRB, RTTE, IMEI and other applicable codes thatare in effect at the time of publication. Skypatrol disclaims allresponsibility for any act or omissions, or for breach of law, code orregulation, including local or state codes, performed by a third party.

Skypatrol strongly recommends that all installations, hookups, transmissions, etc., beperformed by persons who are experienced in the fields of radio frequency technologies.Skypatrol acknowledges that the installation, setup and transmission guidelinescontained within this publication are guidelines, and that each installation may havevariables outside of the guidelines contained herein. Said variables must be taken intoconsideration when installing or using the product, and Skypatrol shall not be responsiblefor installations or transmissions that fall outside of the parameters set forth in thispublication.

Skypatrol shall not be liable for consequential or incidental damages,injury to any person or

property, anticipated or lost profits, loss of time, or other losses incurredby Customer or any third party in connection with the installation of theProducts or Customer's failure to comply with the information andinstructions contained herein.


4/65

Warranty Information

LIMITED WARRANTIES. The following limited warranties give you specific legal rights.You may have others, which vary from state/jurisdiction to state/jurisdiction.

Hardware Limited Warranty. SKYPATROL warrants that the Product shall be free fromdefects in materials and workmanship and will substantially conform to SKYPATROLsapplicable published specifications for the Products for a period of one (1) year from thedate of original purchase. THIS WARRANTY IS VOID IF THE PRODUCT CASING ISOPENED BY ANYONE OTHER THAN A SKYPATROL AUTHORIZED SERVICEFACILITY. The warranty set forth in this paragraph shall not apply to the Software.

Software Limited Warranty. The Software is licensed and not sold. Its use is governed bythe provisions of the applicable End User License Agreement (EULA), if any, includedwith the Software. In the absence of a separate EULA included with the Softwareproviding different limited warranty terms, exclusions, and limitations, the following termsand conditions shall apply. SKYPATROL warrants that the Software will substantiallyconform to the applicable published specifications for the Software for a period of ninety(90) days from the date of valid activation. SKYPATROL does not warrant that theoperation of the Software will be error-free or uninterrupted or that the Softwarefunctions will meet your requirements or that all defects in the Software will be corrected.THIS WARRANTY IS VOID IF YOU BREACH THE SOFTWARE LICENSE SET FORTH

ABOVE.

WARRANTY REMEDIES. SKYPATROLs sole liability and your exclusive remedy underthe warranties set forth above shall be, at SKYPATROLs option, to repair or replace anyProduct or Software that fails to conform to such warranty (Nonconforming Product), orrefund the purchase price paid by you for any such Nonconforming Product, upon yourreturn of any Nonconforming Product to SKYPATROL or, if you purchased the Productfrom an Authorized Distributor, to such Authorized Distributor, in accordance withSKYPATROLs or such Authorized Distributors standard return material authorizationprocedures. The foregoing notwithstanding SKYPATROL will not pay for (i) costs ofinstallation or removal, (ii) costs of product set-up or adjustment, or (iii) shipping orrelated charges of returning the Product for repair, regardless of whether the repair iscovered by the Limited Warranty set forth above. You must pay for shipment of theProduct to the nearest SKYPATROL Authorized Service Facility and, if the warrantyclaim is valid, SKYPATROL will pay for shipment of the repaired or replaced Productback to you. You must provide a purchase receipt or other proof of the date of originalpurchase before warranty service will be rendered. All replaced parts and products, andproducts on which a refund is made, become the property of SKYPATROL. Unless

prohibited by law, new or reconditioned parts and Products may be used in theperformance of warranty service. Repaired or replaced parts and Products arewarranted for the remainder of the original limited warranty period. You will be chargedfor the repair or replacement of the Product made after the expiration of the warrantyperiod.

WARRANTY EXCLUSIONS AND DISCLAIMER. The preceding warranties areconditioned upon submission of a purchase receipt or other proof of the date of original


5/65

purchase and the preceding warranties shall not apply to, and SKYPATROL shall not beresponsible for: (1) damage, failure or malfunction caused by or attributable to acts ofGod, lightning or other incidence of excess voltage or current, fresh or salt waterimmersion or spray, abuse, neglect, accident, misuse, alteration, cosmetic damage orany other occurrence beyond the reasonable control of SKYPATROL; (2) the Products

and Software if they are not properly and correctly installed, configured, interfaced,maintained, stored, and operated in accordance with the relevant operator's manual andspecifications; (3) Services not provided by SKYPATROL; (4) the combination orutilization of the Product or Software with accessories, products, information, data,systems, devices or ancillary or peripheral equipment not made, supplied or specified bySKYPATROL; (5) the operation of the Product or Software under any specification otherthan, or in addition to, the standard specifications for the Product or Software; (6) theProduct and Software if the serial number has been removed or defaced; (7) any repairsother than those provided by a SKYPATROL Authorized Service Facility; (8)consumable parts (e.g., batteries and fuses); (9) the unauthorized modification or use ofthe Product or Software; (10) use of the Product without a valid license for the Software;or (11) any shipment of the Product (claims must be presented to the carrier).

THE WARRANTIES ABOVE STATE SKYPATROLS ENTIRE LIABILITY, AND YOUREXCLUSIVE REMEDIES, RELATING TO PERFORMANCE OF THE PRODUCTS ANDSOFTWARE. EXCEPT AS OTHERWISE EXPRESSLY PROVIDED HEREIN, THEPRODUCTS, THE PROPRIETARY INFORMATION, AND ACCOMPANYING

ACCESSORIES AND MATERIALS ARE PROVIDED AS-IS AND WITHOUTEXPRESS OR IMPLIED WARRANTY OF ANY KIND BY SKYPATROL, ITS

AUTORIZED DISTRIBUTORS OR ANYONE ELSE WHO HAS BEEN INVOLVED IN ITSCREATION, PRODUCTION, INSTALLATION, OR DISTRIBUTION INCLUDING,WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. THESTATED EXPRESS WARRANTIES ARE IN LIEU OF ALL OBLIGATIONS OR

LIABILITIES ON THE PART OF SKYPATROL ARISING OUT OF, OR IN CONNECTIONWITH, ANY PRODUCTS OR PROPRIETARY INFORMATION. SKYPATROL IS NOTRESPONSIBLE FOR THE OPERATION OR FAILURE OF OPERATION OF GPSSATELLITES OR THE AVAILABILITY OF GPS SATELLITE SIGNALS. IF ANY IMPLIEDWARRANTY APPLIES TO THE PRODUCT OR THE PROPRIETARY INFORMATION,SUCH IMPLIED WARRANTY IS LIMITED IN DURATION TO THE DURATION OF THEEXPRESS LIMITED WARRANTY SET FORTH ABOVE. SOME STATES ANDJURISDICTIONS DO NOT ALLOW LIMITATIONS ON DURATION OR THEEXCLUSION OF AN IMPLIED WARRANTY, SO THE ABOVE LIMITATION MAY NOT

APPLY TO YOU. YOU MAY ALSO HAVE ADDITIONAL RIGHTS NOT STATED IN THISDOCUMENT. IF ANY PORTION OF THE LIMITED WARRANTY PROVIDED HEREINIS ILLEGAL OR UNENFORCEABLE, SUCH PARTIAL ILLEGALITY OR

UNENFORCEABILITY SHALL NOT AFFECT THE REMAINDER OF THE LIMITEDWARRANTY.

This Limited Warranty allocates the risk of Product and Software failure between youand SKYPATROL, and SKYPATROLs pricing of the Product reflects this allocation ofrisk and the limitations of liability set forth below. The agents, employees, distributorsand dealers of SKYPATROL are not authorized to make modifications to the LimitedWarranties set forth herein, or make additional warranties binding on SKYPATROL.

Accordingly, additional statements such as dealer advertising or presentation, whether


6/65

oral or written, do not constitute warranties by SKYPATROL and should not be reliedupon.

LIMITATION OF LIABILITY. SKYPATROLS ENTIRE LIABILITY UNDER ANYPROVISION HEREIN SHALL BE LIMITED TO THE GREATER OF THE AMOUNT PAID

BY YOU FOR THE PRODUCT OR SOFTWARE LICENSE OR U.S.$25.00. TO THEMAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALLSKYPATROL OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL,INCIDENTAL OR CONSEQUENTIAL DAMAGES WHATSOEVER UNDER ANYCIRCUMSTANCE OR LEGAL THEORY RELATING IN ANY WAY TO THEPRODUCTS, PROPRIETARY INFORMATION AND ACCOMPANYING ACCESSORIES

AND MATERIALS, (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OFBUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESSINFORMATION, OR ANY OTHER PECUNIARY LOSS), REGARDLESS OF WHETHERSKYPATROL HAS BEEN ADVISED OF THE POSSIBILITY OF ANY SUCH LOSS ANDREGARDLESS OF THE COURSE OF DEALING WHICH DEVELOPS OR HASDEVELOPED BETWEEN YOU AND SKYPATROL, EVEN IF SUCH DAMAGES ARISE

FROM THE NEGLIGENCE OF SKYPATROL AND/OR ITS AGENTS. BECAUSE SOMESTATES AND JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATIONOF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVELIMITATION MAY NOT APPLY TO YOU.

YOU ACKNOWLEDGE THAT THE PRODUCT MAY ALLOW YOU, AT YOURDISCRETION, TO RECEIVE WHERE AVAILABLE FROM AN AUTHORIZEDDISTRIBUTOR SERVICES ENABLED THROUGH THE USE OF THE PRODUCT, ANDYOU IRREVOCABLY AND ABSOLUTELY AGREE THAT UNLESS YOU HAVEPURCHASED SUCH SERVICES DIRECTLY FROM SKYPATROL, SKYPATROLSHALL NOT BE LIABLE IN CONNECTION WITH ANY ACTIONS, OMISSIONS OROTHER OCCURRENCES WITH RESPECT TO SUCH SERVICES PROVIDED BY AN

AUTHORIZED DISTRIBUTOR.


7/65

Date Rev Author Description

JANUARY 24,2008

DRAFTR. SanchezJ. Blanco

Draft

MARCH 20,2008

DRAFTR. Sanchez

J. BlancoC. Moreno

Draft


8/65

Table of Contents

1 INTRODUCTION..................................................................................................... 3

1.1 DOCUMENT SCOPE ............................................................................................... 3

1.2 PLATFORM REFERENCE AND USE......................................................................... 31.3 COMMAND SYNTAX ............................................................................................. 31.4 REVISION HISTORY .............................................................................................. 3

2 AT COMMANDS...................................................................................................... 3

2.1 AUTOMATIC PICRESET ....................................................................................... 32.2 DELETE A RANGE OF EVENT GROUPS .................................................................. 32.3 DELETE A RANGE OF GEO-FENCES ...................................................................... 32.4 EVENT ............................................................................................................... 32.5 EVENT QUERY ..................................................................................................... 32.6 EVENT COUNTER................................................................................................. 3

2.7 GEO-FENCING ...................................................................................................... 32.8 GEOFENCE DEBOUNCE......................................................................................... 32.9 GPSLOCAL SUBSCRIPTION.................................................................................. 32.10 GPSODOMETER.................................................................................................. 32.11 GPSOVERSPEED INTERVAL................................................................................. 32.12 GPSQUALITY FILTERS ........................................................................................ 32.13 GPSREAD ........................................................................................................... 32.14 IGNITION DEBOUNCE ........................................................................................... 32.15 I/ODEBOUNCE..................................................................................................... 32.16 MESSAGE LOG CLEAR......................................................................................... 32.17 MESSAGE LOG DUMP........................................................................................... 3

2.18 MESSAGE LOG ENABLE ....................................................................................... 32.19 MESSAGE LOG READ DATA ................................................................................. 32.20 MESSAGE SEND ................................................................................................... 32.21 ODOMETER.......................................................................................................... 32.22 POWERSAVE ....................................................................................................... 32.23 REAL TIME CLOCKALARM.................................................................................. 32.24 REMOTE TAIP ..................................................................................................... 32.25 TAIP.................................................................................................................... 32.26 SCRIPT VERSION .................................................................................................. 3

APPENDIX A DEFAULT AT VALUES ..................................................................... 3


9/65

SkyPatrol Evolution AT Command Set ReferenceRevision 1.09A

TT8740AN001 (1.09a)Copyright 2005, SkyPatrol, LLC.

Page 9 of 65

1 Introduction

1.1 Document ScopeThis documentation pertains to the AT Command Set to be used in conjunctionwith the SkyPatrol Evolution series units.

1.2 Platform Reference and Use

The SkyPatrol Evolution series unit will be referred to using various terms, toinclude: MS (Mobile Station), TA (Terminal Adapter), DCE (DataCommunication Equipment), or ME (Mobile Equipment).

The SkyPatrol Evolution series unit can be controlled via the use of a DTE (DataTerminal Equipment) platform by issuing the AT commands via a serialinterface.

1.3 Command Syntax

The attention or AT prefix is required prior to entering any command. Allcommands require a carriage return or following the entry of the desiredcommand. All command responses are encapsulated by a carriage return andline feed or . The ASCII display of these characters is suppressedwith only the modem response being presented.

The following examples demonstrate the potential usage of AT commandspresented:

Type Example DescriptionCommand FormatQuery

AT$GXXX=? When entered willreturn the commandformat and valueranges.

Command Read AT$GXXX? When entered willreturn the current valuassigned to thecommand.

Command Write AT$GXXX=,, When entered will setthe command tospecified value(s).

Command Execution AT$GXXX When entered willexecute the specifiedcommand.


10/65



Page 10 of 65

1.4 Revision History

Date Rev Author Description2/5/03 Draft C. Patel Initial Draft.

4/29/03 1.00 C. Patel Initial Release.

6/06/03 1.01 C. Patel Modified and update description of all the commands.Added $EVENT command.

6/10/03 1.02 C. Patel Update $EVENT command: Parm1 and Parm2 definitiofor Output Flash Event

6/13/03 1.03 M.Glover Added AT$NETMON command reference

11/11/03 1.04 C. Patel Added AT$GPSODOM command. UpdatedAT$PWRSAV, AT$GEOFNC, and AT$EVENTcommands.

08/22/05 1.05 D. ONeil Added $MSGLOGEN, $MSGLOGRD, $MSGSND

11/15/05 1.06 D. ONeil Corrected $MSLOGEN command

2/12/07 1.07 D. ONeil Edited Input and Output tables in $EVENTAdded $RTCALRMAdded $IGNDBNC

11/16/07 1.08 D. ONeil Added $GFDBNCAdded Input Event 65Edited Output Event 45Added Output Events 54 58Added $HBRST

Added $USRVALAdded $GPSOSIAdded Input Event 71Added Bit 24 to Parm2 value tableAdded $IODBNCAdded Event 72Added $EVDELR, $GFDELAdded output event 59Added input events 66-69 (timers 5-8)Edited input event 71Added output event 60Edited Bit 6

01/24/08 1.09 D. ONeil Added $GPSQUALAdded $MSGLOGDMP


11/65



Page 11 of 65

2 AT Commands

2.1 Automatic PIC Reset

$HBRST Automatic PIC Reset

Command Function This command allows the user to programthe reset interval.

Command Functional SkyPatrol SpecificGroup

Command Format Query AT$HBRST=?$HBRST:(0,4-168)

Response OK

Write Format AT$HBRST=

Response OK

Read Format AT$HBRST?Response $HBRST:

OK

Execution Format N/AResponse N/A

Parameter Values

0 = Off

4-168 = Number of hours until we stopproviding heartbeat pulse to PIC

Reference N/A

Standard Scope Optional

Implementation Scope Full


12/65



Page 12 of 65

2.2 Delete a Range of Event Groups

$EVDELR Delete a Range of Event Groups

Command Function This command deletes a range of eventgroups.


Command Format Query AT$EVDELR=?Response $EVDELR: (0-99),(0-99)

OK

Write Format AT$EVDELR=,Response OK

Read Format N/AResponse N/A


Parameter Values

First group index in range to be deleted

Last group index in range to be deleted.

Reference N/A



Notes This feature is available in software

version 0.7.8 pkg 43, and later.


13/65



Page 13 of 65

2.3 Delete a Range of Geo-Fences

$GFDEL Delete a Range of Geo-Fences

Command Function This command deletes a range of geo-fences.


Command Format Query AT$GFDEL=?Response $GFDEL: (1-25),(1-25)

OK

Write Format AT$GFDEL=,Response OK



Parameter Values

First geo-fence index in range to bedeleted

Last geo-fence index in range to bedeleted.

Reference N/A



Notes This feature is available in softwareversion 0.7.8 pkg 43, and later.


14/65



Page 14 of 65

2.4 EVENT

$EVENT User Defined Input/Output

Command Function This command allows the user tocustomize the modems input and outputcapabilities. Any combination of inputevents can be monitored to trigger anycombination of output events.


Command Format Query AT$EVENT=?

Response $EVENT: (0-99),(0-3),(0-255),(-2147483647 - 2147483647),(-2147483647- 2147483647)

Write Format AT$EVENT=,,,,

OK

Read Format AT$EVENT?Response $EVENT: evgp evtyp evcat p1 p2

1A 0 27 1 11B 3 22 0 02A 0 27 0 02B 3 14 0 03A 0 9 2 43B 3 37 1 04A 0 9 5 54B 3 21 0 05A 0 9 0 05B 3 13 0 06A 0 9 1 1

6B 3 21 0 0

Execution Format N/AResponse


15/65



Page 15 of 65

2.4 $EVENT User Defined Input/Output (continued)

Parameter Values

This parameter defines the group number of agroup of events and the order they are executed.Events are grouped together to control executionsequence. A group number has to have at leastone input event and one output event. Multipleinput events within a group number would betreated as a logical AND condition. Multiple outputevents within a group number would be executedindividually in a sequential manner.

Valid values for group number are: 1 thru 99.

This parameter defines the type of event: Input orOutput. An Input event can be defined as:

Transition, Occurrence, or Input. The output eventis executed when input event conditions are met.

Value Type of event Description

0Transition

Trigger

A transition Trigger is defined as an input condition,defined by, whose value was

previouslyor less is now greater than

and less thanor was greater or

equal tois now less thanbut

greater than.

The output event would be executed when an inputrequirements are satisfied or

transition to the value set byandwhen they are equal.should be the min

value andshould be the max value.

Example 1:

Parm1 Parm2

0 Max

Figure 1. An output event will be executed when thevalue of an input event exceeds(previously

it was or less) or decreases to a value less

than(previously it was or

greater).

Example 2:

Parm1 = Parm2 = 0

0 1

Figure 2. An output event will be executed when thevalue of an input event is 0 (previously it was


16/65



Page 16 of 65

anything else but 0) andalong with

is set to 0.

Example 3:

0 1

Parm1 = Parm2 = 1

Figure 3. An output event will be executed when thevalue of an input event is 1 (previously it wasanything else but 1) andalong with

is set to 1.

1 OccurrenceTrigger

An Occurrence Trigger is defined as an inputcondition,defined by, whose

current value is greater than or equal toand

less than or equal to.

The output event would be executed when an inputrequirements are satisfied or

transition to the value set byand

when they are equal.should be the min

value andshould be the max value

Example 4:Parm1 Parm2

0 Max

Figure 4. An output event will be executed when thecurrent value of an input eventis between

andincluding boundary conditions.

Example 5:

Parm1 = 0

0 1

Parm2 = 1

Figure 5. An output event will be executed when thevalue of the input event changes from 0 to 1 or vice-versa.

Example 6:

0 1

Parm1 = Parm2 = 1

Figure 6. An output event will be executed when thevalue of the input event is 1 andalong with

is set to 1.

2 Input Trigger

An Input Trigger is defined as an input condition,defined by, that should be

used as a logical AND condition to another input


17/65



Page 17 of 65

condition defined as Transition Trigger or anOccurrence Trigger. An Output event is not triggeredwhen Input Trigger condition is valid.The input event, defined as Input Trigger, is validwhen within the event range defined by

andor whenandareequal.

3 Output

An Output event is executed when all input eventconditions (defined as Transition Trigger, OccurrenceTrigger, or Input Trigger) for that particularare met.

This parameter defines the actual Input or OutputEvent number and their valid range forand .

The below table defines the values for, and parameter for

input events defined as a Transition Trigger,Occurrence Trigger, orInput Trigger.

event

categoryParm1 Parm2 Description

0 0 or 1 0 or 1GPIO1 General purpose Input/Output #10 = Low1 = High

1 0 or 1 0 or 1 GPIO2 General purpose Input/Output #2


3 0 or 1 0 or 1GPIO4 General purpose Input/Output #40 = Main battery disconnected1 =Main battery connected

4 0 or 1 0 or 1

GPIO5 General purpose Input/Output #5Controls the RESET line of the GPS receiver.0 = Turn OFF the GPS receiver.1 = Turn ON the GPS receiver.




8 1 1 Modem power up indication

9 0 to 5 0 to 5Modem GSM registration (see AT+CREGcommand description for GSM registration statusinformation)

10 0 to 8 0 to 8Modem GPRS registration (see AT%CGREGcommand description for GPRS registration status

information)

11 0 or 1 0 or 1Receipt of IP address.0 = No IP address1 = Valid IP address obtained

12 1 1 Timer 1 (set by AT$EVTIM1)




160 to

10000001000000

GPS Distance (unit of measurement is: meters)


18/65



Page 18 of 65

17 0 to 250 250Maximum Velocity (unit of measurement is:Knots)

180 to1760

1760**Analog/Digital 1

19

0 to

1760 1760

**Analog/Digital 2

20 Reserved

21 0 or 1 0 or 1

Geo Fence #1. See AT$GEOFNC command fordetails on setting a circular geo-fence0 = Leaving Geofence area1 = Entering Geofence area

22 0 or 1 0 or 1 Geo Fence #2




26 0 or 1 0 or 1MT Power Save Event0 = Exit Power Save Mode1 = Enter Power Save Mode

27 0 or 1 0 or 1GPS Status0 = Invalid GPS data1 = Valid GPS data

28 1 1 **RTC Alarm Input

290 to

10000001000000

Invalid GPS data for a period of time (unit ofmeasurement is: seconds). Will execute at twicethe value of Param1.

300 to

10000001000000

Unit staying Idle in one place (unit ofmeasurement is: seconds). Will execute at twicethe value of Param1.

31 0 or 1 0 or 1

Geo Fence #6. See AT$GEOFNC command fordetails on setting a circular geo-fence0 = Leaving Geofence area

1 = Entering Geofence area32 0 or 1 0 or 1 Geo Fence #7












44 0 or 1 0 or 1 Geo Fence #1945 0 or 1 0 or 1 Geo Fence #20






51 0 0**Input Event Counter. This event will occurwhen a counter reaches the maximum number of aselected Input event count.


19/65



Page 19 of 65

52 0 or 1 0 or 1New SMS indication.0 = SMS message read from SIM1 = New SMS message received

53 0 to -1 0 to 1Current Input Event Counter count that can beused as an AND condition with other input events

54 0 or 1 0 or 1

Has the user programmed any geo-fence?Normally this can be found by sendingAT$GEOFNC? command and verifying itmanually based on the response sent by the device0 = geo-fence does not exists1 = at least one geo fence was created

55 N/A N/A Reserved

56 N/A N/A Reserved

57 N/A N/A Reserved

58 N/A N/A Reserved

59 0-100 0-100 Battery level as a percentage60 0 9999 0 9999 Number of Unsent Messages ($msglogrd count)

61 0 100 0 100 Memory full percentage ($msglogrd)

6263

64

65 1 to 5 1 to 5

Receipt of Incoming Call with Call Identifiermatching one the numbers configured via the$EVCID command. and correspond to range $EVCID entries which willgenerate the input event.





70 N/A N/A Reserved

71 0-3 0-3

GPS Antenna Status0 = unknown1 = good2 = open3 = short

72 0-1 0-10 = A GPS overspeed interval has ended1 = A GPS overspeed interval has begun

The below table defines the values for, and parameter for output events defined as Output.

event

categoryParm1 Parm2 Description

0 0 0 Changes GPIO #1 to Input (from Output)1 0 0 Changes GPIO #2 to Input (from Output)

2 0 0 Changes GPIO #3 to Input (from Output)






8 0 0 Set GPIO #1 configured as Output to Low (0)



20/65



Page 20 of 65






15 0 0 Set GPIO #8 configured as Output to Low (0)16 0 0 Set GPIO #1 configured as Output to High (1)

17 0 0 Set GPIO #2 configured as Output to High (1)







24 0 0 Toggle GPIO #1 configured as Output








32 Flash GPIO #1 configured as Output







39

See GPIO FlashTable below

Flash GPIO #8 configured as Output

40 Generate and transmit one UDP Message to firstIP address listed in $FRIEND command and

port number listed in $UDPAPI command based

on Parm1 and Parm2 values

41 Generate and transmit a UDP message withAcknowledge. This message is controlled by$ACKTMcommand for number of retries sent.

This message has to be acknowledged to avoidsending of retries.

42

0 to 1

See Bit-Field

Tablebelow

Generate and transmit one UDP Message to allIP address listed in $FRIEND command and

port number listed in $UDPAPI command based

on Parm1 and Parm2 values

43

1 4 0

Resets the timer (Timer #1 Timer #4) specifiedby Parm1 to the time (in seconds) specified by

Parm2. Parm2, when set to 0, resets the timer

to the time last set by $EVTIMx command. A

value other than 0 would set the timer to expireat the new specified interval. A timer can only

be disabled by setting $EVTIMx command to 0.

441 15 0

Execute AT command stored at index number ofthe $STOATEVcommand. Parm1identifies the

index number.


21/65



Page 21 of 65

450-

2147483647

See Bit-Field

Tablebelow

Sends data over SMS to All SMS destinationaddresses configured via $SMSDA command.(For select $SMSDA entries, see eventcategories 54-58)

46 N/A N/A Reserved

47 0 0 to 1 Input Event Counter48

0 0 to 1Input Event Counter reset to value stated by

parm2

491 25

0 -1000000

Set geo-fence specified by parm1 to currentlatitude & longitude with radius specified by

parm2

50

0 57 0 to 1

Emulate AT$EVTEST command via eventengine. Parm1 is the input event number while

Parm2 is the value to emulate for the input

event

51

08640000 0262800

Enter Power Save Mode. Parm1 indicates timeto stay ON in seconds max. 100 days. Parm2indicate time to stay OFF in minutes max. 6

months.Note: RTC must be backup battery voltage andpower control pin has to be configuredaccording on the hardware for this feature work

52

0 to 1

See Bit-Field

Tablebelow

Generate and transmit one TCP/IP Message toIP address & port number listed by $FRIEND

command based on Parm1 and Parm2 values

53

0 99 0 16

Sets periodic RTC alarm in minutes, hours,days, months, or years. Parm1 indicates thefrequency with which to generate the message.Parm2 indicates the unit with which to generatethe message. For example:

Parm1 Parm2 Result1 1 RTC Alarm occurs every

minute1 2 RTC Alarm occurs every hour1 4 RTC Alarm occurs every day1 8 RTC Alarm occurs every

month

540-

2147483647

See Bit-Field

Tablebelow

Sends data over SMS to the first indexed SMSdestination address configured via $SMSDAcommand

550-

21474836

47

See Bit-Field

Tablebelow

Sends data over SMS to the second indexedSMS destination address configured via

$SMSDA command

560-

2147483647

See Bit-Field

Tablebelow

Sends data over SMS to the third indexed SMSdestination address configured via $SMSDAcommand

570-

2147483647

See Bit-Field

Tablebelow

Sends data over SMS to the fourth indexed SMSdestination address configured via $SMSDAcommand


22/65



Page 22 of 65

580-

2147483647

See Bit-Field

Tablebelow

Sends data over SMS to the fifth indexed SMSdestination address configured via $SMSDAcommand

59 0 0

Turns off the modem. (Not to be confused with

sleeping where RTC continues to function. Thiscommand shuts down all modem functions.)

600 - -1

See Bit-Field

Tablebelow

Generate and transmit message to main serialport based on Parm1 and Parm2 values.

GPIO Flash Table

Parm1 Parm2

Bits 16 31 determine the low signal

state while bits 0 15 determine thehigh signal state. A value of 0 for bits16 31 indicates the GPIO willremain in low signal state for thesame amount of time as the highsignal state (50% duty cycle). Thehigh or low states are measured inmultiples of seconds. The togglecount is set by Parm2

The flashing GPIO event will cause the

GPIO output state to toggle at time 0 tothe opposite state prior to starting theGPIO output flash event processing.This counts as toggle #1. An evennumber of toggle count will force afinal state which is the same as theinitial state. An odd number of togglecount will force the final state to beopposite of the initial GPIO outputcondition. 0 = toggle forever.

Bit-Field Table

Parm2 value is obtained as a result of selecting individual bit-fieldsfrom the table below.

Parm2

Bit 0: 1 = send all data generated as a result of this table in Binaryformat

0 = send all data generated as a result of this table in ASCIIformat

Bit 1: 1 = addparm1 data to UDP message (4 bytes in Binary format,

11 bytes of data in ASCII format)0 = do not addparm1data to outbound UDP message

Bit 2: 1 = add $MDMID value (22 bytes of ASCII data irrespective

of Bit 0 setting)

0 = do not add $MDMID valueBit 3: 1 = add $IOCFG and $IOGPA(GPIO direction and data) in

ASCII-HEX format (2 bytes in Binary format, 6 bytes inASCII format)

0 = do not add GPIO direction and data value.

Bit 4: 1 = add $IOADC1 value (2 bytes in binary format, 5 bytes in

ASCII format0 = do not add A/D 1 value.


23/65



Page 23 of 65

Bit 5: 1 = add $IOADC2 value (2 bytes in binary format, 5 bytes in

ASCII format0 = do not add A/D 2 value.

Bit 6: 1 =Message is stored in non-volatile memory until it can be sent,regardless of network status.

0 = Code checks network status before storing message in non-volatile memory. If it appears that the message can be sent outimmediately (network status is clear and message queue has fewor no messages pending), the message is stored in the non-volatile message queue until it can be sent. Otherwise, themessage is deleted.

Bit 7: 1 = add inputnumber (1 byte in binary

format, 3 bytes in ASCII format)0 = do not add inputnumber

Bit 8: 1 = add GPS data (3 bytes ofDate information in Binary formator up to 80 bytes of$GPGGA NMEA message if Bit-0 isset to 0)

0 = do not add this particular field of GPS data

Bit 9: 1 = add GPS data (1 bytes ofStatus information in Binaryformat or up to 80 bytes of$GPGLL NMEA message ifBit-0 is set to 0)


Bit 10: 1 = add GPS data (3 bytes ofLatitude information in Binaryformat or up to 80 bytes of$GPGSA NMEA message ifBit-0 is set to 0)


Bit 11: 1 = add GPS data (4 bytes ofLongitude information in Binaryformat or up to two 80 bytes of$GPGSV NMEA messageif Bit-0 is set to 0)


Bit 12: 1 = add GPS data (2 bytes ofVelocity information in Binary

format or up to 80 bytes of$GPRMC NMEA message ifBit-0 is set to 0)


Bit 13: 1 = add GPS data (2 bytes ofHeading information in Binaryformat or up to 80 bytes of$GPVTG NMEA message ifBit-0 is set to 0)


Bit 14: 1 = add GPS data (3 bytes ofTime information in Binaryformat or 0 bytes if Bit-0 is set to 0)


Bit 15: 1 = add GPS data (3 bytes ofAltitude information in Binaryformat or 0 bytes if Bit-0 is set to 0)


Bit 16: 1 = add GPS data (1 byte ofNumber Of Satellites In Viewinformation in Binary format or 0 bytes if Bit-0 is set to 0)


Bit 17: 1 = disables send of OTA messages when MTG is in Low PowerMode

0 = sends OTA messages when MTG is in Low Power Mode

Bit 18: 1 = send this OTA message via SMS when GPRS services is notavailable

0 = send this OTA message via GPRS only


24/65



Page 24 of 65

Bit 19: 1 = send Last Valid GPS data if current data is invalid0 = send current GPS data valid or invalid

Bits 20: 1 = add Odometer reading (4 bytes ofOdometer information inBinary format or 11 bytes if Bit-0 is set to 0)


Bits 21: 1 = add RTC time (6 bytes ofRTC time in Binary format or 13 bytes if Bit-0 is set to 0)

0 = do not add RTC time with GPS data

Bits 22: 1 = Replace/append modem ID field with 10-byte modem ID(including one leading and one ending space character) if bit-0 is set to 0. Replace/append it with 8-bytes long modem IDvalue if bit-0 is set to 1 (no leading or ending space charactersin binary mode.)(NOTE: bit-22 setting overrides bit-2 setting)

0 = Sent the modem ID as defined by Bit-2Note: The ID will appear right justified.

Bits 23: Battery level as a percentage.1 = add the battery level to the message format

0= do not add the battery level to the message format(NOTE: This bit-field sends 3 bytes (ASCII) when Bit-0 is setto 0 o 1 byte when Bit-0 is set to 1)

Bit 24: 1 = add GPS over speed data (6 bytes ofOdometer informationin Binary format or 18 bytes if Bit-0 is set to 0). Binaryformat: xxyyzz: xx is speed specified by AT$GPSOSI, yy isthe maximum speed incurred during the interval, zz is theduration in seconds of the interval: ASCII format:xxxxx,yyyyy,zzzzz: fields are five bytes long, commadelimited and MSBs of each field are zero padded.

0 = do not add this particular field of GPS dataNote: yyyyy should be interpreted as yyyy.y knots.

Bits 25 31:TBD

Notes A maximum of 150 events (input andoutput) are supported.

Reference



Notes A maximum of 150 events (input and

output) are.


25/65



Page 25 of 65

2.5 Event Query

$EVNTRY EVENT QUERY

Command Function This command queries how many eventshave been used and how many are left.

Command FunctionalGroup

Command Format Query AT$EVNTRY?Response $EVNTRY: ,

OK

Write Format N/AResponse N/A



Parameter Values

Number of events that have been used

Number of events available for new entries

Reference N/A



Notes


26/65



Page 26 of 65

2.6 Event Counter

$EVTIMQRY Event Counter

Command Function This command shows the current count forthe event counter indicated by theargument.


Command Format Query AT$EVTIMQRY=?Response $EVTIMQRY: (1-8)

OK

Write Format AT$EVTIMQRY=Response $EVTIMQRY:=

OK

Read Format AT$EVTIMQRY?Response ERROR

Execution Format AT$EVTIMQRY=8Response $EVTIMQRY: 8=0.000

OK

Parameter Values N/A

Reference ITU-T Ref. V.25ter Chapter 6.3.8

Standard Scope Mandatory


Notes


27/65



Page 27 of 65

2.7 Geo-Fencing

$GEOFNC Geo fencing a circular area

Command Function This command allows a user to send aGPS message when the device moves inor out of a geographical area.

Command Functional Group SkyPatrol Specific

Command Format Query AT$GEOFNC=?Response $GEOFNC: (1 25),(0 - 100000),(-90 -

+90),(-180 - +180)OK

Write Format Response AT$GEOFNC=,,,OK

Read Format Response AT$GEOFNC?$GEOFNC:,,,OK

Execution Format Response N/A

Parameter Values

Defines the fence number

Defines radius of the circle from givenLatitude and Longitude coordinates

Defines the latitude for the center point ofa circle

Defines the longitude for the center pointof a circle

Reference N/A



28/65



Page 28 of 65

2.7 $GEOFNC Geo fencing a circular area(continued)


Notes An AT$EVENT command has to be set tosend a GPS message to the remote hostwhen entering or exiting the fenced area.See the MT-G Users Manual for example.


29/65



Page 29 of 65

2.8 Geofence Debounce

$GFDBNC Set geofence debounce count

Command Function This command allows the user to set the #of consecutive geofence positions requiredto trigger an inside geofence or outsidegeofence event.


Command Format Query AT$GFDBNC=?Response $GFDBNC:(0-250, 0-250)

OK

Write Format AT$GFDBNC=,

Response OK

Read Format AT$GFDBNC?Response $GFDBNC: ,

OK

Execution Format N/A

Response

Parameter Values

consecutive GPS position reports outsidea geofence required to trigger 0 conditionfor geofence input event (see $EVENT)

consecutive GPS position reports inside ageofence required to trigger 1 conditionfor geofence input event (see $EVENT)

Reference N/A



30/65



Page 30 of 65

2.8 $GFDBNC Set geofence debounce count(continued)


Notes The GPS reporting interval variesdepending on the product. For the MTGL,the updates are sent once a second so the$GFDBNC counts correspond to seconds.For the MT-uL, the updates are sent onceevery two seconds.


31/65



Page 31 of 65

2.9 GPS Local Subscription

$GPSLCL Configure sending of GPS message to

the Serial Port

Command Function This command allows the user to configuresending of GPS data on the 9-pin serialport labeled Serial on the SkyPatrolEvolution series device


Command Format Query AT$GPSLCL=?Response $GPSLCL: (0 4)

OK

Write Format Response AT$GPSLCL=OK

Read Format Response AT$GPSLCL?$GPSLCL: OK



32/65



Page 32 of 65

2.9 $GPSLCL Configure sending of GPS message tothe Serial Port(continued)

Parameter Values

0 Disable sending of GPS data to thelocal serial port when the device is in ATcommand mode (Default)1 Enable sending of GPS NMEA ASCIIdata to the local serial port when thedevice is in AT command mode2 Enable sending of GPS NMEA ASCIIdata to the local serial port. This optionhas to be sent by the user in DUN mode.

Data sent as a result of this option willalways contain a UDP/IP header. Data willbe sent to the IP address and port numberset by $UDPAPI command. This optionhas no effect on the operation of themodem when entered via the ATcommand mode.3 Enable sending of GPS TAIP ASCIIdata to the local serial port when thedevice is in AT command mode4 Enable sending of GPS TAIP ASCII

data to the local serial port. This optionhas to be sent by the user in DUN mode.Data sent as a result of this option willalways contain a UDP/IP header. Data willbe sent to the IP address and port numberset by $UDPAPI command. This optionhas no effect on the operation of themodem when entered via the ATcommand mode.

Reference N/A



Notes N/A


33/65



Page 33 of 65

2.10 GPS Odometer

$GPSODOM GPS Odometer History

Command Function This command allows the user to read thehourly Odometer history for four days starting with the current day.


Command Format Query AT$GPSODOM=?Response $GPSODOM: (0-3)

OK

Write Format N/AResponse

Read Format AT$ GPSODOM=Response $ GPSODOM:


34/65



Page 34 of 65

2.10 $GPSODOM GPS Odometer History(continued)


Parameter Values

0 = today1 = yesterday (1 day ago)2 = 2 days ago3 = 3 days ago

Reference N/A




35/65



Page 35 of 65

2.10 $GPSODOM GPS Odometer History(continued)

Notes Distance traveled within an hour is only

saved on top of every hour and during anIgnition off (if configured). Distance for thecurrent hour is not saved in the event of apower cycle.

Hour displayed is in Greenwich MeanTime (GMT) zone.


36/65



Page 36 of 65

2.11 GPS Overspeed Interval

$GPSOSI Set and Query the GPS overspeedinterval

Command Function This command allows the user to definethe criteria for a GPS overspeed event. AGPS overspeed event occurs when aminimum speed is maintained for aspecific duration of time.


Command Format Query AT$GPSOSI=?Response $GPSOSI: (0 65535),(0-65535)

OK

Write Format Response AT$GPSOSI=(0-65535),(0-65535)OK

Read Format Response AT$GPSOSI?$GPSOSI: , ,, , OK

Execution Format Response AT$GPSOSIERROR

Parameter Values

Speed, in nautical miles/hr, that must bemet and/or exceeded to trigger the GPSoverspeed event.

Number of consecutive seconds for which must be maintained to trigger theGPS overspeed event.

If 1, then and represent a GPS overspeed interval that iscurrently active. If 0, they represent theprevious GPS overspeed interval.


37/65



Page 37 of 65

2.11 $GPSOSI GPS Overspeed Interval(continued)

The highest speed that was attained in thecurrent or previous GPS overspeedinterval.

Number of consecutive seconds that thespeed was at or above .

Notes If is set to zero, the GPSoverspeed event is disabled.

This feature is available in softwareversion 0.7.8 pkg 43, and later.


38/65



Page 38 of 65

2.12 GPS Quality Filters

$GPSQUAL GPS QUALITY FILTERS

Command Function This command allows the user toset/query the filter values used todetermine when to interpret GPS data asvalid.


Command Format Query AT$GPSQUAL=?Response $GPSQUAL:(0-1), (0-255)

OK

Write Format AT$GPSQUAL=,Response OK

Read Format AT$GPSQUAL?Response $GPSQUAL:,


Parameter Values

0 (default) = consider GPS data valid if$GPGSA fix is either 2D GPS fix (2) or(3D) Differential GPS fix (3).

1 = consider GPS data valid only if$GPGSA fix is (3D) Differential GPS fix(3).

0 (default) = do not use HDOP value from

$GPGSA sentence when determiningwhether GPS is valid

1-255 = consider GPS data valid only ifHDOP value from $GPGSA sentence isless than or equal to indicated this HDOPlimit.


39/65


40/65



Page 40 of 65

2.13 GPS Read

$GPSRD Read current GPS ASCII data

Command Function This command allows a user to readcurrent NMEA format GPS data.


Command Format Query AT$GPSRD=?Response $GPSRD: [(0-3F),(0-63)], (0-1)

OK

Write Format N/A

Response N/A

Read Format AT$GPSRD=,$GPG.

Response OK


Parameter Values The output NMEA sentence depends onwhether the parameter isentered in Hex or Decimal format. By

default, the parameter is notrequired and parameter hasto be entered as HEX value without thepreceding 0x characters as outlined inHex Format table below.

This field is the sum of the type of NMEAmessages desired. A user has thefollowing message options to select from.Maximum value for in thiscase would be 3F in Hex format or 63 in

decimal format.


41/65



Page 41 of 65

2.13 $GPSRD Read current GPS ASCII data(continued)

Hex Format

UserSelectable

Type of NMEAMessage

0x01 GGA0x02 GLL0x04 GSA0x08 GSV0x10 RMC0x20 VTG

Decimal FormatUser

Selectable

Type of NMEA

Message1 GGA2 GLL4 GSA8 GSV16 RMC32 VTG

1 = value has to be sum ofUser Selectable values from decimal tableformat

0 = select values out of hex table format

Reference N/A



Notes N/A


42/65



Page 42 of 65

2.14 Ignition Debounce

$IGNDBNC Debounce Ignition hardware line for thespecified amount of time

Command Function This command allows a user to set ignitiondebounce time. The ignition line has to bevalid for the specified amount before theevent: GPIO-8 in the event engine will betriggered


Command Format Query AT$IGNDBNC=?Response $IGNDBNC: (04),

OK

Write Format Response AT$IGNDBNC=

Read Format Response AT$IGNDBNC?$IGNDBNC: 0OK


Parameter Values

0 4 seconds. This field specifies thedebounce timeout value.

Reference N/A



Notes If the ignition remains ON for less than orequal to $IGNDBNC, the device will reset.


43/65



Page 43 of 65

2.15 I/O Debounce

$IODBNC Debounce specified GPIO for thespecified amount of time

Command Function This command allows a user to set andquery GPIO debounce time. The GPIOmust be unchanged for the specifiednumber of seconds before the input eventwill be triggered.


Command Format Query AT$IODBNC=?Response $IODBNC: (1-8),(0-60)

OK

Write Format Response AT$IODBNC=,OK

Read Format Response AT$IODBNC?$IODBNC: , , ,, , , ,

OK

Execution Format Response AT$IODBNCERROR

Parameter Values

Number of GPIO whose debounce timeoutis being set.

Number of consecutive seconds must remain unchangedbefore its input event will be triggered.

Debounce timeout for GPIO1.



44/65



Page 44 of 65

2.16 $IODBNC I/O Debounce (continued)







Notes If is set to zero, will not be debounced.

$IGNDBNC is effected by this command.Changes made to GPIO8 will be seen via$IGNDBNC? Writes made by $IGNDBNCwill be seen by $IODBNC?

This feature is available in softwareversion 0.7.8 pkg 43, and later.


45/65



Page 45 of 65

2.16 Message Log Clear

$MSGLOGCL Message Log Clear

Command Function The $MSGLOGCL command erases thelog file.


Command Format Query N/AResponse N/A

Write Format N/A

Response N/A


Execution Format AT$MSGLOGCLResponse OK

Parameter Values None

ReferenceStandard Scope

Implementation Scope

Notes


46/65



Page 46 of 65

2.17 Message Log Dump

$MSGLOGDMP Dump Unsent Messages to Serial Port

Command Function This command allows the user to dumpthe contents of the unsent messages tothe serial port. This command is non-destructive in that it does not actuallyremove the messages from the queue.


Command Format Query AT$MSGLOGDMP=?Response $MSGLOGDMP:(0-3,(0-1)

OK

Write Format AT$MSGLOGDMP=,,

Response OK

Read Format N/AResponse


Parameter Values

0 = event data that was configured to besent to a remote server via GPRS only1 = event data that was configured to be

sent to a remote server via GPRSprimarily but also use SMS as backupmethod if GPRS is not available

2 = event data that was configured to besent to a remote server via SMS only

3 = event data that was configured to besent to a remote server via TCPAPIonly


47/65



Page 47 of 65

2.18 Message Log Enable

$MSGLOGEN Message Log Enable

Command Function The $MSGLOGEN command has beencreated to enable or disable saving GPSdata generated via the event engine inmodems memory


Command Format Query AT$MSGLOGEN=?Response $MSGLOGEN: (0-1)

OK

Write Format AT$MSLOGEN=Response OK

Read Format AT$MSGLOGEN?Response $MSGLOGEN:

Execution FormatResponse

Parameter Values

= 0 1 (possible valid values)

0 = Disable message logging (default).Event data is sent to the remote serverupon occurrence.

1 = Enable message logging. Event datahas to be read via AT$MSGLOGEN

command or whenAT$MSGLOGEN=0 is sent.




48/65


49/65



Page 49 of 65

2.19 Message Log Read Data

$MSGLOGRD Message Log Read Data

Command Function The $MSGLOGRD command has beencreated to read data from memory.


Command Format Query AT$MSGLOGRD=?Response $MSGLOGRD: (0-2),(0-x),(0-y)

OK



Execution Format AT$MSGLOGRD?Response $MSGLOGRD: ,,OK

Parameter Values

= 0 2 (possible valid values).

0 = event data that was configured to besent to a remote server via GPRSonly

1 = event data that was configured to besent to a remote server via GPRSprimarily but also use SMS as backupmethod if GPRS is not available

2 = event data that was configured to besent to a remote server via SMSonly


50/65



Page 50 of 65

2.20 $MSGLOGRD Message Log Read Data(continued)

= xx = total number of messages one

desires to read from the memory. Auser can choose to read 1 messagein which case x = 1 or read allmessages in which case x = 65535.

= yy = starting index number of messages

that are stored in the memory.

NOTE: y cannot be greater thanmaximum number of storedmessages.



Notes AT$MSGLOGRD? command returns 8values. The first two values correspond

to data stored for the GPRS queue. Thenext two values correspond to datastored for SMS AS BACKUP queue, andthe last two values correspond to datastored for SMS queue

Each value is comma (,) delimited. The first value of any queue represents

Total Number of Unread Messages.This value can be used as the field while reading

messages The second value of any queue

represents: Total Number ofMessages Stored for that Queue.Subtract the Total Number of UnreadMessages from the Total Number ofMessages Stored for that Queue anduse that as the


51/65



Page 51 of 65

2.20 $MSGLOGRD Message Log Read Data(continued)

index> of where to read data from inthe memory.


52/65



Page 52 of 65

2.20 Message Send

$MSGSND Message Send

Command Function The $MSGSND command has beencreated to allow sending of data fromone mode to another.


Command Format Query AT$MSGSND=?Response $MSGSND: (0-3),(ASCII DATA)

OK



Execution Format AT$MSGSND=, Response OK

Parameter Values

= 0 3 (possible Valid Values)0 = is sent out the serial port1 = is sent to all SMS

addresses listed in AT$SMSDAcommand.

2 = is sent via GPRS to first IPaddress, configured as server, in

AT$FRIEND command and portnumber defined by AT$UDPAPIcommand

3 = is sent via GPRS to IPaddress and Port number listed inthe AT$PADDST command

= a maximum of 50 bytes ASCIIcharacters


53/65



Page 53 of 65

2.21 $MSGSND Message Send(continued)

Reference

Standard Scope


Notes AT$MSGSND command can be sentto the MTG via SMS, UDP-API, or serialport


54/65



Page 54 of 65

2.21 Odometer

$ODOMETER MT Trip Odometer

Command Function The $ODOMETER command recordshow far the vehicle has traveled in onetrip. The user can reset the odometer atthe beginning of a new trip.


Command Format Query AT$ODOMETER=?

Response $ODOMETER: (0-4000000000)

Write Format AT$ODOMETER=1234 (where 1234 isdistance in meters)

Response OK

Read Format AT$ODOMETER?Response $ODOMETER xxxx (xxxx=distance

traveled in meters)

Execution FormatResponse

Parameter Values




55/65



Page 55 of 65

2.22 $ODOMETER Odometer(continued)

Notes The user shall be able to set a seedvalue for the Virtual Odometer (includinga value of 0 but not higher than themaximum value of 4000000000)

The AT&F command shall not reset theseed value to 0.

The Virtual Odometer reading would bea 4-byte value starting from 0 to4000000000 (maximum of

approximately 2500000 miles before itrolls over to 0)

The unit for Virtual Odometer shall be inMETERS.

The Virtual Odometer history shall beupdated every second

The Virtual Odometer history shall besaved once a minute in modem's

memory. This value shall be retainedthrough an internal or external reset andcan be read upon the next power up orduring run time mode. The deltadistance traveled between the minutemarks could be lost due to anunexpected external or non-modemoriginated reset. However, the totaldistance traveled till the prior minutewould still be preserved.


56/65



Page 56 of 65

2.22 Power Save

$PWRSAV Enable power save mode

Command Function This command allows a user to put thedevice in low power mode when DTR orIgnition line drops. The Ignition line hasto be connected per the user manual forthis feature to work properly. A user hasthe capability of getting a notificationwhen the device entering low powermode or returns to normal operatingmode.


Command Format Query AT$PWRSAV=?Response $PWRSAV: (0 1),(0 1),(0

65535),(0 1)OK

Write Format Response AT$PWRSAV=,,,OK

Read Format Response AT$PWRSAV?$PWRSAV: ,,,OK


Parameter Values

0 disable the DTR feature1 enter low power mode after DTRsignal went low and timeout has expired

0 disable the Ignition feature1 enter low power mode after Ignitionsignal went low and timeout has expired

0 65535 seconds. Timeout value afterwhich the unit will enter low powermode. Unit will work in normal mode


57/65



Page 57 of 65

2.23 $PWRSAV Enable power save mode(continued)

until the timeout has expired.

0 remain registered with GSM/GPRSnetwork during low power mode

1 reset modem when entering normalpower mode

Reference N/A



Notes An AT$EVENT command has to be setto send a GPS message to the remotehost when entering or exiting powersave mode.

If AND parameters are setto 1, then both DTR and Ignition mustbe low for seconds before

the unit will enter low power mode.

The white cable is the ignition line.


58/65



Page 58 of 65

2.23 Real Time Clock Alarm

$RTCALRM Real Time Clock Alarm Settings

Command Function This command handles the setting andquerying of the RTC alarm registers.When the alarm feature has been enabledthe $EVENT engine will be invoked uponthe going off. If the $RTCWAKE call isinvoked following the alarm feature setupthe modem will power back upautomatically upon the alarm going off.The actions of these two features aremutually exclusive of each other, so one or

the other will occur but not both.


Command Format Query AT$RTCALRM=?Response $RTCALRM: (0..99), (1..12), (1..31),

(0..23), (0..59), (0..59), (0..43200)OK

Write Format AT$RTCALRM= ,

Response , , ,, ,OK

Read Format AT$RTCALRM?Response $RTCALRM: , ,

, , ,, , OK



59/65



Page 59 of 65

2.24 $RTCALRM Real Time Clock Alarm(continued)

Parameter Values Parameters are positional dependent, any

parameter may be omitted with the use ofthe comma (,) as a place holder oncommand line. If a parameter is omittedthen the current value in the hardware isused.

< rtc_enabled > Indicates if alarm is enabled or not.1->Enabled, 0->Disabled

< rtc_year > The year on which the alarm is being setto trigger on. The RTC supports years

2000-2099. The data is entered as a twodigit value 0..99.

The month on which the alarm is being setto trigger on. Values range from 1..12.

The day on which the alarm is being set totrigger on. Values range from 1..31.

The hour on which the alarm is being setto trigger on. Values range from 0..24 for

24-Hour mode settings.NOTE: only 24-Hour mode currentlysupported.

The minute on which the alarm is being setto trigger on. Values range from 0..59.

The second on which the alarm is beingset to trigger on. Values range from 0..59.

Periodic Alarm time in minutes. RTC Alarm

will be reset at a period specified by thisparameter

Reference N/A




60/65


61/65



Page 61 of 65

2.24 Remote TAIP

$GPSRTP Enable remote TAIP messaging

Command Function This command enables the user toselect the OTA transmission method ofTAIP data


Command Format Query AT$GPSRTP=?Response $GPSRTP: (0 3)

OK

Write Format Response AT$GPSRTP=OK

Read Format Response AT$GPSRTP?$GPSRTP: OK


Parameter Values

0 disable sending of TAIP data OTA

1,2 Send TAIP data OTA via UDPto the first IP address listed in$FRIEND command3 Send TAIP data OTA via UDP to thefirst IP address in $FRIEND list only

Reference N/A



Notes N/A


62/65



Page 62 of 65

2.25 TAIP

$TAIP Enable the user to send TAIP data to

the GPS receiver

Command Function This command enables the user to sendTAIP data string to the GPS receiver itself


Command Format Query N/AResponse

Write Format Response AT$TAIP=>TAIP_commandTAIP_Command< See the TAIP reference manual for a list ofsupported TAIP commands.

Reference N/A



Notes N/A


63/65



Page 63 of 65

2.26 Script Version

$USRVAL Script Version

Command Function Allows the user to record an ASCII HEXnumber for event script versioning.


Command Format Query AT$USRVAL=?Response OK

Write Format AT$USRVAL=

Response OK

Read Format AT$USRVAL?Response $USRVAL:(hex value)

OK


Parameter Values

(0-FFFFFFFF)

Reference N/A




64/65



Page 64 of 65

Appendix A Default AT Values

$GPSLCL CONFIGURE SENDING OF LOCAL GPSMESSAGE

Default Value: 0Default Value Meaning: feature disabled

$GEOFNC Geo fencing a circle areaDefault Value: 1,0,0,0

2,0,0,03,0,0,04,0,0,0

5,0,0,06,0,0,07,0,0,08,0,0,09,0,0,010,0,0,011,0,0,012,0,0,013,0,0,014,0,0,015,0,0,0

16,0,0,017,0,0,018,0,0,019,0,0,020,0,0,021,0,0,022,0,0,023,0,0,024,0,0,025,0,0,0

Default Value Meaning: feature disabled

$GPSRD Read current GPS dataDefault Value: noneDefault Value Meaning: n/a

$PWRSAV Enable power save modeDefault Value: 0,0,0Default Value Meaning: feature disabled


65/65


$GPSRTP Enable remote TAIP messagingDefault Value: 0

Default Value Meaning: feature disabled

$TAIP Enable the user to send TAIP data to the GPSreceiver

Default Value: noneDefault Value Meaning: n/a

$EVENT User Defined Input/OutputDefault Value: Events 1 6 are configured. Event group 1 and 2

are associated with User LED 2 and GPS fix.Event group 3 6 are associated with User LED

1 and registration statusDefault Value Meaning: User LED 1 indicates registration status. UserLED 2 indicates GPS fix status

$NETMON Network MonitorDefault Value: 0,0Default Value Meaning: feature disabled

$GPSODOM GPS OdometerDefault Value: 0Default Value Meaning: no distance traveled.

skypatrol evolution - tt8740at001 - at commands - revision 1

Documents