On October 21, 2006, M Pulis wrote: > > On Oct 21, 2006, at 5:41 AM, Chase wrote: > > > > > > > when i run the app, my commands are spit out into the text field > > and then they are echo'd back afterward, then a final "OK" and > > that's it. notice that the output form Apple's Internet Connect > > app has an "OK" response after most of the commands. > > I would propose that the modem is not executing your commands or has > become confused. > > You should get as many OK's as Apple does. To fully emulate the log, > wherever Apple gets an OK, put a wait-for-OK state in your logic. > > The OK (not the echo, nor xmitwait) tells you to proceed with the > next write. xmitwait makes sure all chars in the command are sent, > not that the modem has executed the command. Some modems are very > slow for commands that change settings stored internally because > EEPROMs are slow to modify. >
given the way this control works, i'm not exactly sure how to do that. any suggestions? i thought xmitwait did this (or something functionally similar to this). the documentation for Serial control says: "If you need your code to wait for all data to be sent to the serial device before continuing, call the Serial control's XmitWait method immediately following a call to the Write method." regardless, suggestions on how to implement wait-for-OK state would be helpful. thanks. - chase _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
