First of all, I do really appreciate your fast responses and your willingness to help, yet to me, it does not seem to be an Orca problem, as the print will work fine when I use Luban to upload it to the machine and start it from the display. It must be originating from OctoPrint, as I am faced with the same problem when printing a file that is sliced with Luban through OctoPrint.
I also feel like there is a thread documenting my exact struggles here:
But sadly, that thread seems to have been dead for quite some time.
What I am really looking for is Host Action Commands and a solution for the custom G-code problem with the tool changes, described in the thread I linked like this:
“Issue 2. Snapmaker uses a custom gcode command for tool changes (M2000 S200). Originally, this gcode was incompatible with Octoprint. I have altered the code so that it works with Octoprint. This test resulted in successful tool change when switching from T0 to T1. T0 returned home and T1 continued the print in the correct location. However, when switching from T1 back to T0, T1 did not return all the way home. It stopped at x324 because it was restricted by software endstops.”
It seems that at this point, enabling Host Action is possible by compiling the Snapmaker firmware and uncommenting a line in the C++ code. But Snapmaker stopped uploading their code to the public repo, which would leave me stuck with a 5-year-old version of the J1 firmware, which is not really a great outcome.
Even though many internet tutorials give this as a “simple” solution, I am also not quite sure if just enabling them might cause other errors in the build.
I do feel like there is not much I can really do about the problems with the printer heads; the person posting the other thread seems to have built a workaround, but I really don’t feel comfortable working on the firmware code of my printer.
It does really feel like there should be an official solution by now, as using OctoPrint has really become a fairly normal requirement for consumer printers.
At this point, I feel like I should open another thread regarding OctoPrint support. Do you agree?