ELS 61-E copying .jad and .jar file to module in Explorer without USB cable | Telit Cinterion IoT Developer Community
September 22, 2020 - 2:48pm, 4702 views
Is there any possibility to copy Firmware to the els61-E with microsoft explorer (double click on module -> A: -> copying jad and jar file) without using an USB cable. just like we do it with EHS5T?
We tried this on various PCs and it does not work at all for us. We get "coonection failed" errors.
thank you in advance
Hello,
MES tool can communicate with the module on USB and RS232 and it works in the same way with both EHS5 and ELS61-E modules. Please make sure that the module can communicate on ASC0 with a terminal. If there are any problems please verify AT^SPOW? output and AT&V to check if hardware flow control is active (\Q3). Use AT\Q3 to activate it. If power saving on serial interfaces is active, please deactivate it with AT^SPOW=1,0,0. Close the terminal connection before using MES.
Best regards,
Bartłomiej
Hello,
Flow control is active and power saving is turned off.
AT^SPOW?
^SPOW: 1,0,0
OK
AT&V
ACTIVE PROFILE:
E1 Q0 V1 X0 &C1 &D2 &S0 \Q3
S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002
+CBST: 71,0,1
+CRLP: 61,61,78,6
+ICF: 3
+IPR: 115200
+DTMF: 0
^SCKS: 0,0
Does still not work unfortunately.
Ah, there's one more thing - please check if the userware system out is not redirected to ASC0 interface (AT^SCFG? command).
Please make sure first that you are able to execute AT commands on ASC0.
Hello,
we discard the output of the userware. Furthermore we are communicating via the serial connection with the Device, so AT commands on ASC0 are working.
Do you have any further ideas?
Thanks!
Here the "AT^SCFG?" output, maybe it will help:
AT^SCFG?
^SCFG: "Audio/Loop","0"
^SCFG: "Call/ECC","0"
^SCFG: "Call/Speech/Codec","0"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/mode/ASC1","std"
^SCFG: "Gpio/mode/DAI","gpio"
^SCFG: "Gpio/mode/DCD0","gpio"
^SCFG: "Gpio/mode/DSR0","gpio"
^SCFG: "Gpio/mode/DTR0","gpio"
^SCFG: "Gpio/mode/FSR","gpio"
^SCFG: "Gpio/mode/MCLK","gpio"
^SCFG: "Gpio/mode/PULSE","gpio"
^SCFG: "Gpio/mode/PWM","gpio"
^SCFG: "Gpio/mode/RING0","gpio"
^SCFG: "Gpio/mode/SPI","rsv"
^SCFG: "Gpio/mode/SYNC","std"
^SCFG: "Gpio/port/MCLK","GPIO4"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","ELS61-E R2"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEShutdown/sVsup/threshold","0","0"
^SCFG: "MEopMode/CFUN","0","1"
^SCFG: "MEopMode/Comp1",""
^SCFG: "MEopMode/CregRoam","0"
^SCFG: "MEopMode/ExpectDTR","current"
^SCFG: "MEopMode/ExpectDTR","powerup"
^SCFG: "MEopMode/SoR","off"
^SCFG: "MeOpMode/SRPOM","0"
^SCFG: "Radio/Band/2G","0x00000014"
^SCFG: "Radio/Band/3G","0x00000081"
^SCFG: "Radio/Band/4G","0x08080085"
^SCFG: "Radio/Mtpl/2G","0"
^SCFG: "Radio/Mtpl/3G","0"
^SCFG: "Radio/Mtpl/4G","0"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "RemoteWakeUp/Event/USB","none"
^SCFG: "RemoteWakeUp/Ports","current"
^SCFG: "RemoteWakeUp/Ports","powerup"
^SCFG: "Serial/Ifc","0"
^SCFG: "Serial/Interface/Allocation","1","1"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","005B","Cinterion Wireless Modules ","ELSx",""
^SCFG: "Tcp/IRT","3"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","6000"
^SCFG: "Tcp/TLS/Version","MIN","***"
^SCFG: "Tcp/WithURCs","on"
^SCFG: "Trace/Syslog/OTAP","0"
^SCFG: "Urc/Ringline","local"
^SCFG: "Urc/Ringline/ActiveTime","2"
^SCFG: "Userware/Autostart","1"
^SCFG: "Userware/Autostart/Delay","0"
^SCFG: "Userware/DebugInterface","0.0.0.0","0.0.0.0","0"
^SCFG: "Userware/DebugMode","off"
^SCFG: "Userware/Passwd",
^SCFG: "Userware/Stdout","null",,,,"off"
^SCFG: "Userware/Watchdog","1"
Is the same HW setup used for both modules?
Maybe try to update MES on your PC - please check here https://iot-developer.thalesgroup.com/documentation/download-documentati... for the installation CD for ELS61 module. In 'Installer' folder there will be 'MESSetup.exe' file.
We Assume that we have the same HW Setup. We have at least the same Connector pinout on our PCB
Updating the drivers did not work either. Could nto find any folder named "MES" or similiar
Hello,
You have pasted the connectors of RS485 variant. Here the ASC0 interface is connected to RS485 available on A+ and B- lines. ASC1 is available as RS232 on TXD1 and RXD1. No hardware flow control (RTS/CTS lines) is possible for ASC1. Is ELS61 also a terminal version? If so, there is probably no RS485 version. And ASC0 is available via D-Sub connector. Please note that ASC1 is not available in all configurations - please see ^SCFG: "Serial/Interface/Allocation" setting.
BR,
Bartłomiej
We had the EHS5t RS485 in use.
The els 61 is not the terminal version, but we built our own terminal.
We have rewired the ASC0 Port of the ELS 61 to the same connector pins as used on the EHS5T RS485.
We managed to connect to the ELS61-E a few *****. But it is somewhat randoom and does not work on every of our PCs.
Any idea what could cause this behaviour?
Hello,
From the software (module settings) point of view you have probably checked all that might have been most probably changed : AT^SPOW, AT&V (ATQ, AT+IPR,...), AT^SCFG ("Userware/Stdout", "Serial/Interface/Allocation").
So maybe it's hardware related (esp. if it's not the standard terminal). For instance RS232 interface on the module is low voltage and ***** level shifters to connect to PC. But if it still only affects file transfer ... are you sure that there are any problems in AT commands mode?
Another thing that may be worth checking is USB-RS232 converter if you are using any. These devices are sometimes causing problems.
BTW is it not possible to access file system at all or it is only problem in file transfers or only specific files?
Best regards,
Bartłomiej
communicationg with it over Serial connection using RS232 cable and putty for AT commands does not cause any trouble whatsoever.
We cant access the Filesystem at all. we get an "the module has ben disconnected" error while trying to access it via Explorer by doubleclicking "module"
Pages