Resource Name, IVI Logical Name, Driver session on MAX

Inside MAX, we can set Device Name, Logical Names, and Driver Sessions. Can I setup those on LabWindows or LabView? or you have C# wrapper to do this?

Hi Gary,
Unfortunately there is no function in LabVIEW that does any IVI setup. All of the configurations for your driver sessions and logical names need to be set in MAX, and saved. So while you can change the driver session a logical name uses, you can only do this through MAX.
Kind regards,
Sheela Sujeeun
Applications Engineer
National Instruments UK

Similar Messages

Configure IVI Logical Name to use different Driver Session programmatically

Hi,
Is it possible to change the Driver Session associated with an IVI Logical Name in Labview ?
thanks,
Gary.

Hi Gary,
Unfortunately there is no function in LabVIEW that does any IVI setup. All of the configurations for your driver sessions and logical names need to be set in MAX, and saved. So while you can change the driver session a logical name uses, you can only do this through MAX.
Kind regards,
Sheela Sujeeun
Applications Engineer
National Instruments UK

IVI logical name as Variant

Hi,
Another problem with LV 7.11:
I have a 'VI caller' that opens a VI by name or Ref, sets its controls using 'Invoke Method - Set Control Value [Variant], runs the VI and gets all display results. Worked fine up to now.
Today I ran into a problem when I was calling an IVI-based functional generator like NIs example 'IviFgen [ARB] - Generate Arb Wfm.vi'. This has a control named 'FG Device Handle' which is of the type IVI-Class.IviFGen.hp33120a and has the logical name 'FGen'. When I convert this value 'FGen' into Variant, it is represented as a numeric value, e.g. 0x05568858. If I use the string 'FGen', it is converted to '"FGen"'. Both values are NOT ACCEPTED by Set Control Value [Variant] when applied to the apropriate control of the 'IviFgen [ARB] - Generate Arb Wfm.vi'.
What can I do?
Greetings from Germany!
Uwe

Hello!
I tried to use the VI as SubVI and it worked without any exception.
To use it as top level VI called dynamically, you can simply replace the IVI Logical Name Control with a normal string control where you write the logical name.
IVIFGen initialize.vi accept also a String for the logical name.
So you can use the Set Control Value (Variant) to transfer the string to the control.
Best regards
Ken

Retrieving mapping from IVI logical name to full driver session name.

MAX, of course, lets you set up "Driver Sessions" with full names, and then "logical names" which are shortcuts to the full driver session. How can I retrieve the actual driver session that the logical name maps to? I can get the handle to the logcal name list via the IVI library, but I can't find any function that lets me retrieve further information about the logical name. Is this available in the "Configuration Server C API"?

What I want is, as I said, the mapping between the logical name and the session. This must be available, since the IVI drivers use it to go from a logical name to the attached session! One would think that it would be a single function call.
I'm doing this because in my program I can select which of a number of drivers (Newport motion controllers, in this case) a particular GUI control is attached to. The full session name is long, and there are - of course - sessions that have nothing to do with motion controllers. In the control list (a ring control) I use the logical names, which are shorter. However I want to also list the full session name elsewhere. Since I can't go from the session name to the logical name, that mapping isn't stored anywhere, I must go the other way around.
Ok, I think I figured it out. This could really be documented better!
Also, this whole thing could really be in the .ivi library configuration store section, which encapsulates a few of these calls, but not all of them.
//include section
#include <IviConfigServer.h>   //IVI configuration store
//done once at program startup. Note: this gets a copy, you don't have to dispose of ConfigStoreHandle afterwards.
static IviConfigStoreHandle ConfigStoreHandle = NULL;
Status = Ivi_GetConfigStoreHandle (&ConfigStoreHandle);
//This is the pain in the butt.
ViStatus Status;
IviLogicalNameCollectionHandle LogicalNameCollectionHandle = NULL;
IviLogicalNameHandle LogicalNameHandle = NULL;
IviSessionHandle SessionHandle;
ViChar       ControllerSessionName[MAX_Controller_Name_LEN];
ViChar       ControllerDescriptor[MAX_DESCRIPTOR_LEN];
ViChar       ControllerDescription[MAX_Controller_Name_LEN];
//get the configuration store logical name collection (what you see in MAX under "Logical Names")
Status = IviConfig_GetConfigStoreLogicalNameCollection (
    ConfigStoreHandle,
    &LogicalNameCollectionHandle);
