Keyboard Shortcuts
Likes
Search
Readings from 436A power meter using 82357B USB-GPIB?
Hello,
I can't argue against, but my only experience is that I _can_ set the instrument in the state I want (REN active) and can read the output data when I deactivate REN, but not otherwise. I have tried to follow section 3. What I would really like is a description of how to communicate with this instrument using the 82357. Regards, ? Staffan |
Hello,
Final (?) findings. Interactive IO in the Agilent Connection Expert seems not sufficient... Running the code, accessing the VISA library immediately and _not_ using viScanf, but viRead seems to have done the trick. I can now talk to and _read_ (not scan?) from the 436A - Yippie! Many thanks to all you people involved for suggestions, comments and taking the time to comment! Regards, ? Staffan |
开云体育It’s not impossible that you have a stuck gate somewhere, and the operation you observe is not normal for the instrument. It’d be worth checking that against another 436A. Cheers, Kuba
|
Hello,
toggle quoted message
Show quoted text
Indeed a point. Not having a second 436 around, I will try this one and see where it gets me for now, but if anyone would send me a 436 - I’d be happy to test :-) Regards, ?Staffan On Wednesday, November 21, 2018, Kuba Ober <kuba@...> wrote:
|
开云体育Try addressing another device?? (Even one that doesn’t exist...) Dave B (G0WBX) Re: Readings from 436A power meter using 82357B USB-GPIB? From: Staffan Date: Tue, 20 Nov 2018 10:26:07 PST Hello,
-- Created on and sent from a Unix like PC running and using free and open source software. :: |
Hello,
Addressing another device using interactive IO doesn't seem to release the 436. What I did find out though was that viRead - wich is what interactive IO actually does - gets 14 characters back, but it expected 1024... I guess I IO doesn't get an end of line from the 436 and decides it never returned enough characters... Reading the 436 manual, it's clearly stated that it returns exactly 14 characters for each read. So, a response is given, but asking in the wrong way gives an error, not due to the instrument, but due to the setup of I IO... I found a couple of nice functions in the VISA? library - there is a way to deassert the REN line for example. I know now that it isn't needed. Nevertheless, this exercise was good for learning a bit more about Keysight (Agilent/HP) Connection Expert, Interactive IO and, most importantly, how to get the communication working the the VISA library! Regards, ? Staffan |
I also have a HP436A and try to make the GPIB work. After search on several websites, I could not find any example, therefore, I spent two days and figured out this problem. Here is the right GPIB command sequence : ? Interactive Control Copyright 2022 National Instruments Corporation All rights reserved. ? Type 'help' for help or 'q' to quit. ? GPIB0: ibdev ??? enter board index: 0 ??? enter primary address: 13 ??? enter secondary address: 0 ??? enter timeout: 10 ??? enter 'EOI on last byte' flag: 1 ??? enter end-of-string mode/byte: 10 ? ud0: ibclr? <----------- use this to turn on remote LED, required. [0100]?? ( cmpl ) ? ud0: ibwrt "9A+I"? <---- this means: set RF power unit to be W [0100]?? ( cmpl ) count:? 4 ? ud0: ibrd 14????? <-----read 14 byte data as ASCII [0100]?? ( cmpl ) count:? 14 50? 4c? 41? 20? 30? 39? 39? 30????????? P L A?? 0 9 9 0 45? 2d? 30? 39? 0d? 0a????????????????? E - 0 9 . . ? Details about the "PLA" can be found on page 3-19, HP436A operating and service manual. ? ? I use a NI GPIB-USB-HS adaptor, run on windows 10, with NI VISA (2022) installed. With NI MAX scanning, I found the address=13 for HP436A. With NI MAX interactive control, I tried above sequence. When you implement above sequence with C or python, the timing is important. Between ibclr to ibwrt, it needs about 0.3s, between ibwrt and ibrd, it needs at least 1.2s? (1.2s is the worst case according to the manual). |