shared ionet user guide - ge• a new value-added system (such as model-predictive control) can be...

GEH-6812J

Mark* ControllersShared IONet User GuideAug 2019

Public Information

These instructions do not purport to cover all details or variations in equipment, nor to provide for every possiblecontingency to be met during installation, operation, and maintenance. The information is supplied for informationalpurposes only, and GE makes no warranty as to the accuracy of the information included herein. Changes, modifications,and/or improvements to equipment and specifications are made periodically and these changes may or may not be reflectedherein. It is understood that GE may make changes, modifications, or improvements to the equipment referenced herein or tothe document itself at any time. This document is intended for trained personnel familiar with the GE products referencedherein.

GE may have patents or pending patent applications covering subject matter in this document. The furnishing of thisdocument does not provide any license whatsoever to any of these patents.

Public Information – This document contains non-sensitive information approved for public disclosure.

GE provides the following document and the information included therein as is and without warranty of any kind,expressed or implied, including but not limited to any implied statutory warranty of merchantability or fitness forparticular purpose.

For further assistance or technical information, contact the nearest GE Sales or Service Office, or an authorized GE SalesRepresentative.

Revised: Aug 2019Issued: Nov 2012

© 2012 – 2019 General Electric Company.___________________________________* Indicates a trademark of General Electric Company and/or its subsidiaries.All other trademarks are the property of their respective owners.

We would appreciate your feedback about our documentation.Please send comments or suggestions to [email protected]

Public Information

mailto:[email protected]

Document UpdatesRevision Location Description

J

Staged System EvaluationNew section providing procedures to monitor counters in a stagedsystem

Shared IONet Overview

Various updates for clarification and consistencyController to Controller CommunicationsOverviewRules

H Shared IONet OverviewRemoved reference to specific controller in listing of allowedcontroller combinations used for Shared IONet

G RestrictionsRemoved PUAA Universal Analog I/O Module from the list of I/Omodules that have restrictions for use in a Shared IONet Group.PUAA can be used in a Shared IONet Group with no restrictions.

Acronyms and AbbreviationsBPCS Basic Process Control SystemCMS Configuration Management SystemDHCP Dynamic Host Configuration ProtocolSCADA Supervisory Control and Data AcquisitionTMR Triple Modular RedundantUDH Unit Data Highway

GEH-6812J User Guide 3Public Information

Contents1 Overview............................................................................................................................................. 51.1 Shared IONet Overview............................................................................................................................51.2 Controller to Controller Communication Overview ........................................................................................7

2 Rules and Restrictions.................................................................................................................... 92.1 Rules.....................................................................................................................................................92.2 Restrictions .......................................................................................................................................... 10

3 Shared IONet Configuration ........................................................................................................ 113.1 System-level Shared IONet Groups ........................................................................................................... 123.1.1 Insert New Shared IONet Group ........................................................................................................ 123.1.2 Delete or Remove Shared IONet Group............................................................................................... 14

3.2 Component Level Configuration............................................................................................................... 153.2.1 Network Addresses ......................................................................................................................... 153.2.2 Owned and Shared I/O Modules ........................................................................................................ 173.2.3 Shared Inputs ................................................................................................................................. 183.2.4 Connect Variables ........................................................................................................................... 213.2.5 Modify Shared IONet Control Sets ..................................................................................................... 23

3.3 Download Shared IONet ......................................................................................................................... 24

4 Controller to Controller Configuration...................................................................................... 294.1 Controller to Controller Configuration Rules............................................................................................... 304.2 Send and Receive Points ......................................................................................................................... 314.2.1 Show or Hide Unconnected Variables ................................................................................................. 334.2.2 Point Health ................................................................................................................................... 34

5 Advanced Configuration .............................................................................................................. 355.1 Configuration Management System (CMS)................................................................................................. 355.2 Multiple Frame Rates ............................................................................................................................ 375.3 Time Synchronization............................................................................................................................. 385.4 Shared IONet Group Replication .............................................................................................................. 39

6 Troubleshooting ............................................................................................................................. 416.1 Controller Diagnostic Alarms................................................................................................................... 416.2 Build Validation .................................................................................................................................... 426.2.1 Controller Version Not Supported....................................................................................................... 426.2.2 Conflicting IONet IPAddresses ......................................................................................................... 426.2.3 NTP Servers Must Be All Enabled or All Disabled ................................................................................ 436.2.4 Mismatched NTP Servers ................................................................................................................. 436.2.5 Conflicting IONet Bar Codes (Host Name) .......................................................................................... 436.2.6 I/O Module Not Supported................................................................................................................ 446.2.7 Controller and Network Redundancy .................................................................................................. 446.2.8 Controller to Controller Warnings ...................................................................................................... 45

6.3 Download Validation.............................................................................................................................. 456.4 Staged System Evaluation ....................................................................................................................... 46

Glossary of Terms ................................................................................................................................ 49

4 GEH-6812J GEH-6812 Mark Controllers Shared IONetPublic Information

1 OverviewThis document discusses the Shared IONet feature and the Controller to Controller (C2C) communication feature, includingfeature overview, rules and restrictions, configuration, and troubleshooting.

