search

PiSupply / Bright-Pi

Bright Pi
28 stars 10 forks source link

Setting up bright pi on octoprint #18

Open stavi58 opened 3 years ago

stavi58 commented 3 years ago

I'm having issues getting the bright pi working with octoprint. I've build the bright pi per the instructions and have installed the RPi.GPIO library, enabled I2C in RASPI-CONFIG and rebooted. Then did the auto bright pi install with "sSL https://pisupp.ly/brightpicode | bash" and had success but can seem to get it to work when I do the test command. Am I missing a step in setting this up? New to python

tvoverbeek commented 3 years ago

Does this help? https://community.octoprint.org/t/using-brightpi-with-octoprint/18557

stavi58 commented 3 years ago

That's what I was following and didn't seem to have luck. That in conjunction with your manuals.

On Tue, Feb 9, 2021, 1:26 PM Ton van Overbeek notifications@github.com wrote:

Does this help? https://community.octoprint.org/t/using-brightpi-with-octoprint/18557

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PiSupply/Bright-Pi/issues/18#issuecomment-776182583, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASZB4TXUB4VGCFISVLQADBDS6GD6NANCNFSM4XKMIFJQ .

tvoverbeek commented 3 years ago

Anything else using the I2C bus? (e.g. LCD display, sensors on the printer, sending commands to the printer, etc.). What is the output from i2cdetect -y 1 (note: no sudo). Bright-Pi uses I2C address 0x70.

stavi58 commented 3 years ago

No there isn't. This is what I get with the I2Cdetect command. PXL_20210216_143307537

tvoverbeek commented 3 years ago

Something is definitely wrong with your i2c setup. i2cdetect detects a response on every i2c address. Check your wiring for the i2c bus (GPIO2 and GPIO3, physical pins 3 and 5 on the 40-pin connector).

tvoverbeek commented 3 years ago

Generally this happens because something is pulling SDA (pin 3) low. The i2cdetect program checks for the existence of a device by sending its address then letting SDA float high. If the device exists it should pull SDA low to signal its presence. Check your wiring to make sure SDA hasn't been inadvertently connected to ground.

stavi58 commented 3 years ago

Ok i got the light up and running via the test command (brightpi-test.py) through the command line. Now my last question. What plugin on octoprint do I use to independently control the IR LEDs and the white LEDs?

On Tue, Feb 16, 2021, 8:53 AM Ton van Overbeek notifications@github.com wrote:

Generally this happens because something is pulling SDA (pin 3) low. The i2cdetect program checks for the existence of a device by sending its address then letting SDA float high. If the device exists it should pull SDA low to signal its presence. Check your wiring to make sure SDA hasn't been inadvertently connected to ground.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PiSupply/Bright-Pi/issues/18#issuecomment-779888016, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASZB4TT6I4QRIUWHMZZFH73S7KBFFANCNFSM4XKMIFJQ .

tvoverbeek commented 3 years ago

The LEDs can be controlled with the functions of the library. See https://github.com/PiSupply/Bright-Pi. You must find a way to run your own python scripts from octopi.

stavi58 commented 3 years ago

Got it. Thanks

On Sun, Feb 21, 2021, 6:27 AM Ton van Overbeek notifications@github.com wrote:

The LEDs can be controlled with the functions of the library. See https://github.com/PiSupply/Bright-Pi. You must find a way to run your own python scripts from octopi.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PiSupply/Bright-Pi/issues/18#issuecomment-782849891, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASZB4TXO2K3YOCCYYCJEOHDTAD335ANCNFSM4XKMIFJQ .