{"id":7437,"date":"2026-10-15T11:50:00","date_gmt":"2026-10-15T03:50:00","guid":{"rendered":"https:\/\/www.ledpointlight.com\/?p=7437"},"modified":"2026-10-14T18:20:21","modified_gmt":"2026-10-14T10:20:21","slug":"how-to-create-a-dmx-address-schedule-for-led-point-light-sources-on-a-building-facade","status":"publish","type":"post","link":"https:\/\/www.ledpointlight.com\/fr\/blog\/how-to-create-a-dmx-address-schedule-for-led-point-light-sources-on-a-building-facade\/","title":{"rendered":"How to Create a DMX Address Schedule for LED Point Light Sources on a Building Facade"},"content":{"rendered":"

The DMX address allocation takes up space within the handover documentation from which one could use it to pinpoint the exact channel used by the controller. Simply putting all those numbers in an organized column form will not suffice since it needs to correlate with the location, the way of connection, output, universe, and wiring itself.Draft the schedule when the facade planning is underway and then test the mapping of the representative assembly against the ordered LED point light source. Then update the record with whatever actually changed during commissioning.<\/p>\n

\"How<\/figure>\n

Which Fixture Details Must Be Confirmed First<\/h2>\n

The fixture’s control mode determines how addresses are allocated. For example, the XH-H3003 point light source<\/strong><\/a> specification lists a monochrome on-off version and an RGB DMX512 version. The family name therefore does not identify the control configuration by itself. Validate the complete ordered model, channel configuration, and address assignment with the supplier. In case a decoder is included in your order, also confirm the channel configuration for it. Never assume the above based only on the fixture color description.<\/p>\n

Give every physical position its own ID<\/h3>\n

Choose location codes that a person on site can read against the elevation drawing. The code may combine elevation, bay and node position. Mark the starting corner and counting direction, particularly where the cable turns between rows. The physical ID will be kept separate from the DMX ID. The record must reflect where the fixture is located physically within the building and how to access it by a technician even if it changes output locations.<\/p>\n

What Information Belongs in Each Schedule Row<\/h2>\n

Record the location ID, exact fixture variant, controller and output, universe, start address and channel footprint. Include the power zone and cable label so a technician can trace both circuits. Leave fields for the tested address and drawing revision. For grouped fixtures, state which physical positions share the group. Two installers reading the same row should identify the same lights without asking the programmer to interpret it.<\/p>\n

Work through a channel allocation example<\/h3>\n

In terms of basic calculation, assuming that the supplier guarantees the occupancy of three consecutive slots for the RGB node where slot 1 is for Red, slot 2 is for Green, and slot 3 is for Blue. So for node 1 which starts from slot 1, then slot 2 and slot 3 would be used up until the next node will begin on slot 4. For a 512-slot universe, there are 170 nodes starting from slot 1 until slot 510. This calculation is just an example and does not determine the footprint of the XH-H3003 system.<\/p>\n

How Should the Schedule Follow the Cable Route<\/h2>\n

Walk the route on the drawing from the controller output to the final node. Note junctions, changes of direction and any points where the control design divides the run. A visual row can cross a window opening while its cable takes a longer route around the frame. Show that route explicitly. Address order and the order in which pixels appear in an image are related, but they do not have to be identical. The controller mapping must explain the relationship.<\/p>\n

Agree how universe boundaries will be handled<\/h3>\n

Mark the last allocated fixture on one universe and the first on the next. Verify that each channel footprint fits within the assigned range. Where the controller uses a different numbering convention, include its displayed value in the schedule. Also check for duplicated assignments within a universe. Any deliberate duplication should be identified as a group; otherwise a test may light two positions when the installer expects one.<\/p>\n

What Should a Representative Test Assembly Prove<\/h2>\n

Build a section using the ordered fixtures and intended controller configuration. Include a change of direction or a universe boundary if those are important to the facade. The Classic H series point light sources<\/strong><\/a> offer different product configurations, so the test sample must match the approved order. Send red, green and blue separately, then address each position in sequence. Record which physical node responds to each entry. Check the last position as carefully as the first.<\/p>\n

Use a moving single-node pattern<\/h3>\n

A chase moving one lit point through the section makes reversed or skipped positions easier to see. Compare the movement with the schedule and marked drawing. If it changes direction at the wrong bay, first check the cable sequence and mapping. Save the verified test file and its settings for site commissioning. A decorative animation can look acceptable while concealing an incorrect position, particularly on a sparse facade viewed from a distance.<\/p>\n

How Should Installers Record Commissioning Changes<\/h2>\n

Issue a controlled copy of the schedule for each work area. Before testing, compare the cabinet and cable labels with that copy. Record the observed response of each node or group, including any swapped positions. The electrical test should be done following the approved site procedure. In case of several faulty lights, check the power source that they share before checking every single node. The published guide to DMX512 facade pixel lights that are not responding<\/strong><\/a> discusses the distinction between control and power symptoms.<\/p>\n

Update the files after each approved change<\/h3>\n

An address changed on site needs a matching update in the schedule and controller configuration. Make sure that the date, the location affected, and the approval authority of the change are documented. The previous version should be archived separately from the new installation. When transferring the system, provide both the modifiable and read-only versions together with elevations and controller backups. Make sure you identify the software version capable of opening the backup and its owner.<\/p>\n

\"How<\/figure>\n

How Can Xinhe Support Fixture Selection<\/h2>\n

Opto\u00e9lectronique Xinhe<\/strong><\/a> develops and supplies point light sources for architectural landscape and advertising lighting. Its published services include scheme design, product supply and on-site guidance. Ask the company to confirm the control information for the ordered fixture before completing the address table. Share the controller specification and proposed wiring arrangement so any compatibility questions can be addressed at that stage.<\/p>\n

Conclusion<\/h2>\n

Use three references when checking the schedule: the ordered fixture mode, the physical elevation and the saved controller map. If they disagree, stop at a representative assembly and settle the mapping there before repeating it. Keep the record current as installation proceeds. At handover, a maintenance technician should be able to identify a node and restore its control assignment from the project files without rebuilding the whole map.<\/p>\n

FAQs<\/h2>\n

Can the final address schedule be written before choosing fixtures<\/h3>\n

Reserve zones and outputs early, but finalize addresses after confirming the fixture mode and channel footprint. Different modes can require different allocations.<\/p>\n

Why do two point lights respond to the same command<\/h3>\n

Check for a shared address or deliberate group in the controller map. Test the physical positions against the schedule before changing assignments.<\/p>\n

What should be recorded when a point light is replaced<\/h3>\n

Keep its physical ID, replacement model and configured address. Test the affected position and update the maintenance record, including any configuration change.<\/p>","protected":false},"excerpt":{"rendered":"

Create a DMX address schedule for facade LED point lights by mapping fixture IDs, channels, universes, cable routes, tests, and commissioning changes.<\/p>","protected":false},"author":2,"featured_media":7436,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[41],"tags":[],"class_list":["post-7437","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/posts\/7437","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/comments?post=7437"}],"version-history":[{"count":2,"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/posts\/7437\/revisions"}],"predecessor-version":[{"id":7447,"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/posts\/7437\/revisions\/7447"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/media\/7436"}],"wp:attachment":[{"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/media?parent=7437"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/categories?post=7437"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ledpointlight.com\/fr\/wp-json\/wp\/v2\/tags?post=7437"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}