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
Radius M216 and GM300 error code 58
Moderator: Queue Moderator
Re: Radius M216 and GM300 error code 58
Hello:
Additional info that's now available to add to the above issues:
Grabbed one of the Radius M216 UHF 16ch 40 watt mobiles with the factory 5 pin logic bd HLN5173B.
Radius mobile model number D44LRA7PA5AK
Thought it was possible someone prior to the bd member here that owns these radios may have changed bds or eproms or even possibly tried the blanking to make a maxtrac out of the m216 or even possibly reinitiated with wrong info.
First thing I did was grab the worst error 58 coded radius m216 and check its inside bds and components against the factory build specs.
Has the correct rf bd and has the correct 5 pin logic bd HLN5173B and also has the proper Eprom version 4.00 for a 5 pin bd.
If anyone here is familiar with the 16 pin logic bd HLN9313 then think of the above 5 pin logic bd the same features as a 16 pin but only real difference is its a 5 pin not the coveted 16 pin logic bd so 2nd best bd out there and not a terribly bad bd since it is basicly a 16 pin bd but with 5 pin output only.
Ok that all checked out so I figured with the long error tone and error 58 and radio does tx rx and wattage and modulation along with sensitivity seemed to be in working order but needed a good recalibration that id simply blank the radio and reinitiate and see what I got back in test results.
Went through the blanking reinitiation procedure with only one hick cup but otherwise radio reinitiated fine.
The hick up was during the reinitiation at the radios oscillator table input info.
The oscillator crystals number info was intact on the crystal (4509 9964) but the calibration tuning number info was not anywhere on the rf bd but write tag was there but looks like the m tech never ever wrote the info on it so no way to know the compensation value needed for exact setup.
So what I did was looked at my list of on record oscilator crystal numbers and its compensation values and noticed a pattern and took an educated qeustimate at what the compensation value might have been to get me in the ball park and figured my save might just be final warping during freq programming onto dead center of freq.
Well the oscillator known numeric value is 4509 9964 and comparing my info I have been saving just for this very type of recovery I came up with an oscillator compensation value of 271 4178.
After complete reinitiation and doing the best I could with what I had to deal with I programmed the radio to a gmrs freq for testing and to my surprise the radio has now passed radio test on power up no error tones no error code 58 and my fisrt look at the test frq landed only 6 kHz away for a qeuss on the compensation value I entered.
To say the least I WAS STOKED NOW
Did a final freq calibration by warping the freq back on dead center deviation and checked wattage set it at 35 watts modulation was perfect and rx sensitivity was hot as all get out on rx.
Cant argue with that in my books - that's as good as it gets for specs.
So radio did have a messed up code plug that im sure screwed the correct check sum causing all this but for the life of me I couldn't find where it was in the code plug and I looked hard but came up empty handed.
But blanking and reinitation does bring the radios back to normal crrect operating features along with a good complete recalibrated reintiation procedure.
So I can recover the M216s as I see it now.
But as those of you in the know - the gm300 and m120 mobiles if blanked by rss as I seem to recall can not be reinitiated by its correct rss without some issues and believe I read you might have to reinitiate as a maxtrac but make modifications to get the rx audio back as its missing after making it a maxtrac due to the logic bds differences.
So my question im asking now is .
Has anyone blanked a Radius M120 or GM300 with maxtrac blanking program and reitiated with correct rss for the radio and did it work for you ?
Was there any issues I should know about before doing it by blanking totally as to reinitiating ?
Im aware of wavetars hex editing method but im not up to speed on hex editing and would like to take the safe way that I do know if possible.
I really would like to see a write up as to a step for step method for changing the code plugs info by hex editing for a GM300 and or M120 as I believe after catching onto to how you actualy use a hex editing program to do it would really be nice to know but id need a write up of how its done as a ITS DONE LIKE THIS DUMBY
Thank you
Satelite
Additional info that's now available to add to the above issues:
Grabbed one of the Radius M216 UHF 16ch 40 watt mobiles with the factory 5 pin logic bd HLN5173B.
Radius mobile model number D44LRA7PA5AK
Thought it was possible someone prior to the bd member here that owns these radios may have changed bds or eproms or even possibly tried the blanking to make a maxtrac out of the m216 or even possibly reinitiated with wrong info.
First thing I did was grab the worst error 58 coded radius m216 and check its inside bds and components against the factory build specs.
Has the correct rf bd and has the correct 5 pin logic bd HLN5173B and also has the proper Eprom version 4.00 for a 5 pin bd.
If anyone here is familiar with the 16 pin logic bd HLN9313 then think of the above 5 pin logic bd the same features as a 16 pin but only real difference is its a 5 pin not the coveted 16 pin logic bd so 2nd best bd out there and not a terribly bad bd since it is basicly a 16 pin bd but with 5 pin output only.
Ok that all checked out so I figured with the long error tone and error 58 and radio does tx rx and wattage and modulation along with sensitivity seemed to be in working order but needed a good recalibration that id simply blank the radio and reinitiate and see what I got back in test results.
Went through the blanking reinitiation procedure with only one hick cup but otherwise radio reinitiated fine.
The hick up was during the reinitiation at the radios oscillator table input info.
The oscillator crystals number info was intact on the crystal (4509 9964) but the calibration tuning number info was not anywhere on the rf bd but write tag was there but looks like the m tech never ever wrote the info on it so no way to know the compensation value needed for exact setup.
So what I did was looked at my list of on record oscilator crystal numbers and its compensation values and noticed a pattern and took an educated qeustimate at what the compensation value might have been to get me in the ball park and figured my save might just be final warping during freq programming onto dead center of freq.
Well the oscillator known numeric value is 4509 9964 and comparing my info I have been saving just for this very type of recovery I came up with an oscillator compensation value of 271 4178.
After complete reinitiation and doing the best I could with what I had to deal with I programmed the radio to a gmrs freq for testing and to my surprise the radio has now passed radio test on power up no error tones no error code 58 and my fisrt look at the test frq landed only 6 kHz away for a qeuss on the compensation value I entered.
To say the least I WAS STOKED NOW
Did a final freq calibration by warping the freq back on dead center deviation and checked wattage set it at 35 watts modulation was perfect and rx sensitivity was hot as all get out on rx.
Cant argue with that in my books - that's as good as it gets for specs.
So radio did have a messed up code plug that im sure screwed the correct check sum causing all this but for the life of me I couldn't find where it was in the code plug and I looked hard but came up empty handed.
But blanking and reinitation does bring the radios back to normal crrect operating features along with a good complete recalibrated reintiation procedure.
So I can recover the M216s as I see it now.
But as those of you in the know - the gm300 and m120 mobiles if blanked by rss as I seem to recall can not be reinitiated by its correct rss without some issues and believe I read you might have to reinitiate as a maxtrac but make modifications to get the rx audio back as its missing after making it a maxtrac due to the logic bds differences.
So my question im asking now is .
Has anyone blanked a Radius M120 or GM300 with maxtrac blanking program and reitiated with correct rss for the radio and did it work for you ?
Was there any issues I should know about before doing it by blanking totally as to reinitiating ?
Im aware of wavetars hex editing method but im not up to speed on hex editing and would like to take the safe way that I do know if possible.
I really would like to see a write up as to a step for step method for changing the code plugs info by hex editing for a GM300 and or M120 as I believe after catching onto to how you actualy use a hex editing program to do it would really be nice to know but id need a write up of how its done as a ITS DONE LIKE THIS DUMBY
Thank you
Satelite
Re: Radius M216 and GM300 error code 58
Hello:
All ten radios sent for error 58 rss code plug errors and the long error tone upon power on have now been recovered and in working order.
So no longer in need of information.
Satelite
All ten radios sent for error 58 rss code plug errors and the long error tone upon power on have now been recovered and in working order.
So no longer in need of information.
Satelite