<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> 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.

Modbus RTU Custom Sensor

Modbus RTU Custom Sensor

i_square_cyanFor a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Sensor in Other Languages

  • 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

Remarks

  • 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?

i_podYou 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.

Add Sensor

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.

Modbus Channel Specific

Setting

Description

Channel #1 - #5 Name

Enter a name for the channel.

i_round_blueAfter sensor creation, you can change the name of the channel in the channel settings under Name.

Channel #1 - #5 Register Type

Select the type of the register. Choose between:

  • Coil: Coil numbers start with 0 and range from 00001 to 09999.
  • Discrete input: Discrete input numbers start with 1 and range from 10001 to 19999.
  • Input register: Input register numbers start with 3 and range from 30001 to 39999.
  • Holding register: Holding register numbers start with 4 and range from 40001 to 49999.
  • Input register bit: Select Input register bit to monitor a specific bit of the received value. Input register numbers start with 3 and range from 30001 to 39999.
  • Holding register bit: Select Holding register bit to monitor a specific bit of the received value. Holding register numbers start with 4 and range from 40001 to 49999.

i_round_redIt is not possible to change the register type after sensor creation.

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:

  • 16-bit integer
  • Unsigned 16-bit integer
  • 32-bit integer
  • Unsigned 32-bit integer
  • 64-bit integer
  • Float
  • Double

i_round_redIt is not possible to change the data type after sensor creation.

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:

  • Disable (default): The sensor does not create this channel.
  • Enable: The sensor creates this channel. Specify at least the name, type, and register number for this channel below.

i_round_redYou cannot add additional channels after sensor creation.

Basic Sensor Settings

Click the Settings tab of a sensor to change its settings.

Basic Sensor Settings

Basic Sensor 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.

i_round_blueThis setting is for your information only. You cannot change it.

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.

i_round_blueIt is not possible to enter tags with a leading plus (+) or minus (-) sign, nor tags with parentheses (()) or angle brackets (<>).

i_round_blueFor performance reasons, it can take some minutes until you can filter for new tags that you added.

The sensor has the following default tags that are automatically predefined in the sensor's settings when you add the sensor:

  • modbus

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 (i_priority_1) to the highest priority (i_priority_5).

Modbus RTU Specific

Modbus RTU Specific

Modbus RTU Specific

Setting

Description

Device COM Port

Enter the component object model (COM) port of the serial port device.

i_round_blueOn Windows systems, the COM port of the device looks like this, for example: COM3.

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:

  • None (default)
  • Even
  • Odd

Data Bits

Select the number of the data bits of the serial connection. Choose between:

  • 8 (default)
  • 7
  • 6
  • 5

Stop Bits

Select the number of stop bits of the serial connection. Choose between:

  • 1 (default)
  • 2

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 value.

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.

i_round_blueIn a standard Modbus network, there are up to 247 unit IDs, each with a unique assigned identifier from 1 to 247.

Byte Order

Select the sequence of the transmitted information. Choose between:

  • Big-endian (AB CD)
  • Little-endian (DC BA)
  • Big-endian byte swap (BA DC)
  • Little-endian byte swap (CD AB)

Modbus Channel Specific

Modbus Channel Specific

Modbus Channel Specific

Setting

Description

Channel #1 - #5 Register Type

Shows the register type of the channel value.

i_round_bluePRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

Channel #1 - #5 Register Number

Enter the register number from which you want to retrieve information.

i_round_redThe register number must be a number that contains one to five digits. The sensor supports numbers between 0 and 65534.

i_round_blueDepending on your Modbus device, you may need to remove the register type prefix. For example, you need to enter 60 for the input register 30060 or 316 for the holding register 40316.

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:

  • Absolute: Integer64 values with or without an operational sign, such as 10 or 120 or -12 or 120.
  • Delta (counter): The sensor calculates the difference between the last value and the current value. The sensor additionally divides the delta value by a time period to indicate a speed value. The sensor ignores this setting if you select Double or Float as Channel #x Data Type.
    i_round_redThis mode only works if the difference between the last and the current value is positive and increases with each scanning interval. This mode does not support negative values and decreasing values.

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.