1.1 Shared IONet OverviewBeginning with ControlST* V04.06, sharing data between two controller sets on a single Ethernet input/output network(Shared IONet) is available for some Mark* controllers. Beginning with ControlST V07.06, some Shared IONet Groups maycontain up to four controller sets (in accordance with supported controller combinations). With Shared IONet, an ownercontroller configures its owned I/O modules, Writes outputs, Reads Sequence of Events (SOE), and provides diagnosticinformation. Owned I/O modules are attached to the owner controller that can configure and Write outputs to them, and theyobtain IP addresses from their owner controller. Only the owner controller can Write outputs for an I/O module it owns.

Note A controller set is a group of controllers (based on redundancy) with a set of owned I/O modules. In the ToolboxST*System Editor Summary View, a controller set displays as a single controller.

A shared I/O module sends field device inputs to both its owner controller and to all consumer controllers. A consumercontroller receives the field device inputs from the shared I/O modules that are owned by the other owner controller. TheToolboxST application is used to configure the controller sets. The computer with ToolboxST communicates with the I/Odevices through a software gateway function residing in the controllers.

Only the following controller combinations are supported by Shared IONet:

• One Mark VIeS Safety controller and up to three Mark VIe controllers• One MarkStat controller and one Mark VIe controller• Up to four Mark VIe controllers

Note The UCPA controller platform should not be used in a Shared IONet system.

In a Shared IONet Group with Mark VIe controllers and/or a MarkStat controller, any controller can receive the other's inputsand send outputs to the I/O pack it owns.

In a Shared IONet Group containing Mark VIe controllers and one Mark VIeS Safety controller, the Mark VIeS Safety I/Omodule inputs can be shared between both controllers. However, the safety controller only receives inputs from its ownedsafety-certified I/O modules.

Shared IONet provides the following benefits:

• When a safety control system is required, the non-safety controller in the Shared IONet Group can use the sensorsattached to the safety control system with normal latency. This simplifies designs and saves the cost of multiple sensors.

• Elimination of I/O network switches saves cabinet space and component cost.• A small controller set can add additional controllers without having to create a new network infrastructure.• A new value-added system (such as model-predictive control) can be added to a controller set with direct access to the

IONet. This reduces the latency of the process information (inputs) and the programming required to view the processinformation (inputs) in the new value-added controller set.

Overview GEH-6812J User Guide 5Public Information

R S T R S T

Safety Inputs

Field devices for functional safety loop

Mark VIeS controller set owns the safety I/O modules (for SIL rating, configuration, and diagnostic reporting).

Safety I/O modulesBasic process I/O modules

Mark VIe controller set receives the inputs from safety I/O modules (data from safety loop field devices).

One TMR redundant IONet

Shared IONet Example


1.2 Controller to Controller Communication Overview

Note C2C communication is not supported for the Mark VIeS Safety controller.

The Controller to Controller (C2C) feature uses Shared IONet to provide communication between a MarkStat PowerConversion controller and a Mark VIe general-purpose controller. Up to four general-purpose Mark VIe controllers can alsouse this feature. The controllers must reside within a shared IONet Group.

Caution

Critical system signals between controllers must be through hard-wired I/O and notthrough Controller to Controller IONet.

Note For MarkStat controller hardware, contact a GE sales or service office or an authorized GE sales representative.

C2C communication provides the following benefits:

• Uses the Shared IONet feature with same reduced hardware footprint• Separate from the Wind Supervisory Control and Data Acquisition (SCADA) or Unit Data Highway (UDH) network• Signal scoping is not a problem• Uses the same dedicated IONet as I/O packs• Uses same redundancy scheme as IONet

Overview GEH-6812J User Guide 7Public Information

Notes


2 Rules and Restrictions2.1 RulesMultiple controller sets can share a common set of I/O network hardware. All controller sets can receive and interpret inputsfrom shared I/O devices. The following rules apply to the Shared IONet and C2C features:

• A maximum of 50 I/O modules can be attached to the Mark VIeS Safety controller.• A maximum of 200 I/O modules can exist within a Shared IONet Group.

Note The maximum number of I/O modules (PAIC equivalents) varies depending on controller processor type, cabling,switch, complexity of application code, and frame rates. These maximums are not enforced by ToolboxST.

• Only the following controller combinations are allowed:− One Mark VIeS Safety controller and up to three Mark VIe controllers− One MarkStat controller and one Mark VIe controller− Up to four Mark VIe controllers

• The fastest frame rate allowed for the Mark VIeS Safety controller is 40 ms.• Controllers must have the same network redundancy: Simplex, Dual, or Triple Modular Redundant (TMR).• Controller sets can have the following redundancies: Simplex/Simplex, Dual/Dual, TMR/TMR, and Simplex/TMR.• Configuration for a given I/O device is accomplished only by that device’s owning controller.• Outputs for a given I/O device are only driven by the owning controller.• If a Shared I/O point is Forced in a given controller, only that controller identifies the Forced value; no other consuming

controller in the Shared IONet Group will acknowledge the Forced value.• If a Controller to Controller point is Forced, all controllers in the Shared IONet Group that consume that Page will

