User Tools

Site Tools


gcode_storage

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
gcode_storage [2024/10/18 14:04] – [GCode storage] tortegcode_storage [2025/01/21 12:27] (current) torte
Line 1: Line 1:
-===== Sovol KlipperScreen ===== +{{page>redirect#this_wiki_has_moved}} 
-==== GCode storage ====+https://torte71.github.io/InsideSovolKlipperScreen/gcode_storage.html 
 +{{page>redirect#section}} 
 +---- 
 + 
 +===== Sovol KlipperScreen (Makerbase MKS KLIPAD50) ===== 
 +==== Expand G-Code storage space ==== 
 + 
 +Experienced Linux users: Scroll down to [[#for_the_linux_gurus|For the linux gurus]] for a short sum-up what is required. 
 + 
 +----
  
 Sovol's KlipperScreen uses an 8GB emmc card for storage, of which about 7GB are used by the system. Sovol's KlipperScreen uses an 8GB emmc card for storage, of which about 7GB are used by the system.
Line 131: Line 140:
   * All other usb-drives will be used by the automounter as before, i.e. they will be mounted as a subdirectories "USB" under the "gcodes" directory   * All other usb-drives will be used by the automounter as before, i.e. they will be mounted as a subdirectories "USB" under the "gcodes" directory
   * Only remove the usb-drive after shutting down the device   * Only remove the usb-drive after shutting down the device
-  * If the usb-drive was not plugged in during boot, you will either have to mount it manually - or just reboot the device with the usb-drive plugged in.+  * If the usb-drive was not plugged in during boot, you will either have to mount it manually (''sudo mount /home/mks/printer_data/gcodes''- or just reboot the device with the usb-drive plugged in. 
 +  * By default, you cannot access the files on the usb-drive by Windows. But there are several free programs that allow it (e.g. SysInternals LinuxReader or Ext2explore), just search the web for "windows ext4"
 + 
 + 
 +=== For the linux gurus === 
 +  * Set the partition type to "83 linux"
 +  * Format the partition to "ext", e.g. ext4 (a filesystem with linux access rights is required). 
 +  * Make sure to unmount after each step (automounter is still active) 
 +  * In ''/etc/fstab'' use the parameters ''nofail,x-systemd.device-timeout=9'' to allow booting if that drive is not inserted 
 +  * Use the partitions UUID in ''/etc/fstab'', this makes the automounter ignore this drive 
 +  * Make the filesystem writable for users (''chown -R mks:mks <YOUR_MOUNTPOINT>''). 
  
 +=== A last tip ===
 +When there is no usb-drive inserted, create a directory called "_NO_USB_MOUNTED_" (or whatever name you like) in the gcode directory. If the usb-drive is not inserted or broken, this directory will be visible and you know, that gcode files will not end up on the usb-drive, but on the internal file system.
gcode_storage.1729253066.txt.gz · Last modified: 2024/10/18 14:04 by torte