"ALARM: Not Authorized" during Oquirrh Mt Temple Dedication

Discussions around the satellite system and video distribution.
wcook-p40
New Member
Posts: 4
Joined: Tue Aug 25, 2009 6:10 am
Location: Elk Ridge, Utah, USA

"ALARM: Not Authorized" during Oquirrh Mt Temple Dedication

Postby wcook-p40 » Tue Aug 25, 2009 6:26 am

During the Sunday 3:00PM Mountain Time broadcast of the Oquirrh Mountain Template Dedication, the transmission froze for a few seconds and then blacked out completely. Each time the screen showed the message:

ALARM: Not Authorized

The message stayed on the screen for about 5 seconds, then went away and a few seconds later the transmission would continue. This happened 4 times.

So ...
- did anyone else see this message?
- is this an indication of a problem?
- could it be a problem with our satellite equipment?

Thanks

Wes

User avatar
aebrown
Community Administrator
Posts: 14693
Joined: Tue Nov 27, 2007 8:48 pm
Location: Sandy, Utah

Postby aebrown » Tue Aug 25, 2009 7:56 am

wcook wrote:During the Sunday 3:00PM Mountain Time broadcast of the Oquirrh Mountain Template Dedication, the transmission froze for a few seconds and then blacked out completely. Each time the screen showed the message:

ALARM: Not Authorized

The message stayed on the screen for about 5 seconds, then went away and a few seconds later the transmission would continue. This happened 4 times.

So ...
- did anyone else see this message?
- is this an indication of a problem?
- could it be a problem with our satellite equipment?


We received the 3:00pm MDT broadcast with no problems. It definitely was not a problem with the broadcast in general.

It could well be a problem with your satellite equipment. Temple dedication broadcasts are encrypted, and each satellite receiver has to be configured to receive encrypted broadcasts. That's why we had to communicate with the Temple Department to let them know our property number and satellite receiver ID before the Draper Temple dedication (and the same list of receivers was used by default for Oquirrh Mountain). If a receiver was not on the list, it would not have been authorized to receive the encrypted transmission.

It sounds like something wasn't quite right in how your receiver handled the encrypted transmission, and thus it reported it was not authorized. But it seems that it must have been authorized, or you wouldn't have been able to see the broadcast at all. So I would recommend that you report the issue to your FM Group so they can determine if your equipment needs to be repaired.

russellhltn
Community Administrator
Posts: 20779
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Tue Aug 25, 2009 10:41 am

What other messages came up? If the receiver lost the signal, it would have gone though a number of steps. That message would appear after it acquired the signal but before it received the authorization packet.

The culprit could be a weak signal, or a antenna that isn't aimed quite right and is picking up a signal from an adjacent satellite. In the latter case the problem will be dependent on the schedule of the other satellite which would result in seemingly random good sessions and bad sessions. (The thing to watch for is if the problem starts or ends close to the top or bottom of the hour.)
Have you searched the Wiki?
Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.

wcook-p40
New Member
Posts: 4
Joined: Tue Aug 25, 2009 6:10 am
Location: Elk Ridge, Utah, USA

Postby wcook-p40 » Tue Aug 25, 2009 1:26 pm

It happened at about: 2:40, 3:20, 3:55 and 4:10.
And there were no other messages shown.

User avatar
mkmurray
Senior Member
Posts: 3241
Joined: Tue Jan 23, 2007 9:56 pm
Location: Utah
Contact:

Postby mkmurray » Tue Aug 25, 2009 2:32 pm

wcook wrote:It happened at about: 2:40, 3:20, 3:55 and 4:10.
And there were no other messages shown.

Wow, that's an interesting trend (40 mins, 35 mins, 25 mins)...Could there be an overheating issue or something that causes it to quickly reset?
Many questions are already answered on the LDSTech wiki. Check it out!

russellhltn
Community Administrator
Posts: 20779
Joined: Sat Jan 20, 2007 2:53 pm
Location: U.S.

Postby russellhltn » Tue Aug 25, 2009 2:40 pm

mkmurray wrote:Wow, that's an interesting trend (40 mins, 35 mins, 25 mins)...Could there be an overheating issue or something that causes it to quickly reset?


I know our system is powered up 24/7, so I wouldn't expect to see a trend like that if it was overheating.
Have you searched the Wiki?

Try using a Google search by adding "site:tech.lds.org/wiki" to the search criteria.

wcook-p40
New Member
Posts: 4
Joined: Tue Aug 25, 2009 6:10 am
Location: Elk Ridge, Utah, USA

Postby wcook-p40 » Tue Aug 25, 2009 2:41 pm

After the third time, it was looking like about every 40 minutes or so. Then that last one came only 15 minutes after the previous occurrence. However, the meeting went until about 4:30 and it did not show the error in the last 20 minutes or so.

lajackson
Community Moderators
Posts: 6148
Joined: Mon Mar 17, 2008 9:27 pm
Location: US

Postby lajackson » Tue Aug 25, 2009 7:07 pm

wcook wrote:And there were no other messages shown.


This is usually a signal strength issue. If your receiver is borderline during normal broadcasts, you will have issues with any restricted broadcast. Do you have this problem with the priesthood session of general conference?

Other than that, the FM Group is the place to start. And they will probably start by checking the dish alignment.

wcook-p40
New Member
Posts: 4
Joined: Tue Aug 25, 2009 6:10 am
Location: Elk Ridge, Utah, USA

Postby wcook-p40 » Wed Aug 26, 2009 7:40 am

Do you have this problem with the priesthood session of general conference?

No, that has always gone smoothly. This is the first time I've seen this message on any broadcast.

I called my FM group. They said to just call the number on the equipment.

By the way, thanks for all the quick responses. This is a great resource!


Return to “Satellite”

Who is online

Users browsing this forum: No registered users and 2 guests