[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: smsd problem with AT model - Part II
From: |
Romain Parmantier - Mobile Devices |
Subject: |
RE: smsd problem with AT model - Part II |
Date: |
Thu, 5 Oct 2006 16:41:14 +0200 |
Hi All,
Thanks for your answer and your help.
First, answer to your question :
>> 02 41 54 2b 43 50 4d 53 3f 0d 0d 0a 2b 43 50 4d | AT+CPMS? +CPM
>> 53 3a 20 22 53 4d 22 2c 33 30 2c 33 30 2c 22 53 | S: "SM",30,30,"S
>> 4d 22 2c 33 30 2c 33 30 0d 0a 0d 0a 4f 4b 0d | M",30,30 OK
>> Received message type 12
>> GN_OP_GetSMSStatus at line 400 in file lowlevel.c returns error 1
>this is the error *before* the patch?
I have this error *after* the patch.
About your email, I have copy this patch and apply it on my gnokii version.
Indeed, I have forgotten a piece of the patch (T_SetSMSMemoryType() function)
but it still doesn't work. "gnokii --identify" and "gnokii --sendsms" always
work but "gnokii --getsms" doesn't.
It seems that my modem doesn't support PDU mode according the following log :
=============8<============================
address@hidden ~ # gnokii --getsms SM 1
GNOKII Version 0.6.14
LOG: debug mask is 0x1
LOG: rlpdebug mask is 0x1
LOG: xdebug mask is 0x1
phone instance config:
model: AT
port_device: /dev/ttyS0
connection_type: 0
init_length: 0
serial_baudrate: 115200
serial_write_usleep: -1
hardware_handshake: 1
require_dcd: 0
smsc_timeout: 100
connect_script:
disconnect_script:
rfcomm_cn: 1
sm_retry: off
Initializing AT capable mobile phone ...
Serial device: opening device /dev/ttyS0
Serial device: setting RTS to high and DTR to high
Message sent: 0x00 / 0x0004
41 54 5a 0d | ATZ
write: [ATZ<cr>]
read : [ATZ<cr><cr><lf>OK<cr><lf>]
Message received: 0x00 / 0x000a
02 41 54 5a 0d 0d 0a 4f 4b 0d | ATZ OK
Received message type 00
Message sent: 0x00 / 0x0005
41 54 45 31 0d | ATE1
write: [ATE1<cr>]
read : [ATE1<cr><cr><lf>OK<cr><lf>]
Message received: 0x00 / 0x000b
02 41 54 45 31 0d 0d 0a 4f 4b 0d | ATE1 OK
Received message type 00
Message sent: 0x00 / 0x000a
41 54 2b 43 4d 45 45 3d 31 0d | AT+CMEE=1
write: [AT+CMEE=1<cr>]
read : [AT+CMEE=1<cr><cr><lf>OK<cr><lf>]
Message received: 0x00 / 0x0010
02 41 54 2b 43 4d 45 45 3d 31 0d 0d 0a 4f 4b 0d | AT+CMEE=1 OK
Received message type 00
Message sent: 0x06 / 0x0008
41 54 2b 43 47 4d 4d 0d | AT+CGMM
write: [AT+CGMM<cr>]
read : [AT+CGMM<cr><cr><lf> MULTIBAND 900E 1800 <cr><lf><cr><lf>OK<cr><lf>]
Message received: 0x06 / 0x0029
02 41 54 2b 43 47 4d 4d 0d 0d 0a 20 4d 55 4c 54 | AT+CGMM MULT
49 42 41 4e 44 20 20 39 30 30 45 20 20 31 38 30 | IBAND 900E 180
30 20 0d 0a 0d 0a 4f 4b 0d | 0 OK
Received message type 06
Message sent: 0x06 / 0x0008
41 54 2b 43 47 4d 49 0d | AT+CGMI
write: [AT+CGMI<cr>]
read : [AT+CGMI<cr><cr><lf> WAVECOM MODEM<cr><lf><cr><lf>OK<cr><lf>]
Message received: 0x06 / 0x0020
02 41 54 2b 43 47 4d 49 0d 0d 0a 20 57 41 56 45 | AT+CGMI WAVE
43 4f 4d 20 4d 4f 44 45 4d 0d 0a 0d 0a 4f 4b 0d | COM MODEM OK
Received message type 06
Message sent: 0x61 / 0x0009
41 54 2b 43 53 43 53 3f 0d | AT+CSCS?
write: [AT+CSCS?<cr>]
read : [AT+CSCS?<cr><cr><lf>+CSCS: "PCCP437"<cr><lf><cr><lf>OK<cr><lf>]
Message received: 0x61 / 0x0023
02 41 54 2b 43 53 43 53 3f 0d 0d 0a 2b 43 53 43 | AT+CSCS? +CSC
53 3a 20 22 50 43 43 50 34 33 37 22 0d 0a 0d 0a | S: "PCCP437"
4f 4b 0d | OK
Received message type 61
Initialisation completed
Message sent: 0x12 / 0x0009
41 54 2b 43 50 4d 53 3f 0d | AT+CPMS?
write: [AT+CPMS?<cr>]
read : [AT+CPMS?<cr><cr><lf>+CPMS:
"SM",30,30,"SM",30,30<cr><lf><cr><lf>OK<cr><lf>]
Message received: 0x12 / 0x002f
02 41 54 2b 43 50 4d 53 3f 0d 0d 0a 2b 43 50 4d | AT+CPMS? +CPM
53 3a 20 22 53 4d 22 2c 33 30 2c 33 30 2c 22 53 | S: "SM",30,30,"S
4d 22 2c 33 30 2c 33 30 0d 0a 0d 0a 4f 4b 0d | M",30,30 OK
Received message type 12
Message sent: 0x00 / 0x0017
41 54 2b 43 50 4d 53 3d 22 53 4d 22 2c 22 53 4d | AT+CPMS="SM","SM
22 0d 00 00 00 00 00 | "
write: [AT+CPMS="SM","SM"<cr>address@hidden@address@hidden@address@hidden
Message sent: 0x00 / 0x0017
41 54 2b 43 50 4d 53 3d 22 53 4d 22 2c 22 53 4d | AT+CPMS="SM","SM
22 2c 22 4d 45 22 0d | ","ME"
write: [AT+CPMS="SM","SM","ME"<cr>]
read : [AT+CPMS="SM","SM"<cr>^@<cr><lf>+CPMS:
30,30,30,30<cr><lf><cr><lf>OK<cr><lf>]
Message received: 0x00 / 0x002f
02 41 54 2b 43 50 4d 53 3d 22 53 4d 22 2c 22 53 | AT+CPMS="SM","S
4d 22 0d 00 0d 0a 2b 43 50 4d 53 3a 20 33 30 2c | M" +CPMS: 30,
33 30 2c 33 30 2c 33 30 0d 0a 0d 0a 4f 4b 0d | 30,30,30 OK
Received message type 00
Message sent: 0x63 / 0x000a
41 54 2b 43 4d 47 46 3d 30 0d | AT+CMGF=0
write: [AT+CMGF=0<cr>]
read : [^A.+CPMS="SM","SM","ME"<cr><cr><lf>+CMS ERROR: 302<cr><lf>]
Message received: 0x63 / 0x002a
04 01 2e 2b 43 50 4d 53 3d 22 53 4d 22 2c 22 53 | .+CPMS="SM","S
4d 22 2c 22 4d 45 22 0d 0d 0a 2b 43 4d 53 20 45 | M","ME" +CMS E
52 52 4f 52 3a 20 33 30 32 0d | RROR: 302
Received message type 63
PDU mode not supported
GetSMS SM 1 failed! (Command failed.)
Serial device: closing device
=============8<============================
But, when I used minicom, I can use PDU mode :
=============8<============================
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
at+cmgf=1
OK
at+cmgf=0
OK
at+cmgl=4
+CMGL: 1,1,,47
07913366003000F0040B913366706853F50000600120811055801F43A791D57E93CB6DD7D86D0EC3
DDACB04CFCAEE7CFF432DB357EB701
+CMGL: 2,1,,68
07913366003000F0040B913366706853F500006001208190908038737A985E9FB366B5584D5683C5
60B61A4C9683B1602C18AB9A9BD56032186B1883B18E2C28ABC912B3A4E
+CMGL: 3,1,,127
07913366003000F0000B913366963577F40000609002809084807BB0180C2693E940822354DA1CB2
6036582E1673C160AC208B869BD95C369A0DC772B260305B2CE6C2D5682
+CMGL: 4,1,,99
07913366003000F0000B913366964576F40000609002802100805BB0180C26A3E940822354DA1CB2
60B6580C0673C1602C2B8BC562B1582C190C9683D9582C9653559BB1622
...
=============8<============================
Regards,
--
Romain PARMANTIER - Mobile Devices Ingenierie
12 rue Roger Salengro 94 270 Kremlin Bicêtre
Tél.: (+33) 142 119 325 Fax: (+33) 142 118 717
http://www.mobile-devices.fr
- smsd problem with AT model - Part II, Romain Parmantier - Mobile Devices, 2006/10/05
- RE: smsd problem with AT model - Part II,
Romain Parmantier - Mobile Devices <=
- Re: smsd problem with AT model - Part II, Daniele Forsi, 2006/10/05
- Re: smsd problem with AT model - Part II, Pawel Kot, 2006/10/05
- Re: smsd problem with AT model - Part II, Pawel Kot, 2006/10/05
- RE: smsd problem with AT model - Part II, Romain Parmantier - Mobile Devices, 2006/10/06
- Re: smsd problem with AT model - Part II, Pawel Kot, 2006/10/06
- RE: smsd problem with AT model - Part II, Romain Parmantier - Mobile Devices, 2006/10/09
- Re: smsd problem with AT model - Part II, Pawel Kot, 2006/10/09
- Re: smsd problem with AT model - Part II, Daniele Forsi, 2006/10/06
- Re: smsd problem with AT model - Part II, Pawel Kot, 2006/10/06