The original issue, in case of interest, was the DO for sealer inprocess going off and volumeOK coming on not being seen at the same time during comparison very intermittently, leading me to believe there is a polling issue as volumeOK needs to be seen on the same scan as inprocess goes off and I can physically see the volumeOK output drive high from the SCA unit
Posts by Jazsta123
-
-
Sorry I am fairly self taught on these robots, and am not sure which standard this would be referring to (global 2 perhaps?) I have since learned that the robot will call a sealer handshake in the background at the end of any sealer process routines regardless of dispense complete macro called which is what I was confused about, but as the original macro is p-code I'm fairly sure there is no way I can find out what it consisted of myself to determine which i/o states are necessary when leaving the process routine, I am in touch with one of the line builders and will hopefully find out soon, thanks anyways
-
Hi. I have an issue with a Fanuc r200ib controller and sca sealer system, due to a devicenet issue with the p-code 'dispense complete' macro (compares volume ok inputs etc from sca unit to drive faults related to the dispense) the robot has always been using since installation, I have been playing around with implementing what I guess to be a near-replica 'dispense complete ' macro that uses a flag to resolve a polling time issue, this has all seemed to work well, except when I leave my existing sealing program, upon running the 'end' line I'm given a bunch of sealer errors, I guess my question is not specifically what is causing these errors, but how an error can be driven without being written in the program or the background logic? I had always assumed all application faulting would be driven from the unit via DI etc, itself or a programmed alarm? And if the fault is being driven from the SCA unit itself, how is it it can see the sealer process program has been ended without perform any kind of output?
-
I've had battery alarms spring from what turned out to be water damage inside the servo unit itself having had damaged the encoder connections, worth a check I guess