Help to configure EHS6T Lan modem for python GsmModem module | Telit Cinterion IoT Developer Community
February 10, 2022 - 12:21pm, 2267 views
Hello,
I have just purchased an EHS6T Lan modem and would like to use it with python GsmModem module (https://pypi.org/project/python-gsmmodem).
I already adapted the module to work with Coniugo Ethernet LAN Modem ( https://www.coniugo.de/tl_files/dateien/downloads/datenblaetter/GSM-Modems-EN/Datasheet_GPRS_Modem_RS232_USB_LAN.pdf ) : I use the LAN version (700400170S (LAN-Version).
With Cinterion Modem, I have errors when connecting and Modem close doesn't work.
Need help for configure the EHS6T in my context.
Regards,
Hello,
These terminals contain our module and your hardware. And you want to use one of them with this python GsmModem project? And it has nothing to do with our Thales LAN terminal?
Could you then explain some details of your problems? GsmModem project is not known for me. But I could look at it from the module's perspective.
Regards,
Bartłomiej
Hello,
Thanks for your reply.
"These terminals contain our module and your hardware" , Please, do you means Conuingo modem contains Cinterion hadware / Chipset ?
My problem, when I try to connect Modem (telnet on port 1234) from Python, I get Error message. And when I close the telnet session from Python, session is not closed and I cannot connect anymore.
Also when I'm able to connect once and run USSD command, response is not well formatted. For example "new lines" (\n) are not processed....
My main purpose for this modem is to run USSD commands, read SMS from my Python program.
Thanks.
My intention was to figure out if you use some third party terminal with Thales module inside or Thales terminal.
I assume now that it is Thales terminal and you try to send AT commands over Telnet.
Have you tried without Python? And have you tried to manually connect over Telnet after Python script failed? Did you try to debug in Python to see when it fails, what are the errors etc.? Is any debug log available?
In case of USSD please also try manually over Telnet and over serial port and check if there is any difference in the formatting.
In general I would start from testing the same AT commands without Python first.
Hello,
Thank you so much for your suggestions .
I will make all tests and then update you.
Regards,
Hi,
Here is the output of an USSD command :
AT+CUSD=1,"*155#"
OK
+CUSD: 1,"Flooz\0A\0A1-Transfert\0A2-Marchand\0A3-Achat de Produits\0A4-Paiement de factures\0A5-Retrait\0A6-Mon Compte\0A7-Ma banque en ligne\0A8-Promo Conso Flooz\0A9-Autres Services\0A\0A\0A",15
"\0A\0A" Should be new line.....
Thanks.
After URC is printed out I would expect 0D0A, the same as after OK reply. It is the output from physical interface or Telnet? Are both the same?
Hello,
Thanks for your reply.
Shown response if from Telnet Interface. Modem will be used on LAN only.
Thanks.
And how about the physical interface? Did you compare? That would help to verify if this formatting comes from the module or it is changed somewhere in a way. Maybe even by the telnet client.
On the other hand +CUSD: 1 means (which I didn't notice before) that further user action is required and the URC ends with ">" to prompt the TE for the response data (which should be terminated with <CTRL-Z>). So I'd start from testing without telnet first.
Hello,
Sorry for the silence. I did have Serial cable I had to place order for new one and get it shipped.
I tested with serial port the result is exactly the same.
Attached is the serial command output.
Thanks.
Hello,
Thanks for the screen.
So it looks exactly like the description I sent you last time. "+CUSD: 1" means that further user action is required and the URC ends with ">" to prompt the TE for the response data (which should be terminated with <CTRL-Z>). In your screen I see ">" character. So now the response should be sent back.
BR,
Bartłomiej
Pages