Hey, I was hoping someone might have encountered this or know a solution. I had been using regular Orca when the problem started, so switched to Snorca and it didn’t do it until the other day. The only change I made that I can think of is I updated the U1 to the latest firmware (1.6.0). Basically, the slicer is adding a line at the tool change to turn off the LED light, which is really annoying and also shouldn’t be a thing because the error detection and camera both need the light on (also, I have the cooling fan plugged into the extra port at the end of the LED strip, which is why it’s really a problem). I can’t find anything in the slicer that even mentions the LED, so I have no idea why it’s doing it. Below is one example of a section with the line in the gcode. Any help would be appreciated.
Hi, After investigation, our software team could not find any hard‑coded instances of the SET_LED LED=cavity_led WHITE=0 command within the slicer source code.
Hi, Zoe. Thanks for the response. I made a very quick one layer test print using three filaments as an example, but it’s not an allowed file type to attach here. Who should I send it to?
Ok, so I went back and double checked all my profiles (printer and filaments) and found the issue. For some reason, that line was in a filament profile as the end gcode, which is weird since I don’t recall ever adding custom gcode to any filament. But I deleted the line and the problem stopped in the test print I tried. I didn’t realize that Snapmaker Orca and regular Orca shared custom profiles, is that something that was recently added?
I just consulted with our engineer, and he confirmed that Snapmaker Orca and the original Orca Slicer use two separate configuration folders. There is no code logic in either program that directly reads from or writes to the other’s directory.