Users may not create topics, posts, or private messages containing or relating to the following material (especially pertaining to Motorola copyrighted software, unless you want Motorola to come along and shut this site down):

You can backdate the firmware to version 9 or 10 where after you turn power on and off to the radio about a dozen times and the authentication key will be dropped automatically, it must have been a customer feature request.

Or your can overwrite with a useless key for the purpose of not having the key in the radio that was sent to the auth server.

Never heard a reason beyond wanting extra protection that would require zeroize the auth key.

CoM

If the lights are out when you leave the station and then come on the second you key up, you know you have enough power.

In this particular instance it was to verify that the system was actually challenging subscribers for authentication after a 7.17 upgrade, but it could (will) become an issue when we start sending radios to surplus.

When exposed to Rapid Fire Growth or Thermal Emergency, two things are lost:1. Ability to use fine motor skills2. Presence of mind

We operate in restricted/forced full-time. We specifically wanted to see the difference in behavior and notification between a radio that had a mismatched key and a radio that had no key at all (there is no system notification for a radio attempting affiliation with no key, which was elevated to the infrastructure group.)

When exposed to Rapid Fire Growth or Thermal Emergency, two things are lost:1. Ability to use fine motor skills2. Presence of mind

Sorry, should've clarified... the radio will alert and display when authentication fails (if programmed to do so) but UEM will only generate a notification when a radio attempts authentication with a mismatched key, not with no key at all.

When exposed to Rapid Fire Growth or Thermal Emergency, two things are lost:1. Ability to use fine motor skills2. Presence of mind