Fastrack with smstool hangs


#1

using a fastrack extend or fastrack supreme with smstool, it happens sometime that the modem hangs (at least the AT interface), there is no way to access through the serial connection (using raw device nor minicom,…)
The only way is to disconnect the power from fastrack and reconnect.
Gsm signal is constantly on 27.

Modem connected with serial cable to a centos 5 host.

this is the smstool modem configuration :
device = /dev/ttyS0
incoming = yes
cs_convert = yes
baudrate = 115200
mode = new

there is a way to avoid the hang?
there is a way to reset the modem without manually disconnect the power?


#2

Hi,

Can you please elaborate more the “smstool” you are using?
Ideally please provide the link and log when it runs on your machine with fastrack.

Thx
L


#3

The tool we use is:
smstools3.kekekasvi.com/
the version:
smstools-3.1.14-9

With other kind of model on the same OS we never get this problem.

The configuration:

[GSM1]
device = /dev/ttyS0
baudrate = 115200
mode = new
incoming = yes
cs_convert = yes
report = no
regular_run_interval = 60
regular_run_cmd = AT+CREG?;+CSQ;+COPS?

here the piece of smstools log where a sms is sent and then the serial connection to the modem became unavailable:

2012-06-28 05:21:45,6, GSM1: Pre-initializing modem
2012-06-28 05:21:45,7, GSM1: -> ATE0+CMEE=1;+CREG=2
2012-06-28 05:21:45,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:21:45,7, GSM1: <- OK
2012-06-28 05:21:46,7, GSM1: -> AT+CSQ
2012-06-28 05:21:46,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:21:46,7, GSM1: <- +CSQ: 22,0 OK
2012-06-28 05:21:46,6, GSM1: Signal Strength Indicator: (22,0) -69 dBm (Excellent), Bit Error Rate: less than 0.2 %
2012-06-28 05:21:46,6, GSM1: Checking if Modem is registered to the network
2012-06-28 05:21:46,7, GSM1: -> AT+CREG?
2012-06-28 05:21:46,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:21:46,7, GSM1: <- +CREG: 2,1,“4E76”,“0187” OK
2012-06-28 05:21:46,6, GSM1: Modem is registered to the network
2012-06-28 05:21:46,6, GSM1: Selecting PDU mode
2012-06-28 05:21:47,7, GSM1: -> AT+CMGF=0
2012-06-28 05:21:47,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:21:47,7, GSM1: <- OK
2012-06-28 05:21:47,6, GSM1: Checking memory size
2012-06-28 05:21:47,7, GSM1: -> AT+CPMS?
2012-06-28 05:21:47,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:21:48,7, GSM1: <- +CPMS: “SM”,0,50,“SM”,0,50,“SM”,0,50 OK
2012-06-28 05:21:48,6, GSM1: Used memory is 0 of 50
2012-06-28 05:21:48,6, GSM1: No SMS received
2012-06-28 05:21:59,5, smsd: Moved file /var/spool/sms/outgoing/send_Wh6608 to /var/spool/sms/checked
2012-06-28 05:21:59,6, GSM1: I have to send 1 short message for /var/spool/sms/checked/send_Wh6608
2012-06-28 05:21:59,6, GSM1: Sending SMS from to 393351214750
2012-06-28 05:21:59,6, GSM1: Checking if modem is ready
2012-06-28 05:21:59,7, GSM1: -> AT
2012-06-28 05:21:59,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:21:59,5, smsd: Moved file /var/spool/sms/outgoing/send_eG6634 to /var/spool/sms/checked
2012-06-28 05:21:59,7, GSM1: <- OK
2012-06-28 05:21:59,6, GSM1: Pre-initializing modem
2012-06-28 05:21:59,7, GSM1: -> ATE0+CMEE=1;+CREG=2
2012-06-28 05:21:59,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:22:00,7, GSM1: <- OK
2012-06-28 05:22:00,7, GSM1: -> AT+CSQ
2012-06-28 05:22:00,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:22:00,7, GSM1: <- +CSQ: 22,0 OK
2012-06-28 05:22:00,6, GSM1: Signal Strength Indicator: (22,0) -69 dBm (Excellent), Bit Error Rate: less than 0.2 %
2012-06-28 05:22:00,6, GSM1: Checking if Modem is registered to the network
2012-06-28 05:22:01,7, GSM1: -> AT+CREG?
2012-06-28 05:22:01,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:22:01,7, GSM1: <- +CREG: 2,1,“4E76”,“0187” OK
2012-06-28 05:22:01,6, GSM1: Modem is registered to the network
2012-06-28 05:22:01,6, GSM1: Selecting PDU mode
2012-06-28 05:22:01,7, GSM1: -> AT+CMGF=0
2012-06-28 05:22:01,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:22:02,7, GSM1: <- OK
2012-06-28 05:22:02,7, GSM1: -> ATE1+CMGS=136
2012-06-28 05:22:02,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:22:02,7, GSM1: <- >
2012-06-28 05:22:02,7, GSM1: -> 0011000C919333151274050000FF8BCE32BD982F835A20A8F42964169BA016283985828A75F9DB9EA6A7412D90B83E4FBBCBF379042E7F8FCBF379790E6A8162B29B0BE682B962A01668284D5293C32013D402C9702D98AD2583C56420584D278BE96836500B24ACCFD3EEF27C0E82CADFE3F27C0E1A4A93D4E430C8D481925328A85897BFED697A1A
2012-06-28 05:22:02,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:23:00,5, smsd: Moved file /var/spool/sms/outgoing/send_D16063 to /var/spool/sms/checked
2012-06-28 05:23:00,5, smsd: Moved file /var/spool/sms/outgoing/send_h16037 to /var/spool/sms/checked
2012-06-28 05:23:03,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 1.
2012-06-28 05:23:03,7, GSM1: <- 0011000C919333151274050000FF8BCE32BD982F835A20A8F42964169BA016283985828A75F9DB9EA6A7412D90B83E4FBBCBF379042E7F8FCBF379790E6A8162B29B0BE682B962A01668284D5293C32013D402C9702D98AD2583C56420584D278BE96836500B24ACCFD3EEF27C0E82CADFE3F27C0E1A4A93D4E430C8D481925328A85897BFED697A1A
2012-06-28 05:23:03,5, GSM1: Verify PDU: OK
2012-06-28 05:23:04,7, GSM1: -> ATE0
2012-06-28 05:23:04,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:23:09,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 2.
2012-06-28 05:23:09,7, GSM1: <- ATE0 >
2012-06-28 05:23:09,3, GSM1: The modem answer was not OK: 0011000C919333151274050000FF8BCE32BD982F835A20A8F42964169BA016283985828A75F9DB9EA6A7412D90B83E4FBBCBF379042E7F8FCBF379790E6A8162B29B0BE682B962A01668284D5293C32013D402C9702D98AD2583C56420584D278BE96836500B24ACCFD3EEF27C0E82CADFE3F27C0E1A4A93D4E430C8D481925328A85897BFED697A1A
2012-06-28 05:23:09,5, GSM1: Waiting 10 sec. before retrying
2012-06-28 05:23:19,6, GSM1: Checking if modem is ready
2012-06-28 05:23:19,7, GSM1: -> AT
2012-06-28 05:23:19,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:23:24,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 3.
2012-06-28 05:23:24,7, GSM1: <- AT >
2012-06-28 05:23:25,7, GSM1: ->
2012-06-28 05:23:25,7, GSM1: Command is sent, waiting for the answer
2012-06-28 05:23:30,7, GSM1: put_command expected (OK)|(ERROR), timeout occurred. 4.
2012-06-28 05:23:30,7, GSM1: <-
2012-06-28 05:23:30,7, GSM1: -> AT

