Cannot communicate with BGS2-T via RS232 | Telit Cinterion IoT Developer Community
March 16, 2021 - 9:31am, 899 views
Hello,
I have a bgs2t modem and I aqm trying to communicate with it via rs232. I am NOT using a rs232/usb converter and I am using a working cable since it works with another modem device. I used putty with configuration 9600,7,even,1,xon/xoff (the one who sold me the modem told me to use this). I have also used other configurations like 9600,8,none,1 and others, but no way I can communicate.
The putty console stays black and when I press keys nothing happens. I cannot send any AT commands. The modem registers itself on the carrier network since the orange LED blinks 3s off/75ms on, but after that it looks like dead.
I have read on this forum that voltage on IGN_IN pin might be the cause, so I have tried to give a voltage between pins PLUS and GND only but the result is the same.
A lot of users on this forum had a problem similar to mine and they solved it. How can I try?
Hello,
If you see the LED blinking most probably the terminal is working. Do you have the hardware description document for the terminal?
The factory baudrate for ASC0 should be autobauding. As for the rest of parameters 8N1 is the default. Flow control may be disabled or you might try RTS/CTS. But if the terminal was previously used by the seller it may be the best idea to use the parameters they gave you.
Do you have any experience with other Thales modules? To execute any AT command you need to add <CR> character in the end. Try some other terminal program like ZOC or Teraterm to make sure that the software or it's configuration is not problem here.
Best regards,
Bartłomiej
Hello,
I have tried various parameters without success. I do not have experience with Thales modules but I have with other modems, with which I communicate successfully. I have the hardware description document for the terminal. I have tried other terminals but they don't work as well.
How do you connect the device to PC? Do you use any RS232-USB converter? Maybe it is faulty. Are you sure that you try on the correct COM port? Please try to reboot the terminal while it is connected and check if you can see any data (like SYSSTART URC) sent by the terminal.
Maybe the terminals are used but it does not seem probable that all are broken.