I have found a problem with microcom, i.e. microcom -E /dev/ttyAT, on some versions of Firmware for FX30 (I’m on my 3rd version try). I believe the problem is a bug in some versions of microcom and the work around for the buggy version is to simply leave out the -E, for example microcom /dev/ttyAT . so now we get no echo but our AT commands will be processed and we will get the response. As a point of reference my original Firmware version on the delivered card had the buggy microcom and a nonworking “cm data connect”. Then I upgraded to the latest firmware online, where microcom fully worked but cm data connect still did not. Then I got a firmware version from Sierra where “cm data connect” worked but my buggy microcom was back. However, I need a working connection more than I need Echo with microcom. So I will make do for now. My question:How best to get a working version of Microcom? Can I upgrade individually or is it part of the Firmware install and I need to find yet another version of Firmware where “everything” works?
I tried on WP76 module FW R13, I cannot use the -E option. Suggest you use ATE1 to enable echo.
root@swi-mdm9x28-wp:~# microcom /dev/ttyAT -E
microcom: option requires an argument – ‘E’
BusyBox v1.27.2 (2019-07-08 12:01:05 UTC) multi-call binary.
Usage: microcom [-d DELAY] [-t TIMEOUT] [-s SPEED] [-X] [-E] TTY
root@swi-mdm9x28-wp:~# microcom /dev/ttyAT
at
OK
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7609
Revision: SWI9X07Y_02.28.03.05 000000 jenkins 2019/07/08 11:04:16
IMEI: 359782080100340
IMEI SV: 6
FSN: WA803370010910
+GCAP: +CGSM
OK
ate0
OK
OK
OK
at
OK
ati3
Manufacturer: Sierra Wireless, Incorporated
Model: WP7609
Revision: SWI9X07Y_02.28.03.05 000000 jenkins 2019/07/08 11:04:16
IMEI: 359782080100340
IMEI SV: 6
FSN: WA803370010910
+GCAP: +CGSM
OK
Thank you! ate1 worked great for me.