I’ve never seen this code before, curious as to what might have happened? I’ve been running production, 300 or so parts in AUTO, no problems, just went to hit start again and this alarm came on. Running quick cycle parts, not sure if somehow I caused an issue by running a ton of parts way too fast? Not even sure if that could cause this error, just thought I’d include it just in case.
Alarm: SRVO-378 SFDI17 status abnormal (2)
-
Chase -
February 10, 2022 at 4:39 PM -
Thread is Unresolved
-
-
Also got a “SVOFF input” alarm as well.
-
Possibly a wiring issue. Check the wiring to those inputs.
-
Alarm is "SFDIxx Status abnormal"
A chain alarm was detected with the SFDI signal. xx shows the signal name.
SFDI is a DCS input
-
Did you ever figure out the issue?
-
To add to what others said, once you have the problem corrected you'll have to go to your alarms menu and hit F4 "RES_1CH" and then press reset
-
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
-
I had this issue, and after I ripped my remaining hair out I realized that the connector from the auxiliary input board to the, uh, main controller had partially come lose on the main controller.
-
What type of control cabinet, A or B?
Have you checked the DCS I/O connector? It is on the E-Stop board.
-
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.
-
Have you checked all of the fuses, especially on the EStop board?
-
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