A weak electric information system rapid integration debugging method

Abstract

The application discloses a weak current informatization system rapid integration and debugging method, and relates to the technical field of weak current integration and debugging. The method comprises the following steps: topological scanning is performed on each weak current electronic system to be integrated to obtain device physical addresses and protocol characteristic codes, and a space location code is given to the space according to a building space partition coding rule to generate a device original list; the device original protocol characteristic codes are compared with a multi-protocol fingerprint library to automatically identify protocol types and map the protocol types into standardized virtual device objects; and the nodes that have been adjusted and connected are written into an integrated operation database to generate a visual topological view and a debugging acceptance document. The application eliminates a large amount of manual protocol configuration and data point mapping work, automatically generates linkage presets, has hierarchical self-diagnosis and structured archiving functions, significantly shortens the weak current informatization system integration and debugging period, and improves the debugging quality and result traceability.

Description

Technical Field

[0001] This invention relates to the field of low-voltage information system integration and engineering debugging technology, and in particular to a rapid integration and debugging method for low-voltage information systems. Background Technology

[0002] In the construction of low-voltage information systems for modern intelligent buildings and large parks, it is typically necessary to integrate various low-voltage electronic systems from different manufacturers, using different communication protocols and data formats—such as video surveillance, intrusion detection alarms, access control, HVAC building automation, parking management, public area background music broadcasting, and multimedia information dissemination—onto a unified management platform to achieve cross-system information exchange and coordinated control. Currently, in actual project implementation, the integration and commissioning of low-voltage information systems are generally carried out manually or semi-automatically: First, after each subsystem is powered on independently, the construction personnel check on-site whether the physical installation location of the equipment matches the planned location table. Then, they check the online status of each device by directly connecting a laptop to each device or by using the debugging software that comes with the subsystem. This process relies entirely on manual visual identification of device indicator lights and software interface feedback. For medium-sized or larger projects with hundreds or even thousands of front-end detectors, cameras, card readers, temperature and humidity sensors, and actuators, single-point confirmation is extremely time-consuming and prone to omissions or discrepancies between the location and the drawings.

[0003] Secondly, for heterogeneous communication protocols used by different manufacturers' equipment—such as ModbusRTU, BACnet MS / TP, KNX / EIB bus protocols on RS485 bus, BACnet / IP based on TCP / IP, OPC DA / UA, proprietary hexadecimal binary protocols, MQTT publish / subscribe protocols, etc.—integration and debugging personnel need to consult the communication protocol manuals or secondary development dynamic link library interface documents provided by each manufacturer, manually add devices one by one in the integration platform, select the protocol type, fill in the communication parameters (IP address, port number, slave address, baud rate, parity bit, register start address and length, etc.), and manually establish the correspondence between each register point or data object and the data point name of the upper-level management platform. This process is not only extremely labor-intensive, but also prone to address offset, incorrect byte order selection, or incorrect scaling factor settings due to different manufacturers using different register arrangement orders, byte order (endian and big-endian), engineering quantity units, and decimal scaling factors for the same physical quantity. This can lead to abnormal data display or false triggering of linkage during later operation.

[0004] Third, cross-subsystem linkage logic (such as releasing the access control of the corresponding fire compartment after a fire alarm is confirmed, linking the preset position of the spherical camera closest to the alarm point and popping up the real-time image on the video wall of the monitoring center after an intrusion alarm is triggered, and starting the exhaust fan of the corresponding smoke control zone when the CO concentration in the underground garage exceeds the standard) is currently mostly handled by the commissioning personnel in the logic configuration interface of the integration software by dragging and dropping the lines one by one and setting the trigger conditions and execution actions in a graphical or script-based manner. There is a lack of an automatic derivation mechanism based on the building space partition and equipment subordination relationship. When the number of subsystem devices is large and the linkage rules are numerous, not only is the configuration time-consuming, but it is also easy to miss necessary linkage pairings or set the trigger delay parameters incorrectly due to human negligence.

[0005] Fourth, existing debugging methods lack the ability to quantitatively assess the quality of communication links. They usually only use "whether the device responds" as the sole criterion. They cannot detect and warn of situations where there are a large number of retransmissions or CRC check errors in the link but occasional responses. Such hidden dangers often only become apparent after the system is officially put into use, under high concurrency access or increased network load, as intermittent disconnections or data refresh delays. This makes troubleshooting difficult and affects the user experience of the owners.

[0006] Fifth, debugging records are mostly stored as paper sign-in sheets or scattered electronic documents, without establishing a structured association with equipment space coding and test results. When the project is completed and delivered, it is difficult to directly convert them into point ledgers and fault history archives that can be used for reference during the operation and maintenance phase. It is also not conducive to quickly locating existing equipment during later expansion and renovation.

