Dickson Support Database
MultiTech Gateway Firmware Update Notes
| Multitech LoRaWAN Gateway | ||
| Date | Version | Notes |
| 4/23/2024 | 6.3.2 | – Bug fix #14808 When PUSH_ACK is not received the pkt fwd do not reboot – . Bug fix #14807 no temperature sensor found on port 0x48 – Release found here: \\srv-data\iso\4-Processus-V2\Product-Dev\2- Enregistrements et instructions\Logiciel\Gateway LoRa\FW\6.3.2 |
| 2/22/2024 | TBD | – Fix – to be released in next firmware. Will treat both sockets the same way. The device will reboot the the socket connections to self correct. Verstion TBD DevOps 14808 – The root cause has been ID by the R&D team. DATA Socket (S2) has been closed on the Merck network. Something on their network did close our socket. Maybe a switch, we cannot tel. Communication between the receiver and the server consists in 2 sockets. 1 Socket (S1) for the link which holds the link between the receiver and the server. (The receiver sends ping to the server evey X seconds) 1 Socket (S2) for the data which used for data transfer. When S1 is broken or closed, the server detect there is no link anymore between the server and the receiver. after X minutes (setup by the user) the server triggers a technical alarm (depending on alert rules configuration) In short the server monitors the socket Link S1 When S2 is broken or closed, The server does not detect that the receiver does not send data anymore. The S1 socket is still working. After a while without data from any cobalt the server will end to trigger a communication alarm lost, one for each cobalt (basically after 63 minutes) Comments: This is a weakness of our system. The server does not monitor Socket S2. It is a known issue that occurred already with different customers (2 or 3 times). A DEVOPS ticket has been created and R&D team will put the fix in the next sprint, which means a future receiver firmware will linclude that fix that will prevent from any similar issues. We cannot say when the fix will be available. In few words it is a critical issue, that we understand but that is covered up by the communication lost alarms for cobalts. |
| 10/10/2023 | 6.3 | UI Changes – no functional changes – requested list of UI changes https://www.multitech.net/developer/software/mlinux/mlinux-changelog/ |
| 1/10/2023 | 6.0.1 | – update to address hardware updates on new equipment. No need to upgrade existing equipment |
| 6/15/2022 | 5.3.8 | – v5.3.8 of the firmware of the Multitech LoRa gateway has just been released for both Advanced (blue), Pro (grey) and outdoor MTCDTIP – version is about bug fixes and there is no change from an end user point of view, no new behavior, no new feature, no user manual update. Consequently, no transfer knowledge is required. – one major fix specifically for the outdoor MTCDTIP model. So if there is no urgent need to upgrade the current Advanced and Pro gateways |
| 11/17/2021 | 5.3.3 | allows for new LoRa frequencies – update not required for the NA/SA – pro gateway only works in NA/SA and Europe |