PXI - DAQmx tasks will not export to MAX 5.4

[Rich_G]

I am in the process of upgrading a PXI 1050 with an 8176 to an MXI bridge. The latest headache is that the CVI program had several DAQmx (tasks) defined in MAX 3.1.1 which will not export to MAX 5.4. I have been posting these additional questions on my original thread MXI not visible in MAX. I have many tasks for installed PXI cards. I was trying to make simple tasks just defining these cards to change the errors I receive in CVI. I do not have the option to define a task for some of these cards like the 4070 DMM. I did not generate the original CVI code. I am not sure what is defined the DAQmx. Can someone provide some insight ? I have viewed the suggested videos and white paper links. They were instructive but of little help.

[PatJamSim]

Hello Rich,

I noticed that you were working with one of our engineers on an ongoing service request regarding this issue, so I will let him handle it and post the resolution on this forum for anyone who runs across this forum post and has the same issue.  

I certainly encourage any other forum-goers who have input to provide it here.  

Thanks!

[Rich_G]

Can anyone please tell me how to achieve the Convert Traditional NI-DAQ (legacy) configuration to NI-DAQmx... In the newer MAX 5.4 ?

[PatJamSim]

Hello Rich, 

I was able to find that the latest version of NI MAX that should do the conversion is MAX 4.2.  This is also the last version that was provided with the Traditional DAQ 7.4.4 drivers, hence the option being available there and not in the newer versions of MAX.

To get MAX 4.2, you will either need to install TDAQ 7.4.4 or DAQmx 8.5 on a machine that does not currently have MAX.  A virtual machine should be sufficient for this task.  After doing so, you should be able to convert using the option showing in the screen shot you attached.  Did you take those screen shots yourself?  Do you already have MAX 4.2 installed?

In the current version of MAX, there is a similar option under Tools » Traditional NI-DAQ Configuration » Save Configuration As...  Are you able to save your configuration into a more useful file type from this menu?

[Rich_G]

The screen shots are either 3.1.1 or 5.4.  and yes I have taken them myself. I find the old adage to be true. A picture IS worth a thousand words.  I am able to save the configuration of 5.4 and restore it. I found this out when I attempted to import the 3.1.1 configuration export. Just guessing about this, I believe that the 3.1.1 DAQmx defines, like the DMM, will not port to 5.4 because there is no option for this. Which pushes the import into a death spiral which causes the whole import process to go into an invalid state. This in turn requires Task Manager intervention.   I have gotten word from the team that created the software on this test unit. They had subcontracted some of the function calls between the NI-PXI rack and CVI. They call them tool boxes. They also used the option to create a DAQmx define for all legacy PXI devices. I do not believe all of them are used. But it was helpful to understand the software better. There are a mixture of DAQmx task routines in the CVI code and a Traditional device tool box used for most all the remaining devices. And every one of them turning up errors for them not working. I need to find what connection broke between the old CVI 7 and the new CVI 10. I need CVI 10 because I an jumping from Win 2000 to Win 7(32)

[PatJamSim]

Hello Rich,

Have you tried converting from 3.1.1 to 4.2, and then attempting to import to 5.4?  I think using the intermediate version will greatly increase the chances of being able to successfully convert your tasks into the new version of MAX.

Is there potentially a way for you to get your associates to upgrade the so-called tool boxes in the new versions?

I am sorry you have had such troubles getting everything imported into the newest versions, and hope that you are able to do so successfully here in the near future.

[Rich_G]

Unfortunately; no updates without dollars. While we all work for the same company, we must contract work between departments. There was no defect with the software as delivered. Old age crept in to the hardware. Any upgraded hardware, it turns out,  requires updating of the software. The unit had operated reasonably well, until a couple years ago. An unfortunate selection of network security software caused massive headaches. The software chosen assumed a more advanced level of hardware. Mandatory installation on all network computers rendered these controller inoperable. Our local IT guys shaved down the install to minimal components but the controller lost all available ram to this software, NI-MAX requires 20 minutes to build it's database on reboot. The computer controllers struggle to function. They periodically get lost and require a reboot, causing 30 minutes or more to restart. This is driving a replacement. We decided that it would be more cost effective to move to a standard computer interface. With the MXI, we could have a much more friendly and versatile interface. The upgrade is with a different "color" of corporate money. There isn't enough funding to contract a software upgrade. It is feasible to complete the upgrade in house, once we can identify the players and their function. Second we need the necessary time and access to the equipment. I do not have the ability to expend too many extra hours at work. So it takes time. I have been able to piece together the following. In the development stage back in 2004 - 2005, the developers used both Traditional DAQ and DAQmx. They build tasks for the SCXI in CVI. They have toolboxes making calls to Traditional DAQ. Also at some point in time they must have used the option in 3.1.1 to Convert Traditional NI-DAQ(Legacy)Configuration to NI-DAQmx, which built all the extra DAQmx devices we see in the device tree in the MAX 3.1.1. So beyound the errors there appears to be a few red herrings, just for fun. So there is no tasks to convert from 3.1.1, everything is contained in the CVI code. I have to find a way to use the CVI debugger to lead me to the nested, buried code causing the errors, and simply correct them. Just for another layer of complexity, they are probably logic errors, not syntax errors, or updated code errors where the legacy code no longer functions with the updated drivers. Or, hey, it could be the beta version of NI-DAQ, because it is the only one working with Windows 7 (32).