Skip to main content

VibrationStreamMaster

Purpose

VibrationStreamMaster receives real-time and peak reports from a vibration sensor and maps the fields to variables.

Open the plugin

Enter "Development Configuration → Collection Configuration", create a device and select "VibrationStreamMaster" in "Collection Plugin".

Supported channels and data types

Channel typePre-configuration check
TCP ClientConfirm network reachability of the device IP, port, and gateway to the device.

Optional data types: Int32, Double, String

Plugin properties

Protocol parameters

SettingDescription
Station numberDefault: 1; Range: 1~65535; Fill in: text input. Set the station number used for protocol communication.

Address rules

  • actual.x, actual.y, actual.z, peak.accelerationx, peak.accelerationy, peak.accelerationz, peak.speedx, peak.speedy, peak.speedz, peak.offsetx, peak.offsety, peak.offsetz, peak.temperature, peak.voltage, peak.interval, address

Functions

FunctionPurpose
Reception monitoringConfirm that vibration reports reach the gateway.
Variable tableCheck real-time axes, peak acceleration, speed, offset, temperature, voltage, and update time.
Message statisticsReview received and discarded report counts.
Message logInspect the latest sensor frames when mapping does not update.

Device debug

Enter "Development Configuration → Collection Configuration", select the current device and click "More Functions", then open "Debug".

Dedicated debugging page

Use reception monitoring to check the latest vibration report and mapped variables.

VibrationStreamMaster debug subpage 1

Verify the configuration

  1. Make the sensor send one known test report.
  2. Confirm that reception monitoring shows a new frame.
  3. Check that the expected axis or peak variables and collection time update together.
  4. Compare a second report with the sensor display to confirm station number and field mapping.

Troubleshooting

  • No new frame appears: Confirm sensor reporting, station number, TCP address, port, and firewall.
  • Frames arrive but values do not update: Check the address field names, report format, data type, and variable mapping.
  • Values are implausible: Confirm units, axis order, station number, and the sensor's scaling settings.