SSCP Protocol Driver 

SSCP (Shark Slave Communication Protocol) is a native communication protocol of mark… process station with Mervis RT. It is used for configuration, programming and data transfer. Mervis IDE in debugging mode, HT102/200 terminal, mobile application Mervis Menu Reader and SCADA RcWare Vision use SSCP communication protocol for connection with process station. It is also used for horizontal communication between process stations.

• All process station with Mervis RT: full support client and server. (all mark…, IMIO10x and ICIO20x controllers)
• IPLC5xx and WIN RT with SoftPLC RT: client support (read and write data from/to Mervis RT).

• Ethernet
• Serial - server only

• The process stations with operating system FreeRTOS (IMIO10x, ICIO20x, mark100, mark150/xxx, mark12x) have maximum number of connected SSCP clients at a time restricted to 5.
• The process stations with operating system Linux (markMX, mark320, mark220) have maximum number of connected SSCP clients at a time restricted to 20.
• It is recommended to leave one unused connection for Mervis IDE because of service access. If it is required to connect more process stations and maximum number of connection seems to be reached, it is recommended to concentrate data to a single process station, or use ring topology. 
• If integration of SSCP protocol into third party control system is required, contact Domat technical support please. It will provide you with the SSCP protocol specification and SDK (Software Developement Kit) for C# or C++.

For SSCP communication it is necessary to know the device address and access information (see below). For reading and writing of particular variable, a CommID, data offset and length are used. These parameters of each variable is exported by the editor (Mervis IDE, HMI, RcWare Vision…)  to the configuration file. Please note that after variable definition change or changes in function blocks, the variable CommID is changed. The new data from the current project (.exs folder) must be imported in the editors (HMI / RcWare Vision).

• SSCP Address - SSCP slave device address, it is preparation for SSCP communication over serial, used also for TCP communication
• Number of Registrable Groups - parameter for number of registrable groups (function is not supported in versions to 2.2.0.X)
• Number of Variables in Group - parameter for number of variables in registrable groups (function is not supported in versions to 2.2.0.X)
• Enable TCP Server - if enabled, the device listens as a SSCP server on the Ethernet interface
• TCP Server Port - TCP port number used for communication
• Enable Serial Server -  if enabled,  the device listens as a SSCP server on the selected serial interface (function is not supported in versions to 2.2.0.X)
• Serial Server Port -  serial port number used for SSCP serial communication (function is not supported in versions to 2.2.0.X)
• Serial Port Baudrate - communication baudrate over the serial interface (function is not supported in versions to 2.2.0.X)
• Enable SSL Server - activation of server for encrypted communication (function is not supported in versions to 2.2.0.X)
• SSL Server Port -  encrypted communication port (function is not supported in versions to 2.2.0.X) 

See also Controller properties

It is possible to set:

• Link protocol - in version to 2.2.0.X only TCP is supported
• Max. Telegram Duration - how long the client is waiting for response
• Pause between telegrams - time without activity between telegrams

Device
In device properties there are communication parameters to connect another PLC:

• Device Address  -  SSCP slave device address, preparation for SSCP communication on serial bus, used also for TCP communication
• Device IP address - slave IP address
• Device Port - TCP port used for communication (default: 12346)
• User Name  - user name for PLC (there are three user levels Engineering - full rights incl. configuration - “admin”, Full Control - read/write - “user”, Read Only  - “readonly”)
• Password - user password (default: rw)

End Point

• HwConfiguration - IP address which is set in Configuration → Networking of a particular PLC
• Deploy - IP address which is set in PLC connection parameters
• Custom - IP address which is set in device properties of this device

Communication group

Creating and editing is done in the device editor. A communication group defines variables which are communicated together. In Mervis IDE versions to 2.2.0.X  maximum 20 variables in one group are supported.  The number of groups is not restricted. It is possible to define groups for reading or writing. There is also possibility to set Write Only On Change and  Read Changes Only. Property Logical OR over Overlapped is used if values from two datapoints have to be merged into one variable. Example: OR, two bool data points, one of value 1 and second of 0. The set value of the variable will be 1.)

In the properties there is also preparation for registrable groups function. (This function is not supported in versions 2.2.0.X or older.)

Data point

Creating and editing is done in the device editor. Principles are the same as for other common device types, see Defining of HW variables for a communication channel.

In versions to 2.2.0.X it is possible to map only variables from another PLC in the Solution.

For more information about communication between PLCs, see Access to variables from another PLC.