Closed micheld93 closed 3 years ago
Hi @micheld93,
It looks like there is some information missing from this issue that is required to process it:
Please read this guide, especially the troubleshooting section.
If you have read this guide, please tick the box in your issue next to 'I have read the Get Help Guide'
* [x] I have read the Get Help Guide
If you didn't mean to ask for help, please make sure you used the right template - bugs and requests should have [Bug]
and [Request]
respectively in the title.
I'm just a bot 🤖, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.
Please upload the full log files, the octoprint.log as well.
Sorry, here the complete Octoprint.log:
Well, that log file doesn't show me the startup of the server so I can't tell what is setup on your environment. And you can just attach logs as full files, it makes them much easier to read, please remember this in future.
You need to enable SPI to use this plugin. Run the OS configuration test, ensure that SPI is enabled, open your /boot/config.txt
file and check for dtparam=spi=on
in this file, uncommented.
I didn't remember that I can upload full logs, a new one can be found here: octoprint-2.log
SPI is activated. I checked the LEDs with the implemented tests for different colours (in Utilities section) but the colour is not changing. I also executed a reboot with connected LEDs and SPI on but no change.
According to the log file, two of the OS configuration tests failed, one for the SPI buffer and the other for the core frequency. They should be fixed, otherwise you may not be able to control the LEDs. You can use the built in OS configuration test for this.
I fixed the problems with the built in OS config. I was able to set the colour (red or green) several times with a huge time delay but not every time I tried it. I think I need use another supply for the neo pixel ring. I try it and will report what’s the result.
Am 22.06.2021 um 23:57 schrieb Charlie Powell @.***>:
According to the log file, two of the OS configuration tests failed, one for the SPI buffer and the other for the core frequency. They should be fixed, otherwise you may not be able to control the LEDs. You can use the built in OS configuration test for this.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cp2004/OctoPrint-WS281x_LED_Status/issues/143#issuecomment-866364269, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4EPPSQGCPQ2NBHXSNCBJ3TUEBONANCNFSM47AHJT6Q.
Great, keep me posted - there's not much I can do about the delay, as the only place I can think of is that it is the network/API connection that is slow. Do other things (like pressing buttons in the control tab) have as large of a delay? The power supply may be an issue, as the LEDs might not be picking up the commands right if they are underpowered.
It sounds like this issue was solved - if it was not, please let me know.
Sorry. I tried it with a 5V/2A supply and it works very well. It was just not enough power. Thanks for helping.
What do you need help with? I have a good working Octopi attached to my Prusa Mini but I'm unable to control my used Neopixel 12 LED-Ring. I used the wiring mentioned here as well as the neopixel ring used in the tutorial: https://towinet.de/raspberry-pi-kamera-clip-mit-integriertem-neopixel-ring.
The log says that the SPI couldn't be initialised but I have no display attached. The only other device connected to the Pi is a Pi-camera. I'm also wondering why the log says "ws2811" because I changed it to "ws2812 Strip".
Is there anyone who can help me?
Log files [2021-06-20 17:26:42,614] INFO: Initialising LED strip [2021-06-20 17:26:42,617] ERROR: RuntimeError('ws2811_init failed with code -13 (Unable to initialize SPI)') [2021-06-20 17:26:42,618] ERROR: Strip failed to initialize, no effects will be run. [2021-06-20 17:26:42,619] INFO: No strip initialised, exiting the effect process.
https://cp2004.gitbook.io/ws281x-led-status/guides/get-help-guide