# Protocol Specific # Modbus Modbus is a communications protocol originally published by Modicon (now Schneider Electric) in 1979 for use with its programmable logic controllers (PLCs). Simple and robust, it has since become a de facto standard communication protocol, and it is now a commonly available means of connecting industrial electronic devices. [![image-1643017242235.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643017242235.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643017242235.png) ## Info about protocol **Address**: - IP address - every device in Ethernet have physical address (only for Ethernet) - Station address - every slave (client) device have a logical address. - Function - function type - Address - information object address. ### Telegram Structure #### Modbus RTU ##### **Request**
Name Bytes Function
Station 0 Station address
Function 1 Function code
Address Hi 2 Starting address
Address Lo 3
Quantity Hi 4 Quantity
Quantity Lo 5
CRC 6 CRC check
##### **Response**
Name Bytes Function
Station 0 Station address
Function 1 Function code
Bytes 2 Data bytes
Data 3... Data
CRC Depending of data CRC check
#### Modbus RTU/ASCII
**Request**
Name Char Function
Start 0 : 0x3A
Station 1 Station address
Function 2 Function code
Address Hi 3 Starting address
Address Lo 4
Quantity Hi 5 Quantity
Quantity Lo 6
LRC 7 LRC check
End 8 ASCII values of 0x0D & 0x0A
End 9
##### **Response**
Name Char Function
Start 0 : 0x3A
Station 1 Station address
Function 2 Function code
Bytes 3 Data bytes
Data 4... Data
LRC Depending of data LRC check
End Depending of data ASCII values of 0x0D & 0x0A
#### Modbus TCP ##### **Request**
Name Bytes Function
Transaction Identifier 0 For synchronization
Transaction Identifier 1
Protocol Identifier 2 Zero for Modbus/TCP
Protocol Identifier 3
Length 4 Number of remaining bytes in this frame
Length 5
Station 6 Station address
Function 7 Function code
Address Hi 8 Starting address
Address Lo 9
Quantity Hi 10 Quantity
Quantity Lo 11
##### **Response**
Name Bytes Function
Transaction Identifier 0 For synchronization
Transaction Identifier 1
Protocol Identifier 2 Zero for Modbus/TCP
Protocol Identifier 3
Length 4 Number of remaining bytes in this frame
Length 5
Station 6 Station address
Function 7 Function code
Bytes 8 Data bytes
Data 9... Data
### Functions Standard MODBUS functions
Dec Description Direction Support
1 Read Coils Monitor Yes
2 Read Discrete Inputs Monitor Yes
3 Read Holding Registers Monitor Yes
4 Read Input Registers Monitor Yes
5 Write Single Coil Control Yes
6 Write Single Register Control Yes
7 Read Exception Status Monitor No
8 Diagnostic Monitor No
11 Get Com Event Counter Monitor No
12 Get Com Event Log Monitor No
15 Write Multiple Coils Control Yes
16 Write Multiple Registers Control Yes
17 Report Slave ID Monitor No
20 Read File Record Monitor No
21 Write File Record Control No
22 Mask Write Register Control No
23 Read/Write Multiple Registers Both No
24 Read FIFO Queue Monitor No
43 Read Device Identification Monitor No
43 Encapsulated Interface Transport Monitor No
## Settings
#### **MASTER**
[![image-1643022203186.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643022203186.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643022203186.png) *Modbus TCP* *Modbus Serial (ASCII included)*
**Slave address** Address of the device which data is read fromAddress of the device which data is read from
**Scan Rate(ms)** Interval between requests to data Interval between requests to data
##### **SLAVE**
[![image-1643023803538.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643023803538.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643023803538.png) **Address** Select addresses of slaves to simulate Select addresses of slaves to simulate
[![image-1643023849891.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643023849891.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643023849891.png) **Value** Default value which slaves will return from all registers. Default value which slaves will return from all registers.

Default values are overridden by created Tags.

## Functions ### Tags This function allows user to created named points. After points created, user can send it manually or set reply checkbox to automatic reply. - To export Tags to csv file: **Tags -> Export -> Save file dialog appear** - To import Tags from csv file: **Tags -> Import -> Open file dialog appear**[![image-1643024284321.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643024284321.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643024284321.png) #### Creating Tag In Modbus protocol tags are mostly used for Slaves to simulate specific data registers, although they can be used in Master to write data to slave registers or format received data from Slave devices. There are two ways of creating tags: 1\. Add button in the tag menu. [![image-1643024563180.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643024563180.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643024563180.png) 2\. Left mouse button double click value in statistic tab. ##### **Slave** If the simulation mode is **Slave** a modbus tag creation window should look like this and have these parameters. - **Name -** user-friendly tag name. - **Type -** the function to be used. *This means that if The Vinci software gets a request with the 03 function type and there is a tag created with that type and it matches the slave address and data address The Vinci software will respond to the request with the value that is set as the tag value.* - **Slave -** Slave address of tag. - **Address** - Address of slave register. - **Format** - Format to store or read data in. - **Value** - Value of the register. [![image-1643025456556.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643025456556.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643025456556.png) ##### **Master** If the simulation mode is **Master** a modbus tag creation window should look like the one shown below and have these parameters. In this case since this is the **Master** tag creation window it has two additional buttons that give the master the ability to write data to the Slave device. For the selected type he buttons are **Write 5 and Write 15** correlating to the modbus types. In **Master** applications tags are mostly used to format data read from Slaves since data reading from devices is done using **Jobs**.

For types 1 and 2 the buttons will be **Write 5 and Write 15.**

For types 3 and 4 the buttons will be **Write 6 and Write 16**

- **Name -** user-friendly tag name. - **Type -** the type of data. - **Slave -** Slave address of tag. - **Address** - Adress of slave register. - **Format** - Format to store or read data in. - **Value** - Value of the register. [![image-1643026840765.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643026840765.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643026840765.png) ### Jobs Jobs are only available in **Master** simulations. What jobs are meant for is reading data from the Modbus slave device. They can send requests for big chunks of data in a single request. Then the data that slave responds with can be formatted using tags. Job has these parameters: - **Name -** user-friendly job name. - **Station -** Modbus **Slave address** to read data from. - **Function -** the function to be used to read data. - **Address -** slave address to begin reading data from. - **Length** - how many bytes will be read. [![image-1643027572918.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643027572918.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643027572918.png) ### Command Commands are only available in **Master** simulations. Commands are used to send data to **Slave** devices. They serve the same purpose as **Write 5** and **Write 6** buttons in tags. Although, commands will send data to the **Slave address** configured in the **Settings** tab whereas tags will send the data to the **Slave address** configured in the tag configuration. [![image-1643027975682.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643027975682.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643027975682.png)

When using commands make sure to enter the desired Slave Address in the settings tab.

## Setup To setup an Modbus simulation it is fairly straightforward. 1\. Select Modbus and the mode. [![image-1643102234120.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643102234120.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643102234120.png)

There are three different Modbus modes: **Modbus TCP, Modbus Serial RTU, Modbus Serial ASCII.**

2\. Select Serial Port settings according to your device specification. [![image-1643100262054.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643100262054.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643100262054.png) 2.1 If **Modbus TCP** is used then the **IP** address and **Port** will have to be selected. [ ![image-1643102340758.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643102340758.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643102340758.png) 3\. Select settings in the settings tab according to your device, preference and selected mode. [![image-1643102386002.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643102386002.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643102386002.png) 4\. Press the green **START** button and the simulation should start. If everything was done correctly The Vinci software should establish communication with the Modbus device which you can monitor in the console tab. [![image-1643102452860.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643102452860.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643102452860.png) # IEC 60870-5-101 IEC 60870-5-101 is a protocol for power system monitoring and controlling. Mostly used for communication between substations and control centers over radio. [![image-1643028902226.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643028902226.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643028902226.png) ## Info about protocol ### **Telegram Structure** ##### **Teleram format with fixed length** [![image-1643029019486.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643029019486.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643029019486.png) ##### **Telegram format with variable length** [![image-1643029038579.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643029038579.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643029038579.png) - **RES** - Reserved - **PRM** - 1 if master, 0 if slave **PRM** = 1 - **FCB** - alternating bit for successive services per station - **FCV** - (if FCV=1 FCB enabled) **PRM** = 0 - **ACD** - access demand (if ACD=1 there are class 1 data) - **DFC** - data flow control (if DFC=1 further messages may cause data overflow) **ASDU** - Application Service Data Unit
### **Function Code** #### **PRM=1**
**Dec** **Frame type** **Service function** **FCV**
0 SEND/CONFIRM expected Reset of remote link 0
1 SEND/CONFIRM expected Reset of user process 0
2 SEND/CONFIRM expected Reserved -
3 SEND/CONFIRM expected User data 1
4 SEND/REPLY expected User data 0
5 Reserved -
6 Reserved -
7 Reserved -
8 REQUEST for access demand Expected response specifies access demand 0
9 REQUEST/RESPOND expected Request status of link 0
10 REQUEST/RESPOND expected Request user data class 1 1
11 REQUEST/RESPOND expected Request user data class 2 1
12 Reserved -
13 Reserved -
14 Reserved -
15 Reserved -
#### **PRM=0**
**Dec** **Frame type** **Service function**
0 CONFIRM ACK: positive acknowledgment
1 CONFIRM NACK: message not accepted, link busy
2 Reserved
3 Reserved
4 Reserved
5 Reserved
6 Reserved
7 Reserved
8 RESPOND User data
9 RESPOND Requested data not available
10 Reserved
11 RESPOND Status of link
12 Reserved
13 Reserved
14 Reserved
15 Reserved
### **Type identification** Standard IEC 60870-5-101 data types\[1-255\] •\[1-127\] - standard definition •\[128-135\] - reserved for routing of messages •\[136-255\] - for special use
**Dec** **Type** **Description** **Direction** **Support**
**Process information**
1 M\_SP\_NA\_1 Single-point information Monitor Yes
2 M\_SP\_TA\_1 Single-point information with time tag Monitor Yes
3 M\_DP\_NA\_1 Double-point information Monitor Yes
4 M\_DP\_TA\_1 Double-point information with time tag Monitor Yes
5 M\_ST\_NA\_1 Step position information Monitor Yes
6 M\_ST\_TA\_1 Step position information with time tag Monitor Yes
7 M\_BO\_NA\_1 Bit string of 32 bit Monitor Yes
8 M\_BO\_TA\_1 Bit string of 32 bit with time tag Monitor Yes
9 M\_ME\_NA\_1 Measured value, normalized value Monitor Yes
10 M\_ME\_TA\_1 Measured value, normalized value with time tag Monitor Yes
11 M\_ME\_NB\_1 Measured value, scaled value Monitor Yes
12 M\_ME\_TB\_1 Measured value, scaled value wit time tag Monitor Yes
13 M\_ME\_NC\_1 Measured value, short floating point number Monitor Yes
14 M\_ME\_TC\_1 Measured value, short floating point number with time tag Monitor Yes
15 M\_IT\_NA\_1 Integrated totals Monitor Yes
16 M\_IT\_TA\_1 Integrated totals with time tag Monitor Yes
17 M\_EP\_TA\_1 Event of protection equipment with time tag Monitor Yes
18 M\_EP\_TB\_1 Packed start events of protection equipment with time tag Monitor Yes
19 M\_EP\_TC\_1 Packed output circuit information of protection equipment with time tag Monitor Yes
20 M\_PS\_NA\_1 Packed single point information with status change detection Monitor Yes
21 M\_ME\_ND\_1 Measured value, normalized value without quality descriptor Monitor Yes
30 M\_SP\_TB\_1 Single-point information with time tag CP56Time2a Monitor Yes
31 M\_DP\_TB\_1 Double-point information with time tag CP56Time2a Monitor Yes
32 M\_ST\_TB\_1 Step position information with time tag CP56Time2a Monitor Yes
33 M\_BO\_TB\_1 Bit string of 32 bit with time tag CP56Time2a Monitor Yes
34 M\_ME\_TD\_1 Measured value, normalized value with time tag CP56Time2a Monitor Yes
35 M\_ME\_TE\_1 Measured value, scaled value with time tag CP56Time2a Monitor Yes
36 M\_ME\_TF\_1 Measured value, short floating point number with time tag CP56Time2a Monitor Yes
37 M\_IT\_TB\_1 Integrated totals with time tag CP56Time2a Monitor Yes
38 M\_EP\_TD\_1 Event of protection equipment with time tag CP56Time2a Monitor Yes
39 M\_EP\_TE\_1 Packed start events of protection equipment with time tag CP56Time2a Monitor Yes
40 M\_EP\_TF\_1 Packed output circuit information of protection equipment with time tag CP56Time2a Monitor Yes
45 C\_SC\_NA\_1 Single command Control Yes
46 C\_DC\_NA\_1 Double command Control Yes
47 C\_RC\_NA\_1 Regulating step command Control Yes
48 C\_SE\_NA\_1 Set-point Command, normalized value Control Yes
49 C\_SE\_NB\_1 Set-point Command, scaled value Control Yes
50 C\_SE\_NC\_1 Set-point Command, short floating point number Control Yes
51 C\_BO\_NA\_1 Bit string 32 bit command Control Yes
58 C\_SC\_TA\_1 Single command with time tag CP56Time2a Control Yes
59 C\_DC\_TA\_1 Double command with time tag CP56Time2a Control Yes
60 C\_RC\_TA\_1 Regulating step command with time tag CP56Time2a Control Yes
61 C\_SE\_TA\_1 Measured value, normalized value command with time tag CP56Time2a Control Yes
62 C\_SE\_TB\_1 Measured value, scaled value command with time tag CP56Time2a Control Yes
63 C\_SE\_TC\_1 Measured value, short floating point number command with time tag CP56Time2a Control Yes
64 C\_BO\_TA\_1 Bit string of 32 bit command with time tag CP56Time2a Control Yes
**System information**
70 M\_EI\_NA\_1 End of Initialization Monitor Yes
100 C\_IC\_NA\_1 Interrogation command Control Yes
101 C\_CI\_NA\_1 Counter interrogation command Control Yes
102 C\_RD\_NA\_1 Read command Control Yes
103 C\_CS\_NA\_1 Clock synchronization command Control Yes
104 C\_TS\_NA\_1 Test command Control Yes
105 C\_RP\_NA\_1 Reset process command Control Yes
106 C\_CD\_NA\_1 Delay acquisition command Control No
107 C\_TS\_TA\_1 Test command with time tag CP56Time2a Control No
**Parameter**
110 P\_ME\_NA\_1 Parameter of measured values, normalized value Control No
111 P\_ME\_NB\_1 Parameter of measured values, scaled value Control No
112 P\_ME\_NC\_1 Parameter of measured values, short floating point number Control No
113 P\_AC\_NA\_1 Parameter activation Control No
**File transfer**
120 F\_FR\_NA\_1 File ready File transfer No
121 F\_SR\_NA\_1 Section ready File transfer No
122 F\_SC\_NA\_1 Call directory, select file, call file, call section File transfer No
123 F\_LS\_NA\_1 Last section, last segment File transfer No
124 F\_FA\_NA\_1 ACK file, ACK section File transfer No
125 F\_SG\_NA\_1 Segment File transfer No
126 F\_DR\_TA\_1 Directory File transfer No
### **Cause of transmission** Standard IEC 60870-5-101 cause of transmission \[0-63\]
Dec Description
1 Periodic, cyclic
2 Background interrogation
3 Spontaneous
4 Initialized
5 Interrogation or interrogated
6 Activation
7 Confirmation activation
8 Deactivation
9 Confirmation deactivation
10 Termination activation
11 Return information caused by a remote command
12 Return information caused by a local command
13 File transfer
20 Interrogated by general interrogation
21 Interrogated by interrogation group 1
22 Interrogated by interrogation group 2
23 Interrogated by interrogation group 3
24 Interrogated by interrogation group 4
25 Interrogated by interrogation group 5
26 Interrogated by interrogation group 6
27 Interrogated by interrogation group 7
28 Interrogated by interrogation group 8
29 Interrogated by interrogation group 9
30 Interrogated by interrogation group 10
31 Interrogated by interrogation group 11
32 Interrogated by interrogation group 12
33 Interrogated by interrogation group 13
34 Interrogated by interrogation group 14
35 Interrogated by interrogation group 15
36 Interrogated by interrogation group 16
37 Interrogated by counter general interrogation
38 Interrogated by interrogation counter group 1
39 Interrogated by interrogation counter group 2
40 Interrogated by interrogation counter group 3
41 Interrogated by interrogation counter group 4
44 Type Identification unknown
45 Cause unknown
46 ASDU address unknown
47 Information object address unknown
## Settings
**Structure**
[![image-1643030143906.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643030143906.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643030143906.png) **Monitor** **Master** **Slave**
**LINK size in bytes** LINK size in bytes LINK size in bytes LINK size in bytes
**COT size in bytes** COT size in bytes COT size in bytes COT size in bytes
**ASDU size in bytes** ASDU size in bytes ASDU size in bytes ASDU size in bytes
**IOA size in bytes** IOA size in bytes IOA size in bytes IOA size in bytes
Address
[![image-1643030210401.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643030210401.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643030210401.png) **Monitor** **Master** **Slave**
**Link address** Not used Remote device address Own system address
**Timeouts (ms)**
[![image-1643030267851.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643030267851.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643030267851.png) **Monitor** **Master** **Slave**
**Reading data** Waiting data in serial port buffer Waiting data in serial port buffer Waiting data in serial port buffer
**Pause before send** Not used Pause before send data Pause before send data
**Parameters**
[![image-1643030416216.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643030416216.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643030416216.png) **Monitor** **Master** **Slave**
**Send End of ini.** Not used Not used Send end of initialization TI 70 (M\_EI\_NA\_1)
**Auto ack. control commands**Not used Not used Auto acknowledge system commands (TI: 100, 103)
**Auto ack. system commands** Not used Not used Auto acknowledge commands
## System For all system functions user can set custom address: [![image-1643035404803.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643035404803.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643035404803.png) #### General Interrogation This function will send telegram Type-identification = 100 (C\_IC\_NA\_1) [![image-1643035460782.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643035460782.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643035460782.png) **QOI** - qualifier of interrogation \[0...255\] - 20 - Station interrogation - 21 - Interrogation of group 1 - 22 - Interrogation of group 2 - 23 - Interrogation of group 3 - 24 - Interrogation of group 4 - 25 - Interrogation of group 5 - 26 - Interrogation of group 6 - 27 - Interrogation of group 7 - 28 - Interrogation of group 8 - 29 - Interrogation of group 9 - 30 - Interrogation of group 10 - 31 - Interrogation of group 11 - 32 - Interrogation of group 12 - 33 - Interrogation of group 13 - 34 - Interrogation of group 14 - 35 - Interrogation of group 15 - 36 - Interrogation of group 16 #### Counter Interrogation This function will send telegram Type-identification = 101 (C\_CI\_NA\_1) [![image-1643035583657.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643035583657.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643035583657.png) **FRZ** - freeze\[0..3\] - 0 - Station interrogation - 1 - Interrogation of group 1 - 2 - Interrogation of group 2 - 3 - Interrogation of group 3 **RQT** - request\[0..63\] - 1 - Counter group 1 - 2 - Counter group 2 - 3 - Counter group 3 - 4 - Counter group 3 - 5 - General request #### Commands **Read** command will send telegram Type-identification = 102 (C\_RD\_NA\_1) **Test** command will send telegram Type-identification = 104 (C\_TS\_NB\_1) [![image-1643035813048.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643035813048.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643035813048.png) #### Clock synchronization This function will send telegram Type-identification = 103 (C\_CS\_NA\_1) [![image-1643036000740.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643036000740.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643036000740.png) If "PC time" checkbox is checked, then the PC time will be sent. If it's not checked user can set time manually. Time tag status bits: - **IV** - invalid time - **SM** - Summer/Winter - **SB** - Substitute #### Custom Commands This function allows user to send commands to the slave device. [![image-1643036278042.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643036278042.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643036278042.png) ## Tags This function allows user to created named points. After points created user can send it manually or set reply checkbox to automatic reply. - To export Tags to csv file: **Tags -> Export -> Save file dialog appear** - To import Tags from csv file: **Tags -> Import -> Open file dialog appear** There are two ways of creating tags: 1. Create tag button. 2. Double click a signal with the left mouse button in the statistic tab. Main parameters: - **Name** - user-friendly tag name - **Asdu** - Identifier of the device - **Ioa** - Identifier of values from the device. - **Type** - the type of value. Here is an example image of the tag window with the **M\_SP\_TB\_1 (30)** type selected. Each type has different options that can be configured when sending data. For example this type depicted in the picture below can send a value **Off** or **On** and it also is time-tagged. The user in this case can either select a specific time that they have in mind or just mark the PC checkbox and The Vinci software will automatically send the current PC time. As you can see the Value box in this example is greyed out that is because this tag is created on a **master** simulation, and this type doesn't support writing to slave. [![image-1643099817811.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643099817811.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643099817811.png) ## Setup To setup an IEC 60870-5-101 simulation it is fairly straightforward. 1\. Select IEC 60870-5-101 and the mode. [![image-1643100190017.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643100190017.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643100190017.png) 2\. Select Serial Port settings according to your device specification. [![image-1643100262054.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643100262054.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643100262054.png) 3\. Select settings in the settings tab according to your device and preference. [![image-1643100334429.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643100334429.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643100334429.png) 4\. Press the green **START** button and the simulation should start. If everything was done correctly The Vinci software should establish communication with the IEC 60870-5-101 device which you can monitor in the console tab. [![image-1643100408248.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643100408248.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643100408248.png) # IEC 60870-5-103 IEC 60870-5-103 is a protocol for power system monitoring and controlling. Mostly used for communication between protection devices and devices of a control system in a substation (RTU) over fiber optics. [![image-1643031034165.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643031034165.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643031034165.png) ## Info about protocol ### **Telegram Structure** ##### **Teleram format with fixed length** [![image-1643029019486.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643029019486.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643029019486.png) ##### **Telegram format with variable length** [![image-1643031086615.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643031086615.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643031086615.png) - **RES** - Reserved - **PRM** - 1 if master, 0 if slave **PRM** = 1 - **FCB** - alternating bit for successive services per station - **FCV** - (if **FCV**=1 **FCB** enabled) **PRM** = 0 - **ACD** - access demand (if **ACD**=1 there are class 1 data) - **DFC** - data flow control (if **DFC**=1 further messages may cause data overflow) ### **Function Code** #### **PRM=1**
**Dec** **Frame type** **Service function** **FCV**
0 SEND/CONFIRM expected Reset of remote link 0
1 SEND/CONFIRM expected Reset of user process 0
2 SEND/CONFIRM expected Reserved -
3 SEND/CONFIRM expected User data 1
4 SEND/REPLY expected User data 0
5 Reserved -
6 Reserved -
7 Reserved -
8 REQUEST for access demand Expected response specifies access demand 0
9 REQUEST/RESPOND expected Request status of link 0
10 REQUEST/RESPOND expected Request user data class 1 1
11 REQUEST/RESPOND expected Request user data class 2 1
12 Reserved -
13 Reserved -
14 Reserved -
15 Reserved -
#### **PRM=0**
**Dec** **Frame type** **Service function**
0 CONFIRM ACK: positive acknowledgment
1 CONFIRM NACK: message not accepted, link busy
2 Reserved
3 Reserved
4 Reserved
5 Reserved
6 Reserved
7 Reserved
8 RESPOND User data
9 RESPOND NACK: requested data not available
10 Request user data class 1
11 RESPOND Request user data class 2
12 Reserved
13 Reserved
14 Reserved
15 Reserved
### **Type identification** Standard IEC 60870-5-103 data types\[1-255\] - \[1-31\] - standard definition - \[32-255\] - for special use
**Dec** **Description** **Direction** **Support**
1 Time-tagged message Monitor Yes
2 Time-tagged message with relative time Monitor Yes
3 Measurands I Monitor Yes
4 Time-tagged measurands with relative time Monitor Yes
5 Identification Monitor Yes
6 Clock synchronization Both Yes
7 General interrogation Control Yes
8 End of general interrogation Monitor Yes
9 Measurands II Monitor Yes
10 Generic data Both No
11 Generic identification Monitor No
20 General command Control Yes
21 Generic command Control No
23 List of recorded disturbances Monitor No
24 Order for disturbance data transmission Control No
25 Acknowledgment for disturbance data transmission Control No
26 Ready for transmission of disturbance data Monitor No
27 Ready for transmission of a channel Monitor No
28 Ready for transmission of tags Monitor No
29 Transmission of tags Monitor No
30 Transmission of disturbance values Monitor No
31 End of transmission Monitor No
### **Cause of transmission** Standard IEC 60870-5-103 cause of transmission \[0-255\] - \[0\] - not used - \[1-63\] - standard definition - \[64-255\] - for special use
**Dec** **Description**
1 Spontaneous
2 Cyclic
3 Reset frame count bit ( FCB )
4 Reset communication unit ( CU )
5 Start/ restart
6 Power ON
7 Test mode
8 Time synchronization
9 General interrogation
10 End of general interrogation
11 Return information caused by a remote command
12 Return information caused by a local command
20 Command "ACK positive"
21 Command "ACK negative"
31 Transmission disturbance data
40 Generic write command with ACK positive
41 Generic write command with ACK negative
42 Generic read command data valid
43 Generic read command data invalid
44 Generic write conformation
## Settings
**Timeouts (ms)**
[![image-1643031621517.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643031621517.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643031621517.png) **Monitor** **Master** **Slave**
**Reading data** Waiting data in serial port buffer Waiting data in serial port buffer Waiting data in serial port buffer
**Pause before send** Not used Pause before send data Pause before send data
**Address**
[![image-1643031767819.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643031767819.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643031767819.png) **Monitor** **Master** **Slave**
**Link** Not used Remote device address Own system address
**ASDU** Not used Remote device address Own system address
**Commands ack.**
[![image-1643031811132.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643031811132.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643031811132.png) **Monitor** **Master** **Slave**
**Auto ack. system commands** Not used Not used Auto acknowledge system commands
**Auto ack. control commands** Not used Not used Auto acknowledge commands
## System For all system functions user can set custom address: [![image-1643102984838.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643102984838.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643102984838.png) #### General Interrogation This function will send telegram Type-identification = 7 [![image-1643103033727.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643103033727.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643103033727.png) #### Clock synchronization This function will send telegram Type-identification = 103 (C\_CS\_NA\_1) [![image-1643036000740.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643036000740.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643036000740.png) If "PC time" checkbox is checked, then the PC time will be sent. If it's not checked user can set time manually. Time tag status bits: - **IV** - invalid time - **SM** - Summer/Winter - **SB** - Substitute #### General Command This function allows user to send command to slave device. [![image-1643103076282.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643103076282.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643103076282.png) ## Tags This function allows user to created named points. After points created user can send it manually or set reply checkbox to automatic reply. - To export Tags to csv file: **Tags -> Export -> Save file dialog appear** - To import Tags from csv file: **Tags -> Import -> Open file dialog appear** There are two ways of creating tags: 1. Create tag button. 2. Double click a signal with the left mouse button in the statistic tab. Main parameters: - **Name** - user-friendly tag name - **Type** - the type of value. - **Asdu** - Identifier of the device - **Fun -** function number - **Info**- Identifier of values from the device. Here is an example image of the tag window with the **TimeTaggedMessage(1)** type selected. Each type has different options that can be configured when sending data. For example this type depicted in the picture below can send a value **Off** or **On** and it also is time-tagged. The user in this case can either select a specific time that they have in mind or just mark the PC checkbox and The Vinci software will automatically send the current PC time. As you can see the **Value** box in this example is greyed out that is because this tag is created on a **master** simulation, and this type doesn't support writing to slave. [![image-1643104823051.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643104823051.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643104823051.png) ## Setup To setup an IEC 60870-5-103 simulation it is fairly straightforward. 1\. Select IEC 60870-5-103 and the mode. [![image-1643104888959.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643104888959.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643104888959.png) 2\. Select Serial Port settings according to your device specification. [![image-1643100262054.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643100262054.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643100262054.png) 3\. Select settings in the settings tab according to your device and preference. [![image-1643104918264.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643104918264.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643104918264.png) 4\. Press the green **START** button and the simulation should start. If everything was done correctly The Vinci software should establish communication with the IEC 60870-5-103 device which you can monitor in the console tab. [![image-1643104955874.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643104955874.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643104955874.png) # IEC 60870-5-104 IEC 60870-5-104 is a protocol for power system monitoring and controlling. Mostly used to communication between substations and control centers over Ethernet (Fiber optics, 2/3/4G, ...).IEC 60870-5-104 protocol is an extension of IEC 60870-5-101 protocol with the changes in transport, network, link and physical layer services to suit the complete network access. [![image-1643032044811.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643032044811.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643032044811.png) ## Info about protocol ### **Telegram Structure** ##### **Teleram format with fixed length** [![image-1643032078188.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643032078188.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643032078188.png) ##### **Telegram format with variable length** [![image-1643032084988.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643032084988.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643032084988.png) - **APCI** - Application Protocol Control Information (First 6 bytes) - **APDU** - Application Protocol Data Unit (All variable length telegram) - **ASDU** - Application Service Data Unit
### **Type identification** Standard IEC 60870-5-104 data types\[1-255\] - \[1-127\] - standard definition - \[128-135\] - reserved for routing of messages - \[136-255\] - for special use
**Dec** **Type** **Description** **Direction** **Support**
**Process information**
1 M\_SP\_NA\_1 Single-point information Monitor Yes
2 M\_SP\_TA\_1 Single-point information with time tag Monitor Yes
3 M\_DP\_NA\_1 Double-point information Monitor Yes
4 M\_DP\_TA\_1 Double-point information with time tag Monitor Yes
5 M\_ST\_NA\_1 Step position information Monitor Yes
6 M\_ST\_TA\_1 Step position information with time tag Monitor Yes
7 M\_BO\_NA\_1 Bit string of 32 bit Monitor Yes
8 M\_BO\_TA\_1 Bit string of 32 bit with time tag Monitor Yes
9 M\_ME\_NA\_1 Measured value, normalized value Monitor Yes
10 M\_ME\_TA\_1 Measured value, normalized value with time tag Monitor Yes
11 M\_ME\_NB\_1 Measured value, scaled value Monitor Yes
12 M\_ME\_TB\_1 Measured value, scaled value wit time tag Monitor Yes
13 M\_ME\_NC\_1 Measured value, short floating point number Monitor Yes
14 M\_ME\_TC\_1 Measured value, short floating point number with time tag Monitor Yes
15 M\_IT\_NA\_1 Integrated totals Monitor Yes
16 M\_IT\_TA\_1 Integrated totals with time tag Monitor Yes
17 M\_EP\_TA\_1 Event of protection equipment with time tag Monitor Yes
18 M\_EP\_TB\_1 Packed start events of protection equipment with time tag Monitor Yes
19 M\_EP\_TC\_1 Packed output circuit information of protection equipment with time tag Monitor Yes
20 M\_PS\_NA\_1 Packed single point information with status change detection Monitor Yes
21 M\_ME\_ND\_1 Measured value, normalized value without quality descriptor Monitor Yes
30 M\_SP\_TB\_1 Single-point information with time tag CP56Time2a Monitor Yes
31 M\_DP\_TB\_1 Double-point information with time tag CP56Time2a Monitor Yes
32 M\_ST\_TB\_1 Step position information with time tag CP56Time2a Monitor Yes
33 M\_BO\_TB\_1 Bit string of 32 bit with time tag CP56Time2a Monitor Yes
34 M\_ME\_TD\_1 Measured value, normalized value with time tag CP56Time2a Monitor Yes
35 M\_ME\_TE\_1 Measured value, scaled value with time tag CP56Time2a Monitor Yes
36 M\_ME\_TF\_1 Measured value, short floating point number with time tag CP56Time2a Monitor Yes
37 M\_IT\_TB\_1 Integrated totals with time tag CP56Time2a Monitor Yes
38 M\_EP\_TD\_1 Event of protection equipment with time tag CP56Time2a Monitor Yes
39 M\_EP\_TE\_1 Packed start events of protection equipment with time tag CP56Time2a Monitor Yes
40 M\_EP\_TF\_1 Packed output circuit information of protection equipment with time tag CP56Time2a Monitor Yes
45 C\_SC\_NA\_1 Single command Control Yes
46 C\_DC\_NA\_1 Double command Control Yes
47 C\_RC\_NA\_1 Regulating step command Control Yes
48 C\_SE\_NA\_1 Set-point Command, normalized value Control Yes
49 C\_SE\_NB\_1 Set-point Command, scaled value Control Yes
50 C\_SE\_NC\_1 Set-point Command, short floating point number Control Yes
51 C\_BO\_NA\_1 Bit string 32 bit command Control Yes
58 C\_SC\_TA\_1 Single command with time tag CP56Time2a Control Yes
59 C\_DC\_TA\_1 Double command with time tag CP56Time2a Control Yes
60 C\_RC\_TA\_1 Regulating step command with time tag CP56Time2a Control Yes
61 C\_SE\_TA\_1 Measured value, normalized value command with time tag CP56Time2a Control Yes
62 C\_SE\_TB\_1 Measured value, scaled value command with time tag CP56Time2a Control Yes
63 C\_SE\_TC\_1 Measured value, short floating point number command with time tag CP56Time2a Control Yes
64 C\_BO\_TA\_1 Bit string of 32 bit command with time tag CP56Time2a Control Yes
**System information**
70 M\_EI\_NA\_1 End of Initialization Monitor Yes
100 C\_IC\_NA\_1 Interrogation command Control Yes
101 C\_CI\_NA\_1 Counter interrogation command Control Yes
102 C\_RD\_NA\_1 Read command Control Yes
103 C\_CS\_NA\_1 Clock synchronization command Control Yes
104 C\_TS\_NA\_1 Test command Control Yes
105 C\_RP\_NA\_1 Reset process command Control Yes
106 C\_CD\_NA\_1 Delay acquisition command Control No
107 C\_TS\_TA\_1 Test command with time tag CP56Time2a Control No
**Parameter**
110 P\_ME\_NA\_1 Parameter of measured values, normalized value Control No
111 P\_ME\_NB\_1 Parameter of measured values, scaled value Control No
112 P\_ME\_NC\_1 Parameter of measured values, short floating point number Control No
113 P\_AC\_NA\_1 Parameter activation Control No
**File transfer**
120 F\_FR\_NA\_1 File ready File transfer No
121 F\_SR\_NA\_1 Section ready File transfer No
122 F\_SC\_NA\_1 Call directory, select file, call file, call section File transfer No
123 F\_LS\_NA\_1 Last section, last segment File transfer No
124 F\_FA\_NA\_1 ACK file, ACK section File transfer No
125 F\_SG\_NA\_1 Segment File transfer No
126 F\_DR\_TA\_1 Directory File transfer No
127 F\_SC\_NB\_1 Request archive file File transfer No
### **Cause of transmission** Standard IEC 60870-5-101 cause of transmission \[0-63\]
**Dec** **Description**
1 Periodic, cyclic
2 Background interrogation
3 Spontaneous
4 Initialized
5 Interrogation or interrogated
6 Activation
7 Confirmation activation
8 Deactivation
9 Confirmation deactivation
10 Termination activation
11 Return information caused by a remote command
12 Return information caused by a local command
13 File transfer
20 Interrogated by general interrogation
21 Interrogated by interrogation group 1
22 Interrogated by interrogation group 2
23 Interrogated by interrogation group 3
24 Interrogated by interrogation group 4
25 Interrogated by interrogation group 5
26 Interrogated by interrogation group 6
27 Interrogated by interrogation group 7
28 Interrogated by interrogation group 8
29 Interrogated by interrogation group 9
30 Interrogated by interrogation group 10
31 Interrogated by interrogation group 11
32 Interrogated by interrogation group 12
33 Interrogated by interrogation group 13
34 Interrogated by interrogation group 14
35 Interrogated by interrogation group 15
36 Interrogated by interrogation group 16
37 Interrogated by counter general interrogation
38 Interrogated by interrogation counter group 1
39 Interrogated by interrogation counter group 2
40 Interrogated by interrogation counter group 3
41 Interrogated by interrogation counter group 4
44 Type Identification unknown
45 Cause unknown
46 ASDU address unknown
47 Information object address unknown
## Settings
**Structure**
[![image-1643033287784.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643033287784.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643033287784.png) **Master, Slave, Monitor**
**COT size in bytes** COT size in bytes
**ASDU size in bytes** ASDU size in bytes
**IOA size in bytes** IOA size in bytes
**Timeouts (ms)**
[![image-1643033572964.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643033572964.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643033572964.png) **Master** **Slave**
**t0 in seconds** Timeout for the establishment of the connection with the server. Not used
**t1 in seconds** This parameter defines the time in seconds that Master waits maximum for an acknowledge from the slave. This parameter defines the time in seconds that slave waits maximum for an acknowledge from the master.
**t2 in seconds** A S-format frame will be sent at the latest after this time starting from the last received telegram from the slave. A S-format frame will be sent at the latest after this time starting from the last received telegram from the master.
**t3 in seconds** A Test frame will be sent at the latest after this time starting from the last received telegram from the slave. A Test frame will be sent at the latest after this time starting from the last received telegram from the master
**Windows**
[![image-1643033606848.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643033606848.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643033606848.png) **Master** **Slave**
**w size** This parameter indicates the number of received I frames after the S-Frame will be send. This parameter indicates the number of received I frames after the S-Frame will be send
**k size** Maximum I-frames send until acknowledgment. Not used
**SLAVE Parameters**
[![image-1643033659961.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643033659961.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643033659961.png) **Slave**
**Send End of ini. on start up** Send end of initialization TI 70 (M\_EI\_NA\_1)
**Auto ack. U-Frame** Auto ack. U-Frame.
**Auto ack. control commands** Auto acknowledge commands
**Auto ack. system commands** Auto acknowledge system commands (TI: 100, 103)
**MASTER Parameters**
[![image-1643033844026.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643033844026.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643033844026.png) **Master**
**Send Start DT on start up** Send Start DT on startup
**Auto ack. Test Frame** Auto ack. Test frame
## System For all system functions user can set custom address: [![image-1643035404803.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643035404803.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643035404803.png) #### General Interrogation This function will send telegram Type-identification = 100 (C\_IC\_NA\_1) [![image-1643035460782.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643035460782.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643035460782.png) **QOI** - qualifier of interrogation \[0...255\] - 20 - Station interrogation - 21 - Interrogation of group 1 - 22 - Interrogation of group 2 - 23 - Interrogation of group 3 - 24 - Interrogation of group 4 - 25 - Interrogation of group 5 - 26 - Interrogation of group 6 - 27 - Interrogation of group 7 - 28 - Interrogation of group 8 - 29 - Interrogation of group 9 - 30 - Interrogation of group 10 - 31 - Interrogation of group 11 - 32 - Interrogation of group 12 - 33 - Interrogation of group 13 - 34 - Interrogation of group 14 - 35 - Interrogation of group 15 - 36 - Interrogation of group 16 #### Counter Interrogation This function will send telegram Type-identification = 101 (C\_CI\_NA\_1) [![image-1643035583657.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643035583657.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643035583657.png) **FRZ** - freeze\[0..3\] - 0 - Station interrogation - 1 - Interrogation of group 1 - 2 - Interrogation of group 2 - 3 - Interrogation of group 3 **RQT** - request\[0..63\] - 1 - Counter group 1 - 2 - Counter group 2 - 3 - Counter group 3 - 4 - Counter group 3 - 5 - General request #### Commands **Read** command will send telegram Type-identification = 102 (C\_RD\_NA\_1) **Test** command will send telegram Type-identification = 104 (C\_TS\_NB\_1) [![image-1643035813048.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643035813048.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643035813048.png) #### Clock synchronization This function will send telegram Type-identification = 103 (C\_CS\_NA\_1) [![image-1643036000740.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643036000740.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643036000740.png) If "PC time" checkbox is checked, then the PC time will be sent. If it's not checked user can set time manually. Time tag status bits: - **IV** - invalid time - **SM** - Summer/Winter - **SB** - Substitute #### Custom Commands This function allows user to send commands to the slave device. [![image-1643036278042.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643036278042.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643036278042.png) ## Channel With these functions a user has the ability to send any U or S frame telegram. [![image-1643107824514.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643107824514.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643107824514.png) - **Start DT act** - Send *Start Data terminal* activation - **Start DT cnf** - Send *Start Data terminal* confirmation - **Stop DT act** - Send *Stop Data terminal* activation - **Stop DT cnf** - Send *Stop Data terminal* confirmation - **Test Frm act** - Send *Test Frame* activation - **Test Frm cnf -** Send *Test Frame* confirmation [![image-1643107972260.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643107972260.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643107972260.png) **S-Frame ack** - Send S-Frame. User can specify acknowledgment telegram count in text box. ## Tags This function allows user to created named points. After points created user can send it manually or set reply checkbox to automatic reply. - To export Tags to csv file: **Tags -> Export -> Save file dialog appear** - To import Tags from csv file: **Tags -> Import -> Open file dialog appear** There are two ways of creating tags: 1. Create tag button. 2. Double click a signal with the left mouse button in the statistic tab. Main parameters: - **Name** - user-friendly tag name - **Asdu** - Identifier of the device - **Ioa** - Identifier of values from the device. - **Type** - the type of value. Here is an example image of the tag window with the **M\_SP\_TB\_1 (30)** type selected. Each type has different options that can be configured when sending data. For example this type depicted in the picture below can send a value **Off** or **On** and it also is time-tagged. The user in this case can either select a specific time that they have in mind or just mark the PC checkbox and The Vinci software will automatically send the current PC time. As you can see the Value box in this example is greyed out that is because this tag is created on a **master** simulation, and this type doesn't support writing to slave. [![image-1643099817811.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643099817811.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643099817811.png) ## Setup To setup an IEC 60870-5-104 simulation it is fairly straightforward. 1\. Select IEC 60870-5-104 and the mode. [![image-1643108062636.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643108062636.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643108062636.png) 2\. Select Ethernet settings to connect to device. Set the **IP** and the **Port.** (Default port: 2404) [![image-1643108092715.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643108092715.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643108092715.png) 3\. Select settings in the settings tab according to your device and preference. [![image-1643108145112.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643108145112.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643108145112.png) 4\. Press the green **START** button and the simulation should start. If everything was done correctly The Vinci software should establish communication with the IEC 60870-5-104 device which you can monitor in the console tab. [![image-1643108242110.png](https://wiki.elseta.com/uploads/images/gallery/2022-01/scaled-1680-/image-1643108242110.png)](https://wiki.elseta.com/uploads/images/gallery/2022-01/image-1643108242110.png)