Spectra Error 16 while replacing MLM.
Moderator: Queue Moderator
-
- was grem467
- Posts: 1145
- Joined: Mon Jul 21, 2003 12:46 pm
Spectra Error 16 while replacing MLM.
Ive got a spectra D37 on the bench that came in without an MLM.. ok no problem, so i put one in (no version sticker) that came out of a UHF. I bitbanged the MLM to the proper model number and serial number, but now it wont let me blow a codeplug into it. The error states "ERROR 16, Software versions do not match"
Would i be correct in assuming that this MLM version is too old? Is there a way to get a 900Mhz codeplug into it and thereby eraseing the UHF freqs and bandsplit that is in the MLM (even though RSS reads the radio correctly now as a D37)
thanks as always. Spectra hackin is a riot!
Would i be correct in assuming that this MLM version is too old? Is there a way to get a 900Mhz codeplug into it and thereby eraseing the UHF freqs and bandsplit that is in the MLM (even though RSS reads the radio correctly now as a D37)
thanks as always. Spectra hackin is a riot!
-
- was grem467
- Posts: 1145
- Joined: Mon Jul 21, 2003 12:46 pm
-
- was grem467
- Posts: 1145
- Joined: Mon Jul 21, 2003 12:46 pm
ok ive got a uhf with PA problems (its actually the radio that this MLM came out of) so i guess ill pull the command board and match it back to its MLM.
i checked the MLM Version and its v5.04
as for the radio, the only error it gets is fail001 from the uhf freqs programmed into the mlm.. i tried 2 900Mhz codeplugs (one was all the way back from a ver 1.02 mlm! haha) and they all had the error 16 mismatch.
The MLM was bitbanged and reports the correct D37 model number as my codeplugs, but obviously still is aware of the D44 information from the UHF.
For the record, im not so much worried about the radio, the sole purpose of this one is to move on to learning the ins and outs of the spectra, from the world of maxtrac hexediting etc. I know they are totally different beasts, but would rather hose this radio then a VHF or something like that.. lol
i checked the MLM Version and its v5.04
as for the radio, the only error it gets is fail001 from the uhf freqs programmed into the mlm.. i tried 2 900Mhz codeplugs (one was all the way back from a ver 1.02 mlm! haha) and they all had the error 16 mismatch.
The MLM was bitbanged and reports the correct D37 model number as my codeplugs, but obviously still is aware of the D44 information from the UHF.
For the record, im not so much worried about the radio, the sole purpose of this one is to move on to learning the ins and outs of the spectra, from the world of maxtrac hexediting etc. I know they are totally different beasts, but would rather hose this radio then a VHF or something like that.. lol
-
- was grem467
- Posts: 1145
- Joined: Mon Jul 21, 2003 12:46 pm
ok, i removed the command board that this MLM came off of and got the same error. It wont let me dump a 900 codeplug into it, ive tried 3 different codeplugs and all of them get the error 16. now a VHF one will go in no problem (using limited clone), but obviously this does me no good as its a D37 radio.
OK. Now that you've gotten it beyond the hickups, got to offset 0x605F and change the two bytes to 67h. Delete all of the modes, then write and read the radio. Enter an in-band pair and you should be all set.
You didn't say whether you had changed the bandsplit bytes or not. So, I'm assuming that all you changed were the model numbers in the command and mlms. That really means nothing, other than they have to match.
You should now have a default 900MHz conventional, with the same features as your UHF that the boards came out.
Since you didn't say what the 900 model number was, I'm guessing it was a D37KMA5JB5 trunker, or some such. You have to bit bang in a conventional string into the command board to make it think its conventional.
See some of Natedog's earlier posts for the addresses and what to change the string to.
Lee
You didn't say whether you had changed the bandsplit bytes or not. So, I'm assuming that all you changed were the model numbers in the command and mlms. That really means nothing, other than they have to match.
You should now have a default 900MHz conventional, with the same features as your UHF that the boards came out.
Since you didn't say what the 900 model number was, I'm guessing it was a D37KMA5JB5 trunker, or some such. You have to bit bang in a conventional string into the command board to make it think its conventional.
See some of Natedog's earlier posts for the addresses and what to change the string to.
Lee
-
- was grem467
- Posts: 1145
- Joined: Mon Jul 21, 2003 12:46 pm
Glad it worked.
Yeah, I went to the hamfest. Seemed like it was a little less than prior years, but it could have been the cold affecting my perception. The wind chill must have been 30 in the parking lot.
A few odds and ends. Couple of Maxtracs. Same ones the same guy was trying to sell (at yesterday's prices) at the Melbourne fleamarket 3 months ago.
No spectras, but I heard that a 'hawker' from up your way just bought a boatload of Spectras and HT1000s and paid $33K for the lot. I don't know how many, and the details. And, he's begun selling remote head cables on eBay. I dont' want to mention his name here, though.
Melbourne was much larger and the quantity and quality of the goodies seemed better. I'll probably try going to Miami this year, just to see what it's like. Besides, it WILL be warmer than this one....
Lee
Yeah, I went to the hamfest. Seemed like it was a little less than prior years, but it could have been the cold affecting my perception. The wind chill must have been 30 in the parking lot.
A few odds and ends. Couple of Maxtracs. Same ones the same guy was trying to sell (at yesterday's prices) at the Melbourne fleamarket 3 months ago.

No spectras, but I heard that a 'hawker' from up your way just bought a boatload of Spectras and HT1000s and paid $33K for the lot. I don't know how many, and the details. And, he's begun selling remote head cables on eBay. I dont' want to mention his name here, though.
Melbourne was much larger and the quantity and quality of the goodies seemed better. I'll probably try going to Miami this year, just to see what it's like. Besides, it WILL be warmer than this one....
Lee
- natedog224
- Posts: 224
- Joined: Mon Mar 17, 2003 2:15 am
Since this somewhat pertains to MLM changeouts.........
FYI :
If you go to the help screen and then other help where it shows radio info one of the fields will be EEVers.
Which refers to the EEPROM version number. I am guessing it has its own structure on how data is stored. For instance if you take a codeplug from a newer radio and try to clone it into an older one it will say "EEVersions do not match conversion is nescessary" or something like that.
V5.xx MLMs this vers will be 1.14
V6.xx MLMs this vers will be 1.15
You can find information on hacking this on my spreadsheet. Look on some old posts for a link.
When upgrading firmware on MLMs I was having to hack this to 1.15 after changing the from pre6 to 6.16. Otherwise it will program the codeplug EEPROM funny.
The spectras usually do very funny things when you upgrade and MLM like I do. Such as rebooting themselves when you press a function button. Reinitializing the command board fixes these problems and is always part of my upgrades.
FYI :
If you go to the help screen and then other help where it shows radio info one of the fields will be EEVers.
Which refers to the EEPROM version number. I am guessing it has its own structure on how data is stored. For instance if you take a codeplug from a newer radio and try to clone it into an older one it will say "EEVersions do not match conversion is nescessary" or something like that.
V5.xx MLMs this vers will be 1.14
V6.xx MLMs this vers will be 1.15
You can find information on hacking this on my spreadsheet. Look on some old posts for a link.
When upgrading firmware on MLMs I was having to hack this to 1.15 after changing the from pre6 to 6.16. Otherwise it will program the codeplug EEPROM funny.
The spectras usually do very funny things when you upgrade and MLM like I do. Such as rebooting themselves when you press a function button. Reinitializing the command board fixes these problems and is always part of my upgrades.
Nate: Ah ha, you were lurking. Since you brought up reinitializing the Command Board, it seems as though I've tried it until blue in the face, and really don't seem to notice any difference. Probably, I'm doing something wrong.
Reinitializing the processor isn't what you mean, or is it?
I haven't tried it for a while, but seems like I also got the message that it was already initialized as well in almost every case. What am I doing wrong?
Thanks.
Lee
Reinitializing the processor isn't what you mean, or is it?
I haven't tried it for a while, but seems like I also got the message that it was already initialized as well in almost every case. What am I doing wrong?
Thanks.
Lee
Re: Spectra Error 16 while replacing MLM.
Nate,
What would be the procedure to upgrade the MLM Firmware? I have the binary's for the 6.16 chips and spare 27C512's and all the equipment to do the upgrade but am a little unshure of the start to finish process. I have done Moflag updates on same version mlm's, with out any problems, but have not tried the "full" upgrade. I have socketted all the MLM's to make it easer to work with. Any info would be greatly apperciated.
What would be the procedure to upgrade the MLM Firmware? I have the binary's for the 6.16 chips and spare 27C512's and all the equipment to do the upgrade but am a little unshure of the start to finish process. I have done Moflag updates on same version mlm's, with out any problems, but have not tried the "full" upgrade. I have socketted all the MLM's to make it easer to work with. Any info would be greatly apperciated.