MultiViz App User Guide

1. Overview

MultiViz is an Atrium app that connects NCD wireless vibration sensors to MultiViz, the condition monitoring and predictive maintenance platform from Viking Analytics.

MultiViz analyzes vibration data with machine learning to detect machinery faults early and prioritize maintenance. To do that, it needs a steady stream of overall vibration values and time waveforms from each machine. The MultiViz app delivers that stream from the Atrium Gateway: it opens its own encrypted MQTT connection to the broker that MultiViz provisions for your account, and publishes the data of every sensor you link, in the NCD data format. No extra server, Node-RED flow or programming is needed.

The app also gathers the sensor settings MultiViz depends on into one window, can request waveforms from sensors on demand, and shows each sensor’s battery, signal and publishing status.

How the data flows

1. The sensor transmits over the wireless mesh network to the Atrium Gateway, which decodes it.
2. If the sensor is linked and its Report switch is on, the MultiViz app publishes the message to the MultiViz MQTT broker.
3. MultiViz receives the message on the sensor’s topic and builds its asset view on its own platform. There is no asset or machine mapping to do in Atrium.

Each linked sensor sends two kinds of messages:

• Overall: overall vibration and temperature values, at every Data Transmission Interval.
• Waveform: the raw vibration signal (time domain), sent automatically at the Auto Waveform Transmission Interval (Gen4 sensors), or in reply to an on-request waveform command.

2. Requirements

What you need before installing the app.

Supported sensors

3. Installing

Install the app from a package file (.tar.gz) on the gateway’s Apps page.

1. 1
   Open the Apps page

   Log in to the Atrium dashboard and click Apps in the top navigation.
2. 2
   Upload the package

   Use the upload control on the Apps page to select the MultiViz package file (for example multiviz-0.1.0.tar.gz). If MultiViz is listed in the App Center, you can install it from there instead.
3. 3
   Wait for the gateway to reload

   Installing an app restarts the gateway’s services. This takes a few seconds; the page reconnects on its own. Sensor data and settings are kept.
4. 4
   Open the app

   MultiViz appears as a card on the Apps page, with the subtitle Vibration Bridge. Click it to open the app on its Overview screen.

Reinstalling or upgrading the package keeps your broker settings, linked sensors and history.

4. First-Time Setup

The shortest path from a fresh install to data arriving in MultiViz.

Get the MQTT broker details from MultiViz

1. 1
   Open the integration in MultiViz

   Log in to MultiViz, click Integrations in the sidebar.

   

2. 2
   Connect

   Find the ncd.io integration and click Connect.

   

3. 3
   Copy the generated credentials

   MultiViz generates the broker details: broker address, port, user name, password and topic root. Keep them at hand for the next steps.

Connect the Atrium MultiViz app and link a sensor

1. 3
   Open the broker settings

   In the app’s Overview, click the gear button on the MultiViz MQTT Broker card.
2. 4
   Enter the details and connect

   Fill in Broker URL, Port, User name, Password and Topic root, optionally click Test connection, then click Connect. Wait for the Connection status to read Connected, then click Close.
3. 5
   Link a sensor

   Click + Link a sensor, select the sensor in the Sensor list and click Link to MultiViz. Read the popup and click OK. The sensor appears at the top of the Linked Sensors table with its Report switch off.
4. 6
   Apply the recommended settings (Gen4)

   Click the gear button on the sensor’s row, set the values in Recommended values, click Save hardware settings, and reset the sensor (RESET button or magnet on the RESET switch) so it checks in and receives them. Wait for Settings status: Settings applied.
5. 7
   Start publishing

   Turn the sensor’s Report switch on. Reset the sensor to force a transmission, and check that Last Report MultiViz updates and that the data arrives in your MultiViz account.

5. Overview Screen

The app’s home screen: the broker connection, sensor counts, and the sensors linked to MultiViz. It refreshes automatically every 5 seconds.

The two tabs at the top, Overview and Manage Sensors, switch between the app’s screens. The header shows the app version and the gateway model. Hover over any column title, button or field to see a tooltip.

Status cards

Linked Sensors table

Lists every linked sensor, the most recently linked first. + Link a sensor opens the Manage Sensors screen. With no sensors linked, the table reads “No sensors linked yet.”

Row buttons

6. MultiViz MQTT Broker Window

Opened from the gear button on the MultiViz MQTT Broker card. Holds the connection to your MultiViz broker.

7. Sensor Basic Hardware Settings

Opened from the gear button on a Gen4 sensor’s row. Contains the sensor settings recommended to get started with MultiViz.

From the factory, Gen4 sensors use Smart Mode features and have automatic waveform transmission off, to save battery. MultiViz needs regular overall data and periodic waveforms, so these settings usually need changing. All other settings stay on the sensor’s own page in Atrium: Sensors > select the sensor > Settings > Sensor Configuration.

