【AT ERROR】AT指令返回错误 解释

CME ERROR's (GSM Equipment related codes)

Error Description

CME ERROR: 0 Phone failure

CME ERROR: 1 No connection to phone

CME ERROR: 2 Phone adapter link reserved

CME ERROR: 3 Operation not allowed

CME ERROR: 4 Operation not supported

CME ERROR: 5 PH_SIM PIN required

CME ERROR: 6 PH_FSIM PIN required

CME ERROR: 7 PH_FSIM PUK required

CME ERROR: 10 SIM not inserted

CME ERROR: 11 SIM PIN required

CME ERROR: 12 SIM PUK required

CME ERROR: 13 SIM failure

CME ERROR: 14 SIM busy

CME ERROR: 15 SIM wrong

CME ERROR: 16 Incorrect password

CME ERROR: 17 SIM PIN2 required

CME ERROR: 18 SIM PUK2 required

CME ERROR: 20 Memory full

CME ERROR: 21 Invalid index

CME ERROR: 22 Not found

CME ERROR: 23 Memory failure

CME ERROR: 24 Text string too long

CME ERROR: 25 Invalid characters in text string

CME ERROR: 26 Dial string too long

CME ERROR: 27 Invalid characters in dial string

CME ERROR: 30 No network service

CME ERROR: 31 Network timeout

CME ERROR: 32 Network not allowed, emergency calls only

CME ERROR: 40 Network personalization PIN required

CME ERROR: 41 Network personalization PUK required

CME ERROR: 42 Network subset personalization PIN required

CME ERROR: 43 Network subset personalization PUK required

CME ERROR: 44 Service provider personalization PIN required

CME ERROR: 45 Service provider personalization PUK required

CME ERROR: 46 Corporate personalization PIN required

CME ERROR: 47 Corporate personalization PUK required

CME ERROR: 48 PH-SIM PUK required

CME ERROR: 100 Unknown error

CME ERROR: 103 Illegal MS

CME ERROR: 106 Illegal ME

CME ERROR: 107 GPRS services not allowed (欠费等)

CME ERROR: 111 PLMN not allowed

CME ERROR: 112 Location area not allowed

CME ERROR: 113 Roaming not allowed in this location area

CME ERROR: 126 Operation temporary not allowed

CME ERROR: 132 Service operation not supported

CME ERROR: 133 Requested service option not subscribed

CME ERROR: 134 Service option temporary out of order

CME ERROR: 148 Unspecified GPRS error

CME ERROR: 149 PDP authentication failure

CME ERROR: 150 Invalid mobile class

CME ERROR: 256 Operation temporarily not allowed

CME ERROR: 257 Call barred

CME ERROR: 258 Phone is busy

CME ERROR: 259 User abort

CME ERROR: 260 Invalid dial string

CME ERROR: 261 SS not executed

CME ERROR: 262 SIM Blocked

CME ERROR: 263 Invalid block

CME ERROR: 772 SIM powered down

CMS ERROR's (GSM Network related codes)

Error Description

CMS ERROR: 1 Unassigned number

CMS ERROR: 8 Operator determined barring

CMS ERROR: 10 Call bared

CMS ERROR: 21 Short message transfer rejected

CMS ERROR: 27 Destination out of service

CMS ERROR: 28 Unindentified subscriber

CMS ERROR: 29 Facility rejected

CMS ERROR: 30 Unknown subscriber

CMS ERROR: 38 Network out of order

CMS ERROR: 41 Temporary failure

CMS ERROR: 42 Congestion

CMS ERROR: 47 Recources unavailable

CMS ERROR: 50 Requested facility not subscribed

CMS ERROR: 69 Requested facility not implemented

CMS ERROR: 81 Invalid short message transfer reference value

CMS ERROR: 95 Invalid message unspecified

CMS ERROR: 96 Invalid mandatory information

CMS ERROR: 97 Message type non existent or not implemented

CMS ERROR: 98 Message not compatible with short message protocol

CMS ERROR: 99 Information element non-existent or not implemente

CMS ERROR: 111 Protocol error, unspecified

CMS ERROR: 127 Internetworking , unspecified

CMS ERROR: 128 Telematic internetworking not supported

CMS ERROR: 129 Short message type 0 not supported

CMS ERROR: 130 Cannot replace short message

CMS ERROR: 143 Unspecified TP-PID error

CMS ERROR: 144 Data code scheme not supported

CMS ERROR: 145 Message class not supported

CMS ERROR: 159 Unspecified TP-DCS error

CMS ERROR: 160 Command cannot be actioned

CMS ERROR: 161 Command unsupported

CMS ERROR: 175 Unspecified TP-Command error

CMS ERROR: 176 TPDU not supported

CMS ERROR: 192 SC busy

CMS ERROR: 193 No SC subscription

CMS ERROR: 194 SC System failure

CMS ERROR: 195 Invalid SME address

CMS ERROR: 196 Destination SME barred

CMS ERROR: 197 SM Rejected-Duplicate SM

CMS ERROR: 198 TP-VPF not supported

CMS ERROR: 199 TP-VP not supported

CMS ERROR: 208 D0 SIM SMS Storage full

CMS ERROR: 209 No SMS Storage capability in SIM

CMS ERROR: 210 Error in MS

CMS ERROR: 211 Memory capacity exceeded

CMS ERROR: 212 Sim application toolkit busy

CMS ERROR: 213 SIM data download error

CMS ERROR: 255 Unspecified error cause

CMS ERROR: 300 ME Failure

CMS ERROR: 301 SMS service of ME reserved

CMS ERROR: 302 Operation not allowed

CMS ERROR: 303 Operation not supported

CMS ERROR: 304 Invalid PDU mode parameter

CMS ERROR: 305 Invalid Text mode parameter

CMS ERROR: 310 SIM not inserted

CMS ERROR: 311 SIM PIN required

CMS ERROR: 312 PH-SIM PIN required

CMS ERROR: 313 SIM failure

CMS ERROR: 314 SIM busy

CMS ERROR: 315 SIM wrong

CMS ERROR: 316 SIM PUK required

CMS ERROR: 317 SIM PIN2 required

CMS ERROR: 318 SIM PUK2 required

CMS ERROR: 320 Memory failure

CMS ERROR: 321 Invalid memory index

CMS ERROR: 322 Memory full

CMS ERROR: 330 SMSC address unknown

CMS ERROR: 331 No network service

CMS ERROR: 332 Network timeout

CMS ERROR: 340 No +CNMA expected

CMS ERROR: 500 Unknown error

CMS ERROR: 512 User abort

CMS ERROR: 513 Unable to store

CMS ERROR: 514 Invalid Status

CMS ERROR: 515 Device busy or Invalid Character in string (AT+CMGF=1设定文本发送，但是十六进制的时候输入的 FF FE FA 等是没有对应字符的，信箱是否已满)

CMS ERROR: 516 Invalid length

CMS ERROR: 517 Invalid character in PDU  (注意：发送号码前应先发送AT+CMGF=1/AT+CMGF=0设定文本发送还是二进制发送，文本发送时要保证输入的值有对应的字符)

CMS ERROR: 518 Invalid parameter

CMS ERROR: 519 Invalid length or character

CMS ERROR: 520 Invalid character in text

CMS ERROR: 521 Timer expired

CMS ERROR: 522 Operation temporary not allowed

CMS ERROR: 532 SIM not ready

CMS ERROR: 534 Cell Broadcast error unknown

CMS ERROR: 535 Protocol stack busy

短信通信的几种情况和CMS错误
． 如何与GSM MODEM建立通信联系
2． 不能与GSM MODEM进行正常的通信或总是在仿真终端上出现乱码
3． 如何才能知道错误代码
4． 发送短消息后，收到出错信息+CMS ERROR 512
5． 发送短消息后，收到出错信息+CMS ERROR 513
6． 发送短消息后，收到出错信息+CMS ERROR 514
7． 发送短消息后，收到出错信息+CMS ERROR 515
8． 如何才能知道您发送的短消息已被送达目的号码
9． 如何发送中文短消息
10．如何建立一个话音呼叫
11．如何建立一个数据呼叫
12．当GSM MODEM作被叫时，如何显示主叫的电话号码
13．当GSM MODEM作被叫时，如何判别主叫发起的是话音、数据或传真呼叫
14．当GSM MODEM作被叫时，如何使其自动应答或不能自动应答
15．如何不通过SIM卡直接读或写短消息

1． 如何与GSM MODEM建立通信联系
您可用诸如Windows下的超级终端或Pcomm等终端仿真软件，将计算机的串行口与GSM MODEM的串行口用电缆直接连接。

2． 不能与GSM MODEM进行正常的通信或总是在仿真终端上出现乱码
检查您的串口是否保证正常连接，计算机的串口引线与GSM MODEM的串口引线应是一一对应的。GSM MODEM与仿真终端应设置相同的通信速率。
但您初次使用GSM MODEM时，请在仿真终端上设置为通信速率9600bps、8位数据位、无较验位、1位停止位。

3． 如果您想在出错后得到错误代码号，需将GSM Modem作如下设置：
AT+CMEE=1

4． 发送短消息后，收到出错信息+CMS ERROR 512
表示您的GSM MODEM在发送短消息的同时它收到了新的短消息，发送短消息被拒绝，您需要重新发送此条短消息。

5． 发送短消息后，收到出错信息+CMS ERROR 513
您遇上了下面问题中的一种：
a) 您的GSM MODEM失去了无线链路连接；
b) 在发送完短消息后的28秒内，您的GSM MODEM没有收到短消息中心送来的接收确认+CMGS：〈顺序号〉；
c) 在送出请求建立发送短消息的控制信道指令后的42秒内，您的GSM MODEM没有收到基站送来的确认〉。

6． 发送短消息后，收到出错信息+CMS ERROR 514
您遇上了下面问题中的一种：
a) 您设置的短消息中心的号码是错误的；
b) 短消息将要送达的目的号码是错误的；
c) 您发送的短消息被短消息中心拒绝(一般为目的号码不存在或目的号码被禁用)。

7．1、 发送短消息后，收到出错信息+CMS ERROR 515
如果您的GSM MODEM在初始化期间或在指令执行过程当中GSM MODEM又接受新的指令，将会出现此错误。您必须等到初始化完成或指令执行完毕。
2、也有可能是接收方出了问题->忙，心箱已满等
3、AT+CMGF=1设定文本发送，但是十六进制的时候输入的 FF FE FA 等是没有对应字符的，信箱是否已满

8． 如何才能知道您发送的短消息已被送达目的号码
a) 采用文本格式发送
在您采用文本格式发送短消息时，您的GSM MODEM须作以下的设置：
at+csmp=49，〈X〉，〈X〉，〈X〉
at+cnmi=〈X〉，〈X〉，〈X〉，1，〈X〉
〈X〉代表根据您的需要您所选择的合适的参数。
当您发送完短消息后，您将收到来自短消息中心的以下两种确认中的一种：
+CDS：〈X〉，〈顺序号〉，"电话号码"，"发送时间"，"接收时间"，0
或：
+CDS：〈X〉，〈顺序号〉，"电话号码"，"发送时间"，"接收时间"，48
确认中的最后个数代表了此短消息的传输状态。(0表示已经送达目的号码，48表示不可能将此送达目的号码)
b) 采用PDU格式发送
在您采用PDU格式发送短消息时，您的GSM MODEM须作以下的设置：
at+cnmi=〈X〉，〈X〉，〈X〉，1，〈X〉
〈X〉代表根据您的需要您所选择的合适的参数。
在您所要发送的PDU格式的短消息中，您须将短消息中心号码后的第一个字节设成31
在发送完短消息后，您将收到来自短消息中心的以下确认：
+CDS：〈长度〉00〈PDU格式的确认信息〉
注意：在收到的PDU格式的确认中，顺序号和传输状态标志都是以16进制数存在的，您可将其直接转成10进制数而无需将其倒置后再转换。

9． 如何发送中文短消息
采用现有的GSM MODEM发送中文短消息，都必须先将准备发送的中文短消息转换成16位的Unicode编码。
A) 采用文本方式发送
在您采用文本格式发送Unicode编码中文短消息时，您的GSM MODEM须作的设置：
at+csmp=〈X〉，〈X〉，〈X〉，8
〈X〉代表根据您的需要您所选择的合适的参数。
然后您就可将转换好的Unicode编码中文短消息按照发送普通文本短消息的方法发送出去。
B) 采用PDU方式发送
您只须在您的PDU格式的短消息中，将目的号码字符串后的第二个字节设成08，将转
换好的Unicode编码中文短消息作为PDU中的发送内容一齐发送。

10． 如何建立一个话音呼叫
向GSM MODEM的串口送指令ATD〈电话号码〉；〈回车〉必须确认电话号码是一个话音号码而非传真或数据号码。

11． 如何建立一个数据呼叫
先将您的GSM MODEM作如下设置：
at+ipr=9600
at+ifc=2，2
at+cbst=0，0，1
向GSM MODEM的串口送指令ATD〈电话号码〉〈回车〉
必须确认电话号码是一个数据号码而非传真或话音号码，同时必须确认您的SIM卡已开通数据通信的服务。

