Really just for my education, but partially to accurately describe problems related to "scrambled boards/chips". This may be a basic Computer Science type answer.
I have all the basics on the various issues, but after reviewing the documents and articles on the web about these issues I do believe scramble, memory, software and chip are being used very loosely and maybe not very precisely.
My questions are:
Where is the software stored? In the processor and the PLCC Chip or just one?
What type of chip is in the PLCC? Is this just a Read Only memory, or does it have data storage capability, is it a processor too?
Same question about the microprocessor? What type and how does it work in laymens terms?
How do they interact?
My questions are related to the 2 cases listed below. In both cases the sound board is fine but "software gets scramble". In one case you install another chip in the PLCC to resolve the issue and put the original chip back in. So this sounds like the software scrambled must be on the Soundboard somewhere, since you removed the PLCC Chip.
In the other case the "listed" emgines have a software issue that deslects the engine. The only way to fix this software is replace the PLCC chip. This would imply the microprocessor or software on the board is fine, but the chip got scrambled. How does the software glitch effect the PLCC chip. I know it has to do with low battery state, but if the software is on the board, how does the chip software mess up?
I actually have a listed engine in for repair. It was using the BCR. The board and BCR are fine, but the chip in the PLCC doesn't work. I can install other chips and the engine works fine. The solution is replace the chip, but I am trying to understand how the 2 cases differ, yet both are classified as "scrambled boards or chips" by various documents. Thanks, G
This is from the MTH web site.
"Owners of some M.T.H. Electric Trains' Proto-Sound 1 equipped engines built prior to mid-2000 may experience one of two software related errors that are initiated from low or discharged batteries. Some confusion in the marketplace regarding these errors has led to the replacement of the Proto-Sound board when correction could have been resolved through a software upgrade. In each case, the software error can be avoided entirely if the owner replaces the battery prior to use. Battery replacement should only be necessary if the locomotive has not been run within a year and the battery is no older than a year.
What follows is a description of each error and the necessary steps that must be taken to correct the problem. In case #2, the problem only occurs in engines produced in 1995 and 1996 as illustrated in the attached list. QSI, the developer of M.T.H.'s original Proto-Sound system corrected that problem in a later software version.
Case #1: Proto-Sound 1 locomotive starts up and reports three clank sounds
This scenario is always precipitated by a low or discharged battery and can usually be avoided by charging or replacing the battery prior to powering up and operating the locomotive. The problem doesn't occur as soon as the engine is powered up, but rather when the operator tries to get the engine to move by using the direction button or turning the throttle off and then on again to enter the forward or reverse direction. If the battery is too low or discharged at this point it will be unable to supply the circuit board with enough current to operate normally causing the board to become "scrambled". This can be confirmed with the sounding of the three clanks. At this point it will be necessary to reprogram the board with a special software chip. Once reprogrammed, the original software chip can be reinstalled and the engine should perform normally. Essentially, the special software chip reinitializes the board. Unfortunately, the problem can reoccur in the future should the battery become dangerously low or completely discharged. The problem stems from the QSI design of the Proto-Sound board and no permanent fix is available.
Case #2 Proto-Sound 1 locomotive starts up but will not move.
This scenario only occurs in some engines produced in 1996, 1997 and early 1998. The error occurs as a result of a low or discharged battery and causes the software to "deselect" the locomotive. Users of QSI's more full-featured sound systems may recognize the "selection" feature as the QSI system's ability to give engines an ID number. When given an ID number, each engine can be turned on or off (deselected) so as to respond or not to transformer-related actions. An engine that has been deselected will not turn on even if track power is on. The engine will remain quiet and still during all transformer actions until "reselected" through special whistle and bell commands from the transformer. The feature was a precursor to today's command control operations found in the DCS and TMCC systems. However, QSI's approach was deemed to complicated a procedure by M.T.H. for Proto-Sound 1 locomotives. As a result, M.T.H. asked QSI to eliminate the feature from the software used in Proto-Sound 1 engines. Unfortunately, a bug in the QSI software deselects the locomotive when the battery charge becomes too low resulting in an engine that starts up but fails to leave the Reset position. Users may mistakenly assume that the locomotive is locked in neutral. Replacing the battery and performing the unlock procedure or resetting the engine through Feature 18 will not resolve the problem.
Fortunately, the solution for #2 resides in a software update through the installation of a new chip that permanently fixes the "deselect" function from occurring in the future should the battery charge become too low or discharged.