Digital I/O

cancel
Showing results for 
Search instead for 
Did you mean: 

Synchronized I/O with DIO-32HS and DAQmx

I am using LabVIEW 7.1.1 and a DIO-32HS w/ SCB-68 (connection reference label P/N 185754B-01).  I am trying to communicate with the Serial Control Interface of a custom ASIC.  I need to generate an internal clock for the data in & out of the chip (see attached timing diagram).  I have much LabVIEW experience, but am not a frequent user of I/O cards or DAQmx.  I'm unable to produce the desired results and the problems are related to having the external clock for the output available at the SCB terminals while also used as the clock for the input.
 
The attached VIs are two versions of the same basic code with slightly different setups.
The HW setup for ASIC SCI_2.vi only has a connection between P0.2 & P2.0 to loopback a signal for testing the code.
The HW setup for ASIC SCI_3.vi adds another connection between PFI 4 and PFI 5 intended to loopback the clock.
 
Thanks for any suggestions on how to correct my problem.
 
James
 
PS.  To run the VI, just delete the case with the missing VI, there is default data in the false case.
LabVIEW 5.0 seems so long ago...
Download All
0 Kudos
Message 1 of 5
(3,011 Views)
Hello jrjones,

You'll want to put a DAQmx Wait Until Done VI between starting your Task and Clearing it, this will wait for the generation to end before clearing the task, otherwise it will clear immediately after starting.  You might want to take a look at the example programs: Handshaking Output Waveforms-8255 VI and Handshaking Input Waveforms or the Cont Handshaking Input/Output -82550Nin-Buffered shipping examples as you get started.

Post again if you have further questions!
Regards,
Micaela N
National Instruments
0 Kudos
Message 2 of 5
(2,997 Views)

Micaela,

The problem I have is NOT related to a need for a WAIT.  I can view the signals show on my graphs with an o-scope on the SCB-68 terminals.  The problem is related to creating a sample clock that is available at the terminals (to connect to my hardware) and used internally as the sample clock for the DAQmx Read function.  The two VIs show illustrate the problem, on one the clock is available externally and the other internally.  How can I make it work for both an external burst clock and an internal sample clock for the the read?

Thanks in advance for additional suggestions,

James

LabVIEW 5.0 seems so long ago...
0 Kudos
Message 3 of 5
(2,982 Views)
Hi James,

I read that wrong - I must have written that during an afternoon lowl.  I think I see what you are asking now, with the burst mode timing you have to configure both the Pause Trigger Polarity (Pause When) level and the Ready for Transfer Event Active Level.  The Pause Trigger pauses an ongoing acquisition or generation and the Ready for Transfer Event signals that the device is ready for transfer (data is on the lines or space is available in the device FIFO).  You will also need to configure the Input Task Pause Trigger Source and the DAQmx Ready for Transfer Event Output Terminal Source.  To configure the Pause Trigger Source is configured through the DAQmx Trigger Property Node >> More >> Pause >> Digital Level >> Source and the Ready for Transfer Event is configured through the DAQmx Export Signal >> Events >> Ready for Transfer Event >> Output Terminal. 

I found an example of Bidirection Burst Mode I/O in DAQmx on two computers, while I know that you are not doing exactly this, I thought the code showed how to configure the Trigger and Event sources and levels clearly. 

Let me know if you are still having trouble after setting the sources and the levels of the Pause Trigger and the Ready for Transfer Event.

Regards,
Micaela N
National Instruments
0 Kudos
Message 4 of 5
(2,955 Views)

Problem Solved...

Just in case someone reads this thread in the future with a similar problem.  I hate it when I find an old thread that matches my problem and the solution isn't shared.  So here's my VI that solved my particular problem, maybe it will help someone else.

James

 

LabVIEW 5.0 seems so long ago...
0 Kudos
Message 5 of 5
(2,919 Views)