Thanks for the help!


#4

Hi,

I setup the same tool and tested on Ubuntu 10.x using USB-to-Serial cable with Q2687 FW R7.46 and outgoing/incoming SMS is ok.

I am new to the tool and followed your configuration, using below syntex message was sent without problem:
sendsms

Here’s the config file and log attached:

devices = GSM1
logfile = /var/log/smsd.log
loglevel = 7

[GSM1]
read_timeout=1
device = /dev/ttyUSB0
baudrate=115200
mode=new
incoming = yes
cs_convert =yes
report= no
regular_run_interval =60
regular_run_cmd=AT+CREG?;+CSQ;+COPS?

Do you know what FW is running on your Fastrack and what’s the exact model no?
Are you succeed sending SMS with AT cmd using same network SIM?
For example:
AT+CMGF=1
OK
AT+CMGS="+123123123" (please replace with actual phone number)

hello<Ctrl+z>
+CMGS: 9
OK

Can you send below AT command and share the response as well?
ATI3
AT+CSMP?
AT+CGSMS?

P.S. I also checked the PDU in your log and tested sending SMS to it once… please execpt 1 SMS was received. :wink:

Thanks.


#5

found the solution, or better a workaround: downgrading smstools package to smstools-3.1.3-4 the modem works without hangs!