Sovol SV06 2.1.x bugfix build

Due to some issues with updates to Marlin 2.1.x bugfix causing extruder issues, I am temporarily removing v60 from the releases. If you are using v60 I encourage you to go back to v57 until the upstream issues are sorted and I can push a newer update. I am sorry for the inconvenience.

This is for the STOCK Sovol mainboard that comes with the SV06

NOTE THIS IS HIGHLY EXPERIMENTAL FIRMWARE! USE AT YOUR OWN RISK!

IF YOU NOTICE WEIRD BEHAVIOR ON FIRST USE OR AFTER UPGRADING VERSIONS, TRY GOING TO CONFIGURE/ADVANCED/INITIALIZE EEPROM and then reboot

Testing steps for this firmware.

• Grab latest version (or whichever version you like) from the release section here
• Put binary on a fresh FAT32 formatted SD card and insert the sd card into your SV06 while it is powered off
• Boot up SV06. It may take 10-20 seconds. Screen will flash and it should boot. The SV06 Stock board can sometimes be temperamental with sd cards & flashing, if your flash fails & you're left with a blue screen only, switch off & try another card, a new name brand with a fresh format helps.
• It should reset the eeprom when changing a major firmware, but you can config/advanced/initialize eeprom & reset too if you wish.
• Please ensure your X gantry is perfectly level to your bed , do this manually & not with the Auto Z Align function.Use two identical objects on the bed, one under each side of the gantry & lower the gantry down by hand, do not use the motors to lower it, steppers must be disabled or printer should be turned off.
• Go to Motion / Homing and select Auto Home. Watch the homing process. The X axis should go ALL the way to the left and bump up against the left side of the frame. The Y axis should go ALL the way to the back and bump into the back of the frame. If either of these don’t go all the way, or make grinding noises your sensitivity is too high or too low respectively. If you have an issue with the X axis not going all the way to the left your sensorless homing for the X is too sensitive. Likewise if it grinds loudly against the left side it is not sensitive enough. Go to Configuration / Advanced / TMC Drivers / Sensorless Homing. Go to the axis you need to tweak (X or Y). If your X axis stops before hitting the left side you are too sensitive on X. So lower the X value by 5 and retry homing. If your X grinds too much for instance on the left side, you are sensitive enough so raise the X value by 5. Use the same process for Y if it has issues. Once you tweak the values to your liking, be sure to save settings so they persist reboots.
• Autotune PID. Configuration / Advanced / Temperatures / PID Autotune Extruder (wait for finish). Be aware this can take awhile
• The way to tell PID tune is done is your hotend will be cooling down to room temp.
• Store Settings is a good idea here incase of reboot
• Autotune Bed PID Configuration / Advanced / Temperatures / PID Autotune Bed (wait for finish)
• Store Settings is a good idea here incase of reboot
• Before doing any of the following steps. Make sure there is NO filament hanging out of the nozzle . The Extruder autotune done previously can cause filament to ooze out. This can cause you to get faulty calibrations when you do a Z offset or X-Twist as the dry filament will make you think you are closer to the bed that you are!
• Go to Configuration/Advanced/Probe Offsets /Z Offset Wizard (No X-Twist) & calibrate your z offset. Save settings.

  If you downloaded the UBL version follow these steps next

• Go to Motion / Unified Bed Leveling / UBL Mesh Wizard
• Let the UBL probe all the points it can. It won’t be able to do all 100. This is normal.
• Settings should autosave after UBL finishes, but you can save yourself too if you wish

  If you downloaded the bi-linear version follow these steps next

• Go to Motion / Bed Leveling / Level Bed
• Let it probe all 25 points
• When finished do a store settings to save the mesh data

  The following steps are for UBL or bi-linear versions

• Do a test print now before trying x-twist. This is to see if the UBL or bilinear leveling is enough to compensate for your issues with first layers and such before even trying the x-twist. Make sure you have proper startup g-code to use the UBL or bi-linear mesh as mentioned below.
• If your print is good. Congratulations and happy printing.
• If it didn’t help enough, go ahead and run X-Twist. Configuration / Advanced / Probe Offsets / X-Twist
• IMPORTANT ! Rerun your UBL or bi-linear mesh after doing the X-Twist ( the twist doesn’t modify existing mesh data, if modifies future probed points as the UBL or bi-linear leveling does its thing )
• Save settings / Do a test print
• If your print is good, happy printing. If not, come on to the SV06 Facebook group and let us know. Pictures, detail, data, etc can help us in possibly identifying your issue and seeing if we can improve the firmware.
• Also if you find the UBL and bi-linear are not enough for your unit, you can download the manual-mesh version. This one functions like the bi-linear but you manually use the paper or feeler guage with the nozzle for the 5x5 array. Be sure to save after. For people who have struggled with their units getting good first layers with stock firmware, or my UBL or bi-linear version, the manual mesh has fixed their issue. Mind you this is a manual process and takes the probe out of the picture.

