Keyboard Shortcuts
Likes
- HP-Agilent-Keysight-Equipment
- Messages
Search
CHECK OUT THE WIKI The purpose of the wiki is mainly to allow you to find information on instruments, either from either
- The model number
- The function(s) listed below. Some instruments have multiple functions - for example, the 4195A is a VNA, spectrum analyzer and an impedance analyzer. Therefore the 4195A is listed in multiple categories
Please also check out HPWiki available here:
- Accessory kits - various types
- AC power analyzers - PA2201A and PA2203A
- AC power supplies 6811C, 6812C, 6813C
- Airlines
- Arbitrary waveform generators M8194A
- Amplifiers?493A, 495A?
- Attenuators (optical) 8156A, 8157A, 8158B, 81566A, 81576A,?
- Attenuators (RF) 8494A
- Attenuator set (500 Ω) 350C
- Attenuator set (600 Ω) 350D
- Attenuator switch driver
- Audio analyzers? 8903A, 8903B, 8903E,? ?
- Base station test sets
- Bit error rate testers (BERTs)
- Cables
- Capacitance meters U1701A, U1701B, 4272A, 4278A, 4279A
- Capacitor Bridge 4270A,
- Capacitor standards 16380A, 16380C,?
- Carrier noise test setsi
- Cesium frequency standards
- Clamp ammeters
- Close field probes
- Crystal Impedance E4915A, E4916A
- Data Acquisition Systems (DAQs)
- DC power analyzers
- DC power supplies 6030A , 6031A , 6032A, 6033A, 6035A, 6131C, 6621A, 6622A, 6623A, 6624A, 6627A, 6255A, 6645A, 6671A, 6672A, 6673A, 6674A, 6675A, 62003A, 62003C, 62003E, 62004A, 62004B, 62004E, 62005A, 62005B, 62005E, 62006A, 62006B, 62006E, 62010A, 62010C, 62010E, 62012A, 62012C, 62012E, 62015A, 62015C, 62015E, 62018A, 62018C, 62018E, 62024A, 62024C, 62024E, 62028A, 62028C, 62028E, 62048A, 62048C, 62048E
- Delay lines
- Detectors
- Device current waveform analyzers
- Digital communications analyzers
- Directional couplers
- Distortion analyzers 330B, 330C, 330D, 331A, 332A, 333A, 334A, 339A, 8903A, 8903B, 8903E,???
- Dynamic measurement DC source
- Electrometers
- Fading simulators
- Femto ammeters
- Filters
- Frequency counters 522B, 5342A 5343A 5352B
- Frequency standards?
- Function Generators ? 3310A,? 8165A,
- GPIB controllers, extenders, cables etc.
- GPS frequency standards
- Harmonic mixers
- High resistance meters 4339B
- High resistance meter fixtures 16008B
- HEV EV Grid Emulators and Test Systems
- In-circuit test systems
- Impedance analyzers 4195A, 4291A, 4291B, 4395A, 4396A, 4396B, 4294A, E4990A, E4991A
- Impedance Analyzer Accessories
- Impedance / Gain Phase analyzer 4194A
- Impedance Meter 4193A,
- Isolators
- LCR meters? U1701A, U1701B, U1731A,? U1731B, U1731C, U1732A, U1732B, U1732C, U1733C, 4191A , 4192A, 4194A, 4195A, E4196A,? 4216A, 4260A, 4261A, 4262A? 4263A, 4263B, 4271B, 4274A, 4275A, 4276A , 4277A, 4284A, 4285A, 4286A, 4287A, 4291A, 4291B, 4294A, 4332A, 4342A, 4395A, 4396A, 4396B, E4980A and E4980AL
- LCR meter calibration devices? 16380A 42030A? 42090A, 42091A and 42100A
- LCR meter accessories
- 2-Terminal BNCs.
- 4-Terminal Pair (BNC connectors)
- Cable extension 16048A, 16048D, 16048E, 16048G, 16048H
- DC current bias accessories 42841A, 42842A, 42842B, 42842C, 42843A
- DC voltage bias accessories 16065A, 16065C,
- Kelvin clips 16089A, 16089B, 16089C,16089E
- Lead Components 16047A,16047B, 16047D, 16047E
- Material 16451B, 16452A
- Probes 42941A
- SMD 16034E, 16034G, 16034H
- 2-port 16096A
- 7 mm (APC7)
- 2-Terminal BNCs.
- LCZ meters? 4276A, 4277A,
- Lightwave clock / data receivers
- Lightwave converter
- Lightwave component analyzer
- Lightwave measurement system mainframes
- Lightwave polarization analyzers 8509B
- Logic analyzers
- Nemo wireless network solutions.
- Noise and interference test set
- Noise figure analyzers
- Noise sources 346A, 346B. 346C ,
- Matching pads (50 ohm to 75 ohm or similar)
- Materials test equipment
- Microwave repeaters
- Microwave downconverters 70427A
- Microwave / THz sources
- Milliammeter 428B
- Milliohm meter
- Mobile communications DC source
- Modular instruments
- AXIe
- Data acquisition (DAQ)
- USB
- PXIe
- Modulation analyzers
- Multimeters 427A, 970A
- Optical attenuators
- Optical heads
- Optical sources
- Optical spectrum analyzers
- Oscilloscopes 120A, 120AR, 120B, 122A, 130A, 130B, 130BR, 130C, 140A, 140B, 141A, 150A, 150AR, 160B, 180A, 180AR, 180CD, 181A, 181AR, 181T, 181TR, 182C, 182T, 183A, 183B, 184A, 184B, 185A, 185B, 1200A, 1200B, 1220A, 1221A, 1703A, 1707A, 1707B, 1710A, 1710B, 1715A, 1722A, 1725A, 1726A, 1740A, 1741A, 1742A, 1743A, 1744A, 1746A, 1980A, 1980B, 5403A, 6000A, 6000L, 16533A, 16534A, 54100A, 5410B, 54100C, 5100D, 54111D, 54120A, 54120B, 54200A, 54501A, 54502A, 54503A, 54504A, 54520A, 54520C, 54540A, 54540C, 54542A, 54542C, 54600B, 54601A, 54601B, 54602B, 54603B,? 54645A, 54654N, 54710A, 54720A, 54750A, 54825N, E1428,?
- Oven controlled crystal oscillators (OCXOs)
- Pattern generators
- PCM terminal test set
- Phase noise measurement
- Pico ammeters
- Printers 2225
- Plotters 7470A, 7475A?
- Probes
- Protocol analyzers and exercisers.
- Power booster test sets
- Power meters 431A, 431B, 431C, 432A, 435A, 435B, 437B, 438A
- Power splitters
- Power supplies
- Pulse generators
- Q-meters 4342A?
- Q-meter calibration inductors 16470A
- Reflection transmission test set
- Return loss module (optical)
- Relays / switches / switch matrices (optical)
- Relays / switches / switch matrices (RF)
- Resistor standards 42030A?and 42100A
- S-parameter test sets
- Scalar network analyzers
- SCSI bus preprocessor interface E2324A
- Selective level meters 3746A
- Semiconductors
- Semiconductor parameter analyzers 4145A, 4155B, 4156B,
- Signal analyzers
- Signal generators / sweep generators / signal sources / oscillators 200CD, 201B, 209A, 204D,? 608A,? 8165A
- Software
- Source measure units
- Spectrum analyzers 4195A,???
- Switch control units
- SWR meter 415E?
- Time interval? counters
- Time mark generator 226A
- Timing and data state modules
- Torque wrenches
- Transmitter testers
- Trigger modules
- Ultrasound transducers
- Universal bridge? 4260A, 4265A, 4265B?
- Vacuum tube voltmeter 410C
- Vector Impedance Meter 4193A, 4800A, 4815A
- Vector Network Analyzers (VNAs) 4195A,? 8510A, 8510B, 8510C, 8753A, 8753B, 8753C, 8753D, 8753E, 8753ES, 8752ET, 8719A, 8719B, 8719C, 8719D, 8720A, 8720B, 8720C, 8720D, 8720ES, 8722A, 8722B, 8722C, 8722D, 8722ES,
- Vector Network Analyzers (VNA) calibration kits 85032B, 85032E, 85033C, 85033D, 85033E, 85050B, 85050C, 85050D, 85052B, 85052C, 85052D, 85054A, 85054B, 85054D, 85056A
- Vector Network Analyzer (VNA) verification kits
- Vector Signal Analyzer 89650S, 89600S
- Vector voltmeters 8405A, 8508A,
- VXI mainframes 70000B, 70000C
- Waveform and function generators
- Waveguide to waveguide and waveguide to coaxial transitions.
- Wireless 58 OTA chambers
- Wireless channel emulators
- Wireless network emulators
- Wireless communication test sets
?
Re: HP 8554B, no RF after first successful run...
开云体育
Some analog VOMs put out enough current to fry a mixer diode.
From: [email protected] <[email protected]> on behalf of Bill Berzinskas <bberzinskas@...>
Sent: Saturday, September 21, 2024 7:48 AM To: [email protected] <[email protected]> Subject: Re: [HP-Agilent-Keysight-equipment] HP 8554B, no RF after first successful run... ?
I did re-check, and I've since gotten more?problems in?this?area...? ? ? :-D? -10v supply is no longer happy..??
Lot of people saying it might be the mixer diodes, so I may check those w/ my old analog meter today after I look?
over MORE POWER SUPPLIES....? ??
On Sat, Sep 21, 2024 at 5:27?AM Martin via <musaeum=[email protected]> wrote:
|
Re: HP 8554B, no RF after first successful run...
I did re-check, and I've since gotten more?problems in?this?area...? ? ? :-D? -10v supply is no longer happy..?? Lot of people saying it might be the mixer diodes, so I may check those w/ my old analog meter today after I look? over MORE POWER SUPPLIES....? ?? On Sat, Sep 21, 2024 at 5:27?AM Martin via <musaeum=[email protected]> wrote:
|
Re: Introduction
....but the years are long.
toggle quoted message
Show quoted text
I almost missed that. Another "like the hot kiss at the end of a wet fist" moment. DaveD KC0WJN Thanks for all the fish. ============================== All spelling mistakes are the responsibilty of the reader (Rick Renz, STK, ca. 1994) ============================== On Sep 21, 2024, at 09:58, Harvey White via groups.io <madyn@...> wrote: |
Re: Introduction
Oh the damage I have done with vi!
I am an emacs guy, and have the emacs mode-less editor model permanently seared into my brain... Invariably, while using vi, I will forget that I am in command mode, and will touch type a bunch of text, at a furious rate, into being some random command. I won't notice what I have done, until one of my random text/commands honks off vi, and causes it to issue stream of beeps in complaint. When I look up at the screen, I will see that I have blown away a thousand lines of my code, started a few new processes, opened three or four spurious command line windows, and condemned myself to a half day's trying to fix the damage done... Early in my career, I found jove, which stands for (Jonathan's Own Version of Emacs). Jove was written by Jonathan Payne when he was a high school student, and I have ported it to every machine I have ever worked with, unix, msdos, or windows. Now a days, jove is in the debian linux repositories, so it too is available everywhere in linux. Jove is a tiny fraction of the size of vi, or emacs, and can do anything vi can do. I quickly install it on every machine I use and ditch vi. Once, as the sole user, I took down a customer's home grown 68000 based machine, with its home grown port of unix, while I was using it as a development system... I am told, simply by using jove. It took the guy that did the original unix porting a weekend to reassemble the system disk, and bring the machine back up. He forbade me from using jove on his machine, while being totally deaf to my protestations that if a user process can damage a unix system, there is a far bigger problem that needs fixing, than what the user was running... So, I was stuck using vi. About mid week after he banished me to vi, I crashed his machine down again, whilst using vi. This time, it took him a full week to put his machine back together... with some rumblings about my now being responsible for backing up his machine. He also decided that the problem was really me, so he banished me to using a Sun Workstation... -Chuck Harris On Fri, 20 Sep 2024 11:31:17 -0400 "Dave Daniel" <kc0wjn@...> wrote: Eeek! I used EMACS until I realized that vi was always available on |
Re: Introduction
Art is long....
toggle quoted message
Show quoted text
(apologies if I misremember that). Harvey On 9/21/2024 5:14 AM, David C. Partridge wrote:
Life is short. |
Re: Introduction
I'd been using it for the last fifteen years or so.
toggle quoted message
Show quoted text
I dropped it for several reasons: 1. I think I remember running into some difficult to fix errors on their end 2. The code became less useful as I started using C++ more and more. 3. I could not transfer the pascal code from there to an embedded processor. 4. Making my own components never quite worked well enough. (I do programmed arrays of stuff) 5. exactly like C++, the button class is very limited, made my own from a panel. So I'm doing quite similar projects in "Embarcadero" C++, having tried Microsoft VC (and not comprehending the startup menu because they have different names for everything).? Tried Eclipse C (no drag and drop for the UI).? Tried some of the commercial graphics products with an experimenter license, couldn't get them to work (inadequate documention at critical points).? Borland C++ (Embarcadero) seemed the only thing left. <sigh>. I did get a complete application written in it with a decent enough repeatable UI (avoid templates, they refer back to the original code with links regardless of what they say).? So I'll stick with that for a while. Harvey On 9/21/2024 5:10 AM, Dave_G0WBX via groups.io wrote:
Re:- |
Re: GPIB software: Prologix and Python
开云体育Given the code example friendly issued by Chuck I could not resist and spend a couple of hours to test it with my HP437B power meter. The result is not A-level programming but just a script that works. I have not used my Prologix GPIB adapter for many years. The advantage over the HP82357 is that you have more control over the GPIB lines, if you want. The HP adapter seems (much) faster to me. Use it as you wish. Cheers, Harke # try out some gpib data collection using the Prologix gpib-usb controller # Chuck Harris # Harke Smits # Test for HP437B power meter @ GPIB address 3 # serial data format: bytes....----> str.encode("..") # Sept 2024 import serial import time def gpib_init(): ser.write(str.encode("++mode 1\r")) # Controller mode time.sleep(0.1) ser.write(str.encode("++ifc\r")) # assert IFC line time.sleep(0.1) ser.write(str.encode("++auto 0\r")) # time.sleep(0.1) ser.write(str.encode("++eoi 0\r")) # disable EOI assertion time.sleep(0.1) def gpib_read(addr): ser.write(str.encode("++addr " + str(addr) + "\r")) time.sleep(0.1) ser.write(str.encode("++read eoi\r")) return ser.readline().strip() def gpib_write(addr,gpibstr): ser.write(str.encode("++addr " + str(addr) + "\r")) time.sleep(0.1) ser.write(str.encode(gpibstr + "\r")) def check_srq(): srq = False ser.write(str.encode("++srq\r")) srq = (int(ser.readline()) == 1) return srq # # test program... # ser = serial.Serial('COM4',rtscts=0,timeout=1) # verify COM number gpib_address = 3 # HP437B power meter default GPIB address ser.write(str.encode("++ver\r")) # Prologix version print(f"Prologix controller version: {ser.readline().strip()}") gpib_init() gpib_write(gpib_address,"*RST\r") time.sleep(0.5) gpib_write(gpib_address,"IDN?\r") print("ID = " + str(gpib_read(gpib_address)) + "\r") gpib_write(gpib_address,"PR\r") # Preset cmd time.sleep(0.1) gpib_write(gpib_address,"CSZE\r") # Zero command time.sleep(0.1) print(f"Zeroing power meter") while not check_srq(): print(".", end=" ", flush=True) time.sleep(0.2) gpib_write(gpib_address,"CSCL100%\r") # Calibrate command, adjust cal fac if necessary time.sleep(0.1) print(f"\r\nCalibrating power meter") while not check_srq(): print(".", end=" ", flush=True) time.sleep(0.2) time.sleep(5) # PWM needs time to autorange gpib_write(gpib_address,"ERR?\r") # check the error code: zero is all ok print(f"\r\nError code line 71: {int(gpib_read(gpib_address))}") value = str(gpib_read(gpib_address).strip()) print(f"RF power: {value} dBm.\r") print(f"end")
|
HP 8566B Not Showing Any Signal
Hello All!
?
This is my first post here, and I'm super glad to have found this group. I'm working on an HP 8566B that I purchased locally in Dallas.
?
When I got the unit, the only issue I thought I had was an occasional YTO unlock light. Now, as I’ve been playing with it and trying to test signals into the front of the unit, I find that the CAL signal does not show up on the RF input.
Tonight, I really got into it thinking that the attenuator must be at fault based on some YouTube videos I’ve watched showing similar symptoms. Attached is a video showing some of the things that I’m seeing. If you can share any light on any of this, I’d be super grateful.
?
?
After I film this video, I went ahead and torn into it and removed the attenuator block. When I removed the attenuator block, I noticed that the press on connector that connects the attenuator to the motherboard had a pin that was flattened and never made contact in the female header. I assumed I had found my problem tonight so I straightened the pin out and carefully reassembled. It fired it up and I have the exact same issues as before. No matter what amount of signal I run into the input analyzer I’m not able to see it.
The frustrating thing is that yesterday when I was playing with it I was able to see the signal when I ran the reference level down to -27 DB. Luckily I have a unit here so tomorrow night time allowing, I’ll try to pull either the entire YIG sub assembly out and swap that in or merely just swap out the continuator.
Thanks again! Brad Jackson |
Re: Introduction
On 9/21/24 02:37, Tony Goodhew wrote:
I'm on vacation near Shell Knob in Missouri and I'm trying to catch up with this. mammoth thread...No impact here; I'd not touch Visual anything with a ten-foot pole. I run *emacs*. Near-zero usage for such an emulation is not surprising at all. People who want an emacs emulation probably want it because they've run emacs in the past, and such people are probably still running emacs. Further, most Windows people I've met tend not to dig around and explore things, they just do what they're told. If you guys didn't tell them "hey, try emacs mode!" they probably didn't. -Dave -- Dave McGuire, AK4HZ New Kensington, PA |
Re: Introduction
On 9/21/24 04:56, Dave Daniel wrote:
LOL. You never worked at Documation. We had a lot of fun doing weird ...uh... stuff there. It was kind of like being professional adolescents. When Storage Technology bought Documation, we all had to "grow up". But that was in the late 70s and early 80s.Haa, no I never worked there. But I was in the startup company world for a long time; it sounds like the attitudes are similar. :) But even there, we never wire-wrapped in humor. ;) We do have a few Documation card readers at the museum. None working yet; we must fabricate new rollers for them. It was during my stay at Doc that I wirewrapped the only card that I ever built that worked flawlessly without needing rework - a 128 kB memory card, using Intel 2 kB memory ICs, IIRC.Nice! -Dave -- Dave McGuire, AK4HZ New Kensington, PA |
Re: HP 8554B, no RF after first successful run...
Hi Bill,
?
When I first read your post I thought you did some very low frequency stuff.?
Actually you're referring to MHz (Megahertz), not mHz (Millihertz).
?
Since you left the unit running for a while until the fault condition appeared: did you re-check once it was cold again? Like after 24 hours?
?
cheers
Martin |
Re: Introduction
Delphi was very popular in Europe, Germany especially.
There is also (previously? mentioned in another thread) EZGPIB, that is a Pascal based scripting system, for GPIB instrument/device control. I believe that was probably created with Delphi. Sadly it's author has passed, but his site lives on. It's a Windows program, but will run in a guest VM on other OS's, if they can make USB peripherals available to the guest.? I've run it with NI-GPIB and common USB/Serial devices, running in a XP VM as a guest on Linux Mint in the past. Regards. Dave B (UK) -- Created on and sent from a Unix like PC running and using open source software: |
Re: Introduction
Life is short.
toggle quoted message
Show quoted text
-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Harvey White Sent: 21 September 2024 00:44 To: [email protected] Subject: Re: [HP-Agilent-Keysight-equipment] Introduction Lazarus Pascal, and no idea why they named it like that, their product picture is a cheetah. Maybe one of the designers is a Howard? Harvey On 9/20/2024 6:50 PM, Dave Daniel wrote: A longer reply is due. |
Re: Introduction
开云体育Re:-From: Harvey White Date: Fri, 20 Sep 2024 17:44:05 GMT Nope, Borland Pascal, then Delphi.
Have you looked at? ? ? Largely cross platform, and fairly Delphi compatible too. Even sporting a Delphi project import function, that "mostly" works, but usually needs some code fiddling in respect to any serial I/O or Networking. Dave B (UK)
-- Created on and sent from a Unix like PC running and using open source software: |
Re: Introduction
开云体育Hi again.Ah..? the "Large Scale Systems Museum".? That's been mentioned before here. If I'd known about that a few years ago, I'd have 110% definitely visited at least once, as I used to visit a company at Souderton PA on an irregular basis, & did the drive from there to Dayton for the Hamfest back in 2015, with some (also licenced) colleagues who had other business near Pittsburgh.? Resulting in a solo drive back a few days later in some truly horrendous weather!? 4+ hours each way.? (A bit like driving 200 miles on the M6 in the UK these days!) I did get to spend half a day (not enough) at the Wright Patterson Airospace Museum, another one I'd like to re-visit. In an earlier past employment, where I was working with the DG systems, one of my main functions was rebuilding crashed hard drives.? Perkin Elmer, Diablo, Wangco, and the (then) advanced CDC multi platter 96Meg units.? (I could lift one from the rack, onto the bench back then, not now sadly!) Full physical strip-downs and clean, then rebuild, purge and re-align/calibrate, before thrashing the heck out of them with the stressful (not just for the drive!) Random Read test.? Some drives would have to be "secured" to the bench when that test was run, and loose articles nearby removing. We were even recovering some crashed heads with careful cleaning, if they were just lightly damaged by accumulated debris.? Saved a ton of money doing that...? Quite impressive how much physical punishment some would take, then polish up like new and work just fine afterwards. (Plenty of "over qualified incompetent customer" stories accumulated as a result of that work too!) One of the few tasks, where no one really complained about the time taken, as we found that the more care and time spent during the rebuild and setup, the better they performed.? Even better, enjoyable work as well. I doubt very much I'll make it back to the US under my own steam now.? Pitty, as I perhaps could help with your Tek 4014 problem, as I also worked for Tek in the UK in the past, so those CRT storage display systems I understand too. Just a thought, do you home any of the DG Micro Nova systems?? That were advertised as being "IBM PC Compatible" (with the 8086 co-processor card.) Of course, by then, hard drives were mostly non-DIY fixable, sadly. Regards to All. Dave B (G8KBV)? Ex GPO Telecom, Tek', Finnigan MAT Ltd, Texscan, and then way too long at AR UK. -- Created on and sent from a Unix like PC running and using open source software: |
Re: Introduction
LOL. You never worked at Documation. We had a lot of fun doing weird ...uh... stuff there. It was kind of like being professional adolescents. When Storage Technology bought Documation, we all had to "grow up". But that was in the late 70s and early 80s.
toggle quoted message
Show quoted text
It was during my stay at Doc that I wirewrapped the only card that I ever built that worked flawlessly without needing rework - a 128 kB memory card, using Intel 2 kB memory ICs, IIRC. DaveD KC0WJN Thanks for all the fish. ============================== All spelling mistakes are the responsibilty of the reader (Rick Renz, STK, ca. 1994) ============================== On Sep 20, 2024, at 19:29, Dave McGuire via groups.io <mcguire@...> wrote: |
Re: Hughes IMPATT
开云体育Erick thank you but unfortunately I could not justify that sort of expense so I have been collecting the parts for many years Regards Paul South coast UK ? From: [email protected] [mailto:[email protected]] On Behalf Of f1ghb via groups.io ? Hello, ? We can see a full system here : ? ? Best regards Eric |
Re: Hughes IMPATT
开云体育Am 21.09.2024 um 01:17 schrieb ed
breya:
|