LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to import the "NI configuration Export file" (.nce) through Labview programatically?

Hi,
 
Is it possible to import the "NI configuration Export file" (.nce) through Labview programatically?
 
Guru
Regards
Guru (CLA)
0 Kudos
Message 1 of 10
(4,071 Views)
hello,

Yes, this functionality is available with LabVIEW 8.0 or 8.2 and the MAX 4.1
The function is called "MAX Copy Configuration.vi"

For more info about this function, have a look to the KB:
Import and Export a MAX Configuration through LabVIEW

Have a nice day
Nick_CH
Message 2 of 10
(4,065 Views)

Excellent Nick.. Thanks for the info.. I have not yet excxplored LV 8 much...

Regards

Guru

Regards
Guru (CLA)
0 Kudos
Message 3 of 10
(4,053 Views)
I get this every time I run the max copy configuration.vi. Anybody seen this error before?

Error -2147467259 occurred at MAX Copy Configuration.vi

Possible reason(s):

LabVIEW:  (Hex 0x80004005) Unspecified error.




0 Kudos
Message 4 of 10
(3,840 Views)

Hi tsksesa,

 

There seem to be multiple different possibilities for the source of this error, so try to narrow down what is causing the problem. What are using for your source and destination inputs, and do you get this error no matter what these values are? What product types are you copying? Try to copy a different MAX configuration file, and create a simple VI that only executes this function.

 

Also, it is easier to keep track of issues and get you answers if you post separate new questions in new forum posts.

 

Regards,

Stephen S.

National Instruments
Applications Engineering
0 Kudos
Message 5 of 10
(3,813 Views)

Source: system://192.168.1.56 (a real time computer)  destination: c:\max.ini , product: daqmx. 

 

With the upgrade to LV 8.6 the error has stopped but a new bug has shown up.  If I make a change in the RT systems setup the max.ini that is created will contain nothing but the header

 

[DAQmx]

MajorVersion=8

MinorVersion=8

 

 The rest of the file being blank.  But if I reboot my machine (not the target system) it will then make a good .ini file.  I am currently running this in a stand alone vi until I can get it working consistently. 

0 Kudos
Message 6 of 10
(3,800 Views)

Hi tsksesa,

 

Are you running DAQmx 8.8 or 8.7?  If not, upgrade and see if you get the same problem.

Stephen S.
National Instruments
1 Test is worth 1000 expert opinions
0 Kudos
Message 7 of 10
(3,780 Views)
I upgraded with no effect.  Also I have tried using this vi on the RT side and it crashes the RT every time, I have been using the home ip as the target, any suggestions on that? 
0 Kudos
Message 8 of 10
(3,751 Views)
Try takng the RT system out of the equation and just get it to work on your host PC.  So just try to export the MAX config file on your computer to a file that you can open and view.  Once this is working we can add the complexity of the RT. 
Stephen S.
National Instruments
1 Test is worth 1000 expert opinions
0 Kudos
Message 9 of 10
(3,728 Views)
I have moved the Get Max config to the host side its target is set to the source to "system://192.168.1.56" the RT's remote ip addresse, the destanation to a local file path "c:\...\max.ini"  and the product to "daqmx".  Now the export will work but if you change any settings in max you not only have to reboot the RT but you have to reboot the host to get the export to work.  If you try to export it will either crash ( go into a loop where it sets the RT's cpu load to 80% and hangs there or it will simply return a blank "max.ini" as I said before, 3rd quarter 2008 LV, max and daqmx. 
0 Kudos
Message 10 of 10
(3,714 Views)