There are two Connection types that utilize the CIP protocol. The Ethernet/IP – CIP connection and the Ethernet/IP – CIP Browsable. The former is made for performance and the latter is made for flexibility and is the subject of this article.   The connection is browsable, this means that it will scan for variables on the PLC and display them to the user. This contrasts with non-browsable connection that rely on the user to type in the correct address for each Input and Output.   Setting up the connection   First the connection needs to be created, then it must be configured. This includes settings the PLC type, the Rack Number, Slot number and the IP address of the PLC that the connection needs to communicate with:     Next step is to connect to the PLC. Right click the connection in the Connections window and click Connect:   The connection will request a variable list as soon as it connects with the PLC. Once the connection has the variable list it’s ready to be used. Please note that the variable list will only be available while the connection to the PLC is maintained.   Using the connection   The next step is to use the connection. This can be done by adding a button to the control panel. To do this select a square in the Control panel grid, right click and select a Button from the context menu:   Select the newly created button and expand the Pushed entry in the Properties window. Make sure that the connection ID property is the Browsable CIP Connection that was created earlier:   This will add the variable list. Locate a variable in that is of the BOOL type and check the checkbox. The Pushed Output of the button is now linked to the selected variable. If the button is pressed then the value of the variable in the PLC will be true, otherwise if will be false.   

Prerequisites As a prerequisite for creating an OPC UA connection, an OPC UA server must be configured on your controller and must be started.   For a description of the procedure required for starting the emulation of Schneider Electric controllers from EcoStruxure Machine Expert, refer to the How to Emulate User Guide in the EcoStruxure Machine Expert online help. For information about starting an OPC UA server on a PacDrive LMC controller, refer to the OPC UA Server Configuration in the LMC Device Objects and Parameters part of the EcoStruxure Machine Expert online help. For information about starting an OPC UA server on a Modicon M262 Logic/Motion Controller, refer to the OPC UA Server Configuration in the M262 Logic/Motion Controller - Programming Guide in the EcoStruxure Machine Expert online help.   Creating an OPC UA Connection To create an OPC UA connection, proceed as follows: Step Action 1 In the Connections view, right-click inside the table and run the command OPC UA Client from the contextual menu. Result: A new row is added to the table with Protocol = OPC UA. 2 Select this row and configure the connection in the Properties view. 3 In the Communication section, edit the OPC Server Address parameter to enter the IP address and the port of the controller you want to connect to. Use the following format as an example, using the default port 4840: opc.tcp://127.0.0.0:4840 4 In the Connections view, right-click the row you created for the OPC UA connection and run the Connect command from the contextual menu. 5 Enter the Username and Password in the OPC UA Credentials dialog box. NOTE: If anonymous login is allowed by the OPC UA server, select the check box "Anonymous login" in the "Properties view"  to avoid this dialog box for future logins. Result: The message Untrusted Certificate is displayed. 6 Verify that you are about to connect to the correct URL and you trust the certificate. Click Yes to proceed or No to cancel. Result: After the connection to the controller is established, you can see Status = Connected displayed in the row of the selected connection. The available tags are read from the OPC UA server, as indicated in the Logs view by the messages Started reading tags and Finished reading tags. The controller variables can be selected within Experior 7.   OPC UA-Specific Settings in the Properties View The following settings of the Properties view are specific to OPC UA connections: Parameter Description Communication Auto Re-Connect Select this option to perform automatic reconnection attempts when the OPC UA connection is interrupted. Auto Re-Connect Delay Enter a delay for starting the first reconnection attempt after the connection has been interrupted and between the individual reconnection attempts. Default value: 5000 ms Infinite Re-Connect attempts Select this option for an unlimited number of reconnection attempts. The waiting time between each attempt is defined by the Auto Re-Connect Delay parameter. Auto Re-Connect Max. attempts Enter a maximum number of reconnection attempts. The waiting time between each attempt is defined by the Auto Re-Connect Delay parameter. Default value: 5 Anonymous Login If anonymous login is allowed in the OPC UA server (for details, refer to the description of the Disable anonymous login parameter in the OPC UA Server Configuration in the M262 Logic/Motion Controller - Programming Guide in the EcoStruxure Machine Expert online help) select this check box to avoid entering credentials. Communication Interval Enter the minimum delay (in ms) that must elapse between the OPC UA client data requests sent to the OPC UA server. Default value: 16 ms NOTE: Consider the impact this polling frequency can have on the performance of the OPC UA server when reducing the value. If you transfer a large amount of data using an OPC UA connection, consider increasing the polling frequency to avoid slowing down the performance of the OPC UA server. OPC Server Address Enter the IP address and the port of the controller you want to connect to. Use the following format as an example, using the default port 4840: opc.tcp://127.0.0.0:4840 Use Publish-Subscribe Select this check box to activate the publish/subscribe data exchange between the OPC UA client and server.

