Recent Posts

Pages: [1] 2 3 ... 10
1
BeagleBone Black Controllers / Re: PocketScroller...
« Last post by dkulp on Today at 05:24:58 PM »

No luck eliminating the ghosting using master-alpha and adjusting the panel lengths . I also see the ghosting on 128/128/128, 64/64/64, 32/32/32, 16/16/16, 8/8/8, 4/4/4, 2/2/2, 1/1/1. Let me know if you have anything else to try.


Wow.   If it ghosts on all of them AND with the Linsn/ColorLight setups, it really sounds like a panel hardware issue.   I'm not sure what to suggest at this point.   Drop the voltage down to 4.8 or so maybe, but other than that, I'm at a loss.    I was hoping one of the color levels or panel lengths or something wouldn't have the ghosting issue which we could use as a base to start with. 


If you want to experiment some, in the /opt/fpp/src/pru/PocketScrollerV1.hp file, in the DISPLAY_ON and DISPLAY_OFF macros, you could TRY adding a line like "SLEEPNS 200, r17"  (adjust the 200) before and/or after the  SET/CLR line that is in there.    You just need to restart FPPD after editing that file as it's re-compiled when fppd starts.     Possibly at the end of LATCH_HI as well.     


That said, I'm not expecting positive results.  It sounds like a panel issue.  :(
2
BeagleBone Black Controllers / Re: PocketScroller...
« Last post by Cjaqua on Today at 05:06:44 PM »



New "master-alpha" image is up at http://dankulp.com/bbb .   Can you give that a try.  Retry the various panel length settings to see if the ghosting goes away.  Let me know if anything works.


Next thing to try to help determine issues:   in xLights, set the color to full white, see if it ghosts.   Change color to "128/128/128" (hex 0x808080), then 64 (hex 0x404040), etc... to try and see which "bit" (or all) is causing issues.  (My gut feeling is that it's either the 0x808080 case or the 0x010101 case, most of the ghosting I've seen is the latter, but since the row is only set on the first case, I can see that being an issue as well)


How good are you with a Linux command line?   If I send various patch files, would you know how to apply them?

No luck eliminating the ghosting using master-alpha and adjusting the panel lengths . I also see the ghosting on 128/128/128, 64/64/64, 32/32/32, 16/16/16, 8/8/8, 4/4/4, 2/2/2, 1/1/1. Let me know if you have anything else to try.
3
One odd thing.  The IP is notified as:   2601:204:c000:f153::96d3 2601:204:c000f:153:1eed:ad50:d864:16a3
I guess the first part is the IPV6 address 2601:204:c000:f153::96d3 
Not sure what the second half is             2601:204:c000:f153:1eed:ad50:d864:16a3

I'll play some more later.

I thought I had disabled IPv6, but will check again, maybe connman decided it should try to change my mind.

On the Zero slowness, I'm not sure.  Can you go to the Troubleshooting Commands page and look at the 'CPU Utilization' section and see process what is consuming all the CPU?
4
Falcon Player (FPP) / Re: help with p10s and FPP
« Last post by k6ccc on Today at 04:17:48 PM »
For starters, you define four universes and two P10 panels.  A 16 x 32 P10 panel takes three universes, so two panels would take six universes.  Something does not look right on your LED Panels page however.  You have a matrix of two panels which should be 3072 channels, not the 1536 channels shown.

Second is a suggestion is to do initial testing with the channel test page.  If that does not drive the panels, your sequences certainly won't.  Once you have the test pages able to drive the panels, then you can worry about sequences.

Not sure about this one, but at least what I was told (and works for me), is for driving the P10 panels from the Pi (as opposed to driving E1.31 to some other device) you need to set the E1.31 to Unicast with the IP of your Pi as the destination.

I can't help you with sequences running in FPP as I only use Bridge mode.

Welcome to the P10 world (from another newbee)!
5
Falcon Player (FPP) / Re: help with p10s and FPP
« Last post by pixelpuppy on Today at 04:00:24 PM »
hi all i have just bought my first set of p10s, unfortunately i just can't seem to get them to work. i have a Pi 3b, a pi cape from Hanson electronics and  P10 full color led display module, indoor/semi-outdoor SMD RGB P10 LED panel, ...


What do you mean "indoor/semi-outdoor"?   I was under the impression that the Pi with matrix hat doesn't support the outdoor P10's if that's what you have
6
Loaded new image 20180221

Pi3 and 2B operate fine with eth0, wlan0 - tested E1.31 U1 50 pixels - work fine on FPP test page, even sequence test page.  No LED Panels here.

Moved uSD to Pi Zero.  Very slow, but workable.  2-3 seconds between WEB Screens - IE  STATUS to TEST.
(Don't drink coffee if you are going to work the WEB FPP Interface.)
Loading a 100k file aborted the first time ERROR: GATEWAY TIME_OUT
Immediately did a second attempt - worked fine.
Ran E1.31 lights, then LED Panels (2X2 P5's) then BOTH. - No seen issues.

Pi Zero is only running with the uSD and EDIMAX - other than slow, it is working fine for my tests
One odd thing.  The IP is notified as:   2601:204:c000:f153::96d3 2601:204:c000f:153:1eed:ad50:d864:16a3
I guess the first part is the IPV6 address 2601:204:c000:f153::96d3 
Not sure what the second half is             2601:204:c000:f153:1eed:ad50:d864:16a3

I'll play some more later.
7
Falcon Player (FPP) / help with p10s and FPP
« Last post by wilky37 on Today at 03:37:09 PM »
hi all i have just bought my first set of p10s, unfortunately i just can't seem to get them to work. i have a Pi 3b, a pi cape from Hanson electronics and  P10 full color led display module, indoor/semi-outdoor SMD RGB P10 LED panel, 1/8 scan allie express.i have watched numerous videos and read lots of posts and can't see what im doing wrong, i have bought new connector ribbons and even a new pi cape but still no joy. in the set up tab as soon as i tick the box saying enable led output the FPP won't work, it struggles to respond and won't play any saved sequences, i have a few screen shots if someone could just check the set up , i live in the UK so not as easy to get help, many thanks in advance Ian
8
F16V3 Pixel Controller / Re: My Falcon F16v3 Enclosure Build
« Last post by 4rjn on Today at 02:40:54 PM »
What printer do you have?
9

I changed the timeout to 900 seconds yesterday as the flash to eMMC takes over 11 minutes from my class4 card to the emmc on the BBB.
yeah thats' why I prefer to use the script for that instead of the GUI - at least I can see progress instead of a blank screen for 11 minutes  ;D


It is really limited by the CPU speed compiling, I'm not surprised that even the Class 4 can easily keep up.  This is the main reason we distribute compiled binaries for release branches.
Is there any kind of progress or status update that could be displayed while its compiling?  Its always nice for the user to see some feedback when things are going to take a few minutes to complete.  :)
10
At one point, I as wiping out the ccache when creating the images because the download would be a little bit smaller.   However, with how long it takes to compile, I decided the extra few megabytes on the download was less of an issue so I stopped doing that a while ago.

Same here.  Fixing the RGB Matrix build will definitely help on the Pi. We have to compile it 3 times and I just realized last night that it doesn't use ccache.
Pages: [1] 2 3 ... 10
Back to top