# EM7430 send AT command no response **URL:** \ **Category:** MC/EM Series\ **Created:** [September 5, 2016, 10:11am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772 "2016-09-05T10:11:36Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![ason0821](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@ason0821](https://forum.sierrawireless.com/u/ason0821)\ **Post date:** [September 5, 2016, 10:11am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/1 "2016-09-05T10:11:36Z")
Hello, My EM7430 LTE module has some troubles. I modified qcserial.c and qmi\_wwam.c in kernel driver, and embedded board got 3 ttyUSB & “cdc-wam” interfaces. Below is information: > [@](#): > > root@OpenWrt:/# lsusb -t > /: Bus 03.Port 1: Dev 1, Class=root\_hub, Driver=xhci\_hcd/4p, 5000M > /: Bus 02.Port 1: Dev 1, Class=root\_hub, Driver=xhci\_hcd/4p, 480M > |\_\_ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=qcserial, 480M > |\_\_ Port 1: Dev 2, If 2, Class=Vendor Specific Class, Driver=qcserial, 480M > |\_\_ Port 1: Dev 2, If 3, Class=Vendor Specific Class, Driver=qcserial, 480M > |\_\_ Port 1: Dev 2, If 8, Class=Vendor Specific Class, Driver=qmi\_wwan, 480M > |\_\_ Port 1: Dev 2, If 10, Class=Vendor Specific Class, Driver=qmi\_wwan, 480M > |\_\_ Port 3: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M > /: Bus 01.Port 1: Dev 1, Class=root\_hub, Driver=ehci-pci/2p, 480M I tried to send AT command to ttyUSB0-2, but they had not any responses. for example: > [@](#): > > root@OpenWrt:/# cat /dev/ttyUSB2 & > root@OpenWrt:/# cat /dev/ttyUSB1 & > root@OpenWrt:/# cat /dev/ttyUSB0 & > root@OpenWrt:/# echo -e “ATI” \> /dev/ttyUSB2 > root@OpenWrt:/# echo -e “ATI” \> /dev/ttyUSB1 > root@OpenWrt:/# echo -e “ATI” \> /dev/ttyUSB0 Please help me to solve it, or give me some information. Thank you very much. Best Regards, Allen ---
**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:** [September 6, 2016, 6:21am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/2 "2016-09-06T06:21:23Z")
Allen, Please do not use the QC default drivers supplied with the kernel we have seen horrendous problems with them. You need to use our GobiSerial and GobiNet drivers on the source at the link below. [http://source.sierrawireless.com/~/media/support\_downloads/airprime/software/sierralinuxqmidriverss2.25n2.36.tar.ashx](http://source.sierrawireless.com/~/media/support_downloads/airprime/software/sierralinuxqmidriverss2.25n2.36.tar.ashx) After you build them into the system make sure it is actually using them, Linux really likes the QC drivers and you may have to manually delete the .ko files to force it to use the Gobi files. Regards Matt ---
**Author:** ![ason0821](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@ason0821](https://forum.sierrawireless.com/u/ason0821)\ **Post date:** [September 6, 2016, 8:59am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/3 "2016-09-06T08:59:16Z")
Hi mlw, Thank you for your reply. Actually I also porting the GobiSerial driver without GobiNet, and EM7430 had the same situation. Totay I porting GobiSerial and GobiNet again, but GobiNet has error. > [@](#): > > [262.898504] usbcore: registered new interface driver GobiSerial > [262.904468] usbserial: USB Serial support registered for GobiSerial > [262.912084] GobiSerial 2-1:1.0: GobiSerial converter detected > [262.917978] usb 2-1: GobiSerial converter now attached to ttyUSB0 > [262.925745] GobiSerial 2-1:1.2: GobiSerial converter detected > [262.931642] usb 2-1: GobiSerial converter now attached to ttyUSB1 > [262.939754] GobiSerial 2-1:1.3: GobiSerial converter detected > [262.945632] usb 2-1: GobiSerial converter now attached to ttyUSB2 > [262.951784] GobiSerial: 2015-08-27/SWI\_2.25:GobiSerial > [276.984064] GobiNet: 2015-12-08/SWI\_2.36 > [276.989876] GobiNet 2-1:1.8 eth5: register ‘GobiNet’ at usb-0000:00:10.0-1, GobiNet Ethernet Device, c2:07:26:20:50:d6 > [277.000608] Ethernet mode > [278.407623] TE Disabled > [278.410079] GobiNet 2-1:1.8 eth5: unregister ‘GobiNet’ usb-0000:00:10.0-1, GobiNet Ethernet Device > [278.435395] GobiNet: probe of 2-1:1.8 failed with error -14 > [278.443008] GobiNet 2-1:1.10 eth5: register ‘GobiNet’ at usb-0000:00:10.0-1, GobiNet Ethernet Device, c2:07:26:20:50:d6 > [278.453877] Ethernet mode > [289.715632] TE Disabled > [289.718118] GobiNet 2-1:1.10 eth5: unregister ‘GobiNet’ usb-0000:00:10.0-1, GobiNet Ethernet Device > [289.742160] GobiNet: probe of 2-1:1.10 failed with error -14 > [289.747914] usbcore: registered new interface driver GobiNet And AT command still no any responses. Could you give me more information? Thank you very much. Best Regards, Allen ---
**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:** [September 6, 2016, 9:13am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/4 "2016-09-06T09:13:40Z")
Allen, So you are using minicom to connect to /dev/ttyUSB2 and there is no response from it? Regards Matt ---
**Author:** ![ason0821](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@ason0821](https://forum.sierrawireless.com/u/ason0821)\ **Post date:** [September 6, 2016, 9:38am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/5 "2016-09-06T09:38:02Z")
Hi Matt, I only use “cat” command to monitor /dev/ttyUSB2. Because I use AC341U USB dongle, and it has receive responses. So I need to use minicom replace “cat” command? If yes, I will build minicom to test it. > [@](#): > > root@OpenWrt:/# cat /dev/ttyUSB2 & > root@OpenWrt:/# echo -e “ATI” \> /dev/ttyUSB2 > RAWIP mode: > [2247.555662] GobiNet: 2015-12-08/SWI\_2.36 > [2247.561672] GobiNet 2-1:1.8 eth5: register ‘GobiNet’ at usb-0000:00:10.0-1, GobiNet Ethernet Device, c2:07:26:20:50:d6 > [2247.572394] RawIP mode > [2248.988648] TE Disabled > [2248.991139] GobiNet 2-1:1.8 eth5: unregister ‘GobiNet’ usb-0000:00:10.0-1, GobiNet Ethernet Device > [2249.011440] GobiNet: probe of 2-1:1.8 failed with error -14 > [2249.019058] GobiNet 2-1:1.10 eth5: register ‘GobiNet’ at usb-0000:00:10.0-1, GobiNet Ethernet Device, c2:07:26:20:50:d6 > [2249.029868] RawIP mode > > [2266.094608] GobiNet 2-1:1.10 eth5: unregister ‘GobiNet’ usb-0000:00:10.0-1, GobiNet Ethernet Device > [2266.119634] GobiNet: probe of 2-1:1.10 failed with error -4 > [2266.125285] usbcore: registered new interface driver GobiNet Thank you very much. Best Regards, Allen ---
**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:** [September 6, 2016, 10:12am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/6 "2016-09-06T10:12:20Z")
Allen, I would suggest using minicom as it is the most reliable tool to work with the AT commands and will mean you are using a known good method. Regards Matt ---
**Author:** ![dl5162](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/dl5162/32/2169_2.png) [@dl5162](https://forum.sierrawireless.com/u/dl5162)\ **Post date:** [September 6, 2016, 10:39am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/7 "2016-09-06T10:39:15Z")
> [@mlw](#): > > Please do not use the QC default drivers supplied with the kernel we have seen horrendous problems with them. This is nnews to me. Could you please provide enough details to get whatever problem you see fixed? ---
**Author:** ![dl5162](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/dl5162/32/2169_2.png) [@dl5162](https://forum.sierrawireless.com/u/dl5162)\ **Post date:** [September 6, 2016, 10:47am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/8 "2016-09-06T10:47:32Z")
> [@ason0821](#): > > And AT command still no any responses. I have seen this symptom on the MC7455 and EM7455 a few times without yet being able to pinpoint the actual problem. What I have found is that a “usb device reset” (not a modem reset - that does not help) “fixes” the problem. At least it has for me. No guarantees, but worth trying. The easiest way to do a usb reset on linux is by using the “usbreset” utility, which is now part of the usbutils collection. Get it from your favourite distro, or see here: [github.com/gregkh/usbutils/blob … usbreset.c](https://github.com/gregkh/usbutils/blob/master/usbreset.c) ---
**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:** [September 6, 2016, 10:52am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/9 "2016-09-06T10:52:30Z")
We have not ‘fixed’ anything we have just written our own new drivers, I know some engineers internally who ae pretty scathing about the QC open source drivers particularily the qmi\_wwan ones. Regards Matt ---
**Author:** ![dl5162](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/dl5162/32/2169_2.png) [@dl5162](https://forum.sierrawireless.com/u/dl5162)\ **Post date:** [September 6, 2016, 12:49pm UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/10 "2016-09-06T12:49:52Z")
> [@mlw](#): > > We have not ‘fixed’ anything we have just written our own new drivers, I know some engineers internally who ae pretty scathing about the QC open source drivers particularily the qmi\_wwan ones. I am sure you are right. But I still wish they would share those problems so that the problems could be fixed. Using GobNet and GobiSerial is definitely correct for anyone who wants to develop a Sierra supported solution. Or for anyone having problems with the qcserial/qmi\_wwan drivers. Or simply to eliminate drivers as a source of any observed problem. But even if one set of working drivers is enough, it would still be nice to have any known issues with the qcserial/qmi\_wwan drivers fixed as well. Don’t you think so? Frankly, I do not see why you cannot qualify these problems if you “know” about them. There never is much point in referring to problems you are unable to describe. It just looks like FUD. At least to me. Sorry. ---
**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:** [September 6, 2016, 1:59pm UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/11 "2016-09-06T13:59:31Z")
We don’t ‘know’ about them, we have seen them and pushed customers to use software we know works and we are able to support. It is not our place to support open source software, particularly software that is used in direct competition to the hardware that we sell. As I am sure you know, every system is different and as such something that affect one system will have no effect on another (I ran with qcserial for a couple of years without realising it until I plugged a unit with a specific combination of firmware in and it all went wrong). I am sorry if you do not like this approach but we do have a business to run. Regards Matt ---
**Author:** ![dl5162](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/dl5162/32/2169_2.png) [@dl5162](https://forum.sierrawireless.com/u/dl5162)\ **Post date:** [September 6, 2016, 8:12pm UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/12 "2016-09-06T20:12:05Z")
> [@mlw](#): > > We don’t ‘know’ about them, we have seen them and pushed customers to use software we know works and we are able to support. It is not our place to support open source software, Fully understood, and agreed. But I take any reports of problems seriously. If you have a problem and want it fixed, then please give details. If you have a problem and don’t want it fixed, tben please don’t tell me that you have a problem in the first place 😉 > [@](#): > > particularly software that is used in direct competition to the hardware that we sell. This makes me very sorry to hear. And I sincerely believe you are wrong. The Sierre Wireless QMI SDK is a unique product which in no way can be replaced by any community developed and unsupported software. There just is no competition there. On the contrary: Those “products” complete each other by making Sierra Wireless modems available to a larger set of end users. > [@](#): > > As I am sure you know, every system is different and as such something that affect one system will have no effect on another (I ran with qcserial for a couple of years without realising it until I plugged a unit with a specific combination of firmware in and it all went wrong). Yes, I know. Which is why I wanted to know more details. We can only improve if we know about the specific cases where it goes wrong. ---
**Author:** ![fs1](https://avatars.discourse-cdn.com/v4/letter/f/439d5e/32.png) [@fs1](https://forum.sierrawireless.com/u/fs1)\ **Post date:** [September 6, 2016, 10:13pm UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/13 "2016-09-06T22:13:21Z")
> [@mlw](#): > > It is not our place to support open source software, particularly software that is used in direct competition to the hardware that we sell. GobiSerial is open source too. Of course you do not need to support qcserial, but if you happen to find problems, then you can report them and they will be fixed. This is not “supporting”. Also you hopefully have an endeavour that the devices you sell are working correctly. And since qcserial is in the kernel (as opposed to GobiSerial) you have a direct advantage if the devices are working with this driver. The modems you sell are in various Laptops and dongles, people who are using them are most likely not to use GobiNet and GobiSerial for their standard usecase of “Internet access”. For OP: I am using screen for accessing the serial ports. You need to make sure that only one program is accessing the serial port at the same time. ---
**Author:** ![ason0821](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@ason0821](https://forum.sierrawireless.com/u/ason0821)\ **Post date:** [September 7, 2016, 5:32am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/14 "2016-09-07T05:32:36Z")
Hi Matt, I use minicom to connect EM7430, and it still no response. What is step I lose? Thank you. > [@](#): > > Welcome to minicom 2.7 > > OPTIONS: > Compiled on Sep 7 2016, 10:35:22. > Port /dev/ttyUSB2, 05:44:47 > > Press CTRL-A Z for help on special keys > > ATI > AT+GMR > > CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.7 | VT102 | Offline | ttyUSB2 Best Regards, Allen ---
**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:** [September 7, 2016, 6:05am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/15 "2016-09-07T06:05:11Z")
Allen, Can you send the following to a terminal with the unit plugged in uname -r lsusb ls /dev lsmod Regards Matt ---
**Author:** ![ason0821](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@ason0821](https://forum.sierrawireless.com/u/ason0821)\ **Post date:** [September 7, 2016, 6:17am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/16 "2016-09-07T06:17:59Z")
Hi Matt, FYI > [@](#): > > root@OpenWrt:/# uname -r > 3.16.7 > root@OpenWrt:/# lsusb > lsmodBus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 002 Device 002: ID 1199:9071 Sierra Wireless, Inc. > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > root@OpenWrt:/# ls /dev > bsg ptp4 tty25 ttyS0 > bus pts tty26 ttyS1 > console ram0 tty27 ttyS10 > cpu ram1 tty28 ttyS11 > cpu\_dma\_latency ram10 tty29 ttyS12 > ecryptfs ram11 tty3 ttyS13 > full ram12 tty30 ttyS14 > fuse ram13 tty31 ttyS15 > hpet ram14 tty32 ttyS16 > hwrng ram15 tty33 ttyS17 > i2c-0 ram2 tty34 ttyS18 > i2c-1 ram3 tty35 ttyS19 > i2c-2 ram4 tty36 ttyS2 > i2c-3 ram5 tty37 ttyS20 > i2c-4 ram6 tty38 ttyS21 > i2c-5 ram7 tty39 ttyS22 > i2c-6 ram8 tty4 ttyS23 > i2c-7 ram9 tty40 ttyS24 > input random tty41 ttyS25 > kmsg rfkill tty42 ttyS26 > log rtc0 tty43 ttyS27 > loop-control sda tty44 ttyS28 > loop0 sda1 tty45 ttyS29 > loop1 sg0 tty46 ttyS3 > loop2 shm tty47 ttyS30 > loop3 snapshot tty48 ttyS31 > loop4 tpm0 tty49 ttyS4 > loop5 tty tty5 ttyS5 > loop6 tty0 tty50 ttyS6 > loop7 tty1 tty51 ttyS7 > mapper tty10 tty52 ttyS8 > mcelog tty11 tty53 ttyS9 > mem tty12 tty54 ttyUSB0 > net tty13 tty55 ttyUSB1 > network\_latency tty14 tty56 ttyUSB2 > network\_throughput tty15 tty57 ttyprintk > null tty16 tty58 uinput > nvram tty17 tty59 urandom > port tty18 tty6 vcs > ppp tty19 tty60 vcs1 > psaux tty2 tty61 vcsa > ptmx tty20 tty62 vcsa1 > ptp0 tty21 tty63 vga\_arbiter > ptp1 tty22 tty7 vmci > ptp2 tty23 tty8 vsock > ptp3 tty24 tty9 zero > root@OpenWrt:/# lsmod > GobiNet 61578 0 > GobiSerial 12949 0 > crc\_ccitt 12347 1 ppp\_async > e1000 96650 0 > e1000e 155009 0 > exfat 109875 0 > i2c\_algo\_bit 12402 1 igb > igb 137425 0 > ip6\_tables 16625 3 ip6table\_raw > ip6t\_REJECT 12352 0 > ip6table\_filter 12352 0 > ip6table\_mangle 12352 0 > ip6table\_raw 12352 0 > ip\_tables 16621 3 iptable\_raw > ipt\_MASQUERADE 12352 0 > ipt\_REJECT 12352 0 > iptable\_filter 12352 0 > iptable\_mangle 12352 0 > iptable\_raw 12352 0 > minix 33946 0 > msdos 16448 0 > msr 12352 0 > nf\_conntrack 53835 10 nf\_nat\_ipv4 > nf\_conntrack\_ftp 12352 1 nf\_nat\_ftp > nf\_conntrack\_ipv4 12352 1 > nf\_conntrack\_ipv6 12352 0 > nf\_defrag\_ipv4 12398 1 nf\_conntrack\_ipv4 > nf\_defrag\_ipv6 28959 1 nf\_conntrack\_ipv6 > nf\_nat 17195 4 nf\_nat\_ipv4 > nf\_nat\_ftp 12352 0 > nf\_nat\_ipv4 12406 0 > nls\_iso8859\_1 12352 1 > nls\_utf8 12352 0 > ppp\_async 16448 0 > pppoe 16448 0 > pppox 12522 1 pppoe > pps\_core 12601 1 ptp > ptp 16911 2 e1000e > r8169 57408 0 > reiserfs 207382 0 > x\_tables 17541 24 ipt\_MASQUERADE > xt\_CT 12352 0 > xt\_LOG 16448 0 > xt\_REDIRECT 12352 0 > xt\_TCPMSS 12352 0 > xt\_comment 8256 0 > xt\_conntrack 12352 0 > xt\_limit 12352 0 > xt\_mac 8256 0 > xt\_mark 8256 0 > xt\_multiport 8256 0 > xt\_state 12352 0 > xt\_tcpudp 8256 0 > xt\_time 12352 0 Thanks you. Best Regards, Allen ---
**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:** [September 7, 2016, 11:42am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/17 "2016-09-07T11:42:07Z")
Allen, Ok so you are using Open WRT and not pure Linux then? The drivers are intended specifically for Linux and while they are close as OS’s they aren’t exactly the same, I do not know why you are unable to send the AT commands. I know there are people who have got it working but I do not know how. Regards Matt ---
**Author:** ![ason0821](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@ason0821](https://forum.sierrawireless.com/u/ason0821)\ **Post date:** [September 8, 2016, 1:12am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/18 "2016-09-08T01:12:18Z")
Hi Matt, Thanks for your help. I have some questions about: 1.If EM7430 is not have firmware, it might probe successfully? Because I am not sure that EM7430 has firmware or not. 2.I found electronic SPEC in datasheet, and hardware issue might cause ttyUSB abnormally? Attachment is GobiNet debug log. Thank you very much. Best Regards, Allen [GobiNet fail.txt](https://forum.sierrawireless.com/uploads/short-url/wxS4Jp3EGwfFW4mh29FDOOQn5Yq.txt) (15.9 KB) ---
**Author:** ![fs1](https://avatars.discourse-cdn.com/v4/letter/f/439d5e/32.png) [@fs1](https://forum.sierrawireless.com/u/fs1)\ **Post date:** [September 8, 2016, 12:07pm UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/19 "2016-09-08T12:07:31Z")
You could also try typing aten then enter, then ati into minicom (or screen) Although I think that qcserial is not the problem: You could try using GobiSerial for the serial ports. ---
**Author:** ![ason0821](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@ason0821](https://forum.sierrawireless.com/u/ason0821)\ **Post date:** [September 12, 2016, 1:24am UTC](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772/20 "2016-09-12T01:24:12Z")
Hi fs1, Thanks for your reply. I try your recommendation, but it still no any responses. Maybe it has hardware issue with my board, I will debug it. Thank you. Best Regards, Allen [Next page](https://forum.sierrawireless.com/t/em7430-send-at-command-no-response/8772.md?page=2)