Verify and diff, Bringing a block online, Verify and diff -29 – National Instruments NI-FBUS User Manual
Page 52: Bringing a block online -29

Chapter 2
Using the NI-FBUS Configurator
© National Instruments Corporation
2-29
NI-FBUS Configurator User Manual
If you do not select Automatic Mode Handling, the NI-FBUS
Configurator shows a table of all the block modes at the start of
configuration. You have the ability to change any of the modes from this
table, or to set them all to
OOS
using the Set All Targets to OOS button.
The table appears again at the end of configuration, and allows you to set
the modes by hand, or click the Set All to Normal button to put all the
blocks into their normal modes. Note that the modes you have selected will
not be written to the bus until you click the Continue button.
Verify and Diff
This option causes the NI-FBUS Configurator to upload the actual
configuration from the devices after a download. It will then compare
the uploaded information to the configuration file in the NI-FBUS
Configurator. Refer to the
section for
instructions. This will report any differences between the configuration file
and the actual configuration of the devices. It is useful to compare a
configuration file to the bus in cases that the exact configuration on the bus
is unknown or to verify that the devices accepted all assignments.
Bringing a Block Online
If you did not select Automatic Mode Handling during the download
process, you will have to manually change the function blocks back to their
normal mode of operation.
1.
Go to the
MODE_BLK
parameter of the resource block and set the
TARGET
to
Auto
. Wait a few seconds and reread the
MODE_BLK
parameter. The
ACTUAL
field should go to
Auto
. If it does not, examine
the parameters on the Diagnostics tab to identify the problem.
2.
Go to the
MODE_BLK
parameter of the function block you are interested
in and set the
TARGET
to
Auto
.
3.
Reread the
MODE_BLK
parameter. The
ACTUAL
field should go to
Auto
.
If it does not, examine the parameters on the Diagnostics tab
to identify the problem, or refer to your device documentation.
Once the block goes to
NORMAL
mode, it is executing on the device.