Rockwell Automation 1788-FFCT NI-FBUS Configurator User Manual - Manual (Page 71)

1 Publication 1788-UM052B-EN-P - April 2002
Appendix
B
Troubleshooting and Common Questions
This appendix describes how to troubleshoot problems and answers
some common questions.
To determine how to solve a problem, refer to Table 2.1.
Table 2.1 Troubleshooting Problems
Problem Possible Causes Solution
A function block alternates
between IMAN and AUTO modes.
The status of the input parameter
is Bad::No comm. The function block and communication
schedules do not have enough time between
them. Refer to Mode Transition on page B-4.
The PID does not transition to AUTO
mode. The status of OUT/BKCAL_OUT from AI/AO
is Bad::Not Connected or Bad::No Comm. Refer to Mode Transition on page B-4.
The downstream block is not in cascade mode.
The AI does not transition to AUTO
mode from OOS mode. The configuration is incorrect or incomplete. Refer to Mode Transition on page B-4.
The function blocks are in OOS
mode. The resource block is in OOS mode. Set the target mode of the resource block to
AUTO.
You receive a status of Bad:Device
Failure. An error exists with the hardware. Set the RESTART parameter in the Block
window to Processor or Default. If the
problem persists, replace the device.
A device does not appear in
the Project window. The communication parameters are incorrect. Refer to Missing Devices on page B-3.
You are unable to write to a block
parameter. The parameter is read-only. If the parameter is not read-only, refer to the
Reading and Writing Errors on page B-5.
The blocks are in an incorrect mode.
The data is out of range.
A device does not accept
a permanent address. The device does not have a tag. You must set the device tag. For instructions on
setting the tag, refer to the Setting Device or
Block Tags section on page 4-5.
If the device already has a tag, the T3 network
parameter might not be the right length. Remove the device from the active bus and
configure its address separately.
A device does not accept a new tag. The device is in an invalid state. Power the device off and on.
The control is slow. The macrocycle time might be too long. Edit the function block schedule and decrease the
macrocycle time. For more information about
editing the schedule, refer to the Viewing and
Editing Function Block Parameters section on
page 4-19.
A device does not transmit alarms or
trends. You have not configured the alarms or trends. For instructions on how to configure alarms and
trends, refer to the Configuring Alarms
and Configuring Trends sections on pages 4-25
and 4-26, respectively.