Number of views: 3213 Author: AILI Industrial Release time: 2026-11-20 Source: Ai Li Industrial
Before the air-conditioning box is connected to the building automation system, a point table including roll call, function, signal type, unit, range, read and write permissions, alarm and failure status should be provided. Simply listing 'can connect to the Internet' or 'supports remote control' is not enough to complete the connection. It is also necessary to clarify the boundaries of responsibility between the equipment controller and the building control.
For example, the supply air temperature not only needs to have a name, but also needs to describe the collection location, unit, valid range and update method; when starting and stopping the fan, commands, operating feedback and faults need to be distinguished. Analog values, switching values and communication points cannot be replaced by each other just by name. When remote writing is involved, local priority, permissions and recovery logic need to be confirmed.
Basic attributes include roll call, device number, data type, unit and range; control attributes include read and write, valid conditions, local remote and command priority; exception attributes include alarm, communication interruption, power outage and recovery status. If you only write the roll call but not these attributes, it is easy for both parties to have inconsistent understandings during docking. For the relationship between control logic and measuring points, please refer toHow should the air supply temperature sensor of the air conditioning box avoid the influence of local airflow?。
If communication methods such as Modbus are used, the interface form, site address, register number, function code, data type, scaling and byte order need to be clarified. Just because both parties support the same protocol does not mean that register addresses and numerical interpretations will automatically be consistent. The BACnet interface needs to describe the object type, device identification and read and write rules. For the difference between interface form and dry contact, please refer toWhat is the difference between the BACnet interface and dry contact linkage of the air conditioning box? andWhat register information should be specified in Modbus communication of air conditioning box?。
In addition to normal operating data, the point table should also include status such as filter pressure differential alarm, fan failure, sensor failure, communication interruption, and power outage recovery. Control commands and operating feedback must be separated and cannot be represented by the same point. For protection signals involving interlocking, the triggering conditions and recovery methods should be explained to prevent the upper system and local control from overwriting each other.
The priority and confirmation method of alarm points must also be agreed upon. Which alarms require shutdown and which ones are only prompts should be determined by the project control logic and cannot be temporarily added in the upper system. When involving the linkage of multiple devices, please refer toThe supporting ideas of FFU computer group control system clarify the relationship between single unit failure and group control strategy.
Both parties check the values, directions, scaling and real movements according to the same version, and record unopened or unavailable points. Interface testing should include abnormal conditions and cannot only verify normal display. After the point table is changed, the control instructions and as-built data are updated simultaneously to avoid inconsistencies between the on-site version and the system configuration.
During joint debugging, you can first verify the read-only points, then verify the read-write points and alarm points, and proceed in order. If a numerical deviation is found, the range, scaling and byte order should be checked first, and then whether it is a problem with the on-site measurement points or the communication configuration.
When confirming the control matching with Aili Industrial, you can first exchange the floor control point table and division of responsibilities so that the equipment signals and the upper system can be connected according to the same caliber. Aili Industrial has the ability to develop control system software and hardware, and can communicate fan start and stop, speed regulation, temperature and humidity adjustment, filter pressure difference prompts and external equipment linkage according to project requirements; specific sensors, actuators, communication protocols and interface forms are confirmed in the planning stage to facilitate connection with the project control system.
Product form can be viewedAir handling unit andFan box page; clean air supply package can be combinedFFU fan filter unit andCheck the fan filter unit at the EFU equipment end ; when it comes to gaseous pollution control, you can communicate separatelyChemical filter solutions. The specific point table content, communication method and delivery scope still need to be verified based on the corresponding configuration data and on-site working conditions. The actual effect is subject to on-site joint debugging and performance test results.
Submit project parameters:https://ailigy.com/contactus.html
Is it enough to only write the roll call name and address in the order form?
not enough. Function, signal type, unit, range, read and write permissions, alarm and failure status are also required, otherwise it will be easy to understand inconsistently during docking.
If the device supports Modbus, can it be directly connected to the building control?
Not guaranteed. It is also necessary to check the interface form, site address, register definition, data type and scaling method, and confirm through joint debugging.
What support can Aili Industries provide?
The device side points, signal types and communication interfaces can be sorted out based on the project control requirements. The specific point list needs to be confirmed based on the agreement and on-site conditions.
Check items |
Confirm key points |
Check items |
Confirm key points |
|---|---|---|---|
Basic properties |
Name, number, type, unit and range |
Control properties |
Read and write, valid conditions and command priority |
Exception properties |
Alarm, communication interruption and power outage recovery |
Communication parameters |
Addresses, Registers, Scaling and Byte Order |
Joint debugging and verification |
Check values and real actions point by point |
Version management |
Point table changes and synchronized update data |