-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can not see the controller when powered with 24v #52
Comments
Okay, but it does not seem to be working with the P1S. Simple example, I manually turn the P1S light on and and off with no change to the led strip. How would I know if the controller and the P1S are communicating? |
It does work with p1s, mine works perfectly fine with the latest firmware. If your printer refuses to send mqtt information factory reset both of them. Note for the p1 series printers is that you can only have 1 mqtt device eg blled connected to the printer |
It doesn't seem the issue you are experiencing is related to 24v. |
I'm stuck. I finally reset my P1S to factory default and that seems to have
helped (log file attached). The log file says everything is connected but
the LEDs still don't respond. When I disconnect from the computer and power
with the DC input, the LEDs just blink different colors. My test of
connection with the P1S is to turn the P1S LED strip on and off. No
reaction from the LED strip. Could it be the LED strip?
(
https://www.amazon.com/gp/product/B0D4QKVZHP/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
)
On Mon, Nov 25, 2024 at 9:44 AM ***@***.*** ***@***.***> wrote:
It doesn't seem the issue you are experiencing is related to 24v.
It seems it's the simple case of incorrect config. Make sure you enter
correct IP, access code AND serial number.
Also, visit https://dutchdevelop.github.io/blledsetup/ click connect and
then Logs & Console it should tell you if the controller connected to the
printer and receiving messages.
—
Reply to this email directly, view it on GitHub
<#52 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDCDNCY52AZUS4T64YIWRT2CMZULAVCNFSM6AAAAABSJPPSEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYGIYTKNRTG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
Network scan complete
No wifi networks found :(
…-------------------------------------
Connecting to WIFI.. Status check #1 / 10 SSID: NETGEAR_2G BSSID: D2:98:B5:4C:AA:E0
Connecting to WIFI.. Status check #2 / 10 SSID: NETGEAR_2G BSSID: D2:98:B5:4C:AA:E0
Connecting to WIFI.. Status check #3 / 10 SSID: NETGEAR_2G BSSID: D2:98:B5:4C:AA:E0
Connecting to WIFI.. Status check #4 / 10 SSID: NETGEAR_2G BSSID: D2:98:B5:4C:AA:E0
Wifi Status: WL_CONNECTED
IP_ADDRESS:192.168.1.40
Connected To Wifi Access Point: NETGEAR_2G
Specific BSSID: D2:98:B5:4C:AA:E0
RSSI (Signal Strength): -38
BLLED Controller IP Address: 192.168.1.40
Use web browser to access 'http://192.168.1.40/' to view the setup page
Setting up webserver
Webserver started
Setting up MQTT with Bambu Lab Printer IP address: 192.168.1.22
Finished setting up MQTT
Connecting to mqtt...
MQTT connected, subscribing to MQTT Topic: device/01P09A452201208/report
** BLLED Controller started using firmware version: Experimental 16.5.24 **
Updating LEDs from Setup
Initial Boot
(Filtered) MQTT payload, [19013], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [22911], {"print":{"command":"push_status"}}
(Filtered) MQTT payload, [24923], {"print":{"wifi_signal":"-68dBm","command":"push_status"}}
(Filtered) MQTT payload, [26896], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [38961], {"print":{"command":"push_status"}}
(Filtered) MQTT payload, [41015], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [44995], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [49021], {"print":{"wifi_signal":"-68dBm","command":"push_status"}}
(Filtered) MQTT payload, [53085], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [59156], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [61086], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [69172], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [71226], {"print":{"command":"push_status"}}
(Filtered) MQTT payload, [75208], {"print":{"command":"push_status"}}
(Filtered) MQTT payload, [77261], {"print":{"wifi_signal":"-68dBm","command":"push_status"}}
(Filtered) MQTT payload, [79238], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [81250], {"print":{"command":"push_status"}}
(Filtered) MQTT payload, [85272], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [87285], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [93356], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [95292], {"print":{"wifi_signal":"-65dBm","command":"push_status"}}
(Filtered) MQTT payload, [97346], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [113429], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [115482], {"print":{"wifi_signal":"-64dBm","command":"push_status"}}
(Filtered) MQTT payload, [119462], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [121515], {"print":{"command":"push_status"}}
(Filtered) MQTT payload, [123445], {"print":{"command":"push_status"}}
(Filtered) MQTT payload, [125504], {"print":{"command":"push_status"}}
(Filtered) MQTT payload, [129485], {"print":{"wifi_signal":"-68dBm","command":"push_status"}}
(Filtered) MQTT payload, [133589], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [139625], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [145656], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [147630], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [149684], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [151696], {"print":{"wifi_signal":"-66dBm","command":"push_status"}}
(Filtered) MQTT payload, [157773], {"print":{"wifi_signal":"-67dBm","command":"push_status"}}
(Filtered) MQTT payload, [159704], {"print":{"command":"push_status"}}
|
I got the lights to work but only temporarily. They were white and went off and on when I switched the light in the P1S. I was running an overnight print and in the morning, the lights were red and the printer was still printing without any errors reported. I reset the unit again and experienced the same issue, lights flashing random colors and no connection to the P1S. I reset again and monitored the log file. Everything looks good there except that it updates the LED's and goes into an endless loop. Any suggestions? I'm still excited to have this work but I'm also about to give up. |
I got the lights to work but only temporarily. They were white and went off and on when I switched the light in the P1S. I was running an overnight print and in the morning, the lights were red and the printer was still printing without any errors reported. I reset the unit again and experienced the same issue, lights flashing random colors and no connection to the P1S. I reset again and monitored the log file. Everything looks good there except that it updates the LED's and goes into an endless loop. Any suggestions? I'm still excited to have this work but I'm also about to give up. |
Is it me or is it the board? Please help me. |
I have flashed the latest firmware (16.5.24) and I can access and change the controller settings page when connected via USB but when I disconnect the USB and power with 24v, I can no longer access the controller and my P1S printer does not control the led strip. The led stip just changes colors (default, I assume). Any suggestions? I expect it is something simple that I've overlooked. Thanks for your time.
The text was updated successfully, but these errors were encountered: