Strange F48 test mode issue

[lwillisjr]

I have a couple of ports on my F48 that won't send test data. If I check "All" ports and then "Enable" Port 1 does not send data (nothing on the prop), and in another example it does not send data to a string that is the middle of 2 other strings on the same port. Meaning Star Inner and Star Outer (below) are going through the color wash pattern while Star Mid is doing nothing. If I go to another page and then back to the test page these props show not selected (see below). If I check the 2 boxes below, nothing happens. If I go to another page and then back they are "not selected" again.

If I run a sequence direct from xLights the props are working fine. Just seems I can't get the controller to run them in a test mode.

Anyone experience anything like this?

You cannot view this attachment.

[TWW]

I am getting exactly the same problems as you on my F48. Test modes from FPP and output from the Pi or direct from Xlights work just fine, but port 1 and another refuse to do test mode. I changed receivers and leads as well to make sure it wasn't a problem before I saw your thread. It also won't work from selecting test mode using the push buttons on the F48.

I have an F4V3 with the same firmware (2.55) that works just fine, it just seems to be a problem with the F48.

You cannot view this attachment.

[zanclus]

I have a similar  issue , when I load tth test page channels 1-8 are not checked and no data sent. When I check "all" 1-8 become checked butI still get nothing on channels 1-8.  If I refresh the page channels 1-8 become unchecked again.

[zanclus]

I have a similar  issue , when I load tth test page channels 1-8 are not checked and no data sent. When I check "all" 1-8 become checked butI still get nothing on channels 1-8.  If I refresh the page channels 1-8 become unchecked again.

[k6ccc]

I have a similar  issue , when I load tth test page channels 1-8 are not checked and no data sent.

I can't help you with your problem, but PLEASE get out of the habit of referring to each output from a pixel controller as a "Channel".  Call it an output, or port instead.  Each output will normally have hundreds or even thousands of channels.  Calling a pixel controller output a "channel" only causes confusion.
And yes, an output from something like a 16 channel AC controller can be referred to a channel because it really is a single channel.  Even a dumb RGB controller can be confusing because people often refer to the three channels (Red / Green / Blue) as a single channel - and that is confusing...

[TWW]

I updated to firmware 2.58 tonight to see if that would help.

The test mode will not output on port one still IF I have it set to universe one, start channel one. If however I set the start channel to four, test mode works just fine on that port.

I also tried setting all the unused outputs from universe one to another one just to see if that had any effect, but that was no help.

[TWW]

OK latest update.

I did a factory reset to the F48 and downloaded the latest Xlights as it says it supports firmware 2.58.

Still no luck on the test mode when I uploaded my layout to the F48, however changing the start channel from 1 to 4 allowed it to work. Also upping the pixel allocation for the first 16 ports worked once, then stopped when I went back to the test page again.

All still works from the test options in FPP and sequences play just fine both from the Pi and direct from Xlights from my laptop.

UPDATE Nov 21st: Updated to firmware 2.59. Same problems.

[TWW]

First output still not working with most test modes, but 'chase' test option does work as it should.

Anyone else found this?

[mschneids]

Were you able to sort out the issue? I am running the 2.59 firmware and have some very odd/similar issues with test mode. I see in the release notes that some test mode issues were fixed in 2.58 but maybe some still exist?

[TWW]

Were you able to sort out the issue? I am running the 2.59 firmware and have some very odd/similar issues with test mode. I see in the release notes that some test mode issues were fixed in 2.58 but maybe some still exist?

Nope, still not working from F48 apart from when using 'chase' option (firmwar 2.59).


Works fine from F4V3 with 2.59.

[jnealand]

Those of us that have been here for years know that the built in test function is primarily reliable only for showing that the lights will go off and on.  Any other functions are best tested by creating short test sequences.  For my display I have 4 main test sequences and that cover every light in my display, i.e. whole house.

These are basically one line sequences with one effect for 30 seconds.  It you want it go longer put it on repeat.
1- Turn all lights red and do a bars down.
2. Turn all lights green and do a bars right
3. Turn all lights blue and do a bars left
4. Turn all lights white and do a bars up

If your display has been setup and matched to xlights correctly then every thing will look good.  If something looks bad you need to go back and look at your controller configs (at least that is my experience.

For grins you can also make the a sequence that puts the butterfly effect on the whole house and another that makes the whole house twinkle.

[mschneids]

Hi Jim,

I was trying to use the test function to test new strings and props. I'll stick to using my pixel tester for that now. I like the idea of the test sequences but unless I add everything to my layout I don't think that will work in this case.