Did anyone ever make any progress in deciphering the protocol or packets used between LED Studio and the receiver boards when not using a sender card? I work on an Open Source program called the Falcon Player (aka FPP) available via
http://FalconChristmas.com FPP can currently be used to drive the LED panels directly from a Pi or BBB using a couple different Open Source libraries, but I would like to add support for driving Linsn receiver boards directly over Gig-E as well. I already have code to drive ColorLight receiver boards directly over Gig-E, but they use a different protocol.
I'm not currently interested in configuring a sender card, I would like to bypass the sender and send packets directly to the low-cost receiver boards.
I have been able to look at the packet capture posted earlier in this thread as well as some others I have performed and I made a simple script to take the data and put it into a raw data file which can be viewed using ImageMagick or any other program that can display raw RGB data. The image is discernable, but not exact. The Linsn protocol is not as simple as the ColorLight protocol which uses one packet per row of display. The Linsn protocol appears to pack the data together to have a more efficient packet-per-frame count, but it also appears to be padded or encoded in some way because the data in the file does not match the colors on the actual computer screen or LED panel.
I have written some test code and am able to make the LED panels blink by sending packets from Linux to my RV908T, but the panels don't display any correct data because I am not formatting the RGB data correctly in the packets.
Has anyone else made any more progress on this, or is currently working on or interested in driving the Linsn receiver cards directly?