Product is deemed accepted by recipient and is provided without interface to recipient’s products. The documentation and/or product are provided for testing, evaluation, integration and information purposes. The documentation and/or product are provided on an “as is” basis only and may contain deficiencies or inadequacies. The
documentation and/or product are provided without warranty of any kind, express or implied. To the maximum
extent permitted by applicable law, Siemens further disclaims all warranties, including without limitation any implied warranties of merchantability, completeness, fitness for a particular purpose and non-infringement of thirdparty rights. The entire risk arising out of the use or performance of the product and documentation remains with
recipient. This product is not intended for use in life support appliances, devices or systems where a malfunction
of the product can reasonably be expected to result in personal injury. Applications incorporating the described
product must be designed to be in accordance with the technical specifications provided in these guidelines. Failure to comply with any of the required procedures can result in malfunctions or serious discrepancies in results.
Furthermore, all safety instructions regarding the use of mobile technical systems, including GSM products,
which also apply to cellular phones must be followed. Siemens or its suppliers shall, regardless of any legal theory upon which the claim is based, not be liable for any consequential, incidental, direct, indirect, punitive or other
damages whatsoever (including, without limitation, damages for loss of business profits, business interruption,
loss of business information or data, or other pecuniary loss) arising out the use of or inability to use the documentation and/or product, even if Siemens has been advised of the possibility of such damages. The foregoing
limitations of liability shall not apply in case of mandatory liability, e.g. under the German Product Liability Act, in
case of intent, gross negligence, injury of life, body or health, or breach of a condition which goes to the root of
the contract. However, claims for damages arising from a breach of a condition, which goes to the root of the
contract, shall be limited to the foreseeable damage, which is intrinsic to the contract, unless caused by intent or
gross negligence or based on liability for injury of life, body or health. The above provision does not imply a
change on the burden of proof to the detriment of the recipient. Subject to change without notice at any time. The
interpretation of this general note shall be governed and construed according to German law without reference
to any other substantive law.
MC55 AT Command Set
01.05
February 10, 2004
MC55_ATC_V01.05
Confidential / Released
Copyright
Transmittal, reproduction, dissemination and/or editing of this document as well as utilization of its contents and
communication thereof to others without express authorization are prohibited. Offenders will be held liable for
payment of damages. All rights created by patent grant or registration of a utility model or design patent are reserved.
MC55_ATC_V01.05Page 12 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1. Introduction
s
m
obil
e
1.Introduction
1.1Scope of the document
This document presents the AT Command Set for the Siemens Cellular Engine
MC55 Version 01.05.
Before using the Cellular Engine or upgrading to a new firmware version please read the latest product information provided in the Release Notes [1].
More information is available at the Siemens Website: http://www.siemens.com/wm
.
MC55_ATC_V01.05Page 13 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.2 Related documents
s
m
obil
e
1.2Related documents
[1] Release Notes: MC55, Version 01.05
[2] MC55 Hardware Interface Description, Version 01.05
[3] GPRS Startup User's Guide
[4] Remote-SAT User's Guide
[5] Multiplexer User's Guide
[6] Application Note 16: Updating MC55 Firmware
[7] Application Note 02: Audio Interface Design
[8] Multiplex Driver Developer's Guide for Windows 2000 and Windows XP
[9] Multiplex Driver Installation Guide for Windows 2000 and Windows XP
[10] Application Note 22: Using TTY / CTM equipment with MC55
[11] ISO/IEC10646: "Universal Multiple-Octet Coded Character Set (UCS)"; UCS2, 16 bit coding
[12] ITU-T Recommendation V.24: List of definitions for interchange circuits between data terminal equipment
(DTE) and data circuit-terminating equipment (DCE)
[13] ITU-T Recommendation V.25ter: Serial asynchronous automatic dialling and control
[14] 3GPP TS 23.038 (GSM 03.38): Alphabets and language specific information
[15] 3GPP TS 27.005 (GSM 07.05): Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE
- DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)
[16] 3GPP TS 27.007 (GSM 07.07): AT command set for User Equipment (UE)
[17] 3GPP TS 27.060 (GSM 07.60): Mobile Station (MS) supporting Packet Switched Services
[18] 3GPP TS 51.011 (GSM 11.11): Specification of the Subscriber Identity Module - Mobile Equipment (SIM -
ME) interface
[19] 3GPP TS 11.14 (GSM 11.14): Specification of the SIM Application Toolkit for the Subscriber Identity Module
- Mobile Equipment (SIM - ME) interface
MC55_ATC_V01.05Page 14 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.3 Document conventions
s
m
obil
e
1.3Document conventions
Throughout the document, the GSM engines are referred to as ME (Mobile Equipment), MS (Mobile Station), TA
(Terminal Adapter), DCE (Data Communication Equipment) or facsimile DCE (FAX modem, FAX board).
To control your GSM engine you can simply send AT Commands via its serial interface. The controlling device
at the other end of the serial line is referred to as TE (Terminal Equipment), DTE (Data Terminal Equipment) or
plainly 'the application' (probably running on an embedded system).
All abbreviations and acronyms used throughout this document are based on the GSM specifications. For definitions please refer to TR 100 350 V7.0.0 (1999-08), (GSM 01.04, version 7.0.0 release 1998).
1.3.1Quick reference table
Each AT command description includes a table similar to the example shown below. The table is intended as a
quick reference to indicate the following functions:
PIN:Is the AT command PIN protected?
%Yes
!No
§Usage is dependent on conditions specified for the command, or not all command types are PIN
protected (for example write command PIN protected, read command not).
Note: The table provided in the Chapter Available AT Commands and Dependency on SIM PIN
uses the same symbols.
ASC0:Is the AT command supported on the first physical serial interface ASC0?
%Yes
!No
ASC1:Is the AT command supported on the second physical serial interface ASC1?
%Yes
!No
MUXn: Is the AT command usable on the Multiplexer channels MUX1, MUX2, MUX3?
%Yes
!No
§AT command is usable, but under the restrictions specified in the chapter related to the com-
mand.
Note: The columns MUX1, MUX2 and MUX3 are relevant only when the GSM engine operates in Mul-
tiplexer mode, that is, when the first physical serial interface is partitioned into 3 virtual channels
by using the Multiplexer protocol. Usage is the same on ASC0 and MUX1.
Example:
PINASC0ASC1MUX1MUX2MUX3
!%%§§§
MC55_ATC_V01.05Page 15 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.3 Document conventions
s
1.3.2Superscript notation for parameters and values
Table 1.1: Symbols used to indicate the correlations with other commands
Parameter optionMeaning
<param>
<param>
<param>
<param>
Table 1.2: Symbols used to mark different types of default values of parameters
Value optionMeaning
[x]Default value: if the parameter is omitted, the value 'x' will be assumed
(&F)
x
(P)
x
(D)
x
(&W)
(&V)
(ˆSNFW)
(+CSCS)
Parameter value will be stored with AT&W
Parameter value will be displayed with AT&V
Parameter value will be stored with AT^SNFW
Parameter value has to be (is) coded according to current setting of <chset> (see
AT+CSCS for details)
Factory default value, will be restored to 'x' with AT&F
Powerup default value of a parameter which is not stored at power down
Delivery default value of a parameter which cannot be restored automatically
m
obil
e
MC55_ATC_V01.05Page 16 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.4 AT command syntax
s
m
obil
e
1.4AT command syntax
The "AT" or "at" prefix must be set at the beginning of each command line. To terminate a command line enter
<CR>.
Commands are usually followed by a response that includes "
document, only the responses are presented,
Types of AT commands and responses:
AT command typeSyntaxFunction
Test commandAT+CXXX=?The mobile equipment returns the
Read commandAT+CXXX?This command returns the currently
<CR><LF> are omitted intentionally.
<CR><LF><response><CR><LF>". Throughout this
list of parameters and value ranges
set with the corresponding Write
command or by internal processes.
non-variable parameters determined by internal processes in the
GSM engine.
1.4.1Using parameters
•Optional parameters are enclosed in square brackets. If optional parameters are omitted, the current settings
are used until you change them.
•Optional parameters or subparameters can be omitted unless they are followed by other parameters. If you
want to omit a parameter in the middle of a string it must be replaced by a comma. See also example 1.
•A parameter value enclosed in square brackets represents the value that will be used if an optional parameter
is omitted. See also example 2.
•When the parameter is a character string, e.g.
marks, e.g. "Charlie Brown" or "+49030xxxx". Symbols within quotation marks will be recognized as strings.
•All spaces will be ignored when using strings without quotaton marks.
•It is possible to omit the leading zeros of strings which represent numbers.
•If an optional parameter of a V.25ter command is omitted, its value is assumed to be 0.
<text> or <number>, the string must be enclosed in quotation
MC55_ATC_V01.05Page 17 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.4 AT command syntax
Example 1: Omitting parameters in the middle of a string
s
m
obil
e
AT+CCUG?
+CCUG: 1,10,1
OK
AT+CCUG=,9
OK
AT+CCUG?
+CCUG: 1,9,1
OK
Example 2: Using default parameter values for optional parameters
AT+CFUN=5,0
OK
AT+CFUN?
+CFUN: 5
OK
AT+CFUN=
OK
+CFUN: 1
OK
Query current setting
Set only the middle parameter
Query new setting
Activate CYCLIC SLEEP mode, don't reset ME
Query ME mode
Set ME back to normal (default parameters: 1,0)
1.4.2Combining AT commands on the same command line
You may enter several AT commands on the same line. This eliminates the need to type the "AT" or "at" prefix
before each command. Instead, it is only needed once at the beginning of the command line. Use a semicolon
as command delimiter.
The command line buffer accepts a maximum of 391 characters. If this number is exceeded none of the commands will be executed and TA returns ERROR.
The table below lists the AT commands you cannot enter together with other commands on the same line. Otherwise, the responses may not be in the expected order.
Note: When concatenating AT commands please keep in mind that the sequence of processing may be different
from the sequential order of command input. Therefore, if the consecutive order of the issued commands is your
concern, avoid concatenating commands on the same line.
MC55_ATC_V01.05Page 18 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.5 Supported character sets
s
m
obil
e
1.5Supported character sets
The ME supports two character sets: GSM 03.38 (7 bit, also referred to as GSM alphabet or SMS alphabet) and
UCS2 (16 bit, refer to ISO/IEC 10646). See
tables can be found below.
Explanation of terms
•IRA
IRA means that one byte is displayed as two characters in hexadecimal format. for example, the byte 0x36
(decimal 54) is displayed as "36" (two chars).
•Escape sequences
The escape sequence used within a text coded in the GSM default alphabet (0x1B) must be correctly interpreted by the TE, both for character input and output. To the module, an escape sequence appears like any
other byte received or sent.
•TE
TE is the terminal equipment that uses the GSM default alphabet as its character set. MS Hyperterminal
(often used with the module) is an ANSI / ASCII terminal that does not support the GSM default alphabet.
•Data Coding Scheme
The Data Coding Scheme (dcs) is part of a short message and is saved on the SIM. When writing a short
message to the SIM in textmode, the dcs stored with AT+CSMP is used.
•TE Character Set
The currently used TE character set is selected with AT+CSCS.
AT+CSCS for information about selecting the character set. Character
The behavior when encountering characters, that are not valid characters of the supported alphabets, is undefined.
Due to the constraints described below it is recommended to prefer the USC2 alphabet in any external application.
If the GSM alphabet is selected all characters sent over the serial line are in the range from 0 ... 127. CAUTION:
GSM alphabet is not ASCII alphabet!
Several problems resulting from the use of the GSM alphabet:
•"@" character with GSM alphabet value of binary 0 will terminate any C string! This is because the 0 is defined
as C string end tag. Therefore, the GSM Null character may cause problems on application level when using
a 'C'-function as "strlen()". This can be avoided if it is represented by an escape sequence as shown in the
table below.
By the way, this may be the reason why even network providers often replace "@"with "@=*" in their SIM
application.
•Other characters of the GSM alphabet are misinterpreted by an ASCII terminal program. For example, GSM
"ö" (as in "Börse") is assumed to be "|" in ASCII, thus resulting in "B|rse". This is because both alphabets mean
different characters with values hex. 7C or 00 and so on.
•In addition, decimal 17 and 19 which are used as XON/XOFF control characters when software flow control
is activated, are interpreted as normal characters in the GSM alphabet.
When you write characters differently coded in ASCII and GSM (e.g. Ä, Ö, Ü), you need to enter escape
sequences. Such a character is translated into the corresponding GSM character value and, when output later,
the GSM character value can be presented. Any ASCII terminal then will show wrong responses.
Examples for character definitions depending on alphabet
MC55_ATC_V01.05Page 19 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.5 Supported character sets
s
m
obil
e
GSM 03.38
character
Ö5C\\5C5C 35 43
"22"\225C 32 32
ò08BSP\085C 30 38
@00NULL\005C 30 30
CAUTION: Often, the editors of terminal programs do not recognize escape sequences. In this case, an escape
sequence will be handled as normal characters. The most common workaround to this problem is to write a script
which includes a decimal code instead of an escape sequence. This way you can write, for example, short messages which may contain differently coded characters.
GSM character
hex. value
Corresponding
ASCII character
ASCII
Esc sequence
Hex Esc
sequence
MC55_ATC_V01.05Page 20 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.5 Supported character sets
s
m
obil
e
1.5.1GSM alphabet tables and UCS2 character values
This section provides tables for the GSM 03.38 alphabet supported by the ME. Below any GSM character find
the corresponding two byte character value of the UCS2 alphabet.
Figure 1.1: Main character table of GSM 03.38 alphabet
1) This code is an escape to the following extension of the 7 bit default alphabet table.
2) This code is not a printable character and therefore not defined for the UCS2 alphabet. It shall be treated as the accom-
panying control character.
MC55_ATC_V01.05Page 21 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.5 Supported character sets
s
m
obil
e
Figure 1.2: Extension character table of GSM 03.38 alphabet
1) This code value is reserved for the extension to another extension table. On receipt of this code, a receiving entity shall
display a space until another extension table is defined.
2) This code represents the EURO currency symbol. The code value is the one used for the character 'e'. Therefore a receiv-
ing entity which is incapable of displaying the EURO currency symbol will display the character 'e' instead.
3) This code is defined as a Page Break character and may be used for example in compressed CBS messages. Any mobile
which does not understand the 7 bit default alphabet table extension mechanism will treat this character as Line Feed.
MC55_ATC_V01.05Page 22 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.5 Supported character sets
In the event that an MS receives a code where a symbol is not represented in figure Extension character table
of GSM 03.38 alphabet the MS shall display the character shown in the main default 7 bit alphabet table (see
figure Main character table of GSM 03.38 alphabet).
s
m
obil
e
1.5.2UCS2 and GSM data coding and conversion for SMS text mode
This chapter provides basic information on how to handle input and output character conversion for SMS text
mode and Remote-SAT if internal (ME) and external (TE) character representation differ, i.e. if the Data Coding
Scheme and the TE character use different coding.
1.5.2.1Implementing output of SIM data to the TE (direction ME to TE)
dcs
CSCS
GSMCase 1
UCS2Case 4
Case 1
Every byte will be sent as GSM character (or ASCII with Hyperterminal).
Example: 0x41,0x21 ® "AB" (because of conversion from 7-bit to 8-bit)
Case 2
Every byte will be sent as IRA. No conversion.
Example: 0x41,0x42 ® "4142"
Case 3
Every byte will be sent as IRA. No conversion to GSM to avoid data loss.
Example: 0x00,0x41 ® "0041"
Problems:
• 0x41,0x42 ® "4142" (invalid GSM character, but ignored with respect to GSM 07.05)
• 0x41 ® Error (there are two bytes needed)
7-Bit
(GSM default)
GSM (1:1)
GSM to UCS2 (1:2)
8-Bit16-Bit
(UCS2)
Case 2
IRA (1:1)
Case 5
GSM to UCS2 (1:2)
Case 3
IRA (2:2)
Case 6
IRA (2:2)
Case 4
Every byte will be converted from GSM to UCS2.
Example: 0x41,0x42 ® "00410042"
Case 5
Every byte will be converted from GSM to UCS2.
Example: 0x41,0x42 ® "00410042"
Case 6
Example: 0x41,0x42 ® "4142"
Problems:
• 0x41 ® Error (there are two bytes needed)
MC55_ATC_V01.05Page 23 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.5 Supported character sets
s
m
obil
1.5.2.2Implementing input of Terminal data to SIM (direction TE to ME)
e
CSCS
dcs
7-Bit
(GSM default)
8-BitCase 2
16-Bit
(UCS2)
Case 1
Data will be packed to 7-bit.
Maximum text length: 160 characters
Example: "AB" ® 0x41,0x21
Case 2
Data will be saved without any conversion.
Maximum text length: 280 characters
Example: "4142" ® 0x41,0x42
Problems:
• "8f" ® Error (invalid GSM character)
Case 3
Two bytes are needed. No conversion.
Maximum text length: 280 characters
Example: "0041" ® 0x00,0x41
Problems:
• "41" ® Error (there are two bytes needed)
GSMUCS2
Case 1
GSM (1:1)
IRA (1:1)
Case 3
IRA (2:2)
Case 4
UCS2 to GSM (2:1)
Case 5
UCS2 to GSM (2:1)
Case 6
IRA (2:2)
Case 4
Two bytes are needed. Two bytes will be converted to 1 byte GSM and 7-bit packed.
Maximum text length: 640 characters
Example: "00410042" ® 0x41,0x21
Problems:
• "41" ® Error (there are two bytes needed)
• "4142" ® Error (invalid character)
• "0000" ® Error (not an UCS2 character)
• "007B" ® 0x1B,0x28 (the saved data are two bytes long, not 1 byte like in all other cases.
This effects the maximum input length of a string)
Case 5
Two bytes are needed. Two bytes will be converted to 1 byte GSM.
Maximum text length: 560 characters
Example: "00410042" ® 0x41,0x42
Problems:
• "41" ® Error (there are two bytes needed)
• "4142" ® Error (invalid character)
• "0000" ® Error (not an UCS2 character)
• "007B" ® 0x1B,0x28 (the saved data are two bytes long, not 1 byte like in all other cases.
This effects the maximum input length of a string).
MC55_ATC_V01.05Page 24 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.5 Supported character sets
Case 6
Two bytes are needed.
Maximum text length: 280 characters
Example: "00410042" ® 0x00,0x41,0x00,0x21
Problems:
• "41" ® Error (there are two bytes needed)
• "0000" ® Error (not an UCS2 character)
• "007B" ® 0x00,0x7B
s
m
obil
e
MC55_ATC_V01.05Page 25 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.6 Flow Control
s
m
obil
e
1.6Flow Control
Flow control is essential to prevent loss of data or avoid errors when, in a data or fax call, the sending device is
transferring data faster than the receiving side is ready to accept. When the receiving buffer reaches its capacity,
the receiving device should be capable to cause the sending device to pause until it catches up.
There are basically two approaches to regulate data flow: software flow control and hardware flow control. The
High Watermark of the input / output buffer should be set to approximately 60% of the total buffer size. The Low
Watermark is recommended to be about 30%. The data flow should be stopped when the capacity rises close to
the High Watermark and resumed when it drops below the Low Watermark. The time required to cause stop and
go results in a hysteresis between the High and Low Watermarks.
In Multiplex mode, it is recommended to use hardware flow control.
1.6.1Software flow control (XON/OFF flow control)
Software flow control sends different characters to stop (XOFF, decimal 19) and resume (XON, decimal 17) data
flow. The only advantage of software flow control is that three wires would be sufficient on the serial interface.
1.6.2Hardware flow control (RTS/CTS flow control)
Hardware flow control sets or resets the RTS/CTS wires. This approach is faster and more reliable, and therefore, the better choice. When the High Watermark is reached, CTS is set inactive until the transfer from the buffer
has completed. When the Low Watermark is passed, CTS goes active once again.
To achieve smooth data flow, ensure that the RTS/CTS lines are present on your application platform. The application should include options to enable RTS/CTS handshake with the GSM engine. This needs to be done with
the AT command
The default setting of the GSM engine is
hardware handshake on). The setting is stored volatile and must be restored each time after the GSM engine
was switched off.
AT\Q has no read command. To verify the current setting of AT\Q, simply check the settings of the active profile
with
AT&V.
Often, fax programs run an intialization procedure when started up. The intialization commonly includes enabling
RTS/CTS hardware handshake, eliminating the need to set
CSD call, you are advised to check that RTS/CTS handshake is set.
RTS/CTS hardware handshake must also be set if you want to take advantage of the CYCLIC SLEEP modes.
For further details refer to
Note: After deactivating the RTS line, the ME may still send up to 264 bytes (worst case). This can be easily
handled if the buffer of the host application is sufficiently sized, and if a hysteresis is implemented in its Rx buffer.
For host applications that are required to handle a large amount of data at high speed, a total buffer capacity of
512 bytes is recommended.
AT\Q3 - it is not sufficient to set RTS/CTS handshake in the used Terminal program only.
AT\Q0 (no flow control) which must be altered to AT\Q3 (RTS/CTS
AT\Q3 once again. However, before setting up a
AT+CFUN.
MC55_ATC_V01.05Page 26 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.7 Unsolicited Result Code Presentation
s
m
obil
e
1.7Unsolicited Result Code Presentation
URC stands for Unsolicited Result Code and is a report message issued by the ME without being requested by
the TE, i.e. a URC is issued automatically when a certain event occurs. Hence, a URC is not issued as part of
the response related to an executed AT command.
Typical events leading to URCs are incoming calls ("RING"), received SMs, changing temperature, status of the
battery etc.
A summary of all URCs is given in chapter
To announce a pending URC transmission the ME will do the following:
•Activates its Ring line (logic "1") for one second, i.e. the line changes to physical "Low" level. This allows the
TE to enter power saving mode until ME related events request service.
•If the AT command interface is busy a "BREAK" will be sent immediately but the URC will not be issued until
the line is free. This may happen if the URC is pending
-while an AT command is being processed, i.e. during the time from sending the first character "A" of an
AT command by the TE until the ME has responded with "OK" or "ERROR", or
-during a data call.
Please note that AT command settings may be necessary to enable in-band signaling, e.g. refer to
or AT+CNMI.
It is strongly recommended to use the multiplex mode to map logical communication channels onto the serial line
of the MC55, for details refer to [5] and AT command
process URCs while having a data call active on another.
For most of these messages, the ME needs to be configured whether or not to send an URC. Depending on the
AT command, the URC presentation mode can be saved to the user defined profile (see
activated every time you reboot the ME. Several URCs are not user definable, such as "^SYSSTART",
"^SYSSTART <text>", "
Result Codes (URC)
If autobauding is enabled (as factory default mode or set with
output with 57600 bps until the ME has detected the current bit rate. The URCs "^SYSSTART", "^SYSSTART
<text>", however, are not presented at all. For details please refer to Chapter 4.7.1. To avoid problems we recommend to configure a fixed bit rate rather than using autobauding.
^SHUTDOWN" and the Fax Class 2 URCs listed in Chapter Summary of Unsolicited
.
Summary of Unsolicited Result Codes (URC).
AT+CMER
AT+CMUX. Doing so it is possible to use one channel to still
AT&W), or needs to be
AT+IPR=0), URCs generated after restart will be
1.7.1Communication between Customer Application and MC55
Leaving hardware flow control unconsidered the Customer Application (TE) is coupled with the MC55 (ME) via
a receive and a transmit line.
Since both lines are driven by independent devices collisions may (and will) happen, i.e. while the TE issues an
AT command the MC55 starts sending an URC. This probably will lead to the TE's misinterpretation of the URC
being part of the AT command's response.
To avoid this conflict the following measures must be taken:
•If an AT command is finished (with "OK" or "ERROR") the TE shall always wait at least 100 milliseconds
before sending the next one.
This gives the MC55 the opportunity to transmit pending URCs and get necessary service.
Note that some AT commands may require more delay after "OK" or "ERROR" response, refer to the following
command specifications for details.
•The TE shall communicate with the MC55 using activated echo (
received from the TE.
Hence, when the TE receives the echo of the first character "A" of the AT command just sent by itself it has
control over both the receive and the transmit paths. This way no URC can be issued by the MC55 in between.
MC55_ATC_V01.05Page 27 of 4692/10/04
Confidential / Released
ATE1), i.e. the MC55 echoes characters
MC55 AT Command Set
1.8 Common PCN Handset Specification (CPHS)
s
m
obil
e
1.8Common PCN Handset Specification (CPHS)
The ME provides features to implement a device following the prerequisites of the Common PCN Handset Specification (CPHS) Phase 2.
CPHS FeatureDescription/RemarksAT command
Alternate Line ServiceUsing two phone numbers with one SIM card.AT^SALS
Voice Message Waiting
Indication
Operator (Service provider) name from SIM
Network and Service Provider Lock
Call ForwardingGet and set diverted call status. Access specific Elementary
Customer Service Profile
(CSP)
Information numbersHierarchically structured service numbers phonebook on
Indicate the receipt of a short message coded as Voice Message Waiting Indicator as defined by the CPHS Phase 2
standard.
Read specific Elementary Files (6F14h, 6F18h) from SIM. AT+CRSM
Lock/Unlock an ME to specific HPLMN and service provider. AT+CLCK,
File (6F13h) from SIM.
Setting services and their menu entries depending on customer profiles.
SIM according to CPHS 4.2 (mandatory).
AT^SIND,
AT+CMER, indicators
"vmwait1" and
"vmwait2"
(
AT+CPIN)
AT+CCFC, AT+CRSM
AT+CRSM
AT+CRSM
MC55_ATC_V01.05Page 28 of 4692/10/04
Confidential / Released
MC55 AT Command Set
1.9 Errors and Messages
s
m
obil
e
1.9Errors and Messages
The final result codes "+CME ERROR: <err>" and "+CMS ERROR: <err>" indicate errors related to mobile equipment or network. The effect is similar to an ERROR result code.
A final result error code terminates the execution of the command and prevents the execution of all remaining
commands that may follow on the same command line. If so, neither ERROR nor OK result code are returned
for these commands. A 30 seconds timeout causes ERROR to be returned when the input of a command is not
complete.
The format of <err> can be either numeric or verbose. This is set with the command
See also:
•2.11.1
•2.5.1
•
AT+CEER
AT+CMEE.
MC55_ATC_V01.05Page 29 of 4692/10/04
Confidential / Released
MC55 AT Command Set
2. Configuration Commands
s
m
obil
e
2.Configuration Commands
The AT Commands described in this chapter allow the external application to determine the MC55's behaviour
under various conditions.
2.1AT&FSet all current parameters to manufacturer defaults
Syntax
Exec Command
AT&F[<value>]
Response(s)
OK
PINASC0ASC1MUX1MUX2MUX3
!%%%%%
Reference(s)
V.25ter
Command Description
TA sets all current parameters to the manufacturer defined profile.
Parameter Description
<value>
[0]set all TA parameters to manufacturer defaults
Notes
•List of parameters reset to manufacturer default can be found in Chapter Factory Default Settings
Restorable with AT&F
•In addition to the default profile, you can store an individual one with
files enter either
(num)
.
AT&W. To alternate between the two pro-
ATZ (loads user profile) or AT&F (restores factory profile).
•Every ongoing or incoming call will be terminated.
MC55_ATC_V01.05Page 30 of 4692/10/04
Confidential / Released
Loading...
+ 439 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.