Step by Step

This guide helps you navigate the documentation in the correct order so you can successfully create your own fixture. Follow the steps one by one until you have a working product.

An example project (simple product implementation) is available here:
Example Project Overview

In the documentation, you will find generic explanations of all available functions. Many low-level details are already handled by our prepared libraries and examples. We recommend following this guide first, then consulting individual reference sections only when you need additional details.

Technical Development (Hardware & Software)

  1. Select the Right Product
    • Before starting, verify that you have chosen the correct product for your needs.
    • See Implementation Check.
  2. Check Requirements
    • Ensure that your product meets the necessary conditions for the implementation.
    • See Requirements.
  3. Integrate Hardware
    • Integrate the Vision Controller with the required features into your product.
    • Optional features may require additional hardware or software. See Features.
    • For custom hardware design, follow Custom Implementation.
  4. Prepare Software Development
    • Once the PCB is available, you can begin with firmware development.
    • Reference implementations are available for two microcontrollers:
    • If you use another controller, adapt one of these examples.
  5. Test Communication
    • Validate communication between the Vision Controller and your main controller.
    • Follow Test & Run Preparation.
    • First test only your bootloader firmware, then repeat the process with your application firmware.
  6. Understand Bootloader & Firmware Update
    • Make sure you understand how bootloader and application firmware interact.
    • Create a DFU package for the app: Example DFU Package.
    • Flash the bootloader and test the firmware update: DFU Test.
    • Save the DFU file for later use.
  7. Refine RDM Application Firmware
    • Use your normal wired RDM implementation as the base. Vision transports the same RDM commands through the Vision Controller. Do not create a second independent RDM library unless your architecture really requires it.
    • Implement and test all required (and optional) RDM commands.
    • See RDM PIDs and RDM Test.
  8. Implement Control via App / DMX
    • Use your normal wired DMX implementation as the base. Vision Control Behavior 0 is normal DMX Control and shall behave the same as wired DMX. Only Vision Control Behavior 255, App Control, uses fixed app-specific defaults for the current Vision DMX frame.
    • It is basically DMX with some additional options. Please read the Vision DMX Chapter carefully:
    • Test your DMX personalities under Test DMX.
  9. Define DMX Footprint for App Control
    • Legacy naming: App Control Configuration was previously called Creative Configuration or Creative Config in older app versions, screenshots, and URLs.
    • Configure the DMX footprint for app usage: App Control Configuration.
    • Test the configuration in the app: App Control Test.
  10. Add Optional Features
    • If additional features are required, implement them now: Features.
  11. Generate Final Firmware Package
    • Create a new DFU file with the latest firmware.
    • Do not forget to increase the version number so it differs from your initial DFU.

Server Registration & Release Preparation

  1. Register the Fixture on the Vision Web Service

Verification, Certification & Production

  1. Verify Signal Quality
    • Use our reference measurements to ensure your radio design has sufficient signal quality: Test Radio
  2. Verify Functionality
    • Use verification mode to ensure all functions work correctly: Verification.
    • You receive a verification certificate that can be uploaded to the Vision Web Service.
  3. Obtain Certifications
    • Before official distribution, ensure your product has passed all required certifications.
    • See Certification Overview.

© KKT Künzler Technologies GbR.
Developed by KKT - Künzler Technologies GbR