Create Fixture

Create the fixture entry after the company account exists and the final fixture identity is clear. The fixture entry is the App Library record used by the Vision Control App to recognize the product and load the correct app data.

Before you start

Final RDM Manufacturer ID.
Final RDM Device Model ID.
Fixture name, brand name, product description, website, and support information.
Serial number format used by the fixture.
Final or release-candidate firmware file.
Final App Control Configuration that matches the firmware.
Fixture image, app icon, and optional documents such as manual, DMX chart, or technical data sheet.

Important: the RDM Manufacturer ID and RDM Device Model ID must stay stable after release. These two values are how Vision identifies the fixture type.

Open My Fixtures

Create the fixture

Click the plus button to create a new fixture. Fill in the product identity carefully.

RDM ESTA Manufacturer ID: enter the decimal value. If your value is written in hexadecimal, convert it to decimal first. If you are not an RDM manufacturer, use your assigned Vision replacement ID.
RDM Device Model ID: enter the decimal value of the fixture model ID.
Serial number validation: enter the regular expression used to validate fixture serial numbers. If there are no special requirements, use the simple numeric format already recommended by Vision Control.
Product information: add the user-facing name, brand, description, website, and support information.

After saving, the fixture appears on the My Fixtures page. New fixtures are created as draft and are not released to normal users yet.

Add image and icon

The fixture image and icon are shown in the app. They should make the product easy to recognize.

Image: upload a clear product image.
Icon: use a transparent 200 x 150 px icon without active light output.
App Control icon: mark the controllable light area. Older pages or screenshots may call this Icon Creative.

Upload firmware

Open the Software section and upload the firmware file for the fixture. Add clear release notes so the customer can understand what changed.

Use the versioning format expected by the Vision Web Service.
Only release firmware that was tested on the real fixture.
Keep draft firmware internal until it is ready for release.

When the firmware is ready for users, change it from draft to release.

Upload resources

Upload customer-facing documents in the resources area. Typical resources are the user manual, DMX sheet, safety information, technical specification, or service documents.

Upload App Control Configuration

Upload the final App Control Configuration created and tested during implementation. This configuration must match the final firmware behavior. If the firmware behavior changes, check whether the App Control Configuration must also be updated.

Legacy naming: App Control Configuration was previously called Creative Configuration or Creative Config in older app versions, screenshots, URLs, and filenames.

If several firmware versions use the same configuration, they can reference the same App Control Configuration. If a new firmware changes the DMX layout or App Control behavior, upload a new configuration and assign it to the matching firmware version.

Check release information

Before requesting the release, check all information that will be visible or used by the Vision Control App.

Fixture name, brand, description, website, and support contact.
RDM Manufacturer ID and RDM Device Model ID.
Firmware version and release notes.
App Control Configuration assigned to the correct firmware version.
Fixture image, icon, and App Control icon.
Resources such as manual, DMX chart, technical data sheet, or safety information.

The RDM Manufacturer ID and RDM Device Model ID cannot be changed after release. Other product information can be updated later, but it should still be checked carefully before release.

Request release

Request the fixture release only after the real fixture was tested with the final firmware, final App Control Configuration, and final product data. Upload the requested verification information and, if required, a video that demonstrates the fixture functionality.

After release approval, continue with the production chapter: purchase production licenses, flash or update Vision modules, license modules, and verify the first production sample.

Share fixture access

If you manufacture the fixture as an OEM and another company owns the brand, share fixture access with that company after the fixture entry is ready. The brand can then maintain product data or release information according to the agreed workflow.