Recent Posts

Pages: [1] 2 3 ... 10
1
F16V3 Pixel Controller / How to map universe to port Diff Reviver?
« Last post by jerryw on Today at 03:27:19 PM »
How to map universe to port Diff Reviver?
Darn read the example in the manual pages 90+
I canít seem to figure out how to map a Universe to a differential receiver port.
I have differential receiver on output 3 on expansion board (25,26,27 and 28).
Universe 1 through 5 is being used to run a mega tree 16strings, 50nodes, 4 spi ports out.
Thatís 200 nodes per port starting with universe 1 on port 25.
xLights setup is number 1 through 5 with universes 1 thought 5
Address start at 1 through 2550
In F16v3 setup in String port 25 start channel says 7171 through 28 end 7621?
Port 25 Ė 28 is set to 200 pix each.
I tried Absolute addressing and Universe start channel.
I would like to manually program xLights and F16v3 to learn how it works together.

This is my first time using the F14v3 and for sure I do not know how to map universe to out port.
Thanks,
Jerry
2
/home/fpp/media/logs

3
Thanks .. but I dont see an access log in there. Can I turn it on somewhere?
4
Falcon Player (FPP) / Re: Loaded 2.3 now having playlist issues
« Last post by jnealand on Today at 02:38:54 PM »
I've taken to keeping a spare uSD all ready to go.  since I keep all my config files on a USB drive I just swap the uSD and power up.
5
DMX/E1.31 / Re: Xlights/F4V3 Setup Help
« Last post by JonB256 on Today at 02:36:49 PM »
I know it can be done, just getting to work seems to be my issue. When my first prop is a hundred pixels, which is 300 channels, but the Falcon says an end channel is something like 56 is confusing.


If the "end channel" is an unexpected number, then your start channel probably didn't start at the beginning of a numerical universe (and it does not have to)  Whether you use 510 or 512 or something smaller as a universe size.

For example, if you did 4 props, each of them 120 pixels. Universe size of 510.
The first prop, Universe 1, would get 1 thru 480 channels. (that leaves 30 channels)
The second prop gets those 30 and then 450 into the next universe (that leaves 60 channels)
The third prop gets those 60 and then 420 into the next universe (that leaves 90 channels)
and fourth prop gets those 90 and then 390 into the next universe (leaving 120 channels unused, but available for use by another prop, but you could leave it unused, and start the next series of props at a Start channel of 1 in a fresh universe)

Now, full disclosure - I don't pay that much attention to universes - I work in Absolute channels, using an Excel spreadsheet to help. For me, that currently starts at 1 and goes up to 154,624 in xLights. Divide that by 512 and that is 302 Universes. Certain props (big ones) I always start at a channel 1 of a Universe. If multiple smaller, related props can squeeze into a few universes, I run them "end to end" with no gaps between.

I don't know if this helps or makes it worse, but Pixels and controllers and xLights are a numbers game.
6
Falcon Player (FPP) / Re: Loaded 2.3 now having playlist issues
« Last post by JonB256 on Today at 02:16:31 PM »
I ended up re-imaging and it works now.  Not sure why, but I'm going with it!

Re-imaging is so much easier now. I used to avoid it because of the time it took.
7
If you have that logging enabled, they are under File Manager with a Tab for Logs.
8
F16V3 Pixel Controller / Re: Testing lights from F16V3
« Last post by JonB256 on Today at 02:13:12 PM »
Test or real - no difference

5 strings of 50 pixels? or 5 strings of 100?  At reduced power, I can see 250 pixels working. Even at reduced, 500 pixels would have data/color problems toward the end. It isn't the number of strings, its the number of total pixels.

People routinely do 200 at reduced power as one string without injection.
9
Falcon PiCap / export from Vixen3 to FPP w/ PiCap
« Last post by pixelUTfun on Today at 02:09:14 PM »
Hey guys,
Full disclosure up front.  I am a NOOB when it comes to pixels, FPP, and PiCap
This year I decided that I wanted to test the waters with RGB pixels.  I wanted to start small, so I purchased a PiCap and about 150 RGB pixels for the roofline on the front of the house.
(I ended up with 39 pixels for the roofline on the top, and 100 for the roofline on the bottom)

After some trial and error, I got all of the wiring correct so that when I go into 'test mode' in FPP, everything lights up and flashes and whatnot. 

Next step, lets set up a sequence!
I arbitrarily chose to go with Vixen3 and started creating a few sequences.  I exported from V3 and uploaded to FPP successfully.  Everything works when I'm just blinking and changing colors.  The trouble starts when I try to add a 'chase' from one side of the house to the other.  The top is no problem because its all one string...  The bottom is where I have trouble, because I had to cut and splice a few places to make it look clean.  On the bottom string, when I do a chase from left to right, it starts at about pixel 40 or 50 and goes left to pixel 100 and then goes back to pixel 1 and then again to the left where the chase started...  Maybe I mixed up the pixel addressing when I was doing some testing??

I'm pretty confident that its just a configuration error in FPP because its doing what I tell it to, its just starting in the wrong place.
Any guidance that you guys can offer would be greatly appreciated!

10
DMX/E1.31 / Re: Xlights/F4V3 Setup Help
« Last post by Powelln on Today at 01:46:40 PM »
I know it can be done, just getting to work seems to be my issue. When my first prop is a hundred pixels, which is 300 channels, but the Falcon says an end channel is something like 56 is confusing.


Sent from my iPhone using Tapatalk
Pages: [1] 2 3 ... 10
Back to top