Hello,
we have problem with communication between DSOX2012A scope and BenchVue. Scope is connected by GPIB. Scope is recognized and can be added into BenchVue. In Instrument Setting we are able to get data from scope. Problem is in Trace Data tab. When we want to get data by Get Current Traces after several seconds we get this error message: VI_ERROR_TMO: A timeout occured.
Firmware version in scope: 2.41.2015102200
IO lib ver.: 17.1.19313.5
BenchVue 3.0.1510.08
Lib 1.20
Windows 7 64bit
We prefer GPIB over USB connection due to reliability.
Thank you very much.
Stanislav Popelka
we have problem with communication between DSOX2012A scope and BenchVue. Scope is connected by GPIB. Scope is recognized and can be added into BenchVue. In Instrument Setting we are able to get data from scope. Problem is in Trace Data tab. When we want to get data by Get Current Traces after several seconds we get this error message: VI_ERROR_TMO: A timeout occured.
Firmware version in scope: 2.41.2015102200
IO lib ver.: 17.1.19313.5
BenchVue 3.0.1510.08
Lib 1.20
Windows 7 64bit
We prefer GPIB over USB connection due to reliability.
Thank you very much.
Stanislav Popelka
While GPIB provides a more physically robust connection than USB, it can be problematic in some situations. I would first suggest that you see if you can duplicate this problem using a USB or LAN connection, just to see if that clears it up. Also, if you are using a USB-GPIB adapter (82357B), that has some addresses that do not work well with BenchVue because the adapter does not work correctly if serial poll is used. Avoid addresses 9,11,13,25, 27 and 29.
If that is not the problem, other GPIB issues could be related to using an I/O library other than Keysight's. Although NI and Keysight IO can co-exist, sometimes it helps to use ours unless you have NI GPIB hardware. To rule that out, use Control Panel -> Programs and Features to "Modify" (not "Repair") the Keysight IOLS, making Keysight "Primary".
Brian