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

    rehome.g not found

    Scheduled Pinned Locked Moved Unsolved
    Duet Hardware and wiring
    4
    61
    2.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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      Can you post some additional information?

      Results of M122, config.g, homing files, start.g, bed.g any other files that may get called in the chain between startup and starting a print.

      Z-Bot CoreXY Build | Thingiverse Profile

      1 Reply Last reply Reply Quote 0
      • Marco Bonaundefined
        Marco Bona
        last edited by

        @Phaedrux ,I'm not on the printer now. I'll get you the files tomorrow evening. Do you need M122 results after the error appears?

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

          @Marco-Bona said in rehome.g not found:

          Do you need M122 results after the error appears?

          Ideally.

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • Marco Bonaundefined
            Marco Bona
            last edited by

            @Phaedrux, ecco i file:
            -M122 results after error appears:

            m122
            === Diagnostics ===
            RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode)
            Board ID: 08DJM-956L2-G43S4-6JKF0-3S86T-9A5YD
            Used output buffers: 1 of 40 (15 max)
            === RTOS ===
            Static ram: 154604
            Dynamic ram: 164528 of which 28 recycled
            Exception stack ram used: 520
            Never used ram: 73536
            Tasks: NETWORK(ready,1968) HEAT(blocked,1188) CanReceiv(suspended,3424) CanSender(suspended,1432) CanClock(blocked,1436) TMC(blocked,68) MAIN(running,4952) IDLE(ready,76)
            Owned mutexes:
            === Platform ===
            Last reset 00:02:21 ago, cause: power up
            Last software reset at 2020-09-11 16:40, reason: User, spinning module LinuxInterface, available RAM 73508 bytes (slot 1)
            Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
            Error status: 0
            MCU temperature: min 23.0, current 28.1, max 28.2
            Supply voltage: min 23.9, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
            12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
            Driver 0: ok, reads 29500, writes 26 timeouts 0, SG min/max 0/1023
            Driver 1: ok, reads 29500, writes 26 timeouts 0, SG min/max 0/1023
            Driver 2: standstill, reads 29500, writes 26 timeouts 0, SG min/max 0/1023
            Driver 3: standstill, reads 29496, writes 31 timeouts 0, SG min/max 0/1023
            Driver 4: standstill, reads 29511, writes 17 timeouts 0, SG min/max 0/0
            Driver 5: standstill, reads 29511, writes 17 timeouts 0, SG min/max 0/0
            Date/time: 2020-09-11 16:43:03
            Slowest loop: 7.11ms; fastest: 0.13ms
            === Storage ===
            Free file entries: 10
            SD card 0 not detected, interface speed: 37.5MBytes/sec
            SD card longest read time 0.0ms, write time 0.0ms, max retries 0
            === Move ===
            Hiccups: 0(0), FreeDm: 375, MinFreeDm: 372, MaxWait: 43407ms
            Bed compensation in use: none, comp offset 0.000
            === MainDDARing ===
            Scheduled moves: 30, completed moves: 30, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
            === AuxDDARing ===
            Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0  CDDA state: -1
            === Heat ===
            Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 3 -1 -1 -1
            === GCodes ===
            Segments left: 0
            Movement lock held by File
            HTTP* is ready with "M122" in state(s) 0
            Telnet is idle in state(s) 0
            File* is idle in state(s) 43 0 0, running macro
            USB is idle in state(s) 0
            Aux is idle in state(s) 0
            Trigger* is idle in state(s) 0
            Queue is idle in state(s) 0
            LCD is idle in state(s) 0
            SBC is idle in state(s) 0
            Daemon* is idle in state(s) 0 0, running macro
            Aux2 is idle in state(s) 0
            Autopause* is idle in state(s) 0
            Code queue is empty.
            === Network ===
            Slowest loop: 1.28ms; fastest: 0.01ms
            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
            HTTP sessions: 0 of 8
            - Ethernet -
            State: disabled
            Error counts: 0 0 0 0 0
            Socket states: 0 0 0 0 0 0 0 0
            === CAN ===
            Messages sent 547, longest wait 2ms for type 6011
            === Linux interface ===
            State: 0, failed transfers: 0
            Last transfer: 18ms ago
            RX/TX seq numbers: 3923/3924
            SPI underruns 0, overruns 0
            Number of disconnects: 0
            Buffer RX/TX: 120/192-0
            === Duet Control Server ===
            Duet Control Server v3.1.1
            File:
            Buffered code: G30 P1 X140 Y0 Z-99999 S2 ; right lead screw
            Buffered code: M402 ; retract the Z probe
            Buffered code: G29 ; probe the bed and enable compensation
            ==> 112 bytes
            Executing macro bed.g, started by G32
            > Next stack level
            Executing macro start.g, started by system
            Suspended code: G1 Z10 F800
            Suspended code: G1 X0 Y0 F8000 ;go to the center of bed
            Suspended code: G30 X0 Y0 S-2 ;probe current position and ajust Z offset
            Suspended code: G1 Z40 F1000 ;go to Z40
            Suspended code: M584 P5
            Suspended code: M98 P"homev.g"
            Suspended code: M584 P3
            Suspended code: G1 X-137 Y120 F8000 ;go to X-137 Y160
            Suspended code: ;M42 P6 S50
            Suspended code: G4 S1
            > Next stack level
            Suspended code: T0
            Suspended code: M82 ;absolute extrusion mode
            Suspended code: ;Sliced at: Wed 09-09-2020 18:17:10
            Suspended code: M82 ;absolute extrusion mode
            Suspended code: M104 T0 S175
            Suspended code: M190 S50
            Suspended code: M109 S205
            Suspended code: M82 ;absolute extrusion mode
            Suspended code: T0
            Suspended code: G21
            Suspended code: G90
            Suspended code: G92 E0
            Suspended code: G1 X-50 Z2.5 E20 F1500
            Suspended code: G92 E0
            Suspended code: G1 X50 Z0.15 F1000
            Suspended code: M82 ;absolute extrusion mode
            Suspended code: M117 P"rinting..."
            Suspended code: ;
            Suspended code: M82 ;absolute extrusion mode
            Suspended code: ;T0                             ;switch to extruder 1
            Suspended code: ;G92 E0                      ;reset extruder distance
            Suspended code: ;G1 F2000 E93           ;load filament
            Suspended code: ;G92 E0                      ;reset extruder distance
            Suspended code: ;M104 S205
            Suspended code: ;
            Suspended code: M83 ;relative extrusion mode
            Suspended code: M83 ;relative extrusion mode
            Suspended code: G10
            Suspended code: ;LAYER_COUNT:96
            Suspended code: G92 E0
            Suspended code: ;LAYER:0
            Suspended code: M107
            Daemon:
            Finishing macro daemon.g, started by system
            > Next stack level
            Code buffer space: 3904
            Configured SPI speed: 8000000 Hz
            Full transfers per second: 23.89
            File /opt/dsf/sd/gcodes/White_minnow_rev1.gcode is selected, processing
            

            -Varius file:start.g rehome.g probe.g homeall.g customconfig.g config-override.g config.g bed.g
            I think there should be everything.
            Thank you

            1 Reply Last reply Reply Quote 1
            • Marco Bonaundefined
              Marco Bona
              last edited by

              @Phaedrux, after upgrading to 3.2 the problem persists.
              I found that the error (Warning: Macro file rehome.g not found) is also displayed when I launch the macro with M98 P "rehome.g".
              Have you had the opportunity to verify?

              1 Reply Last reply Reply Quote 0
              • Marco Bonaundefined
                Marco Bona
                last edited by

                @Phaedrux, i found the problem. The file name had a space after the .g file extension. Sorry but it wasn't easy to see.
                Eliminating the space works correctly.
                It remains to be understood why when I print, motorss continue to stall while if I start "start.g" from the console machine works correctly.
                I look forward to some help from you if possible.
                Thank you

                droftartsundefined Phaedruxundefined 2 Replies Last reply Reply Quote 0
                • droftartsundefined
                  droftarts administrators @Marco Bona
                  last edited by

                  @Marco-Bona This is the start of the gcode you posted earlier:

                  ;FLAVOR:RepRap
                  ;TIME:1692
                  ;Filament used: 1.00837m, 0m
                  ;Layer height: 0.15
                  ;MINX:-9.255
                  ;MINY:-35.116
                  ;MINZ:0.15
                  ;MAXX:9.259
                  ;MAXY:34.982
                  ;MAXZ:14.4
                  ;POSTPROCESSED
                  ;Generated with Cura_SteamEngine mb-master-20200822
                  T0
                  M82 ;absolute extrusion mode
                  ;Sliced at: Sun 06-09-2020 12:09:56
                  M82 ;absolute extrusion mode
                  M104 T0 S175
                  M190 S50
                  M109 S205
                  M82 ;absolute extrusion mode
                  T0
                  G21
                  G90
                  G92 E0
                  G1 X-50 Z2.5 E20 F1500
                  G92 E0
                  G1 X50  Z0.15 F1000
                  M82 ;absolute extrusion mode
                  M117 Printing...
                  ;
                  M82 ;absolute extrusion mode
                  ;T0                             ;switch to extruder 1
                  ;G92 E0                      ;reset extruder distance
                  ;G1 F2000 E93           ;load filament
                  ;G92 E0                      ;reset extruder distance
                  ;M104 S205
                  ;
                  
                  M83 ;relative extrusion mode
                  M83 ;relative extrusion mode
                  G10
                  ;LAYER_COUNT:96
                  G92 E0
                  ;LAYER:0
                  M107
                  M204 T1000
                  M566 X600 Y600
                  G0 F2400 X6.196 Y0.892 Z0.15
                  M204 P500
                  ;TYPE:SKIRT
                  G11
                  G1 F2100 X6.391 Y3.65 E0.07207
                  G1 X6.657 Y6.33 E0.0702
                  G1 X7.007 Y9.063 E0.07182
                  G1 X7.427 Y11.74 E0.07064
                  G1 X7.926 Y14.423 E0.07114
                  

                  It has these lines:

                  M204 T1000
                  M566 X600 Y600
                  ...
                  M204 P500
                  

                  M204 is setting acceleration for travel moves to 1000mm/s^2 and printing moves to 500mm/s^2, and M566 sets jerk for X and Y. Are these correct values?

                  Ian

                  Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

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

                    @Marco-Bona said in rehome.g not found:

                    It remains to be understood why when I print, motorss continue to stall while if I start "start.g" from the console machine works correctly.

                    Sorry can you explain that again?

                    When you start a print, start.g will get called automatically.

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • Marco Bonaundefined
                      Marco Bona
                      last edited by

                      @droftarts, I think they are correct, I usually use those parameters without problems, do they seem excessive to you?
                      Sorry, but start.g comes before those lines, always takes the first values it finds in gcode file?

                      @Phaedrux, exactly, start.g is automatically called up at the start of printing.

                      I explain the problem (setting M915 S3):

                      • if I start a print during the execution of start.g, X and Y motors stall continuously (then I suspend print because it does not probe bed correctly)
                        -if I start "start.g" from the DWC console with M98 "start.g", machine works perfectly.
                        I think isn't related to the sensitivity of the stall detection otherwise I think I should have same problem in both cases.
                      Phaedruxundefined 1 Reply Last reply Reply Quote 0
                      • Phaedruxundefined
                        Phaedrux Moderator @Marco Bona
                        last edited by

                        @Marco-Bona said in rehome.g not found:

                        if I start a print during the execution of start.g,

                        Again, this doesn't make sense. When you start a print, start.g will be executed. Why would you start a print while start.g is executing?

                        Z-Bot CoreXY Build | Thingiverse Profile

                        1 Reply Last reply Reply Quote 0
                        • Marco Bonaundefined
                          Marco Bona
                          last edited by

                          @Phaedrux , They are 2 separate operations. I'm saying that if I start printing the machine behaves in one way while if I start only start.g with the print canceled the printer behaves in another way. I don't repeat start.g while the machine is paused. Clear?
                          I think it takes some value when starting the program which creates some errors.

                          droftartsundefined 2 Replies Last reply Reply Quote 0
                          • droftartsundefined
                            droftarts administrators @Marco Bona
                            last edited by

                            @Marco-Bona This is the start.g you posted earlier in the thread.

                            G4 S1 
                            M117 Preparing            ;write Preparing
                            G4 S1                     ;delay 1 seconds
                            M280 P0 S160                  ; Send PWM channel 0 the s160 (angle) command
                            M84 V;
                            ; If the printer hasn't been homed, home it
                            if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed
                              G28
                            
                            M42 P6 S40
                            G21                       ;metric values
                            G90                       ;absolute positioning
                            M107                      ;start with the fan off
                            G1 X0 Y0 F10000            ;
                            G1 Z20 F1000               ;
                            M98 P"probe.g"            ;
                            T2 P0                     ;
                            G1 R2 X0 Y0 Z0 F5000      ; 
                            G32                       ;
                            G1 Z10 F800               ;
                            G1 X0 Y0 F8000            ;go to the center of bed
                            G30 X0 Y0 S-2             ;probe current position and ajust Z offset
                            G1 Z40 F1000              ;go to Z40
                            M584 P5
                            M98 P"homev.g"
                            M584 P3
                            G1 X-137 Y120 F8000      ;go to X-137 Y160
                            ;M42 P6 S50
                            G4 S1
                            

                            As you have a start.g, it runs first when a print is run. If you run start.g yourself (with M98 P"start.g") then start a print, it will run start.g again. So possibly running start.g once causes an issue, but twice fixes it. I can't see anything obvious, though start.g seems largely related to homing the V axis, and you haven't linked homev.g. Please post that too.

                            Ian

                            Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

                            Phaedruxundefined 1 Reply Last reply Reply Quote 0
                            • droftartsundefined
                              droftarts administrators @Marco Bona
                              last edited by

                              @Marco-Bona Also, in config.g I noticed:

                              M350 X16 Y16 Z16 W16 16 V16 E32:32 I1 ; configure microstepping with interpolation

                              There needs to be a 'U' before the '16', eg:

                              M350 X16 Y16 Z16 W16 U16 V16 E32:32 I1                             ; configure microstepping with interpolation
                              

                              Ian

                              Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

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

                                What happens if you step through the start.g manually command by command?

                                You say after a print is canceled. What do you have in pause.g cancel.g and stop.g?

                                What else do you have in your slicer start gcode?

                                Z-Bot CoreXY Build | Thingiverse Profile

                                Phaedruxundefined 2 Replies Last reply Reply Quote 0
                                • Marco Bonaundefined
                                  Marco Bona @droftarts
                                  last edited by

                                  @droftarts said in rehome.g not found:

                                  @Marco-Bona Also, in config.g I noticed:

                                  M350 X16 Y16 Z16 W16 16 V16 E32:32 I1 ; configure microstepping with interpolation

                                  There needs to be a 'U' before the '16', eg:

                                  M350 X16 Y16 Z16 W16 U16 V16 E32:32 I1                             ; configure microstepping with interpolation
                                  

                                  Ian

                                  fantastic, correct immediately.

                                  @Phaedrux , @droftarts, sorry but I can't be clear, I'm saying that stall warning occurs only and exclusively when a print is started, if I turn on the printer and execute M98 P "start.g", machine executes the command correctly, I can repeat command at infinity that will always work.
                                  Instead, if I start any printout, stall warning continues to appear.
                                  Again, I assume it is something that conflicts with Cura, but I don't understand what it could be.
                                  If necessary I can post a video.
                                  I am attaching the files you asked me, i am realizing that cancel.g is missing, is that a problem?
                                  homev.g pause.g stop.g

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

                                    @Phaedrux said in rehome.g not found:

                                    What else do you have in your slicer start gcode?

                                    Can you post a sample gcode?

                                    Z-Bot CoreXY Build | Thingiverse Profile

                                    1 Reply Last reply Reply Quote 0
                                    • Marco Bonaundefined
                                      Marco Bona
                                      last edited by

                                      @Phaedrux ,
                                      White_minnow_rev1.gcode

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

                                        @droftarts said in rehome.g not found:

                                        M84 V;

                                        I think it has something to do with homing V and the high steps per mm.

                                        M92 U37.67 V5245.9

                                        What is the V axis?

                                        The start.g turns off the V motor and then homes all axis if an axis isn't homed, so it runs G28. Then you call the probe. and then below again it calls homev with a M98 instead of a G28 V and then rehides the axis.

                                        Then in your slicer end gcode you have M98 P"end.g". What is in end.g?

                                        You don't have a cancel.g so when you cancel a print it's calling stop.g, or it should anyway.

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        1 Reply Last reply Reply Quote 0
                                        • Marco Bonaundefined
                                          Marco Bona
                                          last edited by

                                          @Phaedrux, V axis is a small motor that raises the second tool when not in use.
                                          It turns off the V motor because if it stays on it causes me disturbances during probing.
                                          M98 P "homev.g" and G28 V should do the same thing.

                                          end.g

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

                                            Minor point, but you could move the contents of stop.g into cancel.g, then move end.g into stop.g, and then change the slicer end gcode to M0 instead of M98 PEnd.g. Then all files would be fulfilling their original intentions.

                                            In start.g you have G1 R2 X0 Y0 Z0 F5000 What does this do?

                                            Can you send M98 P"Config.g" and post the results?
                                            Can you send M584, M350, and M92 and M906 to see if the resulting settings are what you expect them to be?

                                            Z-Bot CoreXY Build | Thingiverse Profile

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