acknowledge the Forced value.• Dynamic Host Configuration Protocol (DHCP), diagnostics, and Auto-Reconfiguration for a given I/O device can only

be managed and serviced by the owning controller.• Within a mixed Mark VIe and Mark VIeS Shared IONet Group, the Mark VIe controller can use inputs from the

safety-certified I/O devices, but the Mark VIeS controller can only consume its own safety-certified I/O devices.• All I/O modules must be firmware version V04.06 or later, which requires a firmware upgrade for existing I/O modules.• Controllers must be firmware version V04.06 or later.• Mark VIe I/O modules must support multi-cast addressing for use in a Shared IONet Group. Refer to the section

Restrictions for a list of unsupported I/O modules.

Caution

Use only GE-approved Ethernet switches in all control system I/O networks.Unsupported switches can prevent I/O modules from receiving controller outputs.

Rules and Restrictions GEH-6812J User Guide 9Public Information

2.2 RestrictionsThe following table lists the I/O modules that have restrictions for use in a Shared IONet Group. None of these I/O modulescan share their inputs, but some can coexist on a Shared IONet. All other distributed I/O modules (not listed) do not haverestrictions.

I/O Module Restrictions for Shared IONet

Module Description Can Exist in Shared IONetGroup

PAMBAcoustic Monitoring InputUpgrade to PAMC for Shared IONet No

Does not support multi-castSECA Solar Inverter Interface

WECA Wind DFIGe Converter Interface

PFFA FOUNDATION FieldbusTM linking device No

UCPA A compact form of Mark VIe controller with integral I/O NoPPRF PROFIBUS® Communication

Yes, but cannot share inputs

WCBM Wind Condition Top Box Monitor InterfaceWEMA Power Conversion Main ControlWETA Wind Energy Top Box ControlWEPA 1.6 100m and 2.x Wind Pitch ControlAEPA 1.5 MWWind Pitch ControlPCNO CANopen® Master GatewayPSCA Serial CommunicationPSCH Specialized Serial Communication

PMVE Mark V Migration Control

PMVP Mark V Migration Protection

PMVD Mark V Migration Digital Input/OutputPCMI Mark VI VME I/O Board Interface to the Mark VIe controller


3 Shared IONet ConfigurationFrom the ToolboxST System Editor Tree View, new controllers can be inserted into Shared IONet Groups. An existingcontroller can also be dragged and dropped into Shared IONet Groups from the Tree View, but an IP address may need to bechanged. Refer to the section Network Addresses.

Tip � After any change is made in either the System or Component Editors, a Save command must be performed. AllComponent Editors must be closed before performing a Download Shared IONet command from the System Editor.

Each individual controller and shared set of I/O modules are configured from within Component Editors. Networkconfiguration is also completed from each controller’s Component Editor, as well as the assignment of owned and shared I/Omodules. After component configuration, application downloads to devices in Shared IONet Groups should be completedfrom the System Editor rather than from each individual Component Editor.

Note Individual controller downloads can be completed from Component Editors, but additional issues may arise (forexample controllers out of sync, I/O unhealthy) that would require a download of the other Shared IONet controller.

Shared IONet Configuration GEH-6812J User Guide 11Public Information

3.1 System-level Shared IONet Groups

3.1.1 Insert New Shared IONet Group➢➢ To add a Shared IONet Group

1. Open a ToolboxST system *.tcw file to display the System Editor.

2. Create a Shared IONet Group.

From the System Editor Tree View , right click the system and selectInsert New and SharedIONet

From the New Shared IONet Group dialog box, enter a name and a description (optional) and click OK .

3. If inserting a new controller, from the Tree View, right-click the Shared IONet Group and select Insert New,Controller, and Mark [VIe, VIeS, or Stat] Controller.

a. Complete the Creation Wizard pages to add the controller.

b. If inserting a new second controller, repeat these steps.


4. If adding an existing controller, from the Tree View, drag the controller into the Shared IONet Group. If theMustRebuild/Download message displays, click OK.

a. If the controller is not at least version 4.06, perform an upgrade.

b. If there are I/O modules that are not at least version 4.06 firmware, perform an upgrade.

c. If adding a second controller to the Shared IONet Group that already exists on the system, repeat step 4 a and b.

5. Save the system.

Shared controller display in the Summary View

6. Double-click each controller to open both Component Editors.

7. From each Component Editor, add and configure the I/O modules.


3.1.2 Delete or Remove Shared IONet Group➢➢ To remove a shared IONet Group

1. From the System Editor Tree View, expand the Shared IONet Group and either:

a. Drag the controllers from inside to outside the group.

Or

b. Delete the controllers from inside the group.

2. Select and delete the group folder.

3. Restart the WorkstationST* OPC DA server to refresh the I/O diagnostics as displayed from the system-level controller.If the server is not restarted, active diagnostics may not display from the system level.

When attempting to delete the Shared IONet Group without first removing the controllers, the following message displays.


