Table of Contents
Advertisement
XPS-Q8 Controller
11.4
Examples
Below is a table that shows possible events that can be associated with possible actions.
Some of these examples however, may have unwanted results. Since the XPS controller
provides great flexibility to trigger almost any action at any event, the user must be
aware of the possible unwanted effects.
Examples
1. EventExtendedConfigurationTriggerSet
(G1.P1.SGamma.ConstantVelocityStart, 0, 0, 0, 0)
EventExtendedConfigurationActionSet (GPIO1.DO.DOSet, 4, 4, 0, 0)
EventExtendedStart()
GroupMoveAbsolute (G1.P1, 50)
In this example, when positioner G1.P1 reaches constant velocity, bit #3 on the
digital output on connector number 1 is set to 1 (Note: 4 = 00000100). Note, that the
state of the bit will not change when the constant velocity of the positioner has
ended. In order to do so, a second event trigger would be required (see next
example).
2. EventExtendedConfigurationTriggerSet
(G1.P1.SGamma.ConstantVelocityStart, 0, 0, 0, 0)
EventExtendedConfigurationActionSet (GPIO1.DO.DOSet, 4, 4, 0, 0)
EventExtendedStart()
EventExtendedConfigurationTriggerSet
(G1.P1.SGamma.ConstantVelocityEnd, 0, 0, 0, 0)
EventExtendedConfigurationActionSet (GPIO1.DO.DOSet, 4, 0, 0, 0)
EventExtendedStart()
GroupMoveAbsolute (G1.P1, 50)
In this example, when positioner G1.P1 reaches constant velocity, bit #3 on the
digital output on connector number 1 is set to 1 (Note: 4 = 00000100) and when the
constant velocity of the positioner G1.P1 is over, bit #3 will be set to zero. Note, that
the same effect can not be reached with the event name ConstantVelocityState.
After both events have happened, the event triggers will get automatically removed.
In order to trigger the same action at each motion, it is required to link the events
Figure 46: Possible Events.
143
XPSDocumentation V1.4.x (EDH0301En1060 — 10/17)
Motion Tutorial
Advertisement
Table of Contents
