Falcon Christmas

Falcon Christmas => Falcon PiCap => Topic started by: travcam on April 08, 2017, 12:48:02 PM

Title: PiCap built but can't test strings
Post by: travcam on April 08, 2017, 12:48:02 PM
Earlier in the year I purchased a PiCap to experiment with.  I just received my pixel preorder from Jan and now I'm trying to get everything playing together.


I've got the Pi and the PiCap together, installed FPP and checked (triple) the jumpers.


I started with a 50 pixel string on port 1 as RPIWS281X as the noob walkthru and video describe which puts me at 150 channels.  I'm running 12v ws2811 pixels.

When I try to run a test output for those 150 channels, I get nothing.

I checked output voltage on the PiCap to the pixels and it's 13.4 which seems appropriate for 12v pixels.  I have a 60 amp power supply.   

Anyone know whatelse I can try or test to figure out my problem?  I've already re terminated the pos/Data/neg wires and tried different pixel strings to no avail. I've never ran these lights, so I can't say they work, but when I plug them in, they do flicker blue briefly.
Title: Re: PiCap built but can't test strings
Post by: jnealand on April 08, 2017, 02:54:31 PM
13.4 is pretty high.  Lots of folks have had to turn their power down to 11.5 - 11.8 to get good results.
Title: Re: PiCap built but can't test strings
Post by: patdelaney on April 08, 2017, 02:57:18 PM
I know this may go without saying ... but are you sure you are following the arrows on the strings.


You can only feed the string from one end for data, maybe you have the string reversed?


Pat
Title: Re: PiCap built but can't test strings
Post by: AAH on April 08, 2017, 04:23:08 PM
Pop up some screenshots of the network configuration and the output config pages. Something may have been missed.
Title: Re: PiCap built but can't test strings
Post by: travcam on April 08, 2017, 08:55:46 PM
I know this may go without saying ... but are you sure you are following the arrows on the strings.


You can only feed the string from one end for data, maybe you have the string reversed?


Pat


These are WS2811-12v Pixelstring 18AWG from DIY LED Express.  I don't see any arrows on them...the pigtails I received only fit one connector per string and won't mate the other way.


Just for kicks, I took the data and tried feeding it thru the opposite end using a pin and jumper.. no luck
Title: Re: PiCap built but can't test strings
Post by: travcam on April 08, 2017, 08:59:50 PM
Pop up some screenshots of the network configuration and the output config pages. Something may have been missed.


Here are the network and output pages.


Note: I have the active box checked and saved...  i snapped the pic after trying other things.  Sorry
Title: Re: PiCap built but can't test strings
Post by: JonB256 on April 08, 2017, 10:12:21 PM
Check the "Active" box on the second screen shot. You have it configured but not actually loaded correctly.
Title: Re: PiCap built but can't test strings
Post by: travcam on April 09, 2017, 09:08:46 AM
Check the "Active" box on the second screen shot. You have it configured but not actually loaded correctly.


I've done that and saved it and restarted FPP.  Same result.
Title: Re: PiCap built but can't test strings
Post by: David Pitts on April 09, 2017, 04:15:16 PM
Do you have the green power light lit on PiCap?
Title: Re: PiCap built but can't test strings
Post by: travcam on April 09, 2017, 08:24:42 PM
Do you have the green power light lit on PiCap?

Yes

(https://uploads.tapatalk-cdn.com/20170410/4cbf0030db8f88a518add810b185ee1e.jpg)


Sent from my iPhone using Tapatalk Pro
Title: Re: PiCap built but can't test strings
Post by: JonB256 on April 10, 2017, 06:55:55 AM
As pictured, Red is almost always the POS V, but you may have white and blue swapped.

Sent from my SM-G900V using Tapatalk

Title: Re: PiCap built but can't test strings
Post by: Jonnyb44 on April 10, 2017, 03:35:10 PM
How are you testing? From xlights or fpp test page?


Sent from my iPhone using Tapatalk
Title: Re: PiCap built but can't test strings
Post by: travcam on April 14, 2017, 08:36:04 AM
As pictured, Red is almost always the POS V, but you may have white and blue swapped.

Sent from my SM-G900V using Tapatalk


Traced the wire colors to the circuit board in the bulb and the white wire is data, blue is ground.  So it should be wired properly.
Title: Re: PiCap built but can't test strings
Post by: travcam on April 14, 2017, 08:41:40 AM
How are you testing? From xlights or fpp test page?


Sent from my iPhone using Tapatalk


Testing from the FPP test page.  I used the noob setup guide from the forum.
http://falconchristmas.com/forum/index.php/topic,6139.0.html (http://falconchristmas.com/forum/index.php/topic,6139.0.html)


I figured it was best to get that working independently before I started messing with xlights... so far my experience in the hobby is limited to renards and vixen. 
Title: Re: PiCap built but can't test strings
Post by: Jonnyb44 on April 14, 2017, 08:43:23 AM
Those should light from display testing. As long as they are 12v ws2811


Sent from my iPhone using Tapatalk
Title: Re: PiCap built but can't test strings
Post by: Jonnyb44 on April 14, 2017, 09:20:22 AM
Btw do you have any channels set on the e131 page?


Sent from my iPhone using Tapatalk
Title: Re: PiCap built but can't test strings
Post by: travcam on April 14, 2017, 12:32:51 PM
Those should light from display testing. As long as they are 12v ws2811


Sent from my iPhone using Tapatalk


That's about where I am...  if I had another controller to test with I would certainly help determining if it's the PiCap board or the lights.   I guess it's possible I have a bad run of 4x fifty pixels, but I'd like to think not.
I don't suppose there's a way to verify the pixels independent of a controller due to the data?

Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on April 14, 2017, 12:46:04 PM
Check the "Active" box on the second screen shot. You have it configured but not actually loaded correctly.


I've done that and saved it and restarted FPP.  Same result.

Just to confirm, was this a reboot or just a restart of fppd?   Enabling the RPI_WS281x output needs to disable the onboard sound and a reboot is required.
Title: Re: PiCap built but can't test strings
Post by: travcam on April 14, 2017, 01:20:53 PM
I've done both.  Enable, restart and reboot




Sent from my iPhone using Tapatalk Pro
Title: PiCap built but can't test strings
Post by: travcam on April 14, 2017, 01:21:53 PM
Btw do you have any channels set on the e131 page?


Sent from my iPhone using Tapatalk
That page is still all defaults so nothing defined


Sent from my iPhone using Tapatalk Pro
Title: PiCap built but can't test strings
Post by: Jonnyb44 on April 14, 2017, 01:25:28 PM
That's the only thing I can think of.  Maybe it needs channels defined for output test. 
Captain??

Sent from my iPhone using Tapatalk
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on April 14, 2017, 02:53:39 PM
You don't need to define any E1.31 for the channel test page to work. The only thing you need to do is create a channel output and then toggle testing on and that should turn lights on.

Can you go to the FPP Settings page and set your Log Level to Debug and make sure that at least the 'Channel Outputs' checkbox is checked for the Log Mask section, then restart fppd.  Then go to the FPP File Manager and look at the tail end of the fppd.log file to see if there are any messages about the channel output.  I'm running the latest stock v1.9 code on a Pi right now on an infinity mirror so I know the code should be working.
Title: Re: PiCap built but can't test strings
Post by: travcam on April 14, 2017, 08:50:50 PM
You don't need to define any E1.31 for the channel test page to work. The only thing you need to do is create a channel output and then toggle testing on and that should turn lights on.

Can you go to the FPP Settings page and set your Log Level to Debug and make sure that at least the 'Channel Outputs' checkbox is checked for the Log Mask section, then restart fppd.  Then go to the FPP File Manager and look at the tail end of the fppd.log file to see if there are any messages about the channel output.  I'm running the latest stock v1.9 code on a Pi right now on an infinity mirror so I know the code should be working.


Here's an excerpt from the log. 


2017-04-14 21:47:36 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 6us, Sleep: 49986us, FrameNum: 2202 2017-04-14 21:47:37 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 6us, Sleep: 49987us, FrameNum: 2222 2017-04-14 21:47:38 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 6us, Sleep: 49986us, FrameNum: 2242 2017-04-14 21:47:39 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 6us, Sleep: 49986us, FrameNum: 2262 2017-04-14 21:47:40 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 6us, Sleep: 49985us, FrameNum: 2282 2017-04-14 21:47:41 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 3us, Read: 6us, Sleep: 49987us, FrameNum: 2302 2017-04-14 21:47:42 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 7us, Sleep: 49985us, FrameNum: 2322 2017-04-14 21:47:43 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 3us, Read: 7us, Sleep: 49986us, FrameNum: 2342 2017-04-14 21:47:44 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 8us, Sleep: 49982us, FrameNum: 2362 2017-04-14 21:47:45 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 8us, Sleep: 49982us, FrameNum: 2382 2017-04-14 21:47:46 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 8us, Read: 11us, Sleep: 49976us, FrameNum: 2402 2017-04-14 21:47:47 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 8us, Sleep: 49982us, FrameNum: 2422 2017-04-14 21:47:48 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 8us, Sleep: 49982us, FrameNum: 2442 2017-04-14 21:47:49 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 7us, Read: 8us, Sleep: 49981us, FrameNum: 2462 2017-04-14 21:47:50 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 7us, Sleep: 49983us, FrameNum: 2482 2017-04-14 21:47:51 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 8us, Read: 10us, Sleep: 49977us, FrameNum: 2502 2017-04-14 21:47:52 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 8us, Sleep: 49982us, FrameNum: 2522 2017-04-14 21:47:53 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 9us, Sleep: 49981us, FrameNum: 2542 2017-04-14 21:47:54 (3348) channeltester/ChannelTester.cpp:78:ChannelTester::SetupTest() 2017-04-14 21:47:54 (3348) channeltester/RGBChase.cpp:142:TestPatternRGBChase::DumpConfig 2017-04-14 21:47:54 (3348) channeltester/RGBChase.cpp:143:    colorPattern    : FF000000FF000000FF 2017-04-14 21:47:54 (3348) channeltester/RGBChase.cpp:144:    colorPatternSize: 3 2017-04-14 21:47:54 (3348) channeltester/TestPatternBase.cpp:208:TestPatternBase::DumpConfig() 2017-04-14 21:47:54 (3348) channeltester/TestPatternBase.cpp:209:    cycleMS     : 1000 2017-04-14 21:47:54 (3348) channeltester/TestPatternBase.cpp:210:    channelSet  : 1-150 2017-04-14 21:47:54 (3348) channeltester/TestPatternBase.cpp:211:    channelCount: 150 2017-04-14 21:47:54 (3348) channeltester/TestPatternBase.cpp:216:                : 1-150 2017-04-14 21:47:54 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 7us, Read: 16us, Sleep: 49973us, FrameNum: 2562 2017-04-14 21:47:55 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 7us, Read: 18us, Sleep: 49971us, FrameNum: 2582 2017-04-14 21:47:56 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 7us, Read: 15us, Sleep: 49974us, FrameNum: 2602 2017-04-14 21:47:57 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 7us, Read: 15us, Sleep: 49975us, FrameNum: 2622 2017-04-14 21:47:58 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 7us, Read: 21us, Sleep: 49968us, FrameNum: 2642 2017-04-14 21:47:59 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 17us, Sleep: 49973us, FrameNum: 2662 2017-04-14 21:47:59 (3348) channeltester/ChannelTester.cpp:78:ChannelTester::SetupTest() 2017-04-14 21:48:00 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 8us, Sleep: 49982us, FrameNum: 2682 2017-04-14 21:48:01 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 10us, Sleep: 49980us, FrameNum: 2702 2017-04-14 21:48:02 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 6us, Read: 11us, Sleep: 49978us, FrameNum: 2722 2017-04-14 21:48:03 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 8us, Sleep: 49983us, FrameNum: 2742 2017-04-14 21:48:04 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 11us, Sleep: 49981us, FrameNum: 2762 2017-04-14 21:48:05 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 11us, Sleep: 49981us, FrameNum: 2782 2017-04-14 21:48:06 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 8us, Sleep: 49984us, FrameNum: 2802 2017-04-14 21:48:07 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 4us, Read: 7us, Sleep: 49985us, FrameNum: 2822 2017-04-14 21:48:08 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 5us, Read: 7us, Sleep: 49984us, FrameNum: 2842 2017-04-14 21:48:09 (3353) channeloutput/channeloutputthread.c:174:Output Thread: Loop: 50000us, Send: 3us,
Title: Re: PiCap built but can't test strings
Post by: Keenbfb on April 16, 2017, 02:42:13 AM
You could always test the pixels using an Arduino just to rule broken pixels.
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on April 17, 2017, 11:40:55 AM
Here's an excerpt from the log. 

Nothing looks out of the ordinary in there.  Can you restart fppd again and look to see if there are any startup errors related to the channel output.  I don't think there would be, but it is worth a look.
Title: Re: PiCap built but can't test strings
Post by: JonB256 on April 17, 2017, 01:06:28 PM
travcam, it doesn't say where you live. Perhaps someone is close enough to help you one on one. (there is a place in your profile. Highly recommend everyone use it unless you are hiding from someone :) )
Title: Re: PiCap built but can't test strings
Post by: paudyd on April 17, 2017, 05:29:17 PM
These are WS2811-12v Pixelstring 18AWG from DIY LED Express.  I don't see any arrows on them...the pigtails I received only fit one connector per string and won't mate the other way.


Just for kicks, I took the data and tried feeding it thru the opposite end using a pin and jumper.. no luck


This info is odd and does not really clear up if the string is wired correctly.  Most pixel strings have pigtails on either end.  Just within the last year or two, suppliers have been shipping strings with waterproof connectors attached.  DIY LED Express is one of those suppliers.  So I have to wonder if you have pigtails on only one end and a connector on the other?  In any case, the wires leading to the first pixel should enter on the side opposite the chip.  You may be able to see a DI (Data In) for the middle white wire through the epoxy.  If your wires leading to the first pixel are on the chip side, you need to connect the string on the other end.


Paudyd
Title: Re: PiCap built but can't test strings
Post by: travcam on April 18, 2017, 07:41:02 AM
travcam, it doesn't say where you live. Perhaps someone is close enough to help you one on one. (there is a place in your profile. Highly recommend everyone use it unless you are hiding from someone :) )


Good advice, I'll do that. Besides, some of my best friends started out stalking me online....   ;)
Title: PiCap built but can't test strings
Post by: travcam on April 18, 2017, 03:08:43 PM
Here's an excerpt from the log. 

Nothing looks out of the ordinary in there.  Can you restart fppd again and look to see if there are any startup errors related to the channel output.  I don't think there would be, but it is worth a look.

The 'are the pixels good?' Part of this equation is now answered.  (https://uploads.tapatalk-cdn.com/20170418/d2f6b8db70a9b96c78addabca5d9ae10.jpg)

I'll get a log of the startup and post it tonight once I get the family fed.  I tested them using a cheap $9 amazon pixel controller. 




Sent from my iPhone using Tapatalk Pro
Title: Re: PiCap built but can't test strings
Post by: Moto on August 11, 2017, 03:55:45 PM
Hey all, I came across this thread because I am having the same issue with the exact same setup. I double, triple, and quadruple checked everything (connections, connectors, jumpers, config, etc..). I also worked through all the advice in this thread and still a no-go :( Anyway, Looks like the last reply was back in April and was wondering if you got this sorted out.. and, if so, what was it?

-Thanks in advance!
Title: Re: PiCap built but can't test strings
Post by: rjm12rjm12 on September 23, 2017, 09:35:52 PM
Hi All,


I just received my PiCap and am having the same problem, my lights are good.  Any resolution?


Thanks,


Rob
Title: Re: PiCap built but can't test strings
Post by: AAH on September 23, 2017, 11:47:23 PM
Using a $US3 2811 pixel tester is a much easier option than an Arduino
http://www.hansonelectronics.com.au/product/pixel-tester-2811/ is what I'm talking about. Ray Wu, Scott Led, Paul Zhang etc as well as Feebay all sell them.

You could always test the pixels using an Arduino just to rule broken pixels.
Title: Re: PiCap built but can't test strings
Post by: travcam on September 24, 2017, 05:36:19 AM
Hey all, I came across this thread because I am having the same issue with the exact same setup. I double, triple, and quadruple checked everything (connections, connectors, jumpers, config, etc..). I also worked through all the advice in this thread and still a no-go :( Anyway, Looks like the last reply was back in April and was wondering if you got this sorted out.. and, if so, what was it?

-Thanks in advance!

I never did get my PiCap working.  I got to the last post where I verified the pixels were not the problem and life got in the way. 
I guess there could be a component on the PiCap that is bad but I just never got to that point. 
Now too close to Christmas to do anything with it if I did repair so I'll regroup in Jan. 

Anyone know of an easy way to test the output ICs on the board ?  There a guide somewhere ?


Sent from my iPhone using Tapatalk Pro
Title: Re: PiCap built but can't test strings
Post by: rjm12rjm12 on September 24, 2017, 10:18:46 AM
Hi,


Just a quick update on my status.  I tried a Pi3 and with some figuring out of setup I got mine to work.  I will try the Pi Model B+ v1.2 later and see if I can get things to work with that one also.  I did do a reinstall of the software also.


Rob
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 12, 2017, 10:51:38 PM
I'm having the same issue with a new PiCap. Display testing doesn't produce any results.
However, the fppd log does show an error when the daemon is restarted.
Here's the relevant lines from the log:

2017-11-12 23:01:30 (3341) channeloutput/rpi_ws281x.cpp:220:ws2811_init() failed
2017-11-12 23:01:30 (3341) channeloutput/channeloutput.c:435:ERROR Opening RPIWS281X Channel Output

Pixels check good on an F4V3. Operation (or lack thereof) is the same on a Pi 2 and a Pi3. Tried FPP v1.8 and v1.9. No response with either.
The Cap is powered from a 12VDC suppy, pixels are 12V 2811s. String orientation confirmed via operation on the F4.
Both outputs read 12V when the Channel Output Testing Enable Test Mode box is checked.

Channel outputs screenshot attached.
String 2 behaves the same, i.e. no joy when it's configured for 50 pixels and String 1, zero pixels.

I've been an Electronics technician for 43 years, so I've tried to eliminate as many silly/stupid mistakes as possible, as well as pass along as much info regarding the configuration, and troubleshooting done so far.

Captain?

Can you go to the FPP Settings page and set your Log Level to Debug and make sure that at least the 'Channel Outputs' checkbox is checked for the Log Mask section, then restart fppd.  Then go to the FPP File Manager and look at the tail end of the fppd.log file to see if there are any messages about the channel output.  I'm running the latest stock v1.9 code on a Pi right now on an infinity mirror so I know the code should be working.
Title: Re: PiCap built but can't test strings
Post by: Bwinter on November 12, 2017, 11:13:26 PM

I'm running v1.0-65-gb2ce9e6 here (using a different PiHat) and I'm not having any problems.  Could this mean that it's not necessarily a FPP issue?
Title: Re: PiCap built but can't test strings
Post by: David Pitts on November 13, 2017, 01:56:50 AM
2017-11-12 23:01:30 (3341) channeloutput/rpi_ws281x.cpp:220:ws2811_init() failed
2017-11-12 23:01:30 (3341) channeloutput/channeloutput.c:435:ERROR Opening RPIWS281X Channel Output


Seems FPP is having a problem for some reason. The PiCap itself would not cause this.
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 13, 2017, 06:47:55 AM
Reinstalled FPP v1.8. No change. Upgraded to v1.9 a second time, no help there either. Am going to try a different Pi2.
Title: Re: PiCap built but can't test strings
Post by: JonB256 on November 13, 2017, 06:58:14 AM
Reinstalled FPP v1.8. No change. Upgraded to v1.9 a second time, no help there either. Am going to try a different Pi2.

Bill, how are you testing?  The test sequence page?  Is the Pi set as Standalone, Master, Remote or Bridge?

Can you take a picture of the PiCap with everything connected?
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 13, 2017, 07:37:21 AM
I'm testing from the Display Testing page. Haven't tried the test sequence page yet. The Pi is running in standalone mode.

Will post a pic later today.
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 13, 2017, 02:10:00 PM
Jon,

Here's a couple of shots per your request.

The pixels check good on an F4V3.

I used the info in this post: http://falconchristmas.com/forum/index.php/topic,6139.0.html (http://falconchristmas.com/forum/index.php/topic,6139.0.html) to do the setup and test.
The only difference being the lack of a battery.
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 13, 2017, 05:52:48 PM
Did some more troubleshooting....

Downloaded FPP 1.8 again. Installed it on a PNY Class 10 16GB microSD card. No change. Installed FPP to a Transcend 8GB Class 10 card. No change.
Tried a SanDisk 16GB Class 10 card. No help there either. Tried a different SanDisk 4GB USB thumb drive, no change. All of the flash media were formatted with the SD Assn's SD Card Formatter per the FPP installation instructions.

Tried a different Pi2. No change. That makes two Pi2s and a Pi3 that all produce the same error in the fppd log.
Title: Re: PiCap built but can't test strings
Post by: JonB256 on November 13, 2017, 06:11:21 PM
Two things I see - first is that you aren't using any spacers/standoffs between the PiCap and the Pi. Has anything "touched" on the bottom of the board?

Second - you have an HDMI cable plugged in. Don't know why you have it, but have you tried without out it?
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 13, 2017, 06:25:27 PM
The Phoenix terminal block in P2 is sitting on the HDMI connector's plastic housing, so there is ample clearance between the Cap and the Pi.

I'll pull the HDMI plug and give it another go.
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 13, 2017, 06:27:20 PM
Same results with the HDMI cable disconnected.  :(
Title: Re: PiCap built but can't test strings
Post by: JonB256 on November 13, 2017, 07:45:17 PM
Same results with the HDMI cable disconnected.  :(
Bill, I've compared your board with one I have and all chips and jumpers match.

All I can think of at this point is something is wrong with your board at a chip level.
I didn't see that you tried a spare/extra PiCap.
Title: Re: PiCap built but can't test strings
Post by: David Pitts on November 13, 2017, 08:06:45 PM
The FPP software has no way of knowing if a functional PiCap is connected. So the PiCap is not causing the driver to fail to load. To proof this take the PiCap off and try to run FPP. FPP does not need PiCap attached to run WS2811 pixels out the two pins.

Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 13, 2017, 09:10:31 PM
Jon,

Thanks for the "over-the-shoulder" assist tonight via Teambuilder.
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 13, 2017, 09:18:13 PM
The FPP software has no way of knowing if a functional PiCap is connected. So the PiCap is not causing the driver to fail to load. To proof this take the PiCap off and try to run FPP. FPP does not need PiCap attached to run WS2811 pixels out the two pins.

Confirmed. Still get the error sans the PiCap.
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 13, 2017, 10:36:08 PM
As luck would have it, I've indeed got three Pis that are incompatible with a PiCap.

Knowing the first 26 pins of the 40 pin header have the same pinout as the Pi A/B Rev 2 and later,
I decided to remove the composite video jack on a Pi1, so I could put the Cap on it.

Removed said RCA connector, attached Cap. Pulled the SD card out of the Pi2, popped it into the Pi1.
Fired it up. Both the test and the test sequence work.

If nothing else, I've got a pixel tester!  ;D
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on November 14, 2017, 11:58:08 PM
What version Pi are these, including the hardware revision printed on the board.

One thing you could try is changing the second output's pixel count to 1 to see if that works.
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 15, 2017, 08:06:19 AM
Both Pi 2s are v1.1
The Pi 3 is v1.2

Tried setting the second output to 1. No change.
The fppd log shows the errors even if the PiCap is not installed.
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 15, 2017, 05:02:04 PM
Chris,

Here's an excerpt from the fppd log. Starting or restarting fppd causes the errors.
The PiCap is not installed. The Pi is a 3B v1.2
(I get the same results with the PiCap installed, as I do with it not installed)
Tried it with a fresh install of FPP 1.8, then an upgrade to v1.9
Channel outputs (Other) are configured for a string of 50 pixels on output 1, and 1 pixel on output 2. No E1.31 ports.
I get the same error msgs on both of my Pi 2 v1.1 boards. (with or w/o a PiCap installed)

The only Pi I have that it does work on is a Pi 1 512MB model. (the silkscreening on the board reads Raspberry Pi (c)2011.12)

2017-11-15 23:52:28 (3123) log.c:218:=========================================
2017-11-15 23:52:28 (3123) log.c:219:FPP 1.8-49-ga260de7
2017-11-15 23:52:28 (3123) log.c:220:Branch: v1.8
2017-11-15 23:52:28 (3123) log.c:221:=========================================
2017-11-15 23:52:28 (3125) channeloutput/rpi_ws281x.cpp:220:ws2811_init() failed
2017-11-15 23:52:28 (3125) channeloutput/channeloutput.c:376:ERROR Opening RPIWS281X Channel Output
2017-11-15 23:52:28 (3125) command.c:72:Initializing Command Module
2017-11-15 23:52:28 (3125) Scheduler.cpp:439:Loading Schedule from /home/fpp/media/schedule
2017-11-15 23:52:28 (3125) Scheduler.cpp:516:Current Schedule: (Status: '+' = Enabled, '-' = Disabled, '!' = Outside Date Range, '*' = Repeat)
2017-11-15 23:52:28 (3125) Scheduler.cpp:517:St  Start & End Dates       Days         Start & End Times   Playlist
2017-11-15 23:52:28 (3125) Scheduler.cpp:518:--- ----------------------- ------------ ------------------- ---------------------------------------------
2017-11-15 23:52:28 (3125) fppd.c:210:Starting main processing loop
2017-11-15 23:52:28 (3125) Scheduler.cpp:439:Loading Schedule from /home/fpp/media/schedule
2017-11-15 23:52:28 (3125) Scheduler.cpp:516:Current Schedule: (Status: '+' = Enabled, '-' = Disabled, '!' = Outside Date Range, '*' = Repeat)
2017-11-15 23:52:28 (3125) Scheduler.cpp:517:St  Start & End Dates       Days         Start & End Times   Playlist
2017-11-15 23:52:28 (3125) Scheduler.cpp:518:--- ----------------------- ------------ ------------------- ---------------------------------------------
2017-11-15 23:55:15 (3184) log.c:218:=========================================
2017-11-15 23:55:15 (3184) log.c:219:FPP 1.9-62-gcf857e4
2017-11-15 23:55:15 (3184) log.c:220:Branch: v1.9
2017-11-15 23:55:15 (3184) log.c:221:=========================================
2017-11-15 23:55:15 (3187) channeloutput/rpi_ws281x.cpp:220:ws2811_init() failed
2017-11-15 23:55:15 (3187) channeloutput/channeloutput.c:435:ERROR Opening RPIWS281X Channel Output
2017-11-15 23:55:15 (3187) command.c:72:Initializing Command Module
2017-11-15 23:55:15 (3187) Scheduler.cpp:439:Loading Schedule from /home/fpp/media/schedule
2017-11-15 23:55:15 (3187) Scheduler.cpp:516:Current Schedule: (Status: '+' = Enabled, '-' = Disabled, '!' = Outside Date Range, '*' = Repeat)
2017-11-15 23:55:15 (3187) Scheduler.cpp:517:St  Start & End Dates       Days         Start & End Times   Playlist
2017-11-15 23:55:15 (3187) Scheduler.cpp:518:--- ----------------------- ------------ ------------------- ---------------------------------------------
2017-11-15 23:55:15 (3187) fppd.c:210:Starting main processing loop
2017-11-15 23:55:15 (3187) Scheduler.cpp:439:Loading Schedule from /home/fpp/media/schedule
2017-11-15 23:55:15 (3187) Scheduler.cpp:516:Current Schedule: (Status: '+' = Enabled, '-' = Disabled, '!' = Outside Date Range, '*' = Repeat)
2017-11-15 23:55:15 (3187) Scheduler.cpp:517:St  Start & End Dates       Days         Start & End Times   Playlist
2017-11-15 23:55:15 (3187) Scheduler.cpp:518:--- ----------------------- ------------ ------------------- ---------------------------------------------
Title: Re: PiCap built but can't test strings
Post by: DustinAZ on November 16, 2017, 09:37:51 PM
Fuses on the picap still good?


Sent from my iPhone using Tapatalk
Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 17, 2017, 03:54:24 AM
Hi Dustin,

Ya must've missed it...  ;)   (Reply #50 in the thread, same PiCap)

Title: Re: PiCap built but can't test strings
Post by: Bill Thomson on November 17, 2017, 03:15:36 PM
Received a new Pi 3 and new PiCap today.

Connected everything together, popped in the uSD card from the Pi 3 that produced no output. Works as advertised.

Despite the odds of having three RPis that won't work with a Cap, that's what it appears to be.

That's my luck.
Earlier this year I had three Sun Blade 1500 Workstations on an Airport Surveilance Radar I maintain, go bad at the same time.
Pretty tall odds on that one too, but that's what it turned out to be.
Title: Re: PiCap built but can't test strings
Post by: JonB256 on November 17, 2017, 03:28:12 PM
Received a new Pi 3 and new PiCap today.

Connected everything together, popped in the uSD card from the Pi 3 that produced no output. Works as advertised.

Despite the odds of having three RPis that won't work with a Cap, that's what it appears to be.

That's my luck.
Earlier this year I had three Sun Blade 1500 Workstations on an Airport Surveliiance Radar I maintain, go bad.
Pretty tall odds on that one too, but that's what it turned out to be.

Go figure
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on November 17, 2017, 03:35:45 PM
I am going to add more info to that error message so we can at least get the error code from the rpi_ws281x library to give us an idea of what is happening.  The debug info won't get into v1.9 for a while, but I will add to master-v1.x for now.
Title: Re: PiCap built but can't test strings
Post by: travcam on December 20, 2017, 07:34:09 PM
I never did get my PiCap working.  I got to the last post where I verified the pixels were not the problem and life got in the way. 
I guess there could be a component on the PiCap that is bad but I just never got to that point. 
Now too close to Christmas to do anything with it if I did repair so I'll regroup in Jan. 

Anyone know of an easy way to test the output ICs on the board ?  There a guide somewhere ?


Sent from my iPhone using Tapatalk Pro


So now that I have my show up and running for the year, I have time to tinker with this particular project again.
I've tried about everything I can think of, so I guess I will try a different PI next.


Is there a guide somewhere on troubleshooting the actual PiCap board at a component level?  Running out of options.
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on December 20, 2017, 10:24:01 PM
Is there a guide somewhere on troubleshooting the actual PiCap board at a component level?  Running out of options.

I don't know of any.  Can we try to make sure your FPP config is good?  Can you go to the Logs tab of the FPP File Manager and downloads the Logs ZIP file and attach it here.  That will give me some logs and config files to look at and maybe something there will point to an issue.
Title: Re: PiCap built but can't test strings
Post by: travcam on December 21, 2017, 09:46:48 AM
Is there a guide somewhere on troubleshooting the actual PiCap board at a component level?  Running out of options.

I don't know of any.  Can we try to make sure your FPP config is good?  Can you go to the Logs tab of the FPP File Manager and downloads the Logs ZIP file and attach it here.  That will give me some logs and config files to look at and maybe something there will point to an issue.


Attached log zip file.  I reinstalled FPP and upgraded to the latest version. 


Thanks for the help!
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on December 21, 2017, 03:34:57 PM
Did you hand-edit your channeloutputs file?

There are missing fields and spaces around the equal sign which shouldn't be there.

If you didn't edit this file, check the pixel count field on the Channel Outputs page and make sure there are no spaces in it and then resave and restart fppd.  Even if there is a space there, that wouldn't explain where the space before the equal sign in the config file came from.  The Javascript hardcodes that without an equal sign in it.
Title: Re: PiCap built but can't test strings
Post by: travcam on December 21, 2017, 04:14:19 PM
Did you hand-edit your channeloutputs file?

There are missing fields and spaces around the equal sign which shouldn't be there.

If you didn't edit this file, check the pixel count field on the Channel Outputs page and make sure there are no spaces in it and then resave and restart fppd.  Even if there is a space there, that wouldn't explain where the space before the equal sign in the config file came from.  The Javascript hardcodes that without an equal sign in it.


No, no manual editing.  I looked for spaces and didn't see any in the output page.  I went ahead and deleted the pixels as defined, resaved - restarted.  Then I re-added and saved and restarted again.  still no change.


I can repost a new zip if that will help.
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on December 21, 2017, 04:46:15 PM
Can you attach a new zip as well as a screenshot of your current channel outputs config showing the RPI-WS281x output.
Title: Re: PiCap built but can't test strings
Post by: travcam on December 21, 2017, 05:49:44 PM
Updated files
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on December 21, 2017, 09:06:37 PM
OK, I figured out the issue with the config file in the zip, it is getting munged by some code we had to make sure the files were formatted correctly.  I made a note to fix that.

Your screenshot looks good, but the fppd.log doesn't show the error from the rpi library init function.  Can you follow the instructions in the v1.10 release announcement thread to update to v1.10 so we can see what error the library is returning?

http://falconchristmas.com/forum/index.php/topic,8474.0.html (http://falconchristmas.com/forum/index.php/topic,8474.0.html)

Also, I'm assuming this is an original PI B, not a Pi 2 B or PI 3 B, is that correct?  That may be part of the issue.  Hopefully the fppd.log from v1.10 will help.

After switching to v1.10, go to the FPP File Manager Logs tab and view the fppd.log file.  Look for a few lines at the bottom that looks like this and paste the lines here.  I'm mainly interested in the second from the last line, it should have an error code listed instead of just saying "failed".

Code: [Select]
2017-12-21 18:10:38 (3690) log.c:218:=========================================
2017-12-21 18:10:38 (3690) log.c:219:FPP 1.9-62-gcf857e4
2017-12-21 18:10:38 (3690) log.c:220:Branch: v1.9
2017-12-21 18:10:38 (3690) log.c:221:=========================================
2017-12-21 18:10:38 (3693) channeloutput/rpi_ws281x.cpp:220:ws2811_init() failed
2017-12-21 18:10:38 (3693) channeloutput/channeloutput.c:435:ERROR Opening RPIWS281X Channel Output
Title: Re: PiCap built but can't test strings
Post by: travcam on December 22, 2017, 02:22:26 PM
Updated to the v1.10 branch.


The Pi is a B+



Logs:
2017-12-22 16:16:50 (6027) log.c:218:========================================= 2017-12-22 16:16:50 (6027) log.c:219:FPP 1.10-20-g331eb1e 2017-12-22 16:16:50 (6027) log.c:220:Branch: v1.10 2017-12-22 16:16:50 (6027) log.c:221:========================================= 2017-12-22 16:16:50 (6029) channeloutput/rpi_ws281x.cpp:221:ws2811_init() failed with error: -1 2017-12-22 16:16:50 (6029) channeloutput/channeloutput.c:453:ERROR Opening RPIWS281X Channel Output 2017-12-22 16:17:03 (6407) log.c:218:========================================= 2017-12-22 16:17:03 (6407) log.c:219:FPP 1.10-20-g331eb1e 2017-12-22 16:17:03 (6407) log.c:220:Branch: v1.10 2017-12-22 16:17:03 (6407) log.c:221:========================================= 2017-12-22 16:17:03 (6410) channeloutput/rpi_ws281x.cpp:221:ws2811_init() failed with error: -1 2017-12-22 16:17:03 (6410) channeloutput/channeloutput.c:453:ERROR Opening RPIWS281X Channel Output
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on December 22, 2017, 05:36:21 PM
I looked up the -1 error code and then realized that our older version of the rpi_ws281x library returns -1 for all errors.  When I added the error code to the log message, I must have been browsing the library source on github and didn't realize ours isn't as verbose.  I checked the issue list for the library and didn't see anything about problems with the B+.

If you want to experiment, you can try modifying the rpi_ws281x library source under /opt/fpp/external/rpi_ws281x to print out some useful error messages, but this might have to wait until we upgrade the version of the library we are using after the holidays.  I think I fried my B+ a while back so it is sitting in my 'dead' pile, otherwise I would test to see if I could reproduce.

We want to get on the new version of the library, it supports more hardware like the Zero W and also has some other enhancements such as being able to support one string of WS281x using PCM and one string using SPI.  Using SPI or PCM allows the onboard audio to be left enabled, so that would be a nice enhancement for users, but would require a newer model PiCap which I would need to talk with David about once we had the software tested.
Title: Re: PiCap built but can't test strings
Post by: travcam on December 23, 2017, 10:00:34 AM
I went ahead and ordered a few Pi 3's for some other projects...  I can try one of those if you think it would help?


I can experiment however you'd like me to to help the cause - I won't need this thing working until next season.
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on December 23, 2017, 11:41:25 AM
If you can try the SD and USB in a different model Pi then that would confirm whether it is an issue with the B+ or your config.  Just take the USB and SD and put them in another Pi and it should boot right up.
Title: Re: PiCap built but can't test strings
Post by: vipersinu2 on December 24, 2017, 11:00:10 AM
Try a new usb drive. All 3 of these scandisk usb sticks that I bought will only play for 2 second and stop, I even did a low level format on all 3 of these drives with no luck. The weird part is that the FSEQ file will play in the testing tab, but not in the playlist? I am just experimenting with the 2 PI3 and 2 picaps with the same results on each one. I am only testing with one PI at a time in standalone mode. All the numbers match up in display testing, I was able to light up just Red, Blue, Green on the 1st and last pixels of my 100 node pixel strip.


When using those 3 scandisk usb sticks, I find it weird that the lights will sequence for 2 seconds and stop, and the time has never moved, staying at 00:00


 I tried a small 2gb usb stick that will sequence the light for the whole song, but there is no time count down of the song or no stop button to stop the song.


I just upgraded the fpp to 1.10 with same results on both PI's
I changed the name of the song and FSEQ to santa to keep it simple.
Just to check, I unchecked Active in the other outputs tab and the song starting timing, but of course no lights.
I just tried bridge mode, xlights working fine thru the pi cap
Title: Re: PiCap built but can't test strings
Post by: JonB256 on December 24, 2017, 02:02:48 PM
Your "short" files names seem to work. Try the same fseq and mp3 files but with very short, no punctuation, names.
Title: Re: PiCap built but can't test strings
Post by: vipersinu2 on December 24, 2017, 02:37:47 PM
I just tried another sequence, I saved it as abc.fseq and abc.mp3 no luck, the string of lights start to flash for 2 seconds and turn off. the count down always remains 00:00
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on December 24, 2017, 03:20:45 PM
Did you install a USB sound card and change the FPP Settings to select the USB device?  When using the PiCap, FPP disables the onboard audio because the PWM output is needed to drive the WS281x pixels, so you have to use a USB sound card if you want to play audio.

If you play the sequence by itself, it will likely work.
Title: Re: PiCap built but can't test strings
Post by: vipersinu2 on December 24, 2017, 03:26:32 PM
Hello Captain,


Thank you for the reply, I am not connecting any sound devices to the PI,
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on December 24, 2017, 03:31:38 PM
Thank you for the reply, I am not connecting any sound devices to the PI,

You can't play sound with the onboard sound card if you are using the PiCap.  You will need to use 'sequence only' playlist entries with no audio file and then they will play.  Once you get a USB sound card, go to the FPP Settings page and select the USB sound device, then you can create a new playlist which has sequence+media entries in it.
Title: Re: PiCap built but can't test strings
Post by: vipersinu2 on December 24, 2017, 03:35:10 PM
Captain,

Good catch, no reason to add the MP3 file when just using the FSEQ.

You are the man Sir.
Thank you
Title: Re: PiCap built but can't test strings
Post by: travcam on December 27, 2017, 06:54:44 AM
If you can try the SD and USB in a different model Pi then that would confirm whether it is an issue with the B+ or your config.  Just take the USB and SD and put them in another Pi and it should boot right up.


Mornin' Cap!


So I swapped over to the Pi3.  I just moved the SD & USB over as suggested.  Everything came up and I noticed the settings were set to player, not bridge.  No matter how much I would try, this wouldn't save when changed.  The settings for the lights stayed, so I tried those and still no go.


I did a fresh install of the FPP on the Pi3 with a new SD card.  Set everything back up as it was before.  I could now change from bridge/player and it would save.  But alas, the lights still don't work.


The last few lines on the log file are attached below.
2017-12-26 23:27:30 (3232) log.c:218:========================================= 2017-12-26 23:27:30 (3232) log.c:219:FPP 1.10-20-g331eb1e 2017-12-26 23:27:30 (3232) log.c:220:Branch: v1.10 2017-12-26 23:27:30 (3232) log.c:221:========================================= 2017-12-26 23:27:30 (3235) command.c:72:Initializing Command Module 2017-12-26 23:27:30 (3235) e131bridge.c:93:Universe Count = 0 2017-12-26 23:27:30 (3235) fppd.c:211:Starting main processing loop
Title: Re: PiCap built but can't test strings
Post by: rgarcia112 on December 29, 2017, 07:42:32 PM
Earlier in the year I purchased a PiCap to experiment with.  I just received my pixel preorder from Jan and now I'm trying to get everything playing together.

Was ur issue resolve? I got my PiCap yesterday and today I finally setup everything and I also don't get any lights on when texting it.


I've got the Pi and the PiCap together, installed FPP and checked (triple) the jumpers.


I started with a 50 pixel string on port 1 as RPIWS281X as the noob walkthru and video describe which puts me at 150 channels.  I'm running 12v ws2811 pixels.

When I try to run a test output for those 150 channels, I get nothing.

I checked output voltage on the PiCap to the pixels and it's 13.4 which seems appropriate for 12v pixels.  I have a 60 amp power supply.   

Anyone know whatelse I can try or test to figure out my problem?  I've already re terminated the pos/Data/neg wires and tried different pixel strings to no avail. I've never ran these lights, so I can't say they work, but when I plug them in, they do flicker blue briefly.
Title: Re: PiCap built but can't test strings
Post by: Bwinter on December 29, 2017, 07:46:32 PM
Maybe put 50 on output 2, just in case you're mistakenly connecting your pixels to output 2 (instead of 1).
Title: Re: PiCap built but can't test strings
Post by: rgarcia112 on December 29, 2017, 07:51:41 PM
I tried that too. I don't know if the PiCap needs the battery. Don't know if it comes with one or not but mine didn't cokme with one. I have tried everything and nothing. I tried turn on the Picap without the pixels and once it's booted I slowly connect the pixels and they will blink red but that's about it.
Title: Re: PiCap built but can't test strings
Post by: Bwinter on December 29, 2017, 08:10:18 PM
I tried that too. I don't know if the PiCap needs the battery. Don't know if it comes with one or not but mine didn't cokme with one. I have tried everything and nothing. I tried turn on the Picap without the pixels and once it's booted I slowly connect the pixels and they will blink red but that's about it.


It doesn't need a battery--that's only for the onboard clock (which you won't need at this point).


Can you drop the voltage down to 12v (or slightly lower)?  Are you sure you ENABLED test-mode (top of the testing page)?  That's tripped me up a few times...
Title: Re: PiCap built but can't test strings
Post by: rgarcia112 on December 29, 2017, 08:16:20 PM
My pixels and power supply are 5v. Yep I clicked on the box to check so it would do the test.
Title: Re: PiCap built but can't test strings
Post by: travcam on December 31, 2017, 12:21:52 PM
If you can try the SD and USB in a different model Pi then that would confirm whether it is an issue with the B+ or your config.  Just take the USB and SD and put them in another Pi and it should boot right up.


Mornin' Cap!


So I swapped over to the Pi3.  I just moved the SD & USB over as suggested.  Everything came up and I noticed the settings were set to player, not bridge.  No matter how much I would try, this wouldn't save when changed.  The settings for the lights stayed, so I tried those and still no go.


I did a fresh install of the FPP on the Pi3 with a new SD card.  Set everything back up as it was before.  I could now change from bridge/player and it would save.  But alas, the lights still don't work.


The last few lines on the log file are attached below.
2017-12-26 23:27:30 (3232) log.c:218:========================================= 2017-12-26 23:27:30 (3232) log.c:219:FPP 1.10-20-g331eb1e 2017-12-26 23:27:30 (3232) log.c:220:Branch: v1.10 2017-12-26 23:27:30 (3232) log.c:221:========================================= 2017-12-26 23:27:30 (3235) command.c:72:Initializing Command Module 2017-12-26 23:27:30 (3235) e131bridge.c:93:Universe Count = 0 2017-12-26 23:27:30 (3235) fppd.c:211:Starting main processing loop


==========
UPDATE
==========


I removed all the chips on the piCap and reinstalled them one by one and now I am very happy to report that my piCap WORKS!!  YEAH!!


Thanks for the help everyone!  I'm sure I'll be back with more questions... lol
Title: Re: PiCap built but can't test strings
Post by: Broeng on February 17, 2018, 11:10:18 AM
I am sorry for recycling this but I just received my PiCap yesterday and I am having the same issues.  The only difference is I am 5V vs 12V and v1.9-75-ga7c664e.  I have tested my pixel string with an arduino.  I have verified every setting (RPIWS281X, 50 pixels, Active; Enable Test Mode) and all the correct blocks checked.  I have even removed all the chips and put them back.  Any help would be greatly appreciated.
Title: Re: PiCap built but can't test strings
Post by: David Pitts on February 17, 2018, 12:19:46 PM
I have seen several people (at least five people) go through a few PIs before they got the PI to work with PiCap. Not sure of the reason their PI's did not work. Can you output to lights directly connecting to GPIO of PI?

If the power light on the PiCap is on you have a good 5V, There is only one buffer chip between GPIO and output and I have seen very few fail.
Title: Re: PiCap built but can't test strings
Post by: Broeng on February 17, 2018, 12:32:30 PM
I was just about to test from the GPIOs directly like you recommended.  Before I shutdown I saw the LED panel output was enabled using the same channels.  Now everything works ;D .  I was so focused on what needed to be set, I didn't think about checking those areas that should not be.  Thank you for the quick response David.  This is my first project using pixels and I am looking forward to growing into the F16V3.
Title: Re: PiCap built but can't test strings
Post by: jnealand on February 17, 2018, 02:48:54 PM
In the future it is much better to start a new thread than resurrect an old thread or even piggyback on someone elses problem thread as it can confuse answers to help the original poster.
Title: Re: PiCap built but can't test strings
Post by: David Pitts on February 17, 2018, 02:56:08 PM
I was just about to test from the GPIOs directly like you recommended.  Before I shutdown I saw the LED panel output was enabled using the same channels.  Now everything works ;D .  I was so focused on what needed to be set, I didn't think about checking those areas that should not be.  Thank you for the quick response David.  This is my first project using pixels and I am looking forward to growing into the F16V3.

Hmm. Not sure why that would not make it work as different output types can share same output data.
Title: Re: PiCap built but can't test strings
Post by: CaptainMurdoch on February 17, 2018, 05:00:42 PM
I was just about to test from the GPIOs directly like you recommended.  Before I shutdown I saw the LED panel output was enabled using the same channels.  Now everything works ;D .  I was so focused on what needed to be set, I didn't think about checking those areas that should not be.  Thank you for the quick response David.  This is my first project using pixels and I am looking forward to growing into the F16V3.

Hmm. Not sure why that would not make it work as different output types can share same output data.

The RPIWS281x output and LED Panel output on the Pi both use the PWM outputs and overlapping pins.  I have it on my ToDo list to get some more sanity checking of the user's Channel Output configs in the UI, I have already started working on it, but it will be a v2.0 thing if I can get it finished.
Title: Re: PiCap built but can't test strings
Post by: David Pitts on February 17, 2018, 06:07:56 PM
I was just about to test from the GPIOs directly like you recommended.  Before I shutdown I saw the LED panel output was enabled using the same channels.  Now everything works ;D .  I was so focused on what needed to be set, I didn't think about checking those areas that should not be.  Thank you for the quick response David.  This is my first project using pixels and I am looking forward to growing into the F16V3.

Hmm. Not sure why that would not make it work as different output types can share same output data.


The RPIWS281x output and LED Panel output on the Pi both use the PWM outputs and overlapping pins.  I have it on my ToDo list to get some more sanity checking of the user's Channel Output configs in the UI, I have already started working on it, but it will be a v2.0 thing if I can get it finished.

Makes sense now. :)