The Experior 7 implementation of the RFC1006 protocol is not the full implementation specified in the public RFC1006 protocol specification.   We have focused on creating a simple and reliable communication protocol and the implementation has primarily been developed in order to meet the Siemens SIMATIC PLC requirements.   The RFC1006 protocol is designated ISOonTCP in a Siemens PLC. Note that the protocol specified in this manual is implemented in full by Siemens PLC network card, i.e. no user program necessary to implement this protocol.   Properties Identification Name – Customizable name Id – Customizable Id   Communication Port Number – Port used for communication between Experior and “Device” IP Address – Type in IP address (only available if Mode = Client) Mode – Select “Server” or “Client” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” Auto Connect Delay – Set delay for when the connection will try to reconnect   RFC1006 Remote TSAP – Address of Remote TSAP (Transport Service Access Point) Local TSAP – Address of Local TSAP (Transport Service Access Point) Connection Id – Connection Id used Max TPDU Size – TPDU (Transport Protocol Data Units) maximum size Max TPDU Bytes – TPDU (Transport Protocol Data Units) maximum bytes used Send Connection Request – Activate or Deactivate whether or not a connection request is to be sent Sign Of Life – Activate or Deactivate whether or not Sign Of Life signal is to be used Sign Of Life Interval – Set the time interval between Sign Of Life requests (only Available if Sign Of Life is checked) Sign Of Life Timeout – Set the timeout value (only Available if Sign Of Life is checked)

The 3964R-Protocol is a serial point-to-point protocol for communication between two programmable logic controllers (PLC). Can be set up to use an ethernet connection or a serial (RS-232/RS-422/RS-485).   TCP/IP Properties Identification Name – Customizable name Id – Customizable Id   Communication Port – Port used for communication between EcoStruxure Machine Expert Twin and “Device” Mode – Select “Server” or “Client” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Serial Properties Line Signals DTR – Select if DTR (Data Terminal Ready) is to be used RTS – Select if RTS (Request To Send) is to be used Handshake – Choose from ‘XOnXOff’, ‘RequestToSend’ or ‘RequestToSendXOnXOff’ handshake protocols   Port Settings Port Name – Select the name of the port Baud Rate – Select the baud rate at which to connect Data Bits – Enter the number of data bits to be used Stop Bits – Choose from ‘One’, ‘Two’ or ‘OnePointFive’. Parity – Choose from ‘Odd’, ‘Even’, ‘Mark’ or ‘Space’   Identification Name – Customizable name Id – Customizable Id   Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” Auto Connect Delay – If Auto connect is checked you can set a delay (in miliseconds) after which the connection will attempt a reconnection

