AnsweredAssumed Answered

BenchView Blue screening Windows 7 after enabling the file access feature

Question asked by cymrieg on Sep 3, 2015
Latest reply on Sep 22, 2015 by hognala

Like • Show 0 Likes0
Comment • 8

I was using BenchVue 2.7 successfully until I enabled the feature on the 34461A to do "File Access". After rebooting the instrument I was able to successfully navigate through Windows Explorer to see the files on the instrument.

Problem is although I have disabled this feature on the instrument when ever I run BenchVue now it will blue screen my PC.

I can run NI Visa interactive and communicate with the instrument ok.

I have un-installed BenchView and re-installed it and it still blue screens every time I run BenchVue

Any ideas how to fix this. It is tied to enabling the "file access" feature on the instrument - I think.

No one else has this question

Outcomes

w0dz

Sep 3, 2015 8:09 AM

Do you have Keysight IO Libraries installed along with NI IO Libraries? We have seen some bad behavior when ONLY NI VISA is present, specifically with the 34461A and only with USB. If you do not have Keysight VISA, please try installing it. You do not have to uninstall NI VISA, Keysight IOLS will detect its presence and install itself "side-by-side".

Brian

Actions

cymrieg @ w0dz on Sep 3, 2015 8:25 AM

I have only NI-VISA installed. I will install Keysight IOLS.

The only reason I don't do that is because when calling viFindRsrc in VISA I get the same USB instrument being reported twice. One of the VISA resources show the vendor id in Hex format and the other one is showing the other instrument with a decimal vendor id.

This is all using COM-VISA.

Actions

lhornburg

@ cymrieg on Sep 3, 2015 8:46 AM

I have good news, in Keysight I/O libs 17.1 update 1, that bug is fixed. It should only report 1 USB address now.

Actions

cymrieg @ lhornburg on Sep 3, 2015 9:01 AM

Magic. Thx

Actions

w0dz

@ cymrieg on Sep 4, 2015 1:14 PM

Is your problem resolved now?

Brian

Actions

cymrieg @ w0dz on Sep 5, 2015 8:36 AM

Yes, installing the I/O libraries fixed the issue.

Actions

cymrieg @ cymrieg on Sep 22, 2015 7:59 AM

I know this is a little off topic but "lhornburg" mentioned it in this thread.

I have NI-VISA 2015 and Keysight I/O library17.1.20011.4 installed and on calling FindRsrc in COM-VISA it is returning the same USB instrument twice. Once with the vendor/product id in hex and one with it in decimal.

If you go to NI-MAX it only shows one instrument and Connection Expert only shows one instrument.

Actions

hognala

@ cymrieg on Sep 22, 2015 10:59 AM

My guess is that you are using a 32-bit app? This is a historical issue that has always been this way, not going to change at this point (too many backwards compatibility concerns).

When comparing addresses, convert the decimal to hex or vice-versa, and then do the comparison. Keysight and NI can both accept either form for the viOpen call, its just going to be different for what viFindRsrc returns.

In a 64-bit app both NI and Keysight will return the hex version of the USB address.

Actions

8 Replies

w0dz Sep 3, 2015 8:09 AM
Mark Correct
Correct Answer
Do you have Keysight IO Libraries installed along with NI IO Libraries? We have seen some bad behavior when ONLY NI VISA is present, specifically with the 34461A and only with USB. If you do not have Keysight VISA, please try installing it. You do not have to uninstall NI VISA, Keysight IOLS will detect its presence and install itself "side-by-side".

Brian
Like • Show 0 Likes0
Actions
- cymrieg @ w0dz on Sep 3, 2015 8:25 AM
  Mark Correct
  Correct Answer
  I have only NI-VISA installed. I will install Keysight IOLS.
  
  The only reason I don't do that is because when calling viFindRsrc in VISA I get the same USB instrument being reported twice. One of the VISA resources show the vendor id in Hex format and the other one is showing the other instrument with a decimal vendor id.
  
  This is all using COM-VISA.
  Like • Show 0 Likes0
  Actions
  - lhornburg @ cymrieg on Sep 3, 2015 8:46 AM
    Mark Correct
    Correct Answer
    I have good news, in Keysight I/O libs 17.1 update 1, that bug is fixed. It should only report 1 USB address now.
    Like • Show 0 Likes0
    Actions
    - cymrieg @ lhornburg on Sep 3, 2015 9:01 AM
      Mark Correct
      Correct Answer
      Magic. Thx
      Like • Show 0 Likes0
      Actions
      - w0dz @ cymrieg on Sep 4, 2015 1:14 PM
        Mark Correct
        Correct Answer
        Is your problem resolved now?
        
        Brian
        Like • Show 0 Likes0
        Actions
        cymrieg @ w0dz on Sep 5, 2015 8:36 AM
        Mark Correct
        Correct Answer
        Yes, installing the I/O libraries fixed the issue.
        Like • Show 0 Likes0
        Actions
        cymrieg @ cymrieg on Sep 22, 2015 7:59 AM
        Mark Correct
        Correct Answer
        I know this is a little off topic but "lhornburg" mentioned it in this thread.
        
        I have NI-VISA 2015 and Keysight I/O library17.1.20011.4 installed and on calling FindRsrc in COM-VISA it is returning the same USB instrument twice. Once with the vendor/product id in hex and one with it in decimal.
        
        If you go to NI-MAX it only shows one instrument and Connection Expert only shows one instrument.
        Like • Show 0 Likes0
        Actions
        hognala @ cymrieg on Sep 22, 2015 10:59 AM
        Mark Correct
        Correct Answer
        My guess is that you are using a 32-bit app? This is a historical issue that has always been this way, not going to change at this point (too many backwards compatibility concerns).
        
        When comparing addresses, convert the decimal to hex or vice-versa, and then do the comparison. Keysight and NI can both accept either form for the viOpen call, its just going to be different for what viFindRsrc returns.
        
        In a 64-bit app both NI and Keysight will return the hex version of the USB address.
        Like • Show 0 Likes0
        Actions

BenchView Blue screening Windows 7 after enabling the file access feature

Outcomes

Related Content

Recommended Content