Maxtrac error tone (does not stop).
Moderator: Queue Moderator
Maxtrac error tone (does not stop).
I have had this problem a few times with various models of Maxtracs.
I had thought I'd found a procedure to fix it but I no longer remember.
[MY MAIN QUESTION:]
I have LABware that allows me to read the EEPROM and I was wondering if there is a location in ram that stores what the last error was, as I currently don't have a clue why it's mad.
I have tried loading codeplugs from other radios of the same model# and this did not help. I thought it might.
The Firmware EPROM seems to be the right one and its checksum is correct, and the codeplug matches the serial number and the model description on the CPU shield sticker from the factory.
It is a type-I trunked 2-SYS 2-SUB, D35MQA5GB3AK, MTX820, 5-PIN.
FIRMWARE: V V N 4075A or 52.07
I welcome all help on this. Even if there is special software I might need, let's assume I have it (in case I can figure out a work around without it once the cause is discovered).
Revised:
Some software reports an external EEPROM CHECKSUM ERROR.
Where in the eeprom is the checksum and what addresses are included.
(I know, not asking for much.)
Zap.
I had thought I'd found a procedure to fix it but I no longer remember.
[MY MAIN QUESTION:]
I have LABware that allows me to read the EEPROM and I was wondering if there is a location in ram that stores what the last error was, as I currently don't have a clue why it's mad.
I have tried loading codeplugs from other radios of the same model# and this did not help. I thought it might.
The Firmware EPROM seems to be the right one and its checksum is correct, and the codeplug matches the serial number and the model description on the CPU shield sticker from the factory.
It is a type-I trunked 2-SYS 2-SUB, D35MQA5GB3AK, MTX820, 5-PIN.
FIRMWARE: V V N 4075A or 52.07
I welcome all help on this. Even if there is special software I might need, let's assume I have it (in case I can figure out a work around without it once the cause is discovered).
Revised:
Some software reports an external EEPROM CHECKSUM ERROR.
Where in the eeprom is the checksum and what addresses are included.
(I know, not asking for much.)
Zap.
Maxtracs have a memory chip that stores the codeplug. Some of them are AT28C16 EEPROM's and some of them are Dallas Nonvolitile SRAM chips.
I think the Dallas chips may contain a battery for backup and eventually - they die. I have had the Dallas ones go bad but I've never had a 2816 one go bad. Either way - a bad memory chip could cause your problem.
To solve the problem, I simply replaced the Dallas chip with a 28C16, blanked the board and re-initialized the radio.
I think the Dallas chips may contain a battery for backup and eventually - they die. I have had the Dallas ones go bad but I've never had a 2816 one go bad. Either way - a bad memory chip could cause your problem.
To solve the problem, I simply replaced the Dallas chip with a 28C16, blanked the board and re-initialized the radio.
So I did an entended codeplug wipe. Tuning, everything.
Using the original (when I got it) archived codeplug as a sample to create a new radio from, did not improve the same problem of the long tone when it reset after the rss is done.
However, using a codeplug from a different s/n but same radio model # had a slightly different result.
The radio fully functions and no error tones until I turn it off and back on.
Then the error tones start up and the radio won't function unless I re-write the same codeplug back into the radio.
It will also stop the error sound if I read or write to EEPROM locations.
Using the lab eeprom editor I have found three things.
1). one of the checksums for the seial number is at codeplug 002E or RAM:$B62E.
2). there is a second copy of this value or it's complement somewhere else, that is checked against this.
3). Hi-Lo tone seems to indicate chksum error in serial #, Lo tone seems to indicate chksums don't match.
I didn't replace the dallas memory module yet, it is dated 8827.
I'm now not convinced it is the problem as reading the eeprom with lab fixes it but reading with rss does not. Once again, cycling the power off then on and the problem returns.
Zap
Using the original (when I got it) archived codeplug as a sample to create a new radio from, did not improve the same problem of the long tone when it reset after the rss is done.
However, using a codeplug from a different s/n but same radio model # had a slightly different result.
The radio fully functions and no error tones until I turn it off and back on.
Then the error tones start up and the radio won't function unless I re-write the same codeplug back into the radio.
It will also stop the error sound if I read or write to EEPROM locations.
Using the lab eeprom editor I have found three things.
1). one of the checksums for the seial number is at codeplug 002E or RAM:$B62E.
2). there is a second copy of this value or it's complement somewhere else, that is checked against this.
3). Hi-Lo tone seems to indicate chksum error in serial #, Lo tone seems to indicate chksums don't match.
I didn't replace the dallas memory module yet, it is dated 8827.
I'm now not convinced it is the problem as reading the eeprom with lab fixes it but reading with rss does not. Once again, cycling the power off then on and the problem returns.
Zap
-
- Posts: 18
- Joined: Thu Sep 18, 2003 2:06 am
Your Problem
I encountered the same problem when I tried a bad codeplug in an 820. It's about a 1 sec high tone followed by a cont. low tone, right? What you'll have to do is use the Maxtrac Lab RSS, then select "MAKE BLANK BOARD" option. After you do this, you will need to re-enter the model # in the RSS, I think you might have either the D35 or D45 MQA5GB5_K model. After doing this, go back into the Maxtrac 800 RSS and load a codeplug with the correct serial number. If I remember correctly, the RSS will ask you to initialize the board at that time, asking for the model, series and serial number. You have a "Standard" "Maxtrac 820" and then select the correct model number. Make sure the serial number you set in the Lab RSS is the same as the codeplug you write back to the radio, otherwise, you'll end up with the same error. You can actually change the serial number of a codeplug in the Lab RSS, but for some reason, the Maxtrac Lab RSS doesn't really like the 800 series per se, when you try to load a codeplug into the radio in Lab, it only writes the 64 block codeplug, not the 240 block. These radios are fairly hard to "brick" unless maybe you lose power on the rib or PC during read/write. Just make sure you have a good, working codeplug for the model you are working with before doing any Lab work on them. Let me know if this helps or if you have any more questions.
I have no experience with these radios, but I can tell you I had a similar problem with a Dallas CMOS Clock chip in a PC. The internal battery died. When power was applied, I could set everything and the errors went away, but as soon as I cycled power, the CMOS lost some bytes (not all) and came up with all sorts of errors. Again, resetting things caused the errors to go away until the next power cycle.
Many of these devices had a 10 year lifespan, and if yours was made in 1988, then it's going on 16-17 years now and this could definitely be the problem.
Replacing it with something that has a new battery, or doesn't need one at all, might be the real way to fix this. I was looking for the chip and discovered that it's mounted to the board UNDER another chip (the EPROM maybe). I don't know if it's socketed or if it's even replacable. Perhaps this is the EEPROM that's shown in the schematic.
From the other posts in this thread, it seems that the facts fit the crime, unless of course you live in California.
Bob M.
Many of these devices had a 10 year lifespan, and if yours was made in 1988, then it's going on 16-17 years now and this could definitely be the problem.
Replacing it with something that has a new battery, or doesn't need one at all, might be the real way to fix this. I was looking for the chip and discovered that it's mounted to the board UNDER another chip (the EPROM maybe). I don't know if it's socketed or if it's even replacable. Perhaps this is the EEPROM that's shown in the schematic.
From the other posts in this thread, it seems that the facts fit the crime, unless of course you live in California.
Bob M.
Try Blanking and Reinitializing. Use Lab to Blank, and the regular RSS to Reinit.
Then just build a new codeplug from scratch and program. I had to do this recently with four 800Mhz models that i bought. Someone killed them with RSS or Lab when they were retired and removed from use. They always went back to the corrupt codeplug error tone just like you describe.
After Blanking and Reinitializing they work perfectly. For a more in depth look at how to do it go here:
http://www.repeater-builder.com/maxtrac ... grade.html
The article mainly deals with upgrading a Maxtrac for more channels, but shows step by step how to blank and reinitialize a logic board, and what information is needed, etc.
Then just build a new codeplug from scratch and program. I had to do this recently with four 800Mhz models that i bought. Someone killed them with RSS or Lab when they were retired and removed from use. They always went back to the corrupt codeplug error tone just like you describe.
After Blanking and Reinitializing they work perfectly. For a more in depth look at how to do it go here:
http://www.repeater-builder.com/maxtrac ... grade.html
The article mainly deals with upgrading a Maxtrac for more channels, but shows step by step how to blank and reinitialize a logic board, and what information is needed, etc.
Duct tape is like the force, it has a dark side and a light side and it holds the universe together.
"I Reject Your Reality And Substitute My Own!" - Adam Savage
"I Reject Your Reality And Substitute My Own!" - Adam Savage
I can blank with lab extended ok.
But when re-initializing with RSS, I am told I must load a codeplug first.
When I do, I do not get to select which model I want it to be so I cannot make one from scratch.
The link I followed shows how to make a conventional, this is trunked.
My RSS is MAXTRACS R05.07.00 RVN4030-O
The only good codeplug I can find is: D35 MQA5GB 5
the radio is .....................................D35 MQA5GB 3
I do not have a good plug for this model.
Why would I not want to use the lab to make a fresh CP as all have suggested not to do?
Now, when the radio is programmed, it works without error tone.
Turn it off, and back on, error tone.
READ it (not write) error tone gone again.
Just the RSS accessing it stops the error.
Why would reading a radio clear an error?
But when re-initializing with RSS, I am told I must load a codeplug first.
When I do, I do not get to select which model I want it to be so I cannot make one from scratch.
The link I followed shows how to make a conventional, this is trunked.
My RSS is MAXTRACS R05.07.00 RVN4030-O
The only good codeplug I can find is: D35 MQA5GB 5
the radio is .....................................D35 MQA5GB 3
I do not have a good plug for this model.
Why would I not want to use the lab to make a fresh CP as all have suggested not to do?
Now, when the radio is programmed, it works without error tone.
Turn it off, and back on, error tone.
READ it (not write) error tone gone again.
Just the RSS accessing it stops the error.
Why would reading a radio clear an error?
After you blank it you go to the Service menu and Board Replacement and the go through the Logic Board replacement to select everything.
You mean it won't let you into the service menu? I have yet to have one ask me for anything. I think perhaps what your doing is blanking, then running the RSS and selecting the Change/Create/View CP. You have to reset all the logic board settings first in the service menu, then you will be able to build a new codeplug from scratch.
You mean it won't let you into the service menu? I have yet to have one ask me for anything. I think perhaps what your doing is blanking, then running the RSS and selecting the Change/Create/View CP. You have to reset all the logic board settings first in the service menu, then you will be able to build a new codeplug from scratch.
Duct tape is like the force, it has a dark side and a light side and it holds the universe together.
"I Reject Your Reality And Substitute My Own!" - Adam Savage
"I Reject Your Reality And Substitute My Own!" - Adam Savage
I had one of the Dallas chips go bad in a Zetron Model 8. Same problem, looses it's code. They are bassically a IC socket that has a battery backup in it. The EEPROM plugs into the Dallas socket, the Dallas plugs into the Logic board. They are available new from Dallas, listed in the Mouser catalog... but about $27....
There is also a backup capacitor, 47uf, that supplies power for CMOS memory after the radio powers down. I have had to replace them a few times. On one, I put a 3.6 volt lithium battery in it's place. That kept all the settings even tho all power was removed.
There is also a backup capacitor, 47uf, that supplies power for CMOS memory after the radio powers down. I have had to replace them a few times. On one, I put a 3.6 volt lithium battery in it's place. That kept all the settings even tho all power was removed.
I hate to bring up an old dead thread, but this is the exact problem I'm having with a Maxtrac820. Just gives the error tone, have tried to blank board and reinit with RSS several times, but can't seem to get anywhere. Everything Ive tried just gives me tone. Somewhere in the process I think I lost the original codeplug data AND tune data.
My model is D35MQA5GB5K. I supposedly downloaded a codeplug for this model, but RSS won't let me import it for some reason even though its in the correct directory. Suggestions?
Thanks!
My model is D35MQA5GB5K. I supposedly downloaded a codeplug for this model, but RSS won't let me import it for some reason even though its in the correct directory. Suggestions?
Thanks!