288 Rockwell Automation Publication 2080-UM002N-EN-E - November 2022
Appendix B Quickstarts
1. Start a new project following the same steps and values as the previous project. Set the
values for the following variables as follows:
- HSCAPP.PlsEnable variable should be set to TRUE.
- Set a value only for UFSetting and OFSetting (OutputMask is optional depending if an
output is to be set or not). Your new values should follow the example in Figure 30
:
Figure 30 - PLS Values
In this example, the PLS variable is given a dimension of [1..4]. This means that the HSC
can have four pairs of High and Low Presets.
Once again, your High Presets should be set lower than the OFSetting and the Low
Preset should be greater than the UFSetting. The HscHPOutPut and HscLPOutPut values
will determine which outputs will be turned on when a High Preset or Low Preset is
reached.
2. You can now build and download the program into the controller then debug and test it
following the instructions for the last project.
Forcing I/Os Inputs are logically forced. Status indicators do not show forced values, but the inputs in the
user program are forced.
Forcing is only possible with I/O and does not apply to user-defined variables and non-I/O
variables, and special functions such as HSC and Motion that execute independently from the
User Program scan. For example, for motion, Drive Ready input cannot be forced.
Unlike inputs, outputs are physically forced. Status indicators do show forced values and the
user program does not use forced values.
To Next Page
Loading...
Need help?
General
