AnsweredAssumed Answered

.vxe will not recognize connection with other GPIB-USB converters.

Question asked by flashover21541 on Aug 15, 2012
Latest reply on Aug 26, 2012 by changmeikuan

Like • Show 0 Likes0
Comment • 6

I have a .vxe in VEE 6.0 that runs fine with my Agilent 82357A GPIB-USB converter. When I try to use any other
GPIB-USB converter (Agilent 82357B, NI GPIB-USB-HS, NI GPIB-USB-B) I get a message to check the cable and
make sure I have a meter addressed to 22. I can see everything with the IO control and everything is there. I can use
these devices outside of VEE with no problems. Any help would be very appreciated. Thanks.

No one else has this question

Outcomes

6 Replies

changmeikuan Aug 16, 2012 12:35 AM
Mark Correct
Correct Answer
Screenshot on the error message will be useful. Besides, traces in IO Monitor will be useful too (if you are using Agilent IO Lib. It will be NI I/O Trace if you are using NI VISA).
Which IO Lib version?

-mk
Like • Show 0 Likes0
Actions
- flashover21541 @ changmeikuan on Aug 22, 2012 12:05 PM
  Mark Correct
  Correct Answer
  Sorry I took so long to get back. I should have given more info before. I am using HP3458A's and they are old enough that they don't have an IDN identifier. When I look in Agilent or NI connection wizard I can see the meters. I can't figure out why the Vee can't see it. I am running Libraries 16.
  DH
  Attachments
  - Agilent IO.pdf46.8 KB
  - error screen shot.pdf9.3 KB
  Like • Show 0 Likes0
  Actions
  - changmeikuan @ flashover21541 on Aug 22, 2012 6:19 PM
    Mark Correct
    Correct Answer
    to be migrated, sourceId: 103409
    Like • Show 0 Likes0
    Actions
    - flashover21541 @ changmeikuan on Aug 24, 2012 6:31 AM
      Mark Correct
      Correct Answer
      I think I might have found my problem, but I can't get past it. I tried all the steps in the attached PDF (several times)
      I even tried to start in safe mode with no luck. Thanks for taking your time.
      DH
      Attachments
      agilent 488 problem.pdf186.0 KB
      Like • Show 0 Likes0
      Actions
      - flashover21541 @ flashover21541 on Aug 24, 2012 6:49 AM
        Mark Correct
        Correct Answer
        Sorry, here are the results that you asked for. Thanks.
        DH
        Attachments
        IO Monitor results 8-24-12.pdf83.2 KB
        Like • Show 0 Likes0
        Actions
        changmeikuan @ flashover21541 on Aug 26, 2012 11:29 PM
        Mark Correct
        Correct Answer
        Looking at your Agilent IO.pdf again, I am sorry that I think I have missed out something important. From Agilent IO.pdf, it seems like when you use 82357A and 82357B, both of them have different interface number i.e. GPIB0::22::INSTR and GPIB1::22::INSTR. I guess
        +82357A is GPIB0::22::INSTR+ while
        +82357B is GPIB1::22::INSTR+.
        
        If my guesses are correct then it is much easier to solve. Put the 488.2 things aside first. I am not sure in your program how does it look for device. I hope it is not hard coding to any GPIB interface number GPIB0 or GPIB1. However in IO Monitor result you attached, it is trying to communicate with gpib0, while 82357B is using GPIB1. I would recommend to try below:
        
        (A) Go to Programs > Agilent VEE Pro Runtime 6.0 config > IO Configuration, change the device address to the one that 82357B is using i.e. GPIB1::22::INSTR. Then run the .vxe again see if it works. If it doesn't work, probably the interface number is hard coded inside the program. Anyway, reset the address to GPIB0::22::INSTR in IO Configuration. Then try (B).
        
        (B) In Agilent Connection Expert (the ACE software in Agilent IO.pdf), right click on GPIB0 and delete the whole interface. Delete the whole GPIB1 interface too. Connect 82357B with the instrument to the PC. The default address for 82357B should now be GPIB0 and the device address should be GPIB0::22::INSTR when using 82357B. Run the .vxe again to see if it works.
        
        Please share the outcome then we can see how to proceed next :)
        
        Hope this helps,
        -mk
        
        Edited by: changmeikuan on Aug 27, 2012 2:16 PM
        Like • Show 0 Likes0
        Actions

.vxe will not recognize connection with other GPIB-USB converters.

Outcomes

Attachments

Attachments

Attachments

Related Content

Recommended Content