PRTG Manual: Modbus RTU Custom Sensor
The Modbus RTU Custom sensor connects to a Modbus Remote Terminal Unit (RTU) server and monitors up to five returned numeric values.
For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.
- Dutch: Modbus RTU Custom
- French: Modbus RTU Custom
- German: Modbus RTU Custom
- Japanese: Modbus RTU Custom
- Portuguese: Modbus RTU Custom
- Russian: Modbus RTU Custom
- Simplified Chinese: Modbus RTU Custom
- Spanish: Modbus RTU Custom
- You can only create this sensor on a probe device, either a local probe device or a remote probe device.
- This sensor supports the IPv6 protocol.
- This sensor has a very low performance impact.
- This sensor always uses the serial port of the probe device.
- This sensor uses lookups to determine the status values of one or more channels. This means that possible states are defined in a lookup file. You can change the behavior of a channel by editing the lookup file that the channel uses. For details, see section Define Lookups.
- See the Knowledge Base: How can I apply Zoom Service Status sensors and Modbus sensors via device templates?
You cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. If you want to use this sensor, add it to a remote probe device.
The Add Sensor dialog appears when you manually add a new sensor to a device. It only shows the settings that are required to create the sensor. You can change nearly all settings on the sensor's Settings tab after creation.
Setting |
Description |
---|---|
Channel #1 - #5 Name |
Enter a name for the channel.
|
Channel #1 - #5 Register Type |
Select the type of the register. Choose between:
|
Channel #1 - #5 Data Type |
This field is only visible if you select Input register or Holding register above. Select the data type of the register. Choose between:
|
Channel #1 - #5 Unit |
This field is only visible if you select Input register or Holding register under Channel #x Register Type. Enter a unit for the channel. After sensor creation, you can change the unit of the channel in the channel settings under Unit. |
Channel #2 - #5 |
You can create up to 5 different channels for this sensor. You must define at least one data channel, so you see all available settings for Channel #1 without manually enabling it. Additionally, you can define Channel #2 to Channel #5. To do so, choose between:
|
Click the Settings tab of a sensor to change its settings.
Setting |
Description |
---|---|
Sensor Name |
Enter a name to identify the sensor. |
Parent Tags |
Shows tags that the sensor inherits from its parent device, parent group, and parent probe.
|
Tags |
Enter one or more tags. Confirm each tag with the Spacebar key, a comma, or the Enter key. You can use tags to group objects and use tag-filtered views later on. Tags are not case-sensitive. Tags are automatically inherited.
The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:
|
Priority |
Select a priority for the sensor. This setting determines the position of the sensor in lists. The highest priority is at the top of a list. Choose from the lowest priority ( |
Setting |
Description |
---|---|
Device COM Port |
Enter the component object model (COM) port of the serial port device.
|
Baud Rate |
Enter the speed of the serial connection in baud. The default baud rate is 9600. |
Parity |
Select the parity of the serial connection. Choose between:
|
Data Bits |
Select the number of the data bits of the serial connection. Choose between:
|
Stop Bits |
Select the number of stop bits of the serial connection. Choose between:
|
Retry Attempts |
Enter the number of retries until a timeout occurs. If you enter 0, the sensor does not retry the communication attempt. The default value is 3. Enter an integer. |
Receive Timeout (msec) |
Enter a receive timeout in milliseconds (msec). If the reply from the device takes longer than this value, the request is aborted and triggers an error message. The default value is 500 msec (0.5 seconds). |
Unit ID |
Enter the Modbus unit ID that you want to monitor.
|
Byte Order |
Select the sequence of the transmitted information. Choose between:
|
Setting |
Description |
---|---|
Channel #1 - #5 Register Type |
Shows the register type of the channel value.
|
Channel #1 - #5 Register Number |
Enter the register number from which you want to retrieve information.
|
Channel #1 - #5 Value Type |
This field is only visible if you select Input register or Holding register under Channel #x Register Type. Select the value type that the channel displays. Choose between:
|
Channel #1 - #5 Data Type |
This field is only visible if you select Input register or Holding register under Channel #x Register Type. Shows the Data Type of the Register Number.
|
Channel #1 - #5 Register Width |
This field is only visible if you select Input register bit or Holding register bit under Channel #x Register Type. Select the width of the value in the register. Choose between:
|
Channel #1 - #5 Bit Index |
This field is only visible if you select Input register or Holding register under Channel #x Register Type. Enter the index of the bit that you want to monitor.
|
Setting |
Description |
---|---|
Primary Channel |
Select a channel from the list to define it as the primary channel. In the device tree, the last value of the primary channel is always displayed below the sensor's name. The available options depend on what channels are available for this sensor.
|
Graph Type |
Define how different channels are shown for this sensor:
|
Stack Unit |
This setting is only visible if you enable Stack channels on top of each other as Graph Type. Select a unit from the list. All channels with this unit are stacked on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so. |
Setting |
Description |
---|---|
Result Handling |
Define what PRTG does with the sensor result:
|
By default, all of these settings are inherited from objects that are higher in the hierarchy. We recommend that you change them centrally in the root group settings if necessary. To change a setting for this object only, click under the corresponding setting name to disable the inheritance and to display its options.
For more information, see section Inheritance of Settings.
For more information, see section Root Group Settings, section Scanning Interval.
Schedules, Dependencies, and Maintenance Window
You cannot interrupt the inheritance for schedules, dependencies, and maintenance windows. The corresponding settings from the parent objects are always active. However, you can define additional schedules, dependencies, and maintenance windows. They are active at the same time as the parent objects' settings.
For more information, see section Root Group Settings, section Schedules, Dependencies, and Maintenance Window.
For more information, see section Root Group Settings, section Access Rights.
Which channel units are available depends on the sensor type and the available parameters. If no configurable channels are available, this field shows No configurable channels.
For more information, see section Root Group Settings, section Channel Unit Configuration.
Which channels the sensor actually shows might depend on the target device, the available components, and the sensor setup.
Channel |
Description |
---|---|
Downtime |
In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status in percent. |
[Value] |
The returned numeric values in up to five channels |
Knowledge Base
How can I apply Zoom Service Status sensors and Modbus sensors via device templates?
What security features does PRTG include?
For more information about sensor settings, see the following sections: