If you need assistance, please send an email to forum at 4hv dot org. To ensure your email is not marked as spam, please include the phrase "4hv help" in the subject line. You can also find assistance via IRC, at irc.shadowworld.net, room #hvcomm.
Support 4hv.org!
Donate:
4hv.org is hosted on a dedicated server. Unfortunately, this server costs and we rely on the help of site members to keep 4hv.org running. Please consider donating. We will place your name on the thanks list and you'll be helping to keep 4hv.org alive and free for everyone. Members whose names appear in red bold have donated recently. Green bold denotes those who have recently donated to keep the server carbon neutral.
Special Thanks To:
Aaron Holmes
Aaron Wheeler
Adam Horden
Alan Scrimgeour
Andre
Andrew Haynes
Anonymous000
asabase
Austin Weil
barney
Barry
Bert Hickman
Bill Kukowski
Blitzorn
Brandon Paradelas
Bruce Bowling
BubeeMike
Byong Park
Cesiumsponge
Chris F.
Chris Hooper
Corey Worthington
Derek Woodroffe
Dalus
Dan Strother
Daniel Davis
Daniel Uhrenholt
datasheetarchive
Dave Billington
Dave Marshall
David F.
Dennis Rogers
drelectrix
Dr. John Gudenas
Dr. Spark
E.TexasTesla
eastvoltresearch
Eirik Taylor
Erik Dyakov
Erlend^SE
Finn Hammer
Firebug24k
GalliumMan
Gary Peterson
George Slade
GhostNull
Gordon Mcknight
Graham Armitage
Grant
GreySoul
Henry H
IamSmooth
In memory of Leo Powning
Jacob Cash
James Howells
James Pawson
Jeff Greenfield
Jeff Thomas
Jesse Frost
Jim Mitchell
jlr134
Joe Mastroianni
John Forcina
John Oberg
John Willcutt
Jon Newcomb
klugesmith
Leslie Wright
Lutz Hoffman
Mads Barnkob
Martin King
Mats Karlsson
Matt Gibson
Matthew Guidry
mbd
Michael D'Angelo
Mikkel
mileswaldron
mister_rf
Neil Foster
Nick de Smith
Nick Soroka
nicklenorp
Nik
Norman Stanley
Patrick Coleman
Paul Brodie
Paul Jordan
Paul Montgomery
Ped
Peter Krogen
Peter Terren
PhilGood
Richard Feldman
Robert Bush
Royce Bailey
Scott Fusare
Scott Newman
smiffy
Stella
Steven Busic
Steve Conner
Steve Jones
Steve Ward
Sulaiman
Thomas Coyle
Thomas A. Wallace
Thomas W
Timo
Torch
Ulf Jonsson
vasil
Vaxian
vladi mazzilli
wastehl
Weston
William Kim
William N.
William Stehl
Wesley Venis
The aforementioned have contributed financially to the continuing triumph of 4hv.org. They are deserving of my most heartfelt thanks.
Registered Member #119
Joined: Fri Feb 10 2006, 06:26AM
Location: USA
Posts: 114
I have a Tektronix 2213 oscilloscope that started to act up a while ago. I think it was left on for a while, and then the next time I tried to use it, it had some problems as hopefully seen in the picture below. The traces no longer go across the entire screen. If you try to move them, they sort of bunch up. I can still get a signal on the working part, however. Does anyone know what might cause this or how to fix it? I opened it up, but did not see anything wrong such as blown capacitors like I was told to look for by several people. I looked through the operators manual and service manual which can be found at: But have yet to find something that helps me as I am not very familar with the internal workings of oscillioscopes. From what I can guess, something is wrong with the horizontal sweep generator, but I don't know how to proceed from there. I would imagine that most things would require another oscilloscope to test, so any test might be hard for me to do. Attached is a picture of the setup, a close up of the screen misbehaving, and a short quicktime movie of me moving the display around to show what is happening. I personally don't like quicktime, but thats the format my camera exports to and I don't really know how to convert it.
Registered Member #72
Joined: Thu Feb 09 2006, 08:29AM
Location: UK St. Albans
Posts: 1659
Rule out the simple stuff before diving deep into the circuitry. Is the "Beam Find" button stuck in, or is there a simple fault on the wires from that? That display is characteristic of what happens when you press beam find on a working 'scope, it clamps an off-screen picture down into the visible area so you can see where it went. If it was a fault in the X drive circuitry, you might expect an assymetric fault (from one rail going down), or a less well-defined clamping action on the trace. Try overdriving the Y inputs, a single fault is unlikely to clamp both X and Y, but the beam find will.
Registered Member #119
Joined: Fri Feb 10 2006, 06:26AM
Location: USA
Posts: 114
Thanks for the reply. I can look internally to see if there is a beam find problem, but the beam find button when compressed makes them very small, like less than 1 division. I'll edit with an update when I can check it. When you say overdrive, you mean a "high" voltage signal? It will go off the screen on the Y inputs if that is what you are asking, such as if I increase the div/V or raise the voltage going in.
This site is powered by e107, which is released under the GNU GPL License. All work on this site, except where otherwise noted, is licensed under a Creative Commons Attribution-ShareAlike 2.5 License. By submitting any information to this site, you agree that anything submitted will be so licensed. Please read our Disclaimer and Policies page for information on your rights and responsibilities regarding this site.