CN116320096B - Method and equipment control system for sending and receiving DMX data packet - Google Patents
Method and equipment control system for sending and receiving DMX data packet Download PDFInfo
- Publication number
- CN116320096B CN116320096B CN202310575641.9A CN202310575641A CN116320096B CN 116320096 B CN116320096 B CN 116320096B CN 202310575641 A CN202310575641 A CN 202310575641A CN 116320096 B CN116320096 B CN 116320096B
- Authority
- CN
- China
- Prior art keywords
- domain identifier
- dmx
- target
- data packet
- receiving end
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 65
- 238000004590 computer program Methods 0.000 claims description 21
- 230000001795 light effect Effects 0.000 abstract description 17
- 238000004891 communication Methods 0.000 description 11
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 8
- 230000008569 process Effects 0.000 description 7
- 230000000694 effects Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 101001028025 Homo sapiens Mdm2-binding protein Proteins 0.000 description 2
- 102100037572 Mdm2-binding protein Human genes 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000001747 exhibiting effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/22—Parsing or analysis of headers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
Abstract
A method for sending and receiving DMX data packets and a device control system, wherein the method for sending the DMX data packets is applied to a transmitting end, and the method comprises the following steps: the method comprises the steps of obtaining target data and a first domain identifier, wherein the first domain identifier is used for marking and analyzing a target receiving end of the target data, generating a digital multiplexing DMX data packet, and sending the DMX data packet to the target receiving end, wherein the DMX data packet comprises the target data and the first domain identifier. According to the technical scheme, the target data can be sent to different receiving ends by sending the DMX data packets carrying different first domain identifications, so that the light effect which can be realized by the equipment control system is remarkably improved.
Description
Technical Field
The present application relates to the field of consumer electronics technologies, and in particular, to a method and an apparatus control system for transmitting and receiving Digital Multiplexing (DMX) data packets.
Background
At present, with the improvement of the living standard of people, cultural entertainment activities are gradually increased, and the demands for stage lighting are increasingly larger. The DMX512 protocol is a data dimming protocol, and can be used for digitally controlling dimmers and other control devices in stages, theatres, studios and other places.
In the prior art, the device control system may include a transmitting end and a receiving end corresponding to the transmitting end, where the transmitting end may send data corresponding to the receiving end, and the receiving end may parse the data and present various light effects according to the data. However, since the transmitting end can only transmit the data to the receiving end, the lighting effect that can be achieved by the device control system is very limited.
Disclosure of Invention
The present application is directed to a method and an apparatus control system for transmitting and receiving DMX data packets, and aims to improve the light effect that can be achieved by the conventional apparatus control system.
A first aspect of an embodiment of the present application proposes a method for sending a DMX data packet, where the method is applied to a transmitting end, and the method includes:
acquiring target data and a first domain identifier, wherein the first domain identifier is used for marking a target receiving end for analyzing the target data;
generating a DMX data packet, wherein the DMX data packet comprises the target data and the first domain identifier;
and sending the DMX data packet to the target receiving end.
In some embodiments, the DMX data packet includes a start frame and a plurality of data frames;
the start frame carries the first domain identifier, or a specific data frame in the plurality of data frames carries the first domain identifier.
In some embodiments, the method further comprises:
determining the first domain identifier for marking the target receiving end;
and notifying the target receiving end of the first domain identifier.
In some embodiments, the first field is identified as a value greater than or equal to 0 and less than or equal to 255.
A second aspect of an embodiment of the present application proposes a method for receiving a DMX packet, where the method is applied to a receiving end, and the method includes:
receiving a DMX data packet, wherein the DMX data packet comprises target data and a first domain identifier, and the first domain identifier is used for marking a target receiving end for analyzing the target data;
and if the first domain identifier is the same as the second domain identifier, analyzing the target data, wherein the second domain identifier is used for marking the receiving end.
In some embodiments, the DMX data packet includes a start frame and a plurality of data frames, the method further including:
acquiring the first domain identifier from the initial frame; or alternatively, the first and second heat exchangers may be,
the first domain identification is obtained from a particular data frame of the plurality of data frames.
In some embodiments, the method further comprises:
receiving the submitted second domain identification; or alternatively, the first and second heat exchangers may be,
and receiving the second domain identifier notified by the transmitting end, wherein the transmitting end is used for transmitting the DMX data packet.
In some embodiments, the second field is identified as a value greater than or equal to 0 and less than or equal to 255.
A third aspect of the embodiments of the present application proposes a transmitting terminal, where the transmitting terminal includes:
the system comprises an acquisition module, a first domain identification module and a second domain identification module, wherein the acquisition module is used for acquiring target data and the first domain identification, and the first domain identification is used for marking a target receiving end for analyzing the target data;
the generation module is used for generating a DMX data packet, wherein the DMX data packet comprises the target data and the first domain identifier;
and the sending module is used for sending the DMX data packet to the target receiving end.
A fourth aspect of the embodiments of the present application provides a receiving end, where the receiving end includes:
the receiving module is used for receiving a DMX data packet, wherein the DMX data packet comprises target data and a first domain identifier, and the first domain identifier is used for marking a target receiving end for analyzing the target data;
and the analysis module is used for analyzing the target data if the first domain identifier is the same as the second domain identifier, and the second domain identifier is used for marking the receiving end.
A fifth aspect of the embodiments of the present application proposes an apparatus control system, where the system includes a transmitting end and a receiving end;
the transmitting terminal is used for acquiring target data and a first domain identifier, the first domain identifier is used for marking and analyzing a target receiving terminal of the target data, a DMX data packet is generated, the DMX data packet comprises the target data and the first domain identifier, and the DMX data packet is sent to the target receiving terminal;
the receiving end is configured to receive the DMX packet, and if the first domain identifier is the same as the second domain identifier, parse the target data, where the second domain identifier is used to mark the receiving end.
A sixth aspect of the embodiments of the present application proposes an electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the method according to the first aspect or the steps of the method according to the second aspect as described above when the computer program is executed by the processor.
A seventh aspect of the embodiments of the present application proposes a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the method according to the first aspect or the steps of the method according to the second aspect described above.
Compared with the prior art, the embodiment of the invention has the beneficial effects that:
in this embodiment of the present application, target data and a first domain identifier may be obtained, and a DMX packet may be generated, where the generated DMX packet includes the target data and the first domain identifier. Because the first field identifies the target receiving end for marking and analyzing the target data, the DMX data packet is sent to the target receiving end, so that each receiving end receiving the DMX data packet can identify whether the DMX data packet includes the target data corresponding to the receiving end. That is, by sending DMX data packets carrying different first domain identifiers, target data can be sent to different receiving ends, so that the light effect that can be achieved by the device control system is significantly improved. In addition, the transmitting end can send DMX data packets to a plurality of receiving ends, and the cost of the equipment control system and the cost of the light effect are reduced.
Drawings
Fig. 1 is a schematic diagram of an apparatus control system according to an embodiment of the present application;
fig. 2 is a flow chart of a method for sending DMX data packets according to an embodiment of the present application;
fig. 3 is a schematic data structure diagram of a DMX packet according to an embodiment of the present application;
fig. 4 is a flowchart of another method for sending DMX packets according to an embodiment of the present application;
fig. 5 is a flowchart of a method for receiving a DMX packet according to an embodiment of the present application;
FIG. 6 is a flowchart of another method for receiving a DMX packet according to an embodiment of the present application;
fig. 7 is a schematic flow chart of a device control method according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a transmitting end according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a receiving end according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the technical problems, technical schemes and beneficial effects to be solved by the present application more clear, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the present application.
It will be understood that when an element is referred to as being "mounted" or "disposed" on another element, it can be directly on the other element or be indirectly on the other element. When an element is referred to as being "connected to" another element, it can be directly connected to the other element or be indirectly connected to the other element.
It is to be understood that the terms "length," "width," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," and the like indicate or are based on the orientation or positional relationship shown in the drawings, merely to facilitate description of the present application and simplify description, and do not indicate or imply that the devices or elements referred to must have a particular orientation, be configured and operated in a particular orientation, and therefore should not be construed as limiting the present application.
Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present application, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
Fig. 1 shows a schematic diagram of a device control system according to an embodiment of the present application. The device control system comprises a transmitting end 110 and at least one receiving end 120 (only 3 receiving ends 120 are shown in fig. 1), the transmitting end 110 being in communication connection with each receiving end 120.
The transmitting end 110 may acquire and send data corresponding to any receiving end 120. In some embodiments, the transmitting end 110 may be a remote control, a wireless box, an upper computer, a dimming console, a base station, or the like. Of course, in practical applications, the transmitting end 110 may be other devices.
The receiving end 120 may receive the data sent by the transmitting end 110, and determine whether the data is data corresponding to the receiving end 120. If the data is received by the receiving end 120, the data may be parsed and further processed. In some embodiments, the receiving end 120 may control the lamp to operate based on the data, thereby exhibiting various lighting effects. In some embodiments, the receiving end 120 may be a light fixture. Of course, in practical applications, the receiving end 120 may be other devices.
It will be appreciated that in some embodiments, the transmitting end 110 may also receive data, and the receiving end 120 may also transmit data, that is, the same device may be used as the transmitting end 110 and the receiving end 120, for example, a dimming console may be used as the transmitting end 110 and the receiving end 120.
The communication connection between the transmitting end 110 and the receiving end 120 may be a wired connection or a wireless connection. In some implementations, the wireless connection may be a 2.4GHz, bluetooth, or Wi-Fi based wireless communication connection.
Fig. 2 is a flow chart of a method for sending DMX data packets according to an embodiment of the present application. The method can be used for the transmitting end in fig. 1, and the method comprises the following steps:
s201, acquiring target data and a first domain identifier, wherein the first domain identifier is used for marking a target receiving end for analyzing the target data.
In some implementations, the target data may be used to instruct the target receiving end to perform one or more operations. For example, the target data may be used to indicate whether the luminaire is lighted, the brightness and color of the lighted, and so on.
In some implementations, the first domain identification can be a numerical value. In some embodiments, the first field identification may be any number greater than or equal to 0 and less than or equal to 255. Of course, in practical applications, the first domain identifier may be other information capable of marking the target receiving end.
In some embodiments, a first domain identification for marking the target receiver may be determined, and the target receiver is notified of the first domain identification. In some implementations, obtaining an unassigned domain identifier may include obtaining an unassigned domain identifier and determining the unassigned domain identifier as a first domain identifier. In some implementations, a first domain identification submitted by a user can be received. In some embodiments, the first domain identifier may be notified to the target receiving end when the communication connection is established with the target receiving end, and of course, the first domain identifier may be notified to the target receiving end at other occasions.
In some embodiments, the first domain identification submitted by the target receiving end may be received, that is, the first domain identification determined by the target receiving end is obtained from the target receiving end.
In some embodiments, if the target receiving end and the first domain identifier are determined, a correspondence between the device identifier of the target receiving end and the first domain identifier may be stored.
In some implementations, the target data may be obtained from a third device along with the first domain identification. In some embodiments, the third device may be other devices in a local area network (such as a dimming console or computer, etc.) or other devices in a slave ethernet network (such as a server).
In some embodiments, the manner of acquiring the target data may be different from the manner of acquiring the first domain identifier, for example, the target data and the first domain identifier may be acquired from different devices, respectively. In some embodiments, the timing to acquire the target data may be different from the timing to acquire the first domain identification.
In some embodiments, when the target data is acquired, a target receiving end for analyzing the target data may be determined, and a first domain identifier corresponding to the target receiving end is acquired. In some embodiments, a device identifier of the target receiving end may be obtained, and a first domain identifier corresponding to the device identifier is obtained. In some embodiments, the first domain identifier may be obtained from a stored correspondence between device identifiers and domain identifiers based on the device identifiers, where the correspondence between device identifiers and domain identifiers may include at least one device identifier and a domain identifier corresponding to the device identifier.
Wherein the device identification may be used to mark a device, such as a receiving end. In some embodiments, the device identifier may fixedly mark one receiving end, and the domain identifier may correspond to different receiving ends at different times, or the domain identifier corresponding to one receiving end at different times may be different. For example, the device identifier of a receiving end may be determined by the manufacturer of the receiving end when the receiving end leaves the factory, and the device identifier may mark the receiving end no matter when the receiving end establishes communication connection with the transmitting end at any time; the receiving end can acquire a new domain identifier each time a communication connection is established with the transmitting end, and it is understood that the domain identifier acquired by the receiving end when the receiving end establishes a communication connection with the transmitting end any two times may be different.
S202, generating a DMX data packet, wherein the DMX data packet comprises target data and a first domain identifier.
The obtained target data and the first domain identifier may be encapsulated based on the DMX512 protocol, so as to obtain a DMX packet.
In some embodiments, the data structure of the DMX data packet may be as shown in fig. 3. The DMX packet consists of an idle frame (Mark Time Between Packets, MTBP), an interrupt frame (Break), an interval frame (Mark After Break, MAB), a Start Code (SC), and 512 data frames. In some embodiments, a DMX packet may be referred to as a field.
The MTBP marks that a complete DMX data packet is sent, and is also a marking bit of the next DMX data packet to start, and the high level is valid, which indicates that the current transmission line is in an idle state and no data is transmitted.
Break is a hint control signal for a DMX packet, and corresponds to the program reset phase after the end of a DMX packet, after which the next packet of data should be sent. The Break signal is active low.
The MAB is an indication of the start of a DMX packet, and since the first bit of each frame is low, the MAB is high in order to distinguish between the low level of Break and the low level of the start bit of the frame, and therefore, two low pulses are used before and after a high pulse interval.
The SC is made up of 11 bits, with the exception of the two high end bits, all 9 bits being low, indicating the start of a data frame in a DMX packet. In some embodiments, the first domain identification may be carried in the SC.
One data frame is composed of 11 bits in total of 1 start bit, 8 data bits, and 2 end bits. Each data frame is called a control channel and can control one or several functions of the lighting device. In some implementations, the first field identification can be carried in a particular data frame. In some embodiments, the DMX data packet includes 512 data frames in total, and a particular data frame may include any of the 512 data frames, such as a 1 st frame data frame or a 512 th frame data frame.
In some embodiments, when a particular data frame or SC carries a first field identification, the first field identification is a binary value. The binary values may comprise a sequence of 1's and 0's, wherein a 1 in the binary value may be represented by a high level and a 0 may be represented by a low level.
For example, the first domain identification may be 0000 0000 (i.e., 0 in decimal). The specific data frame or SC carrying the first field identifier may be 0 0000 0000 11, where bit 1 is a start bit, indicated by a low level, bits 2-9 are the first field identifier, and bits 10-11 are an end bit, indicated by a high level.
As another example, the first domain identification may be 0000 0001 (i.e., 1 in decimal). The specific data frame or SC carrying the first field identifier may be 0 0000 0001 11, where bit 1 is a start bit, indicated by a low level, bits 2-9 are the first field identifier, and bits 10-11 are an end bit, indicated by a high level.
As another example, the first domain identification may be 1111 1111 (i.e., 255 in decimal). The specific data frame or SC carrying the first field identifier may be 0 1111 1111 11, where bit 1 is a start bit, indicated by a low level, bits 2-9 are the first field identifier, and bits 10-11 are an end bit, indicated by a high level.
S203, sending the DMX data packet to the target receiving end.
Because the DMX data packet includes the target data and the first domain identifier, the first domain identifier can mark and analyze the target receiving end of the target data, so that sending the DMX data packet can enable each receiving end that receives the DMX data packet to identify whether the DMX data packet includes the target data corresponding to the receiving end. That is, by sending DMX data packets carrying different first domain identifiers, target data can be sent to different receiving ends, so that the light effect that can be achieved by the device control system is significantly improved. For example, the transmitting end comprises a dimming control console, the receiving end comprises a plurality of groups of lamps, and because the SC or the specific data frame in the DMX data packet can carry the first domain identifier and the value range of the first domain identifier is 0-255, the dimming control console can control the at most 256 groups of lamps to emit light through carrying different first domain identifiers in the DMX data packet, and compared with a mode of only controlling one group of lamps to emit light, the dimming control console can provide richer light effects.
In this embodiment of the present application, target data and a first domain identifier may be obtained, and a DMX packet may be generated, where the generated DMX packet includes the target data and the first domain identifier. Because the first field identifies the target receiving end for marking and analyzing the target data, the DMX data packet is sent to the target receiving end, so that each receiving end receiving the DMX data packet can identify whether the DMX data packet includes the target data corresponding to the receiving end. That is, by sending DMX data packets carrying different first domain identifiers, target data can be sent to different receiving ends, so that the light effect that can be achieved by the device control system is significantly improved. In addition, the transmitting end can send DMX data packets to a plurality of receiving ends, and the cost of the equipment control system and the cost of the light effect are reduced.
Fig. 4 is a flowchart of another method for sending DMX data packets according to an embodiment of the present application. The method can be used for the transmitting end in fig. 1, and the method comprises the following steps:
s401, setting a value range of the domain identifier.
In some implementations, a range of values for a domain identification submitted by a user can be received.
In some embodiments, the range of values of the domain identifiers, that is, the number of domain identifiers that can be allocated, that is, the number of receiving ends that can acquire data from the transmitting end, is set.
In some embodiments, the minimum value of the range of values for the domain identification may be greater than or equal to 0 and the maximum value of the range of values for the domain identification may be less than or equal to 255. For example, the range of values for the domain identification may be 0-255. Of course, in practical application, the value range of the domain identifier may be other value ranges.
S402, setting the position of the first domain identifier.
Wherein, setting the location of the first domain identifier may refer to setting the location of the first domain identifier in the DMX packet. In some implementations, the SC or a particular data frame can be set to the location of the first domain identification.
In some implementations, the location of the first domain identification submitted by the user can be received.
S403, sending the DMX data packet to the target receiving end.
In some embodiments, a first domain identifier may be allocated to the target receiving end based on the set value range of the domain identifier, a DMX packet may be generated based on the set location of the first domain identifier, and the DMX packet may be sent to the target receiving end.
The manner of sending the DMX data packet to the target receiving end may be referred to the description of S201 to S203, and will not be described in detail herein.
In the embodiment of the application, the value range of the first domain identifier can be set, so that the number of the receiving ends can be flexibly adjusted, the transmitting end can transmit DMX data packets to more or fewer receiving ends, and the light effect of the equipment control system can be further improved. The position of the first domain identifier can be set, so that the mode carrying the first domain identifier can be flexibly adjusted according to specific scenes such as the size and the type of the target data, the mode carrying the first domain identifier is matched with the specific scenes, and the light effect of the equipment control system can be further improved.
Fig. 5 is a flow chart illustrating a method for receiving DMX data packets according to an embodiment of the present application. The method can be used for the receiving end in fig. 1, and the method includes:
s501, receiving a DMX data packet, wherein the DMX data packet comprises target data and a first domain identifier, and the first domain identifier is used for marking a target receiving end for analyzing the target data.
The DMX data packet can be acquired through communication connection with the transmitting end.
S502, if the first domain identifier is the same as the second domain identifier, analyzing the target data, wherein the second domain identifier is used for marking the current receiving end.
If the second domain identifier corresponding to the current receiving end is the same as the first domain identifier in the DMX data packet, the receiving end is the target receiving end, so that the target data can be obtained from the DMX data packet and analyzed. Of course, if the second domain identifier is different from the first domain identifier, the current receiving end is not the target receiving end, so that no operation may be performed, or the DMX packet may be discarded. That is, by identifying the first domain identifier in the DMX packet, different receiving ends can receive the target data of the same transmitting end, thereby significantly improving the light effect that can be achieved by the device control system.
In some embodiments, the first domain identification may be obtained from an SC or a particular data frame in the DMX data packet. In some embodiments, the particular data frame may include a 1 st data frame or a 512 th data frame.
In some embodiments, the second field identification may be any value greater than or equal to 0 and less than or equal to 255. Of course, in practical applications, the second domain identifier may be other information capable of marking the current receiving end.
In some implementations, a second domain identification can be obtained. In some implementations, obtaining the second domain identification can include obtaining a user-submitted second domain identification. In some embodiments, obtaining the second domain identification may include obtaining a second domain identification of the transmitting-end notification. Of course, in practical application, the second domain identifier may be obtained in other manners.
In some embodiments, the DMX data packet may be verified, including at least one of a security check and an integrity check. If the verification is passed, continuing to process the target data, otherwise, not continuing to process the target data. In some implementations, one or more operations marked by the target data may be performed if the verification passes.
For example, the transmitting end includes a dimming console, the receiving end includes a plurality of groups of lamps, each group of lamps corresponds to a domain identifier, and each domain identifier can be any value between 0 and 255. And the dimming control console sends a DMX data packet to the plurality of groups of lamps, and a first domain mark which can be carried by SC or a specific data frame in the DMX data packet is 2. When each group of lamps acquires the DMX data packet, whether the second domain identifier of the receiving end is 2 or not can be judged, namely, whether the second domain identifier is the same as the first domain identifier or not can be judged, if the second domain identifier is the same as the first domain identifier, the light can be emitted according to the light emitting mode marked by the target data, otherwise, the DMX data packet can be discarded, and the next DMX data packet is waited. Then a maximum of 256 sets of lights may be in communication with the transmitting end to present a richer lighting effect.
In this embodiment of the present application, a DMX packet may be received, where the DMX packet includes target data and a first domain identifier, where the first domain identifier is used to mark a target receiving end that parses the target data. If the second domain identifier corresponding to the current receiving end is the same as the first domain identifier in the DMX data packet, the receiving end is the target receiving end, so that the target data can be obtained from the DMX data packet and analyzed. That is, by identifying the first domain identifier in the DMX packet, different receiving ends can receive the target data of the same transmitting end, thereby significantly improving the light effect that can be achieved by the device control system. In addition, the transmitting end can send DMX data packets to a plurality of receiving ends, and the cost of the equipment control system and the cost of the light effect are reduced.
Fig. 6 is a flowchart of another method for receiving DMX packets according to an embodiment of the present application. The method can be used for a receiving end, and comprises the following steps:
s601, setting a second domain identifier.
In some implementations, a second domain identification submitted by a user can be received. In some embodiments, a second domain identification of the transmitting-side notification may be obtained.
In some embodiments, the second domain identification may be determined based on a range of values of the domain identification, where the second domain identification may be any number within the range of values. For example, the value range is 0-255, and the second field identifier may be 0, 1, 50, or 255.
S602, setting the position of the first domain identifier.
In some implementations, the location of the first domain identification submitted by the user can be received. In some embodiments, the location of the first domain identification may be obtained from the transmitting end.
S603, receiving a DMX data packet, wherein the DMX data packet comprises target data and a first domain identifier.
S604, judging whether the first domain identification is the same as the second domain identification, if so, executing S605, otherwise, executing S606.
In some embodiments, the first domain identification may be obtained from the DMX packet based on the location of the set first domain identification, and the first domain identification may be compared to the set second domain identification.
S605, analyzing the target data.
The method for determining whether the first domain identifier is the same as the second domain identifier and analyzing the target data may be referred to as the related description in S501-S502.
S606, waiting for the next DMX data packet, and returning to S603.
In the embodiment of the application, the position of the first domain identifier can be set, so that the mode carrying the first domain identifier can be flexibly adjusted according to specific scenes such as the size and the type of the target data, the mode carrying the first domain identifier is matched with the specific scenes, and the light effect of the equipment control system can be further improved.
Fig. 7 shows a flow chart of a device control method according to an embodiment of the present application.
S701, configuring a transmitting end and a receiving end.
The manner of configuring the transmitting end may refer to the related descriptions in S401-S402, and the manner of configuring the receiving end may refer to the related descriptions in S601-S602, which are not described in detail herein.
S702, a transmitting end acquires target data and a first domain identifier, wherein the first domain identifier is used for marking a target receiving end for analyzing the target data.
S703, the transmitting end generates a DMX data packet, wherein the DMX data packet comprises target data and a first domain identifier.
S704, the transmitting end transmits the DMX data packet to the target receiving end.
The manner in which the transmitting end performs S702-S704 may be referred to the description related to S201-S203.
S705, if the first domain identification is the same as the second domain identification, the receiving end analyzes the target data, and the second domain identification is used for marking the current receiving end.
The manner in which the receiving end performs S705 may be referred to the description related to S502.
In this embodiment of the present application, the transmitting end may acquire the target data and the first domain identifier, and generate a DMX packet, where the generated DMX packet includes the target data and the first domain identifier, and send the DMX packet to the target receiving end. Because the first domain identifier is used for marking the target receiving end for analyzing the target data, when each receiving end receives the DMX data packet, whether the receiving end is the target receiving end can be judged based on the first domain identifier of the DMX data packet. If the second domain identifier corresponding to the receiving end is the same as the first domain identifier in the DMX data packet, the receiving end is the target receiving end, so that the target data can be obtained from the DMX data packet and analyzed. That is, by sending DMX data packets carrying different first domain identifiers, target data can be sent to different receiving ends, so that the light effect that can be achieved by the device control system is significantly improved. In addition, the transmitting end can send DMX data packets to a plurality of receiving ends, and the cost of the equipment control system and the cost of the light effect are reduced.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic of each process, and should not limit the implementation process of the embodiment of the present application in any way.
Fig. 8 shows a schematic structural diagram of a transmitting end 110 according to an embodiment of the present application. The transmitting terminal 110 includes:
an obtaining module 801, configured to obtain target data and a first domain identifier, where the first domain identifier is used to mark a target receiving end that parses the target data;
a generating module 802, configured to generate a DMX packet, where the DMX packet includes target data and a first domain identifier;
a sending module 803, configured to send the DMX packet to the target receiving end.
In some embodiments, a DMX data packet includes a start frame and a plurality of data frames;
the start frame carries a first domain identifier, or a specific data frame in the plurality of data frames carries the first domain identifier.
In some embodiments, the transmitting end 110 is further configured to determine the first domain identifier for marking the target receiving end;
and notifying the target receiving end of the first domain identifier.
In some embodiments, the first field is identified as a value greater than or equal to 0 and less than or equal to 255.
Fig. 9 shows a schematic structural diagram of a receiving end 120 according to an embodiment of the present application. The receiving end 120 includes:
the receiving module 901 is configured to receive a DMX packet, where the DMX packet includes target data and a first domain identifier, and the first domain identifier is used to mark a target receiving end that parses the target data;
the parsing module 902 is configured to parse the target data if the first domain identifier is the same as the second domain identifier, where the second domain identifier is used to mark the receiving end 120.
In some embodiments, the DMX data includes a start frame and a plurality of data frames; a specific data frame of the plurality of data frames is used to mark the first domain identification, and the receiving end 120 is further configured to:
acquiring a first domain identifier from a starting frame; or alternatively, the first and second heat exchangers may be,
a first domain identification is obtained from a particular data frame.
In some embodiments, the receiving end 120 is further configured to:
receiving the submitted second domain identification; or alternatively, the first and second heat exchangers may be,
and receiving the second domain identifier notified by the transmitting end, wherein the transmitting end is used for transmitting the DMX data packet.
Fig. 10 shows a schematic diagram of an electronic device provided in an embodiment of the present application. As shown in fig. 10, the electronic device 10 of this embodiment includes: a processor 1000, a memory 1001 and a computer program 1002 stored in the memory 1001 and executable on the processor 1000. The steps performed by the transmitting end or the receiving end in the above-described method embodiments are implemented when the processor 1000 executes the computer program 1002, for example, S201-S203 shown in fig. 2, S501-S502 shown in fig. 5. Alternatively, the processor 1000 implements the functions of the modules in the above-described embodiments of the apparatus, such as the functions of the acquisition module 801, the generation module 802, and the transmission module 803 shown in fig. 8, and the functions of the reception module 901 and the analysis module 902 shown in fig. 9, when executing the computer program 1002.
By way of example, the computer program 1002 may be partitioned into one or more modules, which are stored in the memory 1001 and executed by the processor 1000 to complete the present application. One or more of the modules may be a series of computer program instruction segments capable of performing particular functions for describing the execution of the computer program 1002 in the electronic device 10. For example, the computer program 1002 may be divided into a synchronization module, a summary module, an acquisition module, and a return module (modules in the virtual device), each of which specifically functions as follows:
the electronic device 10 may be a desktop computer, a notebook computer, a palm computer, a cloud server, or the like. Electronic devices may include, but are not limited to, processor 1000, memory 1001. It will be appreciated by those skilled in the art that fig. 10 is merely an example of the electronic device 10 and is not intended to limit the electronic device 10, and may include more or fewer components than shown, or may combine certain components, or different components, e.g., the electronic device may further include an input-output device, a network access device, a bus, etc.
The processor 1000 may be a central processing unit (Central Processing Unit, CPU), other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 1001 may be an internal storage unit of the electronic device 10, such as a hard disk or a memory of the electronic device 10. The memory 1001 may also be an external storage device of the electronic device 10, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the electronic device 10. Further, the memory 1001 may also include both an internal storage unit and an external storage device of the electronic device 10. The memory 1001 is used for storing computer programs and other programs and data required for the electronic device. The memory 1001 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated modules, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the flow in the methods of the above embodiments, or may be implemented by a computer program to instruct related hardware, and the computer program may be stored in a computer readable storage medium, where the computer program when executed by a processor may implement the steps of each method embodiment described above. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, executable files or in some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth. It should be noted that the content of the computer readable medium can be appropriately increased or decreased according to the requirements of the jurisdiction's jurisdiction and the patent practice, for example, in some jurisdictions, the computer readable medium does not include electrical carrier signals and telecommunication signals according to the jurisdiction and the patent practice.
The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (8)
1. A method of transmitting digitally multiplexed DMX data packets, the method being applied at a transmitting end, the method comprising:
setting a value range of the domain identifier;
acquiring target data and a first domain identifier, wherein the first domain identifier is used for marking a target receiving end for analyzing the target data, the first domain identifier is in a value range of the domain identifier, and the first domain identifier is obtained by the transmitting end receiving the target receiving end;
setting the position of the first domain identifier, wherein the position comprises a starting frame or a specific data frame in a DMX data packet;
generating the DMX data packet, wherein the DMX data packet comprises the target data, and the DMX data packet comprises the first domain identifier at the position;
and sending the DMX data packet to the target receiving end.
2. The method of claim 1, wherein the method further comprises:
determining the first domain identifier for marking the target receiving end;
and notifying the target receiving end of the first domain identifier.
3. The method of claim 1 or 2, wherein the first field is identified as a value greater than or equal to 0 and less than or equal to 255.
4. A method of receiving digitally multiplexed DMX data packets, the method being applied at a receiving end, the method comprising:
receiving a second domain identifier and sending the second domain identifier to a transmitting end, wherein the second domain identifier is used for marking the receiving end, and the second domain identifier is in the value range of the domain identifier;
receiving a DMX data packet, wherein the DMX data packet comprises target data and a first domain identifier, and the first domain identifier is used for marking a target receiving end for analyzing the target data; setting the position of the first domain identifier, wherein the position comprises a starting frame or a specific data frame in the DMX data packet;
acquiring the first domain identifier from the position of the DMX data packet;
and if the first domain identifier is the same as the second domain identifier, analyzing the target data.
5. The method of claim 4, wherein the receiving the second domain identification comprises:
and receiving the submitted second domain identification.
6. A device control system, wherein the system comprises a transmitting end and a receiving end;
the transmitting end is used for setting a value range of the domain identifier; acquiring target data and a first domain identifier, wherein the first domain identifier is used for marking and analyzing a target receiving end of the target data, the first domain identifier is in a value range of the domain identifier, the first domain identifier is submitted by the transmitting end to the target receiving end, the position of the first domain identifier is set, the position comprises a starting frame or a specific data frame in a DMX data packet, a digital multiplexing DMX data packet is generated, the DMX data packet comprises the target data, the DMX data packet comprises the first domain identifier at the position, and the DMX data packet is transmitted to the target receiving end;
the receiving terminal is used for receiving a second domain identifier and sending the second domain identifier to the transmitting terminal, the second domain identifier is used for marking the receiving terminal, and the second domain identifier is in the value range of the domain identifier; and receiving the DMX data packet, setting the position of the first domain identifier, wherein the position comprises a starting frame or a specific data frame in the DMX data packet, acquiring the first domain identifier from the position of the DMX data packet, and analyzing the target data if the first domain identifier is the same as the second domain identifier.
7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method of any one of claims 1 to 3 or the steps of the method of claim 4 or 5 when the computer program is executed.
8. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method of any one of claims 1 to 3 or the steps of the method of claim 4 or 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310575641.9A CN116320096B (en) | 2023-05-22 | 2023-05-22 | Method and equipment control system for sending and receiving DMX data packet |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310575641.9A CN116320096B (en) | 2023-05-22 | 2023-05-22 | Method and equipment control system for sending and receiving DMX data packet |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116320096A CN116320096A (en) | 2023-06-23 |
| CN116320096B true CN116320096B (en) | 2024-04-05 |
Family
ID=86824305
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310575641.9A Active CN116320096B (en) | 2023-05-22 | 2023-05-22 | Method and equipment control system for sending and receiving DMX data packet |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116320096B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102065081A (en) * | 2010-11-21 | 2011-05-18 | 杨铁军 | Enhanced DMX (Digital Multiplex) 512 communication control method by using LID (Logical Identifier) |
| JP2015185451A (en) * | 2014-03-25 | 2015-10-22 | 東芝ライテック株式会社 | Illuminating fixture and illumination control system |
| CN208905237U (en) * | 2017-12-29 | 2019-05-24 | 欧普照明股份有限公司 | A kind of lighting system |
| WO2022266696A1 (en) * | 2021-06-21 | 2022-12-29 | Electrical Engineering Solutions Pty Ltd | Multi-drop poe network for power distribution and communication |
-
2023
- 2023-05-22 CN CN202310575641.9A patent/CN116320096B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102065081A (en) * | 2010-11-21 | 2011-05-18 | 杨铁军 | Enhanced DMX (Digital Multiplex) 512 communication control method by using LID (Logical Identifier) |
| JP2015185451A (en) * | 2014-03-25 | 2015-10-22 | 東芝ライテック株式会社 | Illuminating fixture and illumination control system |
| CN208905237U (en) * | 2017-12-29 | 2019-05-24 | 欧普照明股份有限公司 | A kind of lighting system |
| WO2022266696A1 (en) * | 2021-06-21 | 2022-12-29 | Electrical Engineering Solutions Pty Ltd | Multi-drop poe network for power distribution and communication |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116320096A (en) | 2023-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5599731B2 (en) | Lighting system settings | |
| EP2179521B1 (en) | Method, system and device for transmitting lighting device data | |
| US20060109203A1 (en) | Method for the allocation of short addresses in illumination systems | |
| US11134554B2 (en) | Control method for combined lamp, and illumination system | |
| CN107078800A (en) | Method and apparatus for transmitting safe VLC identifiers | |
| CN104956768A (en) | Requesting information from lighting devices | |
| CN107919934A (en) | A kind of clock and clock correcting method | |
| CN103558670B (en) | Port lamp-flashing system and method in intelligent ODN system | |
| CN111654844A (en) | Device pairing method and related device and device | |
| CN116320096B (en) | Method and equipment control system for sending and receiving DMX data packet | |
| KR20150032765A (en) | Dimming control system | |
| CN113259205B (en) | Method and system for testing internal interconnection interface of multi-board system | |
| CN102694598B (en) | Coding method and transmission method of visible light signals | |
| CN110710330B (en) | Automatic address allocation apparatus and method for serially connected devices | |
| CN111615242B (en) | Lamp, controller and lamp dimming method | |
| EP3042490B1 (en) | Device, method and network for internet protocol communication over a dmx network | |
| CN112364781B (en) | Intelligent lamp, signal self-adaptive identification method thereof and computer readable storage medium | |
| CN218276958U (en) | Miniature wireless concentrator | |
| US20140199071A1 (en) | Method of processing dmx-vlc address using dmx-512 network and device using the same | |
| CN113056067B (en) | Illumination parameter transmission method, transmission device, server and storage medium | |
| CN112153442A (en) | Playing method, device, terminal, television equipment, storage medium and electronic equipment | |
| KR20130086516A (en) | Visible light communication method using dmx-512 newtork and apparatus for the same | |
| CN210199821U (en) | Intelligent terminal based on internet government affair service system | |
| CN111756607B (en) | Message transmission method and device | |
| CN115665951A (en) | Intelligent lamp control system, control method and dimming method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 518000 floor 2-4, building 21, Longjun Industrial Zone, Jiuwo, Longping community, Dalang street, Longhua District, Shenzhen City, Guangdong Province Applicant after: Shenzhen Aitushi Innovation Technology Co.,Ltd. Address before: 518000 floor 2-4, building 21, Longjun Industrial Zone, Jiuwo, Longping community, Dalang street, Longhua District, Shenzhen City, Guangdong Province Applicant before: APUTURE IMAGING INDUSTRIES Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |