ABB CoreSense M10 User Manual
  1. Manuals
  2. Brands
  3. ABB Manuals
  4. Measuring Instruments
  5. CoreSense M10
  6. User manual
ABB CoreSense M10 User Manual

ABB CoreSense M10 User Manual

Multi-gas monitoring system
Hide thumbs Also See for CoreSense M10:
Table of Contents

Advertisement

Quick Links

Download this manual
—
U S E R G U I D E
CoreSense M10
Multi-gas monitoring system

Advertisement

Table of Contents
loading

Related Manuals for ABB CoreSense M10

Summary of Contents for ABB CoreSense M10

  • Page 1 — U S E R G U I D E CoreSense M10 Multi-gas monitoring system...
  • Page 2 ABB product catalogs, the latter takes precedence. ABB reserves the right to make changes to the specifications of all equipment and software, and contents of this document, without obligation to notify any person or organization of such changes. Every effort has been made to ensure that the information contained in this document is current and accurate.

  • Page 3: Table Of Contents

    Configuring analyzer ID and date/time ....8 Configuring Ethernet ports ........10 8 Troubleshooting Assigning an IP address (SCADA port) ..10 About your CoreSense M10 software ....41 Enabling DHCP Client for SCADA Port ..11 Diagnosing problems ......... 42 Enabling DHCP Server on Service Port ..11 Understanding cabinet LEDs ......
  • Page 4 Changing the active source .......D97 Resetting source odometers ....D98 Reinitializing source initial data ....D98 Managing Coresense M10 configurations .. D98 Backing up the current configuration ..D99 Restoring a configuration ......D99 Toggling validation of the golden reference spectrum ............

  • Page 5: Introducing Coresense M10 Software

    Once your CoreSense M10 multi-gas monitoring system has been properly installed as explained in the CoreSense M10 installation guide, you can monitor the various gases found in your transformer. You can achieve this using the provided software. The following pages explain how to maximize your use of this software.

  • Page 6: Logging In To Your System

    Logging in to your system You access your system via a web browser. The CoreSense M10 software supports the latest versions of commonly used web browsers. Google Chrome and Microsoft Edge are strongly recommended. To access the system, simply point your browser to the address provided by your DHCP server (as indicated on the analyzer cabinet internal touchscreen) or by your network administrator.

  • Page 7: Introducing The Dashboard

    — Figure 2 CoreSense M10 dashboard Menu bar Status bar Measurements NOTICE On first startup of a new CoreSense M10 instrument, allow up to 45 minutes for the first measurement points to appear on the dashboard.. Introducing CoreSense M10 software...
  • Page 8 Page intentionally left blank...

  • Page 9: Setting Up The Analyzer

    Once you are in contact with the monitoring system, you can modify a few basic parameters, as explained in the following pages. You access your system via a web browser. The CoreSense M10 software supports the latest versions of commonly used web browsers. Google Chrome and Microsoft Edge are strongly recommended.
  • Page 10 3 In the General Settings section, change passwords for operators and/or administrators, as necessary (see Figure 4 on page 6). — Figure 4 Password Settings section 4 At the bottom of the page (depending on the size of your screen, you might have to scroll down), click Apply to save the password(s).

  • Page 11: Activating The Sensor Head Thermal Pump

    The thermal pump will fail within minutes if operated in air. To activate the thermal pump: 1 From the CoreSense M10 dashboard (see Figure 2 on page 3), click Settings. The Settings page appears (see Figure 3). 2 Click Administration settings and enter your password (for more information on passwords, see “Changing passwords”...

  • Page 12: Configuring Analyzer Id And Date/Time

    Therefore, the computer connected to the CoreSense M10 shall be set to the local timezone for the following operations to be successful. To properly configure time settings: 1 From the CoreSense M10 dashboard (see Figure 2 on page 3), click Settings. The Settings page appears. 2 Click Administration settings.
  • Page 13 4 Set the time and date. – Click the calendar icon to the right of the Analyzer date/time field and select the appropriate date and time for your monitoring system. — Figure 7 Setting a date and time manually – Check the Use NTP Server box and enter a proper local Network Time Protocol server IP address in the field underneath.

  • Page 14: Configuring Ethernet Ports

    — Figure 9 Restart required dialog box 6 Click Reboot now. The CoreSense M10 system reboots and the changes that you made are applied. Configuring Ethernet ports The CoreSense M10 system cabinet comes with two Ethernet ports: SCADA and Service.

  • Page 15: Enabling Dhcp Client For Scada Port

    Activating this option will allow access to the administration settings menu when accessing the CoreSense M10 web page via the SCADA port. When the option si deactived, the administration settings page is only accessible using a computer connected to the Service port. The access is enable by default on the system.

  • Page 16: Spectrometer Settings

    To enable/disable this feature: 1 From the CoreSense M10 dashboard (see Figure 2 on page 3), click Settings. The Settings page appears (see Figure 3). 2 Click Administration settings and enter your password if necessary (for more information on passwords, see “Changing passwords” on page 5).

  • Page 17: Configuring For Transformer Fluid Type

    You need to set the fluid property temperature based on the standard used by your local transformer fluid analysis laboratory. The factory-set standard is STP and can be changed following these steps: 1 From the CoreSense M10 dashboard (see Figure 2 on page 3), click Settings. The Settings page appears (see Figure 3).
  • Page 18 Page intentionally left blank...

  • Page 19: Configuring Communication Protocols

    DHCP clients or with static IP addresses. You access your system via a web browser. The CoreSense M10 software supports the latest versions of commonly used web browsers. Google Chrome and Microsoft Edge are strongly recommended.

  • Page 20: Modbus

    Modbus The Modbus communication protocol is available on the RS-485 serial interface and the Ethernet SCADA and optical Ethernet ports. The figure below shows the default Modbus configuration. You can change it based on your system administrator’s indications. NOTICE The Modbus slave ID is 1. —...

  • Page 21: Dnp3

    2 Click Save and, in the Browse window that appears, select a location for the file that you are about to save. The CoreSense M10 creates a .xml file in the directory that you chose. Configuring communication protocols...

  • Page 22: Iec 61850

    2 Click Save and, in the Browse window that appears, select a location for the file that you are about to save. The CoreSense M10 creates an .icd file in the directory that you chose. NOTICE The content of the file generated with this procedure is the complete ICD file.

  • Page 23: 4-20 Ma Output Channels

    4–20 mA output channels In the CoreSense M10, 4–20 mA outputs can be defined for up to eight gas sensors (channels 1 to 8). All channels can be configured the same way. In the following procedure, channel 1 is used as an example.
  • Page 24 Page intentionally left blank...

  • Page 25: Configuring 4-20 Ma Input Channels

    Each channel can be given a specific unit and be enabled or disabled as necessary. To configure these settings: 1 From the CoreSense M10 dashboard, click Settings. The Settings page appears. 2 Click Sensors settings and enter your password when asked. The Sensors Settings page appears.
  • Page 26 — Figure 19 Selecting an input channel User Guide...

  • Page 27: Setting Sensor Scaling

    Click Apply at the bottom of the page to save your changes. Setting post-processing channel values With the CoreSense M10, it is possible to add additive and/or multiplicative correction factors to raw sensor data. In CoreSense M10, multiplicative factors are known as slopes and additive factors, as offsets.

  • Page 28: Setting Channel Level Alarms And Warnings

    Setting channel level alarms and warnings Each input channel supports two user-configurable thresholds for both alarms and warnings. It is your responsibility to define these thresholds and enter the appropriate values in the Level validation section. When entering values for these thresholds, you must ensure that warning values, if ever attained, are attained before alarm values.

  • Page 29: Configuring Gas Sensors

    Under normal circumstances, CoreSense M10 gas sensors need little to no fine-tuning. At the factory, the CoreSense M10 is configured to report level warnings and alarms for the following measurement points: moisture (H₂O), hydrogen (H₂), methane (CH₄), acetylene (C₂H₂), ethylene (C₂H₄), ethane (C₂H₆), carbon monoxide (CO), carbon dioxide (CO₂), and total dissolved combustible...

  • Page 30: Configuring Alarms And Warnings For Gas Level Events

    Configuring alarms and warnings for gas level events The CoreSense M10 multi-gas monitoring system is delivered with preset gas level event warnings and alarms. It is possible to modify these default presets. The system supports two user-configurable thresholds for level alarms and two additional user-configurable thresholds for rate-of-change alarms.
  • Page 31 — Figure 24 Selecting a value or gas to configure 5 Enter the appropriate values in the Level validation fields, and check the Enable... box for each relevant value to consider. — Figure 25 Entering post-processing values 6 Click Apply to save the parameters that you just set. Configuring gas sensors...

  • Page 32: Rate Of Change (Roc)

    To configure these settings: 1 From the CoreSense M10 dashboard, click Settings. The Settings page appears. 2 Click Sensor settings. The Sensor settings page appears. 3 Click the arrows adjacent to DGA and fgs. A list of all sensor-measured values appears.
  • Page 33 — Figure 27 Selecting a value or gas to configure 5 Enter the appropriate values in the Rate of Change validation fields, and check the Enable... box for each relevant value to consider. — Figure 28 Entering post-processing values 6 Click Apply to save the parameters that you just set. Configuring gas sensors...

  • Page 34: Setting Advanced Processing Parameters

    The procedures below briefly explain how to enable these processing parameters. With the CoreSense M10, it is possible to add additive and/or multiplicative correction factors to raw sensor data. In CoreSense M10, multiplicative factors are known as slopes and additive factors, as offsets.

  • Page 35: Gas Sensor General Settings

    Gas Sensor General settings Some values can be disabled from the Gas Sensor Settings page. Once the Enabled box is unchecked the corresponding value is removed from the dashboard and stops being updated on the various protocols. By default all sensor values are Enabled. Under normal operation the parameter shall remain Enabled. —...
  • Page 36 Page intentionally left blank...

  • Page 37: Managing Events

    Managing events Events happen inside the system: configuration changes, status changes (warning to alarm, warning to normal, etc.), system errors and reboots, etc. These events can be recorded with the CoreSense M10. The following pages explain how to manage these events.

  • Page 38: Individually

    To acknowledge all events remotely: 1 Click Acknowledge all on the Events page. The Acknowledgment dialog box appears. — Figure 32 Acknowledgment dialog box 2 Enter your name in the Name field and, if necessary, enter comments in the text box underneath. 3 Click Acknowledge.

  • Page 39: Selecting A Specific Time Period

    Selecting a specific time period To select events that happened over the course of a specific time period: 1 From the CoreSense M10 dashboard, click Events in the menu bar. The events table appears. — Figure 35 Events page 2 From the drop-down list above the Date column, you can select a predefined time period. The event list underneath is updated to reflect the selected time period.

  • Page 40: Exporting Events

    For both the From and To fields, click the date selector on the right and select the beginning and end of the required time period. The event table updates accordingly. Exporting events You can export events from the CoreSense M10 software for analysis in another software, for example. Events are exported in a .csv file format. NOTICE If you used accents, spaces or special characters when naming your device, exported files will not work properly.

  • Page 41: Managing History Data

    C h a p t e r 7 Managing history data The CoreSense M10 analysis module applies a certain level of processing to raw data for analysis purposes. It also calculates the rate of change of this data. All this information can be retrieved and exported for further analysis with your favorite tool for dissolved gases software.

  • Page 42: Selecting A Specific Time Period

    gases or channel data whose history has been recorded. 3 Click the arrow next to a gas or channel whose history you want to display (see Figure 39). This opens up a list of available data for this specific gas or channel. —...

  • Page 43: Exporting History Files

    Date selectors Exporting history files You can export history files from the CoreSense M10 software for analysis using specialized software. When exporting gas sensor (fgs) history, all gas values, oil temperatures and TDCGs are downloaded automatically for all 10 gases over the specified time period. However, when exporting channel history files, each channel is exported independently.
  • Page 44 Page intentionally left blank...

  • Page 45: Troubleshooting

    Whenever you need to contact the after-sales service for troubleshooting purposes, you can do so from the About CoreSense M10 menu. When you select this item from the menu bar, an About CoreSense™ M10 box appears where you can obtain the various software versions on-board the analysis module as well as the email address to contact the after-sales service.

  • Page 46: Diagnosing Problems

    Diagnosing problems Most problems that could happen within the CoreSense M10 monitoring system will be recorded as events in the Events log. You will be informed of these problems either with alarms or by looking at the LEDs on the system cabinet or sensor head. The meaning of the various LEDS is explained below.

  • Page 47: Understanding Sensor Head Leds

    YELLOW this indicator light will remain Gas level of at least one gas Moisture levels Or 24-hour on while the CoreSense M10 Or 24-hour rate-of-change rate-of-change are above is booting up. If the sensor of at least one gas is above...

  • Page 48: Managing System Logs

    All system logs are saved in a predefined folder. They contain all sorts of information relevant to a trained service personnel. To access and select a system log file: 1 From the CoreSense M10 dashboard (see Figure 2 on page 3), click Settings. The Settings page appears. 2 Click System Logs.

  • Page 49: Exporting System Logs

    — Figure 46 Selecting a system log file Exporting system logs To export system logs, click Export All and select where you want to save the .zip file (saving options vary with each browser). Troubleshooting 45...

  • Page 50: Managing Spc Files

    The following procedures explain how to generate spectrum files that ABB applications support representatives might need to improve/fix technical problems with your system. Selecting SPC files 1 From the CoreSense M10 dashboard (see Figure 2 on page 3), click Settings. The Settings page appears. 2 Click SPC files.

  • Page 51: Exporting Spc Files

    • If you selected Custom range, the adjacent From and To fields become active. For both fields, click the date selector on the right (see Figure 49) and select the beginning and end of the required time period. The list of spectrum files changes according to the time period selected. —...

  • Page 52: Enabling Remote Access For Service

    To update the firmware via a web browser: 1 Skip to step 2 if you are working remotely. Otherwise, open the CoreSense M10 cabinet and connect your laptop to an Ethernet communication port (SCADA or SERVICE) of the analytical unit with a straight RJ45 Ethernet cable.
  • Page 53 Figure 52 Firmware update page Your system reboots once the firmware is updated. Multiple reboot sequences may be required depending on actions required on the CoreSense M10. 9 After the system has been automaticaly rebooted, return to the web page and click About CoreSense™...

  • Page 54: Updating With A Usb Key

    3 Shutdown the instrument using the main power switch. — Figure 53 Instrument main power switch 4 Insert the USB key on the USB port of the CoreSense M10 cabinet. — Figure 54 Instrument USB port 5 Turn on the instrument using the main power switch (see Figure 4). The update process will start automatically and take a few minutes.
  • Page 55 — Figure 55 Screen calibration The system firmware is considered complete after this last step. Wait until the Dashboard page is displayed for at least 4 minutes (after the reboot, the Dashboard page might be empty for the first 20 minutes). Troubleshooting...
  • Page 56 User Guide...

  • Page 57: Rs-485 Configuration

    — A p p e n d i x A Modbus The RS-485 and Modbus default settings can be modified using the web interface. NOTICE For best results it is recommended to configure the Modbus master with a timeout of 10000 ms and 5 retries.

  • Page 58: Modbus Parameters

    System status see <Status> 16-bit binary map see <Status> table table 40054 FGS status internal error signed 16-bit binary number ABB service dissolved gas and moisture 40055 Moisture status 16-bit binary map see <Gas status> table 40056 Moisture (aw) scaled by...
  • Page 59 Register Modbus Parameter Function Datatype DataRange number 40064 ReSeRVed–Hydrogen RoC return 0 signed 16-bit binary number (ppm/week) 40065 ReSeRVed–Hydrogen RoC return 0 signed 16-bit binary number (ppm/month) 40066 CO status 16-bit binary map see <Gas status> table 40067 CO (ppm) signed 16-bit binary number 40068 CO RoC (ppm/day)
  • Page 60 Register Modbus Parameter Function Datatype DataRange number 40090 RESERVED–C₂H₄ RoC (ppm/ return 0 signed 16-bit binary number month) 40091 C₂H₆ status 16-bit binary map see <Gas status> table 40092 C₂H₆ (ppm) signed 16-bit binary number 40093 C₂H₆ RoC (ppm/day) signed 16-bit binary number 40094 RESERVED–C₂H₆...
  • Page 61 Register Modbus Parameter Function Datatype DataRange number System iO 40200 Oil temperature (Celsius) signed 16-bit binary number 40201 4–20 mA input 1 scaled by 100 signed 16-bit binary number 40202 4–20 mA input 2 scaled by 100 signed 16-bit binary number 40203 4–20 mA input 3 scaled by 100...
  • Page 62 Page intentionally left blank...

  • Page 63: B Dnp3

    A p p e n d i x B DNP3 The CoreSense M10 DNP3 outstation implementation is compliant to level 1 and level 2. You can communicate with the sensor using a data link address = 1. DNP3 is available on the RS-485 serial interface or on the Ethernet interfaces.
  • Page 64 Pointmap1 2 3 4 5 Analog input Binary input Name Point index Unit Name Point index 4–20 mA input 1 4–20 mA input 2 4–20 mA input 3 4–20 mA input 4 CH4_Lev_Warn CH4_Roc_day ppm/day CH4_Lev_Crit Reserved – CH4_Roc_Warn Reserved –...
  • Page 65 Analog input Binary input Name Point index Unit Name Point index Reserved – C2H6_Roc_Warn Reserved – C2H6_Roc_Crit C3H6 C3H6_Lev_Warn C3H6_Roc_day ppm/day C3H6_Lev_Crit Reserved – C3H6_Roc_Warn Reserved – C3H6_Roc_Crit C3H8 C3H8_Lev_Warn C3H8_Roc_day ppm/day C3H8_Lev_Crit Reserved – C3H8_Roc_Warn Reserved – C3H8_Roc_Crit Hydrogen Hyd_Lev_Warn Hyd_Roc_day ppm/day...
  • Page 66 Page intentionally left blank...

  • Page 67: C Iec 61850

    — A p p e n d i x C IEC 61850 The CoreSense M10 implements an IEC 61850 MMS server over TCP/IP Ethernet that is compliant with edition 1 of the IEC 61850 standard. pixiT protocol implementation extra information for Testing...

  • Page 68: Pixit For Server Model

    Description Value/Clarification What is the maximum start up time after a power supply 5 minutes interrupt does this device function only as test equipment? (test equipment need not have a non-volatile configuration; but it cannot be part of the substation automation system) PIXIT for Server Model Description Value/Clarification...

  • Page 69: Pixit For Data Set Model

    Description Value/Clarification Validity: Which status value (ST) quality bits are supported (can be set by server) Good invalid Reserved Questionable Overflow BadReference Oscillatory Failure Olddata inconsistent inaccurate Source: process Substituted Test OperatorBlocked What is the maximum number of data object references in one deprecated GetdataValues request What is the maximum number of data object references in one...

  • Page 70: Pixit For Setting Group Control Model

    PIXIT for Setting Group Control Model Description Value/Clarification What is the number of supported setting groups for each logical device SG is not supported. What is the effect of when and how the non-volatile storage is updated SG is not supported. (compare ieC 61850-8-1 $16.2.4) Can multiple clients edit the same setting group SG is not supported.

  • Page 71: Pixit For Logging Model

    Description Value/Clarification Rp11 does the device support to preassign a RCB to a SCL is not used as a configurable item in this specific client in the SCL device. Rp12 After restart of the server is the value of ConfRev Restored from original configuration restored from the original configuration or retained prior to restart...

  • Page 72: Pixit For Goose Subscribe Model

    PIXIT for GOOSE Subscribe Model Description Value/Clarification What elements of a subscribed GOOSe header are destination MAC address checked to decide the message is valid and the alldata Appid values are accepted? if yes, describe the conditions. gocbRef notes: timeAllowedtoLive •...

  • Page 73: Pixit For Goose Performance

    PIXIT for GOOSE Performance Description Value/Clarification performance class GOOSe not supported. GOOSe ping-pong processing method GOOSe not supported. Application logic scan cycle (ms) GOOSe not supported. Maximum number of data attributes in GOOSe GOOSe not supported. dataset (value and quality has to be counted as separate attributes) PIXIT for Control Model Description...
  • Page 74 Description Value/Clarification Which additional cause diagnosis are supported Unknown not-supported Blocked-by-switching-hierarchy Select-failed invalid-position position-reached parameter-change-in-execution Step-limit Blocked-by-Mode Blocked-by-process Blocked-by-interlocking Blocked-by-synchrocheck Command-already-in-execution Blocked-by-health 1-of-n-control Abortion-by-cancel Time-limit-over Abortion-by-trip Object-not-selected edition 2 specific values: Object-already-selected no-access-authority ended-with-overshoot Abortion-due-to-deviation Abortion-by-communication-loss Blocked-by-command none inconsistent-parameters Locked-by-other-client Ct10 How to force a “test-not-ok”...
  • Page 75 Description Value/Clarification Ct13 Which origin categories are supported bay-control station-control remote-control automatic-bay automatic-station automatic-remote maintenance process Ct14 What happens if the orCat value is not supported or dOns invalid SBOns dOes SBOes Ct15 does the ied accept a SelectWithValue / Operate with dOns the same control value as the current status value SBOns...

  • Page 76: Pixit For Time Synchronization Model

    Description Value/Clarification Ct26 does the ied support control objects with external dOns signals SBOns dOes SBOes Ct27 does the ied support dpC control objects with dOns external signals SBOns dOes SBOes PIXIT for Time Synchronization Model Description Value/Clarification What time quality bits are supported (may be set by the ied) LeapSecondsKnown ClockFailure ClocknotSynchronized...

  • Page 77: Pixit For File Transfer Model

    PIXIT for File Transfer Model Description Value/Clarification What is structure of files and directories File transfer not supported. Where are the COMTRAde files stored Are comtrade files zipped and what files are included in each zip file directory names are separated from the file name by File transfer not supported.

  • Page 78: Mics

    MICS Logical Nodes List The following table contains the list of logical nodes implemented in the device: L: System Logical Nodes LPHD (physical device information) LLN0 (logical node zero) G: Logical Nodes for Generic References GGIO (generic process I/O) S: Logical Nodes for Sensors and Monitoring SIML (insulation medium supervision [liquid]) SIML–Insulation medium supervision (liquid) The IEC 61850-7-4 ed.1 SIML node was extended with data objects defined in technical report...
  • Page 79 SIML DO Name Explanation M/O/C/E C2H4 Measurement of ethylene (in ppm) C2H4ROC ethylene rate of change (RoC in ppm/day) C2H6 Measurement of ethane (in ppm) C2H6ROC ethane rate of change (RoC in ppm/day) C3H6 Measurement of propene (in ppm) C3H6ROC propene rate of change (RoC in ppm/day) C3H8 Measurement of propane (in ppm)
  • Page 80 SIML DO Name Explanation M/O/C/E C2H4ROCWrn ethylene rate of change warning C2H6Alm ethane alarm C2H6ROCAlm ethane rate of change alarm C2H6Wrn ethane warning C2H6ROCWrn ethane rate of change warning C3H6Alm propene alarm C3H6ROCAlm propene rate of change alarm C3H6Wrn propene warning C3H6ROCWrn propene rate of change warning C3H8Alm...
  • Page 81 SIML DO Name Explanation M/O/C/E C2H2ROCAlmSpt Acetylene rate of change alarm set point C2H2WrnSpt Acetylene warning set point C2H2ROCWrnSpt Acetylene rate of change warning set point C2H4AlmSpt ethylene alarm set point C2H4ROCAlmSpt ethylene rate of change alarm set point C2H4WrnSpt ethylene warning set point C2H4ROCWrnSpt ethylene rate of change warning set point...

  • Page 82: Pics

    PICS ACSI Basic Conformance Statement The basic conformance statement is defined in the following table. Client/ Server/ Value/ Subscriber Publisher Comments Client-Server Roles Server side (of TWO-pARTY-AppLiCATiOn-ASSOCiATiOn) Client side of (TWO-pARTY-AppLiCATiOn-ASSOCiATiOn) SCSMs Supported SCSM: ieC 61850-8-1 used SCSM: ieC 61850-9-1 used deprecated SCSM: ieC 61850-9-2 used SCSM: other...
  • Page 83 Client/ Subscriber Server/ Publisher Value/ Comments Reporting Buffered report control M7.1 sequence-number M7.2 report-time-stamp M7.3 reason-for-inclusion M7.4 data-set-name M7.5 data-reference M7.6 buffer-overflow M7.7 entryid M7.8 BufTm M7.9 intgpd M7.10 M7.11 conf-revision Unbuffered report control M8.1 sequence-number M8.2 report-time-stamp M8.3 reason-for-inclusion M8.4 data-set-name M8.5...

  • Page 84: Acsi Service Conformance Test

    Client/ Subscriber Server/ Publisher Value/ Comments If SVC (B41/42) is supported Multicast SVC Unicast SVC For all ieds Time Time source with required accuracy shall be available. Only Time Master are SnTp (Mode 4 response) time server. All other Client / Server devices require SnTp (Mode 3 request) clients Y = service is supported n or empty = service is not supported...
  • Page 85 Services AA: TP/MC Client (C) Server (S) Comments Substitution SetdataValues Setting Group Control SelectActiveSG SelecteditSG SetSGValues ConfirmeditSGValues GetSGValues GetSGCBValues Reporting Buffered Report Control Block (BRCB) Report S24-1 data-change (dchg) S24-2 quality-change (qchg) S24-3 data-update (dupd) GetBRCBValues SetBRCBValues Unbuffered Report Control Block (URCB) Report S27-1 data-change (dchg)
  • Page 86 Services AA: TP/MC Client (C) Server (S) Comments GSSE SendGSSeMessage deprecated in edition 2 GSSE-CONTROL-BLOCK GetReference deprecated in edition 2 GetGSSeelementnumber deprecated in edition 2 GetGsCBValues deprecated in edition 2 SetGsCBValues deprecated in edition 2 Transmission of Sampled Value Model (SVC) Multicast SVC SendMSVMessage Multicast Sampled Value Control Block...

  • Page 87: Tics Mandatory Intop Tissues

    Services AA: TP/MC Client (C) Server (S) Comments Time accuracy Unspecified TL (ms) (low accuracy), T3 < 7) of internal clock (only ed2) T0 (ms) (<= 10 ms), 7 <= T3 < 9 T1 (µs) (<= 1 ms), 10 <= T3 < 13 T2 (µs) (<= 100 µs), 13 <= T3 <...
  • Page 88 Part TISSUE No. Description Impl. Y/NA control parameter T Typo Typo in syntax Typo Syntax Control time Syntax parameter dSet-Ref missing Syntax GOOSe “T” type Add dstAddr to GoCB GOOSe Message “Appid” to “Goid” GsCB “Appid” to “Gsid” SV timestamp: “entryTime” to “TimeStamp” Control “T”...

  • Page 89: D Advanced Maintenance

    Advanced maintenance NOTICE The Maintenance page must only be used by an ABB Level 2 accredited personnel or under the direct supervision of an ABB Level 2 accredited personnel. Unsupervised or unauthorized use of the Maintenance page could permanently damage the CoreSense M10 system, and even the power transformer that it monitors.

  • Page 90: Gathering Diagnostic Data

    Gathering diagnostic data Depending on the problem to solve, you might need to gather data about specific subsystems such as the various sensors and boards. In most of these data pages, you can refresh the displayed data by clicking the Refresh button located at the bottom of the page.

  • Page 91: Ftir Data

    FTIR data To gather FTIR diagnostics data from the Maintenance page, click Sensors diagnostics>FTIR. A table appears indicating various parameters and values. — Figure 58 FTIR diagnostics data Advanced maintenance D87...

  • Page 92: Hydrogen Sensor Data

    Hydrogen sensor data To gather hydrogen sensor data from the Maintenance page, click Sensors diagnostics>Hydrogen sensor diagnostics. A table appears indicating various sensor parameters and values. — Figure 59 Hydrogen sensor diagnostics data D88 User Guide...

  • Page 93: Moisture Sensor Data

    Moisture sensor data To gather moisture sensor data from the Maintenance page, click Sensors diagnostics>Moisture sensor diagnostics. A table appears indicating various sensor parameters and values. — Figure 60 Moisture sensor diagnostics data 4–20 inputs To gather diagnostics data for the 4–20 mA inputs from the Maintenance page, click I/O diagnostics>Inputs 4-20mA.

  • Page 94: Pump Data

    Pump data To gather diagnostics data for the system pumps from the Maintenance page, click Pumps diagnostics. A table appears in the top part of the page indicating various parameters and values. — Figure 62 Pumps diagnostics page NOTICE Use of the bottom part of this page is destined to testing system pumps. Pump testing is explained in more details on "Working on pumps"...

  • Page 95: Source Data

    Source data To gather diagnostics data for the system source from the Maintenance page, click Source diagnostics. A table appears in the top part of the page indicating various parameters and values. — Figure 63 Pumps diagnostics page NOTICE Use of the bottom part of this page is destined to testing and resetting various source parameters.

  • Page 96: Temperature Data

    Temperature data To gather temperature data for diagnostic purposes, click Temperature diagnostics from the Maintenance page. A table appears indicating various temperature parameters and values. — Figure 64 Temperature diagnostics data D92 User Guide...

  • Page 97: Toggling Relays

    3 Click Apply. The state of the physical relays is modified to match the state given on the page. NOTICE The CoreSense M10 is designed to counteract undue external influences (e.g., electromagnetic interferences) by resetting relays to a preferred state every 30 seconds.

  • Page 98: Modifying 4-20 Ma Output Values

    3 Click Apply. The current outputs are modified as indicated. NOTICE The CoreSense M10 is designed to counteract undue external influences by resetting current outputs to a preferred state every 30 seconds. If your testing of the current outputs exceeds 30 seconds, click Refresh to obtain the latest relay states before continuing on.

  • Page 99: Working On Pumps

    Working on pumps When troubleshooting a CoreSense M10 system, you might have to perform tasks on the different pumps (resetting pump state, activating/deactivating a pump, etc.). The following pages explain how to perform these tasks. Activating a pump Sometimes, when performing maintenance or troubleshooting tasks, you need to activate or deactivate pumps over the course of a maintenance or troubleshooting session.

  • Page 100: Resetting The State Of All Pumps

    Enabling auto-refresh The CoreSense M10 is designed so that the user has to click the Refresh button to obtain the system's latest operating state. However, when it comes to pump diagnostics and troubleshooting, a user will often need both hands while optimizing pump and connection behavior.

  • Page 101: Diagnosing System Sources

    Diagnosing system sources When diagnosing CoreSense M10 problems, system sources could be at fault. From the Maintenance page, there are certain actions that you can perform to achieve a diagnostic. — Figure 68 The Source diagnostics page Changing the active source There are two sources in a CoreSense M10 system.

  • Page 102: Resetting Source Odometers

    Resetting source odometers While the CoreSense M10 is in operation, persistent files are created for each source, describing certain parameters and source states. These files are designed to remain in the instrument. However, there are times when you need to erase those files (e.g., after replacing a source).

  • Page 103: Backing Up The Current Configuration

    A backup of your configuration file is saved at the location of your choice. Restoring a configuration After performing any major maintenance operation on a CoreSense M10 system, you should be able to restore a previously created backup your current system configuration if you need to.

  • Page 104: Toggling Validation Of The Golden Reference Spectrum

    Toggling validation of the golden reference spectrum There are times when you will need to change the validation status of the golden spectrum reference. To do so: 1 Click FGS misc from the Maintenance page. The FGS misc page appears (see Figure 70 below). —...
  • Page 105 — A p p e n d i x e Alternate fluids validation Mineral Oil (IEEE Std C57.104-2019) — Table 2 Default dissolved gas concentration limits for Mineral Oil (µL/L [ppm]) Warning threshold Alarm threshold Default state Moisture (H₂O) enabled Hydrogen (H₂) enabled Methane (CH₄)
  • Page 106 Natural Ester (IEEE Std C57.155-2014) — Table 4 Default dissolved gas concentration limits for Natural Ester (µL/L [ppm]) Warning threshold Alarm threshold Default state Moisture (H₂O) enabled Hydrogen (H₂) enabled Methane (CH₄) enabled Acetylene (C₂H₂) enabled Ethylene (C₂H₄) enabled Ethane (C₂H₆) enabled Carbon monoxide (CO) enabled...
  • Page 108 We reserve the right to make technical changes or modify the contents of this document without prior notice. With regard to purchase orders, the agreed particulars shall prevail. ABB does not accept any responsibility whatsoever for potential errors or possible lack of information in this document.

Table of Contents