LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Trouble importing 2013 configuration file into DAQmx 2023Q3

Solved!
Go to solution

I have a program written in LabVIEW 2013 that I am upgrading to LabVIEW 2023Q3. 

I exported the DAQmx configuration from the program and I am now trying to import it into DAQmx 2023Q3 since the new computers are running Windows 11.  But I am not able to import any of the configuration files, I have tried to import using the txt, ini and NCE files.  I attached screen shots of what happens when I try to import the files using 2023Q3.  The NCE file said it was created by a newer version and the txt and ini files show no importable data.

 

I could import all the files into DAQmx 19 that I have installed on a computer running LabVIEW 2019 with no issues.  I exported the configuration from DAQmx 19 and tried to import it into the 2023Q3 version and it did not change anything, still the same errors or issues.

 

I have tried importing the configuration files on 3 different computers that have the 2023Q3 DAQmx installed.  I found some troubleshooting that said to reset the DAQmx configuration as well as a uninstall/reinstall and it did not help.  I can't imagine all 3 computers have bad DAQmx installs.  I am trying to avoid rebuilding the config file.  I am sure others have larger files, but I am thinking it is a 2023Q3 issue.

 

 

**RANT**

I did send a tech support request to NI that has been totally worthless.  After the initial response email from NI I sent all the information that was requested.  After a few days I sent an email asking for progress on the case with no response.  So today I called and the support person was actually trying to update to 2023Q3 so he could see the issues himself while I was on the phone.  He said it might take some time before the updates are finished and would get back to me.  So nothing had been done for 1 week before I called.  That and I could not understand anything because his microphone was so muffled, but I could hear his bird chirping in the background as well as a few trucks that were driving by.  I am so happy with my 2023Q3 subscription and technical support so far. 

   

0 Kudos
Message 1 of 3
(791 Views)

This is a huge stretch, but can you create a new config on the 2023Q3 version and look at the .ini file? If the structure looks the same, try modifying the values of the [DAQmx] MajorVersion and MinorVersion in your old config to match that one. I have no clue if that would work, but if you're at the point where you need to just throw stuff at a wall to see if it sticks...

0 Kudos
Message 2 of 3
(722 Views)
Solution
Accepted by topic author _Bryan

@DHerron wrote:

This is a huge stretch, but can you create a new config on the 2023Q3 version and look at the .ini file? If the structure looks the same, try modifying the values of the [DAQmx] MajorVersion and MinorVersion in your old config to match that one. I have no clue if that would work, but if you're at the point where you need to just throw stuff at a wall to see if it sticks...


Thanks for the idea.

 

I received an email from a different technical support person this morning that was much more helpful.

 

Support had me import the 2013 task into a computer running LabVIEW 2019, remove a digital out task that was used for troubleshooting and not the actual program as well as removing a simulated cDAQ device and then export it.

 

Then I was able to import the 2019 version into 2023Q3.  There were a few small differences in the text versions of the configuration files that I could see when comparing them.  But I won't know for sure until I get the new computer connected to the real equipment, but it looks like it should work.

 

I will let NI try to figure out if it was the task or simulated equipment causing the issue and hopefully fix it.

0 Kudos
Message 3 of 3
(703 Views)