Replies: 1 comment
-
I think I found a clue. OrcaSlicer and PrusaSlicer initially send out a M104 to set the hot end and does not wait to go to temp but continues to custom start gcode. However PrusaSlicer sends and additional M109 after the custom Start Gcode.. Not sure why Prusa does this but maybe LEDs only go to white after M109? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am still running a MendelMax 2.0 that I built and modified to stay current now running Marlin 2.0 and specifically using neopixels. I have gone from slic3r to PrusaSlicer and now to OrcaSlicer. I am puzzled by something that I can easily fix with a M150 R255 B255 U255 in startup.
So what puzzles me is that in PrusaSlicer my LEDs would change colors as the bed was heating and then when the print would start all LEDs would turn to white and stay on during the print. With OrcaSlicer It goes through the temp colors but then it remains at the last temp color through the duration of the print. Neither Prusa ir Orca send out M150 as best as I can see in the Gcode. This function is done in Marlin so there should be no interaction. When I compiled Marlin 2 i enabled the Neopixels and I have #define PRINTER_EVENT_LEDS to allow Marlin 2.0 to cycle through the colors. So why does it not work with Gcode made with OrcaSlicer?
Beta Was this translation helpful? Give feedback.
All reactions