[0007] The aforementioned existing practices result in a lengthy cycle from hardware installation to full system integration, commissioning, and acceptance of low-voltage information systems, typically accounting for 30% to 50% of the entire low-voltage engineering project. Furthermore, these practices heavily rely on a small number of experienced integration and commissioning engineers working on-site, leading to high labor costs, high error rates, and cumbersome acceptance documentation. This has become a prominent bottleneck restricting the efficiency and quality of low-voltage information system project delivery. Summary of the Invention

[0008] In view of this, the present invention provides a rapid integration and debugging method for a low-voltage information system, so as to solve or alleviate one of the technical problems existing in the prior art, and at least provide a beneficial option.

[0009] The technical solution of this invention is implemented as follows: A method for rapid integration and debugging of a low-voltage information system, comprising the following steps: Step A: Perform a topology scan on each subsystem of the low-voltage information system to be integrated and debugged, obtain the physical address of each subsystem's equipment, communication port identifier and native protocol feature code, and assign spatial location codes to each subsystem's equipment according to the preset building space zoning coding rules, generating an original list of equipment with spatial location attributes. Step B: Based on the original list of devices, extract the native protocol feature codes of each subsystem device and compare them with the protocol fingerprints registered in the pre-set multi-protocol fingerprint database. When the matching degree reaches the preset threshold, automatically identify the communication protocol type of the device, and map the device data points of different protocol types to standardized virtual device objects and standardized data points according to a unified intermediate data exchange model to generate an integrated debugging intermediate model. Step C: Based on the spatial location code and subsystem category of each virtual device object in the integrated debugging intermediate model, call the pre-stored subsystem logical association rule table, automatically establish a cross-subsystem linkage logic preset framework, and group and sort the virtual device objects according to debugging priority to generate a preliminary debugging task queue. Step D: Following the order of the preliminary debugging task queue, send link detection commands to each virtual device object and receive return status messages. Determine the connectivity of the device link and the correctness of data interaction based on the return status messages. Start a hierarchical self-diagnosis program for virtual device objects with communication abnormalities and automatically retest after diagnosis. Mark virtual device objects with normal links and correct data point verification as successfully debugged nodes. Record fault characteristic codes and suggested handling strategies for nodes that fail the test, and form a debugging result report. Step E: Write the standardized virtual device objects and their linkage logic preset frameworks corresponding to all the nodes that have been successfully debugged into the integrated operation database, and simultaneously generate a visual system integration topology view and debugging and acceptance record document.

[0010] Preferably, the specific process of performing a topology scan on each subsystem of the low-voltage information system to be integrated and debugged in step A includes: By broadcasting probe packets, we can traverse the ports of each access switch to obtain the binding relationship between the Media Access Control address and the Internet Protocol address. At the same time, we can read the manufacturer identification code and default service port number of the device connected to each port and combine the obtained information into the device physical fingerprint. The spatial location coding adopts a five-level coding structure of "building number - floor number - room number - installation orientation code - equipment serial number". Equipment with the same subsystem category in the same physical area is assigned to the same scanning batch, and the order of scanning batches is arranged in reverse order according to the completion time of regional construction.

[0011] Preferably, the multi-protocol fingerprint database in step B stores the characteristic start byte sequences, register address distribution patterns, and default slave address ranges of RS485 Modbus, BACnet, KNX, OPC UA, MQTT, and TCP / IP custom binary protocols. The comparison and matching process involves first extracting the starting byte sequence of the first frame message returned by the device and calculating the Hamming distance between it and the characteristic starting byte sequences of various protocols in the multi-protocol fingerprint database. Then, it verifies whether the register address distribution conforms to the specification of a certain protocol. If both verifications pass, the device is classified into the corresponding protocol type. The standardized virtual device object includes a globally unique identifier for the device, a spatial location code, a protocol type label, a raw data point address mapping table, and the converted standardized data point name and data type definition.

[0012] Preferably, the pre-stored subsystem logical association rule table in step C contains the following association constraint information: The video surveillance subsystem and the intrusion alarm subsystem define a mapping relationship for alarm-triggered video linkage; the access control subsystem and the fire alarm subsystem define a mapping relationship for access control release after fire confirmation; the building automation subsystem and the environmental monitoring subsystem define a mapping relationship for the start and stop of air conditioning units when temperature and humidity exceed limits; and the parking management subsystem and the video surveillance subsystem define a mapping relationship for license plate recognition-triggered camera capture. The grouping and sorting rules for the debugging priorities are as follows: The subsystems are first sorted by criticality level from highest to lowest as follows: fire alarm subsystem > security alarm subsystem > access control and smart card subsystem > building automation subsystem > information dissemination subsystem > background music subsystem. Within the same subsystem, they are sorted by spatial location code from smallest to largest.