3.2 Component Level ConfigurationDiagnostics and configuration of I/O modules can only be performed from within the owning controller’s Component Editor.After making changes from within a Component Editor, a Save command should be performed to update the system file andthe other Component Editors. Before performing system-level downloads, both Component Editors must be closed to preventany further modifications to components prior to group downloading. However, component level downloads can beperformed as usual, but without disagreement checks between shared control sets.

Caution

If changes are made from the Component Editor (not the System Editor), devicessharing signals will also need to be built and downloaded. If using the DownloadShared IONet function from the System Editor, this check is already performed.

3.2.1 Network Addresses

Note To use Shared IONet, the Mark VIeS Safety controller must always be 1, 2, 3 for R, S, T IONet IP address third octet.

New controllers added to a new Shared IONet Group should not require changes to their network addresses. However,because network addresses must not overlap with each other, a controller dragged into a group may need networkconfiguration. The Mark VIe controller’s IONet 1, 2, and 3 (R, S, T) are set by default as 4, 5, and 6 in the third octet. TheMark VIeS Safety controller’s third octet defaults are 1, 2, and 3. Even if not used currently, it is a best practice to reserve the1, 2, and 3 third octet addresses for a possible future safety controller.

Topography (using subnets) – Simplex Controllers, TMR IONets


➢➢ To view controller IP addresses

1. From the Component Editor General tab Tree View, select the Network Adapter for IONet1.

2. From the Property Editor, locate the IP Address of the controller.

In this example, the number 4 in the IP Address third octet is the signi! cant digit that must not overlap any other controller addresse..s

Note that theNetwork Adapter numbering does not necessarily correspond to the IONet number.

If an existing Mark VIe controller was assigned as 1, 2, and 3 in the third octet, and a new Mark VIeS Safety controller wasadded to a Shared IONet Group, the Component InfoView Log tab displays the following errors:

Error 12:56:06 PM Conflicting IoNet IPAddress 192.168.1.8 has (2) conflicts at SILController_003(IoNet1),Controller002_InSIO (IoNet1)



➢➢ To resolve IP address conflicts

Caution

Verify that it is safe to take the controller offline before changing IP addresses.Changing the IONet IP address third octet will force a compress I/O. This causes amajor revision change that requires an offline download of the controller and all I/Omodules.

Note Compressing the I/O eliminates all forces, if any value was forced.

1. Change the third octet of the Mark VIe controller’s IONet IP addresses to 4, 5 and 6 (or to digits that are not currentlybeing used by another controller).

2. Perform Build, Download, and Restart commands of the controller.


3. Manually restart all attached I/O modules so that they receive the new IP address.

3.2.2 Owned and Shared I/O Modules➢➢ To view and add new modules

1. From the Component Editor Hardware tab Tree View, select Distributed I/O to display the owned I/O modules.

2. Add I/O modules to the owning controller by right-clicking Distributed I/O and selecting Add New Module.

Owning controller

Shared controller

3. After I/O modules are added, click Save.

Note Within a Shared IONet Group, if an I/O module is configured as Required, any controller sharing that I/O module’sinputs will also inherit the Required property. Therefore, any I/O module set as Required must maintain communication withboth the owning and sharing controllers.


3.2.3 Shared Inputs➢➢ To add inputs from a shared controller

1. From the System Editor, open the Component Editor of the controller that does not own the I/O module.

2. Add I/O modules for the shared controller.

Right-click the shared controller and select Ad d Shared I/O .

The I/O modules owned by the shared controller display.

Select the I/O modules to share and click OK

3. After adding the first or removing the last shared input, perform a Download then restart the controller.

4. Save the Component Editor.


Caution

Be aware that if a scale or measurement setting is changed on a shared input, it willaffect both the owning and the consuming controller of that input.

The following is an example of a Mark VIe controller with Shared IONet:

These I/O modules are owned by this Mark VIe controller .They can be configured to display diagnostic alarm information.

The Mark VIeS Safety controller is configured from its own Component Editor

This Mark VIe controller receives inputs from these Mark VIeS shared I/O modules


The following is an example of the Mark VIeS Safety controller with Shared IONet:

Shared I/O modules, which are highlighted in blue, display_Shared

The Mark VIe controller is configured from its own Component Editor. Its I/O cannot be shared to the Mark VIeS Safety controller


3.2.4 Connect VariablesInputs can be connected from shared I/O modules. Shared I/O modules display Variables, Inputs, and Shared I/O Status Theydo not display Diagnostics or Parameters. The Shared I/O Status tab displays EGD status and diagnostics information only.

The Variables tab displays a limited set of data to allow variable connections. The Data Grid contains only the followingread-only columns:

• Name• Direction• Data Type• Device Tag• Description

The Connected Variable column can be modified.

➢➢ To connect variables

From the Hardwaretab Tree View, select the shared I/O module

From the Data Grid, select a variable, then from the Connected Variable column, click the ellipsis button to display the Select a Variable dialog box


It is recommended to add a prefix to the Variable Name to identify the owning controller. Click OK

Caution

Be aware that if a scale or measurement setting is changed on a shared input, it willaffect both the owning and the consuming controller of that input.


