Why does an AT command sometimes return error even if it works fine a moment later?

[Wilbert van Dolleweerd]

I've deployed the example application to the TC65. However, sometimes I can't get it to run. 

See the following AT-commands:

ATZ

OK

AT^SJRA=a:/SMSHeartbeat.jar

ERROR

ATZ

OK

AT^SJRA=a:/SMSHeartbeat.jar

OK

Constructor

startApp

Hello World

destroyApp(true)

Why doesn't it run the first time, but it does the second time? I also see this behaviour sometimes with the AT^SCFG="Userware/Stdout", "ASC0" command, so it is not related to the Java example.

[Joschka Thurner]

Can't remember experiencing this with SJRA/SCFG, maybe this is related to the ATZ? You can turn on extended error reporting (AT+CMEE) for debugging.

[Wilbert van Dolleweerd]

Thanks, will try it tomorrow with the extended error reporting on.

Met vriendelijke groet / kind regards,

Wilbert van Dolleweerd
http://gplus.to/WilbertVanDolleweerd

--
javacint group - http://www.javacint.com/
 
 

[Antonio Lopez]

Hi,

Just try to have at least 200 ms between an answer(OK/ERROR/etc) and a new AT command

Regards

Alopez