12．当GSM MODEM作被叫时，如何显示主叫的电话号码
将您的GSM MODEM作如下设置：
at+clip=1

13．当GSM MODEM作被叫时，如何判别主叫发起的是话音、数据或传真呼叫
将您的GSM MODEM作如下设置：
at+crc=1

14．当GSM MODEM作被叫时，如何使其自动应答或不能自动应答
如果您想让您的GSM MODEM自动应答，将您的GSM MODEM作如下设置：
ats0=〈N〉 N是代表GSM MODEM震铃的次数的一个整数，即GSM MODEM在N 次 震铃后将自动应答。
如果您想让您的GSM MODEM不能自动应答，将您的GSM MODEM作如下设置：
ats0=0

15．如何不通过SIM卡直接读或写短消息
因为SIM卡只有1万到10万次的读写次数和10-15条短消息的存储空间，还涉及到SIM卡上短消息读写需要一定的时间才能完成。这些因素影响了许多应用，这些应用需要通过GSM网络进行大量的数据交换，为保证流程的顺利进行，SIM卡要完成大量的读、写和删除操作，SIM卡的寿命周期很快就会达到，此外，SIM卡完成这些工作所耗费的时间比外界要求的要多。为解决这些问题，有必要在终端上作一些软件设置，使短消息不通过SIM卡进行读写操作。
以下的描述介绍了如何采用这种方法在Falcom A2系列和数据终端MT4002之间不通过SIM卡交换数据，这种方法也可用与2个MT4002之间。
a) 串口上的从终端来的RTS信号可用来指示数据交换时隙是否忙，串口准备好接收数据
b) 如果终端双方都可用来接收和发送短消息，在设置时双方都要设同样的命令和常数。
在接收端，设命令AT+CNMI=2，2，0，0，0
在发送端，设命令AT+CSMP=17，167，0，240 (当使用PDU格式发送时，240改成字符串DCS(F0))
c) 当程序发现短消息以前缀+CMT后跟所传送的数据这种格式时，立即将此短消息捕获并将其分发到原定的地址。
d) 当发送端如果没有设置CSMP=17，167，0，240时，捕获到的短消息应有前缀+CMTI，此时用命令AT+CMGR=n读取并分发到原定的地址，随后用命令AT+CMGD=n将此短消息删除以保证SIM卡有足够多的空间。

Here's a list of all of the "+CMS ERROR" codes for the GSM modem interface ... they can be found defined in the ETSI GSM specs. I figure it is worth posting as they are split between the GSM 07.05, GSM 03.40 and GSM 04.11 specs, and I frequently have to look this up for support incidents. (So if nothing else, I'll be able to search out here to find the list.)

CMS ERROR code list (GSM Modem error codes):

1 - "Unassigned (unallocated) number" 
This cause indicates that the destination requested by the Mobile Station cannot be reached because, although the number is in a valid format, it is not currently assigned (allocated).

8 - "Operator determined barring" 
This cause indicates that the MS has tried to send a mobile originating short message when the MS's network operator or service provider has forbidden such transactions.

10 - "Call barred" 
This cause indicates that the outgoing call barred service applies to the short message service for the called destination.

21 - "Short message transfer rejected" 
This cause indicates that the equipment sending this cause does not wish to accept this short message, although it could have accepted the short message since the equipment sending this cause is neither busy nor incompatible.

27 - "Destination out of service" 
This cause indicates that the destination indicated by the Mobile Station cannot be reached because the interface to the destination is not functioning correctly. The term "not functioning correctly" indicates that a signalling message was unable to be delivered to the remote user; e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc.

28 - "Unidentified subscriber" 
This cause indicates that the subscriber is not registered in the PLMN (i.e. IMSI not known).

29 - "Facility rejected" 
This cause indicates that the facility requested by the Mobile Station is not supported by the PLMN.

30 - "Unknown subscriber" 
This cause indicates that the subscriber is not registered in the HLR (i.e. IMSI or directory number is not allocated to a subscriber).

38 - "Network out of order" 
This cause indicates that the network is not functioning correctly and that the condition is likely to last a relatively long period of time; e.g., immediately reattempting the short message transfer is not likely to be successful.

41 - "Temporary failure" 
This cause indicates that the network is not functioning correctly and that the condition is not likely to last a long period of time; e.g., the Mobile Station may wish to try another short message transfer attempt almost immediately.

