counter digital output with E-Series (DAQmx)

[gavril]

I  have read many messages indicating that DIO are software-time in the E-series (I own a 6034) however

I have got an idea that I don't see (yet) why it should not work. 

As suggested by many, I am using a counter task to generate a single pulse which I want to use as a trigger in

my application.To trigger other devices, I would however prefer using a DI0 line instead of terminal CTR0_OUT (pin 2) 

because it seems safer given the lower limits in sinking and sourcing current of the  CTR0_OUT terminal.

To obtain an hardware-timed pulse on DIO0 with my 6034E, I had the idea of using two digital ouptut tasks. The

first task would start when a RISING edge is detected on CTR0_OUT (configured with DAQmxCfgDigEdgeStartTrig),

then it would put DIO0 in the HIGH state (using DAQmxWriteDigitalLines to write a single sample), and then it would

- I assume - automatically stops. The second task would put DIO0 in the LOW state when a FALLING edge

is detected on CTR0_OUT in a similar manner.  My attempts to implement this approach have been unsucessful

but I do not understand exactly why it does not work (see code below).

Another question is what I need to add to my code so that I would get a new impulse each time

I start the counter task.

Thank you,

Gabriel

// Configure counter task

DAQmxErrChk( DAQmxCreateTask("",&mCtrTask));

DAQmxErrChk (DAQmxCreateCOPulseChanTime(

  mCtrTask,
  "Dev1/ctr0",
  "",
  DAQmx_Val_Seconds,
  DAQmx_Val_Low, //int32 idleState: DAQmx_Val_High  or DAQmx_Val_Low
  0.000,         // float64: initialdelay
  0.001,         // float64: lowtime (must be different from 0)
  hightime));    // float64: hightime

// Configure digital output tasks

long sampsPerChanWritten;
unsigned char High[1]={1};
DAQmxErrChk(DAQmxCreateTask("",&mDigOut1Task));
DAQmxErrChk(DAQmxCreateDOChan(mDigOut1Task,"Dev1/Port0/line0","",DAQmx_Val_ChanForAllLines ));

DAQmxErrChk(DAQmxWriteDigitalLines(mDigOut1Task,1,true,1,DAQmx_Val_GroupByScanNumber,

    High,&sampsPerChanWritten,NULL));

DAQmxErrChk(DAQmxCfgDigEdgeStartTrig(mDigOut1Task,"Dev1/ctr0",DAQmx_Val_Rising));

unsigned char Low[1]={0};
DAQmxErrChk( DAQmxCreateTask("",&mDigOut2Task));
DAQmxErrChk( DAQmxCreateDOChan(mDigOut2Task,"Dev1/Port0/line0","",DAQmx_Val_ChanForAllLines ));

DAQmxErrChk( DAQmxWriteDigitalLines(mDigOut1Task,1,true,1,DAQmx_Val_GroupByScanNumber,

    Low,&sampsPerChanWritten,NULL));
DAQmxErrChk( DAQmxCfgDigEdgeStartTrig(mDigOut2Task,"Dev1/ctr0", DAQmx_Val_Falling));

 

// trigger single pulse
DAQmxErrChk( DAQmxStartTask(mCtrTask));

[Kevin_Price]

The basic problem is that your backdoor workaround is also not supported by your board.  There just isn't a way to get hardware-driven timing for digital output bits on that board.  Not with a sample clock, and also not with a trigger.

Maybe you can wire your counter output to a simple external chip that'll reproduce the pulse while sourcing more current?

-Kevin P.

[gavril]

Thank you Kevin

Right now I am trying to use CTR0_OUT as a switch. The other system has a line (named sync-in)  that is usally at 3.3 V

and that I want to ground when the value on CTR0_OUT is high. To that end, I have connected VTR0_OUT to the

base of a NPN 2N2222 transitor via a 1kOhm resistance. Collector is connected to the sync-in line and emitter is connected

to the ground.

                                                                C  _ _ _ _  sync-in (3.3V)

                           | /

CTR0_OUT --- /\/\/\/\ -----|/

             1KOhm       B |\

                           | \

                            E|

                             |

                           -----

                            ---

                             -

Any other circuit suggestion about how to use CTR0_OUT either as

a switch (with a Photocoupler for example) or as a TTL trigger signal 

would be appreciated. I would appreciate resistance values and component

names if possible since I am not an electronic expert.

Also, what is the powere-on state of CTR0_OUT and what to it

once the task has been stopped?  

Best.

Message Edited by gavril on 11-01-2006 10:07 AM

[AnalogKid2DigitalMan]

gavril:

I use the HPCL-2300 high speed optocoupler quite often to isolate counter signals. Google it to find the app notes. If power on state does not match your requirements, you can use an inverter (SN7404) Attached is a screenshot of a schematic from a system that uses such. No need for U1 in your app, U2 is the aforementioned inverter, C1, R1A/B, U3 and C4 are needed. The output of U3 can be used to pull your 3.3V input low.

Good Luck

-AK2DM

Message Edited by AnalogKid2DigitalMan on 11-01-2006 09:20 AM

[BlondeGrrrl]

AnalogKid-

That's the strangest LabVIEW code I've ever seen. And what's with the green wires?

[gavril]

Thank you Analog Kid.

Another strange LabView code   that I have received. In this case, Sync-in is grounded when DAQ output goes into low state. I was told that the resistor can be as low as 1K or as high as 10K. What would be the best value if the DAQ output corresponded to the CTR0_OUT terminal (pin 2)? How does one determine this value? As usual, I appreciate any comment/suggestion. Gabriel

Message Edited by gavril on 11-02-2006 05:18 AM