Gamedawn

Thanks for that. Next time I'm on site I'll try those things out. If it does turn out to be the Pmac at fault, can they still be repaired?

Thanks for that. Next time I'm on site I'll try those things out. If it does turn out to be the Pmac at fault, can they still be repaired?

It definitely happened after a reset and I'm fairly sure that when I tried it nothing else was running (plc's, motion progs, etc). In fact it was ater a reset and loading the config file that I first noticed the problem, because the config should have set I900=7. We also verified that the link settings are as they should be. Are there any settings that might cause this problem that I could have a look at next time I'm on site?

It definitely happened after a reset and I'm fairly sure that when I tried it nothing else was running (plc's, motion progs, etc). In fact it was ater a reset and loading the config file that I first noticed the problem, because the config should have set I900=7. We also verified that the link settings are as they should be. Are there any settings that might cause this problem that I could have a look at next time I'm on site?

I was working on a machine recently with a PMAC Lite (isa bus) and wanted to change the I900 value to 7. I typed the value in at the terminal but when I checked it the value had changed to 6. This happened every time I typed the value in and also happened with I905, etc. The board is running V1.16D firmware. Has anyone come across this problem before?

I was working on a machine recently with a PMAC Lite (isa bus) and wanted to change the I900 value to 7. I typed the value in at the terminal but when I checked it the value had changed to 6. This happened every time I typed the value in and also happened with I905, etc. The board is running V1.16D firmware. Has anyone come across this problem before?