FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
517 views 2 comments
by anonymous

I have TRB245 and TRB255 with last firmware TRB2XX_R_00.02.03.1.

I received TRB's with GNSS antenna included.

Looking to specifications I saw that have GPS feature.

Please tell me where to find in WEBUI the GPS menu configuration.

Also in CLI the command gpsctl doesn't exist!!!!

Thank you,

Gabriel

1 Answer

0 votes
by anonymous
Hello,

GNSS support for TRB2XX should be available with 2.4 firmware upgrade, that should be released in upcoming weeks. So please wait until that.

Best regards,
VidasKac.
by
Dear VidasKac,

Any news on release date for v2.4 ?

thanks :-)
by

Hi VidasKac,

In that release, will the following issues also be fixed?

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


I gave up after searching this many. The --help command response pasted below suggests that these (and many others) should work

root@Teltonika-TRB255:~# gsmctl -help