ModbusClientPresetRegisters is a container used for writing preset Modbus holding register data values to a client Modbus device. As copied from the palette, a single child ModbusClientPresetRegister entry exists in this component, where you can enter a preset value for that register. Also, you can add additional (consecutive) preset register entries, each with its own value, by using the “Add Preset Register Value” action (or by duplicating or by copying from the palette).

ModbusClientPresetRegisters configuration requires specifying the Starting Address of the first register, and also the Data Type (Integer, Float, Long, Signed Integer). All child preset register components must use this data type.

Writing occurs when the linkable “Write” action is fired. Values specified in the dynamic children are written to the device using the specified starting (absolute) address, and the slot order of the children determines what (consecutive) address is assigned to their values.

As needed, you can copy these components from the modbusAsync or modbusTcp palette into a ModbusAsyncDevice, ModbusTcpDevice, or ModbusTcpGatewayDevice.

Presets (registers and coils) provide write-access only, and are not proxy points—they do not produce polling activity. If copied under the Points container of the client Modbus device, they will not be visible in the Point Manager. You may wish to add a “Presets” container under the device to keep any preset objects.

For more details, see Modbus Client Preset Coils.