ibm system 23 datamaster

[elvikingodaniel]

i picked up abput 2 weeks ago, i replaced every single capacitor in psu, fire up to a beautiful green screen and some errors , i believe most likely bad ic chips. both fdd motor are stuck on running , errors blinking OD 13 14 15 18 35
TRAP 000 2400 C0C0 FEC7 F2F2 F0F2 81F8 0600 0767 8039 0604
guessing 5 bad chips

 

[NeXT]

Well I think for starters the System/23 uses AC motor floppy drives, so they are both constantly running and that is normal.
For decoding TRAP errors there's a service document available on Bitsavers. http://www.bitsavers.org/pdf/ibm/system23/G360-1000-0_Datamaster_Procedures_and_Techniques_Sep84.pdf

 

[RetroAND]

i picked up abput 2 weeks ago, i replaced every single capacitor in psu, fire up to a beautiful green screen and some errors , i believe most likely bad ic chips. both fdd motor are stuck on running , errors blinking OD 13 14 15 18 35
TRAP 000 2400 C0C0 FEC7 F2F2 F0F2 81F8 0600 0767 8039 0604
guessing 5 bad chips

Hello

Before the trap notification there is a sequence on the screen. That are system diagnostics. During this past year I have got used to them... I could help you, but to do so you should post a picture of that sequence. It should be something like this:

Those numbers do not necessarily indicate a failure:

• Reverse actually is the only one indicating failure.
• Underscore means that the particular feature represented by that hexadecimal value is missing. It is an error only if that feature is listed as critical.
• Normal means that the feature represented bu the value is fine.

I hope this helps.

Regards,
Jaume

 

[RetroAND]

My bad, you already posted it... I should re-read before answering. Still, if you hadn't found a solution, I could help.

0x0D is ROS
0x13-0x15 is also ROS
0x18 is ROS too.
0x35 is the keyboard.

The keyboard error can happen because:

1. You turned it on with the keyboard lid opened.
2. The wires may be damaged (as it was in my case).
3. The keyboard may have a defective controller.

You can check what the cause is to try to discard the worst-case scenario.

Also check for underscored values. Any underscored ROS ROM (0x02, 0x09-0x19) in the diagnostics is an unpowered ROS ROM in the board. If that's so, check the traces; once the power is restored they shouldn't appear as missing.

Finally (also preparing for the worst-case with the keyboard), what equipment do you have to dump/write to it?