Question

Our TRB255 test unit is randomly losing it's mobile connection. Last time it was stable for 15-20 days before the connection was permanently lost. Restart of unit is fixing connectivity issue. Before the final loss of connectivity, there were some shorter breaks in connection. Log messages from when connection was permanently lost:

Sat Aug 15 15:53:57 2020 daemon.notice netifd: mob1s1a1 (7195): Mobile status MCC: 242, MNC: 1, PS: attached, traffic-channel-active

Sat Aug 15 15:59:10 2020 daemon.notice netifd: mob1s1a1 (7195): error: couldn't open the QmiDevice: Transaction timed out

Sat Aug 15 15:59:19 2020 daemon.notice netifd: mob1s1a1 (7195): Mobile connection lost!

Sat Aug 15 15:59:26 2020 daemon.notice netifd: Interface 'mob1s1a1' has lost the connection

Sat Aug 15 15:59:26 2020 daemon.notice netifd: Network device 'wwan0' link is down

Sat Aug 15 15:59:29 2020 daemon.notice netifd: mob1s1a1 (10945): Stopping network mob1s1a1

Sat Aug 15 15:59:31 2020 daemon.notice netifd: Interface 'mob1s1a1' is now down

Sat Aug 15 15:59:31 2020 daemon.notice netifd: Interface 'mob1s1a1' is setting up now

Sat Aug 15 15:59:36 2020 daemon.notice netifd: mob1s1a1 (11009): wwan[11009] Using proto:qmux device:/dev/cdc-wdm0 iface:wwan0 desc:Quectel BG96

Sat Aug 15 15:59:38 2020 daemon.info dnsmasq[2515]: read /etc/hosts - 5 addresses

Sat Aug 15 15:59:38 2020 daemon.info dnsmasq[2515]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses

Sat Aug 15 15:59:38 2020 daemon.info dnsmasq-dhcp[2515]: read /etc/ethers - 0 addresses

Sat Aug 15 15:59:40 2020 kern.emerg Mobile data disconnected

Sat Aug 15 15:59:42 2020 daemon.notice netifd: mob1s1a1 (11009): Quering active sim position

Sat Aug 15 15:59:42 2020 daemon.notice netifd: mob1s1a1 (11009): Calculated qmimux ifname: qmimux0

Sat Aug 15 16:00:00 2020 cron.info crond[14982]: USER root pid 11358 cmd /etc/init.d/rut_fota start

Sat Aug 15 16:00:10 2020 daemon.info dnsmasq[2515]: read /etc/hosts - 5 addresses

Sat Aug 15 16:00:10 2020 daemon.info dnsmasq[2515]: read /tmp/hosts/dhcp.cfg01411c - 2 addresses

Sat Aug 15 16:00:10 2020 daemon.info dnsmasq-dhcp[2515]: read /etc/ethers - 0 addresses

Sat Aug 15 16:00:16 2020 daemon.notice netifd: mob1s1a1 (11009): Informing driver of raw-ip for wwan0 ..

Sat Aug 15 16:00:57 2020 daemon.notice netifd: mob1s1a1 (11009): error: couldn't open the QmiDevice: Transaction timed out

Sat Aug 15 16:01:24 2020 daemon.notice netifd: mob1s1a1 (11009): [/dev/cdc-wdm0] Successfully set data format

Sat Aug 15 16:01:24 2020 daemon.notice netifd: mob1s1a1 (11009):                         QoS flow header: no

Sat Aug 15 16:01:24 2020 daemon.notice netifd: mob1s1a1 (11009):                     Link layer protocol: 'raw-ip'

Sat Aug 15 16:01:24 2020 daemon.notice netifd: mob1s1a1 (11009):        Uplink data aggregation protocol: 'qmap'

Sat Aug 15 16:01:24 2020 daemon.notice netifd: mob1s1a1 (11009):      Downlink data aggregation protocol: 'qmap'

Sat Aug 15 16:01:24 2020 daemon.notice netifd: mob1s1a1 (11009):                           NDP signature: '0'

