Telit LE910CX no connection/+CREG returns 0, 2 with Sixfab SIM

ECaricato · January 30, 2022, 12:01pm

Hey,

I currently have two devices, that are unable to connect to the internet via the LTE module. I have installed the device just like 3 others before (same procedure), but the latest two are unable to connect.

Here are some logs:

Output of /home/sixfab/.core/logs/cm-log is mainly filled with this:

2022-01-30 12:44:34,933 --> cm.py              ERROR    check_network() ->
+CREG: 0,2                       

OK

Output of /home/sixfab/.core/logs/agent-log:

2022-01-30 12:45:49,276 --> monitoring.py  DEBUG    Sending new monitoring data
2022-01-30 12:45:49,297 --> monitoring.py  DEBUG    Skipping system data, couldn't find any changes.
2022-01-30 12:45:49,303 --> monitoring.py  DEBUG    Skipping config data, couldn't find any changes.
2022-01-30 12:45:49,392 --> monitoring.py  DEBUG    Updated last monitoring data

Output of /var/log/daemon.log:

Jan 30 12:46:16 raspberrypi avahi-daemon[352]: Joining mDNS multicast group on interface wwan0.IPv6 with address fe80::65b8:a5cf:e7db:b66b.
Jan 30 12:46:16 raspberrypi avahi-daemon[352]: New relevant interface wwan0.IPv6 for mDNS.
Jan 30 12:46:16 raspberrypi avahi-daemon[352]: Registering new address record for fe80::65b8:a5cf:e7db:b66b on wwan0.*.
Jan 30 12:46:16 raspberrypi dhcpcd[730]: wwan0: carrier lost
Jan 30 12:46:16 raspberrypi dhcpcd[730]: wwan0: deleting address fe80::65b8:a5cf:e7db:b66b
Jan 30 12:46:16 raspberrypi avahi-daemon[352]: Withdrawing address record for fe80::65b8:a5cf:e7db:b66b on wwan0.
Jan 30 12:46:16 raspberrypi avahi-daemon[352]: Leaving mDNS multicast group on interface wwan0.IPv6 with address fe80::65b8:a5cf:e7db:b66b.
Jan 30 12:46:16 raspberrypi avahi-daemon[352]: Interface wwan0.IPv6 no longer relevant for mDNS.
Jan 30 12:46:20 raspberrypi dhcpcd[730]: wwan0: carrier acquired
Jan 30 12:46:20 raspberrypi dhcpcd[730]: wwan0: IAID 6a:5f:dd:34
Jan 30 12:46:20 raspberrypi dhcpcd[730]: wwan0: adding address fe80::65b8:a5cf:e7db:b66b
Jan 30 12:46:20 raspberrypi avahi-daemon[352]: Joining mDNS multicast group on interface wwan0.IPv6 with address fe80::65b8:a5cf:e7db:b66b.
Jan 30 12:46:20 raspberrypi avahi-daemon[352]: New relevant interface wwan0.IPv6 for mDNS.
Jan 30 12:46:20 raspberrypi avahi-daemon[352]: Registering new address record for fe80::65b8:a5cf:e7db:b66b on wwan0.*.
Jan 30 12:46:21 raspberrypi dhcpcd[730]: wwan0: soliciting an IPv6 router
Jan 30 12:46:21 raspberrypi dhcpcd[730]: wwan0: rebinding lease of 192.168.225.57
Jan 30 12:46:21 raspberrypi dhcpcd[730]: wwan0: probing address 192.168.225.57/24
Jan 30 12:46:26 raspberrypi dhcpcd[730]: wwan0: leased 192.168.225.57 for 43200 seconds
Jan 30 12:46:26 raspberrypi dhcpcd[730]: wwan0: adding route to 192.168.225.0/24
Jan 30 12:46:26 raspberrypi dhcpcd[730]: wwan0: adding default route via 192.168.225.1
Jan 30 12:46:26 raspberrypi avahi-daemon[352]: Joining mDNS multicast group on interface wwan0.IPv4 with address 192.168.225.57.
Jan 30 12:46:26 raspberrypi avahi-daemon[352]: New relevant interface wwan0.IPv4 for mDNS.
Jan 30 12:46:26 raspberrypi avahi-daemon[352]: Registering new address record for 192.168.225.57 on wwan0.IPv4.
Jan 30 12:46:34 raspberrypi dhcpcd[730]: wwan0: no IPv6 Routers available
Jan 30 12:46:36 raspberrypi dhcpcd[730]: eth0: pid 23522 deleted default route via 192.168.2.1
Jan 30 12:46:36 raspberrypi dhcpcd[730]: eth0: pid 23522 deleted route to 192.168.2.0/24
Jan 30 12:46:36 raspberrypi dhcpcd[730]: wwan0: pid 23524 deleted default route via 192.168.225.1
Jan 30 12:46:36 raspberrypi dhcpcd[730]: wwan0: pid 23524 deleted route to 192.168.225.0/24

