Can I migrate to DAQ-MX piecemeal?

[CoastalMaineBird]

I'm looking at moving my large app to NIDAQ-MX (from Classic NI-DAQ).

I have a SCXI manager (which handles AI chores from SCXI modules).
I have a RELAY manager (which handles DO chores for a DIO board).
I have a DI manager which handles DI chores from a DIO board).
I have an AO manager which handles AO chores from the MIO board (that controls the SCXI chassis).
I have an RT manager which communicates with the RT board (having it's own program).

They are all now working on Classic NI-DAQ.
I want to move to NIDAQ-MX (the simulated devices are great !).

My question is, can I move just one manager at a time over to MX (and leave the others on Classic), or do I have to go whole hog?
In other words, can a single program talk to AI via MX, and a digital board via Classic?

[EdDickens]

It's really going to depend on how your application is written.

The first thing you'll want to do is make sure all the DAQ boards you're using are supported in DAQmx. There are several older boards that DAQmx does not, and will support.

As for the application, the main thing to keep in mind is that DAQmx and Traditional DAQ cannot access the same board. So if you're AI and AO is on the same board, you'd have to migrate those two at the same time. Likewise, since you're using a SCXI through a multifunction DAQ, as soon as you migrate the DAQ card to DAQmx, you'd also have to do the entire SCXI chassis.

There might be more, but those are the basics. It's probably best just to do the whole thing at once.

Ed

[CoastalMaineBird]

The first thing you'll want to do is make sure all the DAQ boards you're using are supported in DAQmx.

Got that covered. I'm OK there.


DAQmx and Traditional DAQ cannot access the same board.

Ah, that's the definitive answer. My AI and AO tasks are separate but access the same board. The relay driver talks to a different board. So I guess I would have to move AI and AO at the same time, and I could leave the DO task for now. Not that it's THAT dificult.

I just now resurrected a timing test program and came to the same conclusion. I migrated the AI part to MX, but left the part that used the on-board timer in Classic.

No Go.

The TASK START VI complains that the (unspecified) resource is reserved. If I remove the code that inits the timer, and then reset the classic driver, The AI task proceeds without complaint.

Thanks.