Translations:Подключение к ПЛК с Codesys/1/en — различия между версиями

Материал из WebHMI Wiki
Перейти к: навигация, поиск
(Новая страница: «WebHMI connects to the PLCs using the CodeSys development system via the Modbus / TCP protocol, by configuring an additional connection in the PLC configuration,…»)
 
Строка 1: Строка 1:
WebHMI connects to the PLCs using the CodeSys development system via the Modbus / TCP protocol, by configuring an additional connection in the PLC configuration, since for each Modbus / TCP client it is necessary to configure separate connections. Those. Even though a configured connection for communication, for example with SCADA system, can exist in the already functioning controller, it is also possible to work with SCADA, and with WebHMI this connection will not work. An additional connection is created as shown in the following figure (for example, the OWEN160 PLC):
+
WebHMI connects to the PLCs using the CodeSys development system via the Modbus / TCP protocol, by configuring an additional connection in the PLC configuration, since for each Modbus / TCP client it is necessary to configure separate connections. I.e. even though a configured connection for communication can exist in the already functioning controller (for example with SCADA system), it is not possible to work with SCADA and with WebHMI simultaneously over this connection. An additional connection is created as shown in the following figure (for example, the OWEN160 PLC):
 
[[Файл:Screenshot 2 1.png|1024px]]
 
[[Файл:Screenshot 2 1.png|1024px]]

Версия 11:33, 5 июня 2018

Информация о сообщении (править)
Это сообщение не имеет описания. Если вы знаете, где или как это сообщение используется, то можете помочь другим переводчикам, добавив к нему описание.
Формулировка сообщения (Подключение к ПЛК с Codesys)
WebHMI подключается к ПЛК использующим систему разработки CodeSys по протоколу Modbus/TCP, путем настройки дополнительного соединения в конфигурации ПЛК , поскольку для каждого клиента Modbus/TCP необходимо настраивать отдельные соединения. Т.е. несмотря на то, что в уже работающем контроллере может присутствовать сконфигурированное соединение для связи, например со SCADA системой, одновременно работать и со SCADA, и с WebHMI по этому соединению не получится. Дополнительное соединение создается как показано на следующем рисунке (на примере ПЛК ОВЕН160):
[[Файл:Screenshot 2 1.png|1024px]]
ПереводWebHMI connects to the PLCs using the CodeSys development system via the Modbus / TCP protocol, by configuring an additional connection in the PLC configuration, since for each Modbus / TCP client it is necessary to configure separate connections. I.e. even though a configured connection for communication can exist in the already functioning controller (for example with SCADA system), it is not possible to work with SCADA and with WebHMI simultaneously over this connection. An additional connection is created as shown in the following figure (for example, the OWEN160 PLC):
[[Файл:Screenshot 2 1.png|1024px]]

WebHMI connects to the PLCs using the CodeSys development system via the Modbus / TCP protocol, by configuring an additional connection in the PLC configuration, since for each Modbus / TCP client it is necessary to configure separate connections. I.e. even though a configured connection for communication can exist in the already functioning controller (for example with SCADA system), it is not possible to work with SCADA and with WebHMI simultaneously over this connection. An additional connection is created as shown in the following figure (for example, the OWEN160 PLC): Screenshot 2 1.png