AC33 Frequencies

[theaton]

I recieved an anonymous submission listing the following changes that need to be made in the AC33 system, possibly representing rebanding:

Delete 867.2500, 866.3500, 866.0750, 867.2500, 857.4875

Add 859.4875, 859.2375, 858.4875, 857.9625, 857.9625, 857.2375, 855.4875

Would anyone like to confirm or deny these changes?

-Tim

 

[qlajlu]

I received an anonymous submission listing the following changes that need to be made in the AC33 system, possibly representing rebanding:

Delete 867.2500, 866.3500, 866.0750, 867.2500, 857.4875

Add 859.4875, 859.2375, 858.4875, 857.9625, 857.9625, 857.2375, 855.4875

Would anyone like to confirm or deny these changes?

-Tim

This is news to me. Give us a couple of days and keep checking back. I'm sure this bunch of guys will do it justice.

 

[gldavis]

857.9625 is listed twice for adding. Typo?

A quick look at "my master trunk list" shows:
867.2500 no listing
866.3500 UCAN Site 43 control
866.0750 no listing
867.2500 no listing
857.4875 AC33 SLC PS active
859.4875 3521 Airport active
859.2375 3521 Airport active
858.4875 3521 airport active
857.9625 AC33 SLC PS active
857.2375 AC33 SLC PS active
855.4875 3521 Airport active

I'll set trunker up and let it run for a couple of days and see waht it shows.

 

[theaton]

AC33 changes

857.9625 is listed twice for adding. Typo?

Add 858.2625 instead. Submitter also says AC33 is now a three-site simulcast system.

 

[bneilson]

So as of right now AC33 (Site 1) is showing the following in use as per Uni-Trunker:

855.2375
856.4875
856.9625
857.2375
857.4875
857.9625
858.2375
858.9625
859.2625
859.9625
860.2375
860.2625 BCC
860.4875 BCC
860.7625 BCC
860.9625 CC

 

[theaton]

AC33 Changes

Using the current db listings, the proposed changes, and bneilsen's report, here's a summary of the AC33 frequencies:

855.2375 Listed & active
855.4875 Listed
856.4875 Listed & active
856.9625 Listed & active (Ctrl?)
857.2375 Listed & active (but listed for addition??)
857.4875 Listed & proposed for deletion
857.9625 Active & proposed for addition (added)
858.2375 Listed & active
858.2625 Proposed for addition
858.4875 Proposed for addition
858.9625 Listed & active
859.2375 Proposed for addition
859.2625 Listed & active
859.4875 Proposed for addition
859.9625 Listed & active
860.2375 Listed & active
860.2625 Listed & active (Alt)
860.4875 Listed & active (Alt)
860.7625 Listed & active (Alt)
860.9625 Listed & active (Ctrl)
866.0750 Listed & proposed for deletion
866.3500 Listed & proposed for deletion
867.2500 Listed & proposed for deletion

Since 857.9625 was proposed for addition and found to be active, I went ahead and added it. I'll wait for further confirmation before making other changes. Please keep listening.

I added a new AC33 group for patches from UCAN. Do these patches always come through with the same TG# as on UCAN? I'm happy to entertain ideas on this listing.

-Tim

 

[qlajlu]

I'm getting a little confused here...course that shouldn't really surprise anyone who knows me...but would someone remind me what the cutoff threshold is for rebanding. gldavis keeps saying the the AC33 system won't be affected by rebanding because all their frequencies are below the threshold and from what I see in this recent post by theaton that statement seems to be very solid, but I would still like to know where the cutoff is.

Also, will the Airport TRS be affected by rebanding? At this point I'm thinking probably not. I guess I could use the 800 MHz Transition Administrator Web site and run the Airport's call sign, couldn't I?

 

[gldavis]

AC33 is not in the freq range for Rebanding. Having said that, we need to keep in mind that AC33 and the airport 3521 are in the process of consolidating. this will require the re-arrainging of freqs that were being used, and the new freqs to be used. I don't know what changes are in store, nor when the "complete" change over will occur, and it has been said in the forum that the job will not be complete till mid/late this year. The "anonymous submission" may reflect a future change. We will have to wait and see.