# Problem AT Commands in Linux **URL:** \ **Category:** MC/EM Series\ **Created:** [May 11, 2016, 8:21pm UTC](https://forum.sierrawireless.com/t/problem-at-commands-in-linux/8564 "2016-05-11T20:21:20Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![aponce](https://avatars.discourse-cdn.com/v4/letter/a/ed8c4c/32.png) [@aponce](https://forum.sierrawireless.com/u/aponce)\ **Post date:** [May 11, 2016, 8:21pm UTC](https://forum.sierrawireless.com/t/problem-at-commands-in-linux/8564/1 "2016-05-11T20:21:20Z")
Hi guys, I have a problem with the modem MC8795V, this device is installed on OS: Ubuntu 12.04 LTS Kernel: 3.2.0-23-generic Driver v.1.7.50 When I run the command “ati” by minicom in the /dev/ttyUSB4 gives me the following reply: * * * ati Sierra Wireless, Incorporated MC8795V APP1 ## OK In other times the command ATi send me more information about dispositvo: * * * ati Manufacturer: Sierra Wireless, Incorporated Model: MC8795V Revision: K2\_0\_7\_46CAP C: / WS / FW / K2\_0\_7\_46CAP / MSM6290 / SRC 2010/12/13 22:29:01 IMEI: 355310038197335 IMEI SV: 25 FSN: CHJ2904329110 3GPP Release 6 - GCAP: + CGSM, + FCLASS, + DS ## OK Another thing I’ve seen is that there are more commands than just answer me with “OK” as in the case of “AT!GSTATUS?” command? Anyone know if this is normal or if I have to do something to get more information modem? Best Regards. PS: Sorry for my bad English. ---
**Author:** ![mlw](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/mlw/32/3706_2.png) [@mlw](https://forum.sierrawireless.com/u/mlw)\ **Post date:** [May 12, 2016, 7:38am UTC](https://forum.sierrawireless.com/t/problem-at-commands-in-linux/8564/2 "2016-05-12T07:38:35Z")
Hi, The clue is in the response from the ATI command where it responds with APP1, this inidcates that it in the end point intended for use with a dial up connection and as a result does not have a full AT parser operational on it hence it just answers OK to most of the commands without giving the expected response. I suspect on your system that the full AT parser is going to be on /dev/ttyUSB3, run minicom against this and see what happens. Regards Matt ---
**Author:** ![aponce](https://avatars.discourse-cdn.com/v4/letter/a/ed8c4c/32.png) [@aponce](https://forum.sierrawireless.com/u/aponce)\ **Post date:** [May 12, 2016, 4:35pm UTC](https://forum.sierrawireless.com/t/problem-at-commands-in-linux/8564/3 "2016-05-12T16:35:12Z")
thanks for you answeer mlw!!! 😃 , OK lets beggin!!! * * * ## – Get the modem device ttyUSB – root@ubuntu:~# dmesg | grep ttyUSB [442.374716] usb 1-2: Sierra USB modem converter now attached to ttyUSB0 [442.377216] usb 1-2: Sierra USB modem converter now attached to ttyUSB1 [442.379329] usb 1-2: Sierra USB modem converter now attached to ttyUSB2 [442.381982] usb 1-2: Sierra USB modem converter now attached to ttyUSB3 [442.383400] usb 1-2: Sierra USB modem converter now attached to ttyUSB4 [442.385138] usb 1-2: Sierra USB modem converter now attached to ttyUSB5 [442.386742] usb 1-2: Sierra USB modem converter now attached to ttyUSB6 Well I try connect to /dev/ttyUSB4 again with the “ATI” command and here have the last result (a few info) * * * Welcome to minicom 2.5 OPTIONS: I18n Compiled on May 2 2011, 00:39:27. Port /dev/ttyUSB4 Press CTRL-A Z for help on special keys Sierra Wireless, Incorporated MC8795V APP1 ## OK > [@](#): > > I suspect on your system that the full AT parser is going to be on /dev/ttyUSB3, run minicom against this and see what happens. OK, lets connect to /dev/ttyUSB3. * * * Welcome to minicom 2.5 OPTIONS: I18n Compiled on May 2 2011, 00:39:27. Port /dev/ttyUSB3 Press CTRL-A Z for help on special keys OK ati Manufacturer: Sierra Wireless, Incorporated Model: MC8795V Revision: K2\_0\_7\_46CAP C:/WS/FW/K2\_0\_7\_46CAP/MSM6290/SRC 2010/12/13 22:29:01 IMEI: 355310038197079 IMEI SV: 25 FSN: CHJ2904162310 3GPP Release 6 +GCAP: +CGSM,+DS,+ES OK * * * 😃 With the /dev/ttyUSB3 it’s works!!! but the device isn’t connect to internet provider configuration, now I connect to internet provider with NetworkManager. * * * ## root@ubuntu:~# cat /var/log/syslog May 12 12:59:12 ubuntu kernel: [412.344148] usb 2-1: USB disconnect, device number 2 May 12 12:59:12 ubuntu kernel: [412.344751] pl2303 ttyUSB4: pl2303 converter now disconnected from ttyUSB4 May 12 12:59:12 ubuntu kernel: [412.344855] pl2303 2-1:1.0: device disconnected May 12 12:59:26 ubuntu kernel: [426.298970] usb 1-2: USB disconnect, device number 6 May 12 12:59:26 ubuntu kernel: [426.299526] sierra ttyUSB0: Sierra USB modem converter now disconnected from ttyUSB0 May 12 12:59:26 ubuntu kernel: [426.299623] sierra 1-2:1.0: device disconnected May 12 12:59:26 ubuntu kernel: [426.302102] sierra ttyUSB1: Sierra USB modem converter now disconnected from ttyUSB1 May 12 12:59:26 ubuntu kernel: [426.302208] sierra 1-2:1.1: device disconnected May 12 12:59:26 ubuntu kernel: [426.303753] sierra ttyUSB2: Sierra USB modem converter now disconnected from ttyUSB2 May 12 12:59:26 ubuntu kernel: [426.303860] sierra 1-2:1.2: device disconnected May 12 12:59:26 ubuntu kernel: [426.305002] sierra ttyUSB3: Sierra USB modem converter now disconnected from ttyUSB3 May 12 12:59:26 ubuntu kernel: [426.305108] sierra 1-2:1.3: device disconnected May 12 12:59:26 ubuntu kernel: [426.305849] sierra ttyUSB5: Sierra USB modem converter now disconnected from ttyUSB5 May 12 12:59:26 ubuntu kernel: [426.305947] sierra 1-2:1.4: device disconnected May 12 12:59:26 ubuntu kernel: [426.306679] sierra ttyUSB6: Sierra USB modem converter now disconnected from ttyUSB6 May 12 12:59:26 ubuntu kernel: [426.306778] sierra 1-2:1.5: device disconnected May 12 12:59:26 ubuntu kernel: [426.307505] sierra ttyUSB7: Sierra USB modem converter now disconnected from ttyUSB7 May 12 12:59:26 ubuntu kernel: [426.307611] sierra 1-2:1.6: device disconnected May 12 12:59:26 ubuntu modem-manager[532]: (tty/ttyUSB3): released by modem /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2 May 12 12:59:26 ubuntu NetworkManager[561]: (ttyUSB3): now unmanaged May 12 12:59:26 ubuntu NetworkManager[561]: (ttyUSB3): device state change: disconnected → unmanaged (reason ‘removed’) [30 10 36] May 12 12:59:26 ubuntu NetworkManager[561]: (ttyUSB3): cleaning up… May 12 12:59:26 ubuntu NetworkManager[561]: (ttyUSB3): taking down device. May 12 12:59:26 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 12:59:26 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 12:59:42 ubuntu kernel: [442.236103] usb 1-2: new high-speed USB device number 7 using ehci\_hcd May 12 12:59:42 ubuntu kernel: [442.373301] sierra 1-2:1.0: Sierra USB modem converter detected May 12 12:59:42 ubuntu kernel: [442.374037] usb 1-2: APM supported, enabling autosuspend. May 12 12:59:42 ubuntu kernel: [442.374716] usb 1-2: Sierra USB modem converter now attached to ttyUSB0 May 12 12:59:42 ubuntu kernel: [442.375274] sierra 1-2:1.1: Sierra USB modem converter detected May 12 12:59:42 ubuntu kernel: [442.376434] usb 1-2: APM supported, enabling autosuspend. May 12 12:59:42 ubuntu kernel: [442.377216] usb 1-2: Sierra USB modem converter now attached to ttyUSB1 May 12 12:59:42 ubuntu kernel: [442.377791] sierra 1-2:1.2: Sierra USB modem converter detected May 12 12:59:42 ubuntu kernel: [442.378664] usb 1-2: APM supported, enabling autosuspend. May 12 12:59:42 ubuntu kernel: [442.379329] usb 1-2: Sierra USB modem converter now attached to ttyUSB2 May 12 12:59:42 ubuntu kernel: [442.379889] sierra 1-2:1.3: Sierra USB modem converter detected May 12 12:59:42 ubuntu udevd[1807]: failed to execute ‘/lib/udev/mtp-probe’ ‘mtp-probe /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2 1 7’: No such file or directory May 12 12:59:42 ubuntu kernel: [442.381538] usb 1-2: APM supported, enabling autosuspend. May 12 12:59:42 ubuntu kernel: [442.381982] usb 1-2: Sierra USB modem converter now attached to ttyUSB3 May 12 12:59:42 ubuntu kernel: [442.382343] sierra 1-2:1.4: Sierra USB modem converter detected May 12 12:59:42 ubuntu kernel: [442.383044] usb 1-2: APM supported, enabling autosuspend. May 12 12:59:42 ubuntu kernel: [442.383400] usb 1-2: Sierra USB modem converter now attached to ttyUSB4 May 12 12:59:42 ubuntu kernel: [442.383798] sierra 1-2:1.5: Sierra USB modem converter detected May 12 12:59:42 ubuntu kernel: [442.384782] usb 1-2: APM supported, enabling autosuspend. May 12 12:59:42 ubuntu kernel: [442.385138] usb 1-2: Sierra USB modem converter now attached to ttyUSB5 May 12 12:59:42 ubuntu kernel: [442.385526] sierra 1-2:1.6: Sierra USB modem converter detected May 12 12:59:42 ubuntu kernel: [442.386273] usb 1-2: APM supported, enabling autosuspend. May 12 12:59:42 ubuntu kernel: [442.386742] usb 1-2: Sierra USB modem converter now attached to ttyUSB6 May 12 12:59:42 ubuntu modem-manager[532]: (ttyUSB3) opening serial port… May 12 12:59:42 ubuntu modem-manager[532]: (ttyUSB1) opening serial port… May 12 12:59:42 ubuntu modem-manager[532]: (ttyUSB2) opening serial port… May 12 12:59:42 ubuntu modem-manager[532]: (ttyUSB6) opening serial port… May 12 12:59:42 ubuntu modem-manager[532]: (ttyUSB0) opening serial port… May 12 12:59:42 ubuntu modem-manager[532]: (ttyUSB4) opening serial port… May 12 12:59:42 ubuntu modem-manager[532]: (ttyUSB5) opening serial port… May 12 12:59:44 ubuntu modem-manager[532]: (ttyUSB3) closing serial port… May 12 12:59:44 ubuntu modem-manager[532]: (ttyUSB3) serial port closed May 12 12:59:44 ubuntu modem-manager[532]: (ttyUSB3) opening serial port… May 12 12:59:44 ubuntu modem-manager[532]: (Sierra): GSM modem /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-2 claimed port ttyUSB3 May 12 12:59:45 ubuntu modem-manager[532]: (ttyUSB3) closing serial port… May 12 12:59:45 ubuntu modem-manager[532]: (ttyUSB3) serial port closed May 12 12:59:48 ubuntu modem-manager[532]: (ttyUSB4) closing serial port… May 12 12:59:48 ubuntu modem-manager[532]: (ttyUSB4) serial port closed May 12 12:59:48 ubuntu modem-manager[532]: (ttyUSB5) closing serial port… May 12 12:59:48 ubuntu modem-manager[532]: (ttyUSB5) serial port closed May 12 12:59:48 ubuntu modem-manager[532]: (ttyUSB6) closing serial port… May 12 12:59:48 ubuntu modem-manager[532]: (ttyUSB6) serial port closed May 12 12:59:55 ubuntu modem-manager[532]: (ttyUSB1) closing serial port… May 12 12:59:55 ubuntu modem-manager[532]: (ttyUSB1) serial port closed May 12 12:59:55 ubuntu modem-manager[532]: (ttyUSB1) opening serial port… May 12 12:59:55 ubuntu modem-manager[532]: (ttyUSB0) closing serial port… May 12 12:59:55 ubuntu modem-manager[532]: (ttyUSB0) serial port closed May 12 12:59:55 ubuntu modem-manager[532]: (ttyUSB0) opening serial port… May 12 12:59:58 ubuntu modem-manager[532]: (ttyUSB1) closing serial port… May 12 12:59:58 ubuntu modem-manager[532]: (ttyUSB1) serial port closed May 12 12:59:59 ubuntu modem-manager[532]: (ttyUSB0) closing serial port… May 12 12:59:59 ubuntu modem-manager[532]: (ttyUSB0) serial port closed May 12 13:00:01 ubuntu modem-manager[532]: (ttyUSB2) closing serial port… May 12 13:00:01 ubuntu modem-manager[532]: (ttyUSB2) serial port closed May 12 13:00:01 ubuntu NetworkManager[561]: (ttyUSB3): failed to look up interface index May 12 13:00:01 ubuntu NetworkManager[561]: b[/b]: new GSM/UMTS device (driver: ‘sierra’ ifindex: 0) May 12 13:00:01 ubuntu NetworkManager[561]: b[/b]: exported as /org/freedesktop/NetworkManager/Devices/3 May 12 13:00:01 ubuntu NetworkManager[561]: b[/b]: now managed May 12 13:00:01 ubuntu NetworkManager[561]: b[/b]: device state change: unmanaged → unavailable (reason ‘managed’) [10 20 2] May 12 13:00:01 ubuntu NetworkManager[561]: b[/b]: deactivating device (reason ‘managed’) [2] May 12 13:00:01 ubuntu NetworkManager[561]: nm\_system\_iface\_flush\_routes: assertion `ifindex > 0' failed May 12 13:00:01 ubuntu NetworkManager[561]: nm_system_iface_flush_addresses: assertion `ifindex \> 0’ failed May 12 13:00:01 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 13:00:01 ubuntu NetworkManager[561]: b[/b]: device state change: unavailable → disconnected (reason ‘none’) [20 30 0] May 12 13:00:01 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 13:02:17 ubuntu NetworkManager[561]: Activation b[/b] starting connection ‘Movistar’ May 12 13:02:17 ubuntu NetworkManager[561]: b[/b]: device state change: disconnected → prepare (reason ‘none’) [30 40 0] May 12 13:02:17 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 13:02:17 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 13:02:17 ubuntu NetworkManager[561]: Activation b[/b] Stage 1 of 5 (Device Prepare) scheduled… May 12 13:02:17 ubuntu NetworkManager[561]: Activation b[/b] Stage 1 of 5 (Device Prepare) started… May 12 13:02:17 ubuntu NetworkManager[561]: Activation b[/b] Stage 1 of 5 (Device Prepare) complete. May 12 13:02:17 ubuntu modem-manager[532]: b[/b] opening serial port… May 12 13:02:17 ubuntu modem-manager[532]: Modem /org/freedesktop/ModemManager/Modems/2: state changed (disabled → enabling) May 12 13:02:28 ubuntu modem-manager[532]: b[/b]: using text mode for SMS May 12 13:02:28 ubuntu modem-manager[532]: Modem /org/freedesktop/ModemManager/Modems/2: state changed (enabling → enabled) May 12 13:02:28 ubuntu NetworkManager[561]: WWAN now enabled by management service May 12 13:02:28 ubuntu modem-manager[532]: Modem /org/freedesktop/ModemManager/Modems/2: state changed (enabled → registered) May 12 13:02:28 ubuntu modem-manager[532]: Modem /org/freedesktop/ModemManager/Modems/2: state changed (registered → connecting) May 12 13:02:29 ubuntu modem-manager[532]: Modem /org/freedesktop/ModemManager/Modems/2: state changed (connecting → connected) May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 2 of 5 (Device Configure) scheduled… May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 2 of 5 (Device Configure) starting… May 12 13:02:29 ubuntu NetworkManager[561]: (ttyUSB3): device state change: prepare → config (reason ‘none’) [40 50 0] May 12 13:02:29 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 2 of 5 (Device Configure) successful. May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) scheduled. May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 2 of 5 (Device Configure) complete. May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) started… May 12 13:02:29 ubuntu NetworkManager[561]: (ttyUSB3): device state change: config → ip-config (reason ‘none’) [50 70 0] May 12 13:02:29 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 13:02:29 ubuntu NetworkManager[561]: starting PPP connection May 12 13:02:29 ubuntu NetworkManager[561]: pppd started with pid 1880 May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) scheduled… May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 3 of 5 (IP Configure Start) complete. May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) started… May 12 13:02:29 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 4 of 5 (IPv6 Configure Timeout) complete. May 12 13:02:29 ubuntu pppd[1880]: Plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so loaded. May 12 13:02:29 ubuntu pppd[1880]: pppd 2.4.5 started by root, uid 0 May 12 13:02:29 ubuntu pppd[1880]: Using interface ppp0 May 12 13:02:29 ubuntu NetworkManager[561]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0) May 12 13:02:29 ubuntu NetworkManager[561]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found. May 12 13:02:29 ubuntu pppd[1880]: Connect: ppp0 ↔ /dev/ttyUSB3 May 12 13:02:29 ubuntu pppd[1880]: CHAP authentication succeeded May 12 13:02:29 ubuntu pppd[1880]: CHAP authentication succeeded May 12 13:02:29 ubuntu kernel: [608.772962] PPP BSD Compression module registered May 12 13:02:29 ubuntu kernel: [608.784214] PPP Deflate Compression module registered May 12 13:02:32 ubuntu pppd[1880]: Could not determine remote IP address: defaulting to 10.64.64.64 May 12 13:02:32 ubuntu pppd[1880]: local IP address 10.60.1.168 May 12 13:02:32 ubuntu pppd[1880]: remote IP address 10.64.64.64 May 12 13:02:32 ubuntu pppd[1880]: primary DNS address 200.28.4.130 May 12 13:02:32 ubuntu pppd[1880]: secondary DNS address 200.28.4.129 May 12 13:02:32 ubuntu NetworkManager[561]: PPP manager(IP Config Get) reply received. May 12 13:02:32 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 5 of 5 (IPv4 Configure Commit) scheduled… May 12 13:02:32 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 5 of 5 (IPv4 Commit) started… May 12 13:02:33 ubuntu ntpd[1487]: Listen normally on 6 ppp0 10.60.1.168 UDP 123 May 12 13:02:33 ubuntu ntpd[1487]: peers refreshed May 12 13:02:33 ubuntu ntpd[1487]: new interface(s) found: waking up resolver May 12 13:02:33 ubuntu NetworkManager[561]: DNS: starting dnsmasq… May 12 13:02:33 ubuntu NetworkManager[561]: (ppp0): writing resolv.conf to /sbin/resolvconf May 12 13:02:33 ubuntu dnsmasq[1934]: started, version 2.59 cache disabled May 12 13:02:33 ubuntu dnsmasq[1934]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN May 12 13:02:33 ubuntu dnsmasq[1934]: using nameserver 200.28.4.129#53 May 12 13:02:33 ubuntu dnsmasq[1934]: using nameserver 200.28.4.130#53 May 12 13:02:33 ubuntu NetworkManager[561]: (ttyUSB3): device state change: ip-config → activated (reason ‘none’) [70 100 0] May 12 13:02:33 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 13:02:33 ubuntu NetworkManager[561]: Unmanaged Device found; state CONNECTED forced. (see [bugs.launchpad.net/bugs/191889](http://bugs.launchpad.net/bugs/191889)) May 12 13:02:33 ubuntu NetworkManager[561]: Policy set ‘Movistar’ (ppp0) as default for IPv4 routing and DNS. May 12 13:02:33 ubuntu NetworkManager[561]: Activation (ttyUSB3) successful, device activated. May 12 13:02:33 ubuntu dbus[516]: [system] Activating service name=‘org.freedesktop.nm\_dispatcher’ (using servicehelper) May 12 13:02:33 ubuntu NetworkManager[561]: Activation (ttyUSB3) Stage 5 of 5 (IPv4 Commit) complete. May 12 13:02:34 ubuntu dbus[516]: [system] Successfully activated service ‘org.freedesktop.nm\_dispatcher’ ## Now I try connect to /dev/ttyUSB3 but don’t work ☹ ## root@ubuntu:~# minicom --device /dev/ttyUSB3 Device /dev/ttyUSB3 is locked. root@ubuntu:~# The /dev/ttyUSB3 is locked when I condected with the network configuration ☹ . Do you know if exist other form for getting that information? (With the ttyUSB5/ttyUSB6 it’s same result ttyUSB4) * * * Welcome to minicom 2.5 OPTIONS: I18n Compiled on May 2 2011, 00:39:27. Port /dev/ttyUSB5 Press CTRL-A Z for help on special keys Sierra Wireless, Incorporated MC8795V APP2 ## OK Welcome to minicom 2.5 OPTIONS: I18n Compiled on May 2 2011, 00:39:27. Port /dev/ttyUSB6 Press CTRL-A Z for help on special keys Sierra Wireless, Incorporated MC8795V APP3 OK * * * Best Regards ---
**Author:** ![mlw](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/mlw/32/3706_2.png) [@mlw](https://forum.sierrawireless.com/u/mlw)\ **Post date:** [May 13, 2016, 7:09am UTC](https://forum.sierrawireless.com/t/problem-at-commands-in-linux/8564/4 "2016-05-13T07:09:39Z")
The problem you have here is that you are connecting the PPP session using /dev/ttyUSB3 (which has the full parser), you should do it using /dev/ttyUSB4, 5 or 6. Alternatively you could use DirectIP. On /dev/ttyUSB3 create the profile with the APN you want to use with the at+cgdcont command then send at!scact=1,1, this activates the network interface. Regards Matt ---
**Author:** ![aponce](https://avatars.discourse-cdn.com/v4/letter/a/ed8c4c/32.png) [@aponce](https://forum.sierrawireless.com/u/aponce)\ **Post date:** [May 19, 2016, 3:10pm UTC](https://forum.sierrawireless.com/t/problem-at-commands-in-linux/8564/5 "2016-05-19T15:10:11Z")
Thanks a lot Matt!!! I followed with your indications. \*\*\* For this I down the network-manager service to make changes with minicom on the modem. * * * Welcome to minicom 2.5 OPTIONS: I18n Compiled on May 2 2011, 00:39:27. Port /dev/ttyUSB3 Press CTRL-A Z for help on special keys AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0 OK ati Manufacturer: Sierra Wireless, Incorporated Model: MC8795V Revision: K2\_0\_7\_46CAP C:/WS/FW/K2\_0\_7\_46CAP/MSM6290/SRC 2010/12/13 22:29:01 IMEI: 355310038197434 IMEI SV: 25 FSN: CHJ2914048310 3GPP Release 6 +GCAP: +CGSM,+DS,+ES OK at+cgdcont? +CGDCONT: 1,“IP”,“bam.clarochile.cl”,“0.0.0.0”,0,0 +CGDCONT: 2,“IP”,“m2m.movistar.cl”,“0.0.0.0”,0,0 ## at!scact=1,1 In the modem when I send the command (at+cgdcont?) in the memory have 2 config, the first is the correct with the SIM in the modem. When send the command (at!scact=1,1) the screen is frozen and I can’t sent other command, also I tryed connect with other console for the next ttyUSB4 but had the same result that ttyUSB3 (frozen). * * * Welcome to minicom 2.5 OPTIONS: I18n Compiled on May 2 2011, 00:39:27. Port /dev/ttyUSB4 Press CTRL-A Z for help on special keys ati ati * * * After this change I can see: 1.- The light of the modem is on and not blinked. ## 2.- I dont have a new interface + ip (modem): root@ubuntu:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:01:c0:13:88:b5 inet addr:10.151.185.241 Bcast:10.151.185.255 Mask:255.255.255.0 inet6 addr: fe80::201:c0ff:fe13:88b5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1748716 errors:0 dropped:0 overruns:0 frame:0 TX packets:177946 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:247195062 (247.1 MB) TX bytes:40282535 (40.2 MB) Interrupt:40 Base address:0x2000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:881 errors:0 dropped:0 overruns:0 frame:0 TX packets:881 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:54594 (54.5 KB) TX bytes:54594 (54.5 KB) ## root@ubuntu:~# I see this page [http://mycusthelp.net/SIERRAWIRELESS/\_cs/AnswerDetail.aspx?aid=44](http://mycusthelp.net/SIERRAWIRELESS/_cs/AnswerDetail.aspx?aid=44) and add the command: 1. at+cfun=1 2. at!pcstate=1 * * * Welcome to minicom 2.5 OPTIONS: I18n Compiled on May 2 2011, 00:39:27. Port /dev/ttyUSB3 Press CTRL-A Z for help on special keys AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0 OK ati Manufacturer: Sierra Wireless, Incorporated Model: MC8795V Revision: K2\_0\_7\_46CAP C:/WS/FW/K2\_0\_7\_46CAP/MSM6290/SRC 2010/12/13 22:29:01 IMEI: 355310038197434 IMEI SV: 25 FSN: CHJ2914048310 3GPP Release 6 +GCAP: +CGSM,+DS,+ES OK at+cgdcont? +CGDCONT: 1,“IP”,“bam.clarochile.cl”,“0.0.0.0”,0,0 +CGDCONT: 2,“IP”,“m2m.movistar.cl”,“0.0.0.0”,0,0 ## OK at+cfun=1 OK at!pcstate=1 ERROR at!scact=1,1 But the result is the same, maybe this doing something wrong 😢 . Best Regards!