Analog input and Digital output at the same time, NI USB 6003

[Houshmandyar]

Hello,

I have a YIG filter that its center frequency is determined by 12-bit digital signal. I need to find out the changing frequency response time. My plan is to acquire data from the YIG's output (after connection to a diode) while changing its bit signal.

I have two NI-USB 6003 devices in hand. I understand that this device is not an SIO and cannot do AI and DO at the same time: start acquiring analog input while changing the digital output, and then end acquisition. Has anyone had this experience with USB devices before? Does dedicating one device to AI and theater to DO help?  Naively, how about using two different computers and devices, one for AI and the there for DO, and use one for the other's trigger?

Thanks

Saeid

[Bob_Schor]

---

@Houshmandyar wrote:

Hello,

I have a YIG filter that its center frequency is determined by 12-bit digital signal. I need to find out the changing frequency response time. My plan is to acquire data from the YIG's output (after connection to a diode) while changing its bit signal.

I have two NI-USB 6003 devices in hand. I understand that this device is not an SIO and cannot do AI and DO at the same time: start acquiring analog input while changing the digital output, and then end acquisition. Has anyone had this experience with USB devices before? Does dedicating one device to AI and theater to DO help?  Naively, how about using two different computers and devices, one for AI and the there for DO, and use one for the other's trigger?

---

Whew!  I've got a USB-6009 and a USB-6002 ("cousins" of the 6003), so it's a good thing I didn't know you can't do AI and DO at the same time, since that's what I'm doing.

The question really is what are the tasks you are trying to do.  I'm assuming you are sampling an analog signal at some reasonable rate, say 1KHz, maybe 1000 points at a time, but it is not clear what the timing issues are for the DO task.  Mine are fairly slow (as in "Make it go High when I push this button on the Front Panel") and are of the "on demand" nature -- there's no problem doing this (with a single USB-600x device).

Can you say a bit more about your AI and DO tasks?  I know you are talking about a 12-bit DO (I think my devices have that many ports) -- say more about the timing.

Bob Schor

[Houshmandyar]

Bob,

As I understand, NI 6003 does the tasks as it blocks others, meaning that two tasks cannot be done at the same time: data sampling is done before the device get the chance to do digital waveform. I have monitored my code and verified that simultaneous AI/DO is not being done. My case is fast changing the digital signal fast. Can you share your code as you say you are already doing it?

[GerdW]

Hi Houshmandyar,

I have monitored my code and verified that simultaneous AI/DO is not being done.

Can you share your code? Please attach a VI, not just an image…

My case is fast changing the digital signal fast.

The NI6003 supports hardware-timed DO: do you use this? (Well, if you would attach your VI we could answer that by our own.)

[Houshmandyar]

Hello,

I have attached my VI. I have also attached the result of a run: I have connected a 1 Hz signal from a signal generator to the AI, just to monitor. As you can see there is a gap between AI and DO, as it is expected that NI 6003 blocks other tasks before finishing one task. The gap is the 100 ms wait, but I want the acquisition continue, even through the wait. This means that not only the analog read stops during the wait, but also it stops before digital write would start. Since changing the digital word affect the analog input, I need to find the time response of this change from the YIG filter. Any suggestion?

[Bob_Schor]

I don't see a Task wired to the DO set of VIs.  Among other things, this means that the timing and other asepcts of the Task are "ill-defined" (they aren't, strictly speaking, un-defined, as they have some default values, but who knows what those are ...).

You do not need a Sequence/Frame structure -- it only clutters up your Block Diagram (you seem to be properly using the Error Line(s) to sequence your operations, as well as LabVIEW's Principle of Data Flow).

There appears to be a computation in the first Frame of AI Acquisition Time (Samples to Read / (2*Sampling Rate)) that goes nowhere and is unused, a curiosity that would have been obvious and "removed" without the Frame.

Bob Schor