Steve, Piggy-backing on this reply, which is an excellent reply and recommendation BTW, if it turns out that they need additional information (e.g. some sort of a "low fluid level" signal), they can hook that (up to 8 bits, anyway ;-) onto the data lines. That way, as you read the motor pulses (i.e. get the data available interrupts), you can snatch the byte of data (if appicable) and process it for whatever purpose the bits may have. I have currently lent my Async Proc manual (I bought the product about 10 days before it went public . . . do I have timing or what? ;-) but I expect it back on Monday. At that time I can give you some specifics if you choose to go that direction.
"Malcolm J. Kudra" <[EMAIL PROTECTED]> wrote: Wilson, Stephen wrote: >Moz and Darren > >Thanks for your replies. > >All I know so far is that the people who are requesting the software say they >will build an interface which will emit a single signal or a series of signals > Stephen, I suggest you consider: 1) Having the engineers connect the pulse signal to one of the (edge-sensitive) RS232 handshake lines; 2) Using the open source (formerly TurboPower) AsyncPro components to capture the handshake status changes; 3) Totalizing, displaying, relaying data (whatever is required) from the AsyncPro output. And please keep us posted on your progress! Best regards, Malcolm __________________________________________________ Delphi-Talk mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi-talk Ralph D. Wilson II [EMAIL PROTECTED] [EMAIL PROTECTED] "Any sufficiently advanced technology is indistinguishable from magic." A. C. Clark --------------------------------- Do you Yahoo!? Make Yahoo! your home page __________________________________________________ Delphi-Talk mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi-talk
