Originally Posted by
mike_Kilroy
all parameters and programs and motor data file. vfs5 is like a big dumb computer. on power up, we load the program into RAM and run it from there. the batt also keeps track of all variables on power down. so when batt goes south, the load gets loaded slightly corrupted. a little more corrupted as time goes on until the machine needs 100 power ups to get a good load then eventually no re power ons will get it to work.
If you want to try just a BRAM change, we can try that; we recently did one with a customer in Australia: just sent them reprogrammed chip they plugged in and got machine back running. In there case, this first try at sending just chip, they ended up with acc/dec rates messed up (aka, different) and none of us could figure it out long distance via email. He reprogrammed rates he could live with (different than they should be!) and has a good machine again. So no telling if that was some fluke or we could do it again and make it all work.
Of course you seem to have OTHER stuff going on too that does not seem explained by a BRAM batt failure. The encoder to a2100 comes from HARDWARE conversion of RESOLVER R/D HARDWARE CHIP: so your confusing enc sigs from noise do not seem related to BRAM issue.
Your previous UV also seem too different from normal BRAM issues. But we know you never got a new BRAM from your exchange 2 years ago since it is date coded 1995, so you can expect weird issues. If you want p&d on the chip and want to try it with no guarantee it is going to fix all your problems, PM or email us - Dennis does pricing and such and they don't let me get into that anymore!