Engineering toolkit
An all-in-one commissioning and fault-finding workspace for discovering devices, testing BMS protocols and turning raw network activity into usable engineering evidence.
One engineering workspace
JNEX brings the network and protocol tools a commissioning engineer normally opens separately into one connected workflow, keeping discovery results, test evidence and reporting together.
Scan a selected IP range, inspect local ARP evidence and open a discovered device’s web page directly from the results. When a controller’s configured address is unknown, JNEX provides active ARP and deeper packet-based MAC hunts rather than relying on a single basic scan.
MAC addresses can be matched against OUI manufacturer information, while the IP changer helps the engineer move the laptop adapter onto the correct address and subnet for commissioning.
JNEX combines IP, ARP and BACnet evidence into a deduplicated device record instead of leaving results scattered across separate tabs. The inventory can retain host, manufacturer, model, BACnet identity, supported protocols, last-seen information, engineer notes and lifecycle status.
Discovered, inferred and manually entered information remain distinguishable. Where the evidence supports it, JNEX can also flag the likely Niagara generation, before the inventory is filtered or exported as CSV and JSON.
Discover BACnet/IP devices automatically across active interfaces or work through manual and BBMD-based scenarios. Engineers can inspect device information, browse objects, search for points and view live values without moving into a separate BACnet utility.
BACnet MS/TP support extends the same workflow to serial trunks while preserving the evidence needed to understand how each device was found.
Scan Modbus TCP ranges and RTU addresses with visible progress, communication outcomes and configurable timing. Safe register reads, retry handling and retained results help distinguish a slow or intermittent response from a genuinely absent device.
Raw TX/RX packets are shown alongside plain-English translations, with additional serial tools for NMEA, ASCII and SDI-12. M-Bus support remains in development.
The built-in lab provides known device responses for learning, demonstrations and checking the workflow away from a live site. Engineers can explore protocol behaviour and reporting without needing an available controller for every test.
This gives new users a safe route through the toolkit before applying the same controls to a real network.
The Diagnostic Assistant explains errors and packet activity in practical language, while logs and audit information preserve what was attempted and what responded. This makes troubleshooting easier to follow and easier to communicate after the visit.
Commissioning reports and downloadable protocol evidence can combine findings, raw exchanges and translated explanations for handover or further investigation.
Inside JNEX
This full-HD walkthrough moves through the real beta interface and its connected engineering tools. Click the window to pause or resume.
JNEX early access
Join the JNEX list for field-test updates, preview builds and release news.