Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members!
[Sorry long post, so I color coded it]
I built a trident. So far so good. Awesome printer, fun build.
I bought some LED buttons on Ali and figured out how to use them as G-code buttons on the front skirt. Pretty cool. One toggles my case lights on and off (they are connected to a spare HE2...
Tied PB6, PB7 PA9 and most of the PE block and they all acted the same. Only spot that continues the proper effect while printing without going schizophrenic is the neopixel slot.
I tried taking 5v from a fan spot, bl touch and direct from the 5v psu.
Man my setup must be funky. I tried exactly that multiple times and it’s going all wonky.
I ended up adding a klipper expander for the 2nd neopixel slot and finally things are working smoothly and predictably.
Daylight starting sets my case light (daylight on a stick) 24v leds to a certain brightness. They are separate from the Disco stick XXL I'm trying to get to work.
I did some further testing and it has something to do with the output pins I'm trying to 'hijack' on the board. I wired the disco...
Here is my print start macro but there shouldn't be anything to trigger the LEDS in there. I've been triggering them manually for testing rather than trying to automate a routine.
[gcode_macro PRINT_START]
# Use PRINT_START for the slicer starting script - PLEASE CUSTOMISE THE SCRIPT
gcode...
Relevant block below. It seems hardware related. When the printer is not printing the LEDS act properly. Effects are smooth and predictable. Seems like noise on the signal pin or something being generated when the printer is printing actively.
Where do you put the resistor? I put it close to...
OK so I have this plug-in working and I can show a normal rainbow effect when the printer is at idle but once the printer starts working the LED effects go kind of crazy. The normal slow flow of the rainbow is erratic and flickering. Anybody know what I did wrong?
My LED is plugged into a BTT...
Great work guys. I was able to get this working on my new trident build with TAP.
One thing I can't figure out is how to set the purge_length. 50 mm seems too long for what I need but the line_purge.cfg is 'read only'. I'm assuming this is by design and I need to set the variable_purge_length...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.