Bring BACnet data and scheduling into Ignition. Add Application Generator where discovery and model generation support your engineering.
Start with what your project requires. Understand the BACnet connection first, then decide where discovery and application generation can support the engineering.
BACnet+ IP and BACnet+ SC bring building data and scheduling into Ignition. Choose the transport that fits your network.
CXS Application Generator supports discovery and model generation. Give discovered data an equipment structure, then continue engineering your Ignition application.
Ignition already has BACnet capabilities. The useful question is which additional CXS capabilities and engineering tools fit your project. Component selection and licensing belong in that conversation.
Choose BACnet/IP or BACnet Secure Connect for the network your application needs.
BACnet+ IP by Relatech-CXS brings BACnet/IP building systems into Ignition with native integration for data acquisition and scheduling. Change-of-Value subscriptions and multiple-property reads support efficient data acquisition, with configuration and deployment managed within Ignition. Build applications that use the operational capabilities of your building systems—from live equipment values to schedules.
Discuss BACnet+ IP
BACnet+ SC by Relatech-CXS brings BACnet Secure Connect building systems into Ignition through encrypted, certificate-based communication, with native integration for data acquisition and scheduling. Change-of-Value subscriptions and multiple-property reads support efficient data acquisition, with configuration and deployment managed within Ignition. Build applications around secure building connectivity while retaining access to equipment values and schedules.
Discuss BACnet+ SCFollow one building-system example from device discovery to an application you can continue to build.
Explore the devices and points on an accessible BACnet network. Understand what is present before deciding how it belongs in the project.
Discovery depends on the network, devices and access available to the project.
Organize the discovered data around a recognizable location and piece of equipment. A point becomes more useful when the application carries its context.
The equipment model should reflect the project’s engineering standards.
Carry the equipment structure into Ignition engineering. Review the generated output, complete the project-specific work and test the resulting application.
Application Generator supports the engineering workflow; it does not replace application design or commissioning.
This is an engineering sequence. Adding Application Generator does not, by itself, change the runtime architecture.
The right starting point depends on the infrastructure you have and the work you need to do.
Look at the available devices, the network and the equipment model you want to carry into Ignition.
Define connectivity and the planned equipment model first. Work through where discovery and application generation will fit as the system develops.
Keep the first discussion focused on the BACnet connectivity your project needs. Assess engineering tools as a separate part of the fit.
No. BACnet Plus addresses connectivity; Application Generator supports discovery and model generation for engineering. Discuss the required components and their licensing for your particular project.
No. The generated structure is a starting point. Project-specific application design, review, testing and commissioning remain part of the engineering work.
Contact the CXS team with your target Ignition version, BACnet requirements and project stage. Confirm current versions, evaluation access, licensing and support before planning an installation.
Tell us what you are connecting, which Ignition version you are working with, and what you need to achieve.
Discuss your projectAsk about project fit, current availability and the right evaluation path.