[0013] Preferably, the specific process of sending link probe commands to each virtual device object and receiving return status messages in step D includes: For TCP / IP devices, send ICMP echo requests and application layer status query commands and wait for a response within a first preset time period; for serial bus devices, send read-only register query frames according to the identified protocol format and wait for a response frame within a second preset time period; for passive contacts or switch quantity acquisition points, send analog quantity toggle test commands and read back the status value through the associated input module. The hierarchical self-diagnostic program includes: Level 1 checking physical link connectivity and switch port status; Level 2 checking the consistency of communication parameter configuration with the recommended default values ​​of the multi-protocol fingerprint database and providing parameter correction suggestions; and Level 3 capturing communication packets for integrity verification and CRC error statistics and marking suspected interference network segments.

[0014] Preferably, step D, which involves recording fault signature codes and suggested handling strategies for nodes that fail the test, specifically includes: Fault characteristic codes are defined as follows: F01 represents a physical link disconnection, F02 represents an IP address conflict or subnet mask error, F03 represents a mismatch in communication baud rate or parity bit configuration, F04 represents the device not returning the expected register value or the data point exceeding the reasonable range, and F05 represents a protocol type identification error that needs to be manually specified. The suggested handling strategies for each fault characteristic code are written in text form in the debugging result report, which includes the cable number to be checked, the suggested range of network parameter values ​​to be modified, and the recommended manual protocol specified operation path.

[0015] Preferably, the specific process of simultaneously generating a visualized system integration topology view and debugging and acceptance record document in step E includes: A plan view is generated by overlaying spatial location codes of each calibrated node with the building plan partition as the base map. A logical linkage topology is generated with the subsystem as the cluster center and the relationships defined in the linkage logic preset framework as the connection. A debugging progress Gantt chart is generated with the debugging task queue as the horizontal axis and the test results PASS / FAIL of each node as the vertical axis. The commissioning and acceptance record document is exported as an electronic spreadsheet file by subsystem, containing equipment name, spatial location code, physical address, protocol type, standardized data point mapping table, test results, fault records and retest results, and automatically appends the timestamps of commissioning start time and end time and the commissioning operator identifier.

[0016] Preferably, a parameter batch injection step is further included between step B and step C: Based on the protocol type and manufacturer information of each virtual device object in the integrated debugging intermediate model, the recommended communication parameter group, data point description table and engineering quantity conversion formula corresponding to the model or similar type of device are retrieved from the preset device template library. The recommended communication parameter group is written into the configuration item of the corresponding virtual device object in batches, and the engineering quantity conversion formula is bound to the standardized data point for linear transformation or nonlinear table lookup conversion when the data is used in the subsequent data presentation. The device template library supports importing extensions in Excel format and indexing by manufacturer and device model.

[0017] Preferably, a real-time alarm push sub-step is executed in parallel during step D: When a virtual device object fails to receive a valid response frame after three consecutive probes, the spatial location code, device type description, and fault feature code of the node are immediately encapsulated into an instant alarm message and pushed to the on-site debugging terminal and remote monitoring platform via WebSocket. At the same time, the node is moved to the end of the current round queue in the debugging task queue and highlighted in red. When the proportion of faulty nodes in the same subnet exceeds a preset percentage, the detection of subsequent nodes in that subnet will be suspended and a prompt will be made to check the status of the subnet gateway and the cascaded ports of the upstream switch.

[0018] Preferably, the method further includes a backtracking verification step after step E is completed: At preset intervals, sampling and revisiting are conducted on all the working nodes that have been written into the integrated operation database. The revisiting includes link round-trip delay measurement, real-time refresh rate verification of key data, and linkage logic trigger simulation test. If any working node is found to have deteriorated into an abnormal state during the revisit, the node is automatically marked and a supplementary debugging process is triggered. At the same time, the revisit time, revisit results, and abnormal situations are recorded in the debugging log for later maintenance and traceability.

[0019] The embodiments of the present invention have the following advantages due to the adoption of the above technical solutions: First, by combining topology scanning with spatial location coding, an original list of equipment with spatial attributes is generated, so that all subsequent commissioning actions can be traced back to specific building zones and installation locations. This solves the problems of disconnect between the location and the actual site location in traditional commissioning and the inability to quickly match the drawings during acceptance. The five-level spatial coding structure is compatible with buildings and parks of different sizes and supports subsequent operation and maintenance GIS / BIM integration.

