# OK after power on reset **URL:** \ **Category:** Open AT\ **Created:** [November 28, 2005, 11:00am UTC](https://forum.sierrawireless.com/t/ok-after-power-on-reset/155 "2005-11-28T11:00:46Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![snoooze](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@snoooze](https://forum.sierrawireless.com/u/snoooze)\ **Post date:** [November 28, 2005, 11:00am UTC](https://forum.sierrawireless.com/t/ok-after-power-on-reset/155/1 "2005-11-28T11:00:46Z")
Hello all, I stumbled into some strange behaviour of a modem. Every time the unit is resetted with power off/on, it sends out “OK” on the serial port even though I’ve not sent any command and its even before “+WIND: 3”!! It doesn’t matter if I got the serial port connected or not, or if flowcontrol is enabled/disabled. However, the “OK” is not sent out after a “+CFUN=1” It seems like it is caused by the fact that an OpenAT application has been running on the unit and later disabled. But the “OK” does not disappear even if Open AT is disabled/deleted (+WOPEN=3, =4, and =0) or even if I download the whole GSM core firmware. I’ve also tried to reconfigure every command I can think of that can cause somthing like this. Unit is Q2406B with 6.41b and Open AT 2.10. Anyone seen this before and know how to get rid of this unwanted “OK”? Is this a Wavecom bug? Is there a workaround? /Snoooze ---
**Author:** ![eyal](https://avatars.discourse-cdn.com/v4/letter/e/76d3ee/32.png) [@eyal](https://forum.sierrawireless.com/u/eyal)\ **Post date:** [November 30, 2005, 11:19am UTC](https://forum.sierrawireless.com/t/ok-after-power-on-reset/155/2 "2005-11-30T11:19:51Z")
I’m using FASTRACK modem ( M1306B ) and i have the same problem. at the first start it show WIND: 3 OK for every period time. ( 2 or 3 sec ) Please Help!!! ---
**Author:** ![snoooze](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@snoooze](https://forum.sierrawireless.com/u/snoooze)\ **Post date:** [November 30, 2005, 2:38pm UTC](https://forum.sierrawireless.com/t/ok-after-power-on-reset/155/3 "2005-11-30T14:38:17Z")
OK, then I’m not alone about this… But My “OK” is sent out before the “+WIND3” ```auto ...Power on... OK +WIND: 3 . . ``` /Snoooze ---
**Author:** ![huangyi](https://avatars.discourse-cdn.com/v4/letter/h/9dc877/32.png) [@huangyi](https://forum.sierrawireless.com/u/huangyi)\ **Post date:** [December 22, 2005, 1:56am UTC](https://forum.sierrawireless.com/t/ok-after-power-on-reset/155/4 "2005-12-22T01:56:46Z")
I have found that the module will response “at+wbhv” with two "OK"s. This happened only to 651\_09gg. at+cgmr 651\_09gg.Q2406B 1478872 070705 14:15 OK ///How come got two OK ??? at+wbhv=1,0 OK OK ---
**Author:** ![skos](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@skos](https://forum.sierrawireless.com/u/skos)\ **Post date:** [January 17, 2006, 7:32am UTC](https://forum.sierrawireless.com/t/ok-after-power-on-reset/155/5 "2006-01-17T07:32:39Z")
Hi, at power on, I have noticed the same result with the “OK”. With “641b09gg.Q2406B 1339080 041604 16:04” I receive also the “OK” before the “+WIND: 3”. But when I use an older version “640d09gg.Q2406B 1273604 091103 18:26” I got no “OK” before the “+WIND: 3”. regards skos ---
**Author:** ![snoooze](https://avatars.discourse-cdn.com/v4/letter/s/f08c70/32.png) [@snoooze](https://forum.sierrawireless.com/u/snoooze)\ **Post date:** [January 17, 2006, 9:07am UTC](https://forum.sierrawireless.com/t/ok-after-power-on-reset/155/6 "2006-01-17T09:07:32Z")
hmm, interesting, > [@](#): > > But when I use an older version “640d09gg.Q2406B 1273604 091103 18:26” I got no “OK” before the “+WIND: 3”. …and when you go back to the 6.41b you get the OK again, right? Have you found out how to get rid of it? Or have you found out what is causing it? /Snoooze ---
**Author:** ![skos](https://avatars.discourse-cdn.com/v4/letter/s/bc79bd/32.png) [@skos](https://forum.sierrawireless.com/u/skos)\ **Post date:** [January 17, 2006, 9:21am UTC](https://forum.sierrawireless.com/t/ok-after-power-on-reset/155/7 "2006-01-17T09:21:04Z")
. > [@](#): > > …and when you go back to the 6.41b you get the OK again, right? Yes, you can receive the OK again. > [@](#): > > Have you found out how to get rid of it? Maybe wavecom build in this OK, because a big customer need this message to detect anything. ❓ ❓ ❓ It could be similar to OpenAt 3.x with the at+wdwl/at+cfun=1 command. There you have also a changed behaviour to OpenAt 2.x regards skos ---
**Author:** ![Wallace](https://avatars.discourse-cdn.com/v4/letter/w/b4bc9f/32.png) [@Wallace](https://forum.sierrawireless.com/u/Wallace)\ **Post date:** [January 17, 2006, 9:24am UTC](https://forum.sierrawireless.com/t/ok-after-power-on-reset/155/8 "2006-01-17T09:24:37Z")
> [@snoooze](#): > > hmm, interesting, > > > [@](#): > > > > But when I use an older version “640d09gg.Q2406B 1273604 091103 18:26” I got no “OK” before the “+WIND: 3”. > > …and when you go back to the 6.41b you get the OK again, right? > > Have you found out how to get rid of it? > > Or have you found out what is causing it? > > /Snoooze Hi, This should be the bug of 6.41b firmware. In 6.41c firmware release note there is stated “Correct Problem” : “OK is displayed when resetting the module”. I tried 6.41c and get no extra “OK”, but not yet tried 6.5x