Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Through AT commands the module can be destried #86

Open
GoogleCodeExporter opened this issue Mar 20, 2015 · 2 comments
Open

Through AT commands the module can be destried #86

GoogleCodeExporter opened this issue Mar 20, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. I called the following command "AT+CSCLK=1" with the library: 
gsm.SimpleWriteln("AT+CSCLK=1");

Now the GSM module will not start any longer. If I make the power on process 
manually like described in the datasheet, the SIM900 will partly communicate, 
but produces a lot of errors. I listened on the UART and it looks like this:
AT
AT
AT
AT
AT
AT
AT
AT
AT
AT&F
ATE0
AT+CLIP=1
AT+CMEE=0
AT+CMEE=0
AT+CMEE=0
AT+CMEE=0
AT+CMEE=0
AT+CMGF=1
AT+CMGF=1
AT+CMGF=1
AT+CMGF=1
AT+CMGF=1
AT+CNMI=2,0
AT+CNMI=2,0
AT+CPMS="SM","SM","SM"
AT+CPMS="SM","SM","SM"
AT+CPMS="SM","SM","SM"
AT+CPMS="SM","SM","SM"
AT+CPMS="SM","SM","SM"
AT+CPMS="SM","SM","SM"
AT+CPMS="SM","SM","SM"
AT+CPMS="SM","SM","SM"
AT+CPMS="SM","SM","SM"
AT+CPMS="SM","SM","SM"
AT+CPBS="SM"
AT+CPBS="SM"
AT+CPBS="SM"
AT+CPBS="SM"
AT+CPBS="SM"
AT+CIPSHUT
AT+CIPSHUT
AT+CIPSHUT
AT+CIPSHUT
AT+CIPSHUT
ATE0


The autostart of the library only produces this:
AT
AT
...
AT
xxx x x xx x   x f (crazy letters) AT+IPR=9600¦ (more crazy letters)


I tried to reset the module with the following commands:
gsm.SimpleWriteln("ATZ")
gsm.SimpleWriteln("AT&F")

But it was no solution. Then I tried to send the commands through this 
application:
http://m2msupport.net/m2msupport/module-tester/
It is possible to send the commands, and I receive a "OK", but when I try to 
start the module later, I only receive ERROR.


To reset the module through the hardware reset input was also no solution.

Does anybody has an idea?


Original issue reported on code.google.com by [email protected] on 27 Jul 2013 at 8:19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant