search

Pixelcontroller / f16v4_issues

F16V4 and F48V4 Issue Tracker
14 stars 0 forks source link

E131 protocol - config issues which resolved when changing to DDP #46

Open mcenerykwm opened 8 months ago

mcenerykwm commented 8 months ago

With XL set to E131... Updated to V27 firmware and with both F16V4 and F48V4NS - reuploaded inputs/outputs -- the controllers would not successfully send test pixel data to smart receiver chains ports -- could not be sent test data from XL 2023.16 nor would pixel tests on directly controller function as expected. Once protocol changed to DDP issues resolved with re-send of inputs/outputs. (this evening in zoom room user with similar issue which resolved once changed from E131 to DDP). Smart receivers V2.01 - Chained A and B receivers in same control box.

keithsw1111 commented 8 months ago

Are you using a good power supply? 5V or 12V. If using 5V then it needs to be a reasonably high current supply. 12V seems less of an issue.

mcenerykwm commented 8 months ago

Keith - re power supplies Meanwell - 12V 350W to all 3 boxes. (1-f48V4NS and 2-F16V4 variant 4 smart receiver chains - 3 chains in use. Now that on DDP all issues resolved -- Kevin

keithsw1111 commented 8 months ago

So this was not just the NS that had an issue ... but the regulat F16 as well. I would need to get with you on zoom to interactively debug it. If you are willing to do so drop me an email at support@pixelcontroller.com and we can find a time (after Christmas if that is better for you).