STX/ETX is a high level transport protocol used for exchanging messages with exterior systems. The message is sent as a test starting with STX (Start of Text) character and ends with the ETX (End of Text) character. Can be set up to use ethernet (TCP/IP) or a serial (RS-232/RS-422/RS-485) connection.   TCP/IP Properties Identification Name – Customizable name Id – Customizable Id   Communication Port – Port used for communication between Experior and “Device” Mode – Select “Server” or “Client” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Serial Properties Line Signals DTR – Select if DTR (Data Terminal Ready) is to be used RTS – Select if RTS (Request To Send) is to be used Handshake – Choose from ‘XOnXOff’, ‘RequestToSend’ or ‘RequestToSendXOnXOff’ handshake protocols   Port Settings Port Name – Select the name of the port Baud Rate – Select the baud rate at which to connect Data Bits – Enter the number of data bits to be used Stop Bits – Choose from ‘One’, ‘Two’ or ‘OnePointFive’. Parity – Choose from ‘Odd’, ‘Even’, ‘Mark’ or ‘Space’   Identification Name – Customizable name Id – Customizable Id   Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” Auto Connect Delay – If Auto connect is checked you can set a delay (in miliseconds) after which the connection will attempt a reconnection

Connect to a PLC using a serial (RS-232/RS-422/RS-485) connection.   Properties Line Signals DTR – Select if DTR (Data Terminal Ready) is to be used RTS – Select if RTS (Request To Send) is to be used Handshake – Choose between ‘XOnXOff’, ‘RequestToSend’ or ‘RequestToSendXOnXOff’ handshake protocols   Port Settings Port Name – Select the name of the port – ‘COM1’ as an example Baud Rate – The baud rate at which to connect Data Bits – Enter the number of data bits to be used Stop Bits – Choose from ‘One’, ‘Two’ or ‘OnePointFive’ Parity – Choose from ‘Odd’, ‘Even’, ‘Mark’ or ‘Space’   Identification Id – Customizable Id Name – Customizable name   Timeout Frame timeout – To mark the end of a message, the serial raw connection waits for a timeout. You can set the time for when the timeout triggers an end of message but the default is after 0.1 seconds   Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Memory Allocation (PLC Input) Automatic – Activate or Deactivate automatic memory allocation Length – Enter data length (only available if Automatic is unchecked) Offset – Enter memory offset (only available if Automatic is unchecked)   Memory Allocation (PLC Output) Automatic – Activate or Deactivate automatic memory allocation Length – Enter data length (only available if Automatic is unchecked) Offset – Enter memory offset (only available if Automatic is unchecked)

If Allen Bradley or Omron controllers are being used then Ethernet/IP-CIP needs to be selected from the list of protocols.   Properties Identification Id – Customizable Id Name – Customizable name   CPU  Slot Number – Enter the slot number of the PLCs CPU Rack Number – Enter the rack number of the PLCs CPU Type – Controller family: LGX, SLC, PLC5 Max Package Size – How much data you can send pr. package   Size Choose between SINT, INT and DINT   Communication Type in IP address (only available if Mode = Client) Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” Port – Port used for communication between Experior and “Device”   Memory Allocation (PLC Input) Automatic – Activate or Deactivate automatic memory allocation Source Name – Input – static value, can’t be changed (only available if Automatic = False) Length – Set data length (only available if Automatic = False) Offset – Minimum offset (only available if Automatic = False)   Memory Allocation (PLC Output) Automatic – Activate or Deactivate automatic memory allocation Source Name – Output – static value, can’t be changed (only available if Automatic = False) Length – Set data length (only available if Automatic = False) Offset – Minimum offset (only available if Automatic = False)

Fetch/Write is a protocol to communicate with a Siemens PLC. If you are using a Siemens 1200 or 1500 series PLC, you will need to grant Experior full access through TIA.   Properties for Fetch Identification Name – Customizable name Id – Customizable Id   Communication Port – Port used for communication between Experior and “Device” IP Address – Type in IP address (only available if Mode = Client) Mode – Select “Server” or “Client” Source – Choose the data area to be read from. Options are Flag Area(M), Input(I), Output(Q), Data Block(DB), Counter Cells(C) or Timer Cells(T) Update Interval – Measured in milliseconds. Less than 25ms activates fast mode updating Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Memory Allocation Automatic – Activate or Deactivate automatic memory allocation Length – Set data length (only available if Automatic = False) Offset – Set offset for data (only available if Automatic = False) Properties for Write Identification Name – Customizable name Id – Customizable Id   Communication Port – Port used for communication between EcoStruxure Machine Expert Twin and “Device” IP Address – Type in IP address (only available if Mode = Client) Mode – Select “Server” or “Client” Destination – Choose the data area to be written to. Options are Flag Area(M), Input(I), Output(Q), Data Block(DB), Counter Cells(C) or Timer Cells(T) Synchronized – Activate and Deactivate synchronization Auto Connect – Activate or Deactivate whether EcoStruxure Machine Expert Twin should try to automatically connect to the “Device”   Memory Allocation Automatic – Activate or Deactivate automatic memory allocation Length – Set data length (only available if Automatic = False) Offset – Set offset for data (only available if Automatic = False)

