EXS82-W connection problem | Telit Cinterion IoT Developer Community
August 29, 2021 - 1:52pm, 1745 views
Hello,
I have been working on the EXS82-W, the ATI1 returns:
EXS82-W
REVISION 01.200
A-REVISION 01.000.01
OK
The embedded application and everything work fine. However, after I insert the SIM and tried to register the network, the connection keeps breaking and send the "device error, resource temporarily unavailable".
I have tried to change the USB cable, but still, it happens very often, every time I sent a AT command, I need to connect again. BTW, I am using cutecom, and I also tried the python tools to connect, it's the same problem. Could you please tell me some possible cause and some possible solutions?
Best regards,
Pinying
Hello,
Would it be possible to paste some log? I haven't seen such message and can't also see it in the AT spec.
Is the embedded application running when it happens? Maybe it's related to the app.
Best regards,
Bartłomiej
Hello,
So after I have talked to you, the problem magically solved itself, as long as I don't touch it, it will maintain the connected status. However, when I disconnect it, it just repeat this problem, that I can not connect the module for a long time. So today I have seen some new thing, it returned +CSQ: 31,99 even I did not ask it to. Do you think it has something to do with the signal itself? The antenna?
Plus, today when I power up the module, the TXD0 LED is red.
Any help will be welcome and thank you ahead!
Best regards,
Joefy
Hello,
I probably wrongly assumed that the "device error, resource temporarily unavailable" comes from the module. But it's probably from your terminal program. I suppose that you are using Linux OS. I think that these problems may be Linux related or terminal related.
As for the terminal I was recently using minicom. It has no GUI but is quite convenient and stable.
As for the +CSQ: 31,99 I suppose that your OS must be sending some commands to the module out of your control and that's why you observed it. I suppose that it also switches off the echo on AT interface.
As for the LED - have you changed any configuration of your board, like switches, jumpers or cables?
BR,
Bartłomiej
Hello,
I didn't change the jumpers, as for the switches, PWR and ASC0 are both on USB. OK, I will try to change to minicom. But still, when this thing happened, the python tool also disconnect all the time. If I don't change or touch them, they work just fine. I really don't understand.
BR,
Joefy
And what do you mean be touching - what exactly do you do to stop it communicating? Is it than possible to connect to the module on this or other interface? Have you tried to debug the system (dmesg, lsusb, something else)?