A visual perception-based stage lamp intelligent configuration system

Abstract

This invention discloses a visual perception-based intelligent configuration system for stage lighting fixtures, belonging to the field of stage lighting control technology. The invention includes: a visual perception unit for establishing a spatial location mapping of the lighting fixtures; an RDM communication interface for reading the unique UID of each lighting fixture; a location-UID fusion module for automatically associating location identifiers with UIDs; a pre-programmed configuration interface for obtaining preset configuration parameters for each location; a batch configuration instruction generation module for generating configuration instructions containing DMX addresses and channel modes; and an RDM batch transmission module for sending instructions in batches to the corresponding lighting fixtures. This invention achieves full automation of the entire process, from automatic lighting fixture location and UID reading to batch configuration transmission, reducing the traditional hours of manual configuration per fixture to minutes, completely solving the industry pain points of low efficiency and error-prone on-site stage lighting configuration. Furthermore, this invention can generate on-site lighting fixture layout information even in scenarios without pre-programming, assisting lighting technicians in manual configuration and subsequent programming.

Description

Technical Field

[0002] This invention relates to the field of stage lighting control technology, specifically to an intelligent system that combines visual perception and RDM communication technology to achieve automatic positioning, identification, and batch configuration of stage lighting fixtures.

[0003] This invention and another patent application filed by the applicant on the same day, "A Physical-Virtual Fusion Multi-View Perception System for Stage Lighting Control" (hereinafter referred to as "Patent 1"), constitute a collaborative relationship: Patent 1 provides underlying visual perception capabilities to obtain the precise spatial position of the lighting fixtures; based on this perception data, this invention combines the RDM protocol to realize automatic identification and batch configuration of the lighting fixtures, and the two together form a complete technical closed loop from "perception" to "configuration". Background Technology

[0004] In stage lighting systems, the correct configuration of each light fixture is fundamental to achieving the desired performance effect. Light fixture configuration mainly includes setting the DMX start address, selecting channel modes, and inputting individual characteristic parameters. Currently, light fixture configuration mainly faces the following technical limitations and industry pain points:

[0005] 1. Limitations of existing configuration methods

[0006] 1.1 Manual Configuration Method Currently, the most common configuration method is manual setup for each light fixture. Operators need to climb to the installation location and manually set the DMX address code via the fixture panel or DIP switch. For large-scale performances (such as concerts and television variety shows), where the number of lights can reach thousands, this method has the following problems:

[0007] Inefficient: A single performance requires hours or even an entire night to prepare;

[0008] High-risk operations: Personnel need to work at heights, which poses a high safety risk;

[0009] Error-prone: Manual input is prone to address conflicts, duplicates, or omissions;

[0010] Unable to handle touring: The process requires repetitive operations at each stop, resulting in a huge workload.

[0011] 1.2 RDM Unit-by-Unit Identification Method The RDM (Remote Device Management) protocol allows reading the luminaire's UID (Unique Identifier) ​​and setting parameters via a control line. The existing RDM configuration process is as follows:

[0012] The RDM controller sends an identification command, and a certain lamp responds (e.g., the light flashes).

[0013] Operators visually observe which light is flashing and manually record its physical location;

[0014] The operator searches for the pre-assigned address code for that location in the console or software;

[0015] The address code is sent to the lighting fixture via RDM;

[0016] Repeat the above steps until all lighting fixtures are configured.

[0017] While this method enables remote settings, it still has the following drawbacks:

[0018] Location verification still requires manual verification: "UID-location" mapping cannot be automatically established;

[0019] Operating each light individually is inefficient: hundreds of lights require repeating the identification-recording-sending process hundreds of times.

[0020] Relying on operator experience: When lights are densely arranged, it is difficult to accurately determine the position of flashing lights.

[0021] 1.3 Serial Automatic Encoding Method: Some existing technologies automatically assign address codes based on the physical serial connection order of the lamps. This method has the following limitations:

