Baud rates over 9600 require some sort of hand shaking otherwise you can loose data. You may be able to get away as high as 14400 without it but I'd bet that alone could be the issue. I had an issue with a Symbol unit where a radio interrupt was causing the serial port to loose data. There were al whole lot of conditions leading up to the hiccup. If the T3 is off doing something 'more important' when your data arrives, it could lead to a loss of data. A complete guess would be the T3 serial port cannot keep up with the data stream without handshaking. Is it possible to enable it on the sensor? Even X-On/Off might help.
----- Original Message ----- From: "Karl-Petter �kesson" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Tuesday, June 08, 2004 11:01 AM Subject: Re: Serial comm differences between Simulator and real device > Hi, > > Thanks for your reply. I did some serial comm stuff in the olds days > too, software for a midi-interface and never had problems then, but now > I havent done any Palm coding for 5 years so it has taken some time to > get back on track. > > What do you mean by geometry? I'm using 38400 baud, 8N1 no handshaking. > Dont have the code here so I'm not sure here but I believe I use mostly > default settings when I open the serial port. > > Clearing I/O buffers? Isn't it enough I just read the data when there is > data available? > > I dont think my sensors is specifically sensitive, it gets the command > from the T3 and starts streaming data, the problem is the T3 that does > not read it. > > /Kalle -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
