146.52 in Las Vegas

[N9JIG]

Las Vegas net simulcast on 146.520. Why?

As we were driving in the Las Vegas NV area this morning i was listening to 146.520 and was chatting with a couple guys here and there. All of a sudden a net came up that was apparently simulcasted from a UHF repeater and that was the end of our little itinerant chit-chat.

I didn't catch what club it was with this net but it sounded like they had at least a UHF repeater active as well as a 2M repeater going, according to references from Net Control. The question of the day was defunct automobile manufacturers.

Why on earth would they use 146.520 for a net like this, especially in a city the size of Vegas? If they wanted to have a VHF Simplex frequency they could have chosen from any of dozens and left 146.520 to the use it is commonly used for. We had a nice 4-way QSO going until this net came up and took over.

 

[Flyham]

As we were driving in the Las Vegas NV area this morning i was listening to 146.520 and was chatting with a couple guys here and there. All of a sudden a net came up that was apparently simulcasted from a UHF repeater and that was the end of our little itinerant chit-chat.

I didn't catch what club it was with this net but it sounded like they had at least a UHF repeater active as well as a 2M repeater going, according to references from Net Control. The question of the day was defunct automobile manufacturers.

Why on earth would they use 146.520 for a net like this, especially in a city the size of Vegas? If they wanted to have a VHF Simplex frequency they could have chosen from any of dozens and left 146.520 to the use it is commonly used for. We had a nice 4-way QSO going until this net came up and took over.

I came across this link, http://www.lvrac.org/reptlist.pdf, but nothing stood out. Otherwise I would assume (i know i know) that perhaps they have a 2 meter simplex remote base tied to that particular UHF Repeater?

 

[W3DMV]

Sorry about your experience which is becoming common now days. It's a shame the
operators didn't monitor your activity before starting operations.
For some reason, many people can not comprehend the idea of a calling
frequency.
My major agitation here is during VHF type contests, operators sit on big mountain
tops and operate contests, thus rendering the frequency useless to other users. ARRL
has always asked participants to avoid the common calling frequencies due to this
problem to no avail. We also have several ops's here in the east who think it's
really neat to orbit in their airplane at 5,000 feet and tie up half the east coast while
making endless contacts to their pleasure.
The list get's long. Used to have a rig on 10 meter FM and listened on 29.6. Upon
establishing contact, moved to a idle simplex frequency to continue the conversation
and free up the channel for others to call. The rig got removed and discarded after
some guy in Nebraska running a 250 watt remote base had the frequency occupied
for several hours.
Little different world out there now days and when I go to club meetings there are
perhaps 30 cars in the parking lot, but myself and only one or two others have any
antennas.
My last FM mobile disappeared over a year ago when some op in central New Jersey
told me to get off his frequency after I placed a short call on 52 to a mobile several miles
ahead of me on the Jersey Turnpike. The ten minute blurb he gave me was not
suitable for public release.
Most of us here who still have mobile rigs now operate on SSB/CW while mobile and got away from the channelized operation that has now days deteriorated the former pleasure of making contacts
on the road.
Good luck and hope you have a better experience on your next trip...
---

 

[N9JIG]

My assumption was that the Net Controller was talking on both 146.520 and the repeater at the same time. I could occasionally hear other simplex check-ins to the net but it wasn't rebroadcasting repeater traffic onto 146.520. They obviously did not check for existing traffic on .520 or they would have heard us.

 

[autovon]

http://forums.radioreference.com/nevada-radio-discussion-forum/252056-146-52-las-vegas.html

 

[PJH]

Since this thread won't die----

I think way back to the OP and to another user in a similar thread, http://forums.radioreference.com/am...as-net-simulcast-146-520-why.html#post2496957 Bryan makes the point that everyone danced around, especially the LV guys.

Its not so much the "rag chewing" on .52 that's the issue, but you have a 100+ watt blowtorch repeating the UHF repeater and other links ONTO .52 which blows out the mobile users.

ERP + HAAT = Will wipe out most mobile simplex users. Its as simple as that.

I come from the land of an infamous 10 meter repeater on the east coast I can still hear it in the Rocky Mountains. Granted its a coornated repeater, but does a station that is licensed for it 10 states away need to be blown out of the water with it listening to NY/NJ traffic?

Prob not, but it is fun at times...

But, back to the issue at hand - as Hooligan eluded to - if Joe Ham Backpacker is trying to call on .52 on a 5ish watt HT for help of some sort and the Gigawatt remote base from 100 miles away is killing the signal....

 

[br0adband]

This thread about activity on 146.52 MHz has had more activity than 146.52 MHz has, go figure.

 

[SCPD]

There at least 3 that I know of that cross band from 52.

 

[N9JIG]

I wasn't aware of the prior thread that this was apparently merged with, I had posted it in the Ham Radio forum, where I thought it belonged.

Regardless, it seems I am not alone in my dislike of the situation but there seems to be little that can be done to fix it except complain so that's what I did!

I feel better now.

 

[bill4long]

Its not so much the "rag chewing" on .52 that's the issue, but you have a 100+ watt blowtorch repeating the UHF repeater and other links ONTO .52 which blows out the mobile users.

Agreed. That's ridiculous.

 

[KD8DVR]

Things you never do on .52

1: Rag Chew
2: Put any voip node (echolink, allstar, etc)
3: Have a net.

Seems like one or more of those unwritten rules have been broken. Of course, I'd expect nothing less.

 

[bill4long]

Things you never do on .52

1: Rag Chew
2: Put any voip node (echolink, allstar, etc)
3: Have a net.

Seems like one or more of those unwritten rules have been broken. Of course, I'd expect nothing less.

I don't see the problem with any of those as long as sufficient pauses are donet to ensure that anyone can break in. Hams are never going to agree on 146.52. To each his own.

 

[com501]

How about if I put a P25 repeater on there? With a 1 meg offset? There ARE some things that just need to be somewhere else. I spend one day a week listening to some goofballs chewing on .52 so close to each other's dekey that I can never get a word in between them. Even with a 110w mobile they can't seem to hear me. Of course, they apparently are 3 miles from each other......

 

[bill4long]

How about if I put a P25 repeater on there? With a 1 meg offset? There ARE some things that just need to be somewhere else. I spend one day a week listening to some goofballs chewing on .52 so close to each other's dekey that I can never get a word in between them. Even with a 110w mobile they can't seem to hear me. Of course, they apparently are 3 miles from each other......

Right. However one uses 52 it should always be done with a mind toward the fact that it is commonly understood to be a calling frequency, and that any breaking stations should have ample opportunity to be acknowledged and allowed to make their call.

 

[com501]

Right. However one uses 52 it should always be done with a mind toward the fact that it is commonly understood to be a calling frequency, and that any breaking stations should have ample opportunity to be acknowledged and allowed to make their call.

+1 on that.