FM CP Logs

[fwillis]

Could someone provide me a copy of necessary log forms for EAS, tower lights, meter readings, and whatever else I will need to be totally legal, when the station actually goes on the air. A link or any help would be appreciated.

 

[TomT]

EAS: You will need to get new CAP-compliant EAS equipment. Don't know about Tri-Lithic, but both the DASDEC and Sage equipment store an internal log.

Best practice would be to print out this log periodically, and attach a cover sheet with a blank where the "chief operator" can sign and date that he checked it, and a space where anything unusual can be noted, such as if the equipment was out of commission for a day or so, or if one of the monitored sources failed to relay an RMT (for example)

Tower Lights: A sheet with blanks to show someone checked the tower lights each day & that they were working OK. Also a line to write comments if not & that FAA notified of any failure.

E.G.: Towers Lights Checked ________Morning _________Evening BY:________ Date:________
Comments_____________

Simply make your own form on a word processor. You are not required to keep a log of meter readings anymore.

 

[OKCRadioGuy]

The real question I have for the group is do we have to have operators sign and off each day anymore as part of the log? I'm a bit unclear about that...

 

[pickledfirefly]

Get a copy of the FCC Checklist for your service (AM/FM/etc).

http://transition.fcc.gov/eb/bc-chklsts/

If you cover the bases in these, you should have no problem. Also, the EAS hand book needs to be posted (and followed) once you are up and running.

http://transition.fcc.gov/pshs/services/eas/handbooks.html

Best of luck and keep it local.

 

[TomT]

No, the operators do not have to sign on and off. The "chief operator,"--which is really a clerical position, not technical, is required to check the EAS log and any other "log"--which would just be the daily check of the tower lights. Other operators can just initial your tower light log; the chief operator then should sign it to show he reviewed it.

If you have the luxury of operators, then, by all means, have whoever is there when it is dark outside check the tower lights. Would be helpful to post instructions on how to report a tower light outage to the FAA (I'm at home, so I don't have that info here). Such failures & time reported should then be described in the "comments" section of the tower light log.

The MOST IMPORTANT paperwork is the public file--fitting subject for a more elaborate post, but this should have issues lists for each quarter as well as as the other required information that they talk about in the checklists (above post).

The EAS handbook is outdated and irrelevant. Just stick the stupid thing on the wall with a nail. Latest EAS proposals from the FCC (see Daily Digest from today/11th) discuss eliminating it. Also you need a copy of the state plan in the file somewhere--assuming your state actually has a state plan.

 

[greg.hahn]

The real question I have for the group is do we have to have operators sign and off each day anymore as part of the log? I'm a bit unclear about that...

The answer is no...unless they make a log entry.

73.1800 says that anyone that makes an entry in the log has to sign the log.

"Any employee making a log entry shall sign the log, thereby attesting to the fact that the entry, or any correction or addition made thereto, is an accurate representation of what transpired."

As a general practice, however, I still require it of all my operators. But rather than having them sign the log twice, as in the old days, I make them sign their name once and print it the second time. Because as a rule I can't read their writing, and if they don't print it, I can't figure out who these guys are!

 

[Bengalsfan]

Simply make your own form on a word processor. You are not required to keep a log of meter readings anymore.

However, it's not a bad idea. Good way to tell if things are beginning to drift out of tolerance. If the FCC follows up on a complaint, you have to prove you are operating within your licensed parameters. Logging meter readings, along with common point current and antenna monitor readings insure you catch it before someone else does and calls the enforcement bureau.

 

[TomT]

Common point? This is an FM CP. Unless the transmitter is really ancient, good enough to take a series of readings when installed, stick them near the transmitter, & check parameters every so often.

 

[nd2023]

If you have the luxury of operators, then, by all means, have whoever is there when it is dark outside check the tower lights. Would be helpful to post instructions on how to report a tower light outage to the FAA (I'm at home, so I don't have that info here). Such failures & time reported should then be described in the "comments" section of the tower light log.

