Overview
Device details is the third page in the Platform Manager drill-down: General overview → Site overview → Device details. What it shows is not configured per device. It is configured once per device type, under Configuration → Device type, and every device of that type gets the same page.
That configuration is spread across six tabs, and this lesson walks all of them.
Prerequisites
- Platform Manager configured with sites and devices (see How to Configure Platform Manager: Sites, Devices, and KPIs)
- Superadmin access — the whole Configuration section requires it
- Points tagged with
site,deviceTypeanddeviceID. These three keys are fixed - Identical point names across every device of the type. This is the part that actually decides whether a layout works
How a Device Details Page Resolves
Platform Manager builds one query and applies it in two halves. First it filters points by the three fixed tags — site against the Site record’s XID, deviceType against the Device type record’s XID, and deviceID against the device’s Device ID. Then it narrows that set to the point names listed in the device type’s groups.
Both halves have to match, and the names are case-sensitive. If either side misses, the card renders empty and no error is raised.
Warning
There is no per-tile tag query. A layout tile does not “find” points by a point-type tag — it displays the group of point names you listed on the Metering, Set points or Additional points tab. If one generator calls its output point “Power” and another calls it “Output kW”, one device type cannot serve both.
Step 1: Open the Device Type
- Go to Configuration → Device type
- Pick a device type from the list on the left, or choose New to create one
- The tab strip is Device type, Metering, Set points, Additional points, Columns, Layout
On the Device type tab:
- Export ID (XID) — required, and this is the value each point’s
deviceTypetag must equal. ACATEGORY-MODELshape such asGEN-S7-1300Tkeeps it readable - Name — required; what appears in drop-downs and panels
- Image path — a path in the file store for the device type image
- Device list point — the point whose value is shown against each device in list views
- Allowed sites — which sites this device type may be used at
- Any custom properties your deployment defines, such as Manufacturer, Model or Category
Step 2: Group the Points
Three tabs define which points appear and where. All three work the same way: Add new group, name the group, then Add new data point and type the point name.
| Tab | Feeds | Behaviour |
|---|---|---|
| Metering | The main values card | The headline readings for the device type |
| Set points | The set points card | Rendered as editable points, so operators can write to them |
| Additional points | The additional points card | A plain list of supporting points |
Multiple groups can be created per tab, and both groups and the points inside them can be re-ordered by dragging.
Tip
Point names here must match the real point names exactly, including case. This is the single most common reason a device type works on one device and not on another.
Step 3: Set the Columns
The Columns tab chooses which points supply each column of the devices table on Site overview. The columns themselves are defined first at Configuration → Global; this tab maps a point to each one for this device type.
Step 4: Build the Layout
The Layout tab is the template grid for Device details. Add new item adds a tile; the pencil icon edits a tile’s size and content; the trash icon removes it. Tiles carry a size such as 2X2 or 8X2, and the grid is drag-and-resize.
Each tile has a type. For a device type these are available:
| Tile type | What it shows |
|---|---|
| Main values | The Metering groups |
| All values | Every point matched for the device |
| Additional points | The Additional points groups |
| Set points | The Set points groups, as writable controls |
| Device info | The device type and device identity fields |
| Active alarms | Alarms scoped to this device |
| Charts | Time-series charts |
| Custom chart | A chart you configure yourself |
| Dashboard | An existing Mango by Radix IoT dashboard embedded in the page |
| Watchlist | An existing watch list |
| Component | A custom UI component from your user module |
A workable generator layout leads with Device info, puts Main values and All values in a wide tile across the top, keeps Active alarms in the right column, and drops Additional points, Charts and Set points underneath.
Warning
A Set points tile writes to the device. A user can only action it if their roles are in the target point’s set permission, so confirm that before exposing controls on a shared layout.
Step 5: Test Across Devices
- Open Site overview and click a device of the configured type
- Confirm each tile shows the data you expect
- Open a different device of the same type and confirm the same template loads with that device’s values — this is the test that actually proves the type
- Exercise a set point control, if the layout has one
- Check the page as a non-superadmin user to confirm they see what they should
Where KPIs Fit — and Where They Do Not
KPIs are a Site and Global feature only. There is no KPI tab on a device type, and Device details does not read the KPI configuration. Device-level presentation is entirely the Layout tab’s job. If you need something the tile types cannot express, embed a Dashboard tile pointing at a custom dashboard.
Troubleshooting
| Issue | Cause | Fix |
|---|---|---|
| The page is empty for one device | Its deviceType tag does not equal the Device type record’s XID, or its deviceID tag does not equal the device’s Device ID | Compare both tag values against the records, not against display names |
| One card is empty, the rest populate | The point names in that group do not match the device’s point names | Compare the group’s names to the actual point names, including case |
| A layout works on one device and not another | The two devices name the same reading differently | Standardise the point names, or split them into two device types |
| A set point control does nothing | The user’s roles are not in the point’s set permission | Add the role to the point’s set permission |
| A card is missing entirely | No tile of that type is on the Layout | Add the tile on the Layout tab |
| Nothing renders and there is no error | Expected — a tag or point-name mismatch fails silently | Check the tags first, then the point names |
Tips from the Field
Name Points Before You Build Types
A device type is only as reusable as the naming underneath it. Agreeing point names per equipment class first turns this lesson into ten minutes of configuration; discovering the disagreement afterwards means renaming points across a fleet.
Use the Multistate Renderer, Not a Meta Point
For a multistate point that reports numeric status codes, set its text renderer to Multistate on the point’s Text renderer properties tab and map each value to a label there. The device layout then shows the label. Building a separate meta point to translate the number is unnecessary work.
One Type Per Real Variation
If two models genuinely expose different points, they are two device types, not one type with gaps. Allowed sites keeps the list manageable as the count grows.
Summary
A device type is a template for the Device details page. The Device type tab holds its identity and XID; Metering, Set points and Additional points list the point names each card shows; Columns feeds the devices table on Site overview; and Layout arranges the tiles. Matching is by the three fixed tags plus exact, case-sensitive point names, KPIs stay at Site and Global level, and a mismatch renders an empty card with no error. Get the naming right and one template serves the whole fleet.