3499 with 44470A and 44471A

[husni h]

Hi,

I'm trying to configure a 3499A (5 slots) with the following cards (slot1 and 2: 44470A, slot 3: 44471A) in MAX. The examples provided in the driver help file only shows how to add 1 card e.g. fill the Driver Setup box with "slot1:44470A". How do I add in information about slot 2 and slot 3?

Anyhow, I tried to add the SCU into Switch Executive 2.1 and I'm able to see the channels 1CH00..1CH09. So, the other cards are not automatically detected.

And if I am able to add the card information of slot 2 and 3, do I need to redo the configuration in Switch Executive?

Thanks for the help.

Regards,

husni h

[Srđan_Zirojević]

In the documentation of the driver (ag3499x notes.pdf) I found the following:

To specify multiple slots, you should separate the slot configuration with a semicolon:

"DriverSetup=slot1:N2260A:2;slot2:N2260A:2D"

So, if you have multiple modules, you'll need to change your driver setup to reflect this.

Once you're done, you will have to recreate your switch executive virtual device, as it learns about available channels at the creation time and cannot be changed at a later point.

If you are using NISE 2.1, and if you have already created enough of a configuration that you don't want to lose, you may export the current configuration to excel spreadsheet, then delete it in max, recreate it using the same device (with updated driver setup) and overwrite the configured hardwires, routes, etc. by using the excel->NISE import example.

Hope this helps!

Message Edited by Srđan Zirojević on 10-12-2006 11:29 AM

[husni h]

Hi,

Thanks. The NISE is now able to see all the cards. I have a few questions regarding how to configure the NISE. Attached is the connection requirements.

I've created a simple configuration
V1    :1CH00
DMM:1COM

Then I created a route V1_DMM: [V1->DMM]

When I tried to use the Test panel to verify the connection, there's no error but the 3499 did not respond. I verified the GPIB connection using MAX to communicate with the instrument by sending the SCPI command "CLOS (@100)" and the 3499 closed 1CH00. How can I check that the correct commands are being sent to the 3499? NI-Spy does not log the actual SCPI commands.

Another question is how do I control the relays (44471A)? Can I still use the niSE connect vi?

Thanks again.

Regards,
husni h

[Neil_S.]

husni h,

Thanks for posting to the NI forums.  This issue sounds rather perplexing.  What do you see in NI-Spy when you run it while using the test panel?  Do you at least see the Switch Executive commands?  You may want to make sure NI-Spy is configured to log every type of call.  You can change these options in Spy >> Options under the View Selection tab.  Would it be possible for you to attach the spy file to your next post so I can take a look at it?

Thanks,

Neil S.
Applications Engineer
National Instruments

Message Edited by Neil S. on 10-13-2006 09:06 AM

[_Brian_]

husni h,

NI Spy may not show calls if you are configured to use a simulated session. To communicate with real hardware, please check that your IVI Driver Session is configured as Simulate With: Don't Simulate and that you have a valid Hardware Asset and Resource Descriptor listed.

The 44471A should work as Srdan suggested:
"DriverSetup=slot1:44470A;slot2:44470A;slot3:44471A"

The 44471A's channels in Switch Executive will be 1CH00L,1CH00H,1CH01L,1CH01H,...,1CH09L,1CH09H

You can use niSE connect vi on these.

Here is a link with some more configuration info:
http://forums.ni.com/attachments/ni/140/8542/2/doc.pdf

Brian

[husni h]

Neil S.,

Attached is the NI-Spy log. I do see the Switch Executive commands but there's no response from the SCU.

Regards,
husni h

[Srđan_Zirojević]

Husni,

did you enable spying on all relevant APIs in NI Spy>>Options? Can you please verify that you have NI-IVISwitch and NI-VISA selected besides the Switch Executive in the NI Spy options dialog. I believe that you did not have those options selected as I cannot see any IviSwtch calls and there should be some since your call to FindRoute correctly completed a route.

Simulating or not, the IviSwtch calls should be logged. Even if you do not see them on your spy screen, those calls are logged to the file and we can analyze the file here, so please just make sure that you've selected needed APIs (the safest: selection is ALL APIs) and re-log the actions to the file. Please repost the file here. Then we will be able to see what's going on.

-Serge

[husni h]

Hi,

When I run Spy there's an error prompt "Unable to locate LabView API". The screen capture is SpyError.jpg. After that Spy still opens. When I checked the Spy->Options the LabView API choice is not checked. Screen capture is SpyOption.jpg. I've tried to repair the installation of various installations but the error still comes up.

I already have the NI-IVISwitch and NI-VISA selected.

Regards,
husni h

[Srđan_Zirojević]

It is OK not to be able to spy on LabVIEW API - we are not interested in that. NI Switch Executive, NI IVI Switch and NI VISA is what we want to see.
From your original spy file I could not see any visa or ivi switch calls. Can you try producing another spy file while making sure that all three options were selected?
thanks!

-Serge

[husni h]

I've uninstalled all the NI applications and reinstalled them back. Now the SCU is working fine. Anyhow, attached is the NI-SPY capture with all the options selected. I managed to fix the NI-SPY missing API by installing NI-VISA 4.0.

Regards,
husni h