Rockwell Automation GMLC Reference Manual - Manual (Page 471)

Publication GMLC-5.2 - November 1999
434 Miscellaneous Blocks
To avoid very complex diagrams, do not use the Call Module Block
unless the application absolutely requires it. The use of this feature may
make it very difficult to edit and debug program flow.
You may wish to use the Call Module block when an external device
needs to make program flow decisions. The external device requires a
method of labeling the routines that the motion controller must execute.
The Call Modules selection in the Tag Explorer displays, in the Tag
Window, the list of available modules that can be used to program the
external device. The external device can then send a variable containing
the label of the routine it needs to execute. The Call Module block can
evaluate this variable and call the appropriate predefined subroutine
module as part of the application program.
Remote Control
Use the Remote Control block to let a master motion controller, using
Multidrop, request a user variable value, status condition, or fault
condition from another motion controller.
The Remote Control block resides on the RS-232/422 Palette.
Unless you select Force to Port (see Specifying the Serial Port), the
Remote Control block sends a specified variable or expression to query,
from serial port B of the master motion controller to serial port A of the
selected slave motion controller. The slave motion controller evaluates
the expression and sends the result back to the master motion controller.
The master motion controller then stores the received value in a specified
variable, using an optional response format.
If you selected DH-485 in the General page of the Configure Control
Options dialog box, the master motion controller uses serial port B for
DH-485 communication, and must use Port A for multidrop
communications. In this case, specify Force to Port A for remote control
operation.