Fixed Incident Count

Cellular Modules Telit ME910C1-WW LTE Module
1

On connect.sixfab.com console for my SIM I see the “Fixed Incident Count” increasing. It’s at 7 now. What is causing that count to increase?

2

Hi @sfeldma ,

An increasing value as we solve cellular connectivity issues.

3

The count is at 9 now. I’m seeing 1/2 second ping times on wwan0…my phone can ping sub 100ms from the same location. What’s going on?

Raspberry Pi Cellular IoT Kit

pi@rpcan2:~ $ sudo ip link set wlan0 down
pi@rpcan2:~ $ ping -c 5 -I wwan0 google.com
PING google.com (142.250.65.78) from 192.168.225.20 wwan0: 56(84) bytes of data.
64 bytes from 142.250.65.78: icmp_seq=1 ttl=109 time=303 ms
64 bytes from 142.250.65.78: icmp_seq=2 ttl=109 time=574 ms
64 bytes from 142.250.65.78: icmp_seq=3 ttl=109 time=275 ms
64 bytes from 142.250.65.78: icmp_seq=4 ttl=109 time=293 ms
64 bytes from 142.250.65.78: icmp_seq=5 ttl=109 time=771 ms

--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 330ms
rtt min/avg/max/mdev = 274.684/443.149/770.811/197.430 ms
pi@rpcan2:~ $ ping -c 5 -I wwan0 google.com
PING google.com (142.250.65.78) from 192.168.225.20 wwan0: 56(84) bytes of data.
64 bytes from 142.250.65.78: icmp_seq=1 ttl=109 time=626 ms
64 bytes from 142.250.65.78: icmp_seq=2 ttl=109 time=595 ms
64 bytes from 142.250.65.78: icmp_seq=3 ttl=109 time=452 ms
64 bytes from 142.250.65.78: icmp_seq=4 ttl=109 time=590 ms
64 bytes from 142.250.65.78: icmp_seq=5 ttl=109 time=430 ms

--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 651ms
rtt min/avg/max/mdev = 429.648/538.459/625.633/81.109 ms

With wlan0:

pi@rpcan2:~ $ sudo ip link set wlan0 up
pi@rpcan2:~ $ ping -c 5 -I wlan0 google.com
PING google.com (142.251.33.78) from 192.168.1.110 wlan0: 56(84) bytes of data.
64 bytes from sea09s28-in-f14.1e100.net (142.251.33.78): icmp_seq=1 ttl=121 time=30.2 ms
64 bytes from sea09s28-in-f14.1e100.net (142.251.33.78): icmp_seq=2 ttl=121 time=27.8 ms
64 bytes from sea09s28-in-f14.1e100.net (142.251.33.78): icmp_seq=3 ttl=121 time=26.8 ms
64 bytes from sea09s28-in-f14.1e100.net (142.251.33.78): icmp_seq=4 ttl=121 time=32.2 ms
64 bytes from sea09s28-in-f14.1e100.net (142.251.33.78): icmp_seq=5 ttl=121 time=30.0 ms

--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 9ms
rtt min/avg/max/mdev = 26.812/29.387/32.175/1.904 ms
4

Fixed Incident Count is now 13…wwan0 seems to be going down and then coming back up, and each time it seems “Fixed Incident Count” increases.

Console says I’m using T-Mobile GSM.

Ping times (when wwan0 is up) continue to be around 400ms, but occasionally I see 4 or 5 second ping times or pkt loss.

What latency and bandwidth should I expect to see over wwan0?

5

Update: I tried a fresh install of Raspberry PI OS and re-ran the sixfab installation code. The Fixed Incident Count when back to zero after the install, but then continued to increment over night. The count is up to 25 now and I’m seeing wwan0 drop off and then reappear a few minutes later, and each time the Fixed Incident Count increments.

Any suggestions on how to debug?

6

If you activate the remote support setting of your device and share the support key with me, I can quickly diagnose your problem.

7

I have the remote support key…how do I send it to you privately?

8

You can send it via email(ensar@sixfab.com) or as a message from the community.

9

Thanks.

Cellular disconnections may have occurred due to poor signal quality. ME910 has a slightly slower connection due to 2G/CAT-M1. Therefore, the latency is 300-500 ms. Other than that, I haven’t seen any problems with your device. Which antennas are you using?

Also, note that your module signal may be blocked in some enclosed indoor environments, so this issue can be easily fixed by moving to another location.

10

Thank you for looking into my connection. I’m using the Pulse Electronics antenna that came with the kit.