The old Broadcast Electronics Transmitter

Alternate title: More blown-up stuff

This Broadcast Electronics Fm 3.5A will be thirty years old in April. We should have a party!

Broadcast Electronics FM 3.5A, WVOS-FM, LIberty NY
Broadcast Electronics FM 3.5A, WVOS-FM, Liberty NY

Unfortunately, this transmitter is not doing too well these days. The PA high voltage feed through capacitor has arced over to the PA cavity, causing the station to be off the air.

BE FM3.5A HV feedthru capacitor
BE FM3.5A HV feed thru capacitor

Naturally, this happened over the weekend, parts will not arrive until Tuesday at the earliest, and the station is without a backup transmitter.

Obviously, trouble shooting this was a two-person job.  Never work alone on HV equipment.  The symptom was the main circuit breaker was tripping after the HV on command.  Starting from the transformer end of the HV power supply circuit and working toward the anode of the PA tube, all of the components were tested by isolating each component then turning the HV on.   Special care was taken to discharge all components after each test.  The capacitors and bleeder resistors were reconnected at the same time.  There is too much risk involved with charged 8 KV capacitors and no way to bleed that charge to ground.  Everything worked up until the PA cavity was reconnected (without the tube), then the breaker tripped again.  Thus, the above feed-through capacitor was removed and disassembled, revealing the damage.

The question is, how long should transmitting equipment last? After all, if one were running a freight delivery company, you would not be driving around in thirty-year-old trucks, would you? No, not if you wanted to stay in business. Like all electro-mechanical equipment; transmitters, consoles, STLs, antennas, computers, etc wear out.  A smart plan would be to have a replacement schedule and be putting money into a capital equipment replacement fund.   Equipment life varies with the type.  Getting twenty years out of a main transmitter is a pretty good service life, going beyond that is pressing one’s luck.  Ten years on any one computer is a very long time.  Then there are certain transmitter manufactures that drop support on older units, which makes it difficult to keep them operating.  Owners and managers need to be cognizant of the age and condition of critical infrastructure.  As field engineers, how much time do we devote to keeping antiquated equipment running, or should we even be servicing it at all?  As independent contractors, we incur a liability whenever we touch something.  Where does the ownership’s responsibility lay in providing safe, functional equipment for their stations?  All interesting questions.

Wireshark; what is it good for

Wireshark is a packet protocol analyzer that is free for download and runs on Windows, Linux, BSD, OS X, and Solaris.  In the evolving broadcasting studio, computer networks are the backbone of the facility. Not just on the office side of the house, but also on the broadcast origination side as well. Today, almost everyone uses some type of computer automation system running on a network. In addition, new technologies such as AoIP consoles, VoIP phone systems, audio and video routing, remote control, off-site monitoring, audio processing, etc continue to develop.  Because of this, more and more broadcast engineering work is falling into the computer and networking realm.

Like anything else, networks can fail.  Failure modes can originate from both the physical side, e.g. wiring, connectors, patch bays, network interface cards or the software/protocol side.  Being able to diagnose problems quickly and take remedial action is important.  On the networking side, if a physical problem has been ruled out, then the problem exists with a protocol.  That is where Wireshark becomes useful; it takes the guesswork out of networking protocol troubleshooting.

Wireshark packet protocol analyzer has the following features (from their website):

  • Deep inspection of hundreds of protocols, more are in development
  • Live capture and offline analysis
  • Standard three-pane packet browser
  • Versions available for Windows, Linux, OS X, Solaris, FreeBSD, NetBSD, and other OS
  • Captured network data can be browsed via a GUI, or via the TTY-mode TShark utility
  • Filtering by protocol, IP address, MAC address, frame type, sequence number, etc
  • VoIP analysis
  • Read/write many different capture file formats: tcpdump (libpcap), Pcap NG, Catapult DCT2000, Cisco Secure IDS iplog, Microsoft Network Monitor, Network General Sniffer® (compressed and uncompressed), Sniffer® Pro, and NetXray®, Network Instruments Observer, NetScreen snoop, Novell LANalyzer, RADCOM WAN/LAN Analyzer, Shomiti/Finisar Surveyor, Tektronix K12xx, Visual Networks Visual UpTime, WildPackets EtherPeek/TokenPeek/AiroPeek, and others
  • Capture files compressed with gzip can be decompressed on the fly
  • Live data can be read from Ethernet, IEEE 802.11, PPP/HDLC, ATM, Bluetooth, USB, Token Ring, Frame Relay, FDDI, and others (depending on your platform)
  • Decryption support for many protocols, including IPsec, ISAKMP, Kerberos, SNMPv3, SSL/TLS, WEP, and WPA/WPA2
  • Coloring rules can be applied to the packet list for quick, intuitive analysis
  • Output can be exported to XML, PostScript®, CSV, or plain text

