A smart infrastructure team needed to replace legacy LonWorks controller paths with a BACnet/IP presentation that could scale across two sites. Chipkin FieldServer helped convert 29 LonWorks devices and 1,994 mapped points into a working BACnet/IP deployment after XIF collection, Neuron ID planning, and data-type cleanup were brought under control.
This was not a small gateway job. The project combined five LonWorks application types, two replacement gateways, and nearly two thousand points that had to be exposed cleanly enough for the downstream BACnet system to commission without guesswork.
At a Glance
- Industry: Enterprise building automation
- Location: California, USA
- Customer: Smart infrastructure and building automation integrator
- Facility type: Dual-site controller replacement project
- Client role: Digital deployment specialists and commissioning team
- Project scale: 29 LonWorks devices across 2 gateways and 1,994 mapped points
- Protocols: From: LonWorks -> To: BACnet/IP
- Chipkin product: Chipkin FieldServer gateway pair replacing MEC06 and MEC07 controller paths
- Project start: August 2022
- Internal reference: FSE15149
Architecture: LonWorks devices and XIF-based mappings -> LonWorks -> Chipkin FieldServer -> BACnet/IP -> building management system
LonWorks to BACnet/IP Challenge
The upstream/server side was a mixed LonWorks environment spanning five application types, including app 9077, 9140, 9145, 9642, and 8053. The downstream/client side needed the full point model normalized into BACnet/IP across two gateway instances tied to different controller replacement scopes.
The complexity came from both scale and source quality. The customer had to provide the right XIF files and device mapping details, while the final gateway build also depended on accurate Neuron IDs for each device. Until all of that source information was in place, the BACnet side could not be considered complete.
Commissioning added another layer. Once the BACnet presentation was live, one class of source values still had to be represented with the correct BACnet object type. That is a real LonWorks migration issue: values can be technically present while still being modeled incorrectly for the downstream client if object semantics are not checked carefully.
Why Chipkin
This was a strong fit for Chipkin because the project combined LonWorks XIF handling, large point-count mapping, and live BACnet commissioning support. Chipkin FieldServer provided the gateway platform, while Chipkin support helped the customer move from partial source documentation to a finished BACnet/IP presentation that could be commissioned in the field.
Projects like this are rarely blocked by the idea of protocol conversion alone. They are blocked by the work required to turn diverse source artifacts into a clean, testable deployment.
The Solution
Chipkin built two gateway configurations to cover the MEC06 and MEC07 replacement scopes, mapping the LonWorks device types into BACnet/IP with the required point structure. The project used XIF-based source definitions to establish the BACnet exposure, while the customer supplied the device-to-gateway assignments and the Neuron IDs needed for final deployment.
The solution matured in stages. Initial files brought four device types into the project, then a later update added the final 8053 application type once its XIF file was available. During live commissioning, the customer and Chipkin also aligned the BACnet object modeling so values with a wider source range would be represented correctly on the BACnet side.
That combination turned the project into a reusable migration pattern rather than a one-off lab exercise. The customer ended up with a field-proven LonWorks to BACnet/IP workflow that could support the full multi-device scope.
For another BACnet/IP retrofit that depended on careful source-side data handling, see the Modbus RTU to BACnet/IP Remote Chiller Integration case study.
Multi-Site BMS Migration Results
The project delivered a working LonWorks to BACnet/IP migration path across two gateway deployments.
Project proof points:
- 29 LonWorks devices were mapped into the replacement architecture.
- 1,994 total points were exposed across the two BACnet/IP gateway files.
- 5 LonWorks application types were incorporated, including a late-stage 8053 addition.
- The final deployment commissioned successfully after BACnet object modeling was aligned with the source values.
Have a Similar LonWorks Migration Project?
Need to replace a legacy LonWorks integration path with a usable BACnet/IP handoff? Chipkin can help with XIF-driven mapping, large point-count gateway configuration, and commissioning support for complex retrofit projects. Tell us about your project.
Frequently Asked Questions
Can FieldServer convert LonWorks to BACnet/IP for a large migration?
Yes. This project used two FieldServer gateways to bring 29 LonWorks devices and 1,994 mapped points into a BACnet/IP replacement architecture.
What source information is needed for a LonWorks migration?
XIF files, device-to-gateway assignments, and the correct Neuron IDs all matter. This case study shows how the BACnet side stays incomplete until those source artifacts are confirmed.
Can Chipkin support high point-count commissioning work?
Yes. The delivered value here was not only gateway hardware. Chipkin also helped the customer work through staged file updates and BACnet object-model corrections during commissioning.