Related Manuals for Phoenix Contact Fieldbus FB-DIAG/FF/LI
Summary of Contents for Phoenix Contact Fieldbus FB-DIAG/FF/LI
- Page 1 Field diagnostics module for monitoring Foundation Fieldbus™ fieldbus segments User manual UM EN FDM...
- Page 2 User manual Field diagnostics module for monitoring Foundation Fieldbus™ fieldbus segments 2014-11-13 Designation: UM EN FDM Revision: This user manual is valid for: Designation Version Order No. FB-DIAG/FF/LI 2316284 FB-DIAG/FF/NC 2316297 PHOENIX CONTACT 3228_en_A...
- Page 3 How to contact us Internet Up-to-date information on Phoenix Contact products and our Terms and Conditions can be found on the Internet at: www.phoenixcontact.com Make sure you always use the latest documentation.
- Page 4 The receipt of technical documentation (in particular user documentation) does not consti- tute any further duty on the part of Phoenix Contact to furnish information on modifications to products and/or technical documentation. You are responsible to verify the suitability and intended use of the products in your specific application, in particular with regard to observ- ing the applicable standards and regulations.
-
Page 5: Table Of Contents
Mapping alerts to an AI or DI block ..............22 3.10 FB-DIAG⁄FF⁄… device identification..............24 Technical appendix........................25 FB-DIAG⁄FF⁄… parameters ................. 25 Parameter descriptions..................28 Alerts and recommended actions ............... 34 Foundation Fieldbus field diagnostic alerts............37 Foundation Fieldbus field diagnostic alerts ............39 3228_en_A PHOENIX CONTACT... - Page 6 FB-DIAG/FF/… Appendixes..........................41 List of figures ...................... 41 List of tables ....................... 43 Explanation of terms ................... 45 PHOENIX CONTACT 3228_en_A...
-
Page 7: Introduction
This may be either by the use of an enclosure approved for use in zones 2 or 22, or by meeting the following requirements: – Non-metallic enclosures must be capable of withstanding the thermal endurance requirements of IEC 60079-0 prior to impact and IP54 testing. 3228_en_A PHOENIX CONTACT... -
Page 8: Csa Conditions For Certification
CSA conditions for certification This device is “open” type equipment that must be used within a suitable end-use system enclosure. The suitability of the enclosure is subject to investigation by the “local authority having jurisdiction” at the time of installation. PHOENIX CONTACT 3228_en_A... -
Page 9: Installation
DIN rail. Push the bottom of the module toward the DIN rail until the bottom foot snaps onto the rail. Figure 2-1 Installation Connection μC F– Figure 2-2 FB-DIAG⁄FF⁄LI block diagram 3228_en_A PHOENIX CONTACT... -
Page 10: Typical Installation
Figure 2-3 FB-DIAG⁄FF⁄NC block diagram Typical installation The FB-DIAG⁄FF⁄NC is intended to be installed with the Phoenix Contact modular device coupler system. Installation of the FB-DIAG⁄FF⁄NC is to the right of an FB-ET trunk module on a segment. Figure 2-4 Typical installation of FB-DIAG⁄FF⁄NC... -
Page 11: Led Indicators
LED flashes six times. At the time the error is cleared, the COMM LED will flash for two additional cycles (1.4 Hz * 2) Table 2-1 shows the LED reaction based on different states: 3228_en_A PHOENIX CONTACT... - Page 12 An FB-DIAG⁄FF⁄… failure (non-flashing Err LED trigger event) will persist until the FB-DIAG⁄FF⁄… is reset or power cycled. If the Err LED does not reset, contact the manufacturer (see “Resetting diagnostic data alarms” on page 17). PHOENIX CONTACT 3228_en_A...
-
Page 13: Operation
Device add drop Device data – Address – Device tag (available in DTM automatically, or inserted by an operator in the EDDL) – Fieldbus signal level – Add/drop state – Retransmits – Trend assignment (available in DTM only) Alarms 3228_en_A PHOENIX CONTACT... -
Page 14: Standard Alarms
Output signal is temporarily invalid (frozen) due to ongoing work on the device. Failure Output signal is invalid due to a malfunction in the field device or its peripherals. Descriptions from Function Block Fieldbus Specification, Part 2: FF-891 FS 1.10 PHOENIX CONTACT 3228_en_A... -
Page 15: Field Diagnostic Alerts
“Maintenance” dialog box For a Foundation Fieldbus host that does not support the alert mechanism, they can poll “_Active” parameters to show field diagnostic conditions. For more detail, please refer to Fieldbus Foundation Specification FF-891 available from www.fieldbus.org. 3228_en_A PHOENIX CONTACT... -
Page 16: Host Support Files
EDDL or DD Support files can be downloaded from www.Fieldbus.org/End user resources/registered products. From the “Manufacture” drop-down menu, select Phoenix Contact. From the “Category” drop-down menu, select Diagnostic. Alternatively, go to Phoenixcontact.com, search for the order number, and click the “Downloads”... -
Page 17: Viewing Device Information
Figure 3-4 Sample “Individual Device Info” page for an EDDL file The DTM operator interface provides a complete list of all the devices on the segment along with their PD Tag. Figure 3-5 Typical view of DTM devices 3228_en_A PHOENIX CONTACT... -
Page 18: Setting Alarm Limits
2. Alarm limits can be viewed and edited utilizing whichever file type is desired. Figure 3-6 Typical “Alarm Limits” page for EDDL file Figure 3-7 Typical “Alarm Limits” page for DTM file PHOENIX CONTACT 3228_en_A... -
Page 19: Detecting And Diagnosing An Alert
The “Diagnostic Variable Summary” page contains information about which alert is activate, and information supporting the conditions for the alert, possible causes for the alert and recommended actions to correct the alert. EDDL and DTM alerts will sometimes include recommended actions. 3228_en_A PHOENIX CONTACT... - Page 20 FB-DIAG⁄FF⁄… Figure 3-10 Typical EDDL alert message with recommended actions Figure 3-11 Typical DTM alert message with recommended actions PHOENIX CONTACT 3228_en_A...
-
Page 21: Resetting Diagnostic Data Alarms
Overall devices reset – Reset retransmit counters – Reset shield short circuit – Reset all diagnostic data Figure 3-12 Typical “Alarm Limits” page for an EDDL file Figure 3-13 Typical “Alarm Limits” page for a DTM file 3228_en_A PHOENIX CONTACT... -
Page 22: Trend Data
Device retransmits Two devices can be chosen from the list of active device addresses. Simultaneous trending of these two devices will be shown, indicating total retransmits for each device. Figure 3-14 Typical “Device Diagnostics/Trends” page for EDDL file PHOENIX CONTACT 3228_en_A... -
Page 23: Dtm Trend Data
Click the “CSV Export” button. Browse to the desired location and name the file. The report will contain data from all four trending pages: – Average segment noise – Segment voltage – Device signal level – Device retransmits 3228_en_A PHOENIX CONTACT... -
Page 24: Commissioning Reports
DD and EDDL system configurations do not have commissioning report capabilities. 3.8.1 DTM commissioning report To create a commissioning report: Click the “DTM” menu and select “Configure” from the menu. Click the “Segment Commissioning Report” button. Figure 3-16 Commissioning “Report” page PHOENIX CONTACT 3228_en_A... -
Page 25: Commissioning Report "Overview" Page
Click the “Save” button next to the report type to save the report using the name and location desired. The report contains: – Overview page. – Alerts, if any, with recommended actions to correct alarms. – Trend pages. Figure 3-17 Commissioning report “Overview” page 3228_en_A PHOENIX CONTACT... -
Page 26: Mapping Alerts To An Ai Or Di Block
PV Peak Low Noise Channel 7 - Peak low-frequency LOW_FREQUENCY _NOISE.PEAK noise PV Avg High Noise Channel 8 - Average high-fre- HIGH_FREQUENCY _NOISE.AVERAGE quency noise PV Peak High Noise Channel 9 - Peak high-frequency HIGH_FREQUENCY_NOISE.PEAK noise PV PHOENIX CONTACT 3228_en_A... - Page 27 Sensor Alert Channel 19 - If on, the (FBK2 cannot communicate w/ FBT6) OR FB-DIAG⁄FF⁄… has encountered (FBT6 fails three consecutive checksums) a loss of communication with the OR (RAM Error) OR (ROM Error) sensor board 3228_en_A PHOENIX CONTACT...
-
Page 28: Fb-Diag⁄Ff
FB-DIAG⁄FF⁄… device identification In addition to the standard Foundation Fieldbus device identification, the FB-DIAG⁄FF⁄… has hardware and firmware revision information for the device. Figure 3-18 EDDL hardware and firmware revision information Figure 3-19 DTM hardware and firmware revision information PHOENIX CONTACT 3228_en_A... -
Page 29: A Technical Appendix
LAS_ADDRESS Unsigned8 none LOWEST_SIGNAL_LE Record: Read only PD_Tag none Address none Value Time (DS-21) time stamp DEVICE_ADD_ Record: Read DROP only PD_Tag none Address none Add_Drop_St 0: Not initialized, 1: Added 2: Dropped Time (DS-21) time stamp 3228_en_A PHOENIX CONTACT... - Page 30 SIGNAL_LEV ADD_DROP_ Read STATE only Read only RETRANSMIT none Read Only DEVICE_INFO_2 Record: 0: Not Initialized, 1: Added ADDRESS Read 2: Dropped only PD_TAG none Writable SIGNAL_LEV ADD_DROP_ Read STATE only Read only RETRANSMIT none Read Only PHOENIX CONTACT 3228_en_A...
- Page 31 Noise 0xA3: Reset Peak LF Noise 0xA4: Reset Lowest Signal Level 0xA5: Overall Devices Reset 0xA6: Reset Retransmit Counters 0xA7: Reset Shield Short 0xA8: Reset All Diagnostic Data TEMPERATURE Integer8 -40 to 90°C valid (-40 to 127°F) 3228_en_A PHOENIX CONTACT...
-
Page 32: A 2 Parameter Descriptions
This function detects the presence of shorts between the cable shield and the + or - signal wire. If no short is detected between the shield and a signal wire, “No Shorts” is displayed. If a short circuit between the + signal wire and the cable shield is detected, “(+) TO SHIELD PHOENIX CONTACT 3228_en_A... - Page 33 FB-DIAG⁄FF⁄… was connected to the fieldbus (or since the function was last reset). By default, measurements greater than 150 mV are OK. The date and time the low signal level was measured is also displayed. 3228_en_A PHOENIX CONTACT...
- Page 34 The segment maximum high-frequency noise before the FB-DIAG⁄FF⁄… sends an alarm out NOISE on the bus. The limit is based on the HIGH_FREQUENCY_NOISE.AVERAGE. ALARM_LIMITS.MAX_FF_ The segment maximum fieldbus noise before the FB-DIAG⁄FF⁄… sends an alarm out on the NOISE bus. The limit is based on the FBUS_FREQUENCY_NOISE.AVERAGE. PHOENIX CONTACT 3228_en_A...
- Page 35 If device xx is added to the segment since the last reset, this parameter will indicate that it OP_STATE has been added. If a device does not respond to a “Pass Token” frame, then device xx is considered “dropped”. 3228_en_A PHOENIX CONTACT...
- Page 36 REVISION.HARDWARE Hardware Revision of the FB-DIAG⁄FF⁄…. (Based on the Phoenix Contact V/C code. Must be written at time of manufacturing. Value is written by writing a 0x50 to the parameter followed by a second write that contains the desired value.) RETRANSMITS.
- Page 37 Parameter mnemonic View_1 View_2 View_3 View_3 View_3 View_4 index ST_REV TAG_DESC STRATEGY ALERT_KEY MODE_BLK BLOCK_ERR UPDATE_EVT BLOCK_ALM TRANSDUCER_DIRECTORY TRANSDUCER_TYPE XD_ERROR COLLECTION_DIRECTORY SEGMENT_VOLTAGE SHIELD_SHORT NUMBER_ACTIVE_DEVICES LOWEST_SIGNAL_LEVEL FBUS_FREQUENCY_NOISE LOW_FREQUENCY_NOISE HIGH_FREQUENCY_NOISE LAS_ADDRESS DEVICE_ADD_DROP ALARM_LIMITS DATA_RESET ACTIVE_ADDRESS DEVICE_INFO_1 DEVICE_INFO_2 TEMPERATURE DETAILED_STATUS RETRANSMITS 3228_en_A PHOENIX CONTACT...
-
Page 38: A 3 Alerts And Recommended Actions
(trunk length + length of all spurs) does not exceed 1900 m and the length of individual spurs does not exceed 120 m. Try putting the device on a different spur from the wiring block. Replace the device. PHOENIX CONTACT 3228_en_A... - Page 39 Measure resistance from shield to ground with a multimeter and verify it is <100 . Disconnect devices one at a time to see if noise disappears. Replace terminators, fieldbus power supplies, and wiring blocks. 3228_en_A PHOENIX CONTACT...
- Page 40 Try putting the device on a different spur from the wiring block. Replace the device. Sensor diagnostic board issues Sensor board status indicates an error. Power cycle device: if issue persists then replace the device. PHOENIX CONTACT 3228_en_A...
-
Page 41: Foundation Fieldbus Field Diagnostic Alerts
*_PRI parameter. The four categories are: Maintenance Although the output signal is valid, the wear reserve is nearly exhausted or a function will soon be restricted due to operational conditions. For example, the build-up of deposits. 3228_en_A PHOENIX CONTACT... - Page 42 Fail, Maint, OffSpec, and Check 32 bits. There is also no restriction on which bits out of the standard 32 may be used for the fail, maintenance, off- specification, or check categories. PHOENIX CONTACT 3228_en_A...
-
Page 43: A 5 Foundation Fieldbus Field Diagnostic Alerts
A bit equal to 1 will mask, i.e., inhibit, the broadcast of a condition, and a bit equal to 0 will unmask, i.e., allow, broadcast of a condition. 3228_en_A PHOENIX CONTACT... - Page 44 FD_MAINT_PRI: This parameter allows the user to specify the priority of this alarm category. FD_CHECK_PRI: This parameter allows the user to specify the priority of this alarm category. FD_RECOMMEN_ACT: This parameter describes the recommended action to correct an alert. PHOENIX CONTACT 3228_en_A...
-
Page 45: Appendixes
DTM trending page ................20 Figure 3-16: Commissioning “Report” page ............20 Figure 3-17: Commissioning report “Overview” page ..........21 Figure 3-18: EDDL hardware and firmware revision information ......24 Figure 3-19: DTM hardware and firmware revision information ....... 24 3228_en_A PHOENIX CONTACT... - Page 46 FB-DIAG/FF/… PHOENIX CONTACT 3228_en_A...
-
Page 47: List Of Tables
Table 3-3: AI block channels ................22 Table 3-4: DI block channels ................23 Appendix A Table A-1: FB-DIAG⁄FF⁄… parameters and description ......... 25 Table A-2: Parameter views .................. 33 Table A-3: Alerts and recommended actions ............34 3228_en_A PHOENIX CONTACT... - Page 48 FB-DIAG/FF/… PHOENIX CONTACT 3228_en_A...
-
Page 49: B 3 Explanation Of Terms
Foundation Fieldbus Fieldbus A fieldbus is a digital, two-way, multi-drop communication link among intelligent measurement and control devices. It serves as a Local Area Network (LAN) for advanced process control, remote input/output, and high-speed factory automation applications. 3228_en_A PHOENIX CONTACT... - Page 50 Capability of an electronic device to monitor its own status and indicate faults that occur within the device. Spur A spur is an H1 branch line connecting to the trunk that is a final circuit. A spur can vary in length from 1 m (3.28 ft.) to 120 m (394 ft.). PHOENIX CONTACT 3228_en_A...
- Page 51 Knowledge of VCRs is generally not required for newer systems that are available today. Virtual field device (VFD) A virtual field device (VFD) is used to remotely view local device data described in the object dictionary. A typical device will have at least two VFDs. 3228_en_A PHOENIX CONTACT...
- Page 52 FB-DIAG/FF/… PHOENIX CONTACT 3228_en_A...
Need help?
Do you have a question about the Fieldbus FB-DIAG/FF/LI and is the answer not in the manual?
Questions and answers