Output of uname -sr:
Linux 5.10.63-v7+

Output of lsusb:

Bus 001 Device 022: ID 1bc7:1206 Telit Wireless Solutions
Bus 001 Device 005: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of lsusb -t:

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M
|__ Port 1: Dev 5, If 0, Class=Vendor Specific Class, Driver=lan78xx, 480M
|__ Port 2: Dev 22, If 0, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 2: Dev 22, If 1, Class=Vendor Specific Class, Driver=, 480M
|__ Port 2: Dev 22, If 2, Class=Communications, Driver=cdc_ether, 480M
|__ Port 2: Dev 22, If 3, Class=CDC Data, Driver=cdc_ether, 480M
|__ Port 2: Dev 22, If 4, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 2: Dev 22, If 5, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 2: Dev 22, If 6, Class=Vendor Specific Class, Driver=option, 480M
|__ Port 2: Dev 22, If 7, Class=Vendor Specific Class, Driver=option, 480M

Output of ls /dev/ttyUSB*:

/dev/ttyUSB0  /dev/ttyUSB1  /dev/ttyUSB2  /dev/ttyUSB3  /dev/ttyUSB4

Output of dmesg | grep tty:

[ 2399.528513] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 2399.596890] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 2399.597454] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[ 2399.597908] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[ 2399.598360] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
[ 2415.101428] usb 1-1.1.2: GSM modem (1-port) converter now attached to ttyUSB0
[ 2415.111710] usb 1-1.1.2: GSM modem (1-port) converter now attached to ttyUSB1
[ 2415.112268] usb 1-1.1.2: GSM modem (1-port) converter now attached to ttyUSB2
[ 2415.112763] usb 1-1.1.2: GSM modem (1-port) converter now attached to ttyUSB3
[ 2415.113294] usb 1-1.1.2: GSM modem (1-port) converter now attached to ttyUSB4

Output of sudo cat /sys/kernel/debug/usb/devices:

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=-264, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 5.10
S:  Manufacturer=Linux 5.10.63-v7+ dwc_otg_hcd
S:  Product=DWC OTG Controller
S:  SerialNumber=3f980000.usb
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms
T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 4
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=0424 ProdID=2514 Rev= b.b3
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  2mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=01 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms
I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms
T:  Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  3 Spd=480  MxCh= 3
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=0424 ProdID=2514 Rev= b.b3
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  2mA 
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=01 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms
I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms
T:  Bus=01 Lev=03 Prnt=03 Port=00 Cnt=01 Dev#=  5 Spd=480  MxCh= 0
D:  Ver= 2.10 Cls=ff(vend.) Sub=00 Prot=ff MxPS=64 #Cfgs=  1
P:  Vendor=0424 ProdID=7800 Rev= 3.00
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  2mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=lan78xx
E:  Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E:  Ad=83(I) Atr=03(Int.) MxPS=  16 Ivl=1ms

Sorry for the long post. I really don’t have any idea myself and hope that you could help me here.
Note: The other working devices have been installed a few weeks ago and thus do not have the newest agent and manager version. They still have these in versions 1.3.5 and 1.4.3.

Thanks in advance and best regards,
Emanuel

ensar · January 31, 2022, 7:49am

Hi Emanuel,

Thanks for the detailed logs.
Firstly, upgrade your device’s agent and manager version to the latest because it has an old version that may cause your connection to fail.
Second, make sure your SIM doesn’t have any monthly limits.

ECaricato · January 31, 2022, 8:26am

Hi ensar,

thanks for your answer. None of my SIMs have any monthly limit.
Also, the devices that work do have the older agent and manager version. Two devices I tried to create in the past days, fail to get any connection. These two devices have the most recent version of the agent and the manager.

Best regards,
Emanuel

ensar · January 31, 2022, 8:54am

Well, I still suggest upgrading to the latest version for all your devices.
Are the devices that cannot connect are online now? If not, connect it and wait for 5-10 min. for the service to fix it. If the devices are online, restart both services. If the problem persists, you can share the remote-support token of the devices with me for detailed control.

ECaricato · January 31, 2022, 10:19am

I will update the other devices as soon as possible.
One of the devices is online right now, via Ethernet. I have waited some time, but the service does not fix it, even after restart.
Can I share the remote-support token right here or would it be better via mail?

ensar · January 31, 2022, 10:24am

Yes, please share via mail: ensar@sixfab.com

ensar · January 31, 2022, 11:49am

Thanks for sharing. Cellular connection successfully established. Now available. The problem was because of the APN. It was set to “de1.super”. I manually set it to “super” and it’s connected. You can check it in the configurations tab. Also, ensure your power supply satisfies the power requirements for Raspberry Pi or HAT.

ECaricato · January 31, 2022, 12:00pm

Thank you very much!
I will check if this is the case on the other device too and update it if necessary.