Jump to content

Ultimaker 3 Custom Gcode Issue


BairdB

Recommended Posts

Posted · Ultimaker 3 Custom Gcode Issue

Hello Forum!

 

I have an Ultimaker 3 and I want to write custom Gcode for the printer to run for vibration testing. I tried to write my own code in a text editor, put that on a flashdrive and then tried printing it on my Ultimaker 3 over USB. I renamed the file to have a .gcode.gz extension because the printer does not recognize the file if I leave it as .txt. However, when I try to run the file on the printer by selecting print, it does not do anything. I have read this post about the Griffin Gcode commands and I am confused how to write my own gcode files for my printer to execute. I think my file might need a header as explained in the post I linked. But I do not know how to implement this, or if the file is a binary or a text.

 

If anyone has any experience writing their own code for the Ultimaker 3 I would appreciate you input.

 

I attached an example of the kind of code I want to run on the printer.

 

Thanks!

 

Baird B.

 

VibrationIsolationTestText.zip

  • Link to post
    Share on other sites

    Posted (edited) · Ultimaker 3 Custom Gcode Issue

    ok, let's see...

     

    • Like any other Ultimaker printer the UM3 can read text files with the file extension ".gcode"
    • In addition the UM3 is able to directly use gcode files that are compressed with gzip, those will have the file extension ".gcode.gz". Cura generates such files by default if you print over network, but it's not mandatory
    • But: the .gcode file has to begin with the mandatory Griffin-"Header" - basically a few lines with specific comments that describe the print job.
    • The easiest way to get such a header is to prepare a similar print job in Cura, slice and save the gcode file to disk.
      Obviously you don't want to heat anything up - so set all temperatures to zero.
      Take a look at the header lines in the file, it's not very hard to interpret. Afterwards replace everything below the header lines with your own G-Code commands.

     

     

    Further:

    • I'm not sure, if the UM3 supports the G28 command (i think it does not?) - it's possible that it will be ignored or it will work different from what you expect. The UM3 has its own start- and end- procedures builtin that are performed for every print. There's no easy way around it.
    • You should add a feedrate (parameter "F") prior or within the first move commands, to tell the printer how fast it should move.

     

    Example:

     

    ;START_OF_HEADER
    ;HEADER_VERSION:0.1
    ;FLAVOR:Griffin
    ;GENERATOR.NAME:Cura_SteamEngine
    ;GENERATOR.VERSION:4.11.0
    ;GENERATOR.BUILD_DATE:2022-02-14
    ;TARGET_MACHINE.NAME:Ultimaker 3
    ;EXTRUDER_TRAIN.0.INITIAL_TEMPERATURE:0
    ;EXTRUDER_TRAIN.0.MATERIAL.VOLUME_USED:3029
    ;EXTRUDER_TRAIN.0.MATERIAL.GUID:506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9
    ;EXTRUDER_TRAIN.0.NOZZLE.DIAMETER:0.4
    ;EXTRUDER_TRAIN.0.NOZZLE.NAME:AA 0.4
    ;EXTRUDER_TRAIN.1.INITIAL_TEMPERATURE:0
    ;EXTRUDER_TRAIN.1.MATERIAL.VOLUME_USED:2515
    ;EXTRUDER_TRAIN.1.MATERIAL.GUID:506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9
    ;EXTRUDER_TRAIN.1.NOZZLE.DIAMETER:0.4
    ;EXTRUDER_TRAIN.1.NOZZLE.NAME:AA 0.4
    ;BUILD_PLATE.TYPE:glass
    ;BUILD_PLATE.INITIAL_TEMPERATURE:0
    ;PRINT.TIME:4321
    ;PRINT.GROUPS:1
    ;PRINT.SIZE.MIN.X:9
    ;PRINT.SIZE.MIN.Y:6
    ;PRINT.SIZE.MIN.Z:0.27
    ;PRINT.SIZE.MAX.X:213
    ;PRINT.SIZE.MAX.Y:214.402
    ;PRINT.SIZE.MAX.Z:32.07
    ;END_OF_HEADER
    ;Generated with Cura_SteamEngine 4.11.0
    
    G0 Z30 F1200
    G0 X40 Y40 F6000
    G0 X50 Y50
    G0 X40 Y40
    G0 X50 Y50
    ...

     

    Edited by tinkergnome
    • Like 1
    Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 18 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...