kinet v1 kinet v2 protocol to support Philips Color Kinetics lights system

[bvbek1@gmail.com]

It would be nice if the xlights could send data over IP directly to Power supply Philips Color Kinetics. They use Kinet v2 protocol what is similar to Artnet. Philips got huge experience with architectural lightnings system and now we can buy very cheap this devices so...
How is a chance for add this output protocol in future?

[keithsw1111]

If we ever lay our hands on samples to test with maybe. If someone had the protocol it could get added speculatively but only if someone agreed to test it for us.

[bvbek1@gmail.com]

Hypothetically... How this process should looks like in real life to achieve that?

Entry level is quite expensive but system itself is similar (topology) like xlights/FPP->Falcone controller->light fixtures(ws2811).
In case of Philips we got LSE(some PC/server unit called Light System Engine)->over Ethernet power supply with some kinet server receiver on board->LED fixtures.
LSE->sPDS-480->Icolor flex LMX lights.

The most expensive part is Philips LSE in this setup so xlights/FPP could easy replace it and then we got access to really nice hardware what in second hand market (ebay) is cheap now.
Alternative way is to use this system without LSE is MADRIX(require license) or OLA like protocol converter gateway but xlights doing the best job in terms of mapping in the market(IMO) and works in live so we can determinate something is working or not I very fast way.

Using Philips software "quickplay pro" I can send over Ethernet package/frames directly to power supply command to change brightness in first light/LED in first port(IP:x.x.x.x, universe:x, num:ports:x) then next for secound LED in secound Port ETC.
Capture this change/command in wireshark and provide UDP payload/protocol how this looks like in real life.

I am happy to be a beta tester in next stage.
I got access to:
PDS-150->colorblast
sPDS-480->Icolor flex LMX lights.
PDS-60ca-> iColor Flex MX
Some old LSE, Controller Keypads, old iplayer.

There is python script who allow to manage simple standard LED fixtures (similar Philips Setup but only 3 colorblast per power supply).
python->PDS-150-> colorblast.
https://github.com/vishnubob/kinet#Fixture

Also OLA allow to make some convert protocol ARTNET->KINET
https://wiki.openlighting.org/index.php/KiNET

I am going to test FPP with OLA Kinet protocol Output to but documentation is limited about that.

I believe few people will be happy to see this protocol in xlights to.

[keithsw1111]

Are you saying if we sent DMX data wrapped by this header addressed to a KiNET device IP address it would work? https://wiki.openlighting.org/index.php/KiNET

[bvbek1@gmail.com]

Well.. have a look.

My header/payload is little different from example :https://wiki.openlighting.org/index.php/KiNET
I thing header from wiki example is for different power supply like PDS-150. I will have a look and paste  PDS-150 header to but for now header from ->pds480ca-24V

data 536 bytes  send to Power supply(pds480ca-24V) kinetv2 protocol header (source wireshark)
04:01:dc:4a:01:00:08:01:00:00:00:00:ff:ff:ff:ff:08:db:00:00:00:02:00:00:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c:3c

04:01:dc:4a          # magic, L   sPDS480 this value is always the same
01:00            # ver, H   sPDS480 this value is always the same
08:01           #type, H   sPDS480 this value is always the same
00:00:00:00           # seq, L  sPDS480 this value is always the same
ff:ff:ff:ff           # timerVal V, L   sPDS480 this value is always the same
08     #value is corresponding with  nr. port in pds480ca-24V power supply where is light string connected.
db      #from QuickPlaypro who change this value with NEW update , Madrix this value is always 00
00:00:00:02:00:00             sPDS480 this value is always the same
3c:3c:3c      # this is where DMX:RED:GREEN:BLUE value first "light" in string.

in attachments is example topology and header+DMX first light set to red "72:00:00"(RED:GREN:BLUE)

[bvbek1@gmail.com]

Kinet v1 protocol
Data send to Power supply PDS-150 Light (colorblast 12)connected to A port assign to DMX channel 1
I was right. Example from WIKI was kinetic v1 protocol header.

This time Only first channel/light is turn on(RED:255 brightness)
data 536 bytes send to Power supply(pds-250) kinetv1 protocol header (source wireshark)
04:01:dc:4a:01:00:01:01:00:00:00:00:00:00:00:00:ff:ff:ff:ff:00:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

04:01:dc:4a  # magic, L  pds150 this value is always the same
01:00              # ver, H   pds150 this value is always the same
01:01              #type, H   pds150 this value is always the same
00:00:00:00   # seq, L   pds150 this value is always the same
00                         # port, B   pds150 this value is always the same
00                         # padding, x   pds150 this value is always the same
0000                     # flags, H   pds150 this value is always the same.
ff:ff:ff:ff           # timerVal V, L  pds150 this value is always the same
00                         # uni, B for pds150 this value is always the same (PDS150 allow connect max 6 lights->18DMX channel).
ff:00:00           #1 channel DMX-COLOR RED:GREEN:BLUE

In attachments: topology PDS150->colorblast12  and header+DMX first light set to red "ff:00:00"(RED:GREN:BLUE)

[keithsw1111]

I am not sure i understand this value:

08     # uni, B. I use port nr8 in pds480ca-24V power supply. when I use port nr1 this will be 01 ETC.

there are a number of terms here I dont fully understand.

[bvbek1@gmail.com]

I wish to have official documentation from Philips but...

I am sure this value is corresponding with physical ports/sockets on back of sPDS-480ca (have a look in attachments).
Is possible Philips simple assign universe per one port where is string addressing light (similar to ws2811) connected to. Or I make mistake with assigning and I should assign this  value to position "# port, B" (from wiki docks)

for example in PDS-150 this value is always 00 because they do not have any ports.

edit:
now should be more clear explained.
08     #value is corresponding with  nr. port in pds480ca-24V power supply where is light string connected to.

[bvbek1@gmail.com]

This screen coms from "device manager" in Madrix.
Madrix is able so search kinetics devices in network.
This is result when I got sPDS 480 connected to my laptop over ethernet.
Is clearly 8 universes.

[bvbek1@gmail.com]

Two different applications send the same command (turn all lights on port8) to pds480 power supply.
04:01:dc:4a:01:00:08:01:00:00:00:00:ff:ff:ff:ff:08:db:00:00:00:02:00:00:ff:ff:ff..QuickPlaypro->pds480 kinetv1 ?
04:01:dc:4a:02:00:08:01:00:00:00:00:ff:ff:ff:ff:08:00:04:00:00:02:ff:0f:ff:ff:ff...   Madrix ->pds480 kinetv2

Two different applications send the same command to pds150 power supply
04:01:dc:4a:01:00:01:01:00:00:00:00:00:00:00:00:ff:ff:ff:ff:00:ff:ff:ff...  QuickPlay pro ->pds150 kinet v1
04:01:dc:4a:01:00:01:01:00:00:00:00:00:00:00:00:ff:ff:ff:ff:00:ff:ff:ff...  Madrix ->pds150  kinetv1


04:01:dc:4a:01:00:09:01:00:00:00:00:00:00:00:00    broadcast hallo call from madrix to 10.255.255.255


Well... not everything is identically but both working.

[keithsw1111]

I cant promise I have it right as there are still some unknowns here but .52 will contain an experimental implementation. Feedback is welcome as I cant test beyond looking at packets in wireshark.

[bvbek1@gmail.com]

You're a STAR !!!!

[keithsw1111]

I doubt it will be right first time.

[bvbek1@gmail.com]

So they will be in second...
Seriously... I am happy you will even try

[keithsw1111]

So did it work?