Telit Communications S p A HE910NAV2 updated SW manual

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE
Notice
While reasonable efforts have been made to assure the accuracy of this document, Telit assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. The information in this document has been carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies or omissions. Telit reserves the right to make changes to any products described herein and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Telit does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others.
It is possible that this publication may contain references to, or information about Telit products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Telit intends to announce such Telit products, programming, or services in your country.
Copyrights
This instruction manual and the Telit products described in this instruction manual may be, include or describe copyrighted Telit material, such as computer programs stored in semiconductor memories or other media. Laws in the Italy and other countries preserve for Telit and its licensors certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Telit and its licensors contained herein or in the Telit products described in this instruction manual may not be copied, reproduced, distributed, merged or modified in any manner without the express written permission of Telit. Furthermore, the purchase of Telit products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Telit, as arises by operation of law in the sale of a product.
Computer Software Copyrights
The Telit and 3rd Party supplied Software (SW) products described in this instruction manual may include copyrighted Telit and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the Italy and other countries preserve for Telit and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, including the exclusive right to copy or reproduce in any form the copyrighted computer program. Accordingly, any copyrighted Telit or other 3rd Party supplied SW computer programs contained in the Telit products described in this instruction manual may not be copied (reverse engineered) or reproduced in any manner without the express written permission of Telit or the 3rd Party SW supplier. Furthermore, the purchase of Telit products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Telit or other 3rd Party supplied SW, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product.
Usage and Disclosure Restrictions License Agreements
The software described in this document is the property of Telit and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement.
Copyrighted Materials
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Telit
High Risk Materials
Components, units, or third-party products used in the product described herein are NOT fault-tolerant and are NOT designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities"). Telit and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
TELIT and the Stylized T Logo are registered in Trademark Office. All other product or service names are the property of their respective owners.
This document is intended for customers integrating HE910V2 modules in their project.
For general contact, technical support, to report documentation errors and to order manuals, contact Telit Technical Support Center (TTSC) at:
TS-EMEA@telit.com TS-NORTHAMERICA@telit.com TS-LATINAMERICA@telit.com TS-APAC@telit.com
Alternatively, use:
http://www.telit.com/en/products/technical-support-center/contact.php
For detailed information about where you can buy the Telit modules or for recommendations on accessories and components visit:
http://www.telit.com
To register for product news and announcements or for product questions contact Telit Technical Support Center (TTSC).
Our aim is to make this guide as helpful as possible. Keep us informed of your comments and suggestions for improvements.
Telit appreciates feedback from the users of our information.
This document contains the following chapters: “Chapter 1: “Introduction” provides a scope for this document, target audience, contact and
support information, and text conventions.
“Chapter 2: “Overview” gives an overview of the features described in the document.
“Chapter 3: “HE910V2 Family Products Specification” describes in details the characteristics
of the product, providing information such as power supply requirements, mechanical dimensions and interfaces specifics.
“Chapter 4: “Basic operations”: gives an overview on the basic operations using AT command: switch on/off, formatting, response, placing a voice call, etc.
“Chapter 5: “Advanced operations”: gives an overview on the advanced operations: access to phonebook, call handling, messages, GPIO setting, alarms, power consumption management etc.
“Chapter 6: “Packet switched data operations”: deals on the GPRS data management. It describes Enhanced Easy GPRS features.
“Chapter 7: “GPS operations”: describes GPS handling for HE910-EUG V2 and HE910-NAG V2. It provides an overview on NMES sentences, message formatting, GPS power management and serial ports for communications.
“Chapter 8: “Service and firmware update” describers the procedure and software tools used to update the firmware of HE910V2.
“Chapter 9: “Document History describers document history for HE910V2.
Danger – This information MUST be followed or catastrophic equipment failure or bodily injury may occur.
Caution or Warning – Alerts the user to important points about integrating the module, if these points are not followed, the module and end user equipment may fail or malfunction.
Tip or Information – Provides advice and suggestions that may be useful when integrating the module.
All dates are in ISO 8601 format, i.e. YYYY-MM-DD.
HE910V2 Hardware user guide 1vvxxx HE910V2 AT commands reference guide 80418ST10126A
The purpose of this document is the description of some common AT command procedures that may be used with the Telit HE910V2 family module. In this document, all the basic functions of a mobile phone are taken into account and for each one of them; a proper command sequence will be suggested. In the Advanced operation section the more useful services and features of the GSM and WCDMA network supported by the Telit HE910V2 family module is taken into account and some command sequence and usage are provided for each one of them. This document and its suggested command sequences must not be considered mandatory; instead, the information given must be used as a guide for properly using the Telit module. For further commands and features that may not be explained in this document refer to the HE910V2 family Product Description document where all the supported AT commands are reported.
NOTE: The integration of the HE910V2 module within user application shall be done according to
the design rules described in this manual
The information presented in this document is believed to be accurate and reliable. However, Telit Communications S.p.A. assumes no responsibility for its use, nor any infringement of patents or other rights of third parties, which may result from its use. No license is granted by implication or otherwise under any patent rights of Telit Communications S.p.A. other than for circuitry embodied in Telit products. This document is subject to change without notice.
Air
interface
Tri-band UMTS/HSPA 900/2100 Quad-Band GSM850/900/1800/1900
Tri-band UMTS/HSPA 850/2100 Quad-Band GSM850/900/1800/1900
Data
Service
HSPA UL 5.76 Mbps, DL 14Mbps WCDMA UL/DL 384kbps, EDGE UL/,DL 236.8Kbps, GPRS UL/DL 85.6 Kbps, CSD 9.6Kbps
In the following sections, HE910V2 family refers to all HE910V2 products mentioned in the table above. Whenever a command and/or feature is referred to a specific model, it is clearly highlighted
+COPS
125 (test command)
+CLCK
15 (SS operation)
5 (FDN enabling/disabling)
+CPWD
15 (SS operation)
5 (PIN modification)
+CLIP
15 (read command)
+CLIR
15 (read command)
+CCFC
15
In case no response is received after the timeout time has been elapsed, then try repeating the last command and if still no response is received until the timeout time, an Unconditional Shutdown MUST be issued and the device must be powered ON again.
In the next paragraphs the following notations are used: <cr> represents the Carriage Return Character (13) <lf> represents the Line Feed Character (10) <xx> represents a parameter with changing name is in place of the double x. (< and > characters are only for limiting the parameter and must not be issued to the terminal). [<xx>] represents an optional parameter whatever name is in place of the xx. [ and ] characters are only for limiting the optional parameter and must not be issued to the terminal).
Every command issued to the Telit modules returns a result response if response codes are enabled (default). The time needed to process the given command and return the response varies, depending on the command type. Commands that do not interact with the SIM or the network, and involve only internal set up settings or readings, have an immediate response, depending on SIM configuration(e.g., number of contacts stored in the phonebook, number of stored SMS), or on the network the command may interact with. In the table below are listed only the commands whose interaction with the SIM or the network could lead to long response timings. When not otherwise specified, timing is referred to set command. For phonebook and SMS writing and reading related commands, timing is referred to commands issued after phonebook sorting is completed. For DTMF sending and dialing commands timing is referred to module registered on network (“AT+CREG?” answer is “+CREG: 0,1” or “+CREG: 0,5”).
+CCWA
15
+CHLD
60
+CPIN
30
+CPBS
5 (FDN enabling/disabling)
+CPBR
5 (single reading)
15 (complete reading of a 500 records full phonebook)
+CPBF
10 (string present in a 500 records full phonebook)
5 (string not present)
+CPBW
5
+CACM
5
+CAMM
5
+CPUC
180
+VTS
20 (transmission of full “1234567890*#ABCD” string with no delay
between tones, default duration)
+CSCA
5 (read and set commands)
+CSAS
5
+CRES
5
+CMGS
120 after CTRL-Z; 1 to get ‘>’ prompt
+CMSS
120 after CTRL-Z; 1 to get ‘>’ prompt
+CMGW
5 after CTRL-Z; 1 to get ‘>’ prompt
+CMGD
5 (single SMS cancellation)
25 (cancellation of 50 SMS)
+CNMA
120 after CTRL-Z; 1 to get ‘>’ prompt
+CMGR
5
+CMGL
100
+CGACT
150
+CGATT
90
D
120 (voice call)
Timeout set with ATS7 (data call)
A
60 (voice call)
Timeout set with ATS7 (data call)
H
60
+CHUP
6
+COPN
10
+COPL
180
+CRSM
180
+FRH
Timeout set with ATS7
+FTH
Timeout set with ATS7
+FRM
Timeout set with ATS7
+FTM
Timeout set with ATS7
+FRS
Timeout set with the command itself
+FTS
Timeout set with the command itself
+WS 46
10
#MBN
10
#TONE
5 (if no duration specified)
#EMAILD
60
#EMAILACT
150
#SEMAIL
210 ( context activation + DNS resolution )
#MSCLASS
15
#STSR
30
#GPRS
150
#SKTD
140 (DNS resolution + timeout set with AT#SKTCT)
#SKTOP
290 ( context activation + DNS resolution + timeout set with AT#SKTCT)
#QDNS
170
#FTPOPEN
120 (timeout set with AT#FTPTO, in case no response is received from server)
#FTPCLOSE
500 (timeout set with AT#FTPTO, in case no response is received from server)
#FTPTYPE
500 (timeout set with AT#FTPTO, in case no response is received from server)
#FTPDELE
500 (timeout set with AT#FTPTO, in case no response is received from server)
#FTPPWD
500 (timeout set with AT#FTPTO, in case no response is received from server)
#FTPCWD
500 (timeout set with AT#FTPTO, in case no response is received from server)
#FTPLIST
500 (timeout set with AT#FTPTO, in case no response is received from server) + time to get listing
#FTPPUT
500 (timeout set with AT#FTPTO, in case no response is received from server)
#SGACT
150
#SH
10
#SD
140 (DNS resolution + connection timeout set with AT#SCFG)
#CSURV
125
#CSURVC
125
#CSURVUC
125
#CSURVB
125
#CSURVBC
125
#CSURVP
125
#CSURVPC
125
Please refer to HE910V2 Hardware User Guide
After a proper power on, the device is ready to receive AT commands on the USB or serial port.
Several things must be checked in order to be sure that the device is ready to send and receive calls and SMS.
HE910V2 family does not support autobauding. Users have to set the right speed for serial communication before device initialization. If HE910V2 family set the right speed, the device responds with OK. The default baudrate is 115200.
send command AT+IPR=<rate><cr> wait for OK response
where rate is the port speed and can be 300,600,1200,2400,4800,9600,19200,38400,57600,115200,230400,460800,3200000,4000000 bps.
The USB or serial port suggested setting is: port speed 115200, character format 8N1 (8 bit per char, No parity bit, and 1 stop bit)
The first thing to check is the SIM presence and PIN code insertion. This can be done with the following commands:
send command AT+CMEE=1<cr> wait for OK response or if you prefer the verbose format instead of the numerical format then: send
command AT+CMEE=2<cr>
wait for OK response
Response
Reason
Action
+CPIN: SIM PIN
SIM is present and PIN is required to continue
operations
Proceed to par. 4.4.2.3
+CPIN: SIM PUK
SIM is present and 10 attempts to give SIM
PIN have failed, so SIM is blocked
Send command
AT+CPIN=<SIM PUK>
+CPIN: SIM PIN2
SIM is present and 3 attempts to give SIM
PIN2 have failed, so SIM PUK2 is required
Proceed to par. 4.4.2.3
+CPIN: SIM PUK2
SIM is present and 10 attempts to give SIM PUK2 have failed, so SIM PIN2 cannot use
anymore.
Send command
AT+CPIN=<SIM PUK>
+CPIN: READY
SIM is present and no PIN code is required to
proceed
Proceed ahead
+CME ERROR: 10
SIM is not inserted
Insert SIM or require SIM
insertion and repeat from par.
4.4.2.2
+CME ERROR: 13
SIM is failure
Check SIM insertion or require a new SIM not defected and repeat
from par. 4.4.2.2
+CME ERROR: 14
SIM is busy
retry later
+CME ERROR: 15
SIM is wrong type
Check SIM, it must be a GSM SIM
or UMTS SIM(USIM).
+CME ERROR: 770
SIM is permanent blocked
Change valid SIM card
Response
Reason
Action
OK
SIM PIN was correct
Proceed ahead
ERROR
the PIN code inserted is not correct
Retry from par. 4.4.2.2
send command AT+CPIN?<cr> wait for response:
send command AT+CPIN=****<cr> where **** stands for the SIM PIN code
(e.g. 1234)
wait for response:
When receiving the ERROR message, repeat Query SIM presence and status since after 3 failed attempts SIM PIN is not requested anymore, but SIM PUK is requested instead. You may need to go through procedure 0
send command AT+CPIN=*******,<newpin><cr> where ******* stands for
the SIM PUK code (e.g. 12345678) and <newpin> (e.g. 1234) will replace the old pin in the SIM.
wait for response:
Response
Reason
Action
OK
SIM PUK was correct
Proceed ahead
ERROR
the SIM PUK code inserted is not correct
Retry from par. 0
Response
Reason
Action
+CME ERROR: 10
SIM not present or damaged
Check SIM or require SIM
insertion and repeat from par.
4.4.2.2
+CME ERROR: 11
SIM is present and PIN is required to
continue operations
Repeat par. 4.4.2.3
+CREG: 0,0
or
+CREG: 1,0
No network is found
Check for antenna cable
connection (antenna may be
disconnected or damaged) or
change position if the antenna is
OK. Repeat par. 4.4.3.1 until a
network is found.
+CREG: 0,1
or
+CREG: 1,1
Mobile is registered on its home network.
Proceed ahead. Ready to call
+CREG: 0,2
or
+CREG: 1,2
Mobile is currently not registered on any
network but is looking for a suitable one to
register.
Repeat procedure at par. 4.4.3.1 to
see if it has found a suitable
network to register in.
+CREG: 0,3
or
+CREG: 1,3
Mobile has found some networks but it is not
allowed to register on any of them, no
roaming was allowed.
Try in another place, and repeat
procedure at par. 4.4.3.1
+CREG: 0,4
or
+CREG: 1,4
Mobile is in an unknown network status
Repeat procedure at par. 4.4.3.1 to
see if it has found a suitable
network to register in
+CREG: 0,5
or
+CREG: 1,5
Mobile has found some networks and is
currently registered in roaming on one of
them
Proceed ahead. Ready to call
When receiving the ERROR message, be careful to check if the SIM PUK is correct before trying again. After 10 failed attempts to provide the SIM PUK the SIM Card will lock and will not be usable anymore.
send command AT+CREG?<cr> wait for response:
When a response +CREG: x,1 or +CREG: x,5 is received, then the device is ready to place and receive a call or SMS. It is possible to jump directly to call setup procedures or SMS sending procedures.
Once the mobile has registered on some network (or even if it has returned +CREG:x,3), it is possible to query the mobile for network identifications, codes and names:
send command AT+COPS=?<cr> wait for response in the format:
+COPS: : [list of supported (<stat>,long alphanumeric <oper>,short alphanumeric <oper>,numeric <oper>,< AcT>)s]
[,,(list of supported <mode>s),(list of supported <format>s)]
where: <stat> - operator availability 0 - unknown 1 - available 2 - current 3 - forbidden <AcT> access technology selected: 0 GSM 2 UTRAN
Since with this command a network scan is done, this command may require some seconds before the output is given.
For example: command
AT+COPS=?<cr>
Answer:
+COPS: (2,"I WIND","WIND","22288",2),(1,"SI MOBITEL GSM","","29341",0),(1,"Vodafone IT","OMNITEL","22210",2), (3,"I TIM","TIM","22201",0),,(0-4),(0-2)
OK
In this case the mobile is registered on the network "I WIND" which is a network from Italy, code: 222 and Network ID: 88. There is also another network available for registration:
"SI MOBITEL GSM" which is a network from Slovenia, code: 293 and Network ID: 41 ,
"SI.MOBIL" which is a network from Slovenia, code: 293 and Network ID: 40 and
<rssi> value
Signal Strength
Indication
0
-113 dBm or less
Signal is VERY low: at the extreme sensibility limit
1
-111 dBm
MMI may indicate only 1 antenna bar
2
-109 dBm
MMI may indicate only 1 antenna bar
3
-107 dBm
MMI may indicate only 1 antenna bar
4
-105 dBm
MMI may indicate only 1 antenna bar
5
-103 dBm
MMI may indicate only 1 antenna bar
6
-101 dBm
MMI may indicate 2 antenna bars
7
-99 dBm
MMI may indicate 2 antenna bars
8
-97 dBm
MMI may indicate 2 antenna bars
9
-95 dBm
MMI may indicate 2 antenna bars
10
-93 dBm
MMI may indicate 3 antenna bars
Vodafone IT from Italy with Nation code 22 and Network 10. The other network is not available for registration:
This command issues a network request and it may require quite a long time to respond, since the device has to wait the answer from the network (it can be as long as 60 seconds). Do not use this command if not necessary.
"I TIM" from Italy, code: 222 and Network ID: 01 – FORBIDDEN
In this case an "I TIM" logo might be reproduced on the MMI to give the user the information that is registered on that network.
Once the mobile has registered on one network, it may be useful to know the received signal strength & quality to give the user an indication of the reliability of the network.
send command AT+CSQ<cr> wait for response in the format:
<WCDMA network > +CSQ: <rssi>,99 OK <GSM network> +CSQ: <rssi>,<ber> OK
where: <rssi> is an integer from 0 to 99 that indicates the received signal strength:
11
-91 dBm
MMI may indicate 3 antenna bars
12
-89 dBm
MMI may indicate 3 antenna bars
13
-87 dBm
MMI may indicate 3 antenna bars
14
-85 dBm
MMI may indicate 3 antenna bars
15
-83 dBm
MMI may indicate 4 antenna bars
16
-81 dBm
MMI may indicate 4 antenna bars
17
-79 dBm
MMI may indicate 4 antenna bars
18
-77 dBm
MMI may indicate 4 antenna bars
19
-75 dBm
MMI may indicate 4 antenna bars
20
-73 dBm
MMI may indicate 4 antenna bars
21
-71 dBm
MMI may indicate 4 antenna bars
22
-69 dBm
MMI may indicate 4 antenna bars
23
-67 dBm
MMI may indicate 4 antenna bars
24
-65 dBm
MMI may indicate 4 antenna bars
25
-63 dBm
MMI may indicate 4 antenna bars
26
-61 dBm
MMI may indicate 4 antenna bars
27
-59 dBm
MMI may indicate 4 antenna bars
28
-57 dBm
MMI may indicate 4 antenna bars
29
-55 dBm
MMI may indicate 4 antenna bars
30
-53 dBm
MMI may indicate 4 antenna bars
31
-51 dBm or more
MMI may indicate 4 antenna bars
99
not detected
MMI may indicate flashing antenna bars
When <rssi> is less than 6, with only 1 MMI antenna bar, the quality of a call will be poor and the call may even drop.
<ber> is an integer from 0 to 7 and 99 that reports the received signal quality measured on the radio traffic channel.
The quality is measured on the traffic channel. It is available only during a conversation. In Idle the reported value must not be considered.
In conversation the quality decreases with the increase of the <ber> number. The <ber> value refers strictly to the GSM radio channel and is a very technical parameter. It
can be used to monitor the voice call quality since the voice quality is inversely proportional to the <ber> number. HE910V2 family doesn’t support ber in WCDMA network so the return value fixed as 99.
Once the mobile has registered on one network, it may be useful to know the received signal strength and the network on which the mobile is registered. These information can be gathered with the commands +CREG, +COPS and +CSQ, which are part of the standard 3gpp GSM 07.07/27.007 commands as seen before, unfortunately these commands are not so fast in the response due to network response time, especially the +COPS command. If You
want to keep your software as general as possible you can follow the indications given before and forget this part; instead if you need or want a faster way to check at the mobile network information, the HE910V2 family provides a special command #MONI which can be used to gather all the information needed in a faster and simpler way:
send command AT#MONI=0<cr> wait for OK response send command AT#MONI?<cr>
wait for response in the format:
When extracting data for the serving cell and the network name is known the format is:
(GSM network) #MONI: <netname> BSIC:<bsic> RxQual:<qual> LAC:<lac> Id:<id>
ARFCN:<arfcn> PWR:<dBm> dBm TA: <timadv>
(WCDMA network)
#MONI: <netmame> PSC:<psc> RSCP:<rscp> LAC:<lac> Id:<id> EcIo:<ecio> UARFCN:<uarfcn> PWR:<dBm> dBm DRX:<drx> SCR:<scr>
When the network name is unknown, the format is: (GSM network)
#MONI: Cc:<cc> Nc:<nc> BSIC:<bsic> RxQual:<qual> LAC:<lac> Id:<id> ARFCN:<arfcn> PWR:<dBm> dBm TA: <timadv>
(WCDMA network)
#MONI: Cc:<cc> Nc:<nc> PSC:<psc> RSCP:<rscp> LAC:,<lac> Id:<id> EcIo:<ecio> UARFCN:<uarfcn> PWR:<dBm> dBm DRX:<drx> SCR:<scr>
When extracting data for an adjacent cell, the format is: (GSM network)
#MONI: Adj Cell<n> [LAC:<lac> Id:<id>] ARFCN:<arfcn> PWR:<dBm> dBm
(WCDMA network)
#MONI: PSC:<psc> RSCP:<rscp> EcIo:<ecio> UARFCN:<uarfcn> SCR:<scr>
Where:
<netname> - name of network operator <cc> - country code <nc> - network operator code <n> - progressive number of adjacent cell <bsic> - base station identification code <qual> - quality of reception
0..7
<lac> - localization area code
<id> - cell identifier <arfcn> - assigned radio channel <dBm> - received signal strength in dBm <timadv> - timing advance <psc> - primary synchronisation code <rscp> - Received Signal Code Power in dBm <ecio> - chip energy per total wideband power in dBm <uarfcn> - UMTS assigned radio channel <drx> - Discontinuous reception cycle length <scr> - Scrambling code
TA: <timadv> is reported only for the serving cell.
When the last setting done is AT#MONI=7, then the Read command reports the above pieces of information for each of the cells in the neighbor of the serving cell, formatting them in a sequence of <CR><LF>-terminated strings. Currently this is available in case of GSM network.
For example (WCDMA):
at#moni=0<cr> OK At#moni<cr> #MONI: Welcome to KTF PSC:270 RSCP:-76 LAC:5121 EcIo:-3.5 UARFCN:10812
PWR:-73 dBm DRX:64 OK at#moni=1<cr> OK at#moni<cr> #MONI: Sync NSet PSC:408 RSCP:-86 EcIo:-13.5 UARFCN:10812 #MONI: Sync NSet PSC:102 RSCP:-104 EcIo:-31.5 UARFCN:10812 OK
In this case the mobile is registered on the network whose Country code is 010 and Network operator code is 03, the signal strength is -83dBm (MMI may indicate 4 antenna bars as reported on the table 5). Other information received is strictly technical and must not be given to the user.
The values reported are random and have no meaning. They are used only to explain command usage.
This command must be used only to gather information on network name and signal strength, to check if mobile is registered or is looking for a suitable network to register. Always use the +CREG command. This is due to the fact that if the network signal is too weak and mobile loses the registration. Until a new network is found the #MONI command reports the last measured valid values and not the real ones.
The TA (timing advance parameter) is valid only during a call. To properly use this feature, check network registration with command +CREG as seen on
par. 2.7.3.1 and when mobile is registered query the mobile for network operator name and signal strength with #MONI command.
Before a voice call can be placed, it is recommended to check if the mobile is registered on a network (see par. 4.4.3.1) and if the signal strength is enough to ensure a call can be made.
send command AT+FCLASS=8<cr> wait for OK response
This command may be omitted if the modifier ";" is added at the end of the ATD command after the dialed number.
The HE910V2 family has three different audio paths:
PCM microphone/ear(PCM)
Usually the internal path is used for a handset function, while the external is used for handsfree function. There are two ways to switch between these two paths:
SOFTWARE: by using the command AT#CAP= <n> (with n=1 OR n=2) HARDWARE: by setting AT#CAP=0 and setting the AXE input high (internal
MT) or low (external HF).
If only one path is needed, then it is preferable to use the internal one (MT).
When Hardware control is not needed AXE pin can be left unconnected. The audio paths can also be switched in both ways during a call.
send command AT#CAP=<n><cr>
Where:
<n> = 0 for HARDWARE control with AXE input <n> = 1 for external HF path (regardless of the AXE input status) <n> = 2 for internal MT path (regardless of the AXE input status)
wait for OK response
For example: 1 - Let us assume that the desired audio path is always the internal MT Command
AT#CAP=2<cr>
Answer
OK
2 - Let us assume that the desired audio path has to be determined by HARDWARE pin AXE Command
AT#CAP=0<cr>
Answer
OK
Now set the hardware pin AXE in the desired status. Set the desired volume on the active audio path speaker output This setting is not strictly necessary; it is also possible to keep the default volume setting.
send command AT+CLVL=<vol><cr>
Where: <vol> is a number between 0 and 10 representing the volume setting: 0 - minimum volume 10 - maximum volume
wait for OK response
The volume setting refers to the ACTIVE path ear line and is stored each time. When changing audio path, the volume setting will be reset to the previously stored value for that audio path.
The microphone of the active path can be muted with an AT command; to be sure that it is not muted, it is suggested to check it with this command
Send command AT+CMUT?<cr>
wait for response in the format:
Response
Reason
Action
OK
The call has been placed
Wait for the other party to lift the
receiver
BUSY
The line called is busy
retry later
NO ANSWER
The receiver did not answer the
call
retry later
NO CARRIER
Call placing has not been
successful
check for mobile registration and
signal strength
+CMUT: <mute> OK
where: <mute> is the muting setting for the microphone: 0 - microphone active 1 - microphone muted
The mute setting is different from Volume setting: it refers to both the audio paths, the mute setting will remain even when changing audio path.
Send command ATD <PhoneNumber><cr> where: <PhoneNumber> is the phone number to be dialed wait for response:
For example: 1- Let us assume you have to call the national number 040 - 4192111, command
ATD 0404192111<cr>
response
OK
2- Let us assume you have to call the national number but in international format +39-40­4192111,
command
ATD +39404192111<cr>
response
OK
3- Let us assume you have to call the international number +386-40-4192111 without previously setting the +FCLASS=8 (voice),
command
ATD +386404192111;<cr>
response
OK
send command AT+CHUP<cr> wait for response OK
During the voice call the device remains in command mode, so the escape sequence (+++) must not be issued before sending commands.
Before a data call can be placed, it is recommended to check if the mobile is registered on a network (see par. 2.7.3.1) and if the signal strength is enough to ensure that a call can be made.
send command AT+FCLASS=0<cr> wait for OK response
The +FCLASS setting is maintained in the memory and there is no need to repeat this command if +FCLASS setting is not changed.
Command
Modulation
Speed
[bps]
Connection Element
AT+CBST=0,0,1
V.32
9600
non transparent
AT+CBST=14,0,1
V.34
14400
non transparent
AT+CBST=16,0,1
V.34
28800
non transparent
AT+CBST=17,0,1
V.34
33600
non transparent
AT+CBST=43,0,1
V.120
14400
non transparent
AT+CBST=48,0,1
V.120
28800
non transparent
AT+CBST=51,0,1
V.120
56000
non transparent
AT+CBST=75,0,1
V.110/ X.31
14400
non transparent
AT+CBST=80,0,1
V.110 / X.31
28800
non transparent
AT+CBST=81,0,1
V.110 / X.31
38400
non transparent
AT+CBST=83,0,1
V.110/ X.31
56000
non transparent
AT+CBST=83,4,1
V.110/ X.31
56000 RDI
non transparent
AT+CBST=84,0,1
X.31
64000
non transparent
AT+CBST=116,1,0
Bit transparent
64000
transparent
AT+CBST=134,1,0
multimedia
64000
transparent
Command
Modulation
Speed
[bps]
Connection Element
AT+CBST=0,0,1
V.32
9600
non transparent
AT+CBST=7,0,1
V.32
9600
non transparent
AT+CBST=12,0,1
V.34
9600
non transparent
AT+CBST=14,0,1
V.34
14400
non transparent
AT+CBST=39,0,1
V.120
9600
non transparent
AT+CBST=43,0,1
V.120
14400
non transparent
AT+CBST=71,0,1
V110/ X.31
9600
non transparent
AT+CBST=75,0,1
V.110/ X.31
14400
non transparent
AT+CBST=7,0,0
V.32
9600
transparent
AT+CBST=12,0,0
V.34
9600
transparent
AT+CBST=14,0,0
V.34
14400
transparent
The data connection can be made using different modulations at different speeds. This connection mode can be selected with the command +CBST. The syntax for the command is:
AT+CBST=<mod>,0,<ce>
These parameters can be selected as seen in the table:
<WCDMA network>
<GSM network>
Once selected the appropriate <mod > and <ce> parameters from the table:
send command AT+CBST=<mod>,0,<ce><cr> wait for OK response
Response
Reason
Action
CONNECT 9600
The called modem is now on line.
exchange data
BUSY
The line called is busy
retry later
NO ANSWER
The receiver did not answer the call
retry later
NO CARRIER
The modem handshaking has not been
successful
Check for mobile registration and
signal strength and eventually
retry.
send command ATD <PhoneNumber><cr> where:
<PhoneNumber> is the phone number to be dialed wait for response:
The response to the ATD command is returned after the modem handshaking, this takes about 30 seconds, so allow this time before doing anything.
When the device is doing the handshake the issue of any character closing the handshake aborts the call.
For example: 1- Let us assume you have to call the national number 040 - 4192111, command
ATD 0404192111<cr>
response
CONNECT 9600
2- Let us assume you have to call the national number but in international format +39-40­4192111,
command
ATD +39404192111<cr>
response
CONNECT 9600
3- Let us assume you have to call the international number +386-40-4192111, command
ATD +386404192111<cr>
response
Loading...
+ 90 hidden pages