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

Publication 1788-UM052B-EN-P - April 2002
B-2 Troubleshooting and Common Questions
Troubleshooting This section describes how to troubleshoot problems you might
encounter while using the NI-FBUS Configurator.
Missing Interface
If your interface(s) does not appear in the Add Links dialog box, you
may need to upgrade your software key to support the additional
links.
If you purchased additional licenses to access more than the default
number of links, contact National Instruments to obtain a new
software key.
After you obtain a new key, complete the steps on page 4-37 to
change your software key.
Missing Symbolic Information
If a function block is missing symbolic information (such as names
and help strings), you may need to import the Device Descriptions
(DDs). For more information about importing DD files, refer to the
Importing Device Description Files section on page 4-4.
If the problem persists after you import the DDs, reset the device.
A device does not publish the data
you configured it to transmit. The function execution time parameter in the
function block does not accurately represent
the execution time. Refer to the Transmission Problems section on
page B-4.
Your interface(s) does not appear
in the Add Links dialog box. You may need to upgrade your software key to
support the additional links. Refer to the Missing Interface section on
page B-2.
A function block is missing symbolic
information (such as names and help
strings). The function block has no DD, and the block
does not correspond to the standard function
blocks defined by FOUNDATION Fieldbus. You may need to import the DDs. To do so,
refer to the Missing Symbolic Information on
page B-2.
The NI-FBUS Configurator cannot read
pertinent block information from the device. Reset the device.
You receive frequent communication
errors when you try to read or write
to a device. Other devices are actively and frequently
polling the device, causing reads to time out. Reduce polling.
The device is in an invalid state. Reset the device.
Table 2.1 Troubleshooting Problems (Continued)
Problem Possible Causes Solution