Radius M216 and GM300 error code 58
Posted: Fri Oct 09, 2015 7:37 pm
Hello:
In another post here on the bd I replied to anothers question on error 58 on the M216 and GM300 mobiles he had.
During the discussion on and off the bd he says only two radios giving the error 58 code but actualy all 10 radios had the error code with some giving the extra long error tone during power up but then went away and they do tx and rx and work fine after the power up and long error beep stops.
He did say modified code plugs as he does have 8ch uhf gm300s showing more than 8chs.
So I figured id clone in a exact matching code plug known to be good.
Did successfully retrieve two m216 mobile with that method and they tuned up to specs and tested fine per the service monitor.
However the other 8 still show error 58 bad code plug but did accept the cloned code plug and did change freqs as was in the known good code plug cloned in so its changing programmed freqs etc by clone method but cant read and get error 58 with the long error tone on power up but after error tone times out the radio will tx / rx modulate and tx wattage is seen and looking good other than needing recalibrated back on freq etc.
These radios are M216 uhf 5 pin logic bd 16ch 35 watters and the GM300 mobiles are 16ch 16 pin logic bds 40 watt uhf mobiles both are 25 kHz wide banders for gmrs and ham intentions after repair if it can be done reasonably.
Worked out a trade over the phone but wasn't aware all the radios were error 58 thought just two as he pmd me a list was only mentioned so trying to recover the code plugs rather than ditch the trade since all radios have error issues other than the two m216s I did recover from by cloning a known good code plug.
Anyone have any additional info that might help me with this ?
Id appreciate hearing some if you know something im missing.
Cant read these radios but can clone in another good code plug to change freqs though just cant read without error 58 but do tx/rx after power up with long error tone that times out after say 10 seconds and everything seems to work after that as a mobile normaly would.
Any ideas ???
Thank you
Satelite
In another post here on the bd I replied to anothers question on error 58 on the M216 and GM300 mobiles he had.
During the discussion on and off the bd he says only two radios giving the error 58 code but actualy all 10 radios had the error code with some giving the extra long error tone during power up but then went away and they do tx and rx and work fine after the power up and long error beep stops.
He did say modified code plugs as he does have 8ch uhf gm300s showing more than 8chs.
So I figured id clone in a exact matching code plug known to be good.
Did successfully retrieve two m216 mobile with that method and they tuned up to specs and tested fine per the service monitor.
However the other 8 still show error 58 bad code plug but did accept the cloned code plug and did change freqs as was in the known good code plug cloned in so its changing programmed freqs etc by clone method but cant read and get error 58 with the long error tone on power up but after error tone times out the radio will tx / rx modulate and tx wattage is seen and looking good other than needing recalibrated back on freq etc.
These radios are M216 uhf 5 pin logic bd 16ch 35 watters and the GM300 mobiles are 16ch 16 pin logic bds 40 watt uhf mobiles both are 25 kHz wide banders for gmrs and ham intentions after repair if it can be done reasonably.
Worked out a trade over the phone but wasn't aware all the radios were error 58 thought just two as he pmd me a list was only mentioned so trying to recover the code plugs rather than ditch the trade since all radios have error issues other than the two m216s I did recover from by cloning a known good code plug.
Anyone have any additional info that might help me with this ?
Id appreciate hearing some if you know something im missing.
Cant read these radios but can clone in another good code plug to change freqs though just cant read without error 58 but do tx/rx after power up with long error tone that times out after say 10 seconds and everything seems to work after that as a mobile normaly would.
Any ideas ???
Thank you
Satelite