Lag on hub2 strings?

[lorajoslyn]

I have my sequence up and running but periodically will have a lag on 4 strands of my mega tree - the only ones on hub #2.

You can see what im talking about here

You are not allowed to view links. Register or Login

Im having a challenge trying to isolate whether its a hardware, firmware, software, or user error.

Using LSP ver 2.5 but 2 revs preious
Etherdongle, verified firmware is v2
Smartstrings all ver 3
Hubs haven't verified version but didnt think the firmware changed.
Exporting LSP to xlights via light elf.

The practical person in me is saying to just leave it be, but my obsessive compulsive personality is winning.

Anyone else having similar issues?

Sent from my SPH-L710 using Tapatalk 2

[bcstuff]

I have noticed a slight lag on the second hub after updating to etherdongle v2 firmware. I am using xlights with v1 controllers. I am planning to add the constantly updating data in the first 512 channels. I am also going to try to turn off unused channels at the end off sequences to see if it helps.

Update:
Looks like the added data on the first 512 channels helped make the lag go away for everything but my star which is on the second hub with 8 strings from the back of my tree. The back of the tree seems to be moving fine but the star is lagging.

I don't feel like taking the star down again, but it may be related to the v3 mod that I did to those controllers. I had trouble and couldn't get them to work so I had to change them back to v1. I have to work a lot the next couple of days but this weekend I might try switching them to hub 1 to test if it is hub related or possibly swap the controllers.

[JonB256]

Which Pixelnet Out port are you using on Hub #1 to feed Hub #2?

The direct output one or the RS485 regenerated one?

[travailen]

Does it make a difference if you go into hub 2 first and then hub to 1?  If it does then
What if you went from the ED to a splitter. Then from the splitter to each hub?

Rick S

[chrisatpsu]

Which Pixelnet Out port are you using on Hub #1 to feed Hub #2?

The direct output one or the RS485 regenerated one?

both Pixelnet output jacks are regenerated

[rm357]

What addresses are you using for the lagging ssc?

If the start address + 3 * number of nodes programmed > 4096, that could be your problem.

[johno123]

If the start address + 3 * number of nodes programmed > 4096, that could be your problem.

Help me understand this one - are you thinking that it's due to crossing over the universe boundaries?

[chrisatpsu]

either that,or the start address was programmed to match the sequencer channel number
example

programming a controller to start on the second pixelnet universe with a start address of 4097, instead of channel 1

[johno123]

Very interesting.  I could have this very issue - and your example is exactly what I have.

On my second hub, I have it set for pixelnet universe 2 using jumpers.  In LSP I have the channel set to 4097.  In the programming utility, I programmed the SSC with 4097.

Did I miss a post somewhere where I should have programmed that SSC as 1? 

[chrisatpsu]

SSC's are only programmed with a start address of 1-4096

and you need to tuck in that last node on the string under the 4096 also.
universe stops counting at 4096, (or else you wouldn't need another universe)

the next universe is exactly that, a new universe, so the channel counts starts over at 1


so a pixelnet etherdongle would be...

universe    channel count for the ssc       sequencer software 
uni1          1-4096                                 00001-04096
uni2          1-4096                                 04096-08192   
uni3          1-4096                                 08193-12288
uni4          1-4096                                 12289-16384

[chrisatpsu]

as a side note...  when you program your DMX stuff, you can only program it for channels 1-512 or it doesn't work

pixelnet is the same, except you're working with blocks of 4096 channels, instead of 512

[smeighan]

SSC's are only programmed with a start address of 1-4096

and you need to tuck in that last node on the string under the 4096 also.
universe stops counting at 4096, (or else you wouldn't need another universe)

the next universe is exactly that, a new universe, so the channel counts starts over at 1


so a pixelnet etherdongle would be...

universe    channel count for the ssc       sequencer software 
uni1          1-4096                                 00001-04096
uni2          1-4096                                 04096-08192   
uni3          1-4096                                 08193-12288
uni4          1-4096                                 12289-16384

I have three hubs

I programmed them 1 to 11,000 using the v3 ssc's,
I got lag on the first hub.

I then went back and programmed them 1to 4096 on each of the three hubs. I got lag on hubs 1. And 2

I am using ver c of xlights.

My first channel on the first hub was 497. This is in the end of the first universe.

I then added one string for a fire stick and set it for channels 1 to 384 on the first hub,
All lag disappeared,

Because it is easier, I am again programming the three hubs as channel 1 to 11,000

No lag, all effects are as expected.

I have the pix lent and Dix jumpers set to
1 and 1 on the first hub
2 and 2on the second hub
3 and 3 on the third hub

A side note, I did not get lag when I ran the show directly from vixen, only xlights.
But adding a string from channel 1 to 384 so,ved the xlights lag.

[chrisatpsu]

true but if you have a channel in the 2nd, or 3rd universes, the ssc needs to be programmed with the smart string utility with a channel between 1 and 4096 with the string not exceeding channel 4096

[chrisatpsu]

once you hit channel 4097, the information for that channel is coming across the next pair of wires in the cat5 cable from the etherdongle.

[johno123]

SSC's are only programmed with a start address of 1-4096

and you need to tuck in that last node on the string under the 4096 also.
universe stops counting at 4096, (or else you wouldn't need another universe)

the next universe is exactly that, a new universe, so the channel counts starts over at 1

Amazing - I'll re-program my SSC's to take note of this, but it appears that most of my SSC's on that second hub didn't care, except I did have some rainbow nodes that I always assumed were due to a V2 vs V3 SSC fix issue.  I wonder if the team was smart enough to have the SSC addressing utility automatically drop it back to 1 if I try programming for 4097....

Sorry to hijack the thread.  Carry on!