Invalid dial command on PLS8-E modem | Telit Cinterion IoT Developer Community
March 25, 2016 - 11:25am, 5472 views
I'm trying to setup a PLS8-E modem on ubuntu 14.02
I've tried various configurations but I always get +CME ERROR: 2 Invalid dial command.
I also tried to send a SMS message with gnokii and that works fine.
root@wink-desktop:~# wvdial orange --> WvDial: Internet dialer version 1.61 --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK --> Sending: AT+CMEE=1 AT+CMEE=1 OK --> Sending: AT&W AT&W OK --> ****m initialized. --> Sending: ATDT*99# --> Waiting for carrier. ATDT*99# +CME ERROR: 2 --> Invalid dial command. --> Disconnecting at Fri Mar 25 06:19:51 2016
The wvdial config is:
[Dialer Defaults] Stupid **** = 1 ****m Type = Analog ****m ISDN = 0 Phone = *99# ****m = /dev/ttyACM1 Username = internet Dial Command = ATDT Password = internet New PPPD = yes [Dialer orange] Init2 = ATZ Init3 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Init4 = AT+CMEE=1 Init5 = AT&W Stupid **** = 1 Phone = *99# ISDN = 0 ****m = /dev/ttyACM1 ****m Type = Analog ****m Baud = 115200 Username = net New PPPD = yes Check Def Route = no
Any ideas on this ?
Also I am unable to make the GPS work on any /dev/ttyACM
Please check if there is a PDP context defined with AT+CGDCONT command. It is recommended to specify the context while dialling (e.g. ATD*99***1#). If parameter is not specified, then the first defined primary context is used.
ATDT seems strange but the 'T' should be ignored according to documentation. I'd try this manually.
Please also check AT^SQPORT? reply to verify if you are using the modem and not application port.
I've tested the AT^SQPORT and I got the fllowing reply:
So it seems it's the application port. How do I change it?
You need to use at^ssrvset command.
at^ssrvset="current" - to check the current setting
at^ssrvset? - to list the possible settings
at^ssrvset="actSrvSet",2 - to set the service set number (2 in this case)
Restart is needed.
There are more possibilities - please see the AT commands specification document for details.
I've tried ssrvset but it didn't work.
It was still on application ****.
Howerver now I am unable to contact the ****m at all. None of the /tty/ACM* ports work.
The ****m is still present in lsusb and dmesg
I do see some error in dmesg
Could you paste the log for ssrvset configuration. Does it reply with ERROR or there's some other issue? Please check the firmware version with ATI1 command if it's possible. There was no ssrvset command in the old release 1. But you should probably have at least release 2.
Can you connect to the module with the terminal and send at commands to it on any interface?
It would be the best way to configure it properly via terminal and then try with the dialling program.