Upgraded a K-line pacific with ps3, Runs and functions great. However when I apply power to track it makes a series of beeps. Does the same thing when I shut the power to track off. I have done a few other ps3 upgrades, but this is the first non mth engine I have done. What am I doing wrong?
Replies sorted oldest to newest
the board is in reset mode. It should cycle out of it on it's own after a power cycle. If it doesn't, you'll have to contact MTH or where you bought it.
I have cycled it on and off quite a few times. It runs great all sounds and functions respond fine.
I just changed the "chain files" in my install. The board played the Morse code right after. It stopped and is fine this morning.
There were a batch of upgrade kits that got stuck in reset mode. I believe they were sold last year?
I installed the PS32 chain file from the mth website. Purchased direct from MTH about a month ago. If it was stuck in reset would it still run?
Yes it will run fine. It seems weird at first, I think it will reset itself when it feels like it!
Maybe ask (or wait) GGG here on the forum for better advice.
I think you have to press shut down and allow the engine to fully finish before killing the track power.
It is a conflict in the processor. You can try to reload the flash code for PS-32. If it takes and clears, your fine. If not you need to send to MTH to reboot the board. Only they have the fixture to do it. I have seen this occur a few times, and of course the type that also locks the board out. G
What do they charge? Will it damage anything to run it as is?
If it runs, you will not have to send it back.
Try reflashing it.
The only time you have to send it back is when it stalls in the flashing process. The board is then 'bricked' and will not interact with the loader software.
You are still OK.
I ran into to same problem using Windows 10 but when I switched to Windows 7 it worked perfectly! Try reflashing it but use Windows 7.
let us know how u make out!
Tried reloading chain file no luck, just says error reading esi files? I do have an old laptop with windows xp. I'am using windows 10 and dcs loader 5
David Minarik posted:If it runs, you will not have to send it back.
Try reflashing it.
The only time you have to send it back is when it stalls in the flashing process. The board is then 'bricked' and will not interact with the loader software.
You are still OK.
Not true Dave. Rare, but it happens, the unit will operate but always play morse code. As I stated you can try a reload, but if no go has to go back to MTH or you live with morse code. Looks like his will no longer be recognized too. G
George,
I have not run into that. Mine have all come around when they are re flashed.
It does sound like his board is bricked. It will have to go back.
Dave
I can live with it. It holds all sesttings and all functions work. Will it eventualy fail?
Yes, but not because of the Software issue. G
They all play a code when reflashed at power down. It does it while comparing old to new code. As the Super cap drains the process never completes. At the next power up it goes through the morse code again as it checks code. It then starts up conventionally. Once that completes it will perform normally and no more morse code. If the flash load had to be aborted during the load, it will continue morse code until a completed reflash is performed, or in rare occasions it locks itself and can no longer be reflashed. Very rare it completes the load and works fine, but will play morse code on every shutdown.
I have posted about this before. Since the board can no longer take a load, my recommendation is to get an RA and have it reflashed. Since you no longer can reload flash, you can never reload a new sound file or flash code. This should be handled as a warranty by MTH. G
I thought the warranty expired when you opened the box!
That's why they recommend an ASC install the kit.
What I don't understand is why the sound file and chain file both loaded successfully at first. Should you load chain file first or does it matter?
It really doesn't matter which order, at least it never has for me. Once you do a power cycle after they're all loaded, it gets it's mind right. It's recommended to do a power cycle after each component in a PS/3 load, so that's what I normally do.
This fault they should cover even if not a ASC, but call to be sure. Occasionally and usually rare, the loader can get some bits wrong in the memory used to process all the other files. When that happens, the board can't be recovered via the loader, must use special test fixture which factory/MTH use to flash the programs. G