SV04 M600 Filament change

[Wiriza01]

M600 command as others have reported for other makes appears to be overlooked by printer. in forums found:

M600 on the SV02 - Need to edit firmware?

Has anyone been able to use the filament change GCODE command M600? My SV02 seems to just skip over it, so I believe it is disabled in the firmware. Unfortunately there is no uncompiled SV02 firmware that I can find. I’m unsure which firmware on the Marlin site would be compatible, as it doesn’t list SV02 as a config example. Does anyone have any suggestions? Thank you in advance.

Filament runout sensor support in Octoprint

I am aware of how to solve it with octoprint and a seperate signal hooked up to the raspberry pi. The issue here is, that Sovol heavily changed Marlin to use the DWIN display in the way they do resulting in a configuration that actually has no display defined in the configuration.h. This means from a Marlin perspective there is no way of a user interaction to respond to a request like an M600 command. During build, this is checked and so the build process throws errors. I will probably excha…

(There were more but limted to two links)

Unclear if Advanced_Pause_Feature is set in configuration_adv.h and as noted w/ last article would need to understand more about DWIN display… all i was looking for was for an updated firmware.

Running [SV04 V1.1.0 Latest Firmware (24th Jan 2022)] which is a year old… Hoping solvol may have an update and or guidance on filament swap (rather not have time filament cut for filament out sensor to swap out. IDEX does help alleviate the need, but still find the need when printing w/ more than 2 color / filament types. Love the printer, but feel it may be time to revisit the Firmware on the SOLVOL 4. Anyone suggestions on m600 gcode commands?

[Bjoern]

The ADVANCED_PAUSE_FEATURE is not activated in SV04 v1.1.0 Marlin firmware. Filament chages are handled in the display handler LCD_RTC.cpp. Building a new FW version seems to be necessary iot process the M600 command.

[Wiriza01]

Thanks. Figured this would be the answer. Unfortunately will keep bypassing one of the filament sensors and “time” it for now. Will await new fw…. Guess not high demand function.