We are experiencing quite some trouble with the “new” Q2400A…
We would like to use the following software because our major application development started with OpenAT 2.0… (Porting to OpenAT 3.x is not an option at the moment, since there are incompatibilities that would need major adjustments in our application…)
ati3 344_09gm.Q2400A 1372584 012406 11:46 OK at+wopen=2 +WOPEN: 2,"AT v02.12" OK
Now, when there is no application loaded (just the core firmware as it is) it does behave strangely on at+wopen commands (in our device or on a starter kit):
at+wopen=1 turns the module off!! That did not happen before with older versions (e.g. OpenAT 2.0 or 2.1c). You will then get the OK after pushing the ON button for about 2 seconds.
at+wopen=1 --> module off OK at+wopen=2 +WOPEN: 2,"AT v02.12" OK at+wopen? +WOPEN: 1 OK at+wopen=0 --> module off OK
after at+wopen=0 the same thing happens.
This is really not good for our application, actually it totally messes with our automated update tool which can’t function when the device shuts off on every firmware update related command… (by the way it does that also when at+wopen=4 is used when an application is loaded)
Of course it doesn’t really matter what the module does when there is NO application loaded… But it will do the same with an application loaded! I just used this scenario to confirm that the behavior is NOT caused by our application.
Another thing is that when our application is running, you can not stop it with
It keeps running!! But you may stop it with
(Needless to say that in the previous releases of OpenAT this just worked fine, too…)
Will there be a fix for the problem that the module turns off? Or was this actually done on purpose? It really will cause us a lot of trouble so I hope to hear some good news!
AT+WOPEN=0 wouldn’t be that critical, as long as we know about it…