If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=
Thanks Brother,
so if you take a bad eeprom off a bd.. and a good one off a working bd... now you have to 1) try and reprogram the bad chip ( ? results ) 2) put the good eeprom on the org bd and reset... seems to me wouldn't it be time/cost effective to just replace main pcb.. reset and be done?
The EEPROM on the new board is blank, no data. The old EEPROM contains machine identity and counts, must be programmed by the manufacturer AFAIK. Just swapping EEPROMS will result in error codes, identity issues. I would avoid that rabbit hole if at all possible. =^..^=
If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=
swapping eeprom causes code, and u004 to fix. New engine board comes with no eeprom installed, so this is normal engine board "replacement" procedure.
It WOULD be simpler to just swap working engine/main pair from working cadaver for testing. I spent 8+ hours troubleshooting every component and cable with kyo rep present, before eeprom conclusion when the issue was last seen in our shop. Never would have thought the eeprom could even cause such a thing, but it did.
The machine was a used device working fine when originally returned, but somehow failed a week after installation in it's new home.
after new eeprom from kyo, that machine ran for several more years until permanent retirement.
Bookmarks