> >Perhaps that's why my serial code was hard to debug on the Emulator!
> >
> >It polls the serial port based on the value of sysTicksPerSecond.
>
> Perhaps...or perhaps not. Poser makes no effort to make sure
> that emulated
> ticks occur at 100 per second. I don't know how frequently the
> tick count is
> incremented, or even if it's faster or slower than 100 per second
> -- it all
> depends on the platform you're running on, the host processor
> speed, the amount
> of time the emulated device spends dozing, etc.
The function returns 100 ticks per second on the emulator. I just used the
value to schedule a nilEvent every 100 mS so I can check for new data (which
can come in randomly). My old serial code was based on the GPS example in
Rhodes and McKeehan. I've simplified the scheduling for my own needs.
Don't know if SysTicksPerSecond() returns the real value on the emulator,
but with the new code, it is working fine on both the emulator and device.
This is on a 300 mHz AMD K6-2 running Win98 with tons of apps running.
Works fine for the 1200 baud stuff I'm targeting.
>
> Someday I'll probably patch the SysTicksPerSecond() function and
> have it return
> an appropriate value. But so far, there hasn't been much of a
> need for this, so
> it remains on my To Do list.
The emulator is a wonderful thing. (2.1d29) ;-)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Joe Wronski FitSense Technology [EMAIL PROTECTED]
Also at: [EMAIL PROTECTED]
http://www.fitsense.com And: http://home.earthlink.net/~jwronski
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
