In cases where you want to write “preset values” to specified coils and/or holding registers in a Modbus device using a linkable “Write” action, you can add special “Preset” components under the device. These are not actually proxy points—you need to copy them from the modbusAsync or ModbusTcp palette.
In rare cases, you may also wish to read/write string data from Modbus files in a device. The palettes also have a component especially for this application, which you can also copy under the Modbus device.
The following procedures explains how:
To add client Modbus presets
To add preset components under a client Modbus device:
-
Open the
modbusAsyncormodbusTcppalette in the Palette side bar. -
In the Nav side bar, expand the client Modbus network to show the Modbus device of interest.
-
From the palette, drag the “Presets” folder onto the Modbus device in the Nav side bar (or, into the property sheet view of that device, if open).
-
In the popup Name dialog, accept the default “Presets” name or enter an alternate name, and click .
The folder is added under the device. By default it contains two “preset containers,” each with one “preset entry”—one for a preset coil, one for a preset holding register. Either preset container can be deleted (if not needed), or duplicated, as well as have additional “preset entries” added.
-
In any preset container, configure the “Starting Address” and other property values, and in its child preset entries (coil or register types), enter the actual preset values.
For more details, see Modbus preset components.
You do not have to copy the entire “Presets” folder from the palette—this is just the easiest way to add both preset containers,
each with a single preset entry child. You can locate preset containers anywhere under the Modbus device. However, be aware
if you copy these components under the Points container, they are not visible in any Modbus Client Point Manager view.
To add client Modbus file records
To add components for client Modbus file records, use the following procedure:
-
Open the
modbusAsyncormodbusTcppalette in the Palette side bar, if not already opened. -
In the Nav side bar, expand the client Modbus network to show the Modbus device of interest.
-
From the palette, drag the “Modbus File Records” folder onto the Modbus device in the Nav side bar (or, into the property sheet view of that device, if open).
-
In the popup Name dialog, accept the default “Modbus File Records” name or enter an alternate name, and click .
The folder is added under the device. By default it contains a single “ModbusClientStringRecord” component. You can duplicate it if multiple file record objects are needed.
-
Double-click the added component to open its property sheet, and enter appropriate configuration values per the Modbus device vendor’s documentation.
For more details, see About Modbus (client) file records.
You do not have to copy the entire “Modbus File Records” folder from the palette—this is simply the easiest way to add the
needed component with a descriptive parent folder. You can locate ModbusClientStringRecord components anywhere under the Modbus
device. However, be aware if you copy these components under the Points container, they are not visible in any Modbus Client Point Manager view.