| Experion HS R530.1 User Assistance

# Troubleshooting problems with specific controller models

## UDC3300 problems

Error message or problem | Description
--- | ---

- You attempt to change a set point Also known as SP. The desired value of a process variable. Setpoint (SP) is an analog point parameter, and the value is entered by the operator. The setpoint can be changed any number of times during a single process. The setpoint is represented in engineering units. See SP in the Control Builder Parameter Reference. See also: analog point, parameter, process variable. in Station Experion's main operator interface. Station presents information using a series of displays. See also: display. and the value changes on the Station display but not on the controller Also known as remote terminal unit, RTU. A generic term for a device that is used to control and monitor one or more processes in field equipment. The most common control and monitoring device in an access control and security system is an access control panel. Other devices include security monitoring panels, elevator controllers, and fire monitoring devices. Controllers include programmable logic controllers (PLCs), loop controllers, bar code readers, and scientific analyzers. See also: C200 controller, control processor, CPM, hybrid controller, network node controller, PLC. faceplate A specialized pop-up that shows a subset of the details shown on the matching point detail (or template) display. It typically shows the point's runtime values and control settings. A faceplate appears when an operator clicks an object that is linked to a point. See also: point, point detail display..

- You attempt to change a set point in Station and the value on the Station display changes to a different value and the controller's faceplate doesn't change.

The communications link between the controller and server The computer on which the Experion database software and server utilities run. See also: Experion server TPS. can become overwhelmed. The solution is to increase the COM Tx Delay on the controller faceplate.

## UMC800 problems

Error message or problem | Description
--- | ---

- You know that you should use the address LOOP n parametername but you don't know what value to use for n.

- You want to access the process variable Normally abbreviated as PV. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. of the only PID Proportional, integral, and derivative control modes. loop you have configured. You used the number n which appears on the top right-hand corner of the PID block A unit of data and operation within Experion. Experion uses blocks as the component from which control strategies are built. The two categories of blocks are hardware entities and functional entities. (LOOP n PV), but the values shown by the server don't seem to match those values in your controller.

The number shown on the top right-hand side of the PID block does NOT correspond with the loop number. You can find out the appropriate number by selecting FilePrintBlock Parameters in the Honeywell Control Builder The control building software, running on a Windows operating system, that provides an environment in which to build control strategies using function blocks for the Honeywell control processor. It includes Function Block Builder, SCM Builder, Function Block Symbols, SCM Symbols and Configuration Forms, SCM Blocks and Configuration Forms, Function Block Faceplate, and the Data Entry Mechanism. See also: control processor. configuration utility.

One of the properties printed out is Modbus ® loop number. Use this number for your loops.

The address PID n PV doesn't download. | The PID part of the address is not valid and doesn't appear in the Universal Modbus driver documentation. You cannot use the names of control blocks within Control Builder as Universal Modbus addresses. You can only use the addresses listed in the Universal Modbus documentation.

You know that you should use the address AI n but you don't know what value to use for n.

The analog input number is calculated using the formula In ISA-S88.01 terms, a category of recipe information that includes process inputs, process parameters, and process outputs. In Honeywell terms, the recommended implementation of a formula is through using Phase block formula and report parameters.: n = (m-1) * 4 + c.

n = the analog input number.

m = the module In SafeView, the file name and path of an executable file name. An application's module is one of the three means by which an application's display window can be “matched” and thus managed by SafeView. The other two are window title and window category./slot number. The UMC800 has 16 slots, numbered 1 to 16.

c = the channel The communications port used by the server to connect to a controller. Channels are one slot, point, or screw terminal of an I/O device for a single I/O value, and are defined using the Quick Builder tool. number (of the analog input). The analog input devices have up to four channels, numbered 1 to 4.

You know that you should use the address DI n or DO n but you don't know what value to use for n.

The digital input number is calculated using the formula: n = (m-1) * 16 + c.

n = the digital input or output number.

m = the module/slot number. The UMC800 has 16 slots, numbered 1 to 16.

c = the channel number (of the digital input or output). The digital I/O devices have up to 16 channels, numbered 1 to 16.

You want to write to a digital output. | Honeywell recommends against writing to a digital output because this forces the output to a particular state, which cannot be overridden using the UMC800 internal logic. (Since this practice is inherently dangerous, it is not supported.) You can create a safer implementation using digital variables and some UMC800 logic blocks.

You see the error:

***** PNTBLD ERROR ***** illegal MODICON plc address

in the Quick Builder The Experion tool used to configure system components, such as standard points, Flex Stations, controllers (other than process controllers), electronic flow measurement (EFM), and printers. See also: controller, electronic flow measurement (EFM), Flex Station, process controller, standard point. output when trying to download a signal tag as a source address (such as TAG 2) to the server.

You might be trying to download to a controller whose OFFSET address is not 0x2000. Refer to the Universal Modbus documentation for information about address ranges and OFFSET.

You see the error: ***** PNTBLD ERROR ***** illegal MODICON plc address in the Quick Builder output when trying to download a signal tag, such as TAG 2, as a destination address to the server. | Signal tags are read-only parameters, so cannot be used as destination addresses. Refer to the Universal Modbus documentation for information about read-only and write-only addresses.

