I don't use the control signals directly so I don't know their limitations.
Try increasing the delay to see if at what point it the signal does go high
for a longer period. That will give you an idea if the signal duration is
too short for the 232 driver.
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent: Friday, September 19, 2003 11:40 AM
Subject: Using Break Signal - Serial Manager
> Unfortunately the duration is too critical (I have to get a 25mS of high
> signal and 25mS of low signal before I can transmit) with less than 2%
> variation.
>
> I tried to eliminate the Int32 problem which SysTaskDelay takes, and I put
a
> dumb loop instead (just to check):
>
> if (blnBreak) {
>
> error = SrmControl(gPortID, srmCtlStartBreak, 0,&flagsSize);
>
> //Temporarily
> while (timeSecond < 1) {
> while (timeStamp < 9750) {
> timeStamp++;
> }
> timeSecond++;
> }
>
> //SysTaskDelay(25*SysTicksPerSecond()/1000);
>
> error = SrmControl(gPortID, srmCtlStopBreak, 0,&flagsSize);
>
> timeSecond=0;
> timeStamp = 0;
>
> //Temporarily
> while (timeSecond < 1) {
> while (timeStamp < 10050) {
> timeStamp++;
> }
> timeSecond++;
> }
> //SysTaskDelay(27*SysTicksPerSecond()/1000);
>
> }
>
> It gets a tiny low signal (almost a bit time) in the midle of high signal
> (3ms before high signal goes down).
>
> The problem persists. Do You think a 25mS high break signal is too short
to
> srmCtlStopBreak?
>
> I'm using Palm Vx (dragonball 20MHz) which returns SysTicksPerSecond() =
> 100, so the math 30*100/1000 = 3 Ticks or 30mS?
>
> []
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
