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…
Hello @Bjoern, Thank you so much for all the work you put into putting out better firmware for the SV04. I’ve recently started using it and it’s a great upgrade. I also see you’ve been active on the forums here and helping people in the community and I feel guilty asking for help when I have nothing to contribute, but here I am.
I’m having what appears to be the same issue as urbnsr above with the filament runout sensors. I haven’t been running your firmware long (maybe 2-3 weeks) and am on 1.15.6 according to the display panel for both the printer and display.
I’m going to be doing a longer print that doesn’t need to look nice and using up a bunch of old rolls, so I wanted to test the runout sensors before doing so. I started a random small print with just a piece of filament stuck in the sensor, and after it had started pulled it out. Here’s what happened next:
- hot end lifts and moves over the purge bucket
- the printer first feeds a little then completely retracts the filament out of the extruder
- the “paused” screen is displayed with the options to stop or resume
- I select resume
- I feed new filament into the extruder and replace my piece in the sensor (as this is a test I wasn’t actually feeding through the sensor). I should note I’ve tried this out of order and doing it before selecting resume and it doesn’t appear to have an impact.
- the printer returns to the normal printing screen however, as described by urbnsr above the hot end just stops heating and its temp starts droping even though the display indicates it should be set at, in this case, 215
- after no major change and given plenty of time to work through things I will press the stop print button
- things get weird.
I wish I could be more specific here but as I’ve tested this a couple times I have not gotten consistent results. A variety of symptoms happen but not always in the same order. The system seems to enter some sort of loop. It may soft reboot at this point but if it does it comes back online with the temp set to 170 for some reason and also gives a number of beeps like it was pausing the print. I am unable to start a new print. I can select the print button and select the file, but it will not accept the user input to start the print. Exiting out from this screen can result in another soft reboot (this is why I say it’s in a sort of “loop” as the only way to start a new print is to use the power button to to a cold start). The system sometimes after rebooting will bring up the pause screen again. I’m assuming on boot it must be thinking that it had a print in progress and had power loss instead of a proper shutdoown? Regardless, its after this that sometimes it brings up the “manually change fillament, click print to continue or stop to stop print” screen.
I was wondering if you’d been able to replicate this issue yourself. If I can provide any more information I’d be happy to do what I can to diagnose the issue. I have not yet but can connect a USB cable to it and bring up pronterface to get a little more information. I’ve noticed this thread itself is quite old and spans a few topics, if you would like me to open a new thread dedicated to it I would gladly do so (I’m new here, not sure on the expectations of that sort of thing).
I hope you read this and are able to help, thanks for all your work!
Hello Pearldrums,
first of all, welcome to the forum. You described several observation which touch several Marlin firmware features that might have had impact…
- advanced pause feature
- filament runout handling
- cold extrusion prevention
- power-loss recovery
Additionally, aborting (stopping) the print without resetting the printer might have left instructions in the queue which led to “weird” & non-deterministic behaviour.
For a thorough analysis it would need more details about printer state (e.g. selected print mode, printed g-code, actions take (buttons pressed) & hidden temp file on your SD-card.
Anyhow, I appreciate your input. Currently I’m working on a new release & will have a deeper look at the (re-)heat procedure after changing/loading filament.
/R
Björn
Hi Bjoern. Thank you for putting so much work into your firmware and this forum. I’ve been using the Sovol SV04 for about 2 months now, and I’m actually quite happy with it. I guess I’m a very beginner in this topic, and therefore the printer doesn’t have to do many things to please me. However, I’m now trying to print with TPE that is biodegradable, and the producer of the filament recommends a printing temperature of 165 Celsius. I noticed that the SV04 is only printing this filament if I set the temperature to 180 degrees Celsius. I guess it’s because the firmware does not accept any value under 180°C. Now my question to you and your firmware is, have you lowered this value? So, can I print my biodegradable filament with your firmware?
Thank you!
Kind regards
Phil
Hello Phil & welcome to the forum!
Short answer: Yes, the SV04 firmware can support printing with lower temperatures that 170°C - this is the current low temperature limit.
It will require to modify the safe extrusion temperature of the PREVENT_COLD_EXTRUSION function.
It can be done by adding the following line of code to the beginning of your G-code file or in the custom G-code section of your slicer:
M302 S150 ; only allow extrusion above 150°C
Alternatively, you could disable PREVENT_COLD_EXTRUSION by using this line of code, but I won’t recommend it:
M302 P1 ; disable cold extrusion checking
/R
Björn
1 Like
Hi Björn, to clarify, is 170 degrees Celsius the low limit of your firmware or Sovol’s own firmware?
And with your line of G-code, can I print at 165 degrees Celsius with both Sovol’s and yours?
If that’s the case, since this is the only restriction I encounter, I may just stick with Sovol’s firmware to keep things easy.
Many thanks!
Best regards
Phil
Hi Phil,
affirmative: PREVENT_COLD_EXTRUSION / M302 is a native Marlin feature which is under the hood in all SV04 firmware versions.
/R
Björn
Hi Björn, thank you for your answer. I used this G-code before with my Prusa Slicer, and it worked to the point that the extruder did work, but the temperature was not read at all. I had it set to 165, but the control panel showed 0°, and it tried to print the part with zero-degree nozzle temperatures.
Therefore, I thought there might be another safety mechanism in place, not only to prevent cold extrusion but also to not read any temperature under a certain value. Am I right with my assumption here?
Firmware version is V1.1.4
I very much appreciate you,
Cheers,
Phil
Hi Phil,
Sovol did not publish their firmware v1.1.4 sources, therefore I won’t be able to find out what went wrong.
There seem to be four solutions:
- Send a problem report to Sovol: info@sovol3d.com
- Ensure a difference of at least 10°C between printing temperature and
M302 Sxxxlower limit temperature. - Try disabled cold extrusion prevention checking:
M302 P1 - I just ran a test using my current firmware version v1.15.7. Extruding at 150°C works when the temperature limit has been lowered using
M302 S140. Maybe it is a good time to switch from the stock firmware.
/R
Björn