EHS6T USB with RS232 | Thales IoT Developer Community
January 14, 2020 - 1:01pm, 2637 views
Hello,
I'm trying to send AT commands to a EHS6T USB over the RS232 interface. But I get no response.
Is the RS232 activated as default?
I use Putty to test the interface. The COM port settings are correct because i can send successfully an AT command to a BGS2T.
For the test I send the simple AT command "AT" to the module.
Can you please help me?
Kind regards,
Clemens
Hello,
EHS6 module has two RS232 interfaces: ASC0 and ASC1. ASC0 is active in any configuration. On the terminal casing it is connected to 9-Pole D-sub connector. You should be using HW flow control (RTS/CTS). Additionally there is a sleep **** on serial interfaces active (please check AT^SOPW? output). However you should still be able to communciate (there may be delays). You can deactivate it with AT^SPOW=1,0,0.
The interface will also not work (for AT commands) if you configure system out for Java application on it - please check AT^SCFG? command.
Regards,
Bartłomiej
Hello Bartłomiej,
I'm using the ASC0 RS232 interface with the 9-Pole D-sub connector. These are my COM port settings (9600bit/s, 8 data bits, None parity, 1 stop bit, Harware flow control) in the windows 7 device manager.
I don't get an answer for all At commands. Don't know what I can do now... The BGS2T is working with the same connection and settings.
Regards,
Clemens
The default baudrate for this module is 115200 (8N1). Maybe that's the reason if all other settings are correct.
Thank you for the informaton.
Now I get a response of the module. But only in the starting phase. The modul is responsing about 30s after a restart.
These is the answer of AT^SCFG?:
^SCFG: "Audio/Loop","0"
^SCFG: "Call/ECC","0"
^SCFG: "Call/Ecall/AckTimeout","5000"
^SCFG: "Call/Ecall/Callback","0"
^SCFG: "Call/Ecall/CallbackTimeout","43200000"
^SCFG: "Call/Ecall/Msd","0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
^SCFG: "Call/Ecall/Pull****","0"
^SCFG: "Call/Ecall/SessionTimeout","20000"
^SCFG: "Call/Ecall/StartTimeout","5000"
^SCFG: "Call/Speech/Codec","0"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/****/ASC1","std"
^SCFG: "Gpio/****/DAI","gpio"
^SCFG: "Gpio/****/DCD0","gpio"
^SCFG: "Gpio/****/DSR0","gpio"
^SCFG: "Gpio/****/DTR0","gpio"
^SCFG: "Gpio/****/FSR","gpio"
^SCFG: "Gpio/****/HSIC","rsv"
^SCFG: "Gpio/****/PULSE","gpio"
^SCFG: "Gpio/****/PWM","gpio"
^SCFG: "Gpio/****/RING0","gpio"
^SCFG: "Gpio/****/SPI","rsv"
^SCFG: "Gpio/****/SYNC","std"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","EHS6"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEShutdown/sVsup/threshold","0","0"
^SCFG: "MEopMode/CFUN","0","1"
^SCFG: "MEopMode/Comp1",""
^SCFG: "MEopMode/Dormancy","0","0"
^SCFG: "MEopMode/ExpectDTR","current"
^SCFG: "MEopMode/ExpectDTR","powerup"
^SCFG: "MEopMode/SoR","off"
^SCFG: "Radio/Band","511"
^SCFG: "Radio/Mtpl","0"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "Serial/Interface/Allocation","1","1"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0058","Cinterion Wireless Modules","EHx",""
^SCFG: "Tcp/IRT","3"
^SCFG: "Tcp/MR","10"
^SCFG: "Tcp/OT","6000"
^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","0"
Please make sure that you have hardware flow control (RTS/CTS) active on PC side and check the power saving on serial interfaces (AT^SPOW?) - if it's active it requires HW flow control and introduces delays in communication.
AT^SPOW?
^SPOW: 2,1000,3
I changed now the setting to 1,0,0.
Now it's working.
Thank you for your help!