i_round_bluePRTG shows this value for reference purposes only. If you need to change this value, add the sensor anew.

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:

  • 16 bits wide (default)
  • 32 bits wide
  • 64 bits wide

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.

i_round_blueEnter a value between 0 and 15, 31, or 63, depending on the Channel #1 - #5 Register Width. 0 monitors the least significant bit. To monitor the most significant bit, enter 15 for a 16-bit register, 31 for a 32-bit register, or 63 for a 64-bit register.

Sensor Display

Sensor Display

Sensor Display

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.

i_round_blueYou can set a different primary channel later by clicking b_channel_primary below a channel gauge on the sensor's Overview tab.

Graph Type

Define how different channels are shown for this sensor:

  • Show channels independently (default): Show a graph for each channel.
  • Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
    i_round_redYou cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

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.

Debug Options

Debug Options

Debug Options

Setting

Description

Result Handling

Define what PRTG does with the sensor result:

  • Discard result: Do not store the sensor result.
  • Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

i_podThis option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

i_round_blueIn a cluster, PRTG stores the result in the PRTG data directory of the master node.

Inherited Settings

By default, all of the following 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 b_inherited_enabled under the corresponding setting name to disable the inheritance and to display its options.

i_square_cyanFor more information, see section Inheritance of Settings.

Scanning Interval

Click b_inherited_enabled to interrupt the inheritance.

Scanning Interval

Scanning Interval

Setting

Description

Scanning Interval

Select a scanning interval from the dropdown list. The scanning interval determines the amount of time that the sensor waits between two scans. Choose from:

  • 30 seconds
  • 60 seconds
  • 5 minutes
  • 10 minutes
  • 15 minutes
  • 30 minutes
  • 1 hour
  • 4 hours
  • 6 hours
  • 12 hours
  • 24 hours

i_round_blueYou can change the available intervals in the system administration of PRTG Network Monitor.

If a Sensor Query Fails

Select the number of scanning intervals that the sensor has time to reach and to check a device again if a sensor query fails. Depending on the option that you select, the sensor can try to reach and to check a device again several times before the sensor shows the Down status. This can avoid false alarms if the monitored device only has temporary issues. For previous scanning intervals with failed requests, the sensor shows the Warning status. Choose from:

  • Set sensor to down immediately: Set the sensor to the Down status immediately after the first request fails.
  • Set sensor to warning for 1 interval, then set to down (recommended): Set the sensor to the Warning status after the first request fails. If the second request also fails, the sensor shows the Down status.
  • Set sensor to warning for 2 intervals, then set to down: Set the sensor to the Down status only after the third request fails.
  • Set sensor to warning for 3 intervals, then set to down: Set the sensor to the Down status only after the fourth request fails.
  • Set sensor to warning for 4 intervals, then set to down: Set the sensor to the Down status only after the fifth request fails.
  • Set sensor to warning for 5 intervals, then set to down: Set the sensor to the Down status only after the sixth request fails.

i_round_blueSensors that monitor via Windows Management Instrumentation (WMI) always wait at least one scanning interval before they show the Down status. It is not possible to immediately set a WMI sensor to the Down status, so the first option does not apply to these sensors. All other options can apply.

i_round_blueIf you define error limits for a sensor's channels, the sensor immediately shows the Down status. None of the interval options apply.

i_round_blueIf a channel uses lookup values, the sensor immediately shows the Down status. None of the interval options apply.

Schedules, Dependencies, and Maintenance Window

i_round_blueYou 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.

Schedules, Dependencies, and Maintenance Window

Schedules, Dependencies, and Maintenance Window

Setting

Description

Schedule

Select a schedule from the list. You can use schedules to monitor during a certain time span (days or hours) every week. Choose from:

  • None
  • Saturdays
  • Sundays
  • Weekdays
  • Weekdays Eight-To-Eight (08:00 - 20:00)
  • Weekdays Nights (17:00 - 09:00)
  • Weekdays Nights (20:00 - 08:00)
  • Weekdays Nine-To-Five (09:00 - 17:00)
  • Weekends

