and want to update to most recent production release.
There is absolutely no issue with the device, I just want to ensure correct behaviour in the upcoming pure LTE / 5G environment with focus on the sub-GHz Bands (700, 800, 900) and 1800MHz. If an update makes no sense in my scenario please tell me as well.
The current latest “stable” firmware version is exactly the one that you have currently. If you want to ensure correct bahviour, as you mention yourself, I’d suggest staying on your current firmware, as the latest one, the 7.16.3, while it might not have any issues, it hasn’t been out long enough to properly tell whether it would be safe to install in a production environment or such.
In that case, if the WebUI isn’t prompting you to upgrade the modem firmware, it is not necessary to do so. That’s the general rule of thumb that we like to recommend to follow. Forced updates are only done (and even then, rarely), when there are actual issues with the modem (disconnections, not connecting to mobile operators, etc.).
The WebUI tells me: “Modem updates from the server are not supported for this device.”
Since the modem firmware has “BETA” in the version number and the device is already a few years old, I assume that an update would make sense.
It would be helpful if future device firmware versions could online check the radio firmware and confirm the validity of the version in operation. It seems to be a frequent issue here.
Thank you for the insights and the feedback on how our modem firmware updating process works. Keeping your device up to date is indeed good practice and can help you keep your device running smoothly. In this case, although your modem firmware does say “BETA”, that doesn’t necessarily mean that you must update the firmware. As mentioned earlier, if you don’t seem to see any issues whatsoever, then an update is definitely not required. These updates, must be done, as I mentioned, when the device exclusively tells you that an update is available and that you should update, or, as mentioned, we, as support, help upgrade the firmwares when it is necessary (modem-related issues, etc.).
The issue is that I fear no to recognize issues in time. In my case I have to ensure optimal LTE band selection behaviour under weak signal conditions. There are certain maintenance cycles in which I can update to that latest version, that makes sense in terms of riskless predictive maintenance. Currently there is no must, but the devices will be in operation for years in places that are difficult to access. Will online update of the modem firmware be part of future device firmware versions? Recent OTD140 devices obviously have this opportunity.
I had similar problems when I wanted to deploy devices with newest software available.
I had to do a research on community.teltonika.lt and have found that there is a tool called modem_updater with which you can flash the modem firmware.
Just do:
opkg update
opkg install modem_updater
opkg install sshfs
modem_updater -g
Select version which you want to install modem_updater -v MODEM_VERSION_FROM_LIST
Looks like they pulling firmware from the server and mounting firmware folder with SSHFS. I was able to pull server address from modem_updater script - modemfota.teltonika-networks.com
to check if my device matches with the same modem FW version - indeed it did.
Downloaded the modem FW with your link mentioned and updated a 2nd device on my desk via WebUI. Worked. I will swap in the remote SIM and report when done. This will take some days. I have remote access but don’t want it to go offline erroniously.
The 2nd device with updated modem firmware works without problems since 1 week (Congstar/Telekom Germany). In this case, I performed the update via LAN to be on the safe side.
As predicted by @MatasR in my use case there is no advantage but also no recognizable disadvantage. The radio is just up to date now and the WebGUI reports: Internal modem firmware version EC25EUGAR06A09M4G_01.200.00.000
The update file name had been “EC25EUGAR06A09M4G_01.200.01.200“ without any recognizable extensions (e.g. .bin).
As initially mentioned the previous version had been EC25EUGAR06A05M4G_BETA1108_01.005.00.000