Motorola, Airlife and the missing PL/CTCSS tones on the LaSalle, CO radio tower

[ScannerSK]

On many occasions Airlife has attempted to contact Weld County Communications on either Fire A (153.785 MHz) or Fire B (154.145 MHz). The conversation typically goes something down the line of Airlife calling Weld County Communications numerous times and Weld County replying each time while Airlife does NOT receive any of the replies from Weld County.

Why?

Some bright person at Motorola ordered the removal of the transmit PL/CTCSS tones from the LaSalle, CO tower for both Fire A and Fire B while at the same time programmed the radios in Airlife with a mandatory receive PL/CTCSS tone for both Fire A and fire B. That is a no win situation!

Motorola either needs to re-enable the transmit PL/CTCSS tone once again on the LaSalle tower for both Fire A and Fire B or they need to reprogram all the Airlife radios so they do not require a receive PL/CTCSS tone.

Hopefully, this is constructive criticism to someone out there in Motorola land who can assist with fixing this problem.

Shawn

 

[fireemt55]

Some bright person at Motorola

Contact Wireless Advanced Communications directly, Wireless Advanced Communications Evans CO Albuquerque NM, they likely are the ones who take care of this.

 

[natedawg1604]

Why isn't Airlife using a FRCC talkgroup? Also, does anyone know if any Weld County Fire agencies ever use these freqs in lieu of an FRCC talkgroup?

 

[ScannerSK]

Fire A and Fire B are used almost exclusively for fire paging, knox/lock box pages, tornado siren activation, and possibly EAS alerts.

On rare occasions a fire department or Airlife will contact Weld dispatch on either Fire A or Fire B. The fire departments do not experience any problems conversing with Weld Dispatch only Airlife. I assume Airlife was programmed with a receive PL to prevent reception of other users/towers while in flight.

Shawn