Clicking the Grafana tile on the home page lands you on a pre-configured dashboard. It shows the most important values from the attached IDEA-4S sensor at a glance.

Dashboard layout

• Four bearing-temperature stat tiles top-left: Bearing 1 through Bearing 4, in °C. With live data the tiles colour according to the configured thresholds.
• Three vibration-velocity gauges top-right: X, Y, Z axes, in mm/s. The scale runs green → yellow → red as values approach the IODD-defined thresholds.
• Time-series panel “IDEA-4S Temperature Bearings” bottom-left: all four bearings over the selected time range. The red dashed line is the alarm threshold; the yellow one the fault threshold.
• Time-series panel “IDEA-4S Vibration Velocity” bottom-right: the three axes over the selected time range.

Both time-series panels draw a continuous line even where a bearing reported nothing in a bucket of the selected range (from gmn-2.34.1). The four bearings do not report in the same instant; a bearing’s line used to break at every such point and leave scattered dots behind. Only a straight connection is drawn between two measured values — no value is invented. A genuine sensor dropout therefore does not show as a gap in the curve; it shows on the tiles above and on the diagnosis page.

Use the time-range picker top-right (here: “Last 5 minutes”) to switch between live and historical views.

Where does the data come from?

IDEA-4S sensor
    │ (IO-Link, RAW)
    ▼
IFM IO-Link master  ──── publishes via MQTT ──────┐
                                                  ▼
                                       Mosquitto broker
                                              │
                                              ▼
                                          DataStore  ── persists ─→  PostgreSQL
                                              │
                                              ▼
                                            Grafana

• The IO-Link master polls the IDEA-4S cyclically and sends each change as an MQTT message. The configured topics are visible in IOLink Master Configuration → Notification.
• DataStore subscribes to these topics, validates them against the schema, and writes the values into the local PostgreSQL on the edge.
• Grafana reads from the PostgreSQL and visualises it. The dashboard ships with the edge; you can clone and customise it.

Signing in: you already are

Grafana has no password of its own. The edge’s control interface signs you in there under your own user name — your name appears top right, and whatever you change is recorded under it. Signing out of the control interface ends your Grafana access with it.

What you may do there follows your role in the control interface:

Your role	In Grafana
Administrator	View, edit and save dashboards
User	View dashboards

If an administrator changes your role, Grafana follows immediately — from your next page load.

Custom dashboards

As an administrator, click Dashboards → New in Grafana’s left sidebar, or duplicate the shipped dashboard, to build your own views. Custom dashboards survive firmware updates — they are not overwritten by the repo seed.

If the save button is missing, you are not signed in to the control interface as an administrator.

Your own dashboard as the start page

Which dashboard the Grafana tab opens is set under Settings → Default Pages. Pick it from the list there — it holds exactly the dashboards that exist on this edge.

If you type the address by hand instead, mind which part you are copying:

/grafana-proxy/d/c10732a9-2e02-47cd-a033-059fb6f34344/idea-4s-dashboard-vwbaunatal
                └──────────────── UID ─────────────┘ └──────── name ────────┘

Grafana finds a dashboard by its UID alone and rewrites the name behind it on every request. An address carrying your dashboard’s name and another dashboard’s UID therefore opens the other one — it saves, it works, it just shows something else. Copies often carry very similar UIDs that differ only in the last few characters.

The control interface checks the address against the dashboards that exist when you save, and tells you when the UID and the name belong to two different dashboards.

How often the display refreshes

The refresh interval sits next to the time range at the top right of Grafana. The shortest setting the edge allows is half a second; 500 ms and 1 s are offered only by dashboards that carry those values in their own interval list — the delivered ones do.

It will not make the display faster than the values arrive. Measured on an edge over two hours, as the gap between consecutive values (median): vibration velocity 0.1 s, bearing and coolant temperatures 0.2 s — a one-second refresh is worth having there. Rotational speed came every 30 s because the spindle was idle: the sensor reports on change, and in operation its values are 0.1 s apart too.

For a smoother picture of a value that is not changing right now, the Refresh live dashboards switch (in the dashboard settings) is the better lever — it keeps the time axis moving without querying more often.

When the dashboard stays empty

If you see axes but no data, the data pipeline is usually broken somewhere:

1. Open Settings → Diagnosis and check that datastore, postgres, and mosquitto are green.
2. Open IOLink Master Configuration → Notification and confirm there is at least one MQTT subscription to 172.16.9.112:1883/teststand/idea-4s (example topic).
3. If both are OK but Grafana is still empty: this can be a known “memory-loss” case — refer to internal documentation or contact Brinkhaus support.