You don't know what number to use for the signal tag using named address TAG or variable using named address MATH_VAR.

1. Start the configuration utility Honeywell Control Builder configuration utility.

2. Select FilePrint.

3. Select Tag Properties, and then click OK.

4. Your printout should show your signal tags. To the right of the words 'Signal Tag' or 'Variable' you should see a number. This is the tag number you should use in the address TAG n or MATH_VAR n.

## HC900 problems

Error message or problem | Description
--- | ---

You see the log message:

Event nnn has bad address. Cannot History Backfill event

This message occurs when points have been configured in HC (Hybrid Control) Designer with Use Signal Tag as the Trend Backfill Log Point Selectionand the backfill data cannot be matched to points built in Experion. If all the points on the controller are configured incorrectly like this, when backfill completes, the event that Experion raises will say that "No samples required backfilling into history."

To fix this problem, you must use HC (Hybrid Control) Designer to change the Trend Backfill Log Point Selection from Use Signal Tag to Use Modbus Address. If this is done after Trend A display in which changes in value over time of one or more point parameters are presented in a graphical manner. See also: display, point parameter. Point Function Blocks have been configured, you must also remove and re-add each of the points to the Trend Point Function Blocks and download the configuration to the controller. Note that doing this will also cause the controller to lose the backfill data it was storing.

You know you should use the address LOOP n parametername but you don't know what value to use for n.

You want to access the process variable of the only control loop that you have configured. You used the number n which appears on the upper-right hand corner of the PID block (LOOP n PV The process variable. An actual value in a process. In the case of an analog point, for example, the PV represents values such as temperature, flow, and pressure. A PV may also be sourced from another parameter or be calculated from two or more measured or calculated variables using a point algorithm. See also: analog point, parameter, point algorithm, PV algorithm, PV clamp, PV period. for loops 1-24 and LOOPX n PV for loops 25-32), but the values shown by the server don't seem to match those values in your controller.

The block execution order number shown on the upper right-hand side of the block does NOT correspond with the loop number. The loop number corresponds with order of entry of the PID loop blocks only. You can find the appropriate number by selecting FilePrint Report Preview, then select the FBD icon and Modbus Register MapSummary Function Block Report in the Hybrid Control (HC) Designer configuration. The Loop Blocks are listed by number. Use this number for your loops.

For analog inputs in the first rack Chassis or cardfile capable of accepting plug-in modules. See also: chassis., you know that you should use the address AI Analog Input. Compare: DI. n but you don't know what value to use for n.

For the first rack only, the analog input number is calculated using the formula:

n = (m-1) * 8 + c.

n = the analog input number

m = the module/slot number. The HC900 Hybrid controller. has up to 12 slots depending on rack size, numbered 1 to 12.

c = the channel number (of the analog input).

The analog input cards have 8 channels, numbered 1 to 8. The 2nd AI channel for slot/module 2 in Rack 1 is AI 10.

I don't know to access analog inputs beyond the first rack.

A Signal Tag is the only way to access analog inputs on a Holding Register controller. Access to analog inputs directly using Non-Named hexadecimal addressing requires Table 3 (Input Register), whereas Signal Tags use Table 4 (Holding Register).

If you have provided a Signal Tag for the Analog Input block output, use this tag number and TAG as the address name, for example, TAG 45 for a controller with an OFFSET address of 2000. Otherwise, you must use Non-Named hexadecimal addressing for a controller with an offset of 0. The address ranges for the racks are as follows:

Rack 1: 0 - FF Foundation Fieldbus. An enabling technology for dynamically integrating dedicated field devices with digitally based control systems. It defines how all "smart" field devices are to communicate with other devices in the control network. The technology is based upon the International Standards Organization's Open System Interconnection (OSI) model for layered communications. See also: Fieldbus Foundation.

Rack 2: 100-1FF

Rack 3: 200 – 2FF

Rack 4: 300 – 3FF

Rack 5: 400 – 4FF

Zero-based addressing is used and two contiguous registers comprise the floating point data. Table 3 (Modbus Function Code 4) is used for access. The first analog channel for slot/module 1 in Rack 2 is: 3:x100 IEEEFP, channel 2 is 3:x102 IEEEFP, channel 8 is 3:x10E IEEEFP. There are 8 inputs per slot/module.

For analog inputs in the first rack, you know that you should use the address DI Digital input. Compare: AI. See also: input. n or DO Digital output. Compare: AO. See also: output. n but you don't know what value to use for n.

For the first rack only, the digital or output number is calculated using the formula:

n = (m-1) * 16 + c.

n = the analog input number

m = the module/slot number. The HC900 has up to 12 slots depending on rack size, numbered 1 to 12.

c = the channel number (of the digital input or output). The digital I/O cards have 8 or 16 channels, numbered 1 to 8 or 1 to 16. An allocation A form of coordination control that assigns a resource to a batch or unit. Note that an allocation can be for the entire resource or for portions of a resource. of 16 I/O is made for each slot/module regardless of type. The 2nd DI channel for slot/module 3 in Rack 1 is DI 34.

I don't know to access digital I/O beyond the first rack.

A Signal Tag is the only way to access digital inputs and outputs on a Holding Register controller. Access to digital inputs and outputs directly using Non-Named hexadecimal addressing requires Table 1 (Digital Input) and Table 0 (Digital Output), whereas Signal Tags use Table 4 (Holding Register).

If you have provided a Signal Tag for the Digital Input or Output block output, use this tag number and TAG as the address name, for example, TAG 56 for a controller with an OFFSET address of 2000. Otherwise, you must use Non-Named hexadecimal addressing for a controller with an offset of 0. The address ranges for the racks are as follows:

Rack 1: 0 - FF

Rack 2: 100-1FF

Rack 3: 200 – 2FF

Rack 4: 300 – 3FF

Rack 5: 400 – 4FF

Zero-based addressing is used and two contiguous registers comprise the floating point data. Table 1 is used for access to digital inputs and Table 0 is used for digital outputs. The 3rd digital input channel for slot/module 6 in Rack 2 is 1:x152, the 4th digital input on the same module is 1:x153. The 5th digital output for slot/module 8 in Rack 3 is 0:x274. There are 8 inputs per slot/module. An allocation of 16 I/O is made for each slot/module regardless of type.

You want to write to a digital output. | Honeywell recommends against writing to a digital output since this forces cannot be returned to normal via Modbus communications. Use the HC Designer tool concurrently for force actions where force removal is supported. You may also use digital Variables and logic blocks in the controller configuration to implement the force more safely via Station.
You see the error: ****** PNTBLD ERROR******* illegal MODICON plc address in the Quick Builder output when trying to download a signal tag as a source address (such as TAG 2) to the server. | You might be trying to download to an All Tables controller whose OFFSET address is not 2,000. Refer to the Universal Modbus documentation about offset ranges and OFFSET.

You see the error:

****** PNTBLD ERROR******* illegal MODICON plc address

in the Quick Builder output when trying to download a signal tag such as TAG 2 as a destination address to the server.

Signal tags are read-only parameters, so cannot be used as destination addresses. You will need to use Variables in your HC900 configuration instead for writes. Refer to the Universal Modbus documentation for information about read-only and write-only addresses.

You don't know what number to use for accessing an HC900 Signal Tag or a Variable.

Start the Hybrid Control (HC) Designer configuration tool.

Select FilePrint Report Preview

Select FBD's icon in the dialog box.

Select Modbus Register MapSignal Tags and Variables from the pull-down menu.

This listing shows the Variables and Signal Tags used in the configuration listed by tag name A unique identifier given to a point or an asset. Compare: item name. See also: asset, point. and in number sequence. Use the number in the # column as your reference for use in the address TAG n (for Signal Tags) or MATH_VAR n for Variables.

You may print out this list for reference by selecting the Print button from Print Preview.

You want to know which HC900 Signal Tags or Variables are digital in nature so that they can be applied to Status points.

You can apply Signal Tags (read only) and Variables (read/write) to digital Status points if they are digital data types. See above for information related to viewing/printing the Tag Information Report. The Data Type column lists whether the parameter Also known as point parameter. A unit of information about a point. For example, an analog point includes parameters such as process variable parameter (PV), output parameter (OP) and setpoint parameter (SP). See also: analog point, output parameter, point, process variable, setpoint parameter. is Digital or Analog. If digital, you may apply to Status points. The UMB driver does the floating point conversion to integer translation to read or write an ON (1) or OFF (0) condition.

You want to know how to input a set point programmer point to use the standard screens in Station for viewing an HC900 set point programmer table and the profile pre-plot. | Consult the HC900 SPP Setpoint in percent. See also: setpoint parameter. & Recipe Support Users Guide. Support is for programmers 1-4 only. There is no UMB driver support for programmers 5-8.
You want to force a digital input on or off via status point A type of standard point that is used to represent discrete or digital field values. See also: dual-bit status point, standard point. OP parameter. | You cannot force a digital input except via the HC Designer configuration software (force DI block output in Monitor mode).

You see the error:

***** PNTBLD ERROR ***** Table Number must match controller Table Number (Table Number: x, controller Table Number: 4)

This error occurs when you used a Holding Register controller ("controller Table Number: 4"), but you specified an address that resides in a different table ("Table Number: x." – x could be 0, 1, or 3).

A Holding Register controller only supports addresses in the Holding Register table. Most named addresses reside in the Holding Register table, but some, such as DI and DO, reside in different tables. If you need to access Digital Outputs, Digital Inputs, or Analog Inputs (Input Registers) on a Holding Register controller, you can connect these to Signal Tags or Analog/Digital Variables, and then use the TAG and MATH_VAR named addresses.

You see the error: *** Cannot change Data Table - set Data Table back to All tables (RTU type: 0) | Once a controller has been downloaded to the server, its Data Table value cannot change. This message informs you of this, and notifies you of the accepted (or previously downloaded) value for this particular controller ("All tables").