Documentation · v1.20
PROMIN Controller User Guide
Browse the PROMIN controller user guide with structured chapters, commissioning workflow, troubleshooting notes, and quick on-page navigation.
1. Introduction: how the interface is organized
The Promin interface consists of working pages where the engineer builds and checks the project, and the Settings screen where the basic controller, network, calibration, and service parameters are configured.
This guide first describes the main working pages of the interface: where to check status, how to place fixtures, perform patching, configure scenarios, schedules, and user screens. The Settings screen is moved to the end of the document so it can be used conveniently as a separate service section.
- Use Dashboard to check controller status, logs, DMX / Art-Net output, HDMI snapshots, RDM, network devices and relay modules.
- Layout and Patch are used for fixture placement and address assignment.
- Timeline, Triggers, Scripts, and Calendar provide playback, automation and scheduling.
- User interface is used when you need to prepare an operational control screen.
- Open Settings when you need to configure the controller itself, the network, calibration, users, or firmware.
2. What should be prepared before you start
Before working with the Promin interface, it is advisable to collect all initial site data in advance. This greatly speeds up commissioning and reduces the risk of repeated setup.
- The name of the controller or site under which the device should appear in the system.
- LAN network parameters: DHCP or static IP, IP address, subnet mask, gateway.
- Art-Net network parameters.
- The site's time zone and whether daylight saving time is required.
- The fixture type and RGB channel order.
3. First start
Connect the engineer's computer or phone to a network that can reach the controller. In a browser, open the controller address provided for the installation and sign in with an authorized administrator account. Review and accept the License Agreement if the controller requests it. If the address is unknown, ask the site administrator or installer; the address depends on the network configuration.
3.1. What pages and sections are available in the interface
| Page / tab | Purpose | When the engineer usually goes here |
|---|---|---|
| Dashboard | Controller status, logs, DMX / Art-Net output, HDMI input snapshots, RDM, network devices, relay modules, and service information. | During site verification, troubleshooting, or the final check. |
| Layout | Creating fixture layouts and groups, placing pixels on the grid, setting fixture types, and highlighting selected pixels on physical outputs. | When you need to create or modify the mapping. |
| Patch | Assigning addresses and output parameters for groups: DMX / Art-Net, universe, broadcast, IP address, and the actual fixture placement within channels 1–512. | When patching by channels is required after the layout has been created. |
| Timeline | Creating timelines with media, effects, live video or audio input, flags, layout preview, and synchronization settings. | When you need to configure or check playback of a show, scenes, or media content. |
| Triggers | Configuring events and actions, including timeline playback, digital I/O, TCP/UDP, RS232, incoming parameters, HTTP requests, and scripts. | When external signals or internal events on the site must be linked to controller actions. |
| Scripts | Creating, editing, running, and debugging JavaScript automation; managing the Global script and consulting the API reference. | When custom logic, calculations, or integrations are needed. |
| Calendar | Configuring schedules and calendar events: one-time and recurring events, links to soft triggers and UI buttons, and manual testing via Run. | When the site must launch scenarios by time, date, week, or astronomical events. |
| User interface | Building customer screens, buttons, and Color Picker screens; configuring appearance, trigger bindings, and preview. | When you need to prepare the operational control screen or link interface buttons to project logic. |
| File Manager | Uploading and managing images and videos used by interface and layout backgrounds. | When preparing or managing files used in the project. |
| Settings - Controller | Controller name, audio output, HDMI input assignments, native RDM, timeline FPS, location, time, backup, and project import. | On almost every new site. |
| Settings - Users | Adding, blocking, and deleting users, and changing passwords. | Usually only during site handover or when responsible staff changes. |
| Settings - Network | LAN, Art-Net, Wi-Fi, RS232, and UDP/TCP socket settings. | At the start of commissioning or when the network design changes. |
| Settings - RGBW Calibration | RGBW and RGBCW calibration, test preview, checking correct addresses and RGB order. | When fixtures are connected and you need to achieve the correct white. |
| Settings - Firmware | Checking for updates, running an update, or rolling back firmware. | After initial startup or for a service task. |
| Settings - Cloud | Connecting the controller to Promin Cloud and configuring synchronization. | When connecting the controller to the cloud or changing synchronization settings. |
3.2. License Agreement
When logging in for the first time, you must review and accept the License Agreement before accessing the controller interface. Read the agreement, select the confirmation checkbox, and click Accept and continue. If updated terms require acceptance, the controller may request confirmation again.
4. Recommended commissioning sequence
To avoid returning to the same points repeatedly, it is convenient to proceed in this order:
- Open Settings - Controller and set the site name, location, time zone, and time.
- Go to Settings - Network and configure LAN and Art-Net.
- If the fixture map needs to be changed, go to the Layout page and bring the layout up to date.
- Then open the Patch page and assign addresses and output parameters for groups.
- If external serial equipment is used, configure RS232.
- If the project works with RGBW or RGBCW fixtures, go to RGBW Calibration and perform calibration.
- If playback scenarios are used on the site, open the Timeline page, select the required layout, check the clips, and run Bake after major changes.
- If buttons, digital inputs, RS232, TCP/UDP commands, or automatic start chains are used on the site, open the Triggers page and configure the required events and actions.
- If the site should work on a schedule, open the Calendar page, create events, check recurrence rules, and verify related bindings.
- If an operational user screen is needed, open the UI page, configure screens and buttons, and then check the result in Preview.
- Open Dashboard and check the controller status, and if necessary view the live DMX / Art-Net monitor.
- Check the Firmware tab and decide whether an update is required before site handover.
- Create a project backup via Save backup.
- If necessary, create or verify users in the Users tab.
If the project uses relay modules or HDMI inputs, add or check the modules under Dashboard → Network, assign capture devices under Settings → Controller, and verify the corresponding trigger or timeline behavior. If custom automation is required, prepare and test the relevant scripts.
5. Dashboard page
The Dashboard page is intended for quickly checking the current status of the controller and troubleshooting. It is the main diagnostic screen that is useful to return to during commissioning and site handover.
5.1. Status tab
The Status tab is suitable for a quick verification that the correct basic data is recorded on the controller.
- Check the controller name, location, time zone, and DST status.
- Verify the coordinates if the site uses geographic parameters.
- Review the time of the last settings update.
- Check the Notes block if it stores service notes for the site.
Working actions are available on the right or at the top of the tab:
- Refresh refreshes the status data.
- Reboot sends the controller for reboot.
- Schedule on / Schedule off enables or disables execution of the calendar schedule.
The Schedule off button is useful during commissioning when you need to temporarily exclude the effect of the schedule on the site. Before handover, make sure the schedule is returned to the required state.
5.2. Logs tab
The Logs tab helps you understand what happened on the controller: events, messages, and possible errors. You can also use filters to quickly find the required log entry.
Use it if something on the site is operating unstably and you need to review the latest events.
The filter panel allows you to narrow down the log list by:
- Search — searches by message text, UID, PID, device, or error details.
- Source — shows entries generated by a specific controller subsystem.
- Level — filters logs by severity, such as information, warning, or error.
- Event Type — shows only entries related to a specific operation or event.
- Actor — filters events performed by a particular administrator, user, or system process.
- From / To — limits results to a selected date and time range.
Click Apply filters to update the list. Click Reset to clear all selected filters.
Refresh reloads the log list.
The First / Previous / Next / Last navigation lets you move through journal pages.
Clear logs permanently clears the journal.
5.3. DMX Out tab
The DMX Out tab shows a live output monitor. It is one of the most useful engineering screens for quickly checking whether the controller is actually outputting data right now.
- Select the required output in the Output field.
- Check the Runtime: Live / Offline indicator.
- Review the number of active channels, peak level, and the time of the last update.
- In the Selected Output block you can verify which output and which scope the signal is going to.
- The 512 Channels grid shows the actual levels of all channels on the selected output.
This tab is especially useful when you need to understand:
- whether there is any outgoing DMX / Art-Net signal at all;
- whether transmission is going to the correct universe or output;
- whether the required channels show activity;
- whether the problem is in the controller or farther down the communication line / inside the fixture.
5.4. RDM tab
5.4.1. Purpose and interface
RDM (Remote Device Management) provides two-way communication with compatible DMX devices. In Dashboard → RDM, the controller discovers responders, reads their supported parameters and, where permitted by the device, sends parameter changes. RDM is available through compatible Art-Net gateways or the controller’s native DMX outputs; the available controls depend on the route and device.
The summary shows RDM status, Controller UID, last update, and counts of gateways, RDM ports, responders, project devices, devices needing attention, stale entries and protocol errors. Refresh snapshot updates the displayed snapshot; it does not start discovery or necessarily read every parameter again.
The tree separates Project devices, which are registered for monitoring, from Discovered gateways and responders. Expand a gateway and its output port to locate a responder, then select a gateway, port, responder or project device to see its details. A responder’s UID uniquely identifies the device; its label can be changed and need not be unique.
RDM dashboard: controller summary and the gateway and responder tree.
5.4.2. Discover gateways and responders
- Connect and power the RDM-compatible devices, and check the DMX wiring and termination. For an Art-Net route, verify that the gateway is reachable, its output is configured correctly, and RDM is supported and enabled on the route.
- Open Dashboard → RDM and expand the gateway in Discovered gateways and responders. Select the intended output port, checking its physical port and Port-Address so that commands are sent on the correct line.
- For an Art-Net port, select Refresh TOD to update the gateway’s Table of Devices. For a native DMX port, the corresponding action may be labelled Discover responders. Wait for discovery to finish and expand the port to see the discovered UIDs.
- Select a responder and check its UID, manufacturer, model, label and online state. If necessary, use Identify to find the physical fixture; turn identification off afterwards.
- Select Refresh capabilities on the responder, or Capability scan on the port, to update the supported-parameter information. Different devices can expose different parameters.
Refresh all ports requests a TOD update for the selected gateway’s available ports. Full rediscovery clears the cached device list for the selected port and performs a complete scan; it can interrupt normal communication on that line. Use it when a regular refresh does not resolve a discovery problem, and confirm the operation when prompted. Responder operations on a port are temporarily unavailable while its discovery is running.
For Art-Net ports, Incremental discovery override offers Auto, On and Off for background discovery when supported. Changes are confirmed through subsequent gateway status observations; do not assume a requested setting has taken effect until the interface reports it.
5.4.3. Responder information and capabilities
Select a discovered responder. Overview shows its UID, label, manufacturer, model, DMX address, footprint, personality, last response, capability-scan status and any warnings. DMX shows the values available for DMX address and operating mode. Parameters contains the individual RDM parameter IDs (PIDs); Sub-devices, Status & Sensors, Network and Diagnostics provide additional device-specific functions and information.
A capability scan describes what the controller knows about the responder. Supported, not advertised, unsupported and error states do not all mean the same thing. A scan with warnings can still return useful values; inspect Diagnostics and the RDM logs for details. Availability of a GET or SET command depends on the selected parameter and the responder, not just on the presence of its name in the list.
5.4.4. Read a parameter (GET)
- Select the responder in the discovered tree and open Parameters. Use the Supported, All, Read only, Writable, Unsupported or Error filter to narrow the list, then select the required PID.
- Check that GET is available. Cached value is the most recently stored value known to the controller; it is not necessarily a fresh response from the device.
- In the Read area, supply the requested fields if this PID requires a request payload. If the interface says the command has no parameter payload, no additional field is needed.
- Click Read to issue GET to that responder. Wait for the response and review the returned value or error. For example, select DMX_START_ADDRESS and Read to obtain the reported starting address.
An empty cached value, a timeout or a NAK does not establish the current device value. Verify the route, device support and response in Diagnostics or View RDM logs, then retry where appropriate. A snapshot refresh and a new GET serve different purposes.
5.4.5. Send a parameter (SET)
- Select the correct responder by UID and open Parameters. Select a writable PID and check that SET is available. Read the existing value first when it is important to know the starting state.
- In Apply typed value, enter the new value in the fields shown for that PID. The fields, allowed values and any required confirmation vary with the parameter and the device. For DEVICE_LABEL, enter the label within the byte limit displayed by the interface. For DMX_START_ADDRESS, enter the intended starting address, allowing room for the device’s footprint and avoiding unintended overlap.
- Click Apply and confirm the operation if requested. Wait for the result; if a SET fails or times out, inspect the message and logs rather than assuming the change succeeded.
- Use Read to request the value again and verify what the responder reports. Check the physical device or its effect when appropriate.
Changing a DMX address or personality can change the occupied channel range and affect the patch and output. Changing network parameters or applying network configuration can interrupt communication. Plan such changes before applying them, then verify the actual route, patch and device state. Read-only PIDs have no SET; a parameter that is not supported by a responder cannot be made writable through the interface.
5.4.6. Add a responder to the project
Discovery makes a responder visible; it does not by itself register it as a project device. To add it, expand its gateway and port, select the discovered responder, verify its UID and current DMX configuration, and choose Add to project. Complete any fields or confirmation presented by the interface. The device then appears under Project devices; a responder that is already registered shows its project-device status instead of Add to project.
Select the project entry to compare Expected configuration with Actual configuration. These include the route, DMX range and footprint/personality where available. A changed address, operating mode or route can produce a mismatch or a Needs attention state. Establish why the difference occurred before accepting the actual configuration as the new expected state.
Layout diagnostic mapping associates the registered device with the appropriate layout/pixel for diagnostics. Review the suggested automatic mapping or select the appropriate mapping mode and target, then use Apply mapping. Check the DMX overlap shown in the diagnostic: registration and mapping do not themselves change the fixture’s DMX address or replace patch configuration. Open responder returns to the live responder; Remove from project removes the registration after confirmation.
5.4.7. Sub-devices, sensors and broadcast
Some responders contain numbered sub-devices. In Sub-devices, choose a PID and specify the first or single sub-device; use Single GET or Single SET for one sub-device. Bulk GET or Bulk SET uses a count and, for a write, a typed value for each sub-device. These operations depend on the responder, gateway and selected PID; consult the device documentation and check the returned result.
Status & Sensors provides the supported status, sensor and related parameter operations. Some are read-only; others require a confirmed write. Network contains network-related parameters where supported. The fields and availability depend on the device, and some changes may disrupt the connection.
Broadcast SET on a port sends a write to multiple responders on that line. Individual responders do not send normal per-device confirmation for a broadcast, so its apparent completion does not prove that every device accepted the value. Use it only when all affected devices and the selected value are known; verify important changes on individual responders afterwards.
5.4.8. Diagnostics and troubleshooting
If the gateway is absent or offline, check the Art-Net network, gateway power and settings. If the gateway is visible but a responder is missing, verify the selected port and Port-Address, RDM support, wiring, termination, device power and discovery state; then update the TOD or run discovery. An ordinary DMX-only device will not respond to RDM requests.
Stale information means that the displayed data may be out of date; check the last update and last response. Port diagnostics show discovery state, responder count and error, timeout and NAK counters. A NAK is a negative response, while a timeout means a response was not received in time. Use the responder’s Diagnostics and View RDM logs to investigate the affected UID and operation.
If a project device needs attention, compare Expected and Actual configuration and inspect layout mapping before changing the project. If a SET appears ineffective, read the parameter again, check the response and the device’s supported features, and verify the physical result. Do not repeatedly issue disruptive commands while discovery or another operation is in progress.
5.5. Network tab
The Network tab shows the current network status of the controller and the connected Art-Net environment. It displays the controller’s LAN and Art-Net IP configuration, including whether each interface is using DHCP or a static address. The tab also shows the last update time and allows the user to manually refresh the network overview.
Below the summary, the tab lists all detected Art-Net devices. For each device, it shows the device name, IP address, short name, input and output universes, Net/Subnet values, firmware version, MAC address, bind IP, last seen time, and node report when available.
If no Art-Net devices are found, the tab indicates that no devices are currently reachable and suggests checking that the devices are powered on and connected to the Art-Net interface.
5.5.1. Remote modules
Dashboard → Network → Modules provides access to compatible Promin remote modules. Use Scan network to discover available modules, add the required module and assign it a unique name. The module card shows its connection state and, when available, provides access to the module’s settings and channels.
The available inputs, outputs, functions and configuration options depend on the module model. Refer to the separate instruction for the specific remote module for connection, setup, supported features and operation.
5.6. HDMI input
Open Dashboard → HDMI input to inspect a snapshot of HDMI 1 or HDMI 2. Select the input and click Refresh to capture a new frame; the image does not update automatically. The snapshot shows the complete input before layout placement, calibration and fades. If it is unavailable, check the capture card, USB connection, assignment and video mode in Settings → Controller.
5.7. About tab
The About tab displays the installed software version, the agreement revision, legal information, and third-party notices. Use it to check the version and review the terms associated with the controller.
5.8. API tab
The API tab is service-oriented. It contains documentation on how commands can be sent to the controller from other devices, interfaces, applications, and so on using HTTP requests.
6. Layout page
The Layout page is used to create and edit the fixture scheme on a grid. Here the engineer forms or corrects the fixture map: layouts, groups, point positions, and their types.
When to go here
Open Layout only if you really need to change the fixture map, address layout, or placement scheme. If the layout is already approved and working, it is better not to change it unnecessarily.
6.1. Top layouts panel
The very top of the page contains switching between different layouts.
- The + button creates a new layout.
- You can switch between layouts using the tabs.
- A layout name can be renamed by double-clicking the name.
- An unnecessary layout can be removed by clicking the cross.
- The Layout page should be viewed as a way to create new control zones, allowing scenes in each zone (Layout) to be switched independently.
6.2. Left Groups panel
The left panel is used to work with fixture groups.
- Search filters groups and pixels by group name and by x and y coordinates.
- Add group creates a new group.
- Expand all and Collapse all expand or collapse all group lists.
- Each group name can be changed.
- Each group has a delete button.
- Inside a group you can use Select all, Unselect, or delete the selected pixels in that group.
Groups should be treated as physical DMX bus connection groups. All fixtures are addressed automatically when added; the address can be changed on the Patch page.
6.3. Right Fixtures and Properties panel
The right panel contains Layout Properties, Fixtures and Properties. Layout Properties contains the grid size, background settings, channel usage and pointer position. Fixtures selects the type for new points; Properties shows the selected pixels.
- In the Fixtures block, the fixture type is selected, for example White, RGB, RGBW, RGBCW, and other channel-order variants.
- In the Properties block, you can view the properties of the selected pixels.
- If one fixture is selected, you can usually change its Name.
- Coord. X and Coord. Y show the coordinates of the selected point.
- Type lets you change the type of the selected fixture or a group of selected fixtures.
- Address is displayed for reference but is edited on the Patch page.
6.4. Central workspace
The center of the page contains the main workspace where the fixture map is drawn.
- Grid in the right Layout Properties panel sets the size of the working grid.
- Group defines which group new points will be added to.
- Tool switches between Draw (to add fixtures) and Select (to select fixtures).
- Fill, when enabled, automatically fills the selected area according to the pattern chosen on the right. When disabled, fixtures are added according to the mouse cursor position.
- Undo and Redo allow you to revert and restore actions.
- Center centers the workspace.
- Fullscreen expands the workspace to full screen.
- Clear Sel clears the current selection.
- Clear clears the layout.
- Export PNG saves the layout map as a PNG.
- The Channels indicator shows the total channel usage.
- The Image tool is used to move the layout background image on the grid.
- The Background selector in the right Layout Properties panel selects an image from the File Manager as a layout reference background.
- Reload refreshes the list of available background images from the File Manager.
- When a background image is selected, Visible shows or hides it, and Lock prevents it from being moved accidentally.
- Opacity controls background transparency.
- W, H, X, and Y define the background image size and position on the grid.
- Fit scales and positions the background image to match the full grid.
- Clear Bg removes the background image from the current layout.
- Del Sel deletes the selected fixtures from the layout.
- The Pointer indicator shows the current cursor position on the grid.
6.5. Highlight selected pixels
To identify fixtures on the installation, select one or more pixels and enable Highlight selection. The selected pixels are sent to the physical outputs at full channel value; other pixels in the current Layout are black while the mode is active. An empty selection makes the whole current Layout black. The active timeline continues running and its current output returns when highlighting is switched off.
Highlight selection and calibration preview cannot be active at the same time. Blackout takes priority. The mode ends when you leave the page or change Layout, and it is not saved as part of the project. Check the patch before using it: fixtures sharing physical channels cannot be controlled independently.
6.6. Basic workflow in Layout
- Create a new layout or select an existing one.
- Create one or more groups for different site zones.
- Select the required fixture type in the right Fixtures panel.
- Select the active group in the Group field.
- Switch to the Draw tool and place points on the grid.
- If the placement needs correction, switch to Select, select the fixtures, and move them.
- If necessary, adjust the names and types of selected fixtures in the Properties panel.
- When finished, save the map using Export PNG if you need to share the scheme or keep it in the site archive.
6.7. Practical mouse and keyboard actions
- Mouse wheel or pinch changes the zoom.
- Middle mouse button or a two-finger gesture is used to move the workspace.
- In Draw mode, normal drawing adds fixtures to the grid.
- In Draw mode, deletion is done with Alt + drawing or the right mouse button.
- In Select mode, selecting an empty area creates a box selection.
- Shift helps add new points to the existing selection.
- Dragging selected fixtures moves them on the grid.
- Arrow keys move the selection, and Delete removes the selected points.
- Undo and Redo are best used immediately after a mistaken action instead of trying to restore everything manually.
- In Select mode, dragging an already selected fixture moves the whole selected set.
- In Select mode, dragging a non-selected fixture first selects it and then moves it.
- Shift + Arrow keys moves the selected fixtures by 10 grid cells.
- In Image mode, dragging with the left mouse button moves the layout background image.
- If the background image is locked, it cannot be moved until Lock is disabled.
- Clear Sel removes the current selection without deleting fixtures.
- Del Sel deletes only the selected fixtures.
- Clear deletes all fixtures from the current layout.
6.8. What to pay attention to
- Clear clears the current layout. Use it deliberately.
- Deleting a group is irreversible if you cannot restore it from a backup.
- If the system reports that the channel limit has been reached, reduce the number of active points or revise the layout structure.
- If you edit the layout on a live site, it is better to save a backup of the current project first
7. Patch page
The Patch page is used to patch groups by channels and to select the output parameters of a group. If Layout is responsible for the position of fixtures on the scheme, then Patch is responsible for which channels and which output those fixtures are assigned to.
7.1. What the top bar shows
The top of the page displays short statistics for the current active group.
- Pixels shows the number of fixtures in the group.
- Used shows how many channels are occupied.
- Free shows how many channels are still available in the 1–512 range.
This line is especially useful when you need to quickly understand whether the group fits into a single 512-channel block and how much capacity remains.
7.2. Left Groups panel
The list of all groups available for patching is displayed on the left.
- The search field helps quickly find a group by name.
- Only one group can be active at a time.
- After selecting a group, its patch is displayed in the center and its output configuration on the right.
7.3. Central patching field
The central workspace shows the channel grid from 1 to 512. Each fixture or fixture segment occupies its own channel range in this grid.
- The Zoom slider changes the display scale.
- The blocks in the field correspond to fixtures in the selected group.
- The label on a block helps identify which fixture it is and which address it currently starts from.
- By dragging, a fixture can be reassigned to a different start address.
The easiest way to think about this screen is: you do not draw a layout here; you distribute already created fixtures across DMX / Art-Net channels.
7.4. How to change a fixture address
- Select the required group on the left.
- Find the required fixture or group segment in the field.
- Hold the block and drag it to a new start address.
- Release the block if the new position is correct.
- After that, check that the fixture occupies the expected channel range.
If the new position overlaps with already occupied channels or goes beyond the allowed range, the interface will show a conflict, and that move cannot be considered correct.
7.5. Right Group configuration panel
The right panel defines where the selected group will be output.
- Output switches the output type: DMX or Artnet.
- If DMX is selected, you need to specify the DMX port.
- If Artnet is selected, you can enable or disable Broadcast.
- If broadcast is disabled, you need to fill in the IP address.
- For Art-Net, the Universe is also specified.
7.6. Recommended workflow in Patch
- First prepare the groups and fixtures in Layout.
- Open Patch and select the required group on the left.
- Configure the group's output type: DMX or Artnet.
- If it is DMX, select the correct physical port.
- If it is Art-Net, set broadcast or unicast, IP address, and universe.
- Arrange the fixtures by addresses within the 1–512 grid.
- Check that there are no overlaps and that the number of used channels looks expected.
- When finished, if necessary, go to Dashboard -> DMX Out and verify that the signal is going to the correct channel / output.
7.7. What to pay attention to
- If the group contains many fixtures, it is convenient to first estimate the total channel consumption using the top statistics.
- If the site uses Art-Net unicast, do not forget to disable broadcast and set the IP address.
- If a fixture does not respond after patching, first check the Patch page, and only then move on to the physical line and the fixture itself.
- After changes in the patch, it is convenient to verify the picture on Dashboard -> DMX Out.
8. Timeline page
The Timeline page is used to prepare and check playback scenarios. Here the engineer assembles or controls the sequence of clips, effects, and timing, and then checks how it will be launched on the site.
8.1. Top control bar
The top part of the page is responsible for launching and organizing timelines.
- The current time position is displayed on the left.
- Play/Pause starts and stops playback of the active timeline in the engineer's browser, so you can understand how the effects will work.
- Home returns the playback pointer to the beginning.
- Bake rebuilds timelines after changes.
- Loop enables looping for the active timeline.
- The + button creates a new timeline, and the tabs at the top let you switch between timelines, rename them, reorder them, and delete unnecessary ones.
8.2. Left Library panel
The content library that can be used in the timeline is located on the left.
- Media upload uploads video and audio files.
- Files in the list can be dragged onto tracks in the center area.
- Each file shows its name and duration, so it is easy to verify the required material right away.
- Unneeded files can be removed from the library with the delete button.
- Below is the Effects list, which can also be dragged onto tracks.
8.3. Central Timeline area
The center contains the main time scale with tracks. This is the workspace where you place clips in time.
- At the top there is a time ruler and the current position indicator.
- The Zoom slider changes the scale and helps you work more accurately with short or long clips.
- Below are the video and audio tracks, where you can drag files and effects from the library.
- A clip on a track can be moved in time, and its right edge can be trimmed if you need to change its duration.
- Clicking a clip selects it for precise adjustment on the right in Inspector.
8.4. Right Preview, Properties, and Inspector panel
The right column helps you verify what is currently playing in the engineer's browser and precisely configure the active timeline or selected clip.
- Preview shows the material under the playhead and any overlaid effects.
- The Properties block sets the general timeline parameters: Sync, Layout, Fade in, Fade out, Length, and Auto trim.
- Sync lets you choose internal time or synchronization via Art-Net TimeCode.
- Layout defines which fixture layout the current timeline will work with.
- In the Inspector block for the selected clip, the following fields are available: Kind, Track, File / Effect, Start, Dur, Fade in, and Fade out.
- If an effect is selected, you can also configure Color, Intensity, and Speed Hz here.
- The Delete button removes the selected clip, and Jump quickly moves the pointer to its position on the time scale.
8.5. Layout preview, live input and flags
8.5.1. Layout preview
Layout preview shows the content under the playhead on the selected Layout's pixel mask. Select the Layout in Properties and use Preview Play/Pause to inspect the browser preview. The browser preview is not a command to start playback on controller outputs.
8.5.2. Video and audio input
For a live source, assign a capture card and mode under Settings → Controller → HDMI inputs. Drag Video input to a video track or Audio input to an audio track. In Inspector select HDMI 1 or HDMI 2. For video, Scale to layout maps the complete frame to the grid; Original size · top left (1:1) uses the top-left pixels without scaling. A timeline can contain one live effect of each type; live video and audio on the same timeline share a source, and a live effect cannot be mixed with other clips on tracks of the same type. Bake after editing the effect, then start the timeline using a configured trigger. Live HDMI frames are shown on controller outputs, not streamed into the Timeline browser preview.
8.5.3. Timeline flags
To add a flag, place the playhead at the required time and click Add flag. Select the flag to edit its name and time in Properties, or drag it along the flag lane. Flags are saved without Bake. A running playback uses changes after its next Start. Create a Timeline Flag trigger to react to a selected flag, any flag on one timeline, or any flag on any timeline.
8.6. Recommended workflow in Timeline
- Open the required timeline or create a new one with the + button.
- In Properties, select the correct Layout for this scenario.
- If synchronization with an external time source is needed, configure the Sync field.
- Upload media files via Media upload if they have not yet been added to the library.
- Drag files and effects to the required tracks.
- Check clip positions in time, durations, and fade parameters.
- After changes, click Bake for the active timeline, or Bake all to rebuild all timelines, and wait for the process to finish.
- Use Preview Play/Pause to check the browser preview. Start the timeline through a configured trigger and check the real light output separately.
8.7. What to pay attention to
- If the site must work by external timecode, do not accidentally leave Internal time enabled.
- If the wrong Layout is selected, the playback result may not match the actual layout on the site.
- After noticeable edits to clips, effects, or timeline order, it is better to run Bake again.
- If it seems during verification that nothing is happening, first check which timeline is active and where the time pointer currently is.
9. Triggers page
The Triggers page is used for automation. Here the engineer links a trigger event to a set of actions, for example launching a timeline, sending a command over the network, outputting a signal, or launching another trigger.
9.1. What the top bar shows
The top of the page displays a short summary of the triggers.
- Total shows the total number of triggers.
- Active shows how many triggers are currently enabled.
- If changes are being saved, the Saving... status may appear at the top.
9.2. Left Triggers panel
The list of all created triggers is located on the left.
- The + button adds a new trigger.
- Clicking a list item opens its configuration in the center and on the right.
- Each trigger in the list shows its name, a short event summary, and the number of actions.
- The Run button allows you to manually test the trigger without waiting for an external event.
- You can drag triggers with the mouse to change the list order.
9.3. Central Event block
The Event block defines what activates the selected trigger. Choose the trigger in the left list, configure its event in the center, and define the resulting actions in the right Actions panel. The fields below Event Type change with the selected event.
Trigger ID is the unique identifier of the trigger and can be copied with the button beside it. Name is the label shown in the trigger list. Enable activates or disables the trigger; Description can record its purpose and the expected source of the event. Delete trigger removes the selected trigger, so check references before deleting it.
Soft: used for a software or manual launch. For example, another trigger, script or interface can invoke it. The Run button in the trigger list executes the trigger’s actions, so check those actions before testing.
Controller Start: activates when the controller starts. Use this event for initialization that should take place at startup, and make sure its actions are appropriate each time the controller starts.
Timeline Started and Timeline Finished: activate when the selected timeline starts or finishes. Choose a timeline in the event settings; where Any is offered, it matches the corresponding event from any timeline. Choose a specific timeline when the action must be limited to one scenario.
Timeline Flag: activates when playback passes a flag. Select the Timeline and then the Flag, or use Any where offered. Flags are created and positioned on the Timeline page. This event supplies indexed parameters: 0 — Timeline ID; 1 — Flag ID; 2 — Layout ID; 3 — flag time in milliseconds; 4 — loop cycle, starting at 0. Bind the required action fields with Par and the corresponding index.
Sync Play: activates on a synchronized playback event. Enter the Sync key used by the sending controller or Start Sync Timeline action. The receiving trigger and the sender must use the same key; distinguish different synchronized scenarios with different keys.
Ethernet Input: choose Protocol (TCP or UDP) and a configured Socket. The Filters fields let you restrict the source with Host filter and match message text with Contains. Configure the corresponding socket first, then enter the filters needed for the intended sender and command. An event with no restrictive filter can respond to a broader set of traffic.
RS232 Input: select Interface (RS232 Port 1 or RS232 Port 2) and configure the Contains and/or Exact match filters as needed. The serial port must be configured to match the connected device. Verify the actual received command and its spelling when configuring filters.
Digital Input: select Interface (Local Controller or an available registered remote module), Input and Level. Logic 0 (LOW) and Logic 1 (HIGH) select the level reached by the input transition. Check the module connection, input wiring and input numbering before testing.
9.4. Right Actions panel
The right column defines which actions are executed after the trigger fires.
- At the top, the type of a new action is selected, and it is added to the chain with the Add action button.
- Each action can be individually enabled or disabled via Enabled.
- Delay sets the action's offset in milliseconds from the trigger firing. Actions with different delays are scheduled from that same start time.
- An unnecessary action is removed with the Delete button.
Available action types:
- Start Trigger: start another trigger and optionally pass parameters to it.
- Run Script: start a selected script with the trigger’s input parameters.
- Start Timeline: start the selected timeline.
- Start Sync Timeline: start a timeline in synchronized playback mode using the specified Sync key.
- Pause Layout: pause playback on the selected Layout.
- Resume Layout: resume playback on the selected Layout.
- Stop Layout: stop playback on the selected Layout.
- Set Layout Color: apply a temporary color and brightness to a Layout, with timing options.
- Clear Layout Color: remove the temporary color from a Layout.
- HTTP Request: send an HTTP or HTTPS request; optional Response and Error triggers can handle the result.
- Send Ethernet: send a message through a configured TCP or UDP socket.
- RS232 Output: send a message through the selected RS232 port.
- Digital Output: set a local controller output or an output on a compatible registered remote module.
See 9.5 for additional details and parameter bindings.
9.5. Input parameters and additional actions
9.5.1. Trigger input parameters
Trigger parameters are an ordered list of values supplied for one execution of a trigger. They let the same trigger work with different values without creating a separate trigger for every case. They are input data for that particular run, not fields that are automatically copied from the Event block. Indexing starts at 0: in [500, true], parameter 0 is the number 500 and parameter 1 is the boolean true.
Values can come from the event or from the component that starts the trigger. For example, Timeline Flag supplies five documented values; Start Trigger can send an explicitly configured list; an HTTP Request action can start a Response or Error trigger with the result; a script can call a trigger with a parameter array. The available indexes and value types therefore depend on the actual source. Do not assume that every event or a manual Run supplies the same list.
To use an incoming value in an action: 1. Add or select the action. 2. Find the destination field, such as Delay, Enabled, Timeline or URL. 3. Enable Par next to that field. 4. Enter the zero-based index in the Params field that appears. With Par enabled, the index identifies a value supplied to this run; with Par disabled, the action uses the value configured in that field. Set Par separately for each field that should use an input parameter.
Example — a reusable timeline action: suppose a trigger receives [500, true]. Configure Start Timeline with a fixed Timeline, enable Par for Delay and enter 0, then enable Par for Enabled and enter 1. The action uses a 500 ms delay and is enabled for that run. If the second value is false, the action is disabled for that run. These are example input values; they must be supplied by the event or caller.
Passing values to another trigger: in the parent trigger add Start Trigger and select the child in Trigger. Under Parameters, use Add parameter to add rows. Each row’s position is the index the child receives. With Par off, enter a valid JSON value in the row, for example 500, true, "hello" or null. Strings require double quotes; numbers and booleans are not quoted. With Par on for a row, enter the index of the parent’s incoming value to forward instead. The row position is the child index; the entered Params index is the source in the parent.
Example — forwarding and reordering: if the parent receives ["message", 500], configure child row 0 with Par enabled and source index 1, and child row 1 with the literal JSON value true. The child receives [500, true]. Reorder rows by dragging or by selecting a row and using the arrow keys; removing or reordering a row changes subsequent child indexes. Confirm that the child’s bindings still refer to the intended positions.
Types and IDs matter. Delay expects milliseconds, Enabled expects a suitable boolean value, and fields that select a Timeline, Layout, Trigger or Script require the appropriate identifier rather than a display name. A text, number, boolean, array or object must be appropriate for the receiving field. An absent index, malformed JSON or a value of the wrong type can prevent an action from behaving as intended; inspect the trigger and Logs rather than assuming a default.
Other sources: Timeline Flag supplies [timeline ID, flag ID, layout ID, time in ms, cycle]. An HTTP Response trigger receives [status, bodyText, headers], while an HTTP Error trigger receives an error object at index 0. Run Script passes the trigger’s input array to the selected script as ctx.params; see the separate scripting guide for script handling.
Test with known parameter values and inspect the action result. A manual Run is useful for testing the action chain, but it may not reproduce the parameter values of a real network message, flag, HTTP response or parent trigger; also test the actual source. Avoid recursive Start Trigger chains.
9.5.2. TCP and RS232 message terminators
TCP and RS232 input commands end with CRLF: carriage return followed by line feed (CRLF). The terminator is removed before the command is passed to the trigger. A single CR or LF does not finish a command. UDP continues to use one datagram as one message.
9.5.3. Digital inputs and outputs
Digital Input and Digital Output can use the local controller or a compatible registered remote module. Select the interface and the appropriate input or output; the names and available channels depend on the selected device. For an input, choose the level transition; for an output, choose the intended value. Verify wiring, module connection and the effect on connected equipment before testing.
9.5.4. Timeline Flag event
Timeline Flag reacts to a flag crossing.
A Timeline Flag event provides parameters in this order: 0 — Timeline ID, 1 — Flag ID, 2 — Layout ID, 3 — flag time in milliseconds, and 4 — loop cycle starting at 0. Use these indexes when binding actions through Par.
9.5.5. Layout color actions
Set Layout Color replaces the selected Layout's light output with a color and brightness; Fade in, Duration and Fade out control the transition. Duration 0 holds the color until it is cleared or replaced. Clear Layout Color restores the current ordinary output. The timeline continues running beneath the color.
9.5.6. HTTP Request
HTTP Request sends an HTTP or HTTPS request using a URL, method, headers, body and timeout. Optional Response and Error triggers can handle the result. An HTTP response, including status 4xx or 5xx, is delivered to Response; a transport or execution failure goes to Error. Fields can use Par bindings.
Response trigger parameters are [status, bodyText, headers]. Error trigger parameters contain an object with code and message at index 0. Configure Par indexes in the receiving trigger's actions to use these values. The selected method and the device's API determine which headers and body are required.
9.5.7. Run Script
Run Script starts a selected script and passes the trigger's input parameters to it.
See trigger parameters and script invocation in the Scripting Guide.
9.6. Recommended workflow in Triggers
- First prepare what the trigger will refer to: Timeline, Layout, RS232, and network sockets.
- Create a new trigger with the + button.
- Set a clear name and, if necessary, a short description.
- Select the required Event Type and fill in the event parameters.
- In the right panel, add one or more actions via Add action.
- For each action, check the type, enabled state, and Delay.
- Enable the trigger via Enable.
- Test the action chain with known input values, then test the actual event source and confirm that the reaction on the site matches the task. Manual Run may not reproduce event-specific parameters.
9.7. What to pay attention to
- If a trigger should react to the network, configure and enable the required TCP/UDP socket in Settings → Network in advance.
- If a trigger starts a timeline, first make sure the timeline itself is prepared and Bake has been executed if necessary.
- If a trigger works via RS232 or Digital Input, verify the correct port selection and level logic.
- The Run button is convenient for commissioning, but after testing it is still worth checking the real external event separately if the trigger is supposed to work automatically.
9.8. Scripts
Open Scripts to create, edit and manage JavaScript automation. Select a script in the list to edit its source and properties. Use Parameters for JSON test input, Save and Run to execute the script, and Console, Result and Problems to inspect output and errors. The API tab provides searchable method signatures and examples. A trigger can start a script with the Run Script action.
For detailed instructions on creating, testing and using scripts, including the available API and operating limits, see the separate Scripts User Guide.
Open the Scripting Guide for JavaScript, controller API methods, and complete examples.
The Global script defines shared functions and variables. Save stores its source; Apply loads it into the shared environment and resets shared variable values. Stop all scripts stops script executions; it does not undo commands already sent or replace Stop All for lighting and timelines. Review a script's behavior before running it on a live installation.
9.8.1. Creating and testing a script
Use New script in the Scripts list and enter the code in Source. In Properties, configure the name, Enabled state, timeout, and description. Save stores the source. Duplicate creates a copy; Delete removes the selected script.
For a manual test, enter a JSON array in Parameters and use Run. The values are available as ctx.params. Script commands affect the real controller and its outputs, so review the code and target objects before running. Use Stop to stop a run.
9.8.2. Diagnostics and API
Problems shows static analysis issues; Console shows script messages and Result shows the outcome. The Properties panel includes the script ID, revision, enabled state, and timeout. The API tab provides searchable methods, parameters, return values, and examples for available controller operations.
Use Logs with the SCRIPT source to investigate starts, completion, failures, and timeouts. Stop all scripts stops script executions and can reset the shared environment; it does not reverse commands already applied.
10. Calendar page
The Calendar page is used for scheduling. Here the engineer creates one-time, recurring, and astronomical events that should start automatically by time.
10.1. Calendar top bar
The upper part of the page helps you quickly switch between view modes and periods.
- View shows the current view mode.
- The Month, Week, and Year buttons switch the calendar display.
- The <<, Today, and >> buttons let you move to the required period.
10.2. Central calendar area
The center displays the calendar grid for the selected period.
- In Month mode it is convenient to see the general picture by date.
- In Week mode it is easier to verify events by time of day.
- In Year mode it is convenient to jump quickly by month.
- Select a date to open Day View, inspect its events, and open an event's settings to review or change its schedule.
10.3. Right All Events panel
The full list of events is shown on the right, regardless of the selected period.
- The Add Event button creates a new event.
- Clicking an event card opens it for editing.
- The Run button lets you test the event manually.
- The card shows the name, a short description of recurrence, and related bindings.
10.4. Event Settings window
This is the main working window of the calendar. Here you define the event name, trigger logic, recurrence, exceptions, and bindings to soft triggers and UI buttons.
These screenshots already show the main editor scenarios: a one-time event, standard recurrence, quick recurrence presets, advanced rules, and astronomical mode. Each of them is described separately below.
10.4.1. Top of the window
- The window title shows Create Event for a new event or Event Settings for an existing one.
- The Close button closes the editor without separately launching the event.
- The Name field sets a clear name. It is best to immediately use a title that operations staff will understand, for example Evening facade start or Weekday storefront lighting.
10.4.2. Schedule block
The Schedule block defines the basic event model.
- The mode switch lets you choose One-time or Recurring.
- For One-time, you set only the date and time of one run.
- For Recurring, you set the start date, recurrence logic, and end mode.
- If the event is recurring, an end selection appears: Never or On date.
- In On date mode, you must specify the end date, after which the event should no longer run.
10.4.3. One-time event
One-time mode is used for a single launch at a specific date and time.
- Use it for one-time switch-ons, holiday scenarios, or technical launches on the site.
- The Date and Time fields are filled in.
- It is the simplest mode if the event should not repeat automatically.
10.4.4. Recurring event
Standard recurring mode is used for daily, weekly, and other regular launches.
- The Start date field sets the date when the rule becomes active.
- The Time field sets the base execution time if you are not using astronomical mode.
- Below, a Repeat block appears with ready-made presets: Minutely, Every day, Weekdays, Weekly, and Monthly.
- The Minutely preset allows you to select minutes within each hour, for example 0, 15, 30, and 45.
- The Weekly preset allows you to choose specific weekdays.
- The Monthly preset lets you specify the day of the month.
- Under the repeat block, the editor shows a draft rule summary so you can immediately see how the system interprets the current settings.
10.4.5. Astronomical mode
Astronomical mode is enabled only for recurring events via the Astronomical event checkbox.
- Instead of a fixed time, you select an event here: At sunset, At sunrise, At moonrise, At moonset, or Moon quarters.
- The Offset (minutes) field sets an offset from the selected astronomical moment.
- Positive values mean launch after the event; negative values mean before it.
- For Moon quarters, an additional selection appears for a specific moon quarter or Any moon quarter mode.
- Below, the system shows the Selected mode string, which helps verify the resulting launch formula.
10.4.6. Advanced repeat controls
This block is needed when the ready-made repeat presets are not enough.
- The Repeat rules section lets you build additional rules and add them with the Add repeat button.
- You can use the BYMINUTE, BYHOUR, and BYMONTHDAY fields, as well as month and weekday selection.
- If nothing is selected for months or weekdays, it means that no restriction is set for that parameter.
- Each added rule is shown as a separate line and can be removed with the Remove button.
- The EXDATE section is used to exclude individual dates and times from an already configured recurrence. Note that you can exclude only a specific date, and it will not repeat every year.
- The Add exclude button adds an exception, and the list below shows all excluded dates.
- The Combined rule field allows you to manually enter RRULE and EXDATE strings if precise manual configuration in RFC 5545 format is required.
- If the syntax of a manual rule is incorrect, the editor will show an error and will not allow invalid logic to be saved.
10.5. Recommended workflow in Calendar
- First prepare the timelines, triggers, and UI buttons if the event needs them.
- Click Add Event and set the event name.
- Select the schedule type and fill in the date, time, and recurrence.
- If the event should launch something in the system, add the required bindings in the Triggers & UI buttons block.
- Save the event via Create or Save.
- Check the result with the Run button and then wait for the real trigger time.
10.6. What to pay attention to
- Scheduling depends on correct time and time-zone settings in Controller.
- If recurrence is used, make sure the RRULE is correct and does not conflict with EXDATE exceptions.
- If the event is linked to a soft trigger or UI button, the corresponding binding must exist and be configured correctly.
- Manual Run is useful for checking logic, but it does not replace verification of a real calendar-based trigger.
11. User interface page
The User interface page (UI Constructor) builds the customer interface. Configure screen types, navigation, controls, appearance and trigger bindings, then check the result in Preview.
11.1. General tab
The General tab is responsible for the overall appearance of the interface.
- In the Theme section, you can quickly apply a ready-made color preset.
- The Branding block sets the Logo Installer, Logo Customer, and Name Customer.
- The Screen Background field selects the image or video used as the interface background.
- The selected background is shown in the Application and in the Preview window.
- Background media is selected from the File Manager media library.
- The Navigation block selects the Home screen and optionally an All zones screen. If All zones is not selected, its customer-interface navigation button is hidden. RDM diagnostics is an On/Off setting.
- In the Colors block, the main interface colors are set.
- The Component styles section configures the global look of action, switch, and zone-card buttons.
- The Refresh all buttons button applies the global styles to the buttons.
11.4. Preview window
On the right, Preview shows the user interface the way operations staff will see it.
- The preview can be switched between different device presets.
- The selected preset changes the preview dimensions. Check representative iPhone, Pixel and Galaxy sizes and verify the result on the actual customer device.
- Use Preview to check the current screen’s appearance and navigation. Test configured controls only when the installation is ready, because linked actions can operate real equipment.
11.5. Color Picker screen
Color picker is a separate screen type for choosing color and brightness. In Screens & Buttons, add an empty screen and select Screen type → Color picker. A Buttons screen containing buttons cannot be switched directly to Color picker; the editor indicates that an empty screen is required. Set Screen name and choose a Soft trigger. Set Color parameter and Brightness parameter to the zero-based indexes expected by the trigger; the defaults are 0 and 1.
A typical Soft trigger uses Set Layout Color: select the intended Layout, enable Par for Color and bind it to the configured color index, then enable Par for Brightness and bind it to the configured brightness index. With the defaults, use indexes 0 and 1. Color is #RRGGBB and brightness is 0–100. The trigger selects the Layout; the Color picker screen itself does not select it. Configure a way to clear or replace the color when needed.
In the customer interface, use the color disc, HEX/RGB fields and brightness slider, or select a quick color. Save stores the current color and brightness in Saved colors; a saved color can be selected or deleted with confirmation. In the editor, Screen texts configures the labels for Save, Quick colors and Saved colors, as well as the deletion dialog. Appearance follows the global theme.
Create a Zone card on a Buttons screen and select the Color picker screen as Target screen so the operator can open it. Check the parameter indexes, target Layout, navigation and the real output during commissioning.
11.6. Recommended workflow in User interface
- First prepare the triggers that will be called by the buttons.
- In the General tab, set branding, colors, and global styles.
- In the Screens & Buttons tab, create the required screens.
- Add buttons and choose their type.
- For each Buttons screen, configure Action targets, Switch On/Off bindings and Zone card destinations as needed. For a Color picker screen, configure its Soft trigger and parameter indexes. Add a navigation route to screens operators need to open.
- Check the result in Preview and run button tests.
11.7. What to pay attention to
- If an Action has no enabled usable target, a Switch lacks the required trigger, or a Zone card lacks a destination, the control may not perform the expected operation.
- For Switch toggles, you need to fill in both On trigger and Off trigger if both states should work.
- If you do not select a Home screen, the initial navigation may be inconvenient for operations staff.
- After major changes, it is useful to check not only the appearance but also the real execution of the buttons using the built-in tests.
11.8. File Manager page
File Manager is a separate page in the main menu for storing project images and videos. Use Upload to add files. All, Images, and Videos filter the list; each item shows its name and size. Copy URL copies the file address and Delete removes the file.
Images and videos can be selected where the interface offers File Manager media, such as user-interface backgrounds and layout background images. Check whether a file is used by the project before deleting it, and verify the affected screen or layout afterward.
12. Settings screen
12.1. Controller
This is the main tab for the initial controller setup. The engineer usually works here first.
12.1.1. Name
The Name field sets the displayed controller name. It is recommended to specify a clear site name, for example the hall, zone, or rack name.
- Use a short and unambiguous name.
- After entering it, make sure the name has updated in the Current Profile panel on the right.
- If the field is left empty, the system will restore the default name.
12.1.2. Audio output
The Audio output field is used only if the project actually uses the controller's audio output.
- If audio is not used, it is usually enough to leave the default option.
- If the required output is not in the list, click Refresh.
- After selection, check that the required device is shown in the profile on the right.
12.1.3. HDMI inputs
Use HDMI inputs to assign HDMI 1 and HDMI 2 to the physical USB ports of compatible capture cards. For video select a supported MJPEG resolution and frame rate, up to 1920 × 1080. Refresh updates the device and mode list. A physical port can be assigned to only one logical input. Settings are saved automatically; a saved but unavailable mode remains visible so the assignment can be diagnosed.
After assigning the source, check a snapshot under Dashboard → HDMI input and configure the Video input or Audio input effect in Timeline. Receiving data from a capture card does not by itself prove that the card is receiving a valid HDMI picture.
12.1.4. Timeline FPS
Timeline FPS sets the working timeline frame rate. Change it only if required by a specific project.
- If the project documentation has no separate requirement, do not change this value unnecessarily.
- If the project is already built for a certain FPS, an uncoordinated change may affect playback.
12.1.5. Notes
The Notes field is convenient for service notes: site address, installation remarks, schematic version, and network specifics.
12.1.6. Location, Latitude, Longitude
The location block is needed for correct operation of time-based logic and logic tied to the site's geography.
- In the Location field, you can choose a city from the list.
- After selecting a city, the system usually fills in the coordinates, time zone, and DST settings automatically.
- If the site is non-standard or an exact address is required, you can manually correct Latitude and Longitude.
- After manual editing, check that the data in Current Profile on the right looks correct.
12.1.7. Time zone
The Time zone field sets the site's time zone. For stable schedule operation, it is important that it is selected correctly.
- If the site is in a typical city, it is more convenient to select the city first and then verify the time zone.
- If the time zone is changed manually, make sure it matches the actual installation location.
- If the controller works on a schedule, this item is critical.
12.1.8. Automatic sync and Controller time
This block configures the controller's current time and its synchronization.
- Automatic sync enables automatic time synchronization if it is available on this controller.
- When automatic synchronization is enabled, manual time editing is usually blocked.
- If you need to set the time manually, first disable automatic synchronization, then enter the date and time in the Controller time field and click Apply.
- After changing the time, compare it with the right panel: the current clock value is visible there.
Practical advice
If the site works on a schedule, first check these three things: Time zone, the status of Automatic sync, and the current Controller time value.
12.1.9. DST
The DST block is responsible for switching between daylight saving time and standard time.
- If daylight saving time is required on the site, enable Enable daylight saving time.
- In the DST preset field, choose a suitable template if it fits the installation country.
- If the template does not fit, manually fill in DST start and DST end.
- If the site is located in a region without time changes, leave DST disabled.
12.1.10. Project export and Project import
The bottom part of the tab contains service actions for project backup and import.
- Save backup creates a backup copy of the current project. This is a convenient way to finish commissioning.
- If Download latest backup is displayed, it downloads the most recent backup copy.
- Import package uploads a project from a file.
Important when importing a project
Project import replaces the active project data on the controller: timelines, layout, triggers, users, sockets, media, and file-manager files. The controller's network settings remain local.
After import, you will need to log in again. Before importing, make sure the correct package is selected.
12.1.11. Reset to defaults
The Reset to defaults button returns the tab parameters to their base values.
12.1.12. Native RDM
Native RDM enables RDM operation on the controller's individual DMX OUT1 and DMX OUT2 ports. Check the setting for the port used by the RDM devices, then use Dashboard → RDM to inspect the port and responders. Disabling RDM leaves the port in DMX-only mode. Perform discovery or changes to a live output only when appropriate for the site.
12.2. Users
The Users tab is not directly related to light calibration, but it may be needed during site handover when access has to be passed to operations staff.
12.2.1. What can be done here
- View the user list.
- Select a user and change the name, login, role, or status.
- Change the password of the selected user.
- Create a new user.
- Delete a user.
12.2.2. What the engineer should look at
- Role defines the level of access. Usually operations staff receive a role according to the project agreement.
- Status lets you quickly activate or block an account.
- When creating a new user, the login must be unique.
- The password should not be too short. The interface provides a hint about the minimum length.
If your task is only lighting commissioning and access has already been issued, you may not need to use this tab.
12.3. Settings screen: Network
The Network tab is used to configure the controller's communication with the site network and related interfaces.
12.3.1. LAN
The LAN block is responsible for the controller's main network connection.
- If the site uses automatic address assignment, enable DHCP.
- If a fixed address is required, disable DHCP and fill in IP address, Subnet mask, Gateway and DNS.
- When DHCP is enabled, the static addressing fields are blocked. This is normal behavior.
- After making changes, click Save network settings.
- The DNS field sets the DNS server used by the LAN interface.
- DNS is needed when the controller must resolve domain names, for example for cloud connection, update checks, or external services.
12.3.2. Art-Net
The Art-Net block is needed if the lighting is routed into a separate lighting network.
- The operating logic is similar to LAN: you can use DHCP or set the address manually.
- If the Art-Net network is separated in the project, specify the parameters of that network specifically.
- After changing the parameters, also click Save network settings.
- The Gateway field is optional for Art-Net. It is usually left empty when Art-Net is used only inside a local lighting network.
- Enable Send Artnet timecode if the controller must send Art-Net timecode to the lighting network.
- After changing the parameters, also click Save network settings.
12.3.3. WiFi Configuration
The controller can connect to an existing wireless network in Wi-Fi client mode. To configure the connection, open Settings → Network and locate the Wi-Fi section.
- Select the required antenna:
- Internal antenna — uses the controller’s built-in antenna.
- External antenna — uses the external antenna connector. Connect the antenna physically before restarting the controller.
- Changing the antenna requires a controller restart. The controller does not restart automatically.
- Enable Wi-Fi.
- Click Search networks to scan for available wireless networks. The list displays each network’s SSID, signal strength, and security type. Select a network to copy its name into the SSID field. For a hidden network, enter the SSID manually.
- For a secured network, enter its Wi-Fi password. If a password is already saved and should be kept, leave the password field blank.
- Configure the IP settings:
- Leave DHCP enabled to obtain the IP address, subnet mask, gateway, and DNS settings automatically.
- Disable DHCP to configure a static IPv4 address. Enter the IP address, Subnet mask, Gateway, and DNS servers manually.
- Click Save Wi-Fi settings to apply the configuration.
After a successful connection, the interface displays the active Wi-Fi network or assigned IP address. The controller’s web interface can then be opened using its Wi-Fi IP address.
The Wi-Fi regulatory region is selected automatically based on the Location configured for the controller. If the location cannot be identified, the controller uses the safe World regulatory mode.
12.3.4. RS232
The RS232 block is needed only in projects where external devices are connected via a serial interface.
- For each port, the following are set individually: Baud rate, Data bits, Parity, Stop bits, and Flow control / Handshaking.
- If RS232 is not used on the site, this block can be left untouched.
- After editing, click Save RS232 settings.
12.3.5. Sockets
The Sockets section more often relates to integration tasks and is not always needed by a lighting engineer. But if the project includes exchange via UDP or TCP, configuration is done here.
- An already created socket is selected on the left.
- Its parameters are edited in the center: name, port, timeout, UDP type, and enabled state.
- On the right, a new socket can be created via Add Socket.
- The Delete socket button removes the selected socket.
12.4. RGBW Calibration
This is the key tab for setting the correct white for RGBW and RGBCW fixtures. It is best to work with it once the network is already configured, the fixtures are connected, and you understand the addressing scheme.
12.4.1. What to check before calibration
- Calibration should be performed in a dark environment; if it is a facade, then at night. Fixtures should illuminate the same surface on which they will later operate. This helps avoid problems caused by different light reflection from different surfaces.
- Make sure the fixtures are actually connected to the output you are going to test.
- Understand the fixture format: RGBW or RGBCW.
- Know the starting RGB address and the white-channel addresses.
- Understand the fixture color order: RGB, RBG, GRB, and so on.
- If you use Art-Net unicast, know the IP address of the target device.
12.4.2. Output source
In both blocks, the path for the test signal output is selected first.
- Use Output source = DMX if you want to output the calibration via the controller's local DMX port.
- Use Output source = Art-Net if the test goes to an Art-Net network.
- For DMX, choose DMX OUT1 or DMX OUT2.
- For Art-Net, the Universe is specified.
- If Broadcast is enabled, the address is sent by broadcast.
- If Broadcast is disabled, make sure to fill in the IP address.
12.4.3. RGBW calibration
The RGBW Calibration section is used if the fixture has one white channel.
- Select the output source: DMX or Art-Net.
- Specify the RGB start address.
- Select the correct RGB order.
- Specify the White address.
- In the Reference Color block, set the Red, Green, and Blue values.
- Click Preview RGBW white.
- Evaluate the white tint and, if necessary, adjust the RGB values.
- Set Confidence from 0 to 1 to adjust the contribution of the white channel to the resulting color. Check the visual result on the actual fixtures after changing it.
- When the result is satisfactory, click Save calibration.
The calibration idea is simple: using two fixtures, the white channel on the first fixture remains on at full level, and you select an RGB color on the second fixture so that the resulting RGB white looks as similar as possible to the white channel of the first fixture. Then, when recalculating color, the controller will use your RGB color as the reference and mix in the white channel to output the final color. If you want to use only the white channel, then the content color should match the RGB calibration color.
12.4.4. RGBCW calibration
The RGBCW Calibration section is used if the fixture has two white channels: cold and warm.
- Select the common output source.
- Specify the RGB start address.
- Select the RGB order.
- Specify the Cold white address and Warm white address.
- In the Cold White Reference block, adjust the RGB mix for cold white and verify it with Preview cold white.
- In the Warm White Reference block, similarly adjust the RGB mix for warm white with Preview warm white.
- After verification, save the configuration via Save calibration.
- Set Confidence from 0 to 1 to adjust the contribution of the white channel to the resulting color. Check the visual result on the actual fixtures after changing it.
12.4.5. Stop preview, Save calibration, Reset defaults
- Stop preview stops the current test output.
- Save calibration saves both calibrations: RGBW and RGBCW.
- Reset defaults returns the form to its initial values.
After finishing the setup, it is recommended to always stop the preview and verify once more that the save operation completed successfully.
12.4.6. Right Preview Status panel
The panel on the right helps you quickly understand what is actually happening.
- Preview shows whether a test is currently running.
- Mode shows the test type: RGBW, RGBCW cold, or RGBCW warm.
- Runtime shows whether execution is connected.
- Output shows exactly where the signal is going.
- RGB address, White, Cold white, and Warm white help you quickly verify addresses without returning to the form.
Typical reasons why preview does not give the required result
- The wrong output is selected, for example DMX instead of Art-Net.
- The Universe or IP address of the Art-Net device is incorrect.
- The RGB order is mixed up.
- The white-channel address overlaps with the RGB range.
- The fixture type is wrong: RGBW and RGBCW are mixed up.
- The controller physically cannot see the execution side or the line.
12.5. Firmware
The Firmware tab is used for service verification of a new firmware version and to start an update or rollback.
12.5.1. When to use this tab
- After starting a new controller, if the procedure requires checking whether the version is current.
- Before site handover, if all devices must be brought to one version.
- For a service task involving an update or rollback.
12.5.2. Checking for an update
- Open the Firmware tab.
- Click Check update.
- Wait for the check to finish.
- Compare the Current version and Available version in the right panel.
- If there is a description of changes, review the Available changelog block.
12.5.3. Update or rollback
- If a newer version is available, the button will show an action such as Update to ....
- If the installed version is newer than the offered one, the system may offer Rollback.
- During the update, the controller may reboot. Take this into account when working on the site.
12.6. Cloud
The Cloud tab is used to pair the controller with the cloud service and manage cloud synchronization.
- Pairing Code is entered when connecting the controller to a cloud account.
- The Pair button links the local controller with the cloud using the entered pairing code.
- Cloud URL shows the cloud server address.
- Customer UI Sync controls whether the local customer ui configuration can be updated automatically from the cloud.
- Calendar Sync controls whether the local calendar can be updated automatically from the cloud.
- Conflict Rule defines what should happen when the cloud calendar and local controller calendar have different versions.
- Cloud wins automatically uses the cloud calendar version.
- Controller wins automatically keeps the local controller calendar version and sends it to the cloud.
- Ask when versions differ shows a conflict warning and lets the user choose which version to keep.
- Pull cloud to local replaces the local controller calendar with the cloud calendar.
- Push local to cloud replaces the cloud calendar with the local controller calendar.
- Disable pairing disconnects the controller from the cloud and stops cloud synchronization.
13. Installing the application on the customer’s device
13.1. About PWA Technology
The PROMIN customer application is a Progressive Web App (PWA). A PWA is opened through a web browser but can be installed on the phone and used like a regular mobile application.
After installation, the application:
- Appears as a PROMIN icon on the Home Screen.
- Opens in a separate app window when supported by the browser and device.
- Does not require installation from the App Store or Google Play.
- Can receive interface updates through the browser; refresh or reopen it if the latest changes do not appear.
- Provides quick access to the controller’s customer interface.
The phone must have network access to the controller for monitoring and control functions to work.
You can watch a video on how to make it on the Promin youtube channel. https://www.youtube.com/@promincontrol
Browser menu names and installation options can differ by device, browser version, and the address used. If an install command is unavailable, use the browser's available Add to Home Screen or shortcut option and verify that it opens the intended customer interface. Access to the controller is still required for live control.
13.2. Installation on iPhone
- Connect the iPhone to a network that provides access to the controller.
- Open Safari.
- Enter the customer interface address provided by the installer: http://<controller-ip-address>/customer/
- Wait until the customer interface opens completely.
- Tap the Share button in Safari.
- Scroll down and select Add to Home Screen.
- Enable Open as Web App, if this option is displayed.
- Check the application name and tap Add.
- Return to the Home Screen and tap the PROMIN icon to open the application.
If Add to Home Screen is not displayed, scroll to the bottom of the Share menu, select Edit Actions, and add it to the available actions. These steps follow Apple’s current procedure for installing web apps on iPhone. Apple Support
13.3. Installation on Android
- Connect the Android phone to a network that provides access to the controller.
- Open Google Chrome.
- Enter the customer interface address provided by the installer: http://<controller-ip-address>/customer/
- Wait until the customer interface opens completely.
- Tap the three-dot menu in Chrome.
- Tap Install and create shortcut, then Install. Depending on the Chrome version and the site, the menu may instead show Install app or Add to Home screen.
- Confirm the installation.
- Return to the Home Screen or application list and tap the PROMIN icon.
The installed PWA can be opened and managed similarly to a regular Android application. Google Chrome Help
13.4. Installation on Windows
The customer application can be installed on a Windows computer using Microsoft Edge or Google Chrome.
13.4.1. Using Microsoft Edge
- Connect the computer to a network that provides access to the controller.
- Open Microsoft Edge.
- Enter the customer interface address provided by the installer: http://<controller-ip-address>/customer/
- Wait until the interface opens completely.
- Click the App available icon in the address bar and select Install. If the icon is not displayed, open the three-dot menu and select More tools → Apps → Install this site as an app.
- Check the application name and click Install.
- If required, select Pin to taskbar, Pin to Start, or Create Desktop shortcut.
- Open the application using the PROMIN icon.
Installed Edge applications can be managed by entering edge://apps in the address bar. Microsoft Support
13.4.2. Using Google Chrome
- Open Google Chrome.
- Enter the customer interface address provided by the installer: http://<controller-ip-address>/customer/
- Wait until the interface opens completely.
- Click the Install icon in the address bar. Alternatively, open the three-dot menu and select Cast, save, and share → Install page as app.
- Confirm the application name and click Install.
- Open the application from the desktop shortcut, taskbar, or Windows Start menu.
The application opens in a separate window and functions like a regular Windows application. The computer must remain connected to a network that provides access to the controller. Google Chrome Help
14. Final check after configuration
After all changes are complete, it is convenient to go through a short checklist:
- In the Controller tab, check the controller name.
- Check the correct Time zone and current time.
- In the Network tab, make sure LAN and Art-Net are set correctly and communication has not been lost.
- If the fixture map was edited, on the Layout page check that the layout, groups, and fixture types match the site.
- If patching was performed, on the Patch page check the group output, port / universe / IP, and the absence of address conflicts.
- If playback scenarios are used, on the Timeline page check the active layout, Sync mode, presence of the required clips, and run Bake after the latest edits.
- If automatic events are used, on the Triggers page check that the required triggers are enabled, the correct Event Type is selected, and the actions work via Run or a real external signal.
- If the site works on a schedule, on the Calendar page check the dates, time, recurrences, bindings, and perform a test launch via Run.
- If a user screen has been prepared, on the User interface page check the home screen, screens, buttons, trigger bindings, and the final appearance in Preview.
- On the Dashboard page, make sure the controller status is correct, and if necessary verify the output signal in the DMX Out tab.
- If calibration was used, in the RGBW Calibration tab stop the preview and make sure the calibration is saved.
- If required by procedure, in the Firmware tab verify that the firmware version matches the work plan.
- Create a project backup via Save backup.
14.1. Additional checks for version 1.20
If relay modules are used, verify their online state and test the intended input and output channels. For HDMI input, verify the USB assignment, selected mode, snapshot and playback through a configured trigger. Test Timeline flags and parameter bindings using representative inputs. For a Color Picker, check the screen's trigger and parameter indexes and the target Layout. Review script errors and HTTP Response/Error handling. Confirm that Highlight selection is off after fixture identification.
15. Common issues and what to check
For solutions to common issues and step-by-step troubleshooting guides, visit our YouTube channel and watch the available support videos.
https://www.youtube.com/@promincontrol
| Situation | What to check |
|---|---|
| The schedule fires at the wrong site time | Check Time zone, the Automatic sync state, the current Controller time value, and the DST settings. |
| Access to the controller was lost after changing the network | Check whether DHCP was enabled instead of a static address, whether the IP, subnet mask, and gateway are correct, and whether the interface must now be opened via the new address. |
| There is no activity in Dashboard -> DMX Out | Check whether the correct output is selected, whether the runtime is working, whether the required timeline or project logic is running, and whether there is any data that should be output right now at all. |
| The timeline does not start as expected | Check that the correct Timeline is open, the playhead is at the correct point, the Loop mode is set properly, and Bake has been run after the latest changes. |
| The timeline does not follow external time | Check the Sync field in Timeline -> Properties. If external synchronization is required, Art-Net TimeCode must be selected, and the external timecode source must actually be present in the system. |
| An event in Calendar does not fire on time | Check the date, time, recurrence mode, correctness of RRULE and EXDATE, and the time and time zone settings in Controller. |
| An event exists in Calendar but does not launch the required action | Check the Triggers & UI buttons block in Event Settings: the required binding must be added, and the soft trigger or UI button itself must exist and be configured correctly. |
| A button is visible in User interface but does nothing | Check the button type, the selected Trigger or On/Off trigger, and then run a test via Test, Test ON, or Test OFF. |
| Navigation in User interface leads to the wrong place | Check the Home screen setting, the All zones setting, and the Target screen field for buttons of the Zone card type. |
| The trigger does not fire | Check that the trigger is enabled, the correct Event Type is selected, all event fields are filled in, and the required source is available: socket, RS232 port, digital input, or timeline. |
| The Run button works, but the external event does not | Check not the Actions list itself, but the event source: TCP/UDP socket, RS232, digital input, selected timeline, or the type of external signal. |
| The trigger fires, but the action is not performed | In the right Actions panel, check that the required action is enabled, has no incorrect Delay, and refers to an existing timeline, layout, trigger, or port. |
| The fixture does not respond to preview | Check the correct output, Universe, IP address, physical connection, and whether communication with the execution side is available. |
| The white color has a tint | Check the RGB order, the starting RGB address, and the correctness of the selected RGB values in the calibration. |
| The fixtures are positioned differently after changing Layout | Check the active layout, selected group, fixture type, the Draw / Select mode, and whether the selected points were accidentally moved. |
| The fixture does not respond after patching | Check the Patch page: the correct group, start address, output type, DMX port or Art-Net universe, broadcast / unicast, and IP address. |
| The address is not assigned when dragging | Check whether there is a conflict with already occupied channels and whether the block goes beyond the 1–512 range. |
| There is a signal after patching, but not on the expected output | Check the Output field in Patch, the DMX port or Art-Net parameters, and then confirm the result on the Dashboard -> DMX Out page. |
| It is impossible to add new points in Layout | Check the channel-limit message and the total Channels value. The current configuration may already be at its limit. |
| Old project data disappeared after import | This is normal behavior. Import replaces the project data on the controller. Always create a backup before importing. |
| It is not possible to change the time manually | Check whether automatic time synchronization is enabled. |
| It is not possible to launch Art-Net unicast preview | Check that broadcast is disabled and that a correct IP address has been filled in. |
| Can not connect to the cloud | The controller cannot connect to cloud: check LAN, gateway, DNS, internet access, pairing code, firewall. |
| Relay module is offline or missing | Check power, network connection, module network settings, and whether it is registered under Dashboard → Network → Modules. Check MODULES entries in Logs. |
| HDMI input snapshot is unavailable | Check the capture card and USB port, the assigned HDMI input, the selected capture mode, and the HDMI source. Use Dashboard → HDMI input → Refresh. A card may provide a black or placeholder frame even when no usable source is connected. |
| Timeline flag does not trigger an action | Check the selected Timeline and Flag filters, that the trigger is enabled, and that playback passes the flag. Restart playback after editing flags. |
| A trigger action receives an unexpected value | Check the source event, parameter index, Par setting, and value format. Inspect the relevant trigger and action entries in Logs. |
| A script fails or stops | Inspect Problems, Console, and Result, check its Enabled state and timeout, and review SCRIPT entries in Logs. |
| An HTTP request fails or returns an unexpected result | Check the URL, connection, response status, timeout, and Response/Error trigger bindings. |