The S7 Functions is a protocol to communicate with a Siemens PLC.   Important: The S7-3xx PLCs have a limitation (that cannot be changed) of PDU (Protocol Data Unit) data size 220 bytes. This is the number of bytes that can be read/written in single operation. The most obvious way to overcome this is to add multiple connections if you expect to exceed 220 bytes in length.   In Experior it is possible to allocate more than 220 bytes per connection but data will then be transmitted in fractions of maximum 220 bytes. Allocating 440 bytes on one connection should have same impact on the PLC performance-wise as setting up two connections with 220 bytes allocated on each.   In both cases Experior will make two read/write operations.   But it is very important not to have too many unused bytes allocated: If there are some addresses in Experior that are positioned in the address area between 0 and 100 and the next address area of interest to the emulation is in the address area from 300 to 500 then it is important to split into two connections: one connection operating in the area between 0 and 100 and another connection operating in the area from 300 to 500. Unless there will in the current example be three read/write operations instead of only two.     If the length exceeds 220 bytes there will be a notification on the connection icon:   It is also important to consider the update internal (see the description of the different properties below): If there are signals that has to be transmitted to the PLC as fast as possible, it is advised that these signals are isolated in a separate connection where only inputs are associated with this connection (like encoder and pulse generator signals). In the same way, if there are signals that does not have to be updated that frequently (like buttons and lamps) it is advised to isolate those signals on a separate connection and then set a higher update interval. Then the PLC have more “time” to answer the request from the connections with a smaller update interval.   Properties Identification Name – Customizable name Id – Customizable Id   Address Rack – Number of rack that is being connected to Slot – Number of slot where CPU is located   Communication IP Address – Type in IP address Update Interval – Measured in milliseconds. Less than 10ms activates fast mode updating Auto Connect – Activate or Deactivate whether EcoStruxure Machine Expert Twin should try to automatically connect to the “Device”   Memory Allocation (PLC Input) Automatic – Activate or Deactivate automatic memory allocation Source Name – Input – static value, can’t be changed (only available if Automatic = False) Length – Set data length (only available if Automatic = False) Offset – Minimum offset (only available if Automatic = False)   Memory Allocation (PLC Output) Automatic – Activate or Deactivate automatic memory allocation Source Name – Output – static value, can’t be changed (only available if Automatic = False) Length – Set data length (only available if Automatic = False) Offset – Minimum offset (only available if Automatic = False)   If you are using a Siemens 1200 or 1500 series PLC, you will need to grant Experior 7 full access through TIA.

