The struggle to connect LoRaWAN devices to legacy BACS

Commercial building occupants want some level of intelligence and automation in their facilities, and real estate owners are racing to deliver via IoT. Perhaps this explains why the building automation and controls market is expected to grow at a CAGR of over 21% through 2028. After all, IoT in facilities is how you get to the promised office of the future — and recent trends have made smart buildings more of a requirement than a privilege.
Internet of Things
Companies have energy goals; IoT helps meet their needs through automated control of HVAC, lighting, and more.ethernet to rs485 adapter  The rise of remote work has resulted in an abundance of unused facility spaces; IoT can identify these spaces, personalize them for casual users, and provide data on how to optimize each square foot.

Given these market forces, the question is not whether to invest in smart building technology, but how to do so in a way that will provide a strong return on investment and support devices that use wired and wireless communications. The Long Range Wide Area Network (LoRaWAN) protocol is a promising solution for wireless devices that require less power than WIFI devices but have a longer range than Bluetooth devices. CAN2.0 Communication Module LoRaWAN is governed by the open, non-profit LoRa Alliance to create low-cost, low-power, long-range wireless connectivity between smart building devices and the platforms they work with.

The problem is that it is difficult for integrators to connect LoRaWAN devices to traditional wired building automation and control systems (BACS). The new IoT Access Protocol (IAP) solves this problem. That’s it.

Any medium or large building will most likely have a BACS with devices that use wired communications, and BACS is not designed to keep pace with IoT innovations. Operators have been using these traditional BACS platforms for decades to manage all the technologies within a building: HVAC, lighting, access control, security, elevators – all of which have gained considerable size with the addition of IoT. practicality.

If you want to scale building automation, you must transfer data from each discrete IoT device to BACS. But there is a mismatch between the LoRaWAN standard and the common BACS network protocol. ethernet to rs485 converter The connection protocols understood by BACS (to name a few) are very rich standards. They have rich data models, specify network services, and provide command and control capabilities—all strictly defined in the BACS architecture.

LoRaWAN itself does not meet all of these BACS definitions, making it difficult to create robust integrations.

The struggle to connect LoRaWAN devices to legacy BACSultima modifica: 2022-10-26T10:49:45+02:00da rubberantenna
Reposta per primo quest’articolo