Are there pre-existing firmware packages for Bluetooth modules such as BT840, BC833, or PTR98? Do we need to develop firmware for these modules ourselves, or will you provide it? We will provide the firmware for the Bluetooth module. You can find it under Section 3 at the following link: https://server.kk-t.eu/ExternalVision/TestPreparations. Each module's firmware is included there.
What is the "Vision Controller"? The "Vision Controller" refers to the Bluetooth module itself. It is sometimes also called the "Vision IC."
Does the Bluetooth module communicate with the MCU using SPI (External Implementation)? Yes, communication between the Bluetooth module and the MCU uses SPI.
In the Software section, I saw topics such as Vision RDM, Vision DMX, Vision Features, and Vision DFU. Are all of these topics intended to run on the MCU connected to the Bluetooth module (External Implementation)? Yes, these topics run on the MCU.
Where can I download these source code libraries? Will they all be provided? You can download them from the Software section of the documentation. Available libraries include Vision RDM (a generic RDM library with manufacturer-specific commands required by VISION) and Vision Features (e.g., for battery runtime). Please also review the basic example project, which shows how to implement all interfaces (RDM, DMX, and DFU) in a simple way. It uses both the VISION SPI and VISION RDM libraries: https://server.kk-t.eu/ExternalVision/ExampleSoftware
Regarding hardware: We will purchase all electronic components ourselves, such as the Bluetooth module, MCU, and other circuitry. You will provide the software, except for the MCU software which we must implement. Is that correct? Yes, that is correct. You purchase all hardware components. We provide the software for the Bluetooth chip, and your team develops the MCU-side software.
On the Pricing Plans page, are all "Modules" software components? And do the prices refer to software usage licenses? Yes, the listed modules are software modules, and the pricing represents software usage license fees.
For the pricing: for example, the "SPI Module" shows a price for quantities above 1000. Does this mean that if we produce 1000 fixtures, we need 1000 SPI Module licenses, each costing X euros? Yes. However, you do not need to buy all licenses upfront. We can also arrange a yearly contract that covers a higher volume, allowing you to benefit from lower pricing.
What could be the cause when the fixture disconnects from the Smartphone:
Check Signal strength. Should be better than -80 dBm.
Make sure the 32.768 kHz crystal has a Clock-Accuracy smaller than 20 PPM. Otherwise Bluetooth misses connection intervals which triggers disconnects.
Please Check FIXTURE_IS_ON Pin. Should be turned on all the time during normal operation.
Bad Power Supply. Check the 3.3V power supply of the Vision Controller if it is noisy or not stable.
Make sure PCB Routing with Capacitors is good.
We have our own DMX control and RDM libraries. Can we not use the RDM libraries and initialization in the examples? Yes. Vision is based on the same DMX and RDM concepts as wired DMX/RDM. In most projects, you should reuse your existing RDM decoder and DMX handling instead of adding a second independent RDM or DMX implementation. The required Vision SPI library mainly handles communication with the Vision Controller. In older documentation this was called the iQMesh library. In the current Vision SPI library you have two callback functions (DmxReceived, RdmReceived). Use these callbacks to pass received RDM and DMX data into your existing fixture logic. To write back RDM answers you can use vision_WriteRdm. If you use your own RDM library, implement the required Vision custom command: https://server.kk-t.eu/ExternalVision/RDMPIDVision – Attention: this is called GetVision and SetVision in the example rdm Library. Make sure you support the mandatory RDM Commands needed from the App. They are declared here: https://server.kk-t.eu/ExternalVision/RDMPID“ Using the DmxReceived callback there is one important difference compared with normal DMX. Each Vision DMX frame contains a Vision Control Behavior value. Value 0 means DMX Control with the fixture's saved DMX settings and should behave like wired DMX. Values 1-254 mean legacy DMX Control for the Vision DMX Adapter only, using a temporary DMX Personality override for this frame only. Value 255 means App Control with fixed App Control defaults. Please get the proper information from: https://server.kk-t.eu/ExternalVision/DMXIntroduction https://server.kk-t.eu/ExternalVision/DMXFrame https://server.kk-t.eu/ExternalVision/DMXPersonality“
