Cannot download a fieldbus module

Incorrect function block MODE: A red X on an AI or AO block could indicate an incorrect mode. Typically, an incorrect mode causes unexpected block output, static output values, or no signal from an active transmitter. Be sure that the Target and Actual modes for the AI block is AUTO and the Target and Actual modes for the AO block is CASCADE.

Incorrect Transducer or Resource block MODE: Also check that the Transducer and Resource blocks' Actual modes are AUTO. Be sure that a Transducer block that configures a Primary, Secondary, or Tertiary variable is in AUTO mode. If it is in Out of Service (OOS) mode, the PV value on a function block that references a channel will be bad. Be aware that some devices make use of a default Transducer block mode such as Manual to facilitate device commissioning. It is possible that a default Transducer block mode is contributing to loop inoperability.

Incorrect CHANNEL: A red X on an AI block, an unexpected AI value, or a transmitter or valve that does not return a value could indicate an incorrect channel. Because each device may be capable of more than one measurement, when you configure an AI block you must specify which measurement you want the block to process. The value for the CHANNEL parameter tells the block which measurement to process. The device manufacturer publishes valid channel values and much of this information is available in DeltaV Books Online. It is possible that the value for the CHANNEL parameter changed between device revisions and an incorrect channel number and or Engineering Units is in use. Some devices support easy configuration for CHANNEL parameter values.

Incorrect choices for L_TYPE parameter: An incorrect choice for L_TYPE parameter can cause a red X on a fieldbus function block in Control Studio. If L_TYPE is set for Indirect or Indirect Square Root and the XD_SCALE is set incorrectly for the type and channel of the device, an error can occur. A red X can occur if L_TYPE is set to Direct and the device requires that OUT_SCALE equals the XD_SCALE or if the device does not support Direct for L_TYPE.

Incorrect choice of Engineering Units in XD_SCALE: A red X on a fieldbus function block in Control Studio or the block going to Out of Service could indicate an incorrect choice of Engineering Units (EU) in XD_SCALE depending upon the setting of the L_TYPE parameter. Some fieldbus functions blocks use an XD_SCALE parameter that defines scaling ranges, engineering units, and the number of decimal places used to display the engineering units associated with the channel input value. An incorrect EU value will cause an Attribute Override Failure which will be listed in the Event Viewer (see the preceding Tip). The Primary Value Type configured in the Transducer block should match the EU configured in the fieldbus block. The majority of fieldbus devices can be configured through the EU in the XD_SCALE parameter. Some devices support easy configuration for XD_SCALE parameter values.

Incorrect choice of Engineering Units in OUT_SCALE: A red X on a fieldbus function block in Control Studio or the block going to Out of Service could indicate an incorrect choice of Engineering Units (EU) in OUT_SCALE depending upon the setting of the L_TYPE parameter. Some fieldbus functions blocks use an OUT_SCALE parameter that defines scaling ranges, engineering units, and the number of decimal places used to display the engineering units associated with the OUT value of the fieldbus function block. An incorrect EU value will cause an Attribute Override Failure which will be listed in the Event Viewer. A configuration error can occur if the Primary Value Type configured in the Transducer block does not match the OUT_SCALE EU configured in the fieldbus function block.

Block Out of Service: A red X on a block in Control Studio could indicate that the block is Out of Service (OOS). This can be caused by a device problem or can occur if the Resource and/or Transducer block is OOS. Select the device in DeltaV Explorer and click Status → Conditions to access the device's Resource and Transducer blocks. The status should be clear with no errors. Use DeltaV Diagnostics and look at device communication statistics and port communication statistics and check the port integrity.

Bad status on input block's PV: Bad status on an input block's PV can be caused by incorrect choice of Engineering Units (EU) and range in the XD_SCALE parameter or an incorrect output value in the Transducer block. The Primary Value Type in the Transducer block should match the EU configured for the AI or AO block.

SHED_OPT is zero: A red X on an AO or DO block in Control Studio online could indicate that the value for SHED_OPT is zero. The value for SHED_OPT must be non-zero.