User-defined export, import, and bulk editing > Bulk editing configuration objects > Bulk editing CHARM I/O cards and CHARMs

Non-SIS CHARM HART device syntax table

HART devices must be bulk edited separately. You can use the charmHART.fmt file or create your own fmt file. 

Note

Even though the condition masks are exported, it is not practical to edit the masks using Bulk Edit because it is not easy to determine how the bits map to conditions. If you need to change condition masks create a new template after configuring the conditions as desired.

The available fields when creating a format file for non-SIS CHARM HART devices are listed in the following table.

Field

Valid Values

Required for Import

cioc_name

16 characters or fewer

Yes

charm_slot_no

8 banks of 12 CHARMs:

CHM1-01 through CHM8-12

Yes

charm_enabled

T, F

No

charm_class

see CHARM Classes and Types

Yes

charm_type

see CHARM Classes and Types

No

charm_functionality

see CHARM Classes and Types

No

charm_assigned_to

The controller to which this CHARM is assigned

No

device_tag

16 characters or fewer. The string must contain at least one alphabetical character and can include the following characters: $, -, and _.

default: <cioc_name>CHMx-yy

No

hart_long_tag

As many as 32 characters.

No

hart_device_signal_tag

16 characters or fewer. The string must contain at least one alphabetical character and can include the following characters: $,  -,  and _.

Yes

hart_device_id

A unique number between 1 and 4294967295

No

hart_device_description

User-configured description

No

hart_device_manufacturer

The manufacturer of the HART device

Yes(1)

hart_device_type

The type of HART device

Yes(1)

hart_device_rev

The revision level of the HART device

Yes(1)

enable_dev_alarms

T = enabled

F = disabled

No

primary_display

Valid picture name

No

faceplate_display

Valid picture name

No

failed_mask_48

Byte string representing the Device alarm conditions set to FAILED

No

failed_mask_subsys

Byte string representing the Subsystem and SIS alarm conditions set to FAILED

No

failed_mask_status

Byte string representing the Status alarm conditions set to FAILED

No

maint_mask_48

Byte string representing the Device alarm conditions set to MAINTENANCE

No

maint_mask_subsys

Byte string representing the Subsystem and SIS alarm conditions set to MAINTENANCE

No

maint_mask_status

Byte string representing the Status alarm conditions set to MAINTENANCE

No

advise_mask_48

Byte string representing the Device alarm conditions set to ADVISORY

No

advise_mask_subsys

Byte string representing the Subsystem and SIS alarm conditions set to ADVISORY

No

advise_mask_status

Byte string representing the Status alarm conditions set to ADVISORY

No

suppress_mask_48

Byte string representing the Device alarm conditions that are suppressed

No

suppress_mask_subsys

Byte string representing the Subsystem and SIS alarm conditions that are suppressed

No

suppress_mask_status

Byte string representing the Status alarm conditions that are suppressed

No

Alarms and Alarm Help

ADVISE_ALM.ENABLE

T or F

No

ADVISE_ALM.PRIORITY

Any valid alarm priority(2)

No

COMM_ALM.ENABLE

T or F

No

COMM_ALM.PRIORITY

Any valid alarm priority(2)

No

FAILED_ALM.ENABLE

T or F

No

FAILED_ALM.PRIORITY

Any valid alarm priority(2)

No

MAINT_ALM.ENABLE

T or F

No

MAINT_ALM.PRIORITY

Any valid alarm priority(2)

No

(1) If hart_device_manufacturer, hart_device_type, and hart_device_rev are populated, the device_subtype field is ignored. The device_subtype field is required if any of the hart_* fields are blank.
(2) The pick lists in the Excel add-in show the system-defined alarm priorities only. If these priorities have been renamed or if new priorities have been added then the pick lists are not updated. You can enter these priorities manually.