Page 1 of 1

MTX8000 receive problem

Posted: Sat Feb 22, 2003 5:05 am
by OX
On conventional channels, my radio stops listening to the channel after about 5 seconds. BUT, if I enable the monitor mode (I've got monitor setup for silent mode) by holding monitor for 2 seconds, it will listen until the cows come home. I reprogrammed the channel to CSQ and the same thing happens. I was thinking it might be the battery saver being enabled but I checked and it's disabled.

(by saying 'not listening', it will not unmute the speaker when it is receiving a signal indicated by the flashing LED)

TX/RX/PL are matched in both radios and again, it happens regardless of CSQ or PL/DPL usage.

Got any ideas?

Posted: Sat Feb 22, 2003 5:15 am
by RESCUE161
Did you try the 'Unmute/Mute Type' function? Under the conventional pres menu, go to 'more options'. Or could it be a scan problem? Is the pers assosciated with a scan list? I'm grasping at straws here...
Scott

Posted: Sat Feb 22, 2003 6:02 am
by RocketNJ
Also maybe the radio needs an alignment? And check the squelch settings. I've een them defailt to a very high threshold.

George

Posted: Sat Feb 22, 2003 11:28 am
by OX
Scan is disabled on my conventional modes and scan is turned off before switching to conventional.

Squelch is not an issue, however I bumped the numbers down by about 4.

Tuning, I doubt it. It receives fine in trunked mode and again, within 5 seconds of transmitting.

I checked the muting and it was set at 'standard'. I changed it to 'unmute, or mute' to match the MTS that I have right next to it. Still no go. The speaker will not unmute while receiving with the exception of having monitor turned on or within five seconds of transmitting.

I swear it sounds like a battery saver issue which is disabled. Literally, you let go of PTT and count to 5 and it won't unmute. And if it receives within the 5 seconds after releasing PTT, it will work fine until 5 seconds after loss of carrier.

I reloaded a backed up codeplug from some time ago (before this started happening) and it still does it.

******EDIT******

Figured it out, it was something screwy in the codeplug. This time I took a backed up codeplug from last year and used the F4 write option instead of the normal F8 write to radio and that fixed that little problem right up.