The purpose of this article is to provide a step by step directions for the development of the built-in Modbus driver settings in the SCADA system WinCC OA.
Unfortunately, the basic course, this connection is not checked and do not give step by step instructions, so I eliminate this gap.
Step by step instructions for connecting a standard station WinCC OA for Modbus TCP protocol. Use popular simulator Modbus TCP Modbus Tools protocol (www.modbustools.com/download.html)
1. Must be pre-installed 64-bit operating system, or the key demo version Wincc OA (v3.14 or later)
2. Download the link above and install ModbusPollSetup64Bit.exe and ModbusSlaveSetup64Bit.exe. Install these components to simulate data flow (sending-receiving telegrams) on the Modbus TCP protocol
3. First run Modbus Slave (telegram generation) with the settings as shown in the figures, allowing work on the home network (upper tick)
4. Expose the slave on the emulator any number
5. Set up the emulator master in accordance with the pattern. Run Modbus Pool
6. We see ticks telegram counter (TX), we see received and transmitted data. By default, the function is set 03 Holding Register
7. Create a new standard project Wincc OA. By choosing two languages for the interface, giving up a password.
8. Run the created project «TestModbusTCP»
9. We wait until the launch of the Services console
10. Stop the emulation protocol driver (plug) and install a new master Modbus driver
11. Set the initialization string in the Modbus Manager
The console should look like this:
12. Expose the configuration of the project file
[Mod_1]
tcpServerPort = 502
and restart all of our empty project
13. We reaffirm access
The console should look like this
14. Set up the driver as on the picture below and activate, click Apply and Active
15. Try to run the emulator Slave
If you swear that the port is busy – GOOD SIGN
We reserve the idea without action and run Modbus Pool
We see that the telegrams are (changing Tx) moves counter lights turn error, read error, then write. We take into account that until we have created a single tag and no survey was created.
16. Create a new data type, and a new data point. New definition point data type integer (Int)
17. Adding to this variable aleas perefiriynogo address and click on Options
Setting of the Modbus protocol list
18. Choose what we PLC, set the polling period. Important!!! wherever it comes to tick «Active»
19. It is necessary to correctly understand the network, start the exchange process and all should get
Start at the beginning you need to Modbus Slave (telegram receiver), only then the driver WinCC OA. By changing the value in the slave we see that WinCC OA reads / receiving data
Modbus Poll so you can run, for example, to replace the value in the register, but after the main driver WinCC OA
Request type:
1C 00 00 00 00 June 1 03 00 00 00 0A
00 1C – packet identifier.
00 00 – always a value
00 06 – length information of the 6-byte packet
01 – logical address controller / 1 is typically, but … /
03 – register read command
00 00 – with the address 0000
00 0A – just read ten registers (twenty bytes)
type A:
1C 00 00 00 17 00 March 1 14 00 17 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 1C – the identifier of the repeat request
00 00 – always a value
00 17 – length of an information part (twenty-three bytes)
01 – address of PLC / repeat from the request /
03 – function
02 – the number of bytes / registers are usually 16-bit, because the number of bytes is a multiple of two /
xxxx – register value
00 1C 00 00 00 06 01 03 00 00 00 0A
00 1C 00 00 00 17 01 03 14 00 17 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
If the Council does not go: reloads often when you set up the driver + unless there is an exchange or writes nonsense, then analyze, what is inside the package exchange
You can take a sniffer Handy for Modbus TCP are here:
soft.mydiv.net/win/files-SmartSniff.html
We see that the connection is working and data changes.
#step_by_step, #Instruction, #WINCCOA, #MODBUS, #drivers, #SCADA
Russian version
Array
(
[ID] => 119
[IBLOCK_ID] => 1
[NAME] => WinCC OA&MODBUS TCP
[IBLOCK_SECTION_ID] =>
[IBLOCK] => Array
(
[ID] => 1
[~ID] => 1
[TIMESTAMP_X] => 14.10.2021 23:54:30
[~TIMESTAMP_X] => 14.10.2021 23:54:30
[IBLOCK_TYPE_ID] => EN
[~IBLOCK_TYPE_ID] => EN
[LID] => s2
[~LID] => s2
[CODE] => articles
[~CODE] => articles
[API_CODE] =>
[~API_CODE] =>
[NAME] => Articles
[~NAME] => Articles
[ACTIVE] => Y
[~ACTIVE] => Y
[SORT] => 10
[~SORT] => 10
[LIST_PAGE_URL] => /articles/
[~LIST_PAGE_URL] => /articles/
[DETAIL_PAGE_URL] => /articles/#ELEMENT_CODE#.html
[~DETAIL_PAGE_URL] => /articles/#ELEMENT_CODE#.html
[SECTION_PAGE_URL] =>
[~SECTION_PAGE_URL] =>
[CANONICAL_PAGE_URL] => https://lapshinvr.com/articles/articles.html
[~CANONICAL_PAGE_URL] => https://lapshinvr.com/articles/articles.html
[PICTURE] =>
[~PICTURE] =>
[DESCRIPTION] =>
[~DESCRIPTION] =>
[DESCRIPTION_TYPE] => html
[~DESCRIPTION_TYPE] => html
[RSS_TTL] => 24
[~RSS_TTL] => 24
[RSS_ACTIVE] => Y
[~RSS_ACTIVE] => Y
[RSS_FILE_ACTIVE] => N
[~RSS_FILE_ACTIVE] => N
[RSS_FILE_LIMIT] =>
[~RSS_FILE_LIMIT] =>
[RSS_FILE_DAYS] =>
[~RSS_FILE_DAYS] =>
[RSS_YANDEX_ACTIVE] => N
[~RSS_YANDEX_ACTIVE] => N
[XML_ID] =>
[~XML_ID] =>
[TMP_ID] =>
[~TMP_ID] =>
[INDEX_ELEMENT] => Y
[~INDEX_ELEMENT] => Y
[INDEX_SECTION] => N
[~INDEX_SECTION] => N
[WORKFLOW] => N
[~WORKFLOW] => N
[BIZPROC] => N
[~BIZPROC] => N
[SECTION_CHOOSER] => L
[~SECTION_CHOOSER] => L
[LIST_MODE] =>
[~LIST_MODE] =>
[RIGHTS_MODE] => S
[~RIGHTS_MODE] => S
[SECTION_PROPERTY] => N
[~SECTION_PROPERTY] => N
[PROPERTY_INDEX] => N
[~PROPERTY_INDEX] => N
[VERSION] => 1
[~VERSION] => 1
[LAST_CONV_ELEMENT] => 0
[~LAST_CONV_ELEMENT] => 0
[SOCNET_GROUP_ID] =>
[~SOCNET_GROUP_ID] =>
[EDIT_FILE_BEFORE] =>
[~EDIT_FILE_BEFORE] =>
[EDIT_FILE_AFTER] =>
[~EDIT_FILE_AFTER] =>
[SECTIONS_NAME] =>
[~SECTIONS_NAME] =>
[SECTION_NAME] =>
[~SECTION_NAME] =>
[ELEMENTS_NAME] => Элементы
[~ELEMENTS_NAME] => Элементы
[ELEMENT_NAME] => Элемент
[~ELEMENT_NAME] => Элемент
[REST_ON] => N
[~REST_ON] => N
[EXTERNAL_ID] =>
[~EXTERNAL_ID] =>
[LANG_DIR] => /
[~LANG_DIR] => /
[SERVER_NAME] => lapshinvr.com
[~SERVER_NAME] => lapshinvr.com
)
[LIST_PAGE_URL] => /articles/
[~LIST_PAGE_URL] => /articles/
[SECTION_URL] =>
[CANONICAL_PAGE_URL] => https://lapshinvr.com/articles/wincc-oa-modbus-tcp.html
[SECTION] => Array
(
[PATH] => Array
(
)
)
[IPROPERTY_VALUES] => Array
(
[ELEMENT_PREVIEW_PICTURE_FILE_NAME] => wincc oa&modbus tcp
[ELEMENT_META_TITLE] => Instructions for configuring the Modbus scada driver-WinCC OA
[ELEMENT_META_KEYWORDS] => wincc, oa, modbus, tcp, scada, protocol, step_by_step, Instruction, WINCCOA, MODBUS, drivers, SCADA
[ELEMENT_META_DESCRIPTION] => Create step-by-step instructions to learn how to configure the built-in Modbus driver for the WinCC OA scada system.
[ELEMENT_PAGE_TITLE] => WinCC OA&MODBUS TCP
[SECTION_META_TITLE] => Automation articles
[SECTION_META_KEYWORDS] => Automation, Articles
[SECTION_META_DESCRIPTION] => I met something worthy of attention during the work. It is difficult to assess the necessity of posting this or that article, I tried to clean up the obvious garbage
[SECTION_PAGE_TITLE] => Here I published articles that may be useful to someone in the production of work
)
[TIMESTAMP_X] => 17.10.2021 19:50:48
[META_TAGS] => Array
(
[TITLE] => WinCC OA&MODBUS TCP
[BROWSER_TITLE] => Instructions for configuring the Modbus scada driver-WinCC OA
[KEYWORDS] => wincc, oa, modbus, tcp, scada, protocol, step_by_step, Instruction, WINCCOA, MODBUS, drivers, SCADA
[DESCRIPTION] => Create step-by-step instructions to learn how to configure the built-in Modbus driver for the WinCC OA scada system.
)
[PREVIEW_TEXT] => The purpose of this article is to provide a step by step directions for the development of the built-in Modbus driver settings in the SCADA system WinCC OA.
Unfortunately, the basic course, this connection is not checked and do not give step by step instructions, so I eliminate this gap.
Step by step instructions for connecting a standard station WinCC OA for Modbus TCP protocol. Use popular simulator Modbus TCP Modbus Tools protocol (http://www.modbustools.com/download.html)
1. Must be pre-installed 64-bit operating system, or the key demo version Wincc OA (v3.14 or later)
2. Download the link above and install ModbusPollSetup64Bit.exe and ModbusSlaveSetup64Bit.exe. Install these components to simulate data flow (sending-receiving telegrams) on the Modbus TCP protocol
3. First run Modbus Slave (telegram generation) with the settings as shown in the figures, allowing work on the home network (upper tick)
[PREVIEW_PICTURE] => Array
(
[ID] => 438
[TIMESTAMP_X] => Bitrix\Main\Type\DateTime Object
(
[value:protected] => DateTime Object
(
[date] => 2021-10-17 19:50:48.000000
[timezone_type] => 3
[timezone] => Europe/Moscow
)
)
[MODULE_ID] => iblock
[HEIGHT] => 565
[WIDTH] => 399
[FILE_SIZE] => 33744
[CONTENT_TYPE] => image/png
[SUBDIR] => iblock/4d1
[FILE_NAME] => wincc_oa_modbus_tcp.png
[ORIGINAL_NAME] => wincc-oa-modbus-tcp.png
[DESCRIPTION] => WinCC OA
[HANDLER_ID] =>
[EXTERNAL_ID] => b3727abb2791d5e3cc4e29ad0434326d
[~src] =>
[SRC] => /upload/iblock/4d1/wincc_oa_modbus_tcp.png
[UNSAFE_SRC] => /upload/iblock/4d1/wincc_oa_modbus_tcp.png
[SAFE_SRC] => /upload/iblock/4d1/wincc_oa_modbus_tcp.png
[ALT] => WinCC OA&MODBUS TCP
[TITLE] => WinCC OA&MODBUS TCP
)
[DETAIL_PAGE_URL] => /articles/wincc-oa-modbus-tcp.html
)
Возврат к списку
