Cellular connection problem on Moxa uc-8100, no signal

Hi,

I hope it’s ok to create new topic, there are a few similar topics but mostly with Raspberries…

So we bought Telit LE910C4-EU Mini PCIe LTE CAT4 from Sixfab. Other HW which we use:

  • Moxa uc-8112-LX
  • ANT-LTE-ASM-02

Our problem is that we cannot establish cellular connection. ‘AT+CSQ’ is returning 99,99 all the time. Connections should be OK, devices should be compatible (including frequency bands), we tried 2 SIM cards (both work in mobile phone), APN should be correct (checked on mobile phone).

It seems that modem is stuck either in mode 8 (factory-test) or 4 (low-power). Manually executing command <AT+CFUN=1> or AT+CFUN=1,1 (setting modem to full functionality) returns “error”. Not sure if mode is really changed because checking with different commands, we get different responses:

  • ‘AT+CFUN?’ returns +CFUN: 1
  • qmicli -d /dev/cdc-wdm0 --dms-get-operating-mode returns original mode (factory-test or low-power)

If you have any advice/ideas how can we resolve this issue would be great.

Here are some responses from AT commands:

root@Moxa: cat /etc/os-release
PRETTY_NAME=“Debian GNU/Linux 9 (stretch)”
NAME=“Debian GNU/Linux”
VERSION_ID=“9”
VERSION=“9 (stretch)”
VERSION_CODENAME=stretch
ID=debian

root@Moxa: uname -a
Linux Moxa 4.4.0-cip-rt-moxa-am335x #1 Mon Dec 5 16:19:55 CST 2022 armv7l GNU/Linux

root@Moxa: lsusb
Bus 002 Device 006: ID 110a:1151 Moxa Technologies Co., Ltd.
Bus 002 Device 005: ID 110a:1151 Moxa Technologies Co., Ltd.
Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 1bc7:1201 Telit Wireless Solutions
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

root@Moxa: dmesg | grep ttyUSB
[ 12.066792] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 12.256035] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 12.405498] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[ 12.535287] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
[ 12.649107] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
[ 13.835487] usb 2-1.2: MOXA UPort 1150I converter now attached to ttyUSB5
[ 14.665854] usb 2-1.3: MOXA UPort 1150I converter now attached to ttyUSB6

partial response of root@Moxa: usb-devices
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1bc7 ProdID=1201 Rev=03.18
S: Manufacturer=Android
S: Product=LE910C4-EU
S: SerialNumber=0123456789ABCDEF
C: #Ifs= 7 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)
I: If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan
I: If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I: If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I: If#= 5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I: If#= 6 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option

root@Moxa: qmicli -d /dev/cdc-wdm0 --dms-set-operating-mode=‘online’
error: couldn’t set operating mode: QMI protocol error (52): ‘DeviceNotReady’

root@Moxa: cell_mgmt at ‘AT+CFUN=1’
ERROR
root@Moxa:

root@Moxa: cell_mgmt at ‘AT+CPIN?’
+CPIN: READY
OK

root@Moxa: cell_mgmt at ‘AT+CSQ’
+CSQ: 99,99
OK

root@Moxa: cell_mgmt at ‘AT+CGMR’
M0F.670010
OK

root@Moxa: cell_mgmt at ‘AT+CPAS’
+CPAS: 0
OK

root@Moxa: cell_mgmt at ‘AT+COPS?’
+COPS: 0
OK

root@Moxa: cell_mgmt at ‘AT#USBCFG?’
#USBCFG: 0
OK

root@Moxa: cell_mgmt at ‘AT#BND?’
#BND: 0,15,80800C5
OK

root@Moxa: cell_mgmt at ‘AT+CREG?’
+CREG: 0,0 (sometimes is returned 0,4)
OK

root@Moxa: cell_mgmt at ‘AT+CGDCONT?’
+CGDCONT: 1,“IP”,“internet”,“”,0,0,0,0
+CGDCONT: 2,“IPV4V6”,“ims”,“”,0,0,0,0
+CGDCONT: 3,“IPV4V6”,“sos”,“”,0,0,0,1
OK

root@Moxa: cell_mgmt at ‘AT#SWPKGV’
25.21.670-P0F.671803
M0F.670010
P0F.671803
A0F.670010
OK

root@Moxa: cell_mgmt at ‘AT#TESTMODE?’
#TESTMODE: 0
OK

If others encounter similar issues, here is what we have discovered.

The problem lies with the modem; however, we are uncertain of the exact cause. Technical support from Telit mentioned that firmware is incompatible with our equipment (but based on the command AT#SWPKGV they have the same FW).

Anyway, we bought another modem and the new one is now functioning correctly.