Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
blocks:app-note:netio_modbus [2024-03-14 14:06] mattias [Control NETIO PDU using Modbus/TCP] |
blocks:app-note:netio_modbus [2024-03-14 15:06] (current) admin [Setup in the Device] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Control | + | =====Control |
- | Work in progress. Currently on hold. | + | |
- | This application note assumes minimum | + | This application note, and the method it describes, requires |
- | At time of writing all current models of Netio power distribution units support modbus via its M2M (machine2machine) | + | All current models of Netio's Power Distribution Units (PDU) support Modbus. |
- | This method requires less configuration compared | + | The Modbus |
====Setup in the Device==== | ====Setup in the Device==== | ||
Line 10: | Line 9: | ||
Find the M2M Api tab and enable the modbus/tcp option. | Find the M2M Api tab and enable the modbus/tcp option. | ||
{{: | {{: | ||
- | Blocks does not support changing | + | Blocks does not support changing |
- | ====Channel addressing==== | + | =====Setup in Blocks editor==== |
+ | ===Channel addressing=== | ||
Consult the [[https:// | Consult the [[https:// | ||
- | Add a modbus | + | Add the modbus |
+ | ===Setup sockets=== | ||
+ | Add a modbus channel, give it a unique for the device, permanent and meaningful name, set the type to Digital (bit), set the direction to out. This will result Blokcs using modbus function 15 (Write Multiple Coils) (Blocks does not support Function 5 (write single coil) That means it sends the current property of all coils in a single call to the device in a single call. | ||
+ | For Netio devices always add as many sockets as the device has. If the device supports two sockets add both, if it supports 4, add all four. The device does not support the way coils are set by Blocks unless all sockets are present. | ||
- | ====Control | + | :!: It is important to not add coil channels that are not available on the device since the device will not perform any actions att all. |
+ | They can then be accessed in blocks with their respective modbus channel property. | ||
- | Add a modbus channel, give it a unique for the device, permanent and meaningful name, set the type to Digital (bit), set the direction to out. This will result in Function 15 (Write Multiple Coils) (Blocks does not support Function 5 (write single coil) That means it sends the current property of all coils in a single call to the device in a single call. | + | ===Setup metering |
- | + | ||
- | Add as many channels as the device support. If the device support two outlets add both, if it supports 4 add all four. | + | |
- | + | ||
- | :!: It is very important to not add coil channels that is not available on the device since the device will not perform any actions att all. | + | |
- | They can then be accessed in blocks with their respective modbus channel Boolean property. | + | |
- | + | ||
- | ====Metering | + | |
Some NETIO devices support extensive power metering options. | Some NETIO devices support extensive power metering options. | ||
From the manual we can find the register we want to access, i.e the Mains Voltage of the device is accessed on Register 1, Function 04 and it is a 16 bit Type. | From the manual we can find the register we want to access, i.e the Mains Voltage of the device is accessed on Register 1, Function 04 and it is a 16 bit Type. | ||
Line 35: | Line 32: | ||
{{: | {{: | ||
- | As an example, to the get the device voltage we enter channel number 2, select the Analog-16bit-word type and direction in. | + | As an example, to get the device |
- | This will result in a new channel using Function 4. | + | |
====Example configuration in Blocks==== | ====Example configuration in Blocks==== |