The AM Forum
March 29, 2024, 05:16:13 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Calendar Links Staff List Gallery Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Guardian X-300-ER Overload Relay  (Read 2169 times)
0 Members and 1 Guest are viewing this topic.
kc2we
Member

Offline Offline

Posts: 138


« on: March 28, 2018, 04:47:16 PM »

Does anyone have a data wiring sheet for the guardian E-300-ER overload relay?  It has a 250-750 ma trip coil and
a 6.3 V reset. Not quite sure how to attach the DC load to the trip coil. there's a WW pot across the trip coil. Seth KC2WE
kc2we (at) arrl dot net


* x-300-er.JPG (39.16 KB, 320x240 - viewed 335 times.)
Logged

Seth Taylor
Opcom
Patrick J. / KD5OEI
Contributing
Member
*
Offline Offline

Posts: 8308



WWW
« Reply #1 on: March 29, 2018, 06:49:02 PM »

I have something like this in a transmitter. Same brand, maybe the same model. It works perfectly. The screen current from the screen voltage supply (-) side passes through the trip coil to GND, which keeps high voltages off the coil.

The pot, connected as a rheostat, reduces the sensitivity (increases trip current) as its resistance is lowered. Mine's set to 160mA to protect a 4-1000 screen. The schematic of that part of the transmitter is shown. One sets the trip point rheostat by attaching a load that draws a known current and turning the pot until it trips.

The latching relay is shown in the 'tripped' or unlatched position.


* overload-relay.png (161.75 KB, 1377x765 - viewed 395 times.)
Logged

Radio Candelstein - Flagship Station of the NRK Radio Network.
kc2we
Member

Offline Offline

Posts: 138


« Reply #2 on: March 30, 2018, 08:47:11 PM »

Tnx for the details. I'll use it on my next tube project. Seth KC2WE
Logged

Seth Taylor
Pages: [1]   Go Up
  Print  
 
Jump to:  

AMfone - Dedicated to Amplitude Modulation on the Amateur Radio Bands
 AMfone © 2001-2015
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines
Page created in 0.049 seconds with 18 queries.