Well, I'm not completely sure what the exact cause was, but after checking everything under the sun, I reloaded the last image backup I had and the problem went away. Maybe at one point someone enabled a SFID22, then somehow it got deleted after it threw the error, and when the image went in it initialized it... Very strange, but I have seen stranger.
Thanks everyone for the suggestions and advice.
-K
R30iB Mate cabinet. Yes, I checked every connector on the E-stop board. It is my understanding that in our situation the I/O for DCS is controlled by Omron Device Net. But we have 5 other robots with this same situation, and we have DCS disabled (currently installing guns getting robots ready to run) and they are operating normally, but this robot, even with DCS disabled is still acting strange. I am considering loading an image from it's sister robot for setup, then returning the current image once the cell is in a run state... I checked the DCS I/O mapping, and there is nothing on there that indicates SFID22. We did have a Japanese technician trying to do something, but I have no idea what as the pendant was in Japanese, and he said he made no changes... I am a little skeptical...
I will check connections to and from main board as well, and bump the device net board to make sure it is fully seated just as a precaution.
I'm having the same issue, SRVO-378 SFID22, I have gone through DCS and can't find any reference to Input 22, and can't figure out where the input is supposed to be coming from. Maybe I am looking in the wrong place, but I have looked all through the I/O section of DCS. Any suggestions would be appreciated.
Thanks,
-K
