Closed tpimh closed 3 years ago
From the description, it sounds like an out of memory/overflow problem. The Nano 33 IoT uses a two controller architecture, so code is executed on different part of the board. Or maybe it is a simple capacity problem in terms of bandwidth. The two controller (ubox & ATSAMD) communicate via SPI.
What is the firmware version of the ubox controller?
Do you use my ArtnetWifiNeoPixel
example without modifications (except number of LEDs)?
Is there only one Artnet universe with all the LED data?
Thank you for your response! The firmware version is 1.2.3, I will try updating it to 1.4.8 and check if it caused the issue.
Yes, I'm using an unmodified example. The only changes I made are ssid
, password
, numLeds
, and dataPin
. There should be only one Artnet universe, but I need to verify this.
Hi, I also tried a bit. WiFiNINA (ubox) firmware: 1.4.8 Adafruit_NeoPixel: 1.9.0 Board: Arduino Nano 33 IoT
I used a PC test program to generate ArtNet frames, at a 50 ms interval (20 FPS). The output was monitored with an oscilloscope. The output was not perfect, but no slow-down or resets. The longest dropout in 20 minutes was about 500 ms. I don't see a problem, so far. What are your results after the firmware upgrade?
Thank you very much! Testing now, and it's working perfectly!
I'm currently using ArtnetWifiNeoPixel example on Arduino Nano 33 IoT with a strip of 46 LEDs.
After a successful connection to Wi-Fi, the animation of the LEDs is smooth and correct for some time, but after ~20 seconds it starts lagging, then all LEDs turn off. If the board is rebooted, it connects to Wi-Fi again, and works well for another ~20 seconds.
I discovered that with lower FPS values, the time before the lag begins is increased. With 9 FPS the time from power on to the state where no LEDs turn on anymore is ~2 minutes. With FPS values of 6 and lower this doesn't happen at all.
What can possibly be causing this? I tried several Wi-Fi routers, and it doesn't seem to be the problem.