3.2.5 Modify Shared IONet Control SetsWhen a controller set is changed, all consuming control sets must be rebuilt. It is then recommended for users to download toall controllers and modules in a Shared IONet Group. This download is not required, but is highly recommended after therebuild scan completes.

The following actions require a restart of the controller:

• Compressed variables• Remapping the I/O to application code prior to startup• Changing the IONet third octet IP address• Adding the first shared I/O module• Removing the last shared I/O module• Adding the first I/O modules to the owning controller• Removal of all I/O modules from the owning controller

Caution


➢➢ To remove shared inputs: Right-click the input and select Remove.

The inputs of the selected I/O module are no longer shared with the other controller. The I/O module remains attached to itsowning controller.

Note Removing shared I/O does not delete the I/O module. I/O modules are deleted from their owning controller'sComponent Editor. A shared controller cannot be deleted from an owning controller’s Component Editor. Controllers aredeleted from within the System Editor.


3.3 Download Shared IONet

Note If dual controller downloads are performed from the System Editor, the Revert function is not available.

The configuration should be downloaded as a unit, unless there are valid reasons not to download a particular component. Notdownloading a component flagged as Download Needed could result in unpredictable operation. Builds and downloads can beperformed from the individual Component Editors.

Caution


➢➢ To build and download the Shared IONet configuration

1. Verify that the Component Editors are saved and closed.

2. If using a Mark VIeS Safety controller, verify that it is unlocked.

3. Download the Shared IONet Group configuration using the Download Wizard.

From the System Editor Systemmenu, select Download Shared IONet to display the Download Shared IONet wizard


Controllers within the group cannot be cleared. Select the group to scan and click Next .

All available I/O is scanned to determine the necessary downloads. A controller status check is performed to determine if anyshared IONet controllers need to be built.


4. If a controller(s) need to be built, the following dialog box displays.If all controllers have already been built, the following dialog box will not display. Skip to step 6 of this procedure tocontinue the download.

Note For further assistance, refer to the section Build Validation.

Do not uncheck any controller

Click OK . The Building Controllers status message displays

5. If an APP_STATE block is not included in the application code of a controller, the following message displays. Select thecontrollers to download if they are in a safe state, and click OK.


6. A download scan report is generated. Click Yes to view the report.

7. The Download Shared IONet dialog box identifies all mismatched (unequal) downloadable items. Because errors canoccur, do not clear these items unless there is a valid reason to do so.

Note Awarning message may display before the Controller Download Status dialog box displays.

8. Click Next to start the download.

When the download is complete, verify that the controllers are in the Controlling state and check the Component InfoViewLog tab for warnings and messages.


Notes


4 Controller to ControllerConfiguration

Attention

For Controller to Controller (C2C) communication, Shared IONet must first be addedand configured. Refer to the procedures in the chapter Shared IONet Configuration.

The following is an example of a typical wind converter system configured with C2C communications.

Wind Power Conversion Example

Controller to Controller Configuration GEH-6812J User Guide 29Public Information

The following figure displays two Mark VIe controllers with a Simplex IONet configured with C2C communications.

Two General-purpose Mark VIe Controllers

4.1 Controller to Controller Configuration RulesConfiguration rules are as follows:

• After the first variable connection (outputs or inputs), a download to the I/O modules and a restart of the controller set isrequired.

• A Build warning will occur if a variable was defined on the connection of an input that is not connected to the output ofthe owning controller.

• If a variable is removed on an output, and then downloaded to the consuming controller, and the consuming controllervariable is removed but not built and downloaded, the variable will become unhealthy on the consuming controller.


4.2 Send and Receive PointsThe owning (output) controller point page must be configured to send variables to the consuming (input) controller pointpage. Each product-based output (local) controller defines a set of points using the following data types: BOOL, DINT,UDINT and REAL. The maximum allowable number of points for each data type are as follows:

• 288 Boolean variables• 30 Signed double integer variables• 120 Real variables• 20 Unsigned double integer variables

➢➢ To configure controllers to send and receive points

1. From the Hardware tab Tree View of the owning controller, select Distributed I/O and the Outputs tab.

2. Notice the Name column. This is the signal name that is used as both the output from the owning controller and as theinput to the consuming controller.

3. If needed, define any Connected Variables from the owning controller to be used within application logic of the owningcontroller only. Connected Variables are not shared to the consuming controller.

4. If necessary, edit the Device Tag and Description columns.

Note The Description field is only editable from the owning controller and shared to the consuming controller. The Devicetag is not copied to the consuming controller.


5. From the Hardware tab Tree View of the consuming controller, select the owning controller icon and the Inputs tab.

6. Notice the Name column. This is the signal name that is used as both the output from the owning controller and as theinput to the consuming controller.

7. Define the Connected Variables to be used within application logic of the consuming controller. Connected Variablesnames are not shared to the consuming controller from the owning controller.

8. If the following message displays, click OK and continue adding connected variables on the Input tab. The controller willreboot after the download.

9. Save the controllers, close the Component Editors, and from the System Editor, perform a Download SharedIONet.


4.2.1 Show or Hide Unconnected VariablesInput or output controller points that are not connected by a variable can be hidden from view.

