#neopixel wont turn on and klicky pcb is lighting up but won't change state when pressed.

7 messages · Page 1 of 1 (latest)

azure tulip
#

I got the klicky pcb setup with 2 piece stealth burner pcb set and connect all the wires to BTT octopus v1. When I power on the printer klicky pcb blue led lights up and when i press down the trigger it turns off but printer doesn't pick up any changes in state.
I have tried the signal wire with PB7 and PG15. Tried ~PB7, ^PB7, !PB7, and ~!PB7. Same variants with PB15. None of them worked. The klicky pcb did come with a spare and I tried with that too same issue.
Neopixel is wired to the PB0. The macros nor any command will turn it on.

#

neopixel wont turn on and klicky pcb is lighting up but won't change state when pressed.

azure tulip
#

Also when I disconnect klicky pcb. Query probe doesn't show triggered.

azure tulip
#

It turns out it was the bat85 diode. So I change signal wire to use signal of the aux port and move the wire to board PG 14. Now the klicky is responding. So half way there. Got the idea from here: https://www.teamfdm.com/forums/topic/3474-klicky-pcb-issues-with-sb-toolhead-board-octopus-control-board/

Still need to fix SB neo pixel. If anyone know what to do that would be appreciated.

Team FDM

Issues with Klicky always in triggered or open state .Klicky is working as in blue LED is on when attached, when switch is pressed it turns off,when removed from toolhead light turns off,however state remains always triggered or open in Mainsail depending on Klipper configuration. Klicky pcb has ...

azure tulip
#

I tested out the voltage it a multimeter. + to - does show 4.9. I accidentally touched something and first led turned green

#

I had removed the jst head of a spare led I got and plugged it into PB0 directly with g and vcc to see if the leds were bad or board was bad. Light turning out means LEDs are good right? Something must be off on configs?