Why i can't connect with an instrument using ivi com driver?

5 次查看（过去 30 天）

Vijith Natarajan 2012-12-11

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/56250-why-i-can-t-connect-with-an-instrument-using-ivi-com-driver

Hi, I created and device object using both drivers(ivi c and ivi com). when i try to connect the instrument using ivi c driver's device object i can connect with the instrument . but when i try to connect the instrument with ivi com driver's device object.

Please explain why and also the difference between ivi c and ivi com.

Thanks in advance Vijith

10 个评论
显示 8更早的评论隐藏 8更早的评论

Walter Roberson 2012-12-27

And are you using the 32 bit or 64 bit MATLAB?

Vijith Natarajan 2012-12-27

32 bit matlab

请先登录，再进行评论。

请先登录，再回答此问题。

回答（1 个）

Ankit Desai 2013-2-12

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/56250-why-i-can-t-connect-with-an-instrument-using-ivi-com-driver#answer_74815

在 MATLAB Online 中打开

IVI-COM is not supported on 64-bit platform. However, if the driver installs both the 32 as well as 64 bit, then you should be able to use the 32-bit driver from 32-bit MATLAB.

The difference between the IVI-C and IVI-COM is explained by pacificmindworks.com in this PDF document.

I installed version 1.1.8 of the IVI driver for the instrument you listed. That driver comes along with MATLAB driver and is automatically installed. You might want to update your driver if it is not the latest one.

There is also an example that is shipped with the driver that shows how to use the driver, once installed. Here's a sample code:

    % Create driver instance
    driver = instrument.driver.AgInfiniiVision();
    % Edit resource and options as needed.  
    % Resource is ignored if option     Simulate=true
    % resourceDesc = 'TCPIP0::<host_name or IP addr>::INSTR';
    resourceDesc = 'GPIB0::7::INSTR';
    initOptions = 'QueryInstrStatus=true, Simulate=true, DriverSetup= Model=, Trace=false';      
    idquery = true;
    reset   = true;
    driver.Initialize(resourceDesc, idquery, reset, initOptions);
    disp('Driver Initialized');