Firmware for ELS61-E R2 | Thales IoT Developer Community
April 3, 2020 - 10:29am, 2068 views
Hello,
we would like to upgrade the firmware of our ELS61-E R2 boards:
ATI1
Cinterion
ELS61-E R2
REVISION 02.000
A-REVISION 01.000.01
OK
We are seeing some stability problem (module not responding to commands any more) and we really would like to check whether it will be better with newer firmware.
Thank you!
CV_AC
Hello,
There's one update for this version (A-REVISION 01.000.02).
If you have any particular problem and especiall if you suspect any issues with the product, please provide more information: what exaclty happens and in what circumstances, any logs if possible, reproducibility etc., please report it to Thales support (if you have access) or to your distributor.
Or you can of course write on the forum - maybe we'll be able to advice.
Best regards,
Bartłomiej
Hello,
reproducability is not good. It turns up every now and then.
We connect with telnet to {ip-address}:1234 and try to issue AT commands. Every now and then, it does make a telnet connection, but does not talk anymore - no AT commands are responded to.
So we power-cycle the device and everything works again.
Can I get the software update from you?
Also, I'm hearing there will be A-REVISION 01.000.05 soon - is there a specific planned release date?
Thanks a lot,
CV_AC
Hello,
Here we are talking about the terminal which consists of ELS61-E R2 module and an additional processr which runs OpenWrt system and is using the module as a modem to provide internet connection for a device connected to LAN port. So we have 2 systems here. And OpenWrt provides the AT commands execution possibility on the module over USB port to LAN device over Telnet. So for now we can't be sure why this happens. Have you tried to establish the telnet connection again? You can check if it is possible to execute commans over RS232 port on the terminal. You can also check if you can connect over SSH to OpenWrt. Does the LAN device still have the internet connection over the terminal when it happens? Are there any specific commands that you send over Telnet when it happens?
As for A-REVISION 01.000.05 I don't have any official information. For now we have A-REVISION 01.000.02 available.
Best regards,
Bartłomiej
Hello,
it's not so easy to try the RS232 port while this happens (production environment, and the device is not exactly "reachable" ... oh well). SSH would be an idea ... I'll keep that in mind the next time I see this.
We use the box for sending SMS messages, so it just hangs around on the mobile network for days and weeks and at some point, when there's an alarm, it ***** to send a SMS. Functionality is really very basic.
We're beginning to try and look after this a bit more systematically now, so first of all, I'll send test SMS messages more frequently to make sure that we detect those "hangs" more quickly. Depending on where I am at that point and whether the device is physically accessible (not so easy these days), more investigations will follow. :)
I'll keep you posted.
Cheers
CV_AC
Hello,
OK, so as I understand the terminal is only used for sending SMS messages over the LAN connection. And sometimes there's no reply.
I agree that some more investigation is needed to diagnose this, for instance what happens if you try to reconnect over Telnet or connect over SSH and try some diagnosis in Linux system. BTW there are few USB interfaces that enumerate in the system, the assignement depends on "Serial/Interface/Allocation" setting. There may be up to 3 available for AT commands. So there may be one not used by OpenWrt which could possibly be also used for diagnosis from inside OpenWrt if the module can reply to commands on USB.
Regards,
Bartłomiej