[0022] Dependent on physical connection order: Address allocation is bound to the connection order and cannot be customized according to pre-programmed design intent;

[0023] Not suitable for cluttered scenarios: Lights are randomly hung during transitions in a tour, making it impossible to maintain a fixed order;

[0024] Unable to interface with 3D pre-programmed models: The assigned address code may not match the address code preset by the designer in the software.

[0025] 2. Differences in requirements across different application scenarios

[0026] There are two typical scenarios in stage lighting practice:

[0027] Scenario A: Scenario with pre-programmed models: In large-scale concerts, TV variety shows, tours and other scenarios, the lighting designer has completed the effect design in 3D software in advance. On-site, it is necessary to accurately match the actual lighting fixtures with the virtual lighting fixtures in the pre-programmed model and set them according to the preset configuration parameters of the model.

[0028] Scenario B: Scenario without pre-programmed models: In scenarios such as temporary performances, flash mobs, rental businesses, and creative exploration, no pre-programmed models are available. Lighting designers need to plan the lighting configuration from scratch and hope to obtain the layout information of the on-site lighting for subsequent programming.

[0029] 3. Summary of Technology Gaps

[0030] In summary, the following technological gaps currently exist in the field of stage lighting:

[0031] There is a lack of a system that can automatically establish the relationship between "lamp UID - physical location - pre-programmed configuration";

[0032] Existing RDM technology requires manual location verification and cannot achieve fully automated batch configuration;

[0033] Visual perception technology has not yet been applied to lighting configuration scenarios to achieve automatic location positioning and automatic identity association;

[0034] In scenarios without pre-programming, there is a lack of tools that can automatically generate on-site lighting layout information and assist in configuration.

[0035] This invention addresses the aforementioned technological gap.

[0036] 4. Existing Technology Basis Description

[0037] It should be noted that this invention uses RDM / UID as the basis for luminaire identification because the RDM (Remote Device Management) protocol has become an international standard in the stage lighting industry, and almost all professional luminaires support this protocol. The RDM protocol allows reading the unique UID of a luminaire and setting parameters via control lines, but its long-standing fundamental flaw is the need for manual location verification—that is, it cannot automatically establish a correspondence between the physical location of the luminaire and its UID. This invention combines visual perception technology with the RDM protocol, automatically creating a spatial location map of the luminaire through visual perception and automatically associating it with the UID read from the RDM, thereby completely solving the problem of manual verification in RDM technology and achieving truly fully automated batch configuration. The independent claims of this invention rely solely on the mature RDM / UID technology, ensuring the practicality and industry applicability of the technical solution. Summary of the Invention

[0038] I. Purpose of the Invention

[0039] This invention aims to provide a vision-based intelligent configuration system for stage lighting fixtures, achieving the following objectives:

[0040] Automatic location positioning: Automatically creates a site location map of the lighting fixtures through visual perception;

[0041] Automatic identification: Automatically reads the UID of each lamp via the RDM protocol;

[0042] Automatic mapping association: Automatically associates the lamp UID with its physical location;

[0043] Batch configuration sending: Send configuration parameters to each lamp in batches according to the pre-programmed model;

[0044] Layout information generation: In scenarios without pre-programming, generate on-site lighting layout information for subsequent use;

[0045] Full-process automation: reducing the time and effort required for manual configuration from several hours or even days to minutes.

[0046] II. Technical Solution

[0047] A stage lighting intelligent configuration system based on visual perception, comprising:

[0048] A visual perception unit is used to collect visual feature information of lighting fixtures in the stage space and establish a spatial position mapping map of the lighting fixtures. The spatial position mapping map includes at least the position identifier of each lighting fixture in the stage coordinate system or image coordinate system.

[0049] The RDM communication interface connects to the lighting control network and is used to read the unique UID of each lighting fixture and obtain a list of lighting fixtures via the RDM protocol.

[0050] The location-UID fusion module is connected to the visual perception unit and the RDM communication interface, and is used to associate the location identifier in the spatial location mapping map with the UID to establish a mapping relationship of {location identifier: UID}.

