Which of the three version is recommended for the SV08? Eddy, Eddy Coil or Eddy Duo. I will be moving to mainline Klipper. Also is there a maximum size Emmc, would 64Gb work or is the limit 32Gb?
Thank you
I dont know of any reason as to why a larger Emmc wouldnt work. Most times size limits are due to the file system used on flash drives. In klipperOS that is ext4.fs:
The ext4 filesystem can support volumes with sizes in theory up to 64 zebibyte (ZiB) and single files with sizes up to 16 tebibytes (TiB) with the standard 4 KiB block size, and volumes with sizes up to 1 yobibyte (YiB) with 64 KiB clusters, though a limitation in the extent format makes 1 exbibyte (EiB) the practical limit.[13] The maximum file, directory, and filesystem size limits grow at least proportionately with the filesystem block size up to the maximum 64 KiB block size available on ARM and PowerPC/Power ISA CPUs.
1 Like
Thank you, thatās very helpful
I got the duo. I have it connected by USB. I thought that if at some point i want to go CANBUS then the Duo would be compatible. Price is about the same soā¦
Thank you that makes sense. appreciated 
::
Attention! Eddy Coil does not have thermal compensation and is therefore not suitable for Z-homing. The sensor can only be used if a Z-homing device is already present.
Hi does this also apply to the Eddy Duo? Can the pressure pad on the back right of the bed be used for Z homing?
Thanks
The duo requires no separate homing device, does USB and CAN and does temperature compensation, I would think this as the best choice
If only USB is on your list then the v1.0 is the budget option with all the features except CAN
Also, mainline klipper is needed. An in-depth guide how to mount it and calibrate it is made by the printasaurus : https://youtu.be/xnGhGZesipI?feature=shared
I ordered the duo, and have got my kit together for the mainline upgrade. Going to wait for the Easter break so I can attack it with a clear mind and free time to get my head around it. Iāve come from a stock Ender 5, so no experience with Klipper but I did once flash the printer to add a CR touch and filament sensor. It was challenging but I am looking forward to not needing to recompile the code every time you make a minor change to the config. That totally sucked.
Thanks for your reply.
PS Printasaurus is Awesome, very clear walk through at the perfect level for me.
Be sure to carefully follow GitHub - Rappetor/Sovol-SV08-Mainline: Getting the Sovol SV08 onto mainline Klipper procedure from their description and not an older video or something. Documentation is constantly updated on this GIT.
I will try and move one of my sv08 printers to mainline klipper soon, I needed them to finish some print jobs first 
1 Like
Seconded. Personally, I hate youtube based tutorials for code related things - a good written description is far superior. I used Rappetorās guide on my printer and had a successful migration to mainline.
And definitely go with the eddy duo - personally, Iām using the eddy-ng fork of the software (thereās a channel for it on the Sovol discord) that allows a combination of sensorless homing + a touchoff during the start sequence to nail the 0 point before bed meshing. Flawless first layers are basically a given once you go through the legwork of setting it up right.
2 Likes
Good to know (and i agree, video are tooo long), so what you did is that ? Home Ā· vvuk/eddy-ng Wiki Ā· GitHub
Are you using it in combination with GitHub - 3DPrintDemon/Demon_Klipper_Essentials_Unified: Devilishly Good Klipper Macros! ? (because i am using it and he has a configuration for eddy)
Iām a little confused now, is the eddy-ng fork move suited to the sv08 over mainline Klipper?
No! Ditching Sovolās version of klipper was literally the first thing I did with my SV08 after printing the test Benchy off the USB drive. I have never had a good experience with companies that release their own custom versions and donāt keep them up to date with mainline.
The eddy-ng code only works on mainline klipper (and on kalico, but anyone who canāt even handle moving to mainline Klipper shouldnāt even think about kalico).
Nope. Mostly stuff from the sovol discord, and my own tweaked print start macro.
Thx. I will try with the simple eddy (the ng one require to replace the hotend cover, I will do that later). I just received it today.
I tried to go Mainline Klipper on my SV08 but as soon as I started the Z Offset calibration using the pressure pad the printer started to crash and do whatever wanted to, reverted back to Sovolās version everything went back to normal immediately.
I followed the guide on github and the video mentioned above, non of it worked for me, SV08 specific features broke every time
May you share your config of eddy ng ? I tried, that works fine, except the ātapā I have always that
EDDYng: Tap failed: 5 errors, last: Tap detected too close to target z at toolhead z=-0.250
(And that is true, that should not down more) How that should trigger the stop ?
HUm, i managed to make work the Eddy NGā¦ but that I did not understood why that failing sometime / how to improve the accurate.
- I am using theses macro GitHub - 3DPrintDemon/Demon_Klipper_Essentials_Unified: Devilishly Good Klipper Macros!
- I added my specific config onto options/probe/eddy-ng.cfg and including it. I also followed the guideline to configure the eddy regular version
[mcu eddy]
serial: /dev/serial/by-id/usb-Klipper_rp2040_504450611086B81C-if00 # Change this to your own path
restart_method: command
[temperature_sensor btt_eddy_mcu]
sensor_type: temperature_mcu
sensor_mcu: eddy
min_temp: 10 # Sets the minimum tempereature for eddys tempereature sensor to operate
max_temp: 100 # Sets the maximum tempereature for eddys tempereature sensor to operate
[probe_eddy_ng btt_eddy]
sensor_type: btt_eddy
i2c_mcu: eddy
i2c_bus: i2c0f
#x_offset: -18.0
#y_offset: 6.0
x_offset: -16
y_offset: 11.5
#tap_target_z: -0.450 #Uncommented but that is for MY OWN printer (do not do that without testing without first)
[temperature_probe btt_eddy]
sensor_type: Generic 3950
sensor_pin: eddy:gpio26
horizontal_move_z: 2
calibration_position: 319,176,5
[bed_mesh]
speed: 150 #500
horizontal_move_z: 3
mesh_min: 15,18
mesh_max: 335,335
probe_count: 15,15
algorithm: bicubic
bicubic_tension: 0.5
split_delta_z: 0.0125
mesh_pps: 3,3
adaptive_margin: 5
fade_start: 1
fade_end: 10
fade_target: 0
[homing_override]
gcode:
# Move 5 up, just in case (this is our safety zhop, this needs 'set_position_z: 0' below)
G91 ; set relative positioning
G0 Z5 F1000 ; 5 up zhop
{% if not rawparams or 'Y' in rawparams %}
{action_respond_info('Homing Y')}
G28 Y
G90 ; set absolute positioning
G0 Y177.5 F6000 ; return to center
M400 ; Wait for move to finish
{% endif %}
{% if not rawparams or 'X' in rawparams %}
{action_respond_info('Homing X')}
G28 X
G90 ; set absolute positioning
G0 X177.5 F6000 ; return to center
M400 ; Wait for move to finish
{% endif %}
{% if not rawparams or 'Z' in rawparams %}
{action_respond_info('Homing Z')}
G90 ; set absolute positioning
G0 X177.5 Y177.5 F6000 ; return to center, please add your offsets manually if you want to
G28 Z
G91 ; set relative positioning
G0 Z10 F1000 ; 10mm zhop before probe
PROBE_EDDY_NG_PROBE_STATIC HOME_Z=1
G0 Z5 F1000 ; 5mm up
M400 ; Wait for move to finish
{% endif %}
G90 ; set absolute positioning
axes: xyz
set_position_z: 0 # This forces the z position to be at 0 when we start homing, so we can move the Z up before homing.
[gcode_macro SET_Z_FROM_PROBE]
gcode:
PROBE_EDDY_NG_PROBE_STATIC HOME_Z=1
- But i DID NOT activated the specifics config on Demon config file for eddy (theses config are defined for eddy regular, not for the NG one).
- Instead of that, i changed in the file
Demon_User_Files/demon_custom_expension_v1.0.1.cfg:
variable_ceal_master_enable: True
variable_pre_mesh: True
variable_post_end: True
[gcode_macro _CUSTOM_PRE_MESH] # Before your printer loads or performs any meshing processes
gcode:
PROBE_EDDY_NG_TAP
[gcode_macro _CUSTOM_POST_END] # Very last command before the PRINT_END macro finishes - if you have set a shutdown via power relay this may not have time
gcode:
PROBE_EDDY_NG_SET_TAP_OFFSET VALUE=0
With that, the good points are :
- Regular homing works very well (and that could be enought to printā¦ but that should be better with the āTAPā)
- The TAP homing, when itās works, all if really perfect. I did not tried yet a very big print but that is better than the original version + i do not have to perform any manual calibration (eventualy if i am strongly change something on the toolhead but i can unmount and remove the head without recalibrate it)
- The print start routine is soooooo fast. QGL is a formality, and bed mesh a real pleasure. I slow down also the bad pre heat (to 1min for PLA/PTEG and 2min for others).
But, sometime the TAP homing does not works. Error like EDDYng: Tap failed with Z at -0.450: Error during homing probe: Probe completed movement before triggering. If this is a tap, try lowering TARGET_Z or adjusting the THRESHOLD.
My guest are :
- A noise onto the USB cable: that is random but that can be.
- A noise related to the screws used to fix the eddy
- Bad positioning of my eddy I am using this one Sovol SV08 BTT Eddy mount for tap with locating pin by Adriano Gelatino | Download free STL model | Printables.com
- I using an usb hub to allow more USB. I powering it with a regulator defined at 5.10V. Maybe that is not perfectly mounted (i used an old USB hub and changed the wiring to use the same GND but different V+ source).
- Bad belt tension. I tried manually, that look āaboutā fine (i trust that is enought but maybe itās not).
If you have any experience / idea to share that may help