|
Post by arthur on Feb 26, 2019 11:13:36 GMT
So I've found something strange which causes the problem. If you put number of pixels more than 33 it starts to freeze !
|
|
|
Post by arthur on Feb 26, 2019 11:29:56 GMT
After a couple of tests, 33 is not stable (hangs after a while), 32 seems to be stable
|
|
|
Post by Admin on Feb 28, 2019 9:30:11 GMT
|
|
|
Post by arthur on Feb 28, 2019 9:54:27 GMT
I can confirm that using the attached sketch everything works as expected, including the show() function. Thank you for your answer but the problem is still here. Can you please try this sketch and check the serial return, It's your file edited to print millis. NeoPixelStrandTest.ino (14.98 KB) NeoPixelStrandTestSync.ino (15.71 KB) You can see here that millis are stopped 10:50:43.479 -> 10:50:15
10:50:43.479 -> 0
10:50:43.513 -> 3
10:50:47.666 -> 3
10:50:51.890 -> 3
10:50:56.074 -> 3
10:50:57.655 -> 3
10:50:59.232 -> 3
10:51:00.781 -> 3
|
|
|
Post by arthur on Feb 28, 2019 10:19:29 GMT
Another test sketch with 80 pixels on Core 0 and 32 pixels on Core 1. Not working like expectedThe same result, millis are stopped NeoPixelStrandTestSync-Serial.ino (16.72 KB) 11:13:13.808 -> Core 0:11:12:45
11:13:13.808 -> Core 0:1
11:13:15.491 -> Core 1:3
11:13:17.137 -> Core 1:3
11:13:18.129 -> Core 0:3
11:13:18.746 -> Core 1:3
11:13:20.290 -> Core 1:3
11:13:21.838 -> Core 1:3
11:13:22.313 -> Core 0:3
11:13:23.343 -> Core 1:3
11:13:26.495 -> Core 0:3
11:13:28.073 -> Core 0:3
11:13:28.724 -> Core 1:3
11:13:29.652 -> Core 0:3
11:13:31.235 -> Core 0:3
11:13:36.971 -> Core 0:3
Test 2 with 32 pixels on Core 0 and Core 1, working like expected
11:16:17.120 -> Core 0:11:15:51
11:16:17.120 -> Core 0:1
11:16:18.801 -> Core 1:1682
11:16:18.835 -> Core 0:1735
11:16:20.411 -> Core 1:3314
11:16:20.479 -> Core 0:3367
11:16:22.054 -> Core 1:4945
11:16:22.088 -> Core 0:4999
11:16:23.563 -> Core 1:6476
11:16:23.631 -> Core 0:6529
11:16:25.108 -> Core 1:8006
11:16:25.177 -> Core 0:8059
11:16:26.650 -> Core 1:9536
11:16:26.685 -> Core 0:9590
Conclusion : using more than 32 pixels causing this issue
|
|
|
Post by Admin on Mar 1, 2019 9:42:11 GMT
|
|
|
Post by arthur on Mar 1, 2019 9:51:16 GMT
Perfect, seems to be OK, Thank you. Could you also take a look to this issue with FastLed, I think it could be helpful for Shieldbuddy community also aurduino.boards.net/post/1347/thread
|
|
|
Post by arthur on Mar 22, 2019 15:52:42 GMT
Hello, I'm getting another problem with this library. When I'm turning on all leds at the same time with white color everything seems to be OK, but when I'm trying to turn on led by led, I'm getting a green or pink color at the beginning and at the end. The problem is only with White color. Can you please try attached sketch and confirm it? NeoPixelStrandTest.ino (2.27 KB) Thank you
|
|
|
Post by arthur on Mar 28, 2019 23:16:41 GMT
Dear Hitex support team, we are again stuck with this library. Can you please help us to find a solution?
|
|
|
Post by Admin on Apr 1, 2019 7:18:43 GMT
This could be difficult for us to test as the library source code is from Adafruit. We assume that this works OK on an Arduino mega?
|
|
|
Post by arthur on Apr 1, 2019 8:06:34 GMT
This could be difficult for us to test as the library source code is from Adafruit. We assume that this works OK on an Arduino mega? Tested on Mega and Due, everything is working perfectly and we are getting a white led pixel running from the begging to the end. The problem is only on Shieldbuddy. Have you tried my sketch?
|
|
|
Post by perschi on Nov 11, 2019 12:27:53 GMT
Hi guys, I would like to use the TC275 ShieldBuddy board to control Adafruit NeoPixelStrandTest_perschi01.ino (14.47 KB) NeoPixelStrandTest_perschi01.ino (14.47 KB) DotStar and NeoPixel strips. I started with the strandtests for each of these types and faced different problems. Thus, I modified the loop() function for some simpler tests. Some facts about the setup: NeoPixel RGBW 24-Pixel Ring, Adafruit 1m strips. The strips have external power supply. Wiring is confirmed with a similar sketch for Arduino MEGA. The DotStar sketch compiled correctly but doesn’t work. The NeoPixel sketch shows strange behaviors which might give better hints to solve the issue. 1) RGBW order is wrong I defined strip0 as NEO_RGBW but it actually behaves like NEO_RBWG. Thus I defined the strip as NEO_RBWG and it behaves like NEO_RGBW. 2) Pixel index differs for different colors I performed some loops over all colors and observed this: B,R,W start at pixel index 0, G starts at pixel 1. 3) The first pixel which is supposed to be red is always orange (R+G) I compiled the sketch on two different computers and get the same results. As I constantly observe the same results. Thus I do not think it’s due to noise. I’m thankful about each advice to solve this issue. Perschi
|
|
|
Post by claire on Feb 9, 2022 14:26:42 GMT
Hello everyone,
I have recently tried to experiment Neopixel on the ShieldBuddy. And it does not work as well. In fact : - When I use the same code for an Arduino and a ShieldBuddy, I have two differents Leds shows, with the same hardware configuration. - When I use the Neopixel test from the ShielBuddy examples, my led are just turning blue, 500ms per 500ms, until the 70th Led on 240 Leds. I have put the right number of Led and pin. I don't know why it doest not work. Does someone had the same problems ? Can someone help me ?
|
|