Thales' cellular IoT products business is now part of Telit Cinterion, find out more.

You are here

Community > Forum > Cellular Hardware > Invalid dial command on PLS8-E modem

Invalid dial command on PLS8-E modem | Telit Cinterion IoT Developer Community

Like
0
5
daniel.onisoru's picture
daniel.onisoru

March 25, 2016 - 11:25am, 5472 views

Hello,

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

Thank you.

5
Comment
Log in or register to post comments
Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Mar 25 2016 - 3:11pm

Hello,

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.

Regards,

Bartłomiej

daniel.onisoru's picture
daniel.onisoru
Mar 25 2016 - 3:49pm

I've tested the  AT^SQPORT and I got the fllowing reply:

 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
ATQ0 V1 E1 S0=0 &C1 &D2
OK
--> Sending: AT&W
AT&W
OK
--> Sending: AT^SQPORT
AT^SQPORT
^SQPORT: Application
OK
--> Modem initialized.
--> Sending: ATD*99***1#
--> Waiting for carrier.
ATD*99***1#
+CME ERROR: 2
--> Invalid dial command.

So it seems it's the application port. How do I change it?

Thank you.

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Mar 25 2016 - 4:27pm

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.

Regards,

Bartłomiej

daniel.onisoru's picture
daniel.onisoru
Mar 28 2016 - 1:10pm

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.

 root@wink-desktop:~# wvdialconf
Editing `/etc/wvdial.conf'.

Scanning your serial ports for a ****m.

ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyS3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyS3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyS3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
Modem Port Scan<*1>: S4   S5   S6   S7   S8   S9   S10  S11
Modem Port Scan<*1>: S12  S13  S14  S15  S16  S17  S18  S19
Modem Port Scan<*1>: S20  S21  S22  S23  S24  S25  S26  S27
Modem Port Scan<*1>: S28  S29  S30  S31
ttyACM0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyACM0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyACM0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyACM1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyACM1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyACM1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyACM2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyACM2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyACM2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyACM3<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyACM3<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyACM3<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
ttyACM4<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
ttyACM4<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
ttyACM4<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.


Sorry, no ****m was detected!  Is it in use by another program?
Did you configure it properly with setserial?

The ****m is still present in lsusb and dmesg

 root@wink-desktop:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 1e2d:0061
Bus 001 Device 005: ID 09da:000a A4Tech Co., Ltd. Optical Mouse Opto 510D / OP-620D
Bus 001 Device 007: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

wink@wink-desktop:~$ dmesg | grep ttyACM
[    3.523073] cdc_acm 1-4.3:1.0: ttyACM0: USB ACM device
[    3.528934] cdc_acm 1-4.3:1.2: ttyACM1: USB ACM device
[    3.541246] cdc_acm 1-4.3:1.4: ttyACM2: USB ACM device
[    3.542891] cdc_acm 1-4.3:1.6: ttyACM3: USB ACM device
[    3.544057] cdc_acm 1-4.3:1.8: ttyACM4: USB ACM device

I do see some error in dmesg

[   13.931694] cdc_ether 1-4.3:1.10 usb0: CDC: unexpected notification 01!
[   13.931747] cdc_ether 1-4.3:1.12 usb1: CDC: unexpected notification 01!
[   15.045128] cdc_acm 1-4.3:1.8: failed to set dtr/rts
[   29.962943] cdc_ether 1-4.3:1.10 usb0: CDC: unexpected notification 01!
[   29.963002] cdc_ether 1-4.3:1.12 usb1: CDC: unexpected notification 01!

Thank you.

Bartłomiej Gemalto Moderator's picture
Bartłomiej Gema...
Mar 30 2016 - 3:07pm

Hello,

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.

Regards,

Bartłomiej