Discover BACnet/IP devices, browse objects and properties, watch live values, review priority behavior, trend points, inspect alarms, and diagnose communication problems.
Premium integration
Commissioning with GEM
Bring equipment online with confidence.
Discover supported equipment, inspect native protocol data, map it into the property, and verify the complete control path—from the device to the interface.
Start with what is there
Find the equipment before entering it.
GEM can scan the local network for likely devices and show their address, vendor, open ports, and a suggested driver. Import a result and the device editor opens with the connection details filled in, ready for an integrator to review and complete.
Network discovery operates on the networks visible to the GEM controller. Results and driver suggestions still require review.
- 01DiscoverFind likely equipment on the local network.
- 02ReviewConfirm the device, driver, and connection details.
- 03MapPlace useful points into GEM’s property model.
- 04VerifyTest control and live feedback end to end.
Native protocol tools
See what the equipment is actually saying.
Dedicated explorers keep common discovery, inspection, mapping, and troubleshooting work inside GEM.
Work with Modbus/TCP or Modbus/RTU, scan unit IDs and register spaces, decode live values, test points, and inspect raw communication when the manual is not enough.
Premium integration
One operating model
Turn protocol points into useful controls.
Select an object or register; choose the subsystem and zone it belongs to; and define what the point represents in GEM.
Test the live read before saving, create a zone without leaving the explorer, and review the mapping before it becomes part of the working system.
Native protocolObject · Register
GEM modelSubsystem · Zone · Attribute
Working systemInterface · History · Automation
Mapped values become part of GEM’s shared model while commands are translated back through the appropriate driver.
At project scale
Repeat the work without repeating the entry.
Start with a known-good configuration, then carry it forward carefully across similar equipment and properties.
Duplicate
Turn one proven device configuration into a set of related devices without rebuilding each one from an empty form.
Move known-good configuration
Carry supported devices, zones, attributes, command sets, and other reusable building blocks between staging and production systems.
Use AI for larger batches
Describe the equipment and structure, review the proposed work, and let GEM reduce repetitive configuration entry.
Verification
Handoff starts with evidence.
A green connection indicator is only the first check. Test the connection, send a known command, watch live state return, and confirm each zone is bound to the right device and address.
Explorer diagnostics, activity, and read-only configuration checks give the project team better context before handoff.
- The driver reports a healthy connection
- A known command produces the expected response
- Live feedback returns to GEM
- Points and zones map to the intended controls
- Diagnostics find no unresolved commissioning issues
Manual device commissioning is always available. Network discovery is part of the Network Monitoring module. BACnet and Modbus—including their dedicated explorers—are premium integration products. AI-assisted batch work is optional and currently requires a customer-supplied Anthropic API key.
From design intent to a confident handoff.
Talk with our team about the equipment, protocols, and commissioning workflow for your project.