I have 2 MTS2000's, one with firmware 5.42 (I think its defiantly 5.4x), and one with firmware 6.40.
Now, this deals with low battery and Tx Disable. When a battery is low on the 5.42 version radio, it will still transmit and warn that the battery is low at the end of transmitting (i.e. Tx Low Bat Chirp). The 6.40 version radio refuses to transmit on low battery...it will Tx Low Bat Chirp and then I'll get the Tx Inhibit tone. (The radio does work with a good fully charged battery.)
This was tested on both radios, with the same low battery. Is there anyway to disable or turn off the Tx Inhibit on low battery on the MTS2000's? I have looked everywhere in the RSS and am unable to find the setting for this.
(Before someone asks, the low battery was first tested on the 6.40 radio which refused to transmit, and was then switched to the 5.42 radio which did transmit.)
MTS2000 Tx Disable
Moderator: Queue Moderator
Once the radio detects a low battery condition, there's no manual method of diabling the TX inhibit.
The best you can do is disable the warning tone.
Do you have any of the side buttons or the concentric programmed for low power?
If you do this, you can 'extend' the TX time using low power(1 watt or less), but the end result is: you will still have the radio disable TX once the battery reaches a specific level.
The only way to change the set battery indicator level, is with lab, regular RSS does not access this 'feature'.
At least my R06.07 does not.
The best you can do is disable the warning tone.
Do you have any of the side buttons or the concentric programmed for low power?
If you do this, you can 'extend' the TX time using low power(1 watt or less), but the end result is: you will still have the radio disable TX once the battery reaches a specific level.
The only way to change the set battery indicator level, is with lab, regular RSS does not access this 'feature'.
At least my R06.07 does not.
This was done to fix a low-voltage problem where the older firmware units could possibly continue transmitting after the PTT was released...with no external indication to the user that it was happening! This caused some fairly major problems on trunked systems of course, tying up repeaters for extended lengths of time. The fix was to not allow transmitting below a certain voltage threshold. It's hard-set in the firmware & cannot be changed, even with LAB. This also affected MTX8000/838 units with corresponding 1.37 (I believe) or older firmware.
Todd
Todd
No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.
Welcome to the /\/\achine.
Welcome to the /\/\achine.
My 1.52 MTX838s are happy to continue transmitting until the battery is so low that the radio reboots itself.wavetar wrote:This was done to fix a low-voltage problem where the older firmware units could possibly continue transmitting after the PTT was released...with no external indication to the user that it was happening! This caused some fairly major problems on trunked systems of course, tying up repeaters for extended lengths of time. The fix was to not allow transmitting below a certain voltage threshold. It's hard-set in the firmware & cannot be changed, even with LAB. This also affected MTX8000/838 units with corresponding 1.37 (I believe) or older firmware.
Todd
Meh, I'm unsure of the version...I do know there's a minimum version the radio has to be on several systems in New Brunswick due to the constant tx issue. I'll see if I can dig up what it is.mr.syntrx wrote:My 1.52 MTX838s are happy to continue transmitting until the battery is so low that the radio reboots itself.wavetar wrote:This was done to fix a low-voltage problem where the older firmware units could possibly continue transmitting after the PTT was released...with no external indication to the user that it was happening! This caused some fairly major problems on trunked systems of course, tying up repeaters for extended lengths of time. The fix was to not allow transmitting below a certain voltage threshold. It's hard-set in the firmware & cannot be changed, even with LAB. This also affected MTX8000/838 units with corresponding 1.37 (I believe) or older firmware.
Todd
Todd
No trees were harmed in the posting of this message...however an extraordinarily large number of electrons were horribly inconvenienced.
Welcome to the /\/\achine.
Welcome to the /\/\achine.
I have two Jedis that will TX down to reboot, and the radios are, according to firmware....
1. MTX9000: R01.51
2. MT2000: R02.13
Both will transmit right up to the point of reboot.
My MTS2000 on the other hand, is version R06.76, and it will not transmit that low, but restarts, then fails to transmit afterwards, but the receiver still functions down to just above the reboot minimum battery level.
1. MTX9000: R01.51
2. MT2000: R02.13
Both will transmit right up to the point of reboot.
My MTS2000 on the other hand, is version R06.76, and it will not transmit that low, but restarts, then fails to transmit afterwards, but the receiver still functions down to just above the reboot minimum battery level.