The URL is used to transport all addressing information necessary to describe the MODBUS connection and register addresses. Timeout in milliseconds of the modbus request.

Note that the reading request timeout can be still controlled using modbus:timeout property. The client will issue a reading command every modbus:pollingTime milliseconds. This property defines the total amount of registers or coils that should be written, beginning with the register specified with the property 'modbus:address'. This property defines the starting address of registers or coils that are meant to be written. The physical bus address of the unit targeted by the mobus request. Notice that when used in conjunction with modbus:function, the value of modbus:function property is ignored. Futhermore, it can be used in multi-operation forms whereas modbus:function cannot. The client will then determine the right function code to be applied in the modbus request.

It can be filled with the following keywords: Coil, DiscreteInput, InputRegister, HoldingRegister. The list is build from wikipedia definition of modbus function names, it can be different in proprietary implementations of modbus protocol.įunction IDs or labels can be either used as values of modbus:function property.Ī more user-friendly property to specify modbus:function. The list of the available function is the following: Function ID Specifies which modbus function should be issue in the requested command. Note: for further details please refer to the documentation. In particular, the optional step sudo npm run link must be executed. Remember to correctly initialize your development environment as described inside the repository readme,īefore starting the example application. servients/modbus-cli/dist/modbus-cli.js modbus-example.js # first init the node package cd examples/servients/modbus-cli

Test server wot download