[0020] Secondly, a multi-protocol fingerprint database is introduced to compare and match protocol feature codes to automatically identify the communication protocol type of the device and complete the standardized mapping of heterogeneous data points to a unified intermediate model. This eliminates the need for debugging personnel to manually refer to the protocol manuals of various manufacturers to add devices one by one and manually establish the correspondence between data points. The manual input and mapping operation of each device, which used to take an average of three to five minutes, is compressed into millisecond-level automatic matching. For projects with thousands of points or more, this can save more than 80% of the protocol configuration time and eliminate common errors such as manually selecting the wrong protocol type or filling in the wrong register address.

[0021] Third, the pre-stored subsystem logical association rule table automatically generates a cross-subsystem linkage logic preset framework based on the principle of co-location of building space and the coupling relationship of subsystem functions. Debugging personnel only need to confirm or make local adjustments to the automatically generated linkage relationship. There is no need to drag and drop the connection in the configuration interface from scratch, which reduces the rate of omission in linkage configuration and keeps the linkage logic consistent with the spatial partition. It is especially suitable for scenarios of repeated layout of standard floors or batch copying of the same type of functional area.

[0022] Fourth, during the detection and testing phase, link detection commands are issued in priority group order and combined with a three-level hierarchical self-diagnosis program. For abnormal communication nodes, physical links, parameter configuration consistency and message integrity are checked in turn. Clear fault characteristic codes and handling suggestions are output, so that on-site personnel can quickly determine whether it is a cable break, address conflict, baud rate mismatch or equipment replacement. The fault location time is shortened from an average of tens of minutes to within a few minutes, and the self-diagnosis process does not rely on the personal experience of the debugging personnel.

[0023] Fifth, the linkage between real-time alarm push and the red highlighting of the debugging queue enables timely detection of upstream network equipment failures during large-scale communication failures, rather than wasting time on numerous single-point timeout reports, thus improving the targeted nature of on-site troubleshooting.

[0024] Sixth, the commissioning results are stored in structured electronic records according to subsystems and spatial locations, and a planar layout view, logical linkage topology diagram and commissioning progress Gantt chart are generated simultaneously. These can be directly delivered to the owner as part of the as-built documentation, or imported into the operation and maintenance management system as an initial asset ledger and historical test baseline. Subsequent backtracking and review steps can periodically verify the stability of the commissioned nodes and trigger supplementary commissioning when they deteriorate, forming a closed-loop data system for the entire lifecycle of commissioning, acceptance and operation and maintenance.

[0025] Seventh, the parameter batch injection step enables the one-time configuration and multiple reuse of communication parameters and engineering quantity conversion formulas for similar devices through the device template library. It supports template extension import, adapts to the replacement of different brands of equipment or the addition of new models, and avoids repeated input.

[0026] In summary, this invention forms a complete process from device discovery, protocol adaptation, linkage pre-configuration, automatic detection and diagnosis to result archiving. The cooperation between each link produces synergistic effects, which improves the overall efficiency of low-voltage information system integration and debugging by more than three times compared with the traditional manual method. The debugging coverage rate can reach 100%, and the human configuration error rate is close to zero.

[0027] The above overview is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features of the invention will become readily apparent from the accompanying drawings and the following detailed description. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 Main flowchart (A→E).

[0030] Figure 2 Flowchart for automatic protocol recognition.

[0031] Figure 3 : Three-level self-diagnosis diagram. Detailed Implementation

[0032] In the following description, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the spirit or scope of the invention. Therefore, the drawings and description are considered to be exemplary in nature and not restrictive.

[0033] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0034] Example 1: Integration and Commissioning of Low-Voltage System for a Single-Building Integrated Office Building

[0035] This embodiment uses the rapid integration and commissioning of a low-voltage information system in a 28-story above-ground and 2-story underground office building as an example. The building contains the following subsystems: a video surveillance subsystem (360 network cameras distributed in elevator lobbies, entrances / exits, and the underground parking garage on each floor); an intrusion alarm subsystem (240 dual-technology detectors and 60 emergency buttons); an access control and card system (120 card readers and electric locks); a building automation subsystem (420 monitoring and control points including temperature and humidity sensors, differential pressure switches, and electric regulating valves); a background music subsystem (200 ceiling speakers divided into 18 broadcast zones); and an information dissemination subsystem (24 LCD all-in-one machines distributed in the ground floor lobby and elevator lobbies on each floor). The construction team has completed wiring, equipment installation, and power supply to individual units.

[0036] Step A: Topology Scan and Spatial Location Encoding Assignment

[0037] The debugging host sends LLDP and ARP probe packets to each access layer switch through the access core switch, traverses all active MAC address and IP address binding relationships, and simultaneously polls the RS485 bus through the serial port server to obtain the bus device response list.

