SPS Nuremberg · 24–26 Nov 2026 · Hall 5, Booth 120 · Visit us!

Book a meeting at our booth →
SPS Nuremberg, 24–26 November 2026, Hall 5, Booth 120 – Relatech CXS, Inductive Automation, Ignition

Meet us at SPS 2026

Experience Ignition and CXS live: Hall 5, Booth 120. Book a fixed appointment with our team.

Book a meeting
Engineering tools / BACnet

Start with the network.
Build with structure.

Discover BACnet devices and objects, configure how they belong in the project, and generate a structured starting point for your Ignition application.

Existing CXS demonstration in Ignition Designer showing equipment tags and an HVAC view
Existing CXS demo · not a live connection
ConnectivityContextEngineering
What it helps you do

Make the integration
work for the project.

Start with the information you need, the system it comes from and the application it must serve.

01

Discover the starting material

Scan the accessible BACnet network and review the devices and objects available to the project.

02

Shape the equipment model

Use configuration and naming conventions to organize information around locations and equipment.

03

Generate, then engineer

Review the output, complete project-specific application work and validate it against the system.

How the pieces relate

A clear path
from source to use.

Use this relationship to frame the technical discussion. Exact module placement and capabilities depend on the selected product and version.

CXS BACnet Application Generator conceptual workflow
Conceptual relationship · confirm product, version and deployment requirements.
In application

A model you can work with.

The existing demonstration shows an equipment hierarchy beside an HVAC view in Ignition Designer. It makes the relationship between system structure and application work visible; it does not prove which resources were generated automatically.

Explore CXS for Ignition
Application platformIgnition by Inductive Automation
Existing demonstration in Ignition Designer

Existing CXS demonstration; illustrates application context, not proof of every product feature.

Before you specify

Resolve the details
that matter.

Use these questions to shape a focused technical evaluation.

What is generated?

Existing documentation describes application objects, I/O references and a hierarchical model. Confirm the exact generated resources and template behavior for the selected release.

What happens when the system changes?

The product documentation describes resynchronization. Review how updates are proposed, how manual changes are preserved and what rollback is available before repeating generation.

What remains with the engineer?

Network prerequisites, application decisions, validation and commissioning remain project work. Generation is a starting point, not evidence of a completed application.

Built for builders

Bring us the application.

Tell us what you are connecting, the platform you use and the work you need to do.

Discuss your project
WordPress Cookie Notice by Real Cookie Banner