Reset ASC0 Baudrate | Telit Cinterion IoT Developer Community
December 26, 2017 - 9:25am, 6237 views
I cannot send at commands to my BGS5 module via ASC0 probably because of baudrate difference.
I don't know what its baudrate was set lastly. I tried with general baudrates 9600,115200, 230400 etc..but I couldn't find. When module restarted, unreadable characters coming to terminal program window instead of ^SYSSTART, ^SYSLOADING.I mean, startup messages are coming but because of baudrate difference they appear as unreadable characters.
Is there a way of resetting ASC0 connection settings to default for situations like this?
there is no way to reset baudrate on ASC0. But you schould be able to find right one but you need to try really all possbile :
Of course you can access module on ASC1 ( if configured) and USB but this will not help as each port has separate baudrate settings.
Thanks for the answer.
I have made a test again now.
I have set the baudrate of terminal program, opened connection and restarted module.
I have made the test repeatingly for all baudrates above. I haven't catched SYSLOADING, SYSSTART strings.
I have seen unreadable values on terminal screen at each test.
What can be the reason? What can I try?
Is this module work normally before? This strings could be module exit but please try other interfaces like USB or ASC1. If also there there is no sysstart sysloading and you cannot use at commands this could indicate that module is broken.
USB interface is working properly. I can send at commands via this interface.
I can also update firmware of module via USB interface.
I didn't have ASC1 outputs (BGS5 module is our own PCB and we don't use ASC1) so I cannot test ASC1 interface.
ASC0 interface also was working 2 days ago. Problem occurred during a firmware update process with gwinswup exe.
Do you have the BGS5 USB available? You could set or see the baudrate through that interface.
Another option is to use Gemalto/Cinterion/Siemens software "Resetbaud.exe" from 2006.
This software scans the all combinations through, including speed, world length, parity, stop bit etc.
The "Resetbaud.exe" can be obtained from your Gemalto contact.
Communication and Mechatronics
Enkom Active Oy – www.enkom-active.fi
Upseerinkatu 3 A, 02600 Espoo, Finland
Mobile: +358 400 411368
Office: +358 10 204 0000
Fax: +358 10 204 0010
Thanks for the answer.
IPR setting is not global. Each interface has its own setting. I mean, IPR setting from USB does not effect the setting of ASC0 or ASC1. IPR setting of each interface can be set only by connecting via that interface.
I don't have information about Resetbaud.exe. Actually, I have asked at my first question if there is a way of resetting baudrate of ASC0. Lukasz, do you know a tool like Antero mentioned?
I don't know this tool but it is not for resetting but only check all possible options. Now when you inform me that problem occur after FW update I have more things to check :
- Please display on USB port AT^SCFG? to check if your configuration is still right - it could happen that after FW update some settings are changed
Here is example of normal settings :
^SCFG: "Serial/USB/DDD","0","0","0409","1E2D","0059","Cinterion Wireless Modules","Cinterion BGx USB Com Port",""
Important points are ASC0 serial lines assigment , serial interface allocation, and Userware/Stout
Another points to check is if you have ^SYSLOADING and ^SYSTART on USB and not only ^SYSLOADING .
Also please check AT^SPOW? It is better to have disabled ^SPOW: 1,0,0 as enabled could make communication attempts harder on serial ports.
Please note that in this command ASC0 and ASC1 can be completely DISABLED ! ( <mode>=0).
We have found the reason of problem and made the ASC0 work with my hardware designer collegue.
As I said previously, the problem occured during a firmware update process with gwinswup.
I had selected baudrate as 460800 on gwinswup to make process faster. Process started but didn't finish successfully. It aborted. So, the baudrate speed remained as 460800.
There are some izolator components (opto coupler) in front of RX,TX pins of ASC0 on our pcb board. And according to my hardware designer collegue, they limit the data speed. Although module supports high data rates, our board does not support high data speed over 250 kbps. Data is damaged for speeds greater than 250kbps.
In our problematic scenario, module was sending SYSSTART,SYSLOADING but they seem as unreadable characters on terminal program. The characters were damaged because of speed problem. Data speed was too fast to be able to detect properly. We communicated with module directly bypassing optocouplers and got characters properly and send AT+IPR=115200 then.
Nice to hear that you resolved this problem.
All the best in coming new 2018 !
Thanks for support.
Happy new year.