> No worries, there are LOTS of different connectors, easy to get
> cross-connected... ;-)
> The many ships I have been on always have the ET Shop near Main Comm. Probably
> a reason for that... ;-)
> I've seen lots of different patch panels, of many types. Some surely
> had N-connectors, many did not. It's too broad of a category to
> generalize the connector types.
> I certainly didn't see anything in the early 1960's... LOL To be
> honest, most of the patch panels in my Navy were pushbuttons which
> electronically connected particular radios to a "trunk line" which then
> connected them to the appropriate antenna coupler. That panel was
> called the "SAS" panel as I recall. In the actual transmitter rooms,
> there were often many receptacles for a particular antenna, and you
> would "latch" in a cable with a latch/lock mechanism on the end of it to
> connect to a certain HF transmitter, for example. Also you often had to
> crank some handles on a coupler to get maximum efficiency out of the
> antenna (reducing VSWR "reflections").
> ... Is fire supposed to shoot out of it like that!?
> --- MultiMail/Linux v0.52
> ¡ Synchronet ¡ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
I often visited the Transmitter compartment(s).
Occasionally I would hear a call on the intercom asking to change freq on one of
the TXs and would do it for Main Comm.
The SRT-14 was my favorite rig.
I read its manual a lot of times.
There were WRT's and one TMC in that compartment with the SRT's.
Up above the Main Deck inthe UHF Room I liked the AN/GRC-17,I think it was 17
maybe 29, too long ago for Ed's Head (C) TM to remember.
It had a 4-65A in it. I liked that tube more than the 4-400 in the SRT's.
Back on topic, The panel I referred to was in Radio One , next to Main Comm.
It let different Antenn be used with the Receivers in Radio One.
My reason for writing Main Comm earlier is because I served as a Flag Messenger
and was in there mainly.
73 de Ed W9ODR . .
---
¡ Synchronet ¡ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
|