The Hide/Show advanced columns or rows button hides all unconnected points but does not reduce the size of the communication exchange page.

If all points are unconnected, the button displays gray.


4.2.2 Point HealthPoint health is dependent on a connected point on the output. If a connected variable is removed from an output and only thecontroller producing the output is downloaded, the point will become unhealthy on the Controller to Controller consumingcontroller.

Producing Controller

Consuming Controller


5 Advanced Configuration5.1 Configuration Management System (CMS)If the ToolboxST application is under CMS control, all components in the Shared IONet Group must be checked out todownload. All normal CMS features apply to the individual components.

This controller must be checked out before performing a Download

Advanced Configuration GEH-6812J User Guide 35Public Information

If the controller is not checked out, the following message displays when download is attempted.


5.2 Multiple Frame RatesThe two control sets within a Shared IONet Group are allowed to have different frame rates. For example, the Mark VIecontroller runs at 10 ms and the Mark VIeS Safety controller runs at 40 ms. However, within a controller set, the redundantcontrollers and I/O modules must run at the same frame rate. Data exchanged between shared control sets have a vote rate asrequired by the difference in controller set frame rates. Incoming data is processed at the consuming controller frame rate.

When the consuming controller’s frame rate is slower than the producing controller, the incoming data intermediate to theconsuming controller frame rate is rejected. When the consuming controller’s frame rate is faster than the producingcontroller, the data is consumed at each frame. The timeout for unhealthy data is based on the producing controller’s framerate.

Caution

To avoid potential communication failures, verify that the sample rate is adequate forthe control loops in which the data is being used. Particular care must be observedwhen using down-sampled data where control loop stability is dependent on datasample rates.

Pay close attention when data is sampled at different frame rates. For example, sharing 40 ms frame rate data from a MarkVIeS Safety control may not provide the necessary bandwidth for a 10 ms Mark VIe control system application. Data andvalues will be repeated multiple times before the producer changes its value.


5.3 Time SynchronizationTime synchronization operates the same for Shared IONet components as it does for standard IONet components.Configuration tips are as follows:

• If using the override time synchronization settings for a component, all controllers in a Shared IONet Group must match.• When a Mark VIeS Safety controller is used, viewing the Set Time from the Mark VIe controller is not allowed because

the safety controller is the grand master.• If using two Mark VIe controllers and attempting to set time to one of the controllers, there is not a definitive way to

know which is the grand master. In this case, the following message displays if the controller is not the grand master. Usethe Set Time from the other controller.


5.4 Shared IONet Group ReplicationIt is possible to replicate the Shared IONet Group and its devices using the System Editor. The replication wizard supportstwo types of replication:

• Simple Replicate creates the new Shared Group name, group devices, and their IP addresses automatically, assigned inlinear order from a base value.

• Replicate using Properties from CSV creates the Shared Group name, group devices name, and IP addresses as defined ina Comma Separated Value (.csv) file. Since Shared IONet Group name, name of the components, and IP address of eachcan be specified, this option is more flexible than Simple Replicate.

If there is a validation error for any of the devices under a Shared IONet Group, the group cannot be replicated. A successfulbuild to the devices must be performed to remove a validation error. The replication wizard removes any trailing numericvalues from the Shared IONet Group name as well as from the shared devices within the group. The group name would be setas Base Shared IONet Group Name in the replication settings page.

The replication wizard settings page allows for starting position number and number of copies. Starting position number issuffixed with the new group name: Base Shared IONet Group Name + Starting position. The same starting position number isused for the devices in the Shared IONet Group. If the group or device already exists with that name, the wizard status isflagged red for that group or name. A different starting number must be provided by the user.


Notes


6 TroubleshootingTo assist with troubleshooting, it is recommended to configure the WorkstationST Recorder and Alarm Viewer to collect datafrom both panels in the Shared IONet Group. This allows the trip logs and alarm logs to have synchronized alarms and tags.Refer to the following documents for setup and configuration:

• WorkstationST Alarm Viewer Instruction Guide (GEI-100620)• WorkstationST Recorder (GEI-100627)• ControlST Software Suite How-to Guides (GEH-6808) (if available), the chapter How to Configure and Troubleshoot a

Trip Log Using the WorkstationST Application

6.1 Controller Diagnostic AlarmsIf a shared I/O module loses communication or inputs are unhealthy, an alarm message is generated by the owning controller.Depending on which IONet the unhealthy I/O module resides on, one of the following alarms for R, S, or T displays. Refer tothe Mark VIe and Mark VIeS Control Systems, Volume II: General-purpose Applications (GEH-6721_Vol_II) for moreinformation on controller alarms 505, 506, and 507.

From the System Editor, select the alarm, and click F1 to display Help for that alarm

Troubleshooting GEH-6812J User Guide 41Public Information

6.2 Build ValidationBuilds can be performed from within each Component Editor. Perform downloads from the System Editor if possible toprevent out-of-sync problems (refer to the section Download Shared IONet). During initial configuration, it is best practice tofirst upgrade the Mark VIeS Safety controller, and verify the default 1, 2, 3 third octet (refer to the section NetworkAddresses). The following are common build validation errors with resolution.

