For modbus to function correctly, your control system must be above version 2.0 firmware. If not then upgrade your control system first before you get started.
Modbus devices should appear under the modbus section in grid view.
If you are sure they are connected to your control system but not appearing, then you may need to scan for new modbus devices first from the control system view.
There are the usual columns at the start which are on most views. After that is product label which is just a way for users to identify what type of modbus device it is. This is useful if the product name is not yet in our database, i.e. the product name is GTIN: 12345678 instead of a meaningful name.
The driver type should match the driver used for the modbus device. This will determine what properties to be set on the device and will differ between each type. The custom type allows you to set custom values for the device including the instance point count which will automatically create new points for you in the point tab.
There is also a link to the corresponding device location for the modbus device.
The point tab contains all of the related modbus device points that have been created for each device. The values will not be editable unless the driver type is set to custom in which case you can give each point an address, details on how to convert the input values that are being read by the device, and the details for the general purpose sensor about what unit is being read and the magnitude for the values.
There is also a link to the corresponding instance for the modbus device point.
Once all of these are setup, you are ready to configure the general purpose sensor portions of the modbus device. For more information on this, see our FAQ on configuring general purpose sensors.
Comments
0 comments
Article is closed for comments.