Rockwell Automation GMLC Reference Manual - Manual (Page 570)

Publication GMLC-5.2 - November 1999
533
3. Download a “clean” version of the application program, and re-run
the program. If the fault does not recur, the problem probably was a
stack underflow, and should be solved.
4. If the block referenced in the error message includes an ordinary call
to another part of the program, the problem is probably a stack over-
flow. In this case, simplify your program by eliminating stack calls,
so the program stack depth of your controller is not exceeded.
5. Consider running your program in either Trace or Step mode, or after
setting breakpoints, to let you follow execution of your program.
This may reveal more calls - especially repetitive calls - than you
might have anticipated.
6. After you have removed enough calls, re-download the application
program, reset the controller and re-execute.
7. If the problem recurs, return to step 1, above.
This fault condition does not appear as an independent fault variable in
either the Tag Window or the Expression Builder.
Fault Ring Error 1394
A Fault Ring Error (Runtime_fault = 34) is detected if:
• All System, Axis and DIM modules are not properly plugged in,
• The connecting pins on any module are bent,
• The Terminator is not properly installed, or
• A hardware problem exists.
To correct the problem:
Verify that each element of the 1394 fault ring (the system module, the
axis modules, any DIM modules and the terminator) is completely
attached. To do so, press together both ends of the fault ring, thereby fully
engaging the connecting pins.
If the problem persists, its cause lies within the hardware. Isolate the
malfunctioning module, as follows: