Beiträge von ScruffR

Thanks for the clarification.
I'm looking forward to the next release where HW LED count won't be hidden (or maybe user choice to unhide when needed).

I found the source of my issue.
For some reason this screen is missing the input field for the total number of LEDs so the default of 100 is assumed and thus only 300 bytes are sent even when the LED Layout is set correctly (140+140+70+70).

However, after a lot of clicking and messing around I once manged to get the total LED count field displayed and once I entered the correct value I did get the correct UDP packet size.

This does appear to be a bug IMHO.
I also dare to ask whether having to provide the total LED number in two places isn't somewhat redundant. Shouldn't the number of LEDs set in the layout suffice? At least when the number set in the layout exceeds the "total LED count" shouldn't the greater of the two be used?

Thanks @TPmodding
I did, but all the places I was looking therein I didn't come across that one and since GitHub search is next to useless I didn't find that when searching for rawudp.

I'll have a read through that code and see whether I can find a reason for the 300 byte limit.

I tried to find some info about the "protocol" used for rawudp but I must have looked in all the wrong places.
So I went ahead and tried to reverse engineer it by just catching the UDP packets but soon got some surprises.

While it is quite obvious that each LED gets its own 3 byte block in the packet I only ever get 300 bytes long datagrams which is only worth 100 LEDs but I'd need 220+ LEDs. How is that? Where is the data for the rest of LEDs and how do I get to it?

Also is there some comprehensible list of possible commands a rawudp controller could send back to the server?