Labview craches when using ag3499x Initialize.vi

[lcooney]

I am using IVI for the first time. The reason, I need to control an AG3499B switch from Labview. I downloaded the latest AG3499x instrument driver and IVI engine (ver 1.83) from the Labview website. I am using Labview 6.0.2 on a Windows95 machine.
The problem is that as soon as I try to run the 'AG3499x Initialize.vi' Labview crashes. I don't know if it is the instrument driver, IVI, Labview or me that is at fault.
One thing seems odd to me in the 'AG3499x Initialize.vi' diagram. A local variable of the 'instrument handle' indicator is wired to both the 'IVI new session' sub-vi and the 'Call library function' sub-vi before it is assigned a value. Other instrument drivers I have used (non IVI) do not do this
.

Any ideas???

TIA

Liam Cooney,
Senior Evaluation Engineer,
Parthus Technologies.

[btejani]

Liam,

The difference in the VI is not an issue, as this is done for all IVI drivers.

Please describe more about your 3499 setup. What modules do you have installed? Different modules require different initialization, so it would be helpful in isolating what's happening.

Due to the re-configurable nature of the instrument, I suggest using InitializeWithOptions, as it will allow you to specify which exact modules are installed. This is important since some of them return ambiguous identification. For example, 44470A and 44470D both return '44470' as their identification, so the driver is unable to determine which one you have, unless you specify it. The control help in InitializeWithOptions explains the syntax needed.

Thanks,

Bankim Tejani
Sof
tware Engineer
National Instruments

[lcooney]

Bankim,

Thanks for your reply.

My setup consists of a 3499B fitted with N2260A MUX module in slot 1, GPIB Address 9.

I have found the same problem using 'ag3499x Initialize With Options' as suggested, with the option string 'Simulate=0,RangeCheck=1,QueryInstrStatus=1,Cache=1,DriverSetUp=slot1:N2260A:1'.

I have narrowed the problem down to the first call to 'ag3499x_error_message' within the 'ag3499x IVI Error Convertor' sub vi, see attached screenshots.

I hope this extra detail helps.

Regards, Liam Cooney.

[btejani]

Liam,

We have found and fixed the bug that caused your crashes. We are very sorry for the delay in reproducing the issue.

An updated version of the driver has been release to the IDNet website: http://www.ni.com/idnet/

Thanks,
--Bankim