Pixie16 Won't Load Past 100 Nodes

[DeBoardfam]

Been having issues with my new Pixie16.  I do pixie config and change it to 150 nodes in HU.  I up HU to 150 nodes on the test screen and turn it on, but nothing past 100 will light in HU test or sequencer. I factory reset the unit. Set it back up. Same thing.   When I reboot, the setting in HU is changed back to 100. Setting doesn't seem to stick.  Any ideas other than what I already tried. 

Thanks!

[dibblejr]

Hopefully our discussion will resolve this.

Anyone reading this

While configuring a pixie16 the Logical Resolution of 100 has nothing to do with the number of pixels. ( that is covered in the manual and my tutorial in the General Hardware section at the top) The OPs was set to 100. 

This should be set to 50 from the factory for normal operation.

If set to 1 - it treats the pixels as if they are dumb nodes.

If set to 100 the last pixel becomes the first pixel.

Also if you are having problems try a factory rest. If that doesnt work try the FW update.

FW 1.05 is out and requires software v 4.4.34 or higher 

JR

 

Edited October 28, 2020 by dibblejr

[TheDucks]

IIRC HU TEST only does 100.  (at least for 4.x)

Make a simple sequence  to test higher counts.

[dibblejr]

20 minutes ago, TheDucks said:

IIRC HU TEST only does 100.  (at least for 4.x)

Make a simple sequence  to test higher counts.

All work in testing when you select higher node counts in the configuration.

JR

[dibblejr]

The OPs problem;

When he purchased the controller from LOR it had the extra jumper.

Since he is using LOR nodes he did what the document said and installed the jumper.

He just told me about it and when I was going to text him to remove it, he did so and 

All lights work in test mode.

Now he has lights.

JR

[DeBoardfam]

Thanks for the help JR. This one was driving me nuts.  Then I just started running through everything.   Tested my other Pixie16 and it worked.  The only difference I could find was the jumper.  Fixed me right up though.