ASC0 and ASC1 stop working after specific commands | Telit Cinterion IoT Developer Community
March 12, 2020 - 1:35am, 1819 views
I am using an EXS82-W module, and this module has the USB to UART port through an FTDI, and ASC1 is a pure UART.
During the development of my firmware to control the module, I noticed that the UARTs stop working.
Here is the scenario:
1 - B80 Kit has its ASC0 connected to PC through the USB port
2 - B80 Kit has its ASC1 connected to a USB->UART converter, connected to pins 10 and 12 of the B80 connector.
So, I have fully access in both ASC0 and ASC1, they work fine, I can send and receive AT commands normally.
However, when I execute any RF-related command in any ASC, both ASCs stop working, for example:
ASC1 = AT // works fine
ASC1 = ATE // works fine
ASC1 = COPS+2 // executes and then both UART stops working
If I execute the same steps in ASC0, the same problem happens at COPS+2.
This problem causes to ASC1 to dump trash signals in the serial channel.
Is there any solution for this?
I suspect that this may be interference from the RF part of the module?
P.S.: AT commands not related to RF-activation works fine, only those that start the RF/start connection are the ones that cause this problem.
Hello,
Do you have more than one module that behaves like that? Can you check 'ATI1' reply?
I have never experienced such problem. I'm not using B80 but it is a standard hardware that was used with other modules.
And what if you only connect ASC0?
Regards,
Bartłomiej
Hello,
Yes, I switched modules and the problem does not happen.
These are the modules I have:
- EXS82-W B2.1 (2 pieces)
- EXS82-W A2.4 (3 pieces)
- ENS22-E (2 pieces)
The problematic one is the EXS82-W B2.1.
With the others, I do not have issues.
ATI1 on the EXS82-W B2.1 gives me this:
ati1
Cinterion
EXS82-W
REVISION 00.020
A-REVISION 01.000.00
ATI1 on the EXS82-W A2.4 gives me this:
ati1
Cinterion
EXS82-W
REVISION 00.038
A-REVISION 01.000.00
I got these new EXS82-W A2.4 today. Since then, I was doing the tests on the B2.1 (problematic).
Hello,
So this proble occurs each time with this module? How about the other piece of the same HW version?
Anyway the firmware version of this problematic module is older. As this is not yet an official final release firmware I think that you should contact the person who provided you with these modules. Maybe it's software related issue. Maybe the firmware update will solve it.
Regards,
Bartłomiej