National Instruments NI-FBUS - Manual (Page 111)

Appendix B Troubleshooting and Common Questions
NI-FBUS Configurator User Manual B-2 ni.com
For more information about downloading the configuration, refer to
the
Download a Project Configuration section of Chapter 2, Using the
NI-FBUS Configurator .
3. Make sure the target mode of both the PID and AO blocks is set to Cas .
The AI block does not transition to Auto mode from OOS mode.
The configuration is incorrect or incomplete. Complete the following steps:
1. Make sure that the resource block is in Auto mode.
2. Make sure the XD_SCALE fields are set to the value specified by the
vendor.
3. Set the target mode of the AI block to Auto .
The function blocks are in OOS mode.
The resource block is in OOS mode. Set the target mode of the resource
block to Auto , then set function block to their normal mode.
AI block will not go to Auto Mode.
The block must be scheduled to execute (done by placing it in the Function
Block Application Editor window and downloading) before it can go into
Auto mode. If the block still will not go into Auto , try the following
solutions:
• Check that the resource block is in Auto .
• Look at the BlockError parameter on the Diagnostics tab. This will
often give reasons for staying in OOS mode.
• For FieldPoint, you can look at the LAST_BLOCK_EVENT parameter.
• Make sure that the parameter L_TYPE has been initialized and other
parameters are set properly.
When using an FP-3000 with a PID block cascade, the high limit flag
goes ON as it should when the output reaches the high limit, but it stays
ON even when that output goes back down.
Reduce the BKCAL_HYS parameter. When outputs hover around alarm
limits, this triggers the alarm to turn on and off. After an alarm has been
triggered, this parameter specifies how far below the alarm limit the output
must fall before the alarm condition will clear. Setting this to zero means
that as soon as the output falls below the alarm limit, the condition will
clear.