Эта тема
- Везде
-
- Эта тема
- Этот форум
-
- Расширенный поиск
Поиск
You are here
ELS61-E +CME ERROR: 148 after CGATT=1 | Telit Cinterion IoT Developer Community
July 5, 2018 — 11:51am, 7593 views
Hello,
we are experiencing +CME ERROR: 148 after CGATT=1 is executed. What could be the cause of this error and how could we fix it?
Command sequence:
AT^SMSO
^SMSO: MS OFF
OK
^SHUTDOWN
<ON_SEQUENCE>
ATE0
ATE0
ATE0
ATE0
ATE0
AT+CGACT=0,1
AT^SMSO
ATE0
ATE0
ATE0
^SYSLOADING
ATE0
ATE0
OK
AT+CMEE=1
OK
AT+CGMI
Cinterion
OK
AT+CGMM
ELS61-E
OK
AT+CGMR
REVISION 01.000
OK
AT+CCID
^SYSSTART
+CCID: XXX
OK
AT+CIMI
XXX
OK
AT+CPIN?
+CPIN: READY
OK
AT+CEREG?
+CEREG: 0,0
OK
AT+CGREG?
+CGREG: 0,4
OK
AT+CREG?
+CREG: 0,1
OK
AT+CGATT?
+CGATT: 0
OK
AT+CGATT?
+CGATT: 0
OK
AT+CGATT=1
+CME ERROR: 148
AT+CGATT?
+CGATT: 0
OK
AT+CGATT=1
+CME ERROR: 148
AT+CGATT?
+CGATT: 0
OK
AT+CGATT=1
+CME ERROR: 148
AT+CGATT?
+CGATT: 0
OK
AT+CGATT=1
+CME ERROR: 148
AT+CGATT?
+CGATT: 0
OK
AT+CGATT=1
+CME ERROR: 148
AT+CGATT?
+CGATT: 0
OK
AT+CGATT=1
+CME ERROR: 148
AT+CGACT=0,1
OK
AT^SMSO
^SMSO: MS OFF
OK
Best regards,
Sebastian
There are two types of GSM error codes: CMS Error codes and CME Error codes that your GSM may return when sending an SMS.
The CMS error codes start with ‘+CMS Error:‘ and are always network related errors. The CME error codes start with ‘+CME Error:‘ and are always device (equipment) related errors.
CME Errors (GSM equipment errors)
CME Error | Description |
0 | Phone failure |
1 | No connection to phone |
2 | Phone adapter link reserved |
3 | Operation not allowed |
4 | Operation not supported |
5 | PH_SIM PIN required |
6 | PH_FSIM PIN required |
7 | PH_FSIM PUK required |
10 | SIM not inserted |
11 | SIM PIN required |
12 | SIM PUK required |
13 | SIM failure |
14 | SIM busy |
15 | SIM wrong |
16 | Incorrect password |
17 | SIM PIN2 required |
18 | SIM PUK2 required |
20 | Memory full |
21 | Invalid index |
22 | Not found |
23 | Memory failure |
24 | Text string too long |
25 | Invalid characters in text string |
26 | Dial string too long |
27 | Invalid characters in dial string |
30 | No network service |
31 | Network timeout |
32 | Network not allowed, emergency calls only |
40 | Network personalization PIN required |
41 | Network personalization PUK required |
42 | Network subset personalization PIN required |
43 | Network subset personalization PUK required |
44 | Service provider personalization PIN required |
45 | Service provider personalization PUK required |
46 | Corporate personalization PIN required |
47 | Corporate personalization PUK required |
48 | PH-SIM PUK required |
100 | Unknown error |
103 | Illegal MS |
106 | Illegal ME |
107 | GPRS services not allowed |
111 | PLMN not allowed |
112 | Location area not allowed |
113 | Roaming not allowed in this location area |
126 | Operation temporary not allowed |
132 | Service operation not supported |
133 | Requested service option not subscribed |
134 | Service option temporary out of order |
148 | Unspecified GPRS error |
149 | PDP authentication failure |
150 | Invalid mobile class |
256 | Operation temporarily not allowed |
257 | Call barred |
258 | Phone is busy |
259 | User abort |
260 | Invalid dial string |
261 | SS not executed |
262 | SIM Blocked |
263 | Invalid block |
772 | SIM powered down |
CMS Errors (GSM Network errors)
CMS Error | Description |
1 | Unassigned number |
8 | Operator determined barring |
10 | Call bared |
21 | Short message transfer rejected |
27 | Destination out of service |
28 | Unindentified subscriber |
29 | Facility rejected |
30 | Unknown subscriber |
38 | Network out of order |
41 | Temporary failure |
42 | Congestion |
47 | Recources unavailable |
50 | Requested facility not subscribed |
69 | Requested facility not implemented |
81 | Invalid short message transfer reference value |
95 | Invalid message unspecified |
96 | Invalid mandatory information |
97 | Message type non existent or not implemented |
98 | Message not compatible with short message protocol |
99 | Information element non-existent or not implemente |
111 | Protocol error, unspecified |
127 | Internetworking , unspecified |
128 | Telematic internetworking not supported |
129 | Short message type 0 not supported |
130 | Cannot replace short message |
143 | Unspecified TP-PID error |
144 | Data code scheme not supported |
145 | Message class not supported |
159 | Unspecified TP-DCS error |
160 | Command cannot be actioned |
161 | Command unsupported |
175 | Unspecified TP-Command error |
176 | TPDU not supported |
192 | SC busy |
193 | No SC subscription |
194 | SC System failure |
195 | Invalid SME address |
196 | Destination SME barred |
197 | SM Rejected-Duplicate SM |
198 | TP-VPF not supported |
199 | TP-VP not supported |
208 | D0 SIM SMS Storage full |
209 | No SMS Storage capability in SIM |
210 | Error in MS |
211 | Memory capacity exceeded |
212 | Sim application toolkit busy |
213 | SIM data download error |
255 | Unspecified error cause |
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 expected |
500 | Unknown error |
512 | User abort |
513 | Unable to store |
514 | Invalid Status |
515 | Device busy or Invalid Character in string |
516 | Invalid length |
517 | Invalid character in PDU |
518 | Invalid parameter |
519 | Invalid length or character |
520 | Invalid character in text |
521 | Timer expired |
522 | Operation temporary not allowed |
532 | SIM not ready |
534 | Cell Broadcast error unknown |
535 | Protocol stack busy |
538 | Invalid parameter |
Connect
- Add your SIM card to the Telit GSM modem and attach it via USB port to your server.
- To find the port where your GSM modem is attached, execute the following script after you’ve marked it as executable.
#!/bin/bash
for sysdevpath in $(find /sys/bus/usb/devices/usb*/ -name dev); do
(
syspath=”${sysdevpath%/dev}”
devname=”$(udevadm info -q name -p $syspath)”
[[ “$devname” == “bus/”* ]] && continue
eval “$(udevadm info -q property –export -p $syspath)”
[[ -z “$ID_SERIAL” ]] && continue
echo “/dev/$devname – $ID_SERIAL”
)
done
# ./listdev.sh
/dev/ttyACM0 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926
/dev/ttyACM1 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926
/dev/ttyACM2 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926
/dev/ttyACM3 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926
/dev/ttyACM4 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926
/dev/ttyACM5 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926
/dev/ttyACM6 - Telit_wireless_solutions_Telit_Wireless_Module_351579057468926
/dev/input/mouse2 - VMware_VMware_Virtual_USB_Mouse
/dev/input/event4 - VMware_VMware_Virtual_USB_Mouse
/dev/input/js0 - VMware_VMware_Virtual_USB_Mouse
/dev/input/mouse3 - VMware_VMware_Virtual_USB_Mouse
/dev/input/event5 - VMware_VMware_Virtual_USB_Mouse
Take a note of the device-path (/dev/ttyACM0)
Configuration
/etc/smsd.conf: This sample configuration file works fine in our productive environment on a SIM card without PIN code enabled – if you need to configure a PIN (if enabled) try configuring “pin=” . Make sure you use the correct device-path from above (device=/dev/ttyACM0) at “device=”.
# Example smsd.conf. Read the manual for a description
# once your configuration is OK, set log level lower (5 is good in most cases)
devices=GSM1
logfile=/var/log/smsd/smsd.log
loglevel=8
user=root
infofile=/var/run/smsd/smsd.working
pidfile=/var/run/smsd/smsd.pid
# 3.1.5 introduced smart logging
smart_logging=yes[GSM1]
init=ATE0
incoming=no
rtscts=no
cs_convert=yes
report=no
mode=new
device=/dev/ttyACM0
pin=0014
baudrate=115200
Testing
Configure your hyperterminal session by using minicom -s
# minicom -s
Select “Serial port setup”
Make sure your settings looks like this (A – Serial Device must match the path from above, E – Bps/Par/Bits must be 19200 8N1 or 115200 8N1). Press ENTER to save your setting.
Select Exit to open the connection to the GSM modem
The connection is initalized
The connection is open, the GSM modem is ready to receive commands
Send SMS by using AT commands. NOTE: In this example we have removed the PIN of the SIM card, if the PIN is still present make sure you are properly authenticated – additional details please see the chapter ‘PIN codes by using AT commands’ below)AT
OK
AT+CMGF=1 -----> set message format, see AT reference
OK
AT+CMGS="+41796316771"
> Hello World!
>
<PRESS CTRL-Z to send the message>
+CMGS: 255
OK
To exit minicom press CRTL-A and then x or q.
Services
Make sure the smsd service is enabled to start on boot# chkconfig --list smsd
smsd 0:off 1:off 2:off 3:on 4:off 5:off 6:off
Enable the service on boot for runlevel 3,4 and 5 by using the following command# chkconfig smsd on
To start/stop the service use following command# service smsd stop
# service smsd start
Make sure the smsd service is running by using the command line
# service smsd status
smsd (pid 1476 1475) is running...
Or check the service status via OP5 webbased GUI
Make sure you can send a SMS message by using OP5 webbased GUI.
To send SMS notifications, make sure your contacts have filled out the ‘Pager’ information
Troubleshooting
CMS Error: 314
AT+CMGS="+41796316771"
+CMS ERROR: 314
CMS Error: 314 usualy means the device is busy and you have to try later again. Sometimes you can try as long as you want, you wont become able to send messages. If this is the case try to reset your GSM modem by using following command and try again afterwards, you may have solved the problem with that.
AT&F
CMS Error: 500
CMS ERROR: 500 is unfortunately a very generic error message. Try to send an SMS directly without storing it to the SIM.
AT+CMGS ‘ Send an SMS directly without storing to the SIM
AT+CMGW ‘ Writing an SMS to the SIM card and then send the SMS
AT+CMGR ‘ By using the CMGR command you can verify if the SMS is written to SIM and it’s current status
Read your configured Service-Center number configured on your SIM card to send SMS messages (for example the number of Swisscom)AT+CSCA?
+CSCA: "+41794999000",145
If the number is not correctly configured then change it by usingAT+CSCA="+41794999000",145
OK
PIN codes by using AT commands
If you have a PIN code enabled SIM card and want to remove / disable the PIN code by using AT commands, then follow these commands. Suppose 9546 is the current PIN code, replace 9546 with your PIN code. Query the state of the SIM card by using the CPIN? command and remove the SIM code afterwards.
AT+CPIN?
+CPIN: SIM PIN ----> pin codes need to be entered
OK
AT+CPIN="9546"
OKAT+CLCK="SC",0,"9546" ----> disable pin code
OKAT+CPIN?
+CPIN: READY
Attached some examples about PIN and PUK management:
AT+CLCK="SC",1,"0000",1 ---->When you want to set pin code "0000"
OK
--Reboot module
AT+CPIN?
+CPIN: SIM PIN
OK
AT+CPIN="0000"
OK
AT+CPWD="SC","0000","1234" ---->When you want to change the pin code to "1234"
OK
--Reboot module
AT+CPIN?
+CPIN: SIM PIN
OK
AT*PSPRAS?
*PSPRAS: 3,10,255,255
OK
AT+CPIN="7777" ---->Input the wrong pin code will reduce the available try times
+CME ERROR: incorrect password
AT*PSPRAS?
*PSPRAS: 2,10,255,255
OK
AT+CPIN="1234"
OK
AT+CPIN?
+CPIN: SIM PUK
OK
AT+CPIN="44753796","1234" ---->When you want to input the PUK code after you input 3 times of the wrong pin.
OK
GSM connection state details
Check for Received Signal Strength & Quality
AT+CSQ
+CSQ: 13,1
Wait for the response in format: +CSQ: <rssi>, <ber>
<rssi>
Integer from 0 to 99 indicates the received signal strength. NOTE: Signal strength less than 6 indicates only 1 antenna bar, the quality of a connection will be poor and the connection may even drop.
<rssi> value | Signal strength | Indication (for devices with a User Interface (MMI)) |
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 |
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 |
<bet>
Integer from 0 to 7 and 99 reports the received signal quality measured on the radio traffic channel (error bit rate in percent)
Check if device is registered to the network
AT+CREG?
+CREG: 0,1
Wait for response in the format: +CREG: <mode>, <stat>
<mode>
0 GSM
2 UTRAN
<stat>
0 – not registered, ME is not currently searching a new operator to register to
1 – registered, home network
2 – not registered, but ME is currently searching a new operator to register to
3 – registration denied
4 – unknown
5 – registered, roaming
Overall overview
“battchg” – battery charge level – battery charge level indicator range 0..5
“signal” – signal quality – signal quality indicator, range: 0 to 7, 99 – not measurable
“service” – service availability – service availability indicator, range: 0 – not registered to any network, 1 – registered
AT+CIND=?
+CIND: (("battchg",(0-5,99)),("signal",(0-7,99)),("service",(0,1)),("sounder",()
Reboot device
AT#REBOOT
Check device hardware
Manufacturer Identification
AT+GMI
Telit
Model Identification
AT+GMM
HE910-D
Revidion Identification
AT+GMR
12.00.024
Serial Identification
AT+GSN
00007406xx
GSM Equipment and Network Error Codes
When controlling GSM devices using AT commands, the device can respond with either “OK” or “ERROR”. Sometimes you will receive an error and you do not know the cause of this error. That’s why most advanced GSM devices support extended errors. Instead of just displaying the “ERROR” message, it also shows an error number. The syntax of this extended error is either “+CMS ERROR: xxx” or “+CME ERROR: xxx”. When the error starts with “+CME ERROR”, it means that the error is a device specific error code. For instance, you are trying to read a phonebook entry before entering a pincode. When there is a network error, for instance, when you try to send an SMS message when there is no network coverage, you will receive an error which starts with “+CMS ERROR”. To enable these extended commands, execute the following commands, or add them to your modems init string:
AT+CMEE=1
AT&W
Below you can find a list containing almost every error code supported by GSM devices.
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 |
CMS ERROR: 516 | Invalid length |
CMS ERROR: 517 | Invalid character in PDU |
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 ERROR: 538 | Invalid parameter |
Reference Guide
Download offline copy: Telit 3G HE910 3G/HSDPA/GSM Modem AT Command Reference R10
Пробный запуск нового GSM модуля A6 от AiThinker. Модуль совместим с российскими сотовыми операторами, потребляет меньше тока, продается на плате с внешним питанием от 5В. Подключим модуль к компьютеру и посмотрим на его старт.
Цель
- Подключить к компьютеру
- Проверить работу АТ команд
- Сделать звонок на модуль
- Проверить потребление тока
Подключение
Для подключения модуля к компьютеру понадобится:
- GSM/GPRS модуль Ai-Thinker A6
- Преобразователь USB TTL UART на базе FTDI
- USB кабель A-Mini
- Кабеля Dupont мама-мама
Далее
- Вставляем СИМкарту в модуль (запрос ПИН-кода у меня выключен)
- Соединяем модуль A6 c FTDI конвертером по следующей схеме:
A6(vcc5) -> FTDI(vcc)
A6(gnd) -> FTDI(gnd)
A6(rx) -> FTDI(tx)
A6(tx) -> FTDI(rx) - На компьютере запускаем терминальную программу, например МОНИТОР ПОРТА в Arduino IDE. Выбираем скорость порта 115200.
- Для включения останется нажать кнопку POWER на модуле не меньше 2 сек. и дальше работать в терминале
После включения в терминале появятся различные информационные строки. Для просмотра версии модуля отправьте команду «ATI» (без кавычек). Для просмотра уровня сигнала отправьте команду «AT+CSQ», появятся «+CSQ:» и два числа через запятую, первое число и есть уровень. Значение в диапазоне от 2 до 30 (чем больше тем лучше).
Попробуйте позвонить на вашу СИМ-карту. В мониторе порта должно появиться RING.
Посмотреть АТ команды для данного модуля можете по ссылке ниже либо тут (совместимые с SIM900)
Энергопотребление
В ходе экспериментов с модулем A6 заметил, ему достаточно было ЗУ для мобильного 5В/550мА со шнуром USB-micro. Контакты были соединены через макетную плату и кабеля Dupont. В схеме был сам GSM модуль A6 + Arduino Nano + датчик температуры DS18B20 + Реле 5В 1канальное, при этом потребление тока всей схемы наблюдал через USB Doctor:
- В режиме простоя — от 40 до 80мА (реле открыто)
- При приеме звонка или отправке СМС — от 80 до 200мА (реле замкнуто)
Примечания
Модуль может автоматически подстраиваться под следующую скорость обмена: 2400, 4800, 9600, 14400, 19200, 28800, 33600, 38400, 57600, 115200, 230400, 460800, 921600. По умолчанию скорость модуля 115200, Если хотите работать на скорости, например, 9600, то после включения модуля прийдется около 3 секунд посылать команду «AT» или другую и модуль сообразит, что с ним хотят общаться на этой скорости.
На Arduino Pro mini 3.3V SoftwareSerial у меня не смог общаться на скорости 115200, пришлось пользоваться 9600.