//how many logical names are there in the collection?
Status = IviConfig_GetLogicalNameCount (
    LogicalNameCollectionHandle,
    &IVI_ItemCount);
//For each logical name, find the corresponding session name
for (i = 1; i <= IVI_ItemCount; i++) {
    Status = IviConfig_GetLogicalNameItemByIndex (
           LogicalNameCollectionHandle,
            i,
            &LogicalNameHandle);
    //get the session name for this logical name
    Status = IviConfig_GetLogicalNamePropertyViString (
           LogicalNameHandle,
            IVICONFIG_VAL_LOGICAL_NAME_NAME,
            MAX_Controller_Name_LEN,
            ControllerDescriptor);
    //get the description for this logical name
    Status = IviConfig_GetLogicalNamePropertyViString (
           LogicalNameHandle,
            IVICONFIG_VAL_LOGICAL_NAME_DESCRIPTION,
            MAX_Controller_Name_LEN,
            ControllerDescription);
    //get the handle for the ession attached to this logical name
    Status = IviConfig_GetLogicalNameSessionReference (
           LogicalNameHandle,
            &SessionHandle);
    //get the name of the session (what I really wanted in the first place)
    Status = IviConfig_GetSessionPropertyViString (
           SessionHandle,
            IVICONFIG_VAL_CONFIG_COMPONENT_NAME,
            MAX_DESCRIPTOR_LEN,
            ControllerSessionName);

IVI driver session In MAX

Hello,
I am confused with IVI drivers. I have two IVI drivers for the same instrument( one of them is newer). When I install the older one, I can see a driver session under drivers session category in MAX but when I install the new one, I do not have drivers session for the instrument in MAX. what is the problem?
Thanks,
Ela

HI,
That is Dc850W IVI-C driver. I got it from the vendor site
http://www.programmablepower.com/products/XTR/XTR_Downloads.htm
That is power supply, the older version is available in idnet, but it has some problems as well, but at least it works somehow!
Thanks,
Ela

RFC destination names and logical names

Hi,
I have an RFC connection set up in the DBCON table. Is there any way to test these connections? I tried using SM59 but I couldnt match the RFC destinations in SM59 with the connection names in DBCON?
Any help will be appriciated.
Thanks,
Praveen

Hi,
DBCON is the table for Database Connections storage. It has nothing to do with RFC connections ans so with SM59...
Regards,
Olivier

Updating Virtual Names in NISE Driver Session

I have created a Driver Session in MAX for my VXI Chassis Slot 3 cards. In this Driver Session on the "Virtual Names" tab, I am entering some virtual names that will correspond to the names on our Interface panel -- i.e. the panel of pins that the outside world sees. In other words, the default virtual name M0CH1COM may become SW1_CH1_COM -- or whatever. I plan to go and create a Virtual Device after this, and when I load the IVI switches for this driver session into the Virtual Device, I will see my virtual names in the IVI Channel column instead of the default physical names.
Suppose I have a great number of these virtual names to enter for a particular driver session, and at this point I only want to enter half of the virtual names into the Driver Session. Once I am convinced that our system is stable, then I will enter the rest of the virtual names into the Driver Session. Is there any way in NISE to get the "last half" of the virtual names from the Driver Session into the Virtual Device that I have created already? I can see where I would have built hardwires, routes, route groups, etc. in the existing Virtual Device, but I'm not sure I know of a way to get the updated Driver Session info into the existing virtual device?
A simpler case of this would be if someone just forgot to enter a virtual name or two into a driver session. They might get further down the road in development, and find that they overlooked a few virtual names. Is there any way for them to go back, enter in those new virtual names, and have the Virtual Device recognize these virtual names?
When I tried to do this -- I could not find a way to get the new virtual names to be recognized by the existing Virtual Device. The only way I found to make it work was to create a new virtual device -- and doing this will cause me to lose my "custom" info in the virtual device.
Any ideas?
Harv

Harv,
I guess this question is related to your previous post.
When you enter virtual channel names in the driver session, the IVI specific driver is supposed to pass these names to NISE. If this is the case, then NISE will show the virtual channels and not the physical channel names. The virtual channel names need to be created before importing a switch in a NISE virtual device.
If you forgot to name a few channels in the driver session and already created a NISE virtual device you will not be able to go back and give virtual channel names to the remaining channels.
Let's assume that your new driver has the exact same topology, connections, channel number etc than the old driver but some channel names are different. CH0 is now name Channel0 and CH1 is now Channel1.
What you could do is export you configuration into an xml file, open the xml file with a text editor (notepad), search for the CH0 and CH1 and replace them with Channel0 and Channel1 respectively. You also need to point to the new IVI specific driver. Now, Create a new NISE virtual device by importing the changed xml file. When you open this new NISE virtual device, it should see that the channels names (Channel0 and Channel1) correspond to the names in the new ivi specific driver and you should not have a problem using it. You would not have to redo your entire configuration.
This will work if ONLY the channel names have changed. If anything else have changed this would not work and you would have to create a new NISE virtual device.

Does mxctrllib provide a call which returns a reference to all the logical names in MAX?

I'm looking for a call that returns all the MAX logical names on a system. I would populate a drop-down box with those names to allow the user to select a name at program run-time. Currently I hard code a particular logical name as a string and init the session. This is not flexible. Thanks ...

The NiMxCtrl.dll which is the server for the mxctrllib objects is meant for National Instruments internal product use only. There is no documentation for developing 3rd party apps that utilize its functionality.
I'm not sure if you are talking about the IVI logical names listed in MAX or not, but if you want to know where you can get a list of these, they are in the ivi.ini file found in your C:\VXIpnp\Win95\niivi directory. Just parse this file to read all of your IVI logical names and setup parameters.
Jason F.
Applications Engineer
National Instruments
www.ni.com/ask

Logical Name and Physical Name of OWB Objects?

Hi,
I am using OWB 10G R1. Version: 10.0.1.0.4
I would like to know, is there any table/script to get list of physical name and logical name of OWB objects (mapping / process flow).
Any help would be appreciated greatly.
Thank you,
Regards,
Gowtham Sen.

Hi,
I only have a skript for OWB 10.2.0.3, maybe it will work with 10gR1 as well:
SELECT object_type,
       object_name,
       logical_name,
       object_path
FROM (SELECT owm_view_utilities.classified_obj_type2(f.elementid, f.classname) AS object_type,
               f.NAME AS object_name,
               f.logicalname as logical_name,
               sys_connect_by_path(f.NAME, '/') as object_path
          FROM firstclassobject_v f
         WHERE 1 = 1
        CONNECT BY f.owningfolder = PRIOR f.elementid
         START WITH f.NAME = 'MY_PROJECT')
WHERE object_type IN ('Process', 'TransformMap')
ORDER BY object_type,
          object_name
;Just replace 'MY_PROJECT' with your project name.
Regards,
Carsten.

Source System Logical Name change

Hello,
We are refreshing our R3Qas system with a copy of our R3Prd system. As part of this task our R3Qas logical name is changing from QASC230 to QASC200.
I am at the point in the refresh where I am beginning tasks on the existing BWQas system.
I Right Click on the source system representing the R3Qas system "QAS client 230" technical name: QASC230. I choose 'Restore' I then provide the logon information but the system it jumps to is the Old R3Qas not the new R3Qas.
I know that it is jumping based on the RFC, So I assume I can change that RFC to jump to the new system, what do you think? Also what about the Source System name an technical name, will it always be QAS Client 230 and QASC230 or can that be changed to reflect the new name of QASC200?
Thanks for your advice and assistance!
Nick

Since the BWQ system was already an existing system that was attached to the previous R3Q system, this task was essentially busy work.
The change that occured was that the existing R3Q system (Physical Name: QAS01 Logical Name: R3QASC230) was being replaced with a new R3Q system (A copy of Production was used) (Physical Name: QAS02 Logical Name: R3QASC200).
The actions that I needed to take to connect BWQ to the new R3Q follow:
1. On QAS02 visit TX SE37. and run RSAP_BIW_DISCONNECT, Choose 'Single Test'. For I_BIW_LOGSYS: I provided BWP001 which corresponds to the logical name of our Production BW system. For I_OLTP_LOGSYS: I provided R3PRDC200 which corresponds to the logical name of the QAS02 system (this system). I then Click 'Execute' and 10 seconds later this step is done.
2. On QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide BWP001. For the 'New Logical System Name' provide BWQ001. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the 'Mapping System Name'.
3. Again on QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide R3PRDC200. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (BASIS already did this step so a message appeared to that effect)
4. On the BWQ box visit TX: BDLS. For the 'Old Logical System Name' provide R3QASC230. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the at the prompt and run.
5. On BWQ create new RFC's based on the old ones to point at the new QAS02 system. Modify the old ones with an X in the 'Target Host' so they do not function.
6. Open up the BWQ client in SCC4. (or perhaps try SM30 to modify the table in the next step)
7. On BWQ visit TX: SE16. Tablename: RSLOGSYSDEST. Change the 'Old' reference to the QAS box to the 'New' information. (ie: R3QASC230 became R3QASC200).
8. On BWQ visit TX: WE20. Expand 'Partner Type LS', Select 'R3QASC200', click the classification tabe, change the 'Partn.Status' from I to 'A' and save.
9. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. Click 'Only Activate' when prompted. you will then get a termination message regarding the port description.
10. On BWQ Back at WE20: Expand 'Partner Type LS', Select R3QASC200, double click on RSRQST. Under 'Outbound Options' click the drop down for 'Reciever port' Select the 'new' correct system and 'Save'.
11. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. You will get a prompt to Use or Check, choose 'Use'. When prompted about 'Connection cannot be used' click 'Delete'. Logon again as ADMIN account, Click 'Continue' when you get the 'User exists...' prompt. Click 'Replicate as well' when prompted. you will then get a termination message regarding the port description.
You should be all set now!
Nick

Configuring Logical name of IVI with out using MAX tool

hi,
I need to configure the Logic name of IVI by API(IviConfigServerCAPI.dll provided by IVI) With out using the MAX tool.Can any one tell me how to use this api to configure the logical name
Regards
Parthipan

It seems you have created a new thread for the topic here. Continue in that thread please
http://forums.ni.com/ni/board/message?board.id=170&thread.id=430393&view=by_date_ascending&page=2

Can multiple Virtual Devices use the same IVI Driver Sessions?

I am using Switch Executive 2.0 and I'm having problems creating multiple Virtual Devices.
I have created a virtual device on a development computer that has no hardware connected to it. This virtual device uses specific drivers to simulate the devices. The problem I'm having is that when I create a second virtual device and try to add the same IVI Switches as the first Virtual device, I'm getting the following error:
An error has occurred while attempting to access the device deviceA_ivi.
Error -223116 occurred:
Internal Software error occurred in Switches software. Please contact National Instruments Support.
File name: .\source\mxsWrappers\tMXSObject.cpp
Line Number 192:
Status Code: -223116
Can someone please explain why?

Can you please elaborate on how did you create those simulated devices? Namely, what does your IVI configuration look like? What does the driver session for the logical name look like? What's the software module? What's the hardware module? What is the driver setup string, and what is the simulation mode for the device in question?
-Serge
Srdan Zirojevic

Logical names lost after database corruption removal

Hi,
I am working on a PXI based project using NI 5663 and NI 5673. The MAX database in system got corrupted recently due to power cut.
I did a database corruption removal and the only issue I face now is that there are no logical names for the devices. I am following the steps from the site below to create the same –
http://www.ni.com/white-paper/4594/en
But after I create a new logical name say for the LO 5652 (associated with 5663), I do not know which driver session to associate with it.
There are driver sessions for niFGen, ni5450 in the list but no session for 5663 or 5673.
Could someone please help me out with creating logical names and associating them to the devices?
Thanks so much,
Sharmi

Hello,
To configure your 5663, you can refer to the RF Vector Signal Analyizer Getting Started Guide pages 37 - 39.
You should open Measurement & Automation Explorer and rename the devices such as VSA_LO, VSA_DC, VSA_DIG for the local oscillator, downconverter and digitzer respectively. Next you will need to associate the downconverter with the local oscillator and digitizer by right clicking the downconverter and selecting properties
To configure the 5673 the steps will be fairly identical, rename the devices if you wish and then associate the upconverter (IQ Vector Modulator) with the arbitrary waveform generator and the local oscillator. You can also refer to the RF Signal Generator Getting Started Guide on pages 23 - 24.
Which programming language are you using the VSA and VSG with? You normally wouldn't need to configure any IVI sessions the the devices. The only configuration normally is just associating the upconverter or downconverting with the LO or digitizer/AWG module.
Anthony F.
Product Marketing Engineer
National Instruments

Finding a logical name for PXI5112 modules to be used in niScope_Init

I need to dynamically allocate the number of PXI5112 modules on several PCs in a C++ program. After going through great length using VISA calls to obtain the VISA logical name ( PXI3::11::INSTR, etc.), I found out that niScope_Init is expecting an IVI or DAQ logical names. How does one go about to get the logical name for those PXI modules so niScope_Init can use? Hardcoding the name such as DAQ::1 is out of the question because the number of modules is different from test to test. Thanks.
Software:
niScope driver: 2.6
Microsoft Visual studio.net 2003
Measurement Studio 7.0
Windows XP SP2
Hardware:
Group1 : 5 PXI5112s
group2 : 3 PXI5112s
group3 : 7 PXI5112s

Here's a quick and dirty example of how to use the niModInst API in C:
ViSession sessionHandle = VI_NULL;
ViInt32 numberOfDevices = 0,
i = 0;
ViChar deviceNameBuffer[256] = "";
niModInst_OpenInstalledDevicesSession(
"niScope",
&sessionHandle,
&numberOfDevices);
for (i=0; i < numberOfDevices; i++) {
niModInst_GetInstalledDeviceAttributeViString(
sessionHandle,
i,
NIMODINST_ATTR_DEVICE_NAME,
256,
deviceNameBuffer);
printf("%s\n", deviceNameBuffer);
niModInst_CloseInstalledDevicesSession(sessionHandle);
The device names that you're printing out in this example can be used as the resourceName input to the niScope_init function.
In practice, though, be sure to check the status that is returned from each function. You can get further information about an error using the niModInst_GetExtendedErrorInfo function. All the functions I used above can be found in the niModInst.h file.
Hope that provides some more help.

Fetch a resource attribute using Last name

Hi All,
I need to fetch a resource attribute 'employeeID' from AD, all I know is only Last Name (I don't know the accountId). How can I acheive this?
Is it possible through EXPRESS or do I need to write a java program.
Please share your ideas.
Thanks in advance

It is possible (with XPRESS) but the search criteria of Last Name will result in lots of erroneous matches. If at all possible, find additional or alternative search criteria to narrow down the field.
Here's some example code for retrieving results from an Active Directory resource. It was written to be used in the Form context (changes would be required if you were executing from a Workflow context).
              <defvar name='results'>
                <invoke name='getResourceObjects' class='com.waveset.ui.FormUtil'>
                  <ref>:display.session</ref>
                  <s>person</s>
                  <s>Active Directory Resource Adapter</s>
                  <map>
                    <s>searchContext</s>
                    <ref>baseDN</ref>
                    <s>searchAttrsToGet</s>
                    <List>
                      <String>cn</String>
                    </List>
                    <s>searchFilter</s>
                    <concat>
                      <s>(sn=</s>
                      <ref>lastnameValue</ref>
                      <s>)</s>
                    </concat>
                    <s>searchScope</s>
                    <s>oneLevel</s>
                  </map>
                </invoke>
              </defvar>baseDN specifies where in the AD tree to start searching (e.g. "cn=Users,dc=Acme,dc=com")
lastnameValue is the lastname you're searching on (e.g. "Smith")
results will be a List of the cn attributes that came back from the search (specified in the List under searchAttrsToGet). You need to put logic around the results to handle the List appropriately.
Use standard LDAP-style search filters in the searchFilter section if you need to add additional qualifiers.
Jason

Resource Name, IVI Logical Name, Driver session on MAX

Similar Messages

Maybe you are looking for