Highlights of features used in the three firmware builds

• Unified Bed Leveling (UBL) an optimized leveling feature that stores a high data point mesh in non-volatile storage. In your startup G-Code you just have it do a 9 point quick probe to figure out the tilt of the bed, and the high resolution mesh is adjusted.
• If you use UBL, add the following to your Gcode in your slicer after the G28 and after your printer has heated up to temp, but before any print starts. This will load your mesh and do that 9 point measurement to determine how to adjust the mesh if needed.

G29 A ; Unified bed-level (BL-Touch)
G29 L0 ; Load Mesh Slot 0
G29 J3 ; Probe 9 points to check mesh

• If you use bi-linear or manual mesh you can add the below line to your startup gcode after the G28. I have the firmware set to turn on leveling for you after a G28, but I would add the below line to be safe.

M420 S1

• X-Twist Compensation Compensates for a twisted X axis by having the user manually take three measurements of the nozzle to the bed and compares them to the probes calculation for that point. It then modifies all future probe points to try to compensate for the twist in the X-Axis. It is very important that after doing the twist you re-run the UBL wizard since the X-Twist values don’t change the existing mesh in memory, only as new points are probed. Also you need to be as precise and consistent as possible when calibrating the 3 X-Twist points. It is recommended to use a feeler gauge so you can make sure each of the three points has the nozzle exactly the same distance from the bed as the others.
• X-Twist Reset Menu : A menu option was added to reset the X-Twist data and turn it off. This would be useful if you want to wipe the twist as you don’t need it, or want to try it without it. NOTE: You must save your settings if you want to make the disabling persistent after a power off. Plus you need to redo your UBL mesh.
• PID Extruder and Bed Control
• Power Loss Recover This feature is turned off by default
• Filament Runout Sensor Support. This feature is turned off by default. The SV06 doesn’t come with a runout sensor, so here is a link to Rory’s design for a mount to install one on your SV06
• Z-Offset Wizard. If you don’t need the X-Twist because your X gantry isn’t twisted you can use this wizard to adjust your Z-Offset
• Rory’s tweaks

Common Troubleshooting

• Firmware flashing seems to be a problem for a lot of people. To start use a freshly FAT32 formatted sdcard. Make sure there are no other .bin files on it. Copy the firmware you downloaded to it. I recommend renaming the file to something short and unique. Any time you flash a new firmware it needs to be a different name than the last. Make sure it still has the .bin on the end of the filename. If it fails to flash, try a different sdcard.

• When you first home your SV06 after changing firmware, you might find the X axis doesn't go all the way to the left and tap the left side of the unit, or the Y axis doesn't go all the way to the back and tap the back of the frame. Or you may find it grinds against the left or back on X or Y. If this is the case, YOU MUST tweak your sensorless homing values for X and Y. If you find the axis in question doesn't move far enough to make contact with the far left or back, you want to decrease the sensitivity of that axis. Likewise if it grinds against the left or back, you want to increase the sensitivity of that axis. Go to Configuration / Advanced / Sensorless Homing and change the X or Y in the direction described above. Go in increments of 5 when changing a value. Save settings when you find something that works.

• The manual mesh firmware works just like bi-linear but is not automated since it doesn't use the probe. To start it you do exactly the same as bi-linear. You go to Motion / Bed Leveling / Level Bed. Then use your paper to adjust all 25 points to have the same tug as the others. You can also use a feeler gauge if you want finer precision.

• It is very important when doing pid autotuning, z-offset calibration, bed leveling, e-steps changing, sensorless homing changes, it is very important to save your settings so they persist after powering down and up again later.

• There is a bug in the current Marlin we use where when you try to edit the steps for Z motor or Extruder on the LCD it does not allow you to edit properly. The values are messed up and it is next to impossible to put in proper values. It is recommended to use your PC, Octoprint, or similar setup and issues the step settings over g-code. Then save settings. If you accidentally go into the step edit for Z or the Extruder, just power down and you won't save the bad settings. If you don't have the ability to connect a PC or Octoprint to your printer, but need change your e-steps, you can do it by creating a gcode file on your computer and printing that gcode file.