Sean Meighan

Software => Xlights Setup => Topic started by: JonB256 on December 17, 2020, 07:36:32 AM

Title: Odd Warning Message from "Check Sequence"
Post by: JonB256 on December 17, 2020, 07:36:32 AM

I'm getting this Warning message when I do a Check Sequence in Tools

Multiple outputs with same universe/id number
    WARN: Multiple outputs (2) with same universe/id number 64001. If using #universe:start_channel result may be incorrect.

I don't have anything specifically defined by Universe/ID number and not at that value of 64001.

And I don't have anything really going wrong, but it is a Warning message so I'm curious.

Title: Re: Odd Warning Message from "Check Sequence"
Post by: Gilrock on December 17, 2020, 08:20:45 AM

It sure is easier for us if you do Tools -> Package Log Files and post it.  Otherwise maybe search with Notepad++ in the xlights_networks.xml file for the value 64001.

Title: Re: Odd Warning Message from "Check Sequence"
Post by: JonB256 on December 17, 2020, 12:52:29 PM

I've attached the xLightsProblem.zip file.
The 64001 number appears many times in the "ModF9B.tmp.csv" file but nowhere else. Something to do with the Start Channel assignment (some are Absolute entries, some are "follows xxxxx" ) but none use Universe designations.

My network definitions are minimal and "NULL" because I manually configure my controllers.

As I said, this doesn't appear to cause any problem and has probably been there for a long time, I was just looking at Warnings.

Title: Re: Odd Warning Message from "Check Sequence"
Post by: keithsw1111 on December 17, 2020, 12:56:10 PM

We provide a way to associate an if with controllers that don?t support universe numbers to make it possible to support the #universe:channel addressing format. If the ids are not unique then clearly this becomes ambiguous and hence the warning. If you are not using that method then you can ignore it as the message suggests.

Title: Re: Odd Warning Message from "Check Sequence"
Post by: JonB256 on December 18, 2020, 02:40:32 PM

This message was caused because my Network setup consisted of two NULL entries instead of just one.

My setup has a Master and two Remotes. There is no channel overlap between the two remotes, so I created a NULL entry for each. While I still don't know where the "64001" value came from, once I changed the setup to a single NULL entry that covered 100% of my channels, the Warning goes away.