Sat Aug 15 16:01:24 2020 daemon.notice netifd: mob1s1a1 (11009): Downlink data aggregation max datagrams: '8'

Sat Aug 15 16:01:24 2020 daemon.notice netifd: mob1s1a1 (11009):      Downlink data aggregation max size: '2048'

Sat Aug 15 16:01:26 2020 daemon.notice netifd: mob1s1a1 (11009): Starting network mob1s1a1 using APN:

Sat Aug 15 16:01:27 2020 daemon.notice netifd: mob1s1a1 (11009): Attempt to retrieve IMSI number...

Sat Aug 15 16:01:27 2020 daemon.notice netifd: mob1s1a1 (11009): Don't get option "apn" from config

Sat Aug 15 16:01:27 2020 daemon.notice netifd: mob1s1a1 (11009): Attempt to fetch APN list...

Sat Aug 15 16:01:27 2020 daemon.notice netifd: mob1s1a1 (11009): Getting APN list from database

Sat Aug 15 16:01:27 2020 daemon.notice netifd: mob1s1a1 (11009): APN Fetch is done Exiting..

Sat Aug 15 16:01:38 2020 daemon.notice netifd: mob1s1a1 (11009): Profile successfully modified.

Sat Aug 15 16:01:54 2020 daemon.notice netifd: mob1s1a1 (11009): cid4: 2

Sat Aug 15 16:02:31 2020 daemon.notice netifd: mob1s1a1 (11009): error: couldn't open the QmiDevice: Transaction timed out

Sat Aug 15 16:03:13 2020 daemon.info procd: Instance rms_mqtt::rms_mqtt pid 8408 not stopped on SIGTERM, sending SIGKILL instead

Sat Aug 15 16:03:19 2020 daemon.notice netifd: mob1s1a1 (11009): pdh4: 2201489936

Sat Aug 15 16:03:51 2020 daemon.notice netifd: mob1s1a1 (11009): error: operation failed: Transaction timed out

Sat Aug 15 16:03:55 2020 daemon.notice netifd: mob1s1a1 (11009): No IPV4 data link!

Sat Aug 15 16:04:17 2020 daemon.notice netifd: mob1s1a1 (11009): error: operation failed: Transaction timed out

Sat Aug 15 16:04:39 2020 daemon.notice netifd: mob1s1a1 (11009): error: couldn't release client: Transaction timed out

Some info:

FW version: TRB2_R_00.02.04.3

Mobile tech: Locked on 4G, Cat-M1

Auto APN

Main functions used:

RS485 Modbus master, MQTT/TLS data sender

RMS active

Wireguard VPN active

Any idea what I can do to fix this? Periodical reboot is not a fix!

BR,

Håvard

Comments

Hi

We have the same problem with two TRB255's that are just being sued on the ethernet port. We have been using the RUT240 so these are new devices for us as we need GPS location on this equipment. We ran both systems in our office for nearly a week without a problem, deployed them and had a failure at each site on the first day. The first unit we found no LTE connection (signal strength or 2g,3G etc) lights on. A power cycle brought it back to life but it failed again the next day. This time I did a power cycle and within 10 minutes it was dead again, so I fitted an RUT240 and it is still running a week later. We did extra testing of the second unit before it left our office on the basis that we had a faulty modem at the first site, but the second site also failed the afternoon of the first day at site. Both modems had the latest firmware (TRB2_R_00.02.06). We set the local controller to power cycle the modem if no comms for 3 hours, and that brought the second site back to life in the evening. Since the second site only went in last Thursday, we will be swapping to an RUT240 straight after Easter.

The modems are fitted to outdoor switchboards so I suspect the TRB255 is having heat issues, but luckily the RUT240 works fine. Still not a final solution as we need the GPS but at least the pump stations are working for now.

Any ideas / suggestions will be very welcome.

Thanks

David

Answer 1

Hi,

Could you send me the troubleshoot file via private message after the disconnection? Do not restart the router as it will lose its system log.

EB.