Discover
NODVIA Field discovers devices, verifies communication and builds project context.
BACnet · Modbus · Climatix · KNX · network toolsVisual HMI designer for NODVIA projects.
Turn field-discovered automation data into a real graphical HMI. NODVIA Studio uses the NODVIA project structure, so BACnet and Climatix points do not have to be manually re-entered into a separate visualization project.
ACTIVE DEVELOPMENT · FIELD TESTING · Studio is being developed alongside NODVIA Field and Project Visualization.

NODVIA connects field diagnostics, project data and graphical visualization in one workflow.
NODVIA Field discovers devices, verifies communication and builds project context.
BACnet · Modbus · Climatix · KNX · network toolsNODVIA Studio opens project points and turns them into HMI pages, popups, trends, schedules and graphical elements.
Values · Gauges · Trends · Schedules · Controls · IconsProject Visualization runs the Studio project directly inside NODVIA Field on an Android phone or tablet.
Fullscreen · Pages · Popups · Portrait / LandscapeOne project workflow from commissioning data to visualization — without rebuilding point lists manually.
The key difference from a generic HMI drawing tool is project context. Studio can use data already collected and organized by NODVIA Field.
Project devices and points are shown in a structured tree. For BACnet projects, context can include Device ID, IP, port, object type, instance, Object Name, Description and units.
Large projects can be searched by point name, description, object type, instance, Device ID, address, units or device/path information.
Studio can use the Climatix SCOPE hierarchy stored in the project, including regular points, schedules and history/trend objects when available.
Drag a point or element onto the canvas, position and resize it, then configure its properties. Multi-select, property reuse and page-based design reduce repetitive setup.
Built-in HVAC and automation vector symbols reduce dependency on external graphics packages and help keep HMI pages visually consistent.
Some elements can support animation or state-based appearance, such as fan rotation or value-dependent styling.
Studio can display the context of discovered BACnet points and use them for element bindings. The goal is to reduce manual re-entry of IP addresses, Device IDs and object instances.
Discovery remains a NODVIA Field task. Studio uses project data.
Climatix information collected through the Field/SCOPE workflow can appear in the Studio point tree. A visualization can include dedicated Climatix schedule and trend/history preview elements.
Studio is not Siemens SCOPE; it uses project data for the NODVIA visualization workflow.
Project Visualization is the Android runtime currently integrated into NODVIA Field. It loads the active project's visualization and renders it on a phone or tablet.
A Climatix schedule or trend can be shown directly on the HMI page. When deeper service access is needed, a click can open the detailed Climatix service view.
The operator experience stays simple while the engineer retains access to the underlying service workflow.
| Capability | NODVIA Field | NODVIA Studio | Project Visualization |
|---|---|---|---|
| Device discovery | Yes | No | No |
| Protocol diagnostics | Yes | No | No |
| Project point database | Creates / updates | Imports / uses | Uses |
| HMI page design | No / runtime functions only | Yes | No |
| Live visualization | through Project Visualization | Designer preview | Yes |
| Pages / popups | Runtime | Design | Runtime |
| BACnet project context | Collects | Displays / uses | Reads bindings |
| Climatix project data | Collects | Displays / uses | Displays supported elements |
The detailed article explains why a shared project model matters and how Field, Studio and Project Visualization complement each other.
Start with real devices in NODVIA Field, design the HMI in NODVIA Studio, and run the project on Android with Project Visualization.