SV04 Bugs (Bjoern's firmware)

Sovol SV04 IDEX
1

So, first and foremost, this is post-power outage, so the firmware is probably fine. I just need tips on what else to try.

Problem: when i go to print a file using Single Mode L (in both printer and slicer), left heats up, table heats up, but then after homing, left returns to its bucket and right also heats up. While heating, right reverse extrudes (out the top, even though there is nothing in the right side at all), and then left does the same.

When I stop things, I get a
Beep, beep, beep, beepbeepbeep, beep, beep
Type of pattern. (1) does this indicate an error of any sort? If so, can we tell the error type?

Following this, I get a random “do you want to resume” popup, and will have PLR file on the SD card. If I stop things quickly and remove the SD card quickly, I don’t have that though.

Things I have tried:

  1. I reflashed the firmware to Sovol 1.1.0 and back to Bjoern firmware, and also reflashed the touchscreen. No change.

  2. I used a different SD card. No change.

  3. I used a different slicer, same settings. No change.

  4. I looked through the gcode manually. The right side temperature is being auto set by the machine to 170, the left side is 250. I see a T0 S250.0 command in the gcode, but there is no T1 S170.0 command. The only 170 in the gcode at all is a y axis position, so I dont think the gcode is making the erroneous commands.

  5. Literally everything in the software works fine - move commands, heating, leveling commands, PIDs, Esteps, Refill commands, etc. Its only this weird thing that happens during printing. Flashing software also goes without a hitch.

  6. I tried the trick where you put M(something or another) at the beginning-ish of the gcode to disable PLR, but that didnt change anything.

Other ideas: I do have another motherboard from when I initially had issues and it turned out to be a bad sensor, so I can try replacing that, but I feel like a firmware flash shouldve corrected software issues, and hardware issues would be more destructive. (2) is that intuition wrong?

(3) Does anyone have any other ideas as to the cause? I’m willing to post the gcode in question so someone can double check me.

Also, in the event I swap the motherboard, I’ll veeify wire connections, but I’m 98% sure nothing has moved since when it was working.

Any help you could offer to my 3 questions is greatly appreciated!!!

2

Hello @Bjoern
Just in case you haven’t seen it.
BR

1 Like
3

Hello konokaiden,
your first observation indicates the result from the right filament runout sensor missing filament: This will heat up the right extruder iot to reload filament. Solution: Ensure that at least a piece of filament is inside the right sensor & that the sensor LED is lit. Alternatively, remove the right sensor connector & try again.
Ad (2): Affirmative, this intuition is wrong - see above.
Anyhow, in case of a defective motherboard port, a custom firmware version that supports filament runout sensors on alternative ports could be a solution.
Ad (3): You could also deactivate the filament runout sensors using g-code M412 S0.

Good luck
Björn

4

Bjoern,

Thanks for the response, this did fix my issue. But my question is, why do i need filament in the unused extruder to run a single extruder print? I dont think this this was the behavior of the default firmware… I could be misremembering, though. When I changed slicers, i used the Sovol slicer, and it definitely didnt auto-populate this M412 S0 just by choosing single mode 1, though that would be a nice feature.

Assuming I added M412 S0 to the code, would that be a permanent shutoff on the checking, or just for this one print file?

Edit: also it’s now no longer giving me any time stats:

17472562496886122197412773121013
174725624968861221974127731210131908Ă—4032 438 KB

Thanks,
Konokaiden

5

Hi again,

Short answer: My current firmware version uses the Marlin advanced pause feature. A filament runout signal will initate the filament change procedure. Sovol’s stock firmware doesn’t use that feature thus the behaviour is different.

This will deactivate the filament runout sensors until the next power-on or the next M412 S1 g-code instruction. Details can be found here.

Check your slicer settings. The time display depends on the set print progress instruction M73.

/R
Björn

2 Likes
6

A legend and a saint! I’ll go ahead and make the gcode changes so it behaves how I’m used to. I really appreciate the help!!!

7

You forgot “a genius”… truly. Björn’s knowledge is encyclopeadic!

8

Thank you for feeding my ego, but rather than encouraging my tendency towards megalomania, let’s focus on what this forum is all about: sharing knowledge, experiences and help to fix problems that have arisen. For the latter, precise problem descriptions make it easier to identify the causes of the problems and find solutions.
Some of the problems occur more frequently, in these cases a reference to an already described solution saves the effort of rewriting. In the case of firmware-related problems, it is not always immediately clear whether it is a bug or possibly a feature of the underlying Marlin firmware. In any case, precise problem descriptions help to analyze and finally to improve the firmware.

Happy printing!
Björn