- From: Herman Bruyninckx <Herman.Bruyninckx_at_mech.kuleuven.ac.be>
- Date: Wed, 30 Apr 2003 22:25:12 +0200 (CEST)
On Wed, 30 Apr 2003, David Schleef wrote: > On Wed, Apr 30, 2003 at 09:39:43PM +0200, Herman Bruyninckx wrote: > > Okay. We planned to use it to make a distinction between different > > INTTRIG instructions to the same channel; more in particular, to start > > and stop a continuous pulse generator output (for the NI660x driver we are writing). So, a kind of software enable, say. [...] > The functionality you're suggesting is best handled by a > (not-yet-defined) configuration instruction. > Any idea what would be the semantics and syntax of such an instruction? Just to avoid redoing our current work in the near future... One way to provide the missing information would be to add some more detailed #defines in addition to INSN_INTTRIG. Another possibility is to use the command functionality, to configure a TRIG_INT for both starting and stopping, and then keeping tracking of how many INSN_INTTRIG instructions have been received in the device driver. But this seems to be a solution that lacks robustness... Herman -- K.U.Leuven, Mechanical Engineering, Robotics Research Group <http://people.mech.kuleuven.ac.be/~bruyninc> Tel: +32 16 322480
Received on 2003-04-30Z19:25:12