# AT+CMGS gives "+CME ERROR: 515" when OpenAT runnin **URL:** \ **Category:** Open AT\ **Created:** [September 14, 2006, 10:01pm UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690 "2006-09-14T22:01:38Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![charlesoram](https://avatars.discourse-cdn.com/v4/letter/c/7ea924/32.png) [@charlesoram](https://forum.sierrawireless.com/u/charlesoram)\ **Post date:** [September 14, 2006, 10:01pm UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/1 "2006-09-14T22:01:38Z")
Hi, If my OpenAt application is running and I try to send an SMS message using AT+CMGS I always get “+CME ERROR: 515”. If I stop the OpenAT application (AT+WOPEN=0) then the AT+CMGS works and the message is sent. I thought this was because my application was calling adl\_smsSubscribe(), but after changing it so that it only calls adl\_smsSubscribe() when needed I still get the same result (when my application wants to send an SMS message it calls adl\_smsSubscribe(), sends the message and then calls adl\_smsUnsubscribe()). I’m using OpenAT 3.01. I’ve just noticed that AT+CGMR doesn’t work while my application is running either. I know what the “+CME ERROR: 515” is supposed to mean, but it doesn’t make sense, because my application has no problem sending an SMS message and neither does AT+CMGS if I stop the application. Any ideas? regards, Charles ---
**Author:** ![coan](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@coan](https://forum.sierrawireless.com/u/coan)\ **Post date:** [February 4, 2007, 12:08pm UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/2 "2007-02-04T12:08:32Z")
Does anybody has an answer to this? I get an CME error 515 whenever I use at+cmgs while I have an open-at application running (any application even a dummy one that doesn’t do anything). If I stop the appl. (at+wopen=0) at+cmgs works normal. I have 650a with SDK 3.01. Should I move to 3.02 or 3.03 ??? ---
**Author:** ![coan](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@coan](https://forum.sierrawireless.com/u/coan)\ **Post date:** [February 4, 2007, 9:35pm UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/3 "2007-02-04T21:35:42Z")
Having done more tests I can say more of what is exactly happening: So with 650a core soft. version and OPEN AT 3.01 while there is an embedded open-at application running in the modem (I tried 2-3 samples) when you try to send an sms from external application (uart) with at+cmgs you get this: at+cmgs=xxxxxxxx (enter) you get the prompt (\>) to write the sms. case a) \>hello [works fine] case b) \>hello (enter) {which is ascii 10 and ascii 13} CME Error 515 error This must be a Wavecom bug. Confusing the intermediate mode (\>) with the OPEN-AT application when you press enter (CrLf character). Can somebody please inform me if it is fixed in OPEN-AT 3.02 , 3.03 or later??? I wouldn’t like to set a new environment to find out if it is behaving the same way. Thank you BR Costas ---
**Author:** ![jan](https://avatars.discourse-cdn.com/v4/letter/j/ce7236/32.png) [@jan](https://forum.sierrawireless.com/u/jan)\ **Post date:** [February 5, 2007, 7:45am UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/4 "2007-02-05T07:45:09Z")
Hi Costas, I don’t know if this is a bug, or a feature… But in any case you should not consider switching to version 3.02. I found some bugs and I think other people here agree that this version should not be used… Best Regards, Jan ---
**Author:** ![charlesoram](https://avatars.discourse-cdn.com/v4/letter/c/7ea924/32.png) [@charlesoram](https://forum.sierrawireless.com/u/charlesoram)\ **Post date:** [February 9, 2007, 2:54am UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/5 "2007-02-09T02:54:28Z")
I should have posted a follow-up to this… The error seems to be fixed in Open AT v3.10 and I do not get the error since I upgraded to 3.10. - Charles ---
**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\ **Post date:** [February 9, 2007, 7:33am UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/6 "2007-02-09T07:33:57Z")
> [@jan](#): > > you should not consider … version 3.02. > I found some bugs and I think other people here agree that this version should not be used… Would you trust v3.03? ---
**Author:** ![jan](https://avatars.discourse-cdn.com/v4/letter/j/ce7236/32.png) [@jan](https://forum.sierrawireless.com/u/jan)\ **Post date:** [February 9, 2007, 8:32am UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/7 "2007-02-09T08:32:17Z")
Trust? No… but trust more than 3.02 or 3.10… Best Regards, Jan ---
**Author:** ![coan](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@coan](https://forum.sierrawireless.com/u/coan)\ **Post date:** [February 9, 2007, 9:15am UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/8 "2007-02-09T09:15:44Z")
Maybe I have to try 3.10 in a different partition ❓ and see how it behaves … It would not be very nice if it solves this issue but introduces new ones ! Charles what is your opinion is it stable enough (3.10)? Thank you ---
**Author:** ![awneil](https://avatars.discourse-cdn.com/v4/letter/a/49beb7/32.png) [@awneil](https://forum.sierrawireless.com/u/awneil)\ **Post date:** [February 9, 2007, 10:00am UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/9 "2007-02-09T10:00:44Z")
> [@coan](#): > > … solves this issue but introduces new ones ! That’s software for you! 8) ---
**Author:** ![charlesoram](https://avatars.discourse-cdn.com/v4/letter/c/7ea924/32.png) [@charlesoram](https://forum.sierrawireless.com/u/charlesoram)\ **Post date:** [February 28, 2007, 12:20am UTC](https://forum.sierrawireless.com/t/at-cmgs-gives-cme-error-515-when-openat-runnin/690/10 "2007-02-28T00:20:09Z")
v3.10 seems to be fine. I haven’t done much with it, other than fix a few bugs, but I have had no complaints from the customer using it for 2 months or more… - Charles