Author |
Post |
|
#1 Sat Apr 22, 2017 21:28, 85 months ago.
|
Member
Registered: Apr 2017
Location: Switzerland
|
Foxbox platform: Version of smsd: 3.1.20 Name and model of a modem / phone: M35 Interface: USB
Dear all,
having above mentioned error and unable to get the system up and running.
smsd.conf
[GSM3] report_device_details = yes #read_timeout = 60 #init = AT+CPMS="SM" #init = at+cmms=2 #init2 = at+csq #pre_init = yes #init = AT+CMEE=1 #init2 = AT+CPMS="SM" #signal_quality_ber_ignore = yes device = /dev/ttyACM0dummy memory_start = 0 send_delay = 0 voicecall_hangup_ath = yes hangup_incoming_call = yes voicecall_ignore_modem_response = yes regular_run_interval = 300 regular_run_cmd = AT+CSQ init = AT+CSQ regular_run_logfile = /var/log/smsd_run3.log #regular_run_loglevel = 7 incoming = no outgoing = yes queues = GSM3, ALL baudrate = 19200 rtscts = yes cs_convert = yes decode_unicode_text = yes internal_combine = yes eventhandler = /etc/sms/scripts/eventhandlerGSM1 #pin = 0000 #
Any ideas why this error keeps coming up? This happens right after starting the service
2017-04-22 23:20:14.447,7, GSM3: -> AT 2017-04-22 23:20:14.447,7, GSM3: Command is sent, waiting for the answer 2017-04-22 23:20:23.369,7, GSM3: put_command expected (OK)|(ERROR), timeout occurred. 1.
|
|
#2 Sat Apr 22, 2017 21:33, 85 months ago.
|
Member
Registered: Apr 2017
Location: Switzerland
Topic owner
|
Just as a note that I've tried the options commented out in the smsd.conf and using device ttyACM0dummy for interceptty purpose.
|
|
#3 Sat Apr 22, 2017 21:38, 85 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Did you first try with the default baudrate, which is 115200? In some cases USB devices work with that speed, but do not answer if the speed is lowered.
You could also show the dmesg output, after a modem is connected.
|
|
#4 Sat Apr 22, 2017 22:00, 85 months ago.
|
Member
Registered: Apr 2017
Location: Switzerland
Topic owner
|
Here is the dmesg output:
[ 4.801155] usb 3-1: new high-speed USB device number 2 using xhci_hcd [ 4.915986] usb 3-1: New USB device found, idVendor=1a40, idProduct=0201 [ 4.916031] usb 3-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 4.916040] usb 3-1: Product: USB 2.0 Hub [MTT] [ 4.917233] hub 3-1:1.0: USB hub found [ 4.917569] hub 3-1:1.0: 7 ports detected [ 5.198197] usb 3-1.1: new full-speed USB device number 3 using xhci_hcd [ 5.288648] usb 3-1.1: New USB device found, idVendor=04e2, idProduct=1414 [ 5.288658] usb 3-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5.320037] cdc_acm 3-1.1:1.0: ttyACM0: USB ACM device [ 5.321307] cdc_acm 3-1.1:1.2: ttyACM1: USB ACM device [ 5.322422] cdc_acm 3-1.1:1.4: ttyACM2: USB ACM device [ 5.323483] cdc_acm 3-1.1:1.6: ttyACM3: USB ACM device [ 5.324509] usbcore: registered new interface driver cdc_acm [ 5.324515] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 5.369208] usb 3-1.2: new full-speed USB device number 4 using xhci_hcd [ 5.459637] usb 3-1.2: New USB device found, idVendor=04e2, idProduct=1414 [ 5.459646] usb 3-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5.462724] cdc_acm 3-1.2:1.0: ttyACM4: USB ACM device [ 5.464332] cdc_acm 3-1.2:1.2: ttyACM5: USB ACM device [ 5.465818] cdc_acm 3-1.2:1.4: ttyACM6: USB ACM device [ 5.467398] cdc_acm 3-1.2:1.6: ttyACM7: USB ACM device [ 5.544221] usb 3-1.5: new full-speed USB device number 5 using xhci_hcd [ 5.634683] usb 3-1.5: New USB device found, idVendor=04e2, idProduct=1414 [ 5.634693] usb 3-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5.637785] cdc_acm 3-1.5:1.0: ttyACM8: USB ACM device [ 5.639389] cdc_acm 3-1.5:1.2: ttyACM9: USB ACM device [ 5.640982] cdc_acm 3-1.5:1.4: ttyACM10: USB ACM device [ 5.642644] cdc_acm 3-1.5:1.6: ttyACM11: USB ACM device [ 5.719233] usb 3-1.6: new full-speed USB device number 6 using xhci_hcd [ 5.809672] usb 3-1.6: New USB device found, idVendor=04e2, idProduct=1414 [ 5.809681] usb 3-1.6: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5.812847] cdc_acm 3-1.6:1.0: ttyACM12: USB ACM device [ 5.814240] cdc_acm 3-1.6:1.2: ttyACM13: USB ACM device [ 5.815829] cdc_acm 3-1.6:1.4: ttyACM14: USB ACM device [ 5.817396] cdc_acm 3-1.6:1.6: ttyACM15: USB ACM device
With baudrate 115200, response still:
2017-04-22 23:59:14.745,2, GSM3: Modem handler 0 terminated. PID: 3458, was started 17-04-22 23:56:48. 2017-04-22 23:59:15.587,5, GSM3: Modem handler 0 has started. PID: 6367. Will only send messages. 2017-04-22 23:59:15.588,5, GSM3: Using read_timeout 60 seconds. 2017-04-22 23:59:15.589,6, GSM3: Checking if modem is ready 2017-04-22 23:59:15.689,7, GSM3: -> AT 2017-04-22 23:59:15.689,7, GSM3: Command is sent, waiting for the answer 2017-04-22 23:59:45.724,7, GSM3: put_command expected (OK)|(ERROR), timeout occurred. 1.
|
|
#5 Sat Apr 22, 2017 22:27, 85 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
You have four MC35 modules, right? Can you show exact model/type of that device?
It seems that each module provides four ports, and usually all ports (with other modems) cannot be used with AT commands. I think that with the first module you should test remaining ports (1, 2 and 3), assuming that ttyACM0 was already tested.
|
|
#6 Sun Apr 23, 2017 11:05, 85 months ago.
|
Member
Registered: Apr 2017
Location: Switzerland
Topic owner
|
16; ACM0-ACM15, Quectel M35. I noticed that it is not mentioned in the supported hardware, could that be an issue?
|
|
#7 Tue Apr 25, 2017 11:47, 85 months ago.
|
Member
Registered: Apr 2017
Location: Switzerland
Topic owner
|
Any ideas?
|
|
#8 Tue Apr 25, 2017 18:45, 85 months ago.
|
Administrator
Registered: May 2009
Location: Jyväskylä, Finland
|
Right now I do not have any other idea than trying /dev/ttyACM0 with Minicom, to see if it works or not. Type AT (enter) and the modem should answer OK.
|