Tip � If using a Mark VIeS Safety controller, it is a recommended practice to first unlock, Build, and Download the safetycontroller, and then re-lock and re-brand. This saves time in subsequent Downloads of the Mark VIe controller because itskips the scan of the Mark VIeS Safety controller.

6.2.1 Controller Version Not SupportedThe following example error message displays when the configured controller's version does not have the Shared IONetfeature. This is because the IONet EGD ProducerIDs have been scaled (based on the controller set index) to ensureuniqueness across all controllers that are physically attached to the IONet.

Error 3:50:50 PM The controller v44Controller does not support multiple controllers on a shared IO network.

To fix this error, complete the recommended upgrade (at a minimum, V04.06) or remove the unsupported controller from theShared IONet Group.

Note Error messages display in the Log tab.

6.2.2 Conflicting IONet IPAddressesThe following example error message displays when the configured controller set's IONet IPAddresses are not unique acrossall the controllers in this Shared IONet Group. It occurs if a previously operating controller is dragged into the group or if thecontroller is created by using the Insert Existing option.

Error 3:54:55 PMConflicting IoNet IPAddress 192.168.1.8 has (2) conflicts at v46Controller(IoNet1).SIL_G5(IoNet1)



To fix this error, change the conflicting controller set's IONet IPAddresses in the third octet.

Note Changing the controller's IONet IPAddress will cause a compress and require a controller restart. (Refer to the sectionNetwork Addresses).


6.2.3 NTP Servers Must Be All Enabled or All DisabledThe following example error message displays when the configured controller's NTP Servers are either not all enabled or notall disabled. This error occurs if a previously operating controller is dragged into a Shared IONet Group or if the controller iscreated using the Insert Existing option. Because of this, the NTP Server has been overridden from the system setting on theimported controller.

Error 3:56:54 PM On a sharedIO network, if any controller has NTP enables, all must be enabled.

To fix this error, from the System Editor, configure all controllers to use the NTP Server. Do not use the NTP override on eachindividual controller.

6.2.4 Mismatched NTP ServersThe following example error message displays when the configured controller's NTP Servers are all enabled, but do not havematching NTP Server IPAddresses. It occurs if a previously operating controller is dragged into a Shared IONet Group or ifthe controller is created by using the Insert Existing option. Because of this, the NTP Server has been overridden from thesystem setting on the imported controller.

Error 3:58:18 PMThe sharedIO Net devices have mismatched NTP Servers configured (if NTP is enabled, allmust match)

To fix this error, from the System Editor, configure all controllers to use the NTP Server. Do not use the NTP override on eachindividual controller.

6.2.5 Conflicting IONet Bar Codes (Host Name)The following example error message displays when the configured controller's bar code (host name) is duplicated on adifferent controller in this Shared IONet Group. It occurs if a bar code is copied and pasted from an existing controller intothe controller being configured. It also occurs when existing controllers that are PMVE, PAMC, or any other UCSA-basedLanModule with location codes not unique are moved into a Shared IONet Group.

