Skip to main content

Comments

4 comments

  • Matthew Fiedler

    The file name limitations are controlled by the firmware and not the Viki itself. The file name should not contain special characters like "( [ &#$" and it should end in ".gcode". Numbers and letters are best for the filenames. 

    0
  • Carlos Pozo

    so it can be anything as long as it follows the no special character rules?

    0
  • Matthew Fiedler

    The filename should:

    1) follow the "No special characters" rule 

    2) end with ".gcode"

     

    Example of good filename:

    PrintBIG.gcode

    Iwant2PrintBiG.gcode

    thislongfilenameisOK.gcode

     

    Example of bad filename:

    (123)wontwork.gcode

    badfile.txt

    badC$ar.gcode

    0
  • Jeric Bautista

    Hey Carlos,

    Also note that the Viki only shows a limited number of characters in the filename. e.g. if your file is called "thislongfilenameisOK.gocde" you may only see it as "thislong~" on the Viki screen, with the ending truncated. 

    That being said if you have multiple files on one SD card it is good practice to name the files fairly different names. If you have multiple versions of the same file, perhaps place the revision at the beginning instead of the end: e.g. "02PrintBIG.gcode" instead of "PrintBIG02.gcode"

    0

Please sign in to leave a comment.