Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Can't access output2 on afg320

I use the IVI driver released by NI on LabVIEW 7.1.1, XP Machine
 
I get full functionality for output1 but for some reason I get nothing but errors with output2.
Using the 'IviFgen->Channel Count' property I get the reply:  '1' !!!
 
Any idea how to fix that?
0 Kudos
Message 1 of 12
(5,245 Views)
Hi Malosh,

In MAX, under IVI Drivers expand Driver Sessions.

You should see Fgen listed. Click that and click on the Virtual Names tab. There is an add button to add a channel to Fgen (there is probably only 1 listed by default).

Once you add that channel you should be good to go.

Regards,
Matt S.

LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.
0 Kudos
Message 2 of 12
(5,226 Views)
Got 2 listed by default...
0 Kudos
Message 3 of 12
(5,222 Views)
Try using the application I'm going to send. Just run the VI I send and see if you see 2 as the channel count. This is using a simulated device, so it should go with the defaults listed in MAX. If this doesn't run without errors, then it's most likely an error in how you've installed IVI. Reinstalling IVI (the compliance package and your IVI driver) will most likely correct this if you get errors. If this runs with no problems, just let us know in a reply and we'll go from there.

Regards,
Matt S.

Message Edited by Matt_S. on 12-16-2005 05:59 PM


LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.
0 Kudos
Message 4 of 12
(5,185 Views)
Hi Matt,
Using your VI with the logical name of my AFG320 ran smoothly - returning the value '1' for the channel count.
Hope can resolve this...
0 Kudos
Message 5 of 12
(5,174 Views)
That's very strange. Some screenshots would be our next best bet. Could you either post a screenshot of NI-Spy or your actual NI-Spy capture while this is going on. A screenshot of the configuration in MAX would be helpful too. Hopefully we'll be able to help out more with that information.

Regards,
Matt S.

LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.
0 Kudos
Message 6 of 12
(5,155 Views)
Hi Matt,
  did what you asked.
Anything else I can supply?
0 Kudos
Message 7 of 12
(5,134 Views)
Hi Malosh,

This looks as though it might be a problem with how the IVI driver is reacting to MAX. Try completely uninstalling the IVI driver and the IVI compliance package. Then reinstall them. If you're still having this problem, it could possibly be a problem with the actual driver, but I didn't see the same results when I tested it here.

Regards,
Matt S.


LabVIEW Integration Engineer with experience in LabVIEW Real-Time, LabVIEW FPGA, DAQ, Machine Vision, as well as C/C++. CLAD, working on CLD and CLA.
0 Kudos
Message 8 of 12
(5,104 Views)
Thanks for all the detailed screen shots.  Very helpful to understand your setup.
 
Before you uninstall and re-install, I have a few suggestions and items to check:
 
a)  Is your logical name "AFG1" configured to link to the driver session "tkafg3x0" in MAX.  I'm guessing so, but check the obvious.  You have lots of other drivers sessions, it might be something as simple as your logical name is linked to a session with only one channel defined.
 
b)  Your "exception" error message has me concerned about your I/O Name control constant that you are using in LabVIEW.  Right click on this constant and select "IVI Class".  When you view the pull right menus, what IVI class has the check mark next to it?  It should be "IviFgen".  If it isn't, change it to "IVIFgen". 
 
d)  Is it at all possible that you might have checked the class on the Get Channel Name VI and accidently saved the VI?  On the front panel of the Get Channel Name VI, check the "IVI Class" as noted in "b" above.  It should also be "IviFgen".
 
c)  Have you tried using the IVI Class example for the IVIFgen?   You might want to start with the example and change the channel to be channel 2.
 
d)  Have you tried using channel 2 through the specific driver before using the class driver?  Again, if you installed the LabVIEW version of the AFG driver, you should have examples and VIs for the specific driver.  You can test the channel 2 in the specific driver.  First try just passing the resource name in the IVI I/O Name control (e.g., "GPIB0::17").  If that works, then pass ing the logical name "AFG1".  The specific driver should handle both the resource name and the IVI logical name.  If that works, then we know that the specific driver is OK, but something is going wrong in the class driver.
0 Kudos
Message 9 of 12
(5,094 Views)

Hi Noel,

I revalidated your comments a-c, and all looks fine.

However - I am ashamed to admit that I haven't tried "d" before. Indeed it works! by using the specific name, and also by using the logical name!

Should I reinstall or could it be a different matter?

Thanks a lot for the inputs!!!

Malosh

0 Kudos
Message 10 of 12
(5,089 Views)