Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    G-code buffer "file" overflow???

    Scheduled Pinned Locked Moved
    General Discussion
    5
    34
    1.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • daoustundefined
      daoust
      last edited by daoust

      Hi, it happen time to time on long print that the duet stop printing. The hot end and the heatbed turn down to 0 deg and the head stay at it last position. Was using sd card.

      I have 2 questions

      Is there a way to restart the print at the same position? My printer is still on and I put back the heat on the heat bed.

      What can be the cause? I take a picture of the message. It say G-code buffer "file" length overflow. Is it because I have to many file in the duet memory?

      Thank you

      20220929_170533_remastered.jpg

      Norderundefined jay_s_ukundefined 2 Replies Last reply Reply Quote 0
      • Norderundefined
        Norder @daoust
        last edited by Norder

        @daoust
        Have you adjusted the GCode-Type in your slicer ?

        In PrusaSlicer, for example, you can find this option in Printer Settings > General > GCode Type. There please RepRapFirmware.

        I think your problem might have something to do with it !?

        Unbenannt.JPG
        Sorry... German layout 😉

        DDA5X... 0.9° Stepper... Linearrails... Duet 2 Wifi... PT100 Board... Duet IR-Probe... Dyze Pro Kit up to 500°C.. etc
        Thingiverse

        daoustundefined 1 Reply Last reply Reply Quote 0
        • jay_s_ukundefined
          jay_s_uk @daoust
          last edited by

          @daoust can you grab an M122 output after that happens?

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          daoustundefined 1 Reply Last reply Reply Quote 0
          • daoustundefined
            daoust @jay_s_uk
            last edited by

            @jay_s_uk I don t know what is a m122. I have leave it open so I can try it soon

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • jay_s_ukundefined
              jay_s_uk @daoust
              last edited by

              @daoust just type M122 into the console and post the output here

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              daoustundefined 1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                Can you also share the gcode file in question?

                Z-Bot CoreXY Build | Thingiverse Profile

                daoustundefined 1 Reply Last reply Reply Quote 0
                • daoustundefined
                  daoust @jay_s_uk
                  last edited by

                  @jay_s_uk 20220930_175450.jpg

                  1 Reply Last reply Reply Quote 0
                  • daoustundefined
                    daoust @Phaedrux
                    last edited by

                    @Phaedrux the file is too big to share😲 😲

                    by the way, the g-code is marlin. sometime when it happen, I just restart the print and everything is fine

                    1 Reply Last reply Reply Quote 0
                    • daoustundefined
                      daoust @Norder
                      last edited by

                      @norder I have allways use marlin firmware, maybe that can be the problem🙄

                      but the file that fail, when reprinted with the same g-code can work fine

                      Norderundefined 1 Reply Last reply Reply Quote 0
                      • Norderundefined
                        Norder @daoust
                        last edited by

                        @daoust
                        It's happened to me before, but they weren't extremely large files.
                        The G0/G1 error I think is because the GCode is a Marlin-Type.

                        So I would switch the slicer to RepRapFirmware as the GCode-Type and slice the component again.

                        DDA5X... 0.9° Stepper... Linearrails... Duet 2 Wifi... PT100 Board... Duet IR-Probe... Dyze Pro Kit up to 500°C.. etc
                        Thingiverse

                        Norderundefined 1 Reply Last reply Reply Quote 0
                        • Norderundefined
                          Norder @Norder
                          last edited by

                          P.S.:
                          If RepRap/Sprinter is also listed in the list of RepRapFirmware, choose RepRapFirmware.
                          RepRap/Sprinter is an obsolete GCode-Type that is no longer being worked on.

                          DDA5X... 0.9° Stepper... Linearrails... Duet 2 Wifi... PT100 Board... Duet IR-Probe... Dyze Pro Kit up to 500°C.. etc
                          Thingiverse

                          1 Reply Last reply Reply Quote 0
                          • Phaedruxundefined
                            Phaedrux Moderator
                            last edited by

                            Yes definitely use RepRapFirmware flavor instead of Marlin.

                            See if you can upload the file to something like dropbox or google drive and share a link that way.

                            Can you send M122 in the gcode console and copy and paste the results here?

                            Z-Bot CoreXY Build | Thingiverse Profile

                            daoustundefined 1 Reply Last reply Reply Quote 1
                            • daoustundefined
                              daoust @Phaedrux
                              last edited by

                              @phaedrux I share a picture of my m122 in this post. for sharing the g-code, I can send it with wetransfer but I need a email. I don t know any other way.

                              jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                              • jay_s_ukundefined
                                jay_s_uk @daoust
                                last edited by

                                @daoust you're on a super old firmware so you'd best upgrade. You won't get any support for issues with 2.02

                                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                                Norderundefined 1 Reply Last reply Reply Quote 1
                                • Norderundefined
                                  Norder @jay_s_uk
                                  last edited by

                                  Upgrade from RRF2 to RRF3 !
                                  Please do not update to the latest firmware immediately, as this can cause problems.
                                  Please work through the following instructions.
                                  https://docs.duet3d.com/User_manual/RepRapFirmware/Migration_RRF2_to_RRF3

                                  Excerpt from the instructions:
                                  Note: it is not possible to upgrade a Duet WiFi, Ethernet or Maestro directly from firmware 1.x or 2.x to 3.01 or later. You must upgrade to firmware 3.0 as an intermediate step.

                                  DDA5X... 0.9° Stepper... Linearrails... Duet 2 Wifi... PT100 Board... Duet IR-Probe... Dyze Pro Kit up to 500°C.. etc
                                  Thingiverse

                                  1 Reply Last reply Reply Quote 0
                                  • Phaedruxundefined Phaedrux moved this topic from 3D Printing General Chat
                                  • daoustundefined
                                    daoust
                                    last edited by

                                    @norder I just upgrade to the new firmware by doing 3.0 first than the newer version. I redo a new configuration with the config tool while using same parameter as before.

                                    Now my z end stop is not working properlly

                                    When I try to home, the bed lift some milimeter than goes down untill colision but if I touch the Z endstop, the bed stop moving.

                                    So it look like the endstop is now inverted from N/C to N/O and vise versa. I try to install a "!" Before the zendstop. The X and Y axis work fine, only the Z axis that is not working🤔. Any I idea???

                                    Thank you

                                    dc42undefined 1 Reply Last reply Reply Quote 0
                                    • dc42undefined
                                      dc42 administrators @daoust
                                      last edited by

                                      @daoust please post your config.g and your homing files.

                                      Duet WiFi hardware designer and firmware engineer
                                      Please do not ask me for Duet support via PM or email, use the forum
                                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                                      daoustundefined 1 Reply Last reply Reply Quote 0
                                      • daoustundefined
                                        daoust @dc42
                                        last edited by

                                        @dc42 so I was able to fix my end stop problem, it was just the rotation side of my stepper motor the problem.

                                        but here I have a small tuning to do to my config file. first, it say I have a error with heater 3, 4, 5, 6, 7... they are not found

                                        second, I have setup a heated chamber, but I would like to have acces on my panel due. is there a way to enter a g-code comande to configure a heated chamber?

                                        lastly, I have trouble with the wifi connection. is it possible that the wifi modul can be defective or it will mostly be my router that are too far. sometime it work fast and other time, it wont connect.

                                        Configuration file for Duet WiFi (firmware version 3.3)
                                        ; executed by the firmware on start-up
                                        ;
                                        ; generated by RepRapFirmware Configuration Tool v3.3.13 on Sun Oct 02 2022 20:41:52 GMT-0400 (Eastern Daylight Time)

                                        ; General preferences
                                        M575 P1 S1 B57600 ; enable support for PanelDue
                                        G90 ; send absolute coordinates...
                                        M83 ; ...but relative extruder moves
                                        M550 P"createbot max" ; set printer name

                                        ; Network
                                        M552 S1 ; enable network
                                        M586 P0 S1 ; enable HTTP
                                        M586 P1 S0 ; disable FTP
                                        M586 P2 S0 ; disable Telnet

                                        ; Drives
                                        M569 P0 S1 ; physical drive 0 goes forwards
                                        M569 P1 S1 ; physical drive 1 goes forwards
                                        M569 P2 S0 ; physical drive 2 goes forwards
                                        M569 P3 S1 ; physical drive 3 goes forwards
                                        M584 X0 Y1 Z2 E3 ; set drive mapping
                                        M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
                                        M92 X80.00 Y80.00 Z640.00 E430.85 ; set steps per mm
                                        M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
                                        M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
                                        M201 X900.00 Y900.00 Z100.00 E2000.00 ; set accelerations (mm/s^2)
                                        M906 X950 Y950 Z850 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent
                                        M84 S30 ; Set idle timeout

                                        ; Axis Limits
                                        M208 X0 Y0 Z0 S1 ; set axis minima
                                        M208 X280 Y250 Z400 S0 ; set axis maxima

                                        ; Endstops
                                        M574 X1 S1 P"!xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
                                        M574 Y1 S1 P"!ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
                                        M574 Z1 S1 P"!zstop" ; configure switch-type (e.g. microswitch) endstop for low end on Z via pin zstop

                                        ;Z-Probe
                                        M558 P1 C"zprobe.in" H5 F120 T6000 ; set Z probe type to unmodulated and the dive height + speeds
                                        G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
                                        M557 X15:215 Y15:195 S20 ; define mesh grid

                                        ; Heaters
                                        M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
                                        M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
                                        M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
                                        M140 H0 ; map heated bed to heater 0
                                        M143 H0 S150 ; set temperature limit for heater 0 to 150C
                                        M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
                                        M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
                                        M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
                                        M143 H1 S350 ; set temperature limit for heater 1 to 350C
                                        M308 S2 P"e1temp" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin e1temp
                                        M950 H2 C"e1heat" T2 ; create chamber heater output on e1heat and map it to sensor 2
                                        M307 H2 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
                                        M141 H2 ; map chamber to heater 2
                                        M143 H2 S100 ; set temperature limit for heater 2 to 100C

                                        ; Fans
                                        M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
                                        M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
                                        M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
                                        M106 P1 S1 H1:2 T70 ; set fan 1 value. Thermostatic control is turned on

                                        ; Tools
                                        M563 P0 D0 H1 F0 ; define tool 0
                                        G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
                                        G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

                                        ; Custom settings are not defined

                                        ; Miscellaneous
                                        M501 ; load saved parameters from non-volatile memory
                                        M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss

                                        Phaedruxundefined 1 Reply Last reply Reply Quote 0
                                        • Phaedruxundefined
                                          Phaedrux Moderator @daoust
                                          last edited by

                                          @daoust said in G-code buffer "file" overflow???:

                                          it say I have a error with heater 3, 4, 5, 6, 7... they are not found

                                          Where do you see that? You only have 3 heaters defined. 0, 1, 2

                                          @daoust said in G-code buffer "file" overflow???:

                                          second, I have setup a heated chamber, but I would like to have acces on my panel due. is there a way to enter a g-code comande to configure a heated chamber?

                                          What firmware version is on your PanelDue? You'll likely need to update it.

                                          https://docs.duet3d.com/en/User_manual/RepRapFirmware/Updating_PanelDue#firmware-update-via-usb

                                          @daoust said in G-code buffer "file" overflow???:

                                          lastly, I have trouble with the wifi connection. is it possible that the wifi modul can be defective or it will mostly be my router that are too far. sometime it work fast and other time, it wont connect.

                                          Please send M122 in the gcode console and copy and paste the results here. Perhaps your wifi module firmware didn't get up to date? Perhaps your signal strength is poor? M122 will tell us more.

                                          Z-Bot CoreXY Build | Thingiverse Profile

                                          daoustundefined 1 Reply Last reply Reply Quote 0
                                          • daoustundefined
                                            daoust @Phaedrux
                                            last edited by

                                            @phaedrux here is the m122 for the heater and a print screen where it say that my heater 4 5 6 7 . . . Have problem

                                            Also when I activate my heated chamber, the temperature rise up to 40 deg c and the heater came in fault because the tempereture rise to slow. The chamber is big so it is normal to rise slow. How can I fix this safety? 20221010_202135.jpg

                                            20221010_202148.jpg

                                            For the panel due firmware update, I will try it this week. Thank you

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA