Orion 2xx manual Jupiter Magnetostrictive Transmitter Foundation fieldbus

Page 15

FAULT_STATE, SET_FSTATE, CLR_FSTATE: these only apply to output function blocks. (The Model 2xx has no output function blocks).

MAX_NOTIFY: the maximum number of alert reports that the transmitter can send without getting a confirmation.

The user can set the number low, to control alert flooding, by adjusting the LIM_NOTIFY parameter value.

LIM_NOTIFY: the maximum numbers of unconfirmed alert notify messages allowed. No alerts are reported if set to zero.

CONFIRM_TIME: the time that the transmitter will wait for confirmation of receipt of a report before trying again. Retry will not occur if CONFIRM_TIME = 0.

WRITE_LOCK: When set to LOCKED, will prevent any external change to the static or non-volatile data base in the Function Block Application of the transmitter. Block con- nections and calculation results will proceed normally, but the configuration will be locked.

UPDATE_EVT (Update Event): is an alert generated by a write to the static data in the block.

BLOCK_ALM (Block Alarm): is used for configuration, hardware, connection, or system problems in the block. The cause of any specific alert is entered in the subcode field. The first alert to become active will set the Active status in the Status attribute. As soon as the Unreported status is cleared by the alert reporting task, another block alert may be reported without clearing the Active status, if the sub- code has changed.

ALARM_SUM (Alarm Summary): contains the current alert status, the unacknowledged states, the unreported states, and the disabled states of the alarms associated with the block.

ACK_OPTION (Acknowledge Option): selects whether alarms associated with the block will be automatically acknowledged.

WRITE_PRI (Write Priority): the priority of the alarm generated by clearing the write lock.

WRITE ALM (Write Alarm): the alert generated if the write lock parameter is cleared.

ITK_VER (ITK Version): contains the version of the Interoperability Test Kit (ITK) used by the Fieldbus Foundation during their interoperability testing.

46-649 Jupiter Magnetostrictive Transmitter - FOUNDATION fieldbus™

12

Image 15
Contents Magnetostrictive Level Transmitter Read this Manual Before Installing Table of Contents Description Foundation Fieldbus OverviewBenefits Device Configuration Device DescriptionsIntrinsic Safety Installation Electrostatic Discharge ESD Handling ProcedureUnpacking Before You Begin Site PreparationEquipment and Tools External Configuration InformationMounting Operational ConsiderationsInternal, Direct Insertion Position the Jupiter transmitter on the side of the MLIWiring Function Blocks OverviewUniversal Fieldbus Block Parameters Resource Block Jupiter Magnetostrictive Transmitter Foundation fieldbus Jupiter Magnetostrictive Transmitter Foundation fieldbus Password Parameters Transducer BlockTransducer Block Parameters Jupiter Configuration Parameters User Calibration ParametersFactory Parameters AI Block Parameters Analog Input BlockChannels Firmware VersionJupiter Magnetostrictive Transmitter Foundation fieldbus Diagnostic Parameters Simulation Feature Troubleshooting TroubleshootingReference Information Display Message Action Comment Status MessagesSize Length Type FF Segment ChecklistAgency Approvals Agency specifications Atex Intrinsically safeAgency Drawing Agency Drawing Specifications FunctionalPerformance Inches mm PhysicalParts Replacement PartsEnhanced Jupiter Magnetostrictive Transmitter Model NumbersNone, defines external mount Direct Insertion Total Level Float Selection References Appendix Transducer Block ParametersJupiter Magnetostrictive Transmitter Service Policy