Where is the data held in Max 3.0

[RayFarmer]

Hi,

Not sure if this right place to post this but as MAX 3.0 was installed with labVIEW 7.0.....here goes..

With Max 2.0, the data assoicated for GPIB, VISA and IVI was held in two places, IVI.INI and VISACONF.INI.
Now Max 3.0 arrives, so where has the data gone. There still is an ivi.ini but it doesn't contain all the data. Visaconf.ini still seeems to be the same.

I can still see most of the settings for drivers, logical names etc when I launch MAX 3.0, that used to be in my old ivi.ini file. So where does it store them now.
Also, what has happened to the default settings that used to be defined for a logical name?

Looking, in the MAX folder there are a load of LV VI's in the MAX\Assistants\LVCGen, what are these used for
.

I have looked, at the Max help but its a bit vague.

Can anyone shed some light.
Regards
Ray Farmer

[gagi1]

Hello Ray,

With installation of LabVIEW 7.0, you have also installed MAX 3.0 and IVI Compliance Package 2.0. The IVI Compliance Package (ICP) 2.0 is a software package that contains IVI class drivers and the support libraries necessary for the development and use of applications that leverage IVI instrument interchangeability. The IVI Compliance Package also is based on and is compliant with the latest version of the instrument programming specifications defined by the IVI Foundation.

One of the most prominent changes between previous IVI products and the IVI Compliance Package is the way that the IVI Engine, IVI MAX configuration utility, and other IVI products included in the IVI Compliance Package access and store configuration information. The Configuration Server provides
a database for storing configuration data and an API for accessing this data.
This database is called the Master Configuration Store. Various IVI products have been redesigned to work with the Configuration Server instead of the previous method, which involved using the ivi.ini file.

If you have any configuration information stored in the ivi.ini file, the installer converts the existing ivi.ini data into a new format that is used by the Configuration Server and stored in the Master Configuration Store file (IviConfigurationStore.xml). This conversion process, which takes place when you install the IVI Compliance Package, removes the converted items from the original ivi.ini file as it places them in the Master Configuration Store database.
The installer also creates a backup copy of the ivi.ini in the same directory as the original ivi.ini.
If, after you install the IVI Compliance Package, you run an older specific instrument driver installer that adds entries to the ivi.ini file, you can convert the newly installed configuration data by running MAX, which monitors the ivi.ini file for changes. If MAX detects any changes, it launches a conversion utility automatically before loading the configuration from the Master Configuration Store file. Also, you can run the converter utility manually by selecting Start�Programs�IVI�Tools�INI to XML Converter.

There are a few KnowledgeBase entries on ni.com on this topic:

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/b83c7bbd43fd855486256cd10077ef06?OpenDocument

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/72f3656387deaefa86256d180062862c?OpenDocument

http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/33b3f3ea0f305a3386256d170064f02d?OpenDocument

You can also find more information in the ICP Release Notes.

I hope this helps.

Regards,

Vesna Jadric
Instrument Drivers/IVI

[RayFarmer]

Hi gagi1,

Thanks for the response.

Configurable Initial Settings have taken over from the old Default Settings. How does one go about defining Configurable Initial Settings. Is it something you place in the registry for a driver?

Regards
Ray Farmer

[gagi1]

Hi Ray,

You are correct. The Default Setup data has been replaced by Configurable Initial Settings. Because the Configurable Initial Settings are selected by the software module developer, and are recognized by the software module during initialization, Configurable Initial Settings are only added by the software module when it is installed. Using Configurable Initial Settings is more restrictive than using the Default Setup. The set of attributes available to your driver sessions in the Configurable Initial Settings is restricted to what is published by the driver developer in the software module entry for that driver. You can edit the value of these attributes for your driver session but you cannot add additional attributes to this list of Configu
rable Initial Settings.

If you need attributes that are not available in the Configurable Initial Settings list, National Instruments recommends that you contact the specific driver supplier.

I hope this makes sense.

Best Regards,

Vesna Jadric
Instrument Drivers/IVI

[RayFarmer]

Hi,

Since I started looking into what's different with MAX 3.0.
I must have done something to my system because I am getting an error when my PC first boots up. Also when I launch NIMax.

I have attached a bitmap of the error dialog.

I have tried doing a repair via the Add/Remove Programs but I am still getting this error.

Any clues as to the cause.
Regards
Ray Farmer

[gagi1]

I do not believe this problem is caused by doing anything within the IVI Configuration utility. You should even be able to use the IVI Drivers category in MAX after getting this error.

Have you installed or uninstalled any NI software components recently? Have you ever had any beta versions of NI software?

Thanks,
Vesna

[RayFarmer]

Hi,

This has only just happened.
The only item I can selected is the IVI and all the lower level items. All the other item such as Software, Drivers causes this error.

The only item I have installed or uninstalled is the MAX, and that was the repair option.

Yes I have had the TestStand beta 3.0, but that has been uninstalled along with all items components weeks ago.


I did launch the LabVIEW Assist application.
I have reconverted my old ivi.ini file.

This has got to be related to the MAX utility, its performing some action, or looking for something that it believes is on my system.

Regards
Ray Farmer

[gagi1]

Ray,

The MAX team here at NI suggested a couple of things to do:

1. Find the directory where MAX is installed. Usually, this is c:\program files\national instruments\max\, but you may have installed it somewhere else. If you do not know where it is installed, search your drive(s) for a file named "nimax.exe". You will find it in the MAX directory. Go to the MAX directory in a command window and type "dir /s" and send us the output. This may provide some insight if some beta leftovers remain on the system.

2. Then rename the Data directory within the MAX directory to something like "DataBackup" and reboot and start MAX to see if the problem still happens. Caution: this action will result in the loss of
NI-DAQmx, NI-Motion, NI-CAN, and VI Logger configuration already performed within MAX.

Did anything else precede this problem starting to happen?

Thanks,
Vesna

[RayFarmer]

Hi,

I did the 2. first and that has stop the errors when I boot up. I have not been in to Max yet.

I have attached a txt file after doing the 1.

Regards
Ray Farmer