[0038] After roughly pre-associating the scanning results with the location table provided by the design institute according to the equipment serial number, each device is assigned a spatial location code according to the five-level coding rule of "building number - floor number - room number - installation orientation code - equipment serial number". In this embodiment, the building number is uniformly recorded as B01, the floor number ranges from B2, B1, F1 to F28, the room number is the actual room number or public area code such as EH (elevator hall), LB (lobby), UG (underground parking garage A area), etc., the installation orientation code is N (north), S (south), E (east), W (west), C (center), and the equipment serial number is the sequential number of the same type of equipment in the same coding location.

[0039] The table below shows example records of spatial location codes assigned to some of the device scanning results in Example 1: Table 1-1 Mapping Table of Original Equipment Scanning Information and Spatial Location Code (Excerpt)

[0040] The scanning batches are sorted by floor from high to low, i.e., first scan F28, then F27, ..., F1, then B1, then B2. Within the same floor, the order is fire protection > security > access control > building control > broadcasting > information release, generating a total of 1,204 original equipment lists.

[0041] Step B: Automatic Protocol Identification and Standardized Virtual Device Object Mapping

[0042] Extract the first frame returned by each device and perform protocol fingerprint matching. Some protocol fingerprint definitions in the multi-protocol fingerprint database are shown in the table below: Table 1-2 Multi-protocol fingerprint database protocol feature matching rules (excerpt)

[0043] After a successful match, a standardized virtual device object (VO) is created for the device. Some mapping results are shown in the table below: Table 1-3 Standardized Virtual Device Object Mapping Results (Excerpt)

[0044] Step C: Automatic generation of the linkage logic preset framework and establishment of the debugging task queue

[0045] The subsystem logical association rule table is invoked; some rules are shown in the table below: Table 1-4 Subsystem Logical Association Rules (Excerpt)

[0046] Based on these rules and the spatial location codes of VOs, a preset linkage framework is automatically established. All 1204 linkage records are not detailed here. The debug task queue is sorted by subsystem criticality level and then arranged within groups in lexicographical order of spatial location codes. A partial excerpt of the queues is shown below. Table 1-5 Excerpt from the preliminary debugging task queue (first ten items)

[0047] Step D: Queue Probe and Hierarchical Self-Diagnosis

[0048] The detection commands were issued sequentially, and the returned results were recorded. In this example, three building automation temperature sensors (VO-BC-031, VO-BC-058, and VO-BC-092) were found to be unresponsive. A tiered self-diagnosis was initiated: Level 1 check showed "Link Down" on the switch port, indicating a loose wiring terminal. The installation personnel were notified to tighten it, and the test passed. Two network cameras (VO-CCTV-088 and VO-CCTV-155) were pinged successfully, but ONVIF GetDeviceInfo returned authentication failure. The diagnosis was that the factory default password had not been changed and the integrated platform was using incorrect credentials. After updating the credentials, the test passed. The remaining nodes passed on the first attempt. The fault records are shown in the table below: Table 1-6 Fault Record Table for Debugging Abnormal Nodes

[0049] Final statistics: Total points: 1204, 1179 passed on the first attempt, and all passed after processing, with a pass rate of 100%.

[0050] Step E: Write to the integrated runtime database and generate documents

[0051] All successfully debugged VOs and linked preset frameworks were written into the integration platform's SQLite runtime library, generating a debug acceptance record Excel file (fields are the same as Tables 1-6, extended to a total of 1204 records), a PNG view of the planar layout, and an SVG of the linked topology. The debug start and end time was recorded as 08:30 to 11:45, with a total duration of 3 hours and 15 minutes.

[0052] Example 2: Phased integration and commissioning of the low-voltage electrical systems in multiple R&D buildings within the industrial park.

[0053] This embodiment uses the rapid integration and commissioning of the low-voltage information system in a high-tech industrial park comprising six independent R&D workshops (numbered P01 to P06) ranging from three to five stories as an example to illustrate the application of this invention in a phased construction and batch delivery scenario. Each workshop is equipped with a video surveillance system (approximately 40 to 60 IPCs per building), an access control card system (approximately 20 to 30 sets per building), a building automation system (approximately 80 to 150 BA points per building, mainly monitoring the temperature, humidity, pressure differential, and chiller unit operating status in the cleanroom), and a fire alarm subsystem (each building is independent but needs to upload status to the central management platform). The park's central control center is equipped with an integrated management platform, and each building is connected via a fiber optic ring network.

[0054] Since the completion times of each building are different, the method described in this invention is used to execute steps A to E in batches according to each building, and finally the entire park's linkage logic is integrated.

[0055] Batch scanning and spatial coding

