BAS, simply put, is the automation synchronization of multi-system building. For those who are engaged in building management, this thing is simply a big trouble that we have to face every day! Many new friends, as well as some masters who have worked for several years, are often confused when they encounter this BAS and don’t know how to start to make each subsystem obedient and work simultaneously!
BAS Basic Points
1. The underlying principle of system docking : that is, building subsystems of different brands and different agreements, such as air conditioning systems, lighting systems, access control systems, etc., must be able to "talk" each other and achieve a tacit cooperation at the data level.
2. Timeline unification is crucial : all modules participating in synchronization must have a unified "time referee", otherwise you will go to yours and I will go to my Multiverse BAS Synchronization. If time does not match, then there is no way to talk about synchronization!
3. Tips for setting priority : During the synchronization process, each task must be ordered in sequence. For example, the fire signal must be at the highest level. Once there is a situation, it must be responded immediately. Other non-tasks must be slightly later. Provide global procurement services for weak current intelligent products!
Key steps to disassemble
1. First list the list of all the BAS subsystems to be synchronized, and mark their models, communication protocols, data interface parameters and other messy but very critical things!
2. Then, according to the listed list, a suitable middleware is equivalent to a "translator" and "coordinator", which can help different systems to build a bridge of communication – don't think it's enough to just find a middleware, be cautious!
3. Configure that damn communication interface. This step must be very careful. Entering a wrong number may cause the entire synchronization to fail, which is a headache!
FAQ
Q: The system is always interrupted synchronously. Do you have to restart them all?
A: When encountering this situation, don’t rush to restart all devices! You first check whether the network is stable. It is likely that a node is loose or the switch is exhausted. If there is no problem with the network, check whether the middleware cache is full. Clearing the cache can sometimes solve the problem!
Q: Is there no problem with the BAS systems of different manufacturers really perfectly synchronized?
A: Perfect synchronization is almost difficult to achieve in actual operation… But through standardized protocol conversion and patient parameter debugging, it is still possible to achieve a relatively ideal synchronization state, which is rather laborious!
Practical Pit Avoidance Guide
1. Never ignore the importance of that system log! If you check the log frequently, you may be able to discover the upcoming synchronization abnormality in advance based on some clues inside – it is really useful!
2. Before doing formal synchronization, you must experiment several times in the test environment and simulate all possible extreme situations. Don’t just operate rashly in the real environment, otherwise the losses will be huge if there is a problem!
3. Regularly evaluate and optimize the synchronization strategy, because as the buildings are used, various loads and user needs will change, and the original strategy will definitely not be applicable, so you need to adjust according to the situation!
Personal opinion: Overall, although BAS is complex and cumbersome to operate, it will encounter various problems that are very difficult, as long as you master the basic points and key steps above and have enough patience to debug and optimize, it can still enable the building automation system to achieve relatively efficient and stable synchronous operation, providing strong technical support for smart building management!
Leave a Reply