Falcon Christmas

The Lab (Technical Talk) => Protocols and File Formats => Topic started by: esset on September 27, 2020, 03:31:31 AM

Title: Cleaning and speeding up config
Post by: esset on September 27, 2020, 03:31:31 AM
Hi, I'm trying to optimize my setup even if it's working how it's setup now.
fpp master.png
SanDevices_E682.png
SanDevices_E6804.png
xlights.png
(I'm sorry if I post in wrong category so moderator feel free to move my thread.)

My setup with master, remotes and bridges



Everything seem have working but I would like to fix some errors and speed up the net as much as possible.

Here is an output from xlights.
Multiple outputs with same universe/id number
    WARN: Multiple outputs (4) with same universe/id number 1. If using #universe:start_channel result may be incorrect.
    WARN: Multiple outputs (4) with same universe/id number 2. If using #universe:start_channel result may be incorrect.
    WARN: Multiple outputs (4) with same universe/id number 3. If using #universe:start_channel result may be incorrect.
    WARN: Multiple outputs (4) with same universe/id number 4. If using #universe:start_channel result may be incorrect.
    WARN: Multiple outputs (4) with same universe/id number 5. If using #universe:start_channel result may be incorrect.
    WARN: Multiple outputs (3) with same universe/id number 6. If using #universe:start_channel result may be incorrect.
    WARN: Multiple outputs (3) with same universe/id number 7. If using #universe:start_channel result may be incorrect.
    WARN: Multiple outputs (3) with same universe/id number 8. If using #universe:start_channel result may be incorrect.
Title: Re: Cleaning and speeding up config
Post by: pixelpuppy on September 27, 2020, 07:49:02 AM
You have the same universe numbers defined on multiple controllers.   Universe numbers should be unique across the whole network.

In other words, you have Universes 1-8 defined for the E6804 and then you defined the same Universes 1-8 on the E682.  A better method would be something like defining Universes 101-108 on the E6804 and Universes 201-208 on the E682, and then Universe 301-308 on your first pi, Universe 401-408 on your 2nd pi, etc.
Title: Re: Cleaning and speeding up config
Post by: esset on September 27, 2020, 08:13:25 AM
Quote from: pixelpuppy on September 27, 2020, 07:49:02 AMYou have the same universe numbers defined on multiple controllers.  Universe numbers should be unique across the whole network.

In other words, you have Universes 1-8 defined for the E6804 and then you defined the same Universes 1-8 on the E682.  A better method would be something like defining Universes 101-108 on the E6804 and Universes 201-208 on the E682, and then Universe 301-308 on your first pi, Universe 401-408 on your 2nd pi, etc.
Thank you, that's what I suspected when I saw the error message. It has worked well but wants it right so I redo it as you suggested. It also said that I had large empty channel jumps between models, does the performance affect very negatively?

Also, now I'm using several rasberry pi in BRIDGE mode over 100Mbit cat5 network, will SLAVE mode have better refressrate since the data is splitted to different units?
The reason I use BRIDGE mode is that is that I had some issues with SLAVE mode few years ago. The slaves freezed and had to be manually reset several times per day. Maybe fixed on todays releases.
Title: Re: Cleaning and speeding up config
Post by: Poporacer on September 27, 2020, 08:44:02 AM
Quote from: esset on September 27, 2020, 08:13:25 AMIt also said that I had large empty channel jumps between models, does the performance affect very negatively?
That is usually due to having more universes configured than you are actually using. Even if you aren't using it, the player is sending out the data for those universes. (it looks like one of your sandevices only needs 6 Universes and you are sending it 8) 

I would strongly recommend using the features in xLights to let it manage your controllers. For each controller, select the Vendor, Model and Variant. Make sure the Universe start number is correct (101,102,103, etc.) Then select the Auto Layout Models and Auto Size options. Once you have that done, then go to the visualizer on each controller and make sure the models are on the ports you want. If not, put them where they belong. (you might get some error messages as you do it, that is normal...until you are finished anyway) Save the settings in your Controller tab AND in your layout tab. Then go to the Controllers tab and use the upload feature at the bottom right. Upload inputs, then outputs. xLights will configure your ports, Universes, etc. for you. I know this might sound like a lot or confusing, if so, jump in the Zoom room and the people there can walk you through it.
Title: Re: Cleaning and speeding up config
Post by: esset on September 27, 2020, 12:11:25 PM
Quote from: Poporacer on September 27, 2020, 08:44:02 AMI would strongly recommend using the features in xLights to let it manage your controllers.

Wow, that looks very interesting and usefull when the network grows. It have been difficult to track all settings and all controllers.
Title: Re: Cleaning and speeding up config
Post by: Bwinter on September 27, 2020, 12:53:08 PM
Quote from: Poporacer on September 27, 2020, 08:44:02 AM
Quote from: esset on September 27, 2020, 08:13:25 AMIt also said that I had large empty channel jumps between models, does the performance affect very negatively?
That is usually due to having more universes configured than you are actually using. Even if you aren't using it, the player is sending out the data for those universes. (it looks like one of your sandevices only needs 6 Universes and you are sending it 8)

I would strongly recommend using the features in xLights to let it manage your controllers. For each controller, select the Vendor, Model and Variant. 
What's the recommended approach when your controller isn't listed?  I've been trying to configure the controllers (as recommended), but not seeing options on how to manually generate
Title: Re: Cleaning and speeding up config
Post by: Poporacer on September 27, 2020, 02:34:10 PM
Quote from: Bwinter on September 27, 2020, 12:53:08 PMWhat's the recommended approach when your controller isn't listed?  I've been trying to configure the controllers (as recommended), but not seeing options on how to manually generate
What controller is it that isn't listed and how are you using it in the scheme of things? Do you have any of the controllers that are listed?
Title: Re: Cleaning and speeding up config
Post by: Bwinter on September 27, 2020, 03:12:09 PM
Quote from: Poporacer on September 27, 2020, 02:34:10 PM
Quote from: Bwinter on September 27, 2020, 12:53:08 PMWhat's the recommended approach when your controller isn't listed?  I've been trying to configure the controllers (as recommended), but not seeing options on how to manually generate
What controller is it that isn't listed and how are you using it in the scheme of things? Do you have any of the controllers that are listed?
I have several Crocket and my own DIY PiHats (two output), 6-output PiHats (several) and pixel-splitters.  I guess (?) I could just use the FPP-PiHat in place of the 2-port Crocket/DIY version (although, not 100% sure they are a direct-comparison).  Not sure how to apply the others, though.

I'm presuming that the normal (and generic/DIY versions) PiHats use the DDP protocol, as opposed to the OPC protocol ("used by some DIY Arduino/Raspberry controllers")?

I guess I'm just struggling with converting from my prior methods of absolute channel numbering, versus this universe-based scheme.  To clarify, I can still use absolute channel numbering with the new 2020 xLights, without assigning any controllers (as I always have done in the past)?
Powered by SMFPacks Menu Editor Mod