- Home
- Category
- Hvac And Refrigeration
- Hvac Controls And Thermostats
- Building Automation Network Controllers
- Bacnet Controllers Gateways
Showing 0 products
Frequently Asked Questions
What makes BACnet different from a general protocol?
It carries meaning, not just numbers.
Devices present objects with units and descriptions.
Alarm limits and reliability travel with the value.
A client can ask what a device contains.
The system can be browsed rather than decoded.
That is what it was designed for.
Why does that help multi-vendor work?
Devices describe themselves.
Nobody has to document register maps first.
A third party supervisor can read both.
Alarming and scheduling are defined in the protocol.
They are not invented per project.
Integration effort falls considerably.
What does a gateway actually do?
Presents non-BACnet equipment as BACnet objects.
The rest of the system then sees it natively.
It is useful and it is a compromise.
One more device to configure and maintain.
Its mapping is project-specific knowledge.
Document it where it can be found later.
Do all BACnet devices support the same things?
No, and the label implies more than it delivers.
Devices are certified to profiles.
Two products can support different services.
Ask for the conformance statement, not the logo.
Check the services the design depends on.
Scheduling and trending are common gaps.
What has to be planned across an estate?
Device instance numbering and addressing.
Instances must be unique across the network.
Per-building schemes collide when sites are joined.
Retrospective renumbering is disruptive.
Set a convention before the first device.
Record it with the network documentation.
Which physical layer should be used?
It depends on distance and device count.
Twisted pair suits field devices and long runs.
Ethernet-based variants suit controller backbones.
Mixed estates commonly use both.
Routers join the segments.
Decide the topology before wiring anything.
What should be required at handover?
The conformance statements for every device type.
The object list and instance numbering scheme.
Gateway mappings in readable form.
Network topology with segment addresses.
This is what a future integrator will need.
Without it the openness is theoretical.