- Hyperview
- Quickstart
- Asset Management
- Product Catalog Management
- Discoveries
- Supported protocols
- What kind of data is collected?
- Setting up Data Collectors
- Adding or deleting discoveries
- Configuring discoveries
- Running discoveries
- Reviewing discovery reports
- Maintaining Data Collectors
- Best practices
- Settings
- Search Features
- Extracting Data
- Licensed Features
- AssetTracker
- Document Management
- Firmware Management
- Rack Security
- User Accounts
- Release Notes
- Hyperview 3.5 (May 3 2022)
- Hyperview 3.4 (April 6 2022)
- Product catalog management
- New licensed feature: Firmware Management
- Linux Data Collector enhancements
- New bulk actions: Update Access Policy, Update Model
- New Delta-T and average temperature sensors for racks
- Miscellaneous improvements
- API changes
- Deprecations
- New AvailableFirmwareVersions endpoint (licensed feature)
- New Bulk endpoints
- New FirmwareDownload endpoints (licensed feature)
- New FirmwareVersions endpoints (licensed feature)
- New Manufacturers endpoints
- New PduBreakers endpoint
- New ProductProperties endpoints
- New ProductPropertyKeys endpoint
- New Products endpoints
- New UserProductImages endpoints
- Notable bug fixes
- Known issues
- Hyperview 3.3 (January 17 2022)
- Hyperview 3.2 (November 18 2021)
- Hyperview 3.1 (September 17 2021)
- New bulk actions
- Heat map and environmental sensor visualizations
- New computed sensors
- New Network Components page for assets
- New asset type and asset property
- Sensor graph improvements
- Advanced Search improvements
- Miscellaneous improvements
- API changes
- Notable bug fixes
- Known issues
- Changes in version 3.1.1
- Changes in version 3.1.2
- Changes in version 3.1.3
- Changes in version 3.1.4
- Hyperview 3.0 (August 24 2021)
- Hyperview 2.6 (July 26 2021)
- Hyperview 2.5 (July 14 2021)
- Hyperview 2.4 (June 18 2021)
- Hyperview 2.3 (May 21 2021)
- Hyperview 2.2 (April 28 2021)
- Hyperview 2.1 (March 16 2021)
- Hyperview 2.0 (February 25 2021)
- Hyperview 1.6 (February 01 2021)
- Hyperview 1.5 (December 22 2020)
- Hyperview 1.4 (November 27 2020)
- Hyperview 1.3 (October 21 2020)
- Hyperview 1.2 (August 31 2020)
- Watched assets
- PDU breaker decorations
- New Assets By Location view
- New Assets by Type view and related changes
- Control credentials for rack PDUs
- Reachability monitoring
- Layout enhancements
- Discovery enhancements
- Rack Security enhancements (licensed feature)
- Other notable improvements
- API changes
- Known issues
- Notable bug fixes
- Changes in version 1.2.1
- Changes in version 1.2.2
- Changes in version 1.2.3
- Hyperview 1.1 (July 17 2020)
- Hyperview 1.0 (May 28 2020)
- RAMP3
- Release Notes
- RAMP Version 3.16
- RAMP Version 3.15
- RAMP Version 3.14
- RAMP Version 3.13
- RAMP Version 3.12
- RAMP Version 3.11
- RAMP Version 3.10
- RAMP Version 3.9
- RAMP Version 3.8
- RAMP Version 3.7
- RAMP Version 3.6
- RAMP Version 3.5
- RAMP Version 3.4
- Installation Guide
- Upgrade Guide
- User Guide
- Introduction
- Typical RAMP DCIM Deployment Scenarios
- Launching RAMP DCIM
- Application Menu
- Status
- Search
- Logs & Reports
- Action Menu
- Asset Information
- Software
- Operating Systems
- Retired Assets
- Adding Devices
- Add New
- Bulk Load
- Discoveries
- Tasks & Workflows
- Tasks
- Workflows
- Workflow Templates
- Planned Moves
- Notifications
- All Notifications
- Notification Methods
- Users
- Users
- Active Directory Groups
- Models
- Manage Documents
- Contracts
- End of Life
- BACnet Definitions
- Modbus Definitions
- Modbus Slave Mappings
- License Keys
- Locale and Units Settings
- Global Settings
- Asset Vue Settings
- RAMP Services Status
- Help
- Background jobs
- Tools
- Logout
- Visual Navigation Control
- Tree Navigation Control
- Performing a Tree Search
- Dragging and Dropping Using the Tree Control
- Device Types
- Blade Enclosure
- Blade Server
- Camera
- Environmental Monitor
- Expansion Module
- Generator
- In Row Cooling
- Network
- Other Devices
- Patch Panel
- PDU/RPP
- Rack
- Rack PDU
- Rack / Tower UPS
- Server
- Transfer Switch
- Undefined
- UPS
- Utility
- Virtual Server
- Logical Groups
- Tab Navigation
- Asset Views
- Cloud Support
- Location View
- Using AssetTracker
- Contacting Technical Support
- Appendix 1: Setting Up Monitoring for VMware
- Appendix 2: Email Configuration
- FAQ
- 1. Data Collector Configuration Fails with Unable to Register Error
- 2. Manager Configuration fails with Domain Authentication Error
- 3. Manager Configuration fails with IIS 7 Error
- 4. Manager Configuration fails with SQL Authentication Error
- 5. Data Collector process freezes at startup
- 6. Login issue for users authenticating using Windows AD
- 7. Requirements for Discovering Linux, FreeBSD and Windows Instances (Physical, virtual and cloud)
- 8. Managing Your Asset Limit
- 9. Report Device Count to Hyperview
- 10. RAMP licensing
- 10.1. What are the different types of licenses and how do they behave?
- 10.2. What does RAMP report?
- 10.3. Which assets are billable and which assets are not?
- 10.4. What URL does RAMP communicate with to send billing reports?
- 10.5. How often does RAMP report back home?
- 10.6. What happens when the number of assets change midterm?
- 11. Data Collector is Unable to Register URL
- 12. RAMP Device Types
- 13. Best Practices for Discovery in RAMP
- 14. End of Life and Support Policy
- Videos
- Integrations
- Release Notes
Managing Modbus TCP definitions¶
Modbus TCP is a communication protocol typically used by facility or building level assets. Hyperview allows the creation of Modbus TCP definitions to handle the monitoring of such equipment separate from auto-discoveries.
A Modbus TCP definition can be assigned to any number of assets to enable monitoring on that asset if they share the same object mapping, but only one definition can be applied to an individual asset at a time.
Adding a Modbus TCP definition¶
Go to Settings → Modbus TCP Definitions.
Click Add. Alternatively, if you have no Modbus TCP definitions, click Add new Modbus TCP definition.
Enter a Name and Asset Type for the definition, and click Save.
A success message will appear, and the Overview page of the new Modbus TCP definition will be displayed. Proceed to add sensor definitions.
Tip
Refer to the “Adding a single asset” section in Adding assets for steps to manually add assets with a Modbus TCP monitoring profile.
Adding a numeric sensor definition¶
While editing or adding the Modbus TCP definition, click the Numeric Sensors tab.
Click Add. Alternatively, if there are no existing sensor definitions, click Add Numeric Sensor.
Provide values for Address, Type, Data Type, Sensor Type, Sensor Name, Sensor Unit, and Multiplier. Note that the Sensor Name and Sensor Unit fields will only appear once you have selected a Sensor Type.
Click Save.
A success message will appear, and the numeric sensor definition will be listed in the grid. Repeat the steps to add additional sensor definitions as appropriate.
Adding a non-numeric sensor definition¶
While editing or adding the Modbus TCP definition, click the Non-numeric Sensors tab.
Click Add. Alternatively, if there are no existing sensor definitions, click Add Non-numeric Sensor.
Provide values for Object Instance, Type, Sensor Type, Sensor Name. Additionally, you can modify Value mappings (for all types) or add Value mappings (for non-binary types).
Click Save.
A success message will appear, and the non-numeric sensor definition will be listed in the grid. Repeat the steps to add additional sensor definitions as appropriate.
Updating a Modbus TCP definition¶
Go to Settings → Modbus TCP Definitions → Edit.
Update values from the Overview or Numeric Sensors tab as required, and save your changes.
A success message will appear for each change, and the current page will reload to reflect the change.
Updating or deleting a sensor definition¶
While on the Numeric Sensors tab or the Non-numeric Sensors tab for a Modbus TCP definition:
Click Edit to update values for an existing sensor definition. Click Save to save the updated sensor definition.
Click Delete → Delete to delete an existing sensor definition.
A success message will appear in each case, and the current page will reload to reflect the change.
Deleting a Modbus TCP definition¶
You cannot delete a Modbus TCP definition that has associated assets. After you have updated associated assets (from each asset’s Information → Monitoring page):
Go to Settings → Modbus TCP Definitions.
Click Delete → Delete for the intended definition.
A success message will appear, and the current page will reload to reflect the change.