42 - "Congestion" 
This cause indicates that the short message service cannot be serviced because of high traffic.

47 - "Resources unavailable, unspecified" 
This cause is used to report a resource unavailable event only when no other cause applies.

50 - "Requested facility not subscribed" 
This cause indicates that the requested short message service could not be provided by the network because the user has not completed the necessary administrative arrangements with its supporting networks.

69 - "Requested facility not implemented" 
This cause indicates that the network is unable to provide the requested short message service.

81 - "Invalid short message transfer reference value" 
This cause indicates that the equipment sending this cause has received a message with a short message reference which is not currently in use on the MS-network interface.

95 - "Invalid message, unspecified" 
This cause is used to report an invalid message event only when no other cause in the invalid message class applies.

96 - "Invalid mandatory information" 
This cause indicates that the equipment sending this cause has received a message where a mandatory information element is missing and/or has a content error (the two cases are indistinguishable).

97 - "Message type non-existent or not implemented" 
This cause indicates that the equipment sending this cause has received a message with a message type it does not recognize either because this is a message not defined or defined but not implemented by the equipment sending this cause.

98 - "Message not compatible with short message protocol state" 
This cause indicates that the equipment sending this cause has received a message such that the procedures do not indicate that this is a permissible message to receive while in the short message transfer state.

99 - "Information element non-existent or not implemented" 
This cause indicates that the equipment sending this cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the cause. However, the information element is not required to be present in the message in order for the equipment sending the cause to process the message.

111 - "Protocol error, unspecified" 
This cause is used to report a protocol error event only when no other cause applies.

127 - "Interworking, unspecified" 
This cause indicates that there has been interworking with a network which does not provide causes for actions it takes; thus, the precise cause for a message which is being send cannot be ascertained.

0...127 - Other values in this range are reserved, defined by GSM 04.11 Annex E-2 values

128 - Telematic interworking not supported x 
129 - Short message Type 0 not supported x x 
130 - Cannot replace short message x x 
143 - Unspecified TP-PID error x x 
144 - Data coding scheme (alphabet) not supported x 
145 - Message class not supported x 
159 - Unspecified TP-DCS error x x 
160 - Command cannot be actioned x 
161 - Command unsupported x 
175 - Unspecified TP-Command error x 
176 - TPDU not supported x x 
192 - SC busy x 
193 - No SC subscription x 
194 - SC system failure x 
195 - Invalid SME address x 
196 - Destination SME barred x 
197 - SM Rejected-Duplicate SM x 
198 - TP-VPF not supported X 
199 - TP-VP not supported X 
208 - SIM SMS storage full x 
209 - No SMS storage capability in SIM x 
210 - Error in MS x 
211 - Memory Capacity Exceeded X 
212 - SIM Application Toolkit Busy x x 
255 - Unspecified error cause

128...255 - Other values in this range are reserved, defined by GSM 03.40 subclause 9.2.3.22 values

300 - ME failure 
301 - SMS service of ME reserved 
302 - operation not allowed 
303 - operation not supported 
304 - invalid PDU mode parameter 
305 - invalid text mode parameter 
310 - SIM not inserted 
311 - SIM PIN required 
312 - PH-SIM PIN required 
313 - SIM failure 
314 - SIM busy 
315 - SIM wrong 
316 - SIM PUK required 
317 - SIM PIN2 required 
318 - SIM PUK2 required 
320 - memory failure 
321 - invalid memory index 
322 - memory full 
330 - SMSC address unknown 
331 - no network service 
332 - network timeout 
340 - no +CNMA acknowledgement expected 
500 - unknown error

256...511 - Other values in this range are reserved

512... - manufacturer specific

17 - "Network failure". 
This cause is sent to the MS if the MSC cannot service an MS generated request because of PLMN failures, e.g. problems in MAP.

22 - "Congestion". 
This cause is sent if the service request cannot be actioned because of congestion (e.g. no channel, facility busy/congested etc.).

22 - "Memory capacity exceeded". 
This cause indicates that the mobile station cannot store the incoming short message due to lack of storage capacity.

Note that error "22" is defined twice. It is likely that "CMS ERROR 22" would be due to the first definition, while the second definition is likely to only be a status code for delivery reports.

本文来自CSDN博客，转载请标明出处：http://blog.csdn.net/Rookie_CEO/archive/2009/12/30/5097035.aspx