i_round_blueYou can create schedules, edit schedules, or pause monitoring for a specific time span. For more information, see section Schedules.

Maintenance Window

Select if you want to set up a one-time maintenance window. During a maintenance window, monitoring stops for the selected object and all child objects. They show the Paused status instead. Choose between:

  • Do not set up a one-time maintenance window: Do not set up a one-time maintenance window. Monitoring is always active.
  • Set up a one-time maintenance window: Set up a one-time maintenance window and pause monitoring. You can define a time span for the pause below.

i_round_blueTo terminate an active maintenance window before the defined end date, change the time entry in Maintenance Ends to a date in the past.

Maintenance Begins

This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the start date and time of the one-time maintenance window.

Maintenance Ends

This setting is only visible if you enable Set up a one-time maintenance window above. Use the date time picker to enter the end date and time of the one-time maintenance window.

Dependency Type

Select a dependency type. You can use dependencies to pause monitoring for an object depending on the status of a different object. You can choose from:

  • Use parent: Use the dependency type of the parent object.
  • Select a sensor: Use the dependency type of the parent object. Additionally, pause the current object if a specific sensor is in the Down status or in the Paused status because of another dependency.
  • Master sensor for parent: Make this sensor the master object for its parent device. The sensor influences the behavior of its parent device: If the sensor is in the Down status, the device is paused. For example, it is a good idea to make a Ping sensor the master object for its parent device to pause monitoring for all other sensors on the device in case the device cannot even be pinged. Additionally, the sensor is paused if the parent group is paused by another dependency.

i_round_blueTo test your dependencies, select Simulate Error Status from the context menu of an object that other objects depend on. A few seconds later, all dependent objects are paused. You can check all dependencies under Devices | Dependencies in the main menu bar.

Dependency

This setting is only visible if you enable Select a sensor above. Click b_search_light and use the object selector to select a sensor on which the current object will depend.

Dependency Delay (Sec.)

This setting is only visible if you select Select a sensor above. Define a time span in seconds for the dependency delay.

After the master sensor for this dependency returns to the Up status, PRTG additionally delays the monitoring of the dependent objects by the time span you define. This can prevent false alarms, for example, after a server restart or to give systems more time for all services to start. Enter an integer value.

i_round_redThis setting is not available if you set this sensor to Use parent or to be the Master sensor for parent. In this case, define delays in the parent device settings or in its parent group settings.

Access Rights

Click b_inherited_enabled to interrupt the inheritance.

Access Rights

Access Rights

Setting

Description

User Group Access

Define the user groups that have access to the sensor. You see a table with user groups and group access rights. The table contains all user groups in your setup. For each user group, you can choose from the following group access rights:

  • Inherited: Inherit the access rights settings of the parent object.
  • No access: Users in this user group cannot see or edit the sensor. The sensor neither shows up in lists nor in the device tree.
  • Read access: Users in this group can see the sensor and view its monitoring results. They cannot edit any settings.
  • Write access: Users in this group can see the sensor, view its monitoring results, and edit its settings. They cannot edit its access rights settings.
  • Full access: Users in this group can see the sensor, view its monitoring results, edit its settings, and edit its access rights settings.

i_square_cyanFor more details on access rights, see section Access Rights Management.

Channel Unit Configuration

Click b_inherited_enabled to interrupt the inheritance.

i_round_blueWhich 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.

Channel Unit Configuration

Channel Unit Configuration

Setting

Description

Channel Unit Types

For each type of channel, select the unit in which PRTG displays the data. If you define this setting on probe, group, or device level, you can inherit these settings to all sensors underneath. You can set units for the following channel types (if available):

  • Bandwidth
  • Memory
  • Disk
  • File
  • Custom

i_round_blueCustom channel types are only available on sensor level.

Channel List

i_round_blueWhich channels the sensor actually shows might depend on the monitored 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

More

i_square_blueKnowledge Base

How can I apply Zoom Service Status sensors and Modbus sensors via device templates?

What security features does PRTG include?

Sensor Settings Overview

For more information about sensor settings, see the following sections: