Falcon Controller v5 No output of lights

there has been no models or pixels sent to the falcon from xlights, all outputs on the falcon have 0 pixels setup
are youy visualiing the outputs then uploading ?
 

there has been no models or pixels sent to the falcon from xlights, all outputs on the falcon have 0 pixels setup
are youy visualiing the outputs then uploading ?
That screenshot clearly shows 100 pixels per output. Nothing has been sent from xLights but that's completely irrelevant for test mode to work, as long as configuration is here, which it is.

What behaviour is there when you use the test function from within the WebGUI and select the specific output?

Unrelated - but I would suggest changing the front page from "Universe/Channel" or E1.31 mode to DDP mode.
 
Xlights uses start channels and pixel numbers not universes ,
Yoy have all outputs set as channel 1-100 for 300 channels
Xlights would need the second port sent to 301as the start channel

Also set it to DDP as e131 is not as efficient
 
Yoy have all outputs set as channel 1-100 for 300 channels
Xlights would need the second port sent to 301as the start channel
That's totally irrelevant to the discussion at hand. Here we are talking that it's not even working in test mode. The poster is trying to get pixels to light up using just the controller.
ve got a falcon controller v5 and connected up controller and trying to use the onboard test function
Getting that working is unrelated to the sequencer application or its configuration. It could be xLights, vixen, or even a lighting desk, at this point, nothing is feeding the controller data, it's generating it's own pixel data.

Xlights uses start channels and pixel numbers not universes ,
xLights uses channel numbers internally ad to generate the FSEQ data. That's where it stops
When it sends (either output to lights, or via xScheduler, or FPP pulling from FSEQ) - it will output whatever the controller is set up for. If it's configured in E1.31, then it MUST use universes and channels. That's just how E1.31 works. DDP uses only channel numbers. In DDP mode, it could send that controller as raw channels (say 500-799, if those are the xLights channel nubers) or, it could always send it as 1-based - eg 1-300- despite it being 500-799 in xLights.

Also set it to DDP as e131 is not as efficient
The difference in efficiency doesn't matter to most people's shows.
It becomes an issue when you are using your show player with 100Mbps ethernet, and are outputting more than about 80,000 pixels worth of data. That's where DDP's lower overhead can help.
 
Back
Top