Download ScadaWorks Technical Reference Manual

Section II ScadaWorks Development Cycle 49
Disable I/O Scan From Running On Target Controller
If this setting is checked, I/O updating will be turned off. This can be useful as a troubleshooting aid to isolate the
controller from what the real I/O is doing.
For normal operation, do not disable the I/O scan
Include ISaGRAF Application Files
When checked (default), the ISaGRAF application files will also be sent when the startup configuration (see Target |
Send Complete Controller Setup... menu selection) is sent to the target node. By first performing a make (see Tools" |
ISaGRAF Make... menu selection) to compile any application changes, this allows the user send all of the updated
program files that are required to run the application (without having to launch the ISaGRAF development/debugger
tools).
Enable ISaGRAF Strict Variable Checking
When enabled (default), strict checking will not only insure that the endpoints of a referenced block are valid
ISaGRAF variables, but that all the variables in the block are valid as well.
For example, with strict checking enabled, the ScadaBuilder Workbench will not let you attach a block with a missing
variable to a "delta" Trigger.
Send ScadaBuilder Configuration Over Debugger
This option is left checked most of the time. It can be used to recover some memory from the system at the cost of a
little convenience.
Checked
The ScadaBuilder node file "node.sbr" which is stored in the <node name> directory will be compiled into the
ISaGRAF program image during a Make which allows it to be transferred to the controller when an ISaGRAF
Debugger download is done. This convenience costs application memory by placing the node.sbr file as a binary
resource within the ISaGRAF program. The larger the file, the less memory available to the ISaGRAF application.
Unchecked
The ScadaBuilder file "node.sbr" will not be compiled into the ISaGRAF program when a Make is done. The
ScadaBuilder configuration must then be downloaded using the Target | Send Startup Config... menu or the Target
button. Changes done in ScadaBuilder will not be updated until the Target download operation is performed.
The advantage however, is a significant gain in program memory. This is particularly useful in combination with other
memory intensive features such as HTTP and FTP when resources are at a premium.