This helps so much, thank you!!
Tomorrow I will try to connect octoprint through the front. If that works, that will be my go to setup as second best option i guess.
1 Like
I just tried connecting my RPI with octopi to the front of the USB-A port of the Snapmaker J1, but I am not able to get connected, so I think only the USB-B port is compatible for this kind of communication.
After this I tried manually editing the G-code (M605 S1 after the G28, and using only the word TIME for enabling time left of printing) from luban and applying the right command order. That worked, but is not really convenient to must be doing this all the time.
Also: the extruders are warming up above the object, just like when using Cura Gcode.
About the filament runout sensor not working, I think that has to do with the printer's firmware not supporting host action command. See: OctoPrint tells me my firmware lacks support for "host action commands", what does this mean?
I now tried something new: duplication mode. This has the same behaviour. It prints normal via USB-stick in the front and via octoprint only T0 starts printing.
Luban test duplication.gcode (312.3 KB)
Do you see something unusual in the Gcode?
After reading the reply from @MarkA121 and interacting with @xboxhooah I have come to the conclusion that Snapmaker has purposely crippled the firmware when commands are being fed through the USB-B connector.
All is not lost, however, as Snapmaker has open-sourced the firmware. The Github repository is at https://github.com/Snapmaker/SnapmakerController-IDEX and there are some issues reported regarding OctoPrint.
If I understand the issue #30, then it looks like remedies for the problems seen in this topic will require learning how to build and modify the firmware if someone in the community that frequents that repository hasn't made a fixed version available.
@xboxhooah, I don't see anything unusual in that gcode but see issue #29 for a possible fix.
1 Like
You can add the M605 commands to the starting and ending gcode automatically. In Cura, there is a place to enter custom Gcodes for starting and ending a print under each printer's profile. Octoprint also has a place for custom gcodes. I would expect that Luban has the same functionality, but I'm not familiar enough with it just yet to know for sure.
Cura is not giving me the workaround I need, so I'm staying with Luban. If only I have a simple way to edit the Gcode that let's the Snapmaker J1 do what it's supposed to do, via the USB-B, it would be a second best altenative for me.
It looks like Luban has no functionality to editing Gcode. So i edited the Gcode myself and replaced 'M605 S2 X162 R0' with 'M605 S0' and after the G28 I placed the 'M605 S2 X162 R0', all for a proper homing result.
test copy.gcode (313.6 KB)
Unfortunately only the left extruder (T0) starts printing, while the right extruder (T1) warms up but does no go to print.
Anyone ever figured out how to use duplication and mirror mode via octoprint?
I shared this post and my other post Octoprint and IDEX problem: extruders run into each other - #24 by MarkA121 - Snapmaker J1/J1s - Snapmaker: where creation happens with Snapmaker support, after they told me to ask the community for help. This was their response: "We are sorry, due to the shortage of staff in the R&D development, we are temporarily unable to solve the problem of third-party modification of the machine for you. I hope you can understand."
I don't think we can expect any updates in the firmware at any time from Snapmaker itself.
Then they should put the source files into the open source community.