Frankieswi Posted November 18 Posted November 18 I run 3 networks, LOR Regular on com7, AUX A on com4, and AUX B on com5. LOR Regular had 9 LOR 1600x controllers, all at firmware 1.15.....unit ID's 01-09. Same config for years. AUX A and Aux B are for Pixie8's running the LOR packaged pixel trees. Aux A is Unit ID's 21-28 and firmware 1.01, and Aux B is 31-38 with firmware 1.07. if I scan for 01-38 ONLY on LOR REG, it get ID's 01-09, as expected if I scan for 01-38 ONLY on Aux A, I get ID's 21-28, as expected if I scan for 01-38 ONLY on Aux B, I get ID's 31-38, as expected if I scan for 01-38 ONLY on the AUX networks, I get ID's 21-28 and 31-38, as expected. If I scan for 01-38 on LOR Reg AND either AUX A or AUX B, i get the expected results. When I try to scan all three networks, I get mixed results...sometimes 1-3 1600x's drop off.... sometimes one of the Pixies drop off.... it varies, but i have yet to get all 3 nets with all units. Any clue? I checked unit ID's on all controllers. I checked all ethernet cables. I am running S6.3.6 Pro. I've been running this config for 3 years now. It never happened on the S5 HU or earlier versions of S6. Is It a firmware issue?
k6ccc Posted November 18 Posted November 18 This has been happening at times for at least a decade - nothing new with S6.
Frankieswi Posted November 26 Author Posted November 26 Interesting. I haven’t had this happen before….
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now