Jump to content

G-Code incompatibility


Preatorianul

Recommended Posts

Posted · G-Code incompatibility
1 hour ago, GregValiant said:

It looks like the fan should be coming on at layer 2.  If you search the gcode file is there an "M106" in there?  M106 S255 would be the cooling fan at 100%.

I have just M107 for Start G-code. M106 S0 I have just at the End G-code.

image.thumb.png.86ed15e28608c6cfede541a7b4fb19f3.png

  • Link to post
    Share on other sites

    Posted · G-Code incompatibility

    I installed a Chiron in Cura and set up cooling the way you have it and it looks to be working correctly.  Right under Layer:0 I get M106 S255.

     

    With a model loaded and your settings the way you like, use the "File | Save Project" command and post the 3mf file here.

  • Link to post
    Share on other sites

    Posted · G-Code incompatibility
    12 hours ago, GregValiant said:

    I installed a Chiron in Cura and set up cooling the way you have it and it looks to be working correctly.  Right under Layer:0 I get M106 S255.

     

    With a model loaded and your settings the way you like, use the "File | Save Project" command and post the 3mf file here.

     Is good to know that you made it and was right. Now let's see what is wrong with mine! First I suspected the hot-end wiring which failed first, but I have replace it. Now I started printing an old calibration file that I have it on the SD card and the cooling fan worked.

    AC_3cm paralelipiped.3mf

  • Link to post
    Share on other sites

    Posted (edited) · G-Code incompatibility

    image.thumb.png.fd9cb1c9be29824447b08e2a22b4d239.png

    I Have it the same.

     

    Edited by Preatorianul
  • Link to post
    Share on other sites

    Posted (edited) · G-Code incompatibility

     It's working after all. The previous test I made it printing on-line with the printer. Now I generated the G-Code and I print from the SD card and is working fine.

    20211205_124305.jpg

    Edited by Preatorianul
  • Link to post
    Share on other sites

    Posted (edited) · G-Code incompatibility

    When I opened your 3mf file I immediately sliced it with no changes and the gcode was correct with:

    ;LAYER:0

    M106 S255

    So the setting "Initial Fan Speed" = 100% did work.  I changed the setting to 50% and to 0% and the gcode was also correct with M106 S127.5 and M107 respectively.

    In that gcode snippet you posted there is:

    ;LAYER:0

    M107

    Which seems to indicate that you had Initial Fan Speed set to 0% for that slice?

     

    Try installing another instance of your printer with a different name and try slicing with the new instance.  It's possible there is a glitch in your installation of Cura, but only affecting a single setting like that is odd.

    What version of Cura are you using?

    I am attaching a 3mf file of your model with some altered cooling settings.  When I slice that file the gcode has 17 lines with M106 as the fan speed bounces up and down due to Minimum Layer Time.

     

    GV_3cmparalelipiped.3mf

    Edited by GregValiant
  • Link to post
    Share on other sites

    Posted · G-Code incompatibility

     Thank you very much for your support! I previously came to the idea that Chiron is not working well with some detail settings of Cura, like the variable layer thickness. Maybe is the case now. My previous setting was to start with the regular fan speed 0.

  • Link to post
    Share on other sites

    Posted · G-Code incompatibility

    If there is no M106 in the file then the problem is before the printer.  Open a text editor program and paste the snippet below into a text file, then save it as a gcode and print it.   It will exercise the fan at 20 second intervals.  If the fan responds correctly then the problem is elsewhere.

     

    M106 S255  ;fan on full

    M117 FAN 100%  ;message to the LCD

    G4 S10  ;20 second wait

    M106 S0  ;fan off

    M117 FAN OFF  ; message to the LCD

    G4 S10  ;20 second wait

    M106 S127 ;fan at 50%

    M117 FAN 50%  ;message to the LCD

    G4 S10 ;20 second wait

    M106 S0

     

    Regarding the layer movement - Gcode tells the printer where to go and what to do.  The variable layer thickness (like with Adaptive Layers) is no different than any other movement command.  If your layer height is .2 then the Z will be told to move .2.  If the command is a different layer height then that gcode command might tell the printer to move the Z 0.1.  The gcode might look like this...

    ;LAYER:0

    G0 X0 Y0 Z0.2

    ;lots more code

    ;LAYER:1

    G0 X0 Y0 Z0.3

    ;lots more code

    ;LAYER:2

    G0 X0 Y0 Z0.5

    In that example - the first layer is .2 high, the second layer is .1 high, and the third layer is back to being .2 high.

    The printer should just go where it's told to go.

    • 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

      • 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
      • Ultimaker Cura 5.6 stable released
        Cura now supports Method series printers!
         
        A year after the merger of Ultimaker and MakerBotQQ, we have unlocked the ability for users of our Method series printers to slice files using UltiMaker Cura. As of this release, users can find profiles for our Method and Method XL printers, as well as material profiles for ABS-R, ABS-CF, and RapidRinse. Meaning it’s now possible to use either Cura or the existing cloud-slicing software CloudPrint when printing with these printers or materials
        • 48 replies
    ×
    ×
    • Create New...