A few things to keep in mind with the physical connection.  Connecting a computer to a switch port will establish a collision domain between the switch port and the computer which is also called a network segment.  The computer NIC will see all traffic on that collision domain and all broadcast traffic on the network or sub-network that the switch is attached to.  If there is a suspected problem with a particular network segment, the Wireshark computer needs to join that collision domain.

Creating a network segment tap with a hub
Creating a network segment tap with a hub

This can be done most simply by installing Wireshark on the host in that domain. Alternatively, a hub can be used to add another host to the collision domain.  Or, if it is a managed switch, there may be a provision to send all traffic on the switch out of one designated port.  This is called ‘port mirroring’, ‘port monitoring’, ‘Roving Analysis’ (3Com), or ‘Switched Port Analyzer’ or ‘SPAN’ (Cisco).

Network diagram with managed switch
Network diagram with managed switch

A quick tutorial on what to look for when using Wireshark, Part A:

Part B:

And briefly, that is how it is done.  There are many more videos on youtube and elsewhere if interested in learning more.

Happiness is: An AM directional array at licensed values

Last week I did some repair work at WDDY in Albany NY. It seems the sample line on one of the towers was melted in half by a lightning strike. This station uses sample loops up on the tower for its directional antenna monitoring system.

WDDY antena array, Albany, NY
WDDY antena array, Albany, NY

As it happened, the sample line in question was on the reference tower, which makes everything else meaningless.  Before the meltdown, there were several years’ worth of maintenance logs that showed the previous values for current ratio and phase relationship.

With the transmitter turned off and locked out, I removed the damaged section of the line from the base of the tower to the RF choke coil in the tuning house.  Where the sample line came off of the base of the tower, there was a UHF-type connector that had been improperly applied.  Using spare parts, I fixed that connector, then spliced the line into place.  Upon power-up, the transmitter and antenna readings returned to their previous values, which were slightly out of tolerance.

Thus, some phasor tuning was needed.  There are not too many people left that can properly tune an AM phasor.  All of the control interact with each other; moving the power or phase to one tower will likely affect all of the other towers and possibly the reflected power on the transmitter.  This phasor was made in the 1970s by Multronics with what looks like all RCA parts.  Multronics, I think, was John Mullaney who is more known for the folded unipole antenna.  In any case, after a good few hours of careful hand cranking and a run out to the reference tower to move a coil tap, here are the results:

WDDY tower one, reference
WDDY tower one, reference
WDDY tower two
WDDY tower two
WDDY tower three
WDDY tower three
WDDY forward/reflected power
WDDY forward/reflected power

Not bad for a day’s work.

New Studio Project, Part II

The finished product:

SAS Rubicon console, WAJZ Albany, NY
SAS Rubicon console, WAJZ Albany, NY

This is the finished product from an earlier post.  Currently, it is the studio for WAJZ in Albany, but that is not permanent.  The SAS studio goes together fairly quickly, as most of the trunking between the TOC and studio is done over the SAS data channel.

The studio monitors (Tanoy Reveal) are set on little posts under the computer screens. I like this setup as the DJs are less likely to rock the house if they decide to crank up the volume on their favorite tune.  I am also kind of digging the lack of a tabletop equipment pod.  That takes up a lot of countertop space and always seems to be in the way.  There are two CD players racks mounted below the counter (lower left), which are almost never used.