Issues with KiNet

139 views
Skip to first unread message

DaAwesomeP

unread,
Feb 25, 2019, 10:41:26 PM2/25/19
to open-lighting
Hi all,
I have a ColorKinetics PDM-202 and a strip of 46 FlexSL lights. I can control them flawlessly in the Phillips Quick Player program, but OLA is struggling with them.

After I defined the IP in the KiNet config file, OLA properly sees the controller/power supply and connects to it. What is weird is the addressing and control:
  • Adjusting channel 1 causes the first LED to go from green to yellow
  • Adjusting channel 2 causes the first LED to go from blue to cyan
  • Adjusting channel 3 causes the first LED to go from off to dim blue
  • This repeats somewhat sporadically for the remaining channels
  • Adjusting some channels occasionally causes other LEDs to go to random colors
  • After a while of not touching them, the LEDs will go off or go to green (random ones)
  • Sometimes when adjusting the faders/channels in the OLA web UI, they jump to a certain value after setting them (I am sure that it is not my mouse moving horizontally)
Have I simply mapped or configured something incorrectly?

Thanks,
Perry

DaAwesomeP

unread,
Feb 25, 2019, 10:42:01 PM2/25/19
to open-lighting
This is OLA v 0.10.3 on a Raspberry Pi.

Peter Newman

unread,
Feb 26, 2019, 8:08:03 PM2/26/19
to open-lighting
Hi Perry,

I think the discussion in here is relevant:

I'm aware there are KiNet v1 and v2 protocols, I'm guessing the PORTOUT thing may be the other version, or perhaps it's more subtle than that.

It sounds like it's almost there, and you have the key things of a working KiNet receiver and a working transmitter, so a bit of Wireshark work out to yield the solution. Similar to this FAQ question, you're probably best placed to add the support, but I'm happy to help where I can:

DaAwesomeP

unread,
Feb 27, 2019, 12:59:16 AM2/27/19
to open-lighting
I see. I don't know if I would be successful, but I could give it a whirl when I find time. Is there a document specifying how KiNet works and the protocol specifics?

Thanks,
Perry

DaAwesomeP

unread,
Feb 27, 2019, 1:14:46 AM2/27/19
to open-lighting
OK, I'm experiencing something very strange. When I control the LEDs from the DMX keypad or the faders in the OLA web UI, I have the strange output above. However, if I control them via sACN from QLC+, they work perfectly!

Peter Newman

unread,
Mar 1, 2019, 11:41:35 AM3/1/19
to open-lighting
I don't think KiNet is generally well documented, it's been reverse engineered I believe, we've got some stuff (including in kinet.cpp in our source code) which is part ay there. I've also created this issue to gather together some of the info:

Do you mean QLC+ -> sACN -> OLAd -> KiNet?

What does ola_patch show?

Does the same thing happen if you use ola_dmxconsole?

New or old Web UI?

Does ola_dmxmonitor show the unexpected channel values too?

Other than that, olad -l 4 logs may help:

Peter Newman

unread,
Sep 10, 2022, 10:19:30 AM9/10/22
to open-lighting
Hello Perry and other interested parties. I've finally made some progress on this having had access to a good test device.

The draft PR is here, along with some comments and questions which I'd appreciate input on/answers to (commenting on the GitHub PR or here is fine).

I still need to add the bit of code to actually send from OLA with this new code, but at that point any real world testing would be appreciated too!

This will finally add Kinet PORTOUT/v2 support to OLA hopefully.
Reply all
Reply to author
Forward
0 new messages