BGS5T no response on COM port after some days - need to power off/on to work again! | Thales IoT Developer Community
August 22, 2020 - 7:54am, 1838 views
Hi,
I am using BGS5T modem with COM port connection on Windows10 computer.
After several days of normal usage, modem stops responding. AT commands are not answered any more! I tried with computer restart (without modem power off), but modem still don't respond!
The cure is to unplug modem from power supply, and reaply power. Modem starts working again.
Hello,
How do you connect the module - over RS232 or USB? Did you try to replug the cable or disconnect and reconnect the terminal program?
Regards,
Bartłomiej
It is connected over RS232.
I tried also with USB connection, but found driver problems and instabillity. (USB connection generates 2 virtual com ports, for instance).
I also tried repluging cable, without success, and tried with terminal, without success. (no response to AT commands).
At the moment modem is powered off and on again, it works (I don't have to do any action on my computer).
Regards,
Gregor
Hello,
Yes on USB there is mmore than one port available. In case of EHS6 for example there are even more ports.
Have you also tried on USB while this problem happened with RS232. Please check the SCFG "Serial/Interface/Allocation" configuration to make sure if USB should work. If repluging the cable does not solve the issue and the module does not reply on USB either that would suggest some real problem with the module. Maybe it is related to power supply. How frequently does it happen? Does the status LED change?
Regards,
Bartłomiej
Hi,
It happened again. I had USB and RS232 cables connected. Virtual com ports (on USB) disappeared and modem didn't respond any more to AT commands. I had to power off and on again for it to work again.
What do you suggest?
BR, Gregor
Hello,
And how about the status LED? Did it go off? Have you tried to replug the USB cable? anyway if USB ports disappeared, it could suggest that the module switched off. How do you use the device - was any terminal program connected to serial interface? Do you have any log - is there anything special like some URCs thrown before this happened? On the other hand what power supply do you use with he device? Maybe it is somehow related to the problem.
Regards,
Bartłomiej