That's assuming the studio is close enough to the tower site that people can actually see the entire tower from the parking lot. It does no good if the studio is 30 miles from the tower site.

 

[reelyreal]

If you have the luxury of operators, then, by all means, have whoever is there when it is dark outside check the tower lights. Would be helpful to post instructions on how to report a tower light outage to the FAA (I'm at home, so I don't have that info here). Such failures & time reported should then be described in the "comments" section of the tower light log.

That's assuming the studio is close enough to the tower site that people can actually see the entire tower from the parking lot. It does no good if the studio is 30 miles from the tower site.

You don't have to be able to physically see the tower to "check" the tower lights. Any engineer worth a lick has the lights connected to their remote control for easy checking.

 

[Bengalsfan]

Common point? This is an FM CP. Unless the transmitter is really ancient, good enough to take a series of readings when installed, stick them near the transmitter, & check parameters every so often.

Unless things have changed since the last time I checked, AM stations do have common point readings. Correct? While I know this is in reference to an FM question, I was using that as an example of things to check on a regular basis. And if you are going to check the parameters "every so often", why not write them down for reference? Might come in handy when you are standing in front of a cold transmitter and no idea why. Logs have helped me on more than one occasion in figuring out what when wrong.

 

[greg.hahn]

If you have the luxury of operators, then, by all means, have whoever is there when it is dark outside check the tower lights. Would be helpful to post instructions on how to report a tower light outage to the FAA (I'm at home, so I don't have that info here). Such failures & time reported should then be described in the "comments" section of the tower light log.

That's assuming the studio is close enough to the tower site that people can actually see the entire tower from the parking lot. It does no good if the studio is 30 miles from the tower site.

You don't have to be able to physically see the tower to "check" the tower lights. Any engineer worth a lick has the lights connected to their remote control for easy checking.

By the way- apparently there are a lot of engineers that aren't worth a lick. Because not only do they have to be connected to the remote control, FCC rule 17.49 states that the circuit must be designed "to register any failure of such lights, to insure that all such lights are functioning properly as required."

That means it should be designed so that if 1 side marker bulb goes out, you should be able to tell it.


It seems a lot of guys just connected the sensor that worked fine in 1974 to their new, fancy dial up remote control they bought in the 90s. Back in the 70s you had an analog meter, and could see the current changing. The dial up kind captures an instantaneous sample, and that's it. How are you going to tell if you have a light out?

These work well: Sine Systems ACM-2

 

[greg.hahn]

Common point? This is an FM CP. Unless the transmitter is really ancient, good enough to take a series of readings when installed, stick them near the transmitter, & check parameters every so often.

Unless things have changed since the last time I checked, AM stations do have common point readings. Correct? While I know this is in reference to an FM question, I was using that as an example of things to check on a regular basis. And if you are going to check the parameters "every so often", why not write them down for reference? Might come in handy when you are standing in front of a cold transmitter and no idea why. Logs have helped me on more than one occasion in figuring out what when wrong.

I totally agree. I'm a big fan of logging lots of meter readings at every weekly inspection so I can spot trends.

The operators back at the station only take meter readings that make sense. For instance, I just took over some stations, and on the stations with a solid state transmitter, I told them they could stop taking PA voltage and PA current readings. I never really cared or paid attention to what they were writing down, so why write it down?

So they check power output, tower lights, and for AMs, antenna current and directional parameters.

And I added a new meter reading: Room temperature. Now there is a useful meter reading!

And guess what? 3 days after I began that practice in that market, it turned real cold and the new air conditioners for the transmitter building froze up. It's 15 degrees outside, and the jocks are calling and letting me know that it's 90 in the transmitter building!

We got somebody up there to fix things before we incurred damage on a brand new transmitter. I'm mighty glad I had those guys checking that!

 

[TomT]

My thought was to take a full set of readings when the transmitter is installed--leave them at the site. Then check against them every time you are out. No need to have reams of readings--you'll notice when something is off.

Relying on the "operators"--assuming you even have this luxury--is useless. Most places this is minimum wage help. Or highly paid with a bigger ego attached. Local cluster has two AM's--one not audible at the studio at night. Went off the air one day. Operator dutifully wrote down "0--0--0" for readings.

