BGS5 RS232 accesss | Thales IoT Developer Community
March 24, 2017 - 4:18pm, 1730 views
Hello,
we have several devices with a BGS5, which can't be accessed via RS232. Communication via USB is working fine, the RS232 Transceiver is working correct with correct voltage levels.
UART settings are 115,2kBaud/8/1/none.
AT+CGMR
REVISION 01.100
AT^SPOW?
^SPOW: 1,0,0
OK
AT^SCFG?
^SCFG: "Call/ECC","0"
^SCFG: "GPRS/AutoAttach","enabled"
^SCFG: "Gpio/****/ASC1","gpio"
^SCFG: "Gpio/****/DAI","gpio"
^SCFG: "Gpio/****/DCD0","std"
^SCFG: "Gpio/****/DSR0","std"
^SCFG: "Gpio/****/DTR0","std"
^SCFG: "Gpio/****/FSR","gpio"
^SCFG: "Gpio/****/PULSE","gpio"
^SCFG: "Gpio/****/PWM","gpio"
^SCFG: "Gpio/****/RING0","std"
^SCFG: "Gpio/****/SPI","gpio"
^SCFG: "Gpio/****/SYNC","std"
^SCFG: "Ident/Manufacturer","Cinterion"
^SCFG: "Ident/Product","BGS5"
^SCFG: "MEShutdown/Fso","0"
^SCFG: "MEopMode/SoR","on"
^SCFG: "Radio/Band","15"
^SCFG: "Radio/OutputPowerReduction","4"
^SCFG: "Serial/Interface/Allocation","0","0"
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0059","Cinterion Wireless Modules","Cinterion BGx USB Com Port",""
^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/Passwd",
^SCFG: "Userware/Stdout","null",,,,"off"
^SCFG: "Userware/Watchdog","0"
OK
Any ideas on how to get the UART working?
Best regards!
Hello,
The ASC1 is disabled according to the configuration but ASC0 should be working.
Is it that it's working with some devices and with some (same devices) not? Was it working in the past?
As I understand the modules are mounted in your own hardware and there are some level shifters added?
The power saving on RS is disabled. And how about the flow control?
Could you paste ATI1 and AT&V replies?
Regards,
Barłomiej
Hello Bartomiej,
The modules are monted on our terminal devices. The terminals are all factory tested, then delivered to the customer. After some time with the customer, RS232 communication is no longer working (it happened with ca. 15-20% of the delivered terminals).
The RS232 interface is fully connected, DTR and RTS are handled by the the DTE. As an expreiment CTS and RTS at the terminal were directly connected. But still no RS232 communication is possible.
These are the replies:
ATI1
Cinterion
BGS5
REVISION 01.100
A-REVISION 00.000.21
OK
AT&V
ACTIVE PROFILE:
E1 Q0 V1 X4 &C1 &D2 &S0 \Q3
S0:000 S3:013 S4:010 S5:008 S6:000 S7:060 S8:000 S10:002
+CBST: 7,0,1
+CRLP: 61,61,78,6
+CR: 0
+CRC: 0
+CMGF: 0
+CNMI: 1,0,0,0,0
+CMEE: 0
+CSMS: 0,1,1,1
+CREG: 0,1
+CLIP: 0,2
+COPS: 0,0,"E-Plus",0
+CGSMS: 1
OK
Best regards
Hello,
I suppose that you mean by RS232 the ASC0 interface.
Don't you have any information from the customer if they have been doing anything special with the terminals before that happened? This might be helpful.
If it was working previously it might be either the hardware failure or maybe they have changed some configuration.
According to the profile the hardware flow control is active and for this firmware it is the only option.
I suppose that the module is soldered to the board and there is no way to test it outside.
Is there any customer MIDlet running?
How about ASC1 interface - is it also connected, have you tried to communicate?
Have you tried any tracing or oscilloscoping of the lines?
You have the latest firmware.
For now I can't think of any more configuration settings that might cause this.
Regards,
Bartłomiej