custom_protocols
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
custom_protocols [2020/02/07 12:50] – [readRegister] emozolyak | custom_protocols [2021/07/23 14:03] – [Creating a Protocol] emozolyak | ||
---|---|---|---|
Line 21: | Line 21: | ||
To go to the list of user protocols, click on the button " | To go to the list of user protocols, click on the button " | ||
- | {{ :: | + | {{ :: |
You will be taken to the protocol management page. In this example, we see two demonstration protocols - ModBus TCP Demo and ModBus ASCII Demo: | You will be taken to the protocol management page. In this example, we see two demonstration protocols - ModBus TCP Demo and ModBus ASCII Demo: | ||
- | {{ :: | + | {{ :: |
Let's look at the page for editing the ModBus TCP Demo protocol: | Let's look at the page for editing the ModBus TCP Demo protocol: | ||
Line 40: | Line 40: | ||
The regular expression must ensure that the register address is validated on the register editing page (when this protocol is selected). Example: | The regular expression must ensure that the register address is validated on the register editing page (when this protocol is selected). Example: | ||
- | {{ :: | + | {{ :: |
We also see a convenient code editor. It supports formatting, highlighting and validation of syntax. So it's convenient to write the code | We also see a convenient code editor. It supports formatting, highlighting and validation of syntax. So it's convenient to write the code | ||
If there is a syntax error in the code, a red X appears in the corresponding line. To see a detailed error message, just point your mouse at it: | If there is a syntax error in the code, a red X appears in the corresponding line. To see a detailed error message, just point your mouse at it: | ||
- | {{:: | + | {{:: |
After creating the protocol, it will appear in the drop-down list of available PLC models on the page of creating newConnections and with it you can work as well as with the usual built-in protocol: | After creating the protocol, it will appear in the drop-down list of available PLC models on the page of creating newConnections and with it you can work as well as with the usual built-in protocol: | ||
- | {{ : | + | {{ : |
===== Necessary functions ===== | ===== Necessary functions ===== | ||
Line 446: | Line 446: | ||
As an example we've made (partually) several protocols: | As an example we've made (partually) several protocols: | ||
- | *[[http:// | + | *[[modbus_tcp_custom|ModBus TCP]] |
- | *[[http:// | + | *[[modbus_ascii_custom|ModBus ASCII]] |
- | *[[http:// | + | *[[modbus_rtu_custom|Modbus RTU]]. |
+ | *[[http_get_custom | HTTP request example]] | ||
*Other devices that were connected using [[http:// | *Other devices that were connected using [[http:// | ||
custom_protocols.txt · Last modified: 2023/02/21 17:52 by emozolyak