-
|
Is there a way to do this without loading the project and recompiling it? For my strip, green in the UI actually delivers red, red delivers green, and blue correctly delivers blue. Also, need to increase the number of addressable LEDs to 96, as only less than half of my strip lights up. Thank you, I love this project; it's wonderful! |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 6 replies
-
|
No way to fix this at the moment without building it yourself. Wouldn’t be too hard to add those things as configuration options though. |
Beta Was this translation helpful? Give feedback.
-
|
I've added this functionality - you can update your device over-the-air - details are in the release section. |
Beta Was this translation helpful? Give feedback.
-
|
OMG, thank you! I ran the update (super convenient how you set that up), and everything worked great! Still running it all on a breadboard, so I want to do some more testing, but seeing perhaps one or two bugs. The one I’m more confidant in is after setting 96 LEDs, then power cycling the ESP, it defaults back to the 33 or 36 LEDs. Not a big deal of course. It let’s be set it back to 96 4 out of 5 times, but can get into a funk where it ignores the number I set, or lights up a little of the beginning and the end of the strip at the same time. Power cycling it again and setting it back to 96 fixes that. That could be breadboard related or something on my end though, I’ll do further testing. The shift to RGB works perfect. One other quick question, this is the strip I’m using: It wants it defined like this: Does that “NEO_KHZ800” matter? And/or is that what your code is using already? Just double checking. Lastly, thanks for the quick reply on this, super cool project you have here, love it! Can I buy you a coffee or something? You have a favorite coffee shop I can get you gift card for or something? Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
Whoops - a bug in saving the state, see below. The recommended settings are pretty standard, this software will work fine with that strip. One thing to watch is the power requirements of the strip. If you get random glitches then you might need to think about how you provide power to the whole setup. |
Beta Was this translation helpful? Give feedback.
-
|
Just checked the data sheet. The strip has a max rating of 13W, which is 2.6A at 5 volts. Most USB wall warts top out at 2.1A, so if you see some glitching you should probably get a beefier supply and adjust your wiring appropriately - Adafruit has some guides on that. Remember the ESP32 needs some power too, though that tops out at about 0.4A. |
Beta Was this translation helpful? Give feedback.
-
|
Fixed persistence bug - new release |
Beta Was this translation helpful? Give feedback.
-
|
You rule! Thank you. Yeah, I was just going to include this link (https://www.amazon.com/dp/B08D5ZD528?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1) to the ESP I'm using if that mattered in the ROM/saving issue. Thanks for tracking that bug down. Regarding power, I'm using a 10A desktop variable power supply at the moment and will be sure to provide lots of amps in the final setup. Thanks! One other bug, possibly, and I'll keep testing to provide more info to reproduce. I've seen the strip get stuck in either the "Printing" or "Warning" states a few times and only a reboot will reset it. A couple of times I've just had the strip sitting on my desk in the "Printer Idle" state, and it changes to "Printing" all by itself (I think). I've also seen this when I just hit "Print Plate" in Bambu Studio, then cancel the final dialog box and actually not start the print. The strip hops into Printing (after clicking "print plate" and does not leave it. The other one is when I start a print, and everything is working well, then I cancel the print through Bambu Studio (red stop square), and the strip goes into Warning mode, which is correct. But when I clear the warning box in Bambu Stuido, I would expect the strip to go back to Idle at some point, and it does not. All this is just feedback, so no rush or anything here, love the project, thank you so much! I'll keep testing/playing around with it. Nice work! |
Beta Was this translation helpful? Give feedback.
-
|
Just ran the update, 0.3.1, and works great! LED Type and Count persist now, thanks! One thing to note, the udpate resets all Reactive Settings, and the Printer's IP, Access Code, and Serial number, all very minor to set back up, but just thought I would note. Also, I think I have more info on the unexpected state changes noted above. The strip moves as expected from idle to printing as soon as you click print plate in BS. If you don't go froward with the print and X out of the print plate dialog, the strip will stay in the printing state forever (I think). If you actually start the print, then cancel/stop it before the end, the strip goes into Error (not warning) state and remains there for about 3-5 mins, then flips back to printing (not idle). If you reboot during that error state, it boots up to idle, but then flips to printing in that same 3-5 min window. Hope that helps, again, all minor, thanks again! Edit: Looks like actually doing nothing, just booting up the ESP/Strip, watching it go from no wifi, to no printer, to idle, it will eventually hop over to the Printing state after 3-5 mins. Just an FYI... Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I’ll have to take a look at what MQTT messages the printer is pumping out and verify them against my state machine. There’s a lot of messages! Take a look at MQTTBroker.cpp |
Beta Was this translation helpful? Give feedback.
-
|
Gotcha, will do, no worries, this is super cool! Also, https://buymeacoffee.com/ Happy to support you and the project. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Just wanted to check in. I've had the whole setup running for 2 weeks now, and it's working great! I love it, thanks again. What I found with my P1S on 01.07.00.00 is that the lighting states work perfectly after one print cycle and until the printer restarts/powers-down. However, if the printer restarts, the states are random, with the behavior I described above. So, it's not really a big deal. Suggestion: The P1S's internal stock light is dumb. Perhaps with a Bambu firmware update, it will get smart and turn off after a print. Wondering if you could add an IO pin assignment in your app to trigger a relay that can control the stock light. i.e., I ONLY want it on when I'm printing. Thoughts? Thanks again! |
Beta Was this translation helpful? Give feedback.
I've added this functionality - you can update your device over-the-air - details are in the release section.