[0051] A pre-programmed configuration interface is used to obtain the preset lighting configuration parameters for each position identifier in a scenario with a pre-programmed model or a console database. The configuration parameters include at least the DMX start address.

[0052] A batch configuration instruction generation module is connected to the location-UID fusion module and the pre-programmed configuration interface. It is used to generate configuration instructions containing corresponding configuration parameters for each UID according to the mapping relationship in a scenario with a pre-programmed model.

[0053] The RDM batch sending module is connected to the batch configuration instruction generation module and is used to send the configuration instructions in batches to the lamps with corresponding UIDs via the RDM protocol.

[0054] III. Optional Enhancement Solutions

[0055] To further enhance system functionality, the present invention may also include the following optional features:

[0056] The layout information generation module, connected to the location-UID fusion module, is used to generate on-site lighting layout information based on the {location identifier: UID} mapping relationship in scenarios without a pre-programmed model, for lighting engineers to manually configure or program as a reference.

[0057] The individual feature compensation module is used to store the individual feature data of each lamp (such as motor hysteresis, response delay, etc.) and associate it with the UID. It is sent together in the configuration command to achieve precise control of "one lamp, one policy".

[0058] The lamp-by-lamp inspection module, connected to the visual perception unit, is used to control the lamps to light up sequentially and assist in establishing the association between position and UID through a timing method.

[0059] The manual configuration interface, connected to the layout information generation module, is used to manually set configuration parameters for selected lamps in scenarios without a pre-programmed model, and send them through the RDM batch sending module.

[0060] The configuration verification module is connected to the visual perception unit and is used to verify whether the lamp works normally according to the new configuration through visual perception after the configuration is sent, and to provide feedback on the configuration result.

[0061] IV. Beneficial Effects

[0062] Compared with the prior art, the present invention has the following beneficial effects:

[0063] Full-process automation: The traditional manual configuration of each machine, which used to take several hours, is shortened to an automated process of 10-15 minutes, improving efficiency by more than 90%.

[0064] No manual location verification is required: The location map is automatically created through visual perception, and the UID is automatically read through RDM to automatically complete the {location:UID} mapping, completely eliminating the manual verification process.

[0065] Seamless integration with pre-programmed designs: In scenarios with pre-programmed models, the preset configuration parameters for each position can be retrieved directly from the 3D pre-programmed model, ensuring that the on-site configuration is completely consistent with the design intent.

[0066] Batch configuration capability: Supports sending configuration parameters for hundreds of lamps in a single operation, far exceeding the efficiency of traditional one-by-one operation.

[0067] Configuration verification closed loop: Visual verification ensures that the configuration is executed correctly, forming a complete closed-loop control.

[0068] Compatible with the existing RDM ecosystem: Based on the standard RDM protocol, it can be directly applied to existing RDM-supporting lighting fixtures without additional hardware modifications.

[0069] Expanding application scenarios: In scenarios without pre-programmed models, it can generate on-site lighting layout information to assist lighting engineers in manual configuration and subsequent programming, thereby improving system applicability. Attached Figure Description

[0070] Figure 1: Schematic diagram of the overall system architecture of this invention. Explanation of markings in the diagram:

[0071] 101—Visual perception unit, used to collect visual feature information of lighting fixtures in the stage space and establish a spatial position mapping map of the lighting fixtures;

[0072] 102—RDM communication interface, connected to the lighting control network, used to read the unique UID of each lighting fixture and obtain the lighting fixture list via the RDM protocol;

[0073] 103——Location-UID fusion module, connected to the visual perception unit (101) and the RDM communication interface (102), is used to associate the location identifier in the spatial location mapping map with the UID and establish a mapping relationship of {location identifier: UID}.

[0074] 104 — Pre-programmed configuration interface, used to obtain the preset lighting configuration parameters for each position identifier in the 3D pre-programmed model or console database;

[0075] 105—Batch configuration instruction generation module, connected to the location-UID fusion module (103) and the pre-programmed configuration interface (104), is used to generate configuration instructions containing corresponding configuration parameters for each UID according to the mapping relationship;

[0076] 106—RDM batch transmission module, connected to batch configuration instruction generation module (105), used to send configuration instructions to the lamps with corresponding UIDs via RDM protocol;

[0077] 107 — Lighting fixtures, receive configuration commands and execute parameter settings;

[0078] 108—Configuration information verification module, connected to visual perception unit (101), is used to verify whether the lamp works normally according to the new configuration through visual perception after the configuration is sent, and to provide feedback on the configuration result.

[0079] In the diagram, solid arrows indicate the main data flow, while dashed arrows indicate the feedback path.

[0080] Figure 2 Visual-UID-address mapping principle diagram.

[0081] This diagram illustrates the process of establishing the core mapping relationship and its connection with batch configuration generation.

[0082] Explanation of markings in the diagram:

[0083] 101—Visual perception unit, which collects the position information of the lights in the stage space and outputs the three-dimensional coordinate data (x1, y1, z1), (x2, y2, z2), etc. of each light in the stage coordinate system;

[0084] 102—RDM communication interface, reads the unique UID of each lamp and outputs a list of lamp UIDs (UID1, UID2, etc.).

[0085] 103—Location-UID Fusion Module: Receives the location coordinate data and the UID list data, and uses an intelligent matching algorithm to associate the spatial coordinates of the lamp with its UID to establish a complete mapping table;

[0086] 104 — Pre-programmed configuration interface, obtains the preset lighting configuration parameters for each position identifier in the 3D pre-programmed model or console database, the configuration parameters including at least the DMX start address;

[0087] 105—Batch configuration instruction generation module, receives the {location coordinates: UID} mapping relationship and the preset configuration parameters, merges the two, matches the preset configuration parameters of the location identifier according to the UID corresponding to each spatial coordinate, and generates a configuration instruction containing the corresponding configuration parameters for each UID, forming a configuration instruction set.

[0088] The arrows in the diagram indicate the direction of data flow:

[0089] The position coordinate data output by the visual perception unit (101) flows to the position-UID fusion module (103).

[0090] The UID list data output by the RDM communication interface (102) flows to the location-UID fusion module (103).

[0091] The {location coordinates: UID} mapping relationship output by the location-UID fusion module (103) flows to the batch configuration instruction generation module (105).

[0092] The preset configuration parameters output by the preprogrammed configuration interface (104) flow to the batch configuration instruction generation module (105).

[0093] The configuration instruction set output by the batch configuration instruction generation module (105) is used by downstream modules.

[0094] Figure 3 : Schematic diagram of the process for lamp-by-lamp inspection and location mapping.

[0095] This diagram illustrates the process by which the visual perception unit establishes a spatial location map of the lamps through lamp-by-lamp inspection.

[0096] Explanation of markings in the diagram:

[0097] 101—Visual perception unit, which synchronously acquires stage images at every moment;

[0098] 102—RDM communication interface, for connection to the lighting control network;

[0099] 301—Timing control unit, connected to the RDM communication interface (102), used to control the lamps to light up sequentially in a predetermined order, with the command timing sequence being t1, t2, t3, t4, ..., tn. n Only one light fixture is lit at any given time;

[0100] 107-1, 107-2, 107-3, 107-4, ..., 107-n — Light fixture 1, light fixture 2, light fixture 3, light fixture 4, ..., light fixture n, which receive the lighting command in sequence and light up.

[0101] 302—Lighting fixture spatial location database, connected to the visual perception unit (101), used to integrate all time-recorded location information to generate a complete lighting fixture spatial location mapping map.

[0102] The arrows in the diagram indicate the direction of control and data flow:

[0103] The timing control unit (301) sends lighting commands (dashed arrows) to the lamps (107-1 to 107-n) sequentially through the RDM communication interface (102).