Fields

The window shows only the fields the sensor’s type and firmware support. Under each field, Sensor reports shows the value the sensor has now, the allowed range, and any value still waiting to send.

Recommended values

Saving and applying

1. 1
   Save

   Click Save hardware settings. Only changed fields are saved; the button is disabled until you change something.
2. 2
   Let the sensor check in

   Saved settings are sent the next time the sensor checks in with the gateway (every 60 minutes unless the sensor’s check-in interval was changed). To apply them right away, reset the sensor: press and release the RESET button, or hold a magnet near the RESET switch and move it away.
3. 3
   Watch the Settings status

   The box at the bottom shows the delivery status, the last check-in and the estimated next check-in. Close the window once it reads Settings applied.

Reset to current values puts every field back to the value the sensor reports now and discards unsaved edits. Saving after a reset also cancels any change still waiting to be sent. Cancel closes the window without saving.

8. On-request Waveform Data

Opened from the waveform button on a sensor’s row. Makes Atrium send a waveform request to the sensor right after each of its data transmissions; the sensor answers with a waveform message, which is published to MultiViz.

• Gen4 sensors: optional. If the sensor already sends waveforms automatically (Auto Waveform Transmission Interval), you don’t need it.
• V3 sensors (types 80 and 81): the only way to get waveforms, because they don’t send them automatically.

Request types

Enable a request

1. 1
   Choose and save

   Select the request type (and probe, sample rate and duration if shown) and click Save. The text beside the button confirms what is saved, or warns about unsaved changes.
2. 2
   Enable

   Turn on the On-request waveform data switch. It reads Enabled, and Atrium sends the saved request after every data transmission from the sensor until you turn it off.

On 2-channel sensors, the status is shown per probe (for example “Probe 1: Waveform received”).

9. Historical, Details and Remove

The other three windows opened from a sensor’s row.

Historical

Titled Latest publications, it lists the sensor’s last 50 events, newest first, with their date and time.

Details

Shows everything that doesn’t fit in the table: MQTT publish (On or Off), Sensor model, Type, Probes, Device address, Firmware, Location, Asset, Battery, RSSI, Last Seen on Atrium, Last Report MultiViz, On-request waveform status and Linked since. Location and Asset come from the sensor’s settings in Atrium.

Remove

The trash-can button asks Remove sensor from MultiViz?. Click Remove to unlink the sensor: it stops sending data to MultiViz and leaves the table. The sensor itself stays on the gateway, and you can link it again from Manage Sensors. To stop publishing only for a while, turn its Report switch off instead.

10. Manage Sensors Screen

Lists every supported vibration sensor on the gateway and links new ones to MultiViz.

Link a sensor to MultiViz

The Sensor list shows the whitelisted vibration sensors that aren’t linked yet, as type – name (last 8 characters of the address). Select one and click Link to MultiViz. A 2-channel sensor is linked as one sensor, both probes included.

The link starts with publishing off, and a popup confirms it:

• Sensor linked to MultiViz (Gen4): recommends checking the basic sensor configuration before enabling the Report switch.
• V3 vibration sensor linked to MultiViz (types 80 and 81): explains that the sensor has no automatic waveforms (use On-request Waveform Data) and is configured with Node-RED.

Click OK to go to the Overview, where the new sensor is highlighted at the top of the table.

Vibration Sensors on this Atrium Gateway

11. Integration

What the app sends, where, and what it reads from the gateway.

MQTT

Radio commands to sensors

The app sends commands to sensors over the wireless network in two cases only: waveform requests while On-request Waveform Data is enabled, and the settings you save in Sensor Basic Hardware Settings (delivered by Atrium at the sensor’s check-in).

Automations, inter-app bus and AI assistants

The app does not publish events or provide actions on the Atrium inter-app bus, so it adds nothing to the Automations page. It does not expose any tools or data to an AI assistant over MCP.

Data the app reads from the gateway

• Sensor messages, as Atrium receives them.
• The sensor list: type, firmware, name, location, asset, battery, RSSI and last seen time. Only whitelisted sensors are shown.
• Sensor configuration and check-in status, for the Sensor Basic Hardware Settings window.
• The gateway model and the gateway’s radio address (for Use this Atrium).

12. Settings and Data Handling

Where the app keeps its settings and how it handles credentials.

• Broker password: stored encrypted on the gateway and never shown again after saving.
• TLS: always used; there is no setting to turn it off.
• History: the last 50 events per sensor are kept for the Historical window; older ones are deleted automatically.
• Upgrades and reinstalls keep the broker settings, linked sensors, on-request waveform settings and history.
• Removing a sensor unlinks it from MultiViz only. Its Atrium data and settings are not touched, and the app keeps its on-request waveform settings and history in case you link it again.

13. Troubleshooting

Common problems, their cause and the fix.

14. Reference

Defaults and limits.