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 addressees 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 Transmission Bit/Byte Wise – Limited transmission. Changed inputs are only written bit-wise and byte-wise. This avoids interference with memory in the PLC that is allocated for Outputs (enabling this option can slow down transmission speed drastically) Communication IP Address – Type in IP address 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 (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 full access through TIA.

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.   As part of the basic psychics model example guide, we show how to use the Siemens Fetch and Write protocol  to test the model.   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 Experior 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 synchronisation 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)

If Allen Bradley or Omron controllers are being used then Ethernet/IP-CIP needs to be selected from the list of protocols.   Click through to learn how to communicate with Allen Bradley PLCs through the CIP protocol.   Properties Identification Name – Customizable name Id – Customizable Id Communication CPU Slot Number – Enter the slot number of the PLCs CPU Size – Choose between BOOL, SINT, INT and DINT 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” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”

It is possible to use an OPC server (Data Access) in conjunction with Experior. Select this option if that is the device being used.   As part of the basic psychics model example guide, we show how to use an OPC Server to test the model.   Properties Identification Name – Customizable name Id – Customizable id Communication Host Name – IP address of the device running the server Server – Allows you select the current running OPC Comms Server

This section provides a brief overview of the available Communications Protocols, what they are and how to use and configure them.   To insert a Communications Protocol, right click on the Communications pane and select it from the pop-up context menu.   There are 8 different main communication protocols.   Depending on the supplied Experior license, different low level communication protocols can be set up for use within Experior.   The following 5 protocols are generally used for direct connections to PLCs and allow Experior to use/respond to PLC symbolics, ladder logic code etc.   Siemens (which itself is split down into 2 different protocol types, Fetch & Write – which are generally used together – and S7 Functions) Ethernet/IP – CIP OPC Serial (RAW) Beckhoff ADS   These last 3 protocols are for configuring systems to allow Experior to send and receive system telegrams and messages.   STX/ETX (contains options for configuring Serial and TCP/IP connections) 3964R (contains options for configuring Serial and TCP/IP connections) RFC1006   Auto Connect   Under the Properties for each communications protocol is the option to Auto Connect when the model is loaded.   When set to True the communications protocol will try and automatically connect when the model is loaded.   The Delay property allows the user to define a time for the communications protocol to wait before it tries to automatically connect.  

If you are using a Siemens 1200 or 1500 series PLC, you will need to grant Experior full access through TIA.   Open project in TIA Go to PLC properties Under General tab select Protection Make sure Full Access is selected as shown in the figure Check Permit access with PUT/GET communication from remote partner as shown in the figure below  

Connect to a PLC using a serial (RS-232/RS-422/RS-485) connection.   Properties Identification Name – Customizable name Id – Customizable Id Port Settings Port Name – Select the name of the port, COM1 for example Baud Rate – Select the baud rate at which to connect Parity – Choose from Odd, Even, Mark or Space Data Bits – Enter the number of data bits to be used Stop Bits – Choose from One, Two or OnePointFive 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 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 = False) Offset – Enter memory offset (only available if Automatic = False) Memory Allocation (PLC Output) Automatic – Activate or Deactivate automatic memory allocation Length – Enter data length (only available if Automatic = False) Offset – Enter memory offset (only available if Automatic = False)

Select this protocol if TwinCAT Controllers are being used.   Properties Identification Name – Customizable name Id – Customizable Id Communication Port – Port used for communication between Experior and “Device” IP Address – IP Address of the Beckhoff Controller Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”  

STX/ETX is a high level transport protocol used for exchanging messages with exterior systems. Can be set up to use serial (RS-232/RS-422/RS-485) or an ethernet connection.   TCP/IP Properties   Identification Name – Customizable name Id – Customizable Id Validation MVT – Select the MVT (Message Validation Template) being used for this protocol 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” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Serial Properties Identification Name – Customizable name Id – Customizable Id Port Settings Port Name – Select the name of the port, COM1 for example Baud Rate – Select the baud rate at which to connect Parity – Choose from Odd, Even, Mark or Space Data Bits – Enter the number of data bits to be used Stop Bits – Choose from One, Two or OnePointFive. 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 Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”

The 3964R-Protocol is a serial point-to-point protocol for communication between two programmable logic controllers (PLC). Can be set up to use a serial (RS-232/RS-422/RS-485) or an ethernet connection.   TCP/IP Properties Identification Name – Customizable name Id – Customizable Id Validation MVT – Select the MVT (Message Validation Template) being used for this protocol 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” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”   Serial Properties Identification Name – Customizable name Id – Customizable Id Port Settings Port Name – Select the name of the port, COM1 for example Baud Rate – Select the baud rate at which to connect Parity – Choose from Odd, Even, Mark or Space Data Bits – Enter the number of data bits to be used Stop Bits – Choose from One, Two or OnePointFive 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 Communication Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device”

The Experior implementation of the RFC1006 protocol is not the full implementation specified in the public RFC1006 protocol specification.   Xcelgo has 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 Validation MVT – Select the MVT (Message Validation Template) being used for this protocol 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” Auto Connect – Activate or Deactivate whether Experior should try to automatically connect to the “Device” 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 = True) Sign Of Life Timeout – Set the timeout value (only Available if Sign Of Life = True)