[0104] The visual perception unit (101) acquires images at every moment and transmits the calculated position information of a single lamp to the lamp spatial position database (302) in real time.

[0105] The spatial location database of lighting fixtures (302) integrates all single-point data to generate the final location map.

[0106] Figure 4 : Batch configuration sending process diagram.

[0107] This diagram illustrates the process of generating and sending batch configuration commands.

[0108] Explanation of markings in the diagram:

[0109] 102—RDM communication interface, which converts configuration commands into communication signals conforming to the RDM standard;

[0110] 103 — Location-UID fusion module, outputs the {location:UID} mapping relationship;

[0111] 104 — Pre-programmed configuration interface, outputs a preset configuration parameter table;

[0112] 105—Batch configuration instruction generation module, receives mapping relationship and preset configuration parameters, generates configuration instructions for each UID, and integrates them into configuration data package (401).

[0113] 106—RDM bulk transmission module, receives configuration data packets (401) and sends them in bulk to the target lighting fixtures via the RDM protocol;

[0114] 107 — Lighting fixtures, receive configuration commands and execute parameter settings;

[0115] 108—Configuration information verification module, which uses the visual perception unit (101) to collect the working status of the lamps and verify the configuration results;

[0116] 401 — Configuration data package, containing configuration information for multiple lighting fixtures, represented in the form of {UID : DMX address} key-value pairs.

[0117] The arrows in the diagram indicate the direction of data flow:

[0118] The mapping relationship output by the location-UID fusion module (103) and the preset configuration parameters output by the preprogrammed configuration interface (104) flow together to the batch configuration instruction generation module (105).

[0119] The configuration data packet (401) generated by the batch configuration instruction generation module (105) flows to the RDM batch transmission module (106).

[0120] The RDM bulk transmission module (106) sends configuration commands to the lamps (107) through the RDM communication interface (102) (solid arrows indicate command issuance).

[0121] The RDM confirmation message returned by the luminaire can optionally flow to the configuration information verification module (108) via the RDM communication interface (102) (dashed arrows indicate optional feedback);

[0122] The configuration information verification module (108) collects the actual working status through the visual perception unit (101) and feeds back the visual verification results to the batch configuration instruction generation module (105) to achieve closed-loop control.

[0123] Figure 5 Configuration verification closed-loop diagram.

[0124] This diagram illustrates the workflow of the configuration verification module, forming a closed-loop control from configuration distribution to effect verification.

[0125] Explanation of markings in the diagram:

[0126] 101—Visual perception unit, which restarts data acquisition after configuration is sent to capture the actual working status of the lamp. The working status includes, but is not limited to: whether the lamp responds to the control signal according to the newly configured DMX address, and outputs the acquired actual status data to the configuration information verification module (108);

[0127] 104—Pre-programmed configuration interface, serving as one of the expected configuration data sources, connects to the 3D pre-programmed model or console database, storing preset lighting configuration parameters for each location. This interface provides expected configuration data to the configuration information verification module (108) as a comparison benchmark.

[0128] 105—Connects to the configuration information verification module (108), and after receiving the retransmission instruction from the abnormal branch, regenerates the configuration instruction for the corresponding abnormal lamp based on the stored {location identifier: UID} mapping relationship and preset configuration parameters. The generated instruction can be retransmitted to the lamp (107) through the RDM batch sending module, forming a cycle of re-verification;

[0129] 107 – The stage lighting fixture has been configured and distributed, and is in a state of pending verification. The fixture has received configuration instructions via the RDM batch transmission module, but it has not yet been confirmed whether its actual working status meets expectations.

[0130] 108—Configuration information verification module, connected to the visual perception unit (101) and the pre-programmed configuration interface (104) respectively, is used to receive the actual working status data of the lamp and compare it with the expected configuration. This module has a built-in comparison algorithm and supports multiple methods such as address response verification, light column parameter verification, and status code verification. Based on the comparison result, the configuration information verification module (108) executes the following branch process:

[0131] Normal branch: If the actual status matches the expected configuration, the configuration is successful and the verification process ends. A success log can be recorded, or the process can proceed to verifying the next light fixture.

[0132] Abnormal Branch: If the comparison is inconsistent, it indicates a configuration error or lamp malfunction, triggering the abnormal handling process. The configuration information verification module (108) sends a resend command to the batch configuration command generation module (105), requesting the regeneration of the configuration command for the corresponding abnormal lamp. The resend command must at least include the UID of the abnormal lamp and the parameters that need to be reconfigured.

[0133] The arrows in the diagram indicate the direction of data flow:

[0134] The actual working status data collected by the visual perception unit (101) flows to the configuration information verification module (108).

[0135] The expected configuration data provided by the pre-programmed configuration interface (104) flows to the configuration information verification module (108).

[0136] After the configuration information verification module (108) performs the comparison, if the comparison is consistent, the process ends normally; if the comparison is inconsistent, a resend instruction is sent to the batch configuration instruction generation module (105).

[0137] The batch configuration instruction generation module (105) regenerates the configuration instruction based on the retransmission instruction, and then sends it again to the configured lamps (107) through the RDM batch transmission module (106), forming a cycle of re-verification.

[0138] Figure 6 : Schematic diagram of scene layout information generation without pre-programming.

[0139] This figure illustrates the process of generating on-site lighting layout information based on visual perception and RDM communication in a scenario without a pre-programmed model.

[0140] Explanation of markings in the diagram:

[0141] 101—Visual perception unit, outputs spatial position coordinate data of the lamp;

[0142] 102—RDM communication interface, outputs a list of lamp UIDs;

[0143] 103 — Location-UID fusion module, outputs the mapping relationship of lamp {location identifier: UID};

[0144] 601—Layout information generation module, connected to the location-UID fusion module (103), is used to receive the mapping relationship of the lamp {location identifier: UID} and generate the on-site lamp layout information file.

[0145] The arrows in the diagram indicate the direction of data flow:

[0146] The position coordinate data output by the visual perception unit (101) flows to the position-UID fusion module (103).

[0147] The UID list data output by the RDM communication interface (102) flows to the location-UID fusion module (103).

[0148] The mapping relationship data of the lamp {location identifier: UID} output by the location-UID fusion module (103) flows to the layout information generation module (601).

[0149] The layout information generation module (601) generates a site lighting layout information file based on the {location identifier: UID} mapping relationship and outputs it to the outside for lighting engineers to manually configure or program for reference. Detailed Implementation

[0150] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments.

[0151] Example 1: Application in large-scale concerts (with pre-programmed model)

[0152] In a large-scale concert tour, 200 stage lights (including beam lights, pattern lights, and color-changing lights) were suspended above the stage, all supporting the RDM protocol. When the lights were moved from city A to city B, the DMX addresses and channel modes needed to be reconfigured at the new venue.

[0153] System Deployment:

[0154] Visual perception unit: A binocular camera solution is adopted, with two high-definition industrial cameras deployed on the left and right sides in front of the stage.

[0155] RDM communication interface: Connects all luminaires via DMX cable and supports RDM protocol communication.

[0156] Step 1: Visual mapping (lamp inspection) The system controls all lamps to enter the inspection mode, and lights up each lamp in sequence (each lamp is lit for 2 seconds). The visual perception unit (101) records the pixel coordinates when each lamp is lit and generates a temporary position list: {position 1, position 2, …, position 200}.

[0157] Step 2: Batch UID Reading The system sends a broadcast query command via the RDM protocol, and all lamps return their UIDs. The RDM communication interface (102) obtains the list of lamp UIDs: {UID1, UID2, …, UID200}.

[0158] Step 3: Location-UID mapping The location-UID fusion module (103) associates the inspection sequence of Step 1 with the UID list of Step 2: the light lit at time t1 → UID1, the light lit at time t2 → UID2, ..., and generates a mapping table: {location 1:UID1, location 2:UID2, ..., location 200:UID200}.

[0159] Step 4: Load Pre-programmed Configuration. The pre-programmed configuration interface (104) reads the preset configuration parameters for each position from the 3D pre-programmed model (such as Depence2): Position 1: DMX address = 1, channel mode = extended mode; Position 2: DMX address = 21, channel mode = standard mode; ...

[0160] Step 5: Batch Configuration Sending The batch configuration instruction generation module (105) generates configuration instructions for each UID according to the mapping relationship. The RDM batch sending module (106) sends configuration instructions to all lamps in batches via the RDM protocol: To UID1: DMX address = 1, channel mode = extended; To UID2: DMX address = 21, channel mode = standard; ... Supports simultaneous broadcast mode sending, and can also unicast sequentially to ensure reliability.

[0161] Step 6: Configuration Verification After the configuration is sent, the configuration information verification module (108) observes the status of the lamps again through the visual perception unit (101): controls the lamps to light up sequentially according to the new address; verifies whether the position of the lit lamps is consistent with the expectation; if there is an abnormality (such as a lamp not responding), automatically resends or alarms.

[0162] Result: All 200 lights were automatically configured within 12 minutes, without any manual climbing or verification, with an accuracy rate of 100%.

[0163] Example 2: Application of rapid scene transition in TV variety shows (with pre-programmed model)

[0164] In a certain TV variety show, multiple different scenes need to be recorded every day, and the lighting layout and configuration requirements for each scene are different.

[0165] Step 1: The visual mapping camera captures a panoramic image of the stage, and the visual perception unit (101) automatically detects the pixel coordinates of all the lights through an image recognition algorithm to generate a position list.

[0166] Step 2: Batch reading of UIDs via RDM communication interface (102) Read the UIDs of all lamps through the RDM protocol.

[0167] Step 3: Location-UID mapping (visual guidance) The system controls the light fixture 1 to flash, and the visual perception unit (101) automatically identifies its location. The location-UID fusion module (103) records {location A : UID1}. The system then controls the light fixture 2 to flash and records {location B : UID2}. No manual intervention is required throughout the process, and the system automatically completes all mappings.

[0168] Steps 4-6: Same as steps 4-6 in Example 1.

[0169] Results: 100 lamps were automatically configured within 8 minutes, which is more than 90% more efficient than the traditional RDM operation of one lamp at a time (which takes 1-2 hours).

[0170] Example 3: Temporary Music Festival Application (No Pre-programmed Model)

[0171] At a temporary outdoor music festival, 150 stage lights were suspended above the stage, with no pre-programmed models available. The lighting technician needed to quickly configure the lights and wanted to obtain the layout information of the lights on site for subsequent programming.

[0172] System deployment: Same as in Example 1.

[0173] Steps 1-3: Same as steps 1-3 in Example 1, complete visual mapping and location-UID mapping, which takes 6 minutes.

[0174] Step 4: Layout Information Generation. The layout information generation module (601) generates a site lighting layout information file based on the mapping table generated in Step 3 and the 3D coordinates of the lighting fixtures reconstructed by the visual perception unit (101). The layout information includes: the UID of each lighting fixture, the 3D coordinates (X, Y, Z) of each lighting fixture, and the relative positional relationship between the lighting fixtures. The layout information is provided to the lighting engineer in the form of a visual interface or a file.

[0175] Step 5: Manual Configuration (Optional) The lighting engineer sets the DMX address and channel mode for the luminaires on the console or manual configuration interface based on the layout information. The system sends the configuration commands to the corresponding luminaires via the RDM batch transmission module.

[0176] Result: The lighting technicians obtained a complete on-site lighting layout diagram, which allowed them to program based on the actual locations, while significantly reducing configuration time compared to traditional methods.

[0177] Example 4: Application of Individual Feature Compensation

