10948 questions

13055 answers

20358 comments

27907 members

0 votes
468 views 5 comments
by

Hi,

I have many TRB141 and TRB145 with firmware 00.01.05 which are not exactly lije specifications.

I saw that it'a practice for Teltonika, I have also TRB245 and TRB255 in which GNSS doesn't work.

For now I tried to update firmware on TRB 145 and TRB 141 with the new one appeared on site TRB14X_R_00.02.03.2

I receive the message The uploaded image file does not contain a supported format.

Can you explain what's the problem?
My patience is coming to an end! A lot of problems with Teltonika devices and I am loosing money.
Best regards,
Gabriel

by

Hi,

We also have several issues with similar families of firmware.

Incredibly frustrating.

Issues/Bugs:

TRB145: Firmware (Latest version)  
1) In RS485 Client mode the modem continually drops its connection and reconnects every "timeout interval". It should stay connected as it used to (previous firmwares for TRB145 and other devices like the TRB255 are successful at this).

TRB255: Firmware (TRB2_R_00.02.03.1)
1) In Modbus TCP Slave mode, many of the dynamic registers cannot be read.
https://wiki.teltonika-networks.com/view/TRB255_Monitoring_via_Modbus#Set_Parameters
Basic value registers such as "System Host Name" and "System Uptime" can be read, but the "Modem ID" and most importantly the "IMSI" cannot be read. We need to be able read the IMSI out of the device to identify it. Only about half of the advertised registers are able to be read successfully.

2) In the WebUI, none of the network parameters are filled out - eg, the screen does not show the network that it is connected to, the uptime, the IP address, the IMSI etc.  (Screenshot attached)

3) It does not seem to be possible to send AT commands via the CLI (eg. gsmctl -A AT+CIMI should retrieve the IMSI from a BG96 but the CLI says that it cannot understand the command)

4) In the CLI, several (most) of the gsmctl commands are either "not understood" by the interpreter "timeout",  or take a very long time to respond (eg. try to get the imsi with gsmctl -x). This still occurs when we put it into debug mode.At this stage it may take >30 seconds for some of these commands to respond, if they respond at all. For the IMSI command, I have only had 1 successful response from this command as 99% of the time it fails. The device has definitely read the IMSI by this time as it is connected to the internet and successfully transmits data over our IPSec tunnel. I have pasted findings from this in blue below:
  
eg.
root@Teltonika-TRB255:~# gsmctl -v                                                                                  
GSMCTL version: 0.2b                
root@Teltonika-TRB255:~# gsmctl -k                                                                                  
root@Teltonika-TRB255:~# gsmctl --at AT+CIMI <-- Dead

root@Teltonika-TRB255:~# gsmctl -x <-- Dead

root@Teltonika-TRB255:~# gsmctl -i   <-- Dead
Failed to invoke a gsmd object method                                                                                
GSMCTL error: reading message                                                                                        
N/A  
root@Teltonika-TRB255:~# gsmctl -c <-- Dead

root@Teltonika-TRB255:~# gsmctl -v                                                                                  
GSMCTL version: 0.2b                                                                                                
root@Teltonika-TRB255:~# gsmctl -j                                                                                  
Connected                                                                                                            
root@Teltonika-TRB255:~# gsmctl -J <-- Dead

root@Teltonika-TRB255:~# gsmctl -P <-- Dead
We have also had issues with updating and rolling back firmware and had to have TRB145 devices RMA'd as they were irrecoverable.
Let's hope they resolve these issues and the firmware update issues very shortly.

1 Answer

0 votes
by

Hello,

Have you checked the important notification in the FW wiki page here ? https://wiki.teltonika-networks.com/view/TRB141_Firmware_Downloads

Let me know if you can't upgrade by following this procedure: https://wiki.teltonika-networks.com/view/TRB141_Legacy_FW_Upgrade_Instructions

by
I can guarantee that these will not help. We recently tried the above and the device was irrecoverable- couldn't update, couldn't roll back, couldn't connect to network - had to be sent back for RMA.
by
Hi,

could you please send me serial codes of the devices that you've sent to RMA? Also please private message me the troubleshoot files of TRB's you have issues with.

EB.
by

Hi ErnestasB,

Can you please email me directly.

We got RMA'd devices back, still having issues:

Issues/Bugs:

TRB145: Firmware (Latest version)  
1) In RS485 Client mode the modem continually drops its connection and reconnects every "timeout interval". It should stay connected as it used to (previous firmwares for TRB145 and other devices like the TRB255 are successful at this).

TRB255: Firmware (TRB2_R_00.02.03.1)
1) In Modbus TCP Slave mode, many of the dynamic registers cannot be read.
https://wiki.teltonika-networks.com/view/TRB255_Monitoring_via_Modbus#Set_Parameters
Basic value registers such as "System Host Name" and "System Uptime" can be read, but the "Modem ID" and most importantly the "IMSI" cannot be read. We need to be able read the IMSI out of the device to identify it. Only about half of the advertised registers are able to be read successfully.

2) In the WebUI, none of the network parameters are filled out - eg, the screen does not show the network that it is connected to, the uptime, the IP address, the IMSI etc.  (Screenshot attached)

3) It does not seem to be possible to send AT commands via the CLI (eg. gsmctl -A AT+CIMI should retrieve the IMSI from a BG96 but the CLI says that it cannot understand the command)

4) In the CLI, several (most) of the gsmctl commands are either "not understood" by the interpreter "timeout",  or take a very long time to respond (eg. try to get the imsi with gsmctl -x). This still occurs when we put it into debug mode.At this stage it may take >30 seconds for some of these commands to respond, if they respond at all. For the IMSI command, I have only had 1 successful response from this command as 99% of the time it fails. The device has definitely read the IMSI by this time as it is connected to the internet and successfully transmits data over our IPSec tunnel. I have pasted findings from this in blue below:
  
eg.
root@Teltonika-TRB255:~# gsmctl -v                                                                                  
GSMCTL version: 0.2b                
root@Teltonika-TRB255:~# gsmctl -k                                                                                  
root@Teltonika-TRB255:~# gsmctl --at AT+CIMI <-- Dead

root@Teltonika-TRB255:~# gsmctl -x <-- Dead

root@Teltonika-TRB255:~# gsmctl -i   <-- Dead
Failed to invoke a gsmd object method                                                                                
GSMCTL error: reading message                                                                                        
N/A  
root@Teltonika-TRB255:~# gsmctl -c <-- Dead

root@Teltonika-TRB255:~# gsmctl -v                                                                                  
GSMCTL version: 0.2b                                                                                                
root@Teltonika-TRB255:~# gsmctl -j                                                                                  
Connected                                                                                                            
root@Teltonika-TRB255:~# gsmctl -J <-- Dead

root@Teltonika-TRB255:~# gsmctl -P <-- Dead
We have also had issues with updating and rolling back firmware and had to have TRB145 devices RMA'd as they were irrecoverable.
Let's hope they resolve these issues and the firmware update issues very shortly.
Kind regards, SD