Makes more sense to have remote call call you when something goes out of parameters.

With trend towards the concrete shelters--with no ventilation--having temperature sensor makes sense. Especially with tube transmitters being kept cool by air conditioners. Again--have the remote control call you--though it's nice if someone else would catch it.

 

[greg.hahn]

Relying on the "operators"--assuming you even have this luxury--is useless.

I agree it can be, but it doesn't have to be. WHIO in Dayton, Ohio has some of the best trained operators that I've seen in 30 years. The management there takes the time to teach them what they need to know and hold them accountable for the work they are being paid to do.

Just as the board ops of any station are fully expected by management to make sure things keep playing on the air, on time, that all spots play, that show prep gets pulled for the morning show, etc, etc, etc, board ops there are actually expected to read the meters, decide if the meter reading is acceptable, and log them. And they do it.

They aren't highly paid, technical geniuses. But the system is made so that they can do it, and the meter readings are included in the list of expectations we have of them as a transmitter operator.

In fact, the remote control would have called the engineering staff next, but first it called the hotline, and the operator called the engineering staff himself.

It can be done.

 

[WNTIRadio]

I have remote controls at many sites that will call me if something goes out of parameter. I can set a high/low range with both a "warning" alarm and then a critical alarm. So if the Tx is set for 5kW, it calls me if it goes below 90% power or above 103%. I know I have until 105%, but I like to build in a margin of error on the overpower side.

Same goes for the tower lights. Have a current monitor and a value set in the remote. It'll call me if it goes down while the lights are on (have the alarm disabled during the daylight hours).

It's nice to have jocks looking at the readings just to have them take some responsibility for the operation. But at the same time, the remote only calls me if there's a real problem. And the new Burk units I've put in will also email me, and I can log in from my phone to check readings, turn things on and off etc. I have a Nautel that has direct IP access.

This day and age, I don't see the need for reams of paper logs.

 

[greg.hahn]

This day and age, I don't see the need for reams of paper logs.

So if someone comes in and finds that your remote control is miscalibrated by 4%, and your 102 is really 106, how do you prove it hasn't been like that for a year or more?

If the power fails and the generator doesn't start, how do you document to your employer that the generator has been checked every week and was working as recently as last Friday?

You can do 50 sheets a year for a transmitter site to document that you are doing your job. Or you can do 12 sheets a year, one a month, to include less information but still document what you do.

I think to neglect keeping a paper log is very unwise.

I used to contract for a guy. I did one sheet a month for his sites, with a column for each weekly inspection. When I sent him a bill, I included a PDF of the log sheet. He loved it. It showed him I was actually looking at his stuff. It gave him something to put in his files to prove he was trying to do the right thing. Now maybe the question will never come up. But if it does, he's not caught empty-handed.

For 50 cents worth of paper per year... it's a smart thing to do.

 

[ChiefEngineer]

We put our transmitter info with our EAS logs. Part is my vision problems and help from a secretary. This keeps it all handy when Charlie visits.

 

[WNTIRadio]

I didn't say not to use a single sheet of paper or two a month to check things... I have a log book at every TX site that I write everything down in when I visit them. All TX parameters, remote control calibration, tower lights (when applicable), generator (when applicable) even inside and outside temperature.

What I was speaking of was reams of paper where the jocks are taking readings every single hour. If the remote control is not calibrated, then those won't be worth anything anyway, since they will most likely be taking readings from said remote. That's a waste of time to me. The remote is more descriptive and more accurate when it calls me on a weekend than, "Uh, I think we're off the air. Okay maybe not. Wait, which channel again do you want me to go to? Huh? We have one of those? Ohhhh, right." etc etc.

I can log in or call in and get the whole scoop. And if something does drift out, it'll let me know as soon as it happens.

 

[TomZ]

I would like to have a linear log to help me decide what happened....
http://www.datataker.com.au/DT80M.php

The 'live demo' link is what I'm wanting.... not weather, though......