Experior.Core.Communication.PLC.Input and Experior.Core.Communication.PLC.Output are classes used to communicate with a PLC.   When they are added to an assembly and made available through a property in the Property window then the Experior user will be able to link the Input with an available connection and specify the address or Byte/Bit depending on the Size. By default this is DataSize.BOOL and hence corresponds with one bit.   You can obtain the corresponding connection through the Connection property and get the address/byte/bit through the properties Byte and Bit (in case the Size is not a DataSize.BOOL the starting address can be found in the Byte property and the Bit property will be “None”).   DataSize Size   The Size property returns what type of data is defined to be exchanged using Input/Output. By default this is DataSize.Bool.   Other possible values are: DataSize.BYTE this is a single byte (8bits) DataSize.WORD this is unsigned 16 bits DataSize.INT this is signed 16 bits DataSize.DWORD this is unsigned 32 bits DataSize.DINT this is signed 32 bits DataSize.STRING this is an array of characters DataSize.ARRAY this is an array of bytes DataSize.FLOAT this is a floating point DataSize.REAL this is a floating point DataSize.REAL32 this is a signed 32 bits DataSize.LINT this is a signed 64 bits DataSize.LREAL this is a 64 bit floating point DataSize.LWORD this is unsigned 64 bit DataSize.SINT this is a signed 8 bit   When the Size property is either DataSize.STRING or DataSize.ARRAY then the length of the string/array can be specified in the Length property.   In the example below the creation of different input output objects is illustrated. In addition, the usage of events to react upon receiving of input and sending of a string messages is shown.   using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; using System.Windows.Media; using System.Xml.Serialization; using Experior.Core.Assemblies; using Experior.Core.Communication.PLC; using Experior.Interfaces; [Serializable] [XmlType(TypeName = "Experior.Catalog.ExampleAssemblies.ExampleInputOutputInfo")] public class ExampleInputOutputInfo : AssemblyInfo { // we add our Output and Input objects into the corresponding info object of // the assembly so that is completely saved (serialised) and restored (deserialised) // when saving and loading the model it is in. public Output outputbit; public Output outputdata; public Input inputbit; public Input inputdata; public int maxnumberofcharacters = 12; } public class ExampleInputOutput : Assembly { private ExampleInputOutputInfo info; public ExampleInputOutput(ExampleInputOutputInfo info) : base(info) { if (info.outputbit == null) { //create Output object by default the size is one bit info.outputbit = new Output(); // give it a description info.outputbit.Description = "Block/Unblock"; } //add the output to the environment so that it becomes visible in the Output window Add(info.outputbit); // send the initial value // 0 when NoNC is Normally Open // 1 whent NoNC is Normally Closed info.outputbit.Off(); if (info.outputdata == null) { info.outputdata = new Output(); info.outputdata.Description = "Send Barcode"; } info.outputdata.Size = DataSize.STRING; info.outputdata.Length = MaxNumberOfCharacters; //add the output to the environment so that it becomes visible in the Output window Add(info.outputdata); // create a Input object to receive a signal (usually from the PLC) if (info.inputbit == null) { info.inputbit = new Input(); info.inputbit.Description = "SignalA"; } info.inputbit.On += new Input.OnEvent(inputbit_On); info.inputbit.Off += new Input.OnEvent(inputbit_Off); info.inputbit.OnNoNcChanged += new Register.NoNcChangedEvent(inputbit_NoNcChanged); //add the input to the environment so that it becomes visible in the Input window Add(info.inputbit); // create a Input object to receive a signal (usually from the PLC) if (info.inputdata == null) { info.inputdata = new Input(); info.inputdata.Description = "LoadDestination"; } // we will receive a string of maximum MaxNumberOfCharacters info.inputdata.Size = DataSize.STRING; info.inputdata.Length = MaxNumberOfCharacters; info.inputdata.OnReceived += new Input.ReceivedEvent(inputdata_Received); //add the input to the environment so that it becomes visible in the Input window Add(info.inputdata); } void inputdata_Received(Input sender, object value) { if (value != null) { // because inputdata.Size = DataSize.STRING the value we receive will be a string so we can cast it to a string string data = (string)value; Experior.Core.Environment.Log.Debug.Write("Received " + data); Experior.Core.Environment.Log.Write("Received " + data); } Experior.Core.Environment.Diagnostic.Message("Inputdata was defined at address " + sender.ByteNo); Experior.Core.Environment.Diagnostic.Message("Inputdata has value " + sender.Value); } void inputbit_Off(Input sender) { // this will be called when we received an Off message for the input bit // this is 0 when NO (NormallyOpen) or 1 when NC (Normally Closed) Experior.Core.Environment.Diagnostic.Message("Input " + sender.ToString() + " off value " + sender.Value, System.Windows.Media.Colors.Green, Experior.Core.Environment.DiagnosticAction.STICKY, Experior.Core.Environment.Signs.Warning); } void inputbit_On(Input sender) { // this will be called when we received an Off message for the input bit // this is 0 when NO (NormallyOpen) or 1 when NC (Normally Closed) Experior.Core.Environment.Diagnostic.Message("Input " + sender.ToString() + " on value " + sender.Value, System.Windows.Media.Colors.Green, Experior.Core.Environment.DiagnosticAction.TEMPORARY, Experior.Core.Environment.Signs.Check); // send a message to info.outputdata OutputData.Send("Hello World!"); } void inputbit_NoNcChanged(IRegister sender) { Experior.Core.Environment.Diagnostic.Message("Input " + sender.ToString() + " changing NO/NC value to " + sender.NormallyClose, System.Windows.Media.Colors.Green, Experior.Core.Environment.DiagnosticAction.ALARM, Experior.Core.Environment.Signs.None); Experior.Core.Environment.Diagnostic.Message("Input was defined for byte " + ((Register)sender).ByteNo + " and bit " + sender.BitNo); } public override void Dispose() { if (((ExampleInputOutputInfo)info).inputbit != null) { ((ExampleInputOutputInfo)info).inputbit.On -= new Input.OnEvent(inputbit_On); ((ExampleInputOutputInfo)info).inputbit.Off -= new Input.OnEvent(inputbit_Off); ((ExampleInputOutputInfo)info).inputbit.OnNoNcChanged -= new Register.NoNcChangedEvent(inputbit_NoNcChanged); } if (((ExampleInputOutputInfo)info).inputdata != null) { ((ExampleInputOutputInfo)info).inputdata.OnReceived -= new Input.ReceivedEvent(inputdata_Received); } base.Dispose(); } public Input InputBit { get { return ((ExampleInputOutputInfo)info).inputbit; } set { ((ExampleInputOutputInfo)info).inputbit = value; } } public Input InputData { get { return ((ExampleInputOutputInfo)info).inputdata; } set { ((ExampleInputOutputInfo)info).inputdata = value; } } public Output OutputBit { get { return ((ExampleInputOutputInfo)info).outputbit; } set { ((ExampleInputOutputInfo)info).outputbit = value; } } public Output OutputData { get { return ((ExampleInputOutputInfo)info).outputdata; } set { ((ExampleInputOutputInfo)info).outputdata = value; } } public int MaxNumberOfCharacters { get { return ((ExampleInputOutputInfo)info).maxnumberofcharacters; } set { ((ExampleInputOutputInfo)info).maxnumberofcharacters = value; } } public override string Category { get { return "ExampleInputOutput"; } } public override ImageSource Image { get; } = Common.EmbeddedImageLoader.Get("Cube"); }

There are two different ways to connect to a PLC depending on whether you use a tag based or an address based connection. If you wish to use a tag based connection you have to start by connecting to the PLC in the Connections window. If you want an address based connection you have to wait to connect to the PLC in the connections window until you have chosen the right settings for the object, you wish to connect.    It is possible to connect most assemblies and controls in the model to a PLC, such as connecting a lamp or a sensor. You have to choose which PLC you wish to connect to for each individual input and output, not just for the assembly as a whole.  If you only have one PLC in the connections window, the object will automatically choose this PLC. If you have more than one PLC  you can choose which PLC to connect to in the assembly’s properties window under ‘connection id’. Having the PLCs connected already only works if you want to use a tag based connection on the object. Then, when you have chosen which PLC to connect to, you can see a list of tags in the properties window. Choose the corresponding tag and the object will be connected to the PLC.   If you wish to use an address based connection you have to start by going to the properties window for the object you wish to connect. Here you should find the PLC input or PLC output category and press the toggle arrow on the side of the category:   Now you can go to the Address field and type in the address for your PLC. You can also choose the right source in the source field. Then you can go to the connections window and connect the PLC so the object will begin sending information to your PLC.