AnsweredAssumed Answered

DSOX2012A GPIB communication problem

Question asked by popelsta on Jan 22, 2016
Latest reply on Feb 8, 2016 by w0dz

Like • Show 0 Likes0
Comment • 5

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

No one else has this question

Outcomes

w0dz

Jan 22, 2016 8:31 AM

Hi Stanislav,

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

Actions

popelsta @ w0dz on Jan 25, 2016 1:01 AM

Hi Brian,

this problem occures only in case of GPIB connection. During USB connection it is without problem (we have different problem in USB connection. We can not capture averaged data from scope (normal are ok) but this is different problem... ).

Yes, we use USB-GPIB adapter (82357B). Scope adress is 7 and only Keysight IO library are installed in computer.

Thank you for your ideas how to solve it.

Actions

w0dz

@ popelsta on Jan 28, 2016 8:43 AM

If you can send us an IO Monitor trace of the SCPI bus traffic, we might be able to see something. Please capture a trace and post it here or send to bv_support at keysight dot com.

Brian

Actions

popelsta @ w0dz on Jan 29, 2016 3:01 AM

Hi Brian,

here is log file.

Thank you.

Standa

Attachments

IOMonitorLog.xml163.2 KB

Actions

w0dz

@ popelsta on Feb 8, 2016 2:03 PM

We finally figured out what's going on here. Sorry it took so long! We are sending a very long SCPI string to the device. While it is not a problem for USB and LAN, it is a problem for GPIB. We have a test for GPIB scopes in BenchVue for this very reason, which is supposed to cause the SCPI string to get split into several "chunks". Unfortunately, when a Wavegen is present, there's a bug in the code that prevents this from working right (it thinks it's a function generator and not a scope, so the flag that tells it to split the GPIB doesn't get set). We will be fixing this bug at the next opportunity, probably with rev 3.5, which will be out in June. You can get around it by using USB or LAN.

Thanks for bringing this bug to our attention!

Brian

Actions

5 Replies

w0dz Jan 22, 2016 8:31 AM
Mark Correct
Correct Answer
Hi Stanislav,

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
Like • Show 0 Likes0
Actions
- popelsta @ w0dz on Jan 25, 2016 1:01 AM
  Mark Correct
  Correct Answer
  Hi Brian,
  
  this problem occures only in case of GPIB connection. During USB connection it is without problem (we have different problem in USB connection. We can not capture averaged data from scope (normal are ok) but this is different problem... ).
  
  Yes, we use USB-GPIB adapter (82357B). Scope adress is 7 and only Keysight IO library are installed in computer.
  
  Thank you for your ideas how to solve it.
  Like • Show 0 Likes0
  Actions
  - w0dz @ popelsta on Jan 28, 2016 8:43 AM
    Mark Correct
    Correct Answer
    If you can send us an IO Monitor trace of the SCPI bus traffic, we might be able to see something. Please capture a trace and post it here or send to bv_support at keysight dot com.
    
    Brian
    Like • Show 0 Likes0
    Actions
    - popelsta @ w0dz on Jan 29, 2016 3:01 AM
      Mark Correct
      Correct Answer
      Hi Brian,
      
      here is log file.
      
      Thank you.
      
      Standa
      Attachments
      IOMonitorLog.xml163.2 KB
      Like • Show 0 Likes0
      Actions
      - w0dz @ popelsta on Feb 8, 2016 2:03 PM
        Mark Correct
        Correct Answer
        We finally figured out what's going on here. Sorry it took so long! We are sending a very long SCPI string to the device. While it is not a problem for USB and LAN, it is a problem for GPIB. We have a test for GPIB scopes in BenchVue for this very reason, which is supposed to cause the SCPI string to get split into several "chunks". Unfortunately, when a Wavegen is present, there's a bug in the code that prevents this from working right (it thinks it's a function generator and not a scope, so the flag that tells it to split the GPIB doesn't get set). We will be fixing this bug at the next opportunity, probably with rev 3.5, which will be out in June. You can get around it by using USB or LAN.
        
        Thanks for bringing this bug to our attention!
        
        Brian
        Like • Show 0 Likes0
        Actions

DSOX2012A GPIB communication problem

Outcomes

Attachments

Related Content

Recommended Content