[0056] A topological scan was performed on each building, with building numbers P01 to P06. The remaining coding rules followed the same as in Example 1. The table below shows the partial scan coding results for building P03: Table 2-1 Equipment Scanning and Spatial Coding Mapping Table for Building P03 (Excerpt)

[0057] Batch injection of parameters

[0058] The equipment template library has pre-loaded templates for temperature and humidity transmitters from mainstream BA manufacturer W, card readers from mainstream access control brand K, and network cameras from mainstream IPC brand H. Some template contents are shown in the table below: Table 2-2 Equipment Template Library Parameter Injection Template Table (Excerpt)

[0059] During batch injection, the communication parameters and data point descriptions are automatically filled into the VO that matches the template, reducing manual intervention.

[0060] Cross-building linkage rules and park-wide integration

[0061] In addition to the intra-building linkage, an additional park-level linkage rule is defined: If any building confirms a fire alarm → the central monitoring platform displays four selectable screens (panoramic view of the building's ground floor lobby + two evacuation stairwells + local view from the fire control room) → the park's public address system broadcasts an evacuation announcement → the access control system releases all controlled doors in that building. This rule is established once and for all six buildings after their individual debugging is completed, by re-running the linkage framework generation steps across the entire park's VO (Virtual Object) set.

[0062] The following table is a summary excerpt of the park-wide linkage rules: Table 2-3 Summary Table of Park-Level Collaboration Rules (Excerpt)

[0063] Summary of debugging results

[0064] The results of the phased commissioning of the six buildings and the final integrated commissioning of the entire park are summarized in the table below: Table 2-4 Summary Table of Debugging Statistics for Each Building in the Park

[0065] All additional tests and linkage triggers for the entire park were successful, generating a system integration topology view for the entire park and a debugging and acceptance document package categorized by building.

[0066] Example 3: Rapid Re-commissioning of Localized Incremental Levels in the Upgrade and Retrofit of Existing Building Low-Voltage Electrical Systems

[0067] This embodiment illustrates how, in the upgrading and renovation of existing building low-voltage information systems—that is, retaining some old subsystems, adding or replacing some equipment, and expanding new linkage functions—the present invention achieves incremental re-debugging by performing retrospective verification on historically debugged nodes in the existing integrated operation database and performing complete and rapid integrated debugging on newly added nodes.

[0068] The scenario is set as follows: the comprehensive office building described in Example 1 is being renovated after three years of use. The original building automation system is retained, but 32 new sensors (Modbus RTU) are added to the CO / NOx concentration monitoring points in the underground parking garage on the second basement level. Eighteen new sets of facial recognition access control terminals (private TCP protocol, supporting HTTP JSON API) are added. The original independently operating community perimeter alarm is connected to the integrated platform and new rules are generated to link with the original video surveillance.

[0069] Execution of retrospective review steps

[0070] A sampling revisit probe was performed on the original 1,204 VO nodes already written into the integrated operation database in Example 1 (sampling ratio based on subsystem criticality levels: 100% for anti-alarm, 100% for security alarm, 50% for access control, 30% for building control, and 20% for the rest). The revisit content included link round-trip latency (Ping or serial port query timeout statistics), real-time refresh rate of key point data (standard deviation of the time interval between ten consecutive samplings), and linkage simulation trigger test (only non-interference soft triggers). The revisit record is shown in the table below: Table 3-1 Existing Node Backtracking and Verification Record Table (Excerpt)

[0071] During the follow-up visit, it was found that VO-BC-045 (B01-F12-1201-C-03) timed out without returning, indicating that additional debugging was needed. All other sampling nodes were normal.

[0072] Quick integration and debugging of new nodes

[0073] Perform complete steps A through E (scanning, protocol identification, mapping, linkage framework generation, detection, and data archiving) on ​​the 32 newly added air quality sensors and 18 sets of facial recognition access control terminals in the underground parking garage. An example of the scanning code for the new nodes is shown in the table below: Table 3-2 Excerpt of the Scanning Code Table for Air Quality Sensors in Newly Added Underground Parking Garages

[0074] Table 3-3 Newly Added Facial Recognition Access Control Terminal Scanning Code Table (Excerpt)

[0075] The newly added sensor Modbus register mappings are: 40001 = CO concentration (ppm×10), 40002 = NOx concentration (ppm×10); the newly added access control terminal standardized data points are: DI_FaceMatch (Boolean), DI_CardPresent (Boolean), DO_RelayRelease (Boolean), AI_PersonCount (Integer).

[0076] Extended linkage rules: If the average CO concentration at any monitoring point in the underground parking garage exceeds 30 ppm for 5 consecutive minutes, the exhaust fan of the corresponding fire compartment will be activated (if there are existing BA DO points). A voice prompt, "Please minimize your stay," will be broadcast in the local broadcast zone. If the perimeter alarm is triggered, the existing PTZ camera preset position closest to the alarm zone and the newly added perimeter wall-mounted camera will capture the image. The alarm image will be pushed to the security app. Some of the extended linkage rules are shown in the table below: Table 3-4 Upgrade and Extension Linkage Rules Table

[0077] All fifty newly added nodes passed the initial testing. The integrated operating database version number was updated along with the existing nodes. An incremental debugging report, including Tables 3-2 to 3-4 and the full test records for the new nodes, was added to the original debugging and acceptance documentation. Retrospective review revealed an abnormal node, VO-BC-045. On-site inspection revealed a loose crimped wire on the back of the floor distribution frame. After re-crimping, the test passed, and this was recorded in the supplementary maintenance log.

[0078] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various variations or substitutions within the technical scope disclosed in the present invention, and these should all be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A rapid integration and debugging method for a low-voltage information system, characterized in that, Includes the following steps: Step A: Perform a topology scan on each subsystem of the low-voltage information system to be integrated and debugged, obtain the physical address of each subsystem's equipment, communication port identifier and native protocol feature code, and assign spatial location codes to each subsystem's equipment according to the preset building space zoning coding rules, generating an original list of equipment with spatial location attributes. Step B: Based on the original list of devices, extract the native protocol feature codes of each subsystem device and compare them with the protocol fingerprints registered in the pre-set multi-protocol fingerprint database. When the matching degree reaches the preset threshold, automatically identify the communication protocol type of the device, and map the device data points of different protocol types to standardized virtual device objects and standardized data points according to a unified intermediate data exchange model to generate an integrated debugging intermediate model. Step C: Based on the spatial location code and subsystem category of each virtual device object in the integrated debugging intermediate model, call the pre-stored subsystem logical association rule table, automatically establish a cross-subsystem linkage logic preset framework, and group and sort the virtual device objects according to debugging priority to generate a preliminary debugging task queue. Step D: Following the order of the preliminary debugging task queue, send link detection commands to each virtual device object and receive return status messages. Determine the connectivity of the device link and the correctness of data interaction based on the return status messages. Start a hierarchical self-diagnosis program for virtual device objects with communication abnormalities and automatically retest after diagnosis. Mark virtual device objects with normal links and correct data point verification as successfully debugged nodes. Record fault characteristic codes and suggested handling strategies for nodes that fail the test, and form a debugging result report. Step E: Write the standardized virtual device objects and their linkage logic preset frameworks corresponding to all the nodes that have been successfully debugged into the integrated operation database, and simultaneously generate a visual system integration topology view and debugging and acceptance record document.

2. The rapid integration and debugging method for a low-voltage information system according to claim 1, characterized in that, The specific process of performing a topology scan on each subsystem of the low-voltage information system to be integrated and debugged in step A includes: By broadcasting probe packets, we can traverse the ports of each access switch to obtain the binding relationship between the Media Access Control address and the Internet Protocol address. At the same time, we can read the manufacturer identification code and default service port number of the device connected to each port and combine the obtained information into the device physical fingerprint. The spatial location coding adopts a five-level coding structure of "building number - floor number - room number - installation orientation code - equipment serial number". Equipment with the same subsystem category in the same physical area is assigned to the same scanning batch, and the order of scanning batches is arranged in reverse order according to the completion time of regional construction.

3. The rapid integration and debugging method for a low-voltage information system according to claim 1, characterized in that, The multi-protocol fingerprint database in step B stores the characteristic start byte sequences, register address distribution patterns, and default slave address ranges of RS485 Modbus, BACnet, KNX, OPC UA, MQTT, and TCP / IP custom binary protocols. The comparison and matching process involves first extracting the starting byte sequence of the first frame message returned by the device and calculating the Hamming distance between it and the characteristic starting byte sequences of various protocols in the multi-protocol fingerprint database. Then, it verifies whether the register address distribution conforms to the specification of a certain protocol. If both verifications pass, the device is classified into the corresponding protocol type. The standardized virtual device object includes a globally unique identifier for the device, a spatial location code, a protocol type label, a raw data point address mapping table, and the converted standardized data point name and data type definition.

4. The rapid integration and debugging method for a low-voltage information system according to claim 1, characterized in that, The pre-stored subsystem logical association rule table in step C contains the following association constraint information: The video surveillance subsystem and the intrusion alarm subsystem define a mapping relationship for alarm-triggered video linkage; the access control subsystem and the fire alarm subsystem define a mapping relationship for access control release after fire confirmation; the building automation subsystem and the environmental monitoring subsystem define a mapping relationship for the start and stop of air conditioning units when temperature and humidity exceed limits; and the parking management subsystem and the video surveillance subsystem define a mapping relationship for license plate recognition-triggered camera capture. The grouping and sorting rules for the debugging priorities are as follows: The subsystems are first sorted by criticality level from highest to lowest as follows: fire alarm subsystem > security alarm subsystem > access control and smart card subsystem > building automation subsystem > information dissemination subsystem > background music subsystem. Within the same subsystem, they are sorted by spatial location code from smallest to largest.

5. The rapid integration and debugging method for a low-voltage information system according to claim 1, characterized in that, The specific process of sending link probe commands to each virtual device object and receiving return status messages in step D includes: For TCP / IP devices, send ICMP echo requests and application layer status query commands and wait for a response within a first preset time period; for serial bus devices, send read-only register query frames according to the identified protocol format and wait for a response frame within a second preset time period; for passive contacts or switch quantity acquisition points, send analog quantity toggle test commands and read back the status value through the associated input module. The hierarchical self-diagnostic program includes: Level 1 checking physical link connectivity and switch port status; Level 2 checking the consistency of communication parameter configuration with the recommended default values ​​of the multi-protocol fingerprint database and providing parameter correction suggestions; and Level 3 capturing communication packets for integrity verification and CRC error statistics and marking suspected interference network segments.

6. The rapid integration and debugging method for a low-voltage information system according to claim 5, characterized in that, Step D, which involves recording fault signature codes and suggested handling strategies for nodes that fail the test, specifically includes: Fault characteristic codes are defined as follows: F01 represents a physical link disconnection, F02 represents an IP address conflict or subnet mask error, F03 represents a mismatch in communication baud rate or parity bit configuration, F04 represents the device not returning the expected register value or the data point exceeding the reasonable range, and F05 represents a protocol type identification error that needs to be manually specified. The suggested handling strategies for each fault characteristic code are written in text form in the debugging result report, which includes the cable number to be checked, the suggested range of network parameter values ​​to be modified, and the recommended manual protocol specified operation path.

7. The rapid integration and debugging method for a low-voltage information system according to claim 1, characterized in that, The specific process of synchronously generating a visualized system integration topology view and debugging and acceptance record documents in step E includes: A plan view is generated by overlaying spatial location codes of each calibrated node with the building plan partition as the base map. A logical linkage topology is generated with the subsystem as the cluster center and the relationships defined in the linkage logic preset framework as the connection. A debugging progress Gantt chart is generated with the debugging task queue as the horizontal axis and the test results PASS / FAIL of each node as the vertical axis. The commissioning and acceptance record document is exported as an electronic spreadsheet file by subsystem, containing equipment name, spatial location code, physical address, protocol type, standardized data point mapping table, test results, fault records and retest results, and automatically appends the timestamps of commissioning start time and end time and the commissioning operator identifier.

8. The rapid integration and debugging method for a low-voltage information system according to claim 1, characterized in that, Between step B and step C, there is also a parameter batch injection step: Based on the protocol type and manufacturer information of each virtual device object in the integrated debugging intermediate model, the recommended communication parameter group, data point description table and engineering quantity conversion formula corresponding to the model or similar type of device are retrieved from the preset device template library. The recommended communication parameter group is written into the configuration item of the corresponding virtual device object in batches, and the engineering quantity conversion formula is bound to the standardized data point for linear transformation or nonlinear table lookup conversion when the data is used in the subsequent data presentation. The device template library supports importing extensions in Excel format and indexing by manufacturer and device model.

9. The rapid integration and debugging method for a low-voltage information system according to claim 1, characterized in that, During the execution of step D, a real-time alarm push sub-step is executed in parallel: When a virtual device object fails to receive a valid response frame after three consecutive probes, the spatial location code, device type description, and fault feature code of the node are immediately encapsulated into an instant alarm message and pushed to the on-site debugging terminal and remote monitoring platform via WebSocket. At the same time, the node is moved to the end of the current round queue in the debugging task queue and highlighted in red. When the proportion of faulty nodes in the same subnet exceeds a preset percentage, the detection of subsequent nodes in that subnet will be suspended and a prompt will be made to check the status of the subnet gateway and the cascaded ports of the upstream switch.

10. The rapid integration and debugging method for a low-voltage information system according to claim 1, characterized in that, The method further includes a backtracking verification step after step E is completed: At preset intervals, sampling and revisiting are conducted on all the working nodes that have been written into the integrated operation database. The revisiting includes link round-trip delay measurement, real-time refresh rate verification of key data, and linkage logic trigger simulation test. If any working node is found to have deteriorated into an abnormal state during the revisit, the node is automatically marked and a supplementary debugging process is triggered. At the same time, the revisit time, revisit results, and abnormal situations are recorded in the debugging log for later maintenance and traceability.

Images