[0178] A certain performance has extremely high requirements for lighting precision, requiring the individual characteristic data of each light (motor hysteresis, response delay) to participate in the control.

[0179] Step 1: Individual Feature Database Construction. When building the database for the first time, the system automatically scans and obtains the individual feature data of each lamp, and stores the individual feature data in association with the UID: {UID1: hysteresis 0.1°, delay 5ms}.

[0180] Step 2: Configuration Sending During each configuration, the batch configuration instruction generation module (105) packages and sends the individual feature data along with configuration parameters such as DMX address and channel mode.

[0181] Step 3: Precision control console. In subsequent control, individual feature compensation is automatically applied to achieve precise control of "one light, one policy".

[0182] The above embodiments are merely illustrative examples. Those skilled in the art can adjust the functions and parameters of each module according to actual needs without departing from the protection scope defined by the claims of this invention.

Claims

1. A stage lighting intelligent configuration system based on visual perception, characterized in that, include: A visual perception unit is used to collect visual feature information of lighting fixtures in the stage space and establish a spatial position mapping map of the lighting fixtures. The spatial position mapping map includes at least the position identifier of each lighting fixture in the stage coordinate system or image coordinate system. The RDM communication interface connects to the lighting control network and is used to read the unique UID of each lighting fixture and obtain a list of lighting fixtures via the RDM protocol. The location-UID fusion module is connected to the visual perception unit and the RDM communication interface, and is used to associate the location identifier in the spatial location mapping map with the UID to establish a mapping relationship of {location identifier: UID}. A pre-programmed configuration interface is used to obtain the preset lighting configuration parameters for each position identifier in the 3D pre-programmed model or console database. The configuration parameters include at least the DMX start address. A batch configuration instruction generation module, connected to the location-UID fusion module and the pre-programmed configuration interface, is used to generate configuration instructions containing corresponding configuration parameters for each UID according to the mapping relationship. The RDM batch sending module is connected to the batch configuration instruction generation module and is used to send the configuration instructions to the lamps with the corresponding UIDs via the RDM protocol.

2. The system according to claim 1, characterized in that, The visual perception unit establishes a position mapping map through a lamp-by-lamp inspection method, including: controlling the lamps to light up sequentially; acquiring images of each lamp when it is lit; and recording the pixel coordinates or three-dimensional coordinates corresponding to each lamp.

3. The system according to claim 1, characterized in that, It also includes a configuration verification module, which is connected to the visual perception unit, and is used to verify whether the lamp works normally according to the new configuration through visual perception after the configuration is sent, and to provide feedback on the configuration result.

4. The system according to claim 1, characterized in that, It also includes an individual feature compensation module for storing individual feature data for each lamp, wherein the individual feature data includes at least one or more of motor hysteresis and response delay; the batch configuration instruction generation module sends the individual feature data together with the configuration instruction.

5. The system according to claim 1, characterized in that, It also includes a layout information generation module, which is connected to the location-UID fusion module, and is used to generate on-site lighting layout information based on the {location identifier: UID} mapping relationship in a scenario without a pre-programmed model. The layout information includes at least the three-dimensional coordinate position and UID of each lighting fixture.

6. The system according to claim 1, characterized in that, The RDM bulk transmission module supports at least one of the following transmission modes: Broadcast mode: Sends the same configuration to all lights at once; Group broadcast mode: Send configuration to a specific group of lights; Unicast mode: Send personalized configurations to each light fixture individually.

7. The system according to claim 1, characterized in that, The configuration parameters include at least one of the following: The luminaire's DMX start address; the luminaire's channel mode; network configuration parameters; luminaire name or label; channel curve mode; fan speed mode.

8. The system according to claim 1, characterized in that, The visual perception unit includes at least one of the following implementations: A single physical image acquisition device; a stereoscopic vision system consisting of multiple physical image acquisition devices; and the system described in another patent application filed by the applicant on the same day, entitled "A Physical-Virtual Fusion Multi-View Perception System for Stage Lighting Control".

Images