Error 4:06:05 PMConflicting IoNet HostName TBAIH1C-JR1–0000001 has conflicts at v46controller(PAIC-277

Error 4:06:05 PMConflicting IoNet HostName TBAIH1C-JS1–0000001 has conflicts at v46controller(PAIC-277

Error 4:06:05 PMConflicting IoNet HostName TBAIH1C-JT1–0000001 has conflicts at v46controller(PAIC-277

To fix this error, enter a unique bar code for each I/O module in the group.


6.2.6 I/O Module Not SupportedThe following example error message displays when attached I/O modules do not support the Shared IONet feature. It occursif a previously operating controller is dragged into the Shared IONet Group or if the controller is created by using the InsertExisting option. Because of this, the controller is still consuming older revisions of I/O modules.

Error 4:13:07 PMController V46Controller cannot be in a Shared IONet Group because I/O module PAMB-22does not support Shared IONet

Error 4:13:07 PMController V46Controller cannot be in a Shared IONet Group because I/O module PFFA-22does not support Shared IONet

Error 4:13:07 PMController V46Controller cannot be in a Shared IONet Group because I/O module SECA-22does not support Shared IONet

Error 4:13:07 PMController V46Controller cannot be in a Shared IONet Group because I/O moduleWECA-22 does not support Shared IONet

To fix this error, upgrade the I/O modules to a supported version (at least version 4.06) or remove any unsupported I/Omodules.

Note For more information, refer to the section Restrictions.

6.2.7 Controller and Network RedundancyThe following example error message displays when either the controller or network redundancies have conflicts. It occurs ifonly one controller is modified to be dual redundant. If so, all controllers and the network redundancy must be dual.

Error 4:23:53 PMConflicting Controller Redundancies on this sharedIO Network (If any controller is dual,ALL must be dual)

Error 4:23:53 PMConflicting IoNet Network Redundancies on this sharedIO Network (All NetworkRedundancies must match)

Error 4:23:53 PM LanModule PAIC-21: PackT (JT1) must have an IoNet connection.

Error 4:23:53 PMLanModule PAIC-21: PackT (JT1) must be connected to IoNets 1 & 2 for dual networkredundancy.

To fix this error, either modify all controllers and network redundancy to be dual or remove all dual redundancies.

Note For more information, refer to the section Rules.


6.2.8 Controller to Controller WarningsThe following three Build warnings are specific to the Controller to Controller (C2C) feature.

Warning 4:09:16 PMThe local C2C output point DistributedIO.G1-264.Bool001 on this controller G1 is drivenwith no other controllers consuming

When a connected variable is added to a C2C output point, that output is said to be driven by the owning controller. Unlessthere is another controller in this same Shared IONet Group that is consuming that I/O point (C2C input) by having aconnected variable on that second controller, a warning will be issued so the user knows that the other controller in the SharedIONet Group should be edited to add this connected variable to its C2C inputs from the first controller.

Warning 4:09:16 PMThe local input point Bool_001 on this controller G1 is not being driven by C2C Outputs oncontroller G2-Test

Whenever a C2C input I/O point has a connected variable, a Build warning indicates that this C2C input is not being drivenby the other controller unless the user adds a connected variable to the C2C outputs of the other controller.

Warning 4:23:33 PMThis controller is in a Shared IONet Group. The controller 'NeverOpenedCtrlr' in theShared IONet Group 'C2C_001' must be opened and saved at least once in order to builda complete system. For example: inputs on this controller may go unhealthy.

Upon first adding a new controller to a Shared IONet Group, the new controller needs to be opened and saved so the existingfiles for the controller will have the updated Shared IONet information. Without this step, the existing controllers will not beable to read the new controller's Shared IONet information.

6.3 Download ValidationIf, while performing a Download Shared IONet function from the System Editor, the error message Unable to verity the typeof I/O pack (pack name) because it is already in program mode displays in the Log, one of the following actions must betaken to complete the Download.

• Restart the LAN module.• Perform the Download from the Component Editor since that allows I/O packs in program mode to receive a Download.


6.4 Staged System EvaluationWhen a system configuration is close to exceeding the set maximum thresholds (refer to the section Rules for maximumguidelines), GE suggests the user create a staged system for evaluation and monitor the following counters from the AdvancedDiagnostics Commands window:

• Verify that the Executing llm seq/fc command counters are equal to 0:− egd Sweeper OvrCount− egd Sweeper ReOvrCount

• Verify that the Executing llm egd/io/ei command counters are equal to 0:− MissCnt− LateCnt− DupCnt

➢➢ To reset and monitor command counters

1. Open the Component Editor and go online with the controller.

2. From the View menu, select Diagnostics, then select Controller Advanced Diagnostics to display the AdvancedDiagnostics Commands window.

3. From the Tree View, expand Commands , expand Diagnostics, then expand Counter Reset.

4. Select Diagnostic Counter Reset and click Send Command to reset the counters.

5. From the Tree View, select Various Advanced Info and click Send Command to display the counters.

6. From the Summary View, locate the Executing llm seq/fc command egd Sweeper and verify that the OvrCountand ReOvrCount counters are 0, as displayed in the figure Executing llm seq/fc Command Counter Values at 0.

7. Locate the Executing llm egd/io/ei command and verify that theMissCnt, LateCnt, and DupCnt counters are 0, asdisplayed in the figure Executing llm egd/io/ei Command Counter Values at 0.


Executing llm seq/fc Command Counter Values at 0


Executing llm egd/io/ei Command Counter Values at 0


Glossary of Terms

BPCS Basic Process Control System that includes a Mark VIe or MarkStat controller set, but not a Mark VIeS Safetycontrol.

Broadcast Network traffic that is simultaneously addressed to all devices on IONet. This type of addressing is used inlegacy control applications.

Consumer Controller The controller receiving the inputs from the shared I/O modules that are owned by the other ownercontroller.

Controller Set The group of controllers (based on redundancy) with the set of owned I/O modules. From the SystemEditor Summary View, a controller set displays as a single controller.

Multi-cast The delivery of a message or information to a group of destination IONet devices simultaneously in a singletransmission from the source. Mark VIe controllers use multi-cast addressing to send outputs to I/O modules unless legacyhardware requires otherwise.

Owner Controller The controller that allows for the configuration of the owned I/O modules, writes outputs, reads SOEs,and provides diagnostic information.

Owned I/O Modules Modules attached to their owner controller that can configure and write to them.

Shared I/O Module An I/O module with inputs to its owner controller that are also sent to the consuming controller

Shared Controller Node Each controller’s Component Editor tree view displays both its owned I/O modules and theshared controller node. Inside the shared controller node are displayed the shared I/O modules that are being consumed by thecontroller whose Component Editor is being viewed.

SCADA Supervisory Control and Data Acquisition network provides data access to each wind turbine and theoperations/maintenance building, and remote access through internet.

UDH Unit Data Highway is the communications network traditionally used by controllers to communicate to other systemlevel equipment.

GEH-6812J Glossary of Terms 49Public Information

Notes

50 GEH-6812 Mark Controllers Shared IONetPublic Information

Public Information

shared ionet user guide - ge• a new value-added system (such as model-predictive control) can be...

Documents