Hi, how are you?
I installed the firmware and I really liked it, but about the left extruder, it still doesn’t accept a negative value in x, my code is similar to yours, could this be a limitation that Orca Slice is placing? I’ll do the same test on the Prusa later and let you know here, thank you very much for your help
Hi again,
the G-code above worked as intended directly via USB-cable using Pronterface & also via .gcode-file from SD-card. You could check your slicer output files whether there are any changes to your cleaning gcode sequence. Do you run a printer server that might apply any changes?
/R
Björn
Hi, I found the problem. If I use dual mode on the printer, the left extruder doesn’t accept negative x after it starts printing. I adjusted the gcode to use both extruders in single mode, and then everything works fine.
Now, another problem I’m having is with Pause. The machine stops and retracts the filament, but it doesn’t start printing again after I confirm to resume.
Hi again,
my g-code fragment posted above worked both in single mode & dual mode on my SV04. Which firmware version are you currently using?
Concerning your pause issue: Without details about current g-code sequence, actions you took, used printer mode & installed firmware version I won’t be able to provide any help.
/R
Björn
On the pause issue: I have posted about this before. I see it when the filament detector throws an error. The display gives the prompt: Paused. “Resume” to continue, “Stop” to cancel.
After I replace the filament and select Resume, the screen goes back to the printing progress display and while the bed temperature maintains it’s target temperature, the nozzle temperature keeps dropping even though the target temperature still indicates 210°c (in my case).
I am running firmware v.1.15.6
Then, either through time or the nozzle temperature drops too far, another error pops up. I restart at this point. I don’t know how the gcode could affect this, but this is the code used to test:
PauseIssue_PLA_1m2.gcode (5.1 KB)
Hello urbnsr,
I don’t remember your posting about a similar filament sensor issue. Anyhow, thanks a lot for your g-code & your description on how the issue happened. I’ll try to reproduce the situation & have a closer look iot find a solution.
/R
Björn
Thanks Bjoern. I don’t think my previous post was about the filament sensor, itself, I just used the sensor yesterday to simulate the condition to put the printer into the pause/resume cycle to better describe how it works. Or doesn’t…