I think I'm fighting the NIDAQ driver software but I'm looking for
confirmation of my hypothesis.
I'm trying to use a time-delayed one-shot (PCI-6602 counter) to trigger a
signal elsewhere in my system after my software shuts down (Borland C++
application). Unfortunately, it appears as though once the user exits the
software, the counter / timer is reset automatically by the driver thereby
cancelling any signal that I had previously set up to trigger at some point
in the future. Is this what's happening?
Thanks
Andy Struckhoff
DCS Corporation
Machine Vision Systems Center
