Device and Firmware Information
Model: TRB246
Previous Firmware: TRB2M_R_00.07.13.1
Current Firmware: TRB2M_R_00.07.14 (upgraded on 2025-04-27 at 20:17:16)
Network Operator: 20820
Connection Type: LTE
Issue description
I’ve been experiencing connection problems with my TRB246 modem over a few weeks. The logs show frequent unexpected shutdowns, mobile data disconnections, and SIM card state errors while running firmware version TRB2M_R_00.07.13.1.
On April 27th, 2025, I upgraded to firmware TRB2M_R_00.07.14. Following the upgrade, there was a brief period of instability (about 4 minutes) with multiple reboots. After this initial period, overall stability has improved with:
-
Fewer unexpected shutdowns
-
More stable mobile data connections
-
No SIM card state change errors
However, the device still experiences:
-
Occasional unexpected shutdowns (e.g., on April 28th at 07:08:00, and multiple times on April 29th)
-
Brief mobile data disconnections (e.g., on April 29th at 19:58:24, reconnected at 19:59:05)
I’m seeking advice on:
-
Are there recommended settings to improve connection stability for this specific model and firmware?
-
Could there be hardware-related issues causing the persistent unexpected shutdowns even after the firmware upgrade?
-
Are there diagnostic tools or commands I should run to gather more detailed information about the connection failures?
Any assistance or guidance would be greatly appreciated. I can provide additional logs or information if needed.
Some instability with mobile connection on my side.
Rollabacked to R_00.07.13.1.
I have a TRB500.
Hi Gianluca, thank you.
I see on Teltonika website that:
TRB2M_R_00.07.14 | 2025.04.24
Note: This firmware version has been withdrawn due to a critical issue affecting the Data Limit, traffic monitoring functionalities.
I have upgraded my unit to this firmware.
I still have a very unstable connection and very frequent reboots.
What should I do? If I roll back I will lose all the configuration I seem to understand.
I managed to connect to the unit and download the troubleshoot folder and the events logs.
This morning the unit kept rebooting many times and connection was lost..
Can anyone help interpreting the logs and suggest a solution?
The device is in a remote location not easily accessible.
Bests,
This is an extract from a log of this morning:
| ID |
Date |
Source |
Event group |
Event type |
Event |
| 2215 |
2025-05-06 07:16:33 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2216 |
2025-05-06 07:16:33 |
Startup |
system |
notice |
Device startup completed |
| 2217 |
2025-05-06 07:16:37 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2218 |
2025-05-06 07:17:20 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2219 |
2025-05-06 07:17:21 |
Startup |
system |
notice |
Device startup completed |
| 2220 |
2025-05-06 07:17:24 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2221 |
2025-05-06 07:18:07 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2222 |
2025-05-06 07:18:07 |
Startup |
system |
notice |
Device startup completed |
| 2223 |
2025-05-06 07:18:11 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2224 |
2025-05-06 07:18:54 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2225 |
2025-05-06 07:18:54 |
Startup |
system |
notice |
Device startup completed |
| 2226 |
2025-05-06 07:18:58 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2227 |
2025-05-06 07:19:42 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2228 |
2025-05-06 07:19:42 |
Startup |
system |
notice |
Device startup completed |
| 2229 |
2025-05-06 07:19:47 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2230 |
2025-05-06 07:20:28 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2231 |
2025-05-06 07:20:28 |
Startup |
system |
notice |
Device startup completed |
| 2232 |
2025-05-06 07:20:32 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2233 |
2025-05-06 07:21:16 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2234 |
2025-05-06 07:21:16 |
Startup |
system |
notice |
Device startup completed |
| 2235 |
2025-05-06 07:21:20 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2236 |
2025-05-06 07:22:03 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2237 |
2025-05-06 07:22:03 |
Startup |
system |
notice |
Device startup completed |
| 2238 |
2025-05-06 07:22:07 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2239 |
2025-05-06 07:22:50 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2240 |
2025-05-06 07:22:50 |
Startup |
system |
notice |
Device startup completed |
| 2241 |
2025-05-06 07:22:54 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2242 |
2025-05-06 07:23:36 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2243 |
2025-05-06 07:23:36 |
Startup |
system |
notice |
Device startup completed |
| 2244 |
2025-05-06 07:23:40 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2245 |
2025-05-06 07:24:24 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2246 |
2025-05-06 07:24:24 |
Startup |
system |
notice |
Device startup completed |
| 2247 |
2025-05-06 07:24:28 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2248 |
2025-05-06 07:25:12 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2249 |
2025-05-06 07:25:12 |
Startup |
system |
notice |
Device startup completed |
| 2250 |
2025-05-06 07:25:15 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2251 |
2025-05-06 07:25:59 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2252 |
2025-05-06 07:25:59 |
Startup |
system |
notice |
Device startup completed |
| 2253 |
2025-05-06 07:26:02 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2254 |
2025-05-06 07:26:45 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2255 |
2025-05-06 07:26:45 |
Startup |
system |
notice |
Device startup completed |
| 2256 |
2025-05-06 07:26:49 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2257 |
2025-05-06 07:27:06 |
Switch Events |
network |
notice |
Port link state of port LAN1 (100 baseT) changed to UP |
| 2258 |
2025-05-06 07:27:33 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2259 |
2025-05-06 07:27:33 |
Startup |
system |
notice |
Device startup completed |
| 2260 |
2025-05-06 07:27:36 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2261 |
2025-05-06 07:27:53 |
Switch Events |
network |
notice |
Port link state of port LAN1 (100 baseT) changed to UP |
| 2262 |
2025-05-06 07:28:20 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2263 |
2025-05-06 07:28:20 |
Startup |
system |
notice |
Device startup completed |
| 2264 |
2025-05-06 07:28:23 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2265 |
2025-05-06 07:28:40 |
Switch Events |
network |
notice |
Port link state of port LAN1 (100 baseT) changed to UP |
| 2266 |
2025-05-06 07:29:08 |
Startup |
system |
info |
Device startup after unexpected shutdown |
| 2267 |
2025-05-06 07:29:08 |
Startup |
system |
notice |
Device startup completed |
| 2268 |
2025-05-06 07:29:11 |
Switch Events |
network |
notice |
Port link state of port CPU/WiFi (1000 baseT) changed to UP |
| 2269 |
2025-05-06 07:29:28 |
Switch Events |
network |
notice |
Port link state of port LAN1 (100 baseT) changed to UP |
| 2270 |
2025-05-06 08:29:48 |
DHCP |
network |
info |
Leased 192.168.1.141 IP address for client 00:d0:2c:08:3a:8b - 14987 in LAN |
| 2271 |
2025-05-06 08:34:15 |
DHCP |
network |
info |
Leased 192.168.1.141 IP address for client 00:d0:2c:08:3a:8b - 14987 in LAN |
| 2272 |
2025-05-06 08:34:46 |
Mobile Data |
network |
info |
Mobile data connected (internal modem) |
| 2273 |
2025-05-06 08:34:46 |
Network Type |
network |
info |
Joined LTE network (internal modem) |
| 2274 |
2025-05-06 08:34:46 |
Network Operator |
network |
info |
Connected to 20820 operator (internal modem) |
| 2275 |
2025-05-06 16:21:13 |
Web UI |
connections |
notice |
User admin successfully authenticated on HTTP from 127.0.0.1 to 127.0.0.1 |
It has now been like that for days… It keeps rebooting..
Hello @AlbyDallo,
To better assist you, I’d like to kindly ask the following:
- Have you had a chance to install the latest 7.14.2 firmware version? If feasible, preferably without selecting “Keep Settings” (if not possible, then following the instructions provided here).
- Could you confirm when these issues first started occurring? From the description, I assume they weren’t present on older firmware versions before 7.13.1?
- Could you confirm whether Ping Reboot is not enabled under System → Maintenance → Auto Reboot?
- What type of power supply are you currently using with the device? If possible, I’d recommend testing with a different unit, ideally a 12W PSU, to see if it improves the situation.
Please let me know how it goes after checking the points above. If the issue continues to occur regularly, I’ll be happy to reach out to you privately to gather more details and assist further.
Best regards,
Hi,
- the device is currently using TRB2M_R_00.07.14.2. It was not possible to do it without the Keep Settings option, so I did use the instructions described in the TRB246 Firmware webpage:
-
The issues were not present before upgrading to firmware TRB2M_R_00.07.14.
-
Ping reboot was activated some weeks ago, but the logs config that this is not the issue. The modem is experiencing repeated “Unexpected reboots” more than once per day.
-
We are using a standard 12V DC power supply.
The unit is deployed at sea and cannot be easily reached.
I would greatly appreciate if you could revise the troubleshoot and event logs that I recently downloaded.
The behaviour has not improved in the past month..
Best regards,
Alberto
Thank you for the update. As mentioned, to assist you effectively, we’ll need to continue this process privately. You should find a support request form in the inbox of the email address you used for your forum registration. Kindly fill out the form, and please reference Ticket ID: 13551 when submitting it. Once the form is completed, we’ll contact you directly via email to investigate the issue in detail and help work towards a solution.
Best regards,
