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

G32 ERROR

Scheduled Pinned Locked Moved
Duet Hardware and wiring
7
108
5.1k
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.
  • undefined
    moe.adams9093
    last edited by 29 Jan 2021, 16:32

    No I will do that tonight when I get back home and do some recrackin.

    1 Reply Last reply Reply Quote 0
    • undefined
      moe.adams9093 @Phaedrux
      last edited by 29 Jan 2021, 16:37

      @Phaedrux man your sharp yes I think thats the problem. I will try it tonight because when I homed only that axis was moving and the rest wasn't moving at all. I thought when I combine all of them they should automatically be the same type. Thanks

      1 Reply Last reply Reply Quote 0
      • undefined
        moe.adams9093
        last edited by 31 Jan 2021, 18:33

        So I went ahead and did combine all of my endstops on a single line in this order

        M574 Z2 S1 p"!exp.e2stop+!exp.e3stop+!exp.e5stop+!exp.e6stop";
        

        it crashed my firmware so I had to do a hard reset and erase firmware and reupload new firmware but this time I did install 3.2. and also I did try just one endstop
        M574 Z2 S1 p"!exp.e2stop . ti did ignore the bed to go down to 500 it went to -500.

        undefined 1 Reply Last reply 31 Jan 2021, 19:22 Reply Quote 0
        • undefined
          Veti
          last edited by 31 Jan 2021, 18:44

          @moe-adams9093 said in G32 ERROR:

          M574 Z2 S1 p

          dunno if it matter but use a capital P

          1 Reply Last reply Reply Quote 0
          • undefined
            moe.adams9093
            last edited by 31 Jan 2021, 19:00

            I tried CAP P still doing the same thing

            1 Reply Last reply Reply Quote 0
            • undefined
              Veti @moe.adams9093
              last edited by 31 Jan 2021, 19:22

              @moe-adams9093 said in G32 ERROR:

              it crashed my firmware

              please post a M122 after the crash

              1 Reply Last reply Reply Quote 0
              • undefined
                moe.adams9093
                last edited by 31 Jan 2021, 20:14

                its to late to post M112 because I already fixed this issue. now Im dealing with homing-all problem it just not working. I don't know if the duet can allow to use EndStops on max and Zprob On MIN

                undefined 1 Reply Last reply 31 Jan 2021, 20:52 Reply Quote 0
                • undefined
                  fcwilt @moe.adams9093
                  last edited by 31 Jan 2021, 20:52

                  @moe-adams9093 said in G32 ERROR:

                  its to late to post M112 because I already fixed this issue. now Im dealing with homing-all problem it just not working. I don't know if the duet can allow to use EndStops on max and Zprob On MIN

                  Yes it can - just need to get the settings right.

                  Is homing using the Z end stop sensors working?

                  Frederick

                  Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                  1 Reply Last reply Reply Quote 0
                  • undefined
                    moe.adams9093
                    last edited by 31 Jan 2021, 20:57

                    so now I was able to get one end stop to work but when press the end-stop all 4 z motors stop not individually.

                    1 Reply Last reply Reply Quote 0
                    • undefined
                      moe.adams9093
                      last edited by 31 Jan 2021, 21:03

                      @moe-adams9093 said in G32 ERROR:
                      when I write this code and hit save and restart the board Deg light will flash red and the bord is not reachable at this stage so I had to manually erase the firmware and reupload all files again

                      M574 Z2 S1 P"!exp.e2stop+!exp.e3stop+!exp.e5stop+!exp.e6stop";
                      
                      1 Reply Last reply Reply Quote 0
                      • undefined
                        moe.adams9093
                        last edited by 31 Jan 2021, 21:28

                        M574 Z2 S1 P"!duex.e2stop+!duex.e3stop+!duex.e5stop+!duex.e6stop";

                        this line of Code it did work but when I press any of the end-stop all 4 Z motors Stop not individually

                        undefined 1 Reply Last reply 31 Jan 2021, 22:35 Reply Quote 0
                        • undefined
                          fcwilt @moe.adams9093
                          last edited by 31 Jan 2021, 22:35

                          @moe-adams9093 said in G32 ERROR:

                          M574 Z2 S1 P"!duex.e2stop+!duex.e3stop+!duex.e5stop+!duex.e6stop";

                          this line of Code it did work but when I press any of the end-stop all 4 Z motors Stop not individually

                          I have no idea why you should have had to erase the firmware - that makes no sense at all.

                          In any case since you had to upload all the files again but post config.g and homeall.g using the </> tag to be sure we are looking at the most recent.

                          Frederick

                          Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                          1 Reply Last reply Reply Quote 0
                          • undefined
                            Phaedrux Moderator
                            last edited by 1 Feb 2021, 03:43

                            Can you please send M122 and M98 P"config.g" and post the results?

                            We are assuming you are on RRF3 but I don't think we've actually checked yet.

                            @moe-adams9093 said in G32 ERROR:

                            I don't know if the duet can allow to use EndStops on max and Zprob On MIN

                            It certainly can. The endstops are configured with M574 and called into action with a G1 H1 Z move, and the probe is configured with M558/G31 and called into action with G30. So as long as both are configured, you can choose which to use by either using a G1 H1 Z move or a G30/G29.

                            Z-Bot CoreXY Build | Thingiverse Profile

                            undefined 1 Reply Last reply 1 Feb 2021, 06:18 Reply Quote 0
                            • undefined
                              moe.adams9093 @Phaedrux
                              last edited by 1 Feb 2021, 06:18

                              @Phaedrux Ok so after long hours of troubleshooting and looking on duet documentation and also at duet form to find someone had the same issue. so at first when I added this code line to my config.g

                              M574 Z2 S1 P"!duex.e2stop+!duex.e3stop+!duex.e5stop+!duex.e6stop";

                              the moment when I hit save and restart the system never came back online my Degnostic light on the DuetEthernet Board was flashing red. at that stage, I went and connected via USB to enable M552S1 but my Yat Couldn't find the duet so I went ahead and jumped the 2 erase headers and reinstall the firmware everything came back as it supposed I went back a gain and added same code and it worked fine after that I'm not sure why the board did crash. so now this is my latest configuration files

                              ; Configuration file for Duet WiFi (firmware version 3)
                              ; executed by the firmware on start-up
                              ;
                              ; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Oct 13 2020 21:14:55 GMT-0500 (Central Daylight Time)
                              ; General preferences
                              G90 ; send absolute coordinates...
                              M83 ; ...but relative extruder moves
                              M550 P"DIVINCI-3D (MP4560)" ; set printer name
                              M669 K1 ; select CoreXY mode
                              ; Network
                              M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
                              M586 P0 S1 ; enable HTTP
                              M586 P1 S0 ; disable FTP
                              M586 P2 S0 ; disable Telnet
                              ; Drives
                              M569 P10 R1 T2:2:2:2 S1 ; physical drive 0 goes forwards
                              M569 P11 R1 T2:2:2:2 S1 ; physical drive 1 goes forwards
                              M569 P3 S1 ; physical drive 3 goes forwards
                              M569 P4 S1 ; physical drive 4 goes forwards
                              M569 P5 S1 ; physical drive 5 goes Backwards
                              M569 P6 S1 ; physical drive 6 goes Backwards
                              M569 P8 S0 ; physical drive 7 goes Backwards
                              M569 P9 S0 ; physical drive 9 goes backwards
                              M584 X10 Y11 Z5:6:8:9 E3:4 ; set drive mapping
                              M671 X5.0:455.0:455.0:5.0 Y25.0:25.0:455.0:455.0 S6 ; ZBelts Near Locations
                              M350 X16 Y16 Z16 E16:16 I1 ; configure microstepping with interpolation
                              M92 X40.00 Y40.00 Z410.00 E415.00:415.00 ; set steps per mm
                              M566 X900.00 Y900.00 Z12.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
                              M203 X6000.00 Y6000.00 Z400 E1200.00:1200.00 ; set maximum speeds (mm/min)
                              M201 X500.00 Y500.00 Z40.00 E250.00:250.00 ; set accelerations (mm/s^2)
                              M906 X1800 Y1800 Z1000 E500:500 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 X460 Y460 Z460 S0 ; set axis maxima
                              M574 X1 S1 P"!xstop" ; configure active-high endstop for low end on X via pin !xstop
                              M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin !ystop
                              M574 Z1 S2 ; configure Z-probe endstop for low end on Z
                              M574 Z2 S1 P"!exp.e2stop+!exp.e3stop+!exp.e5stop+!exp.e6stop" ; configure Z-probe endstop for low end on Z
                              ; Z-Probe
                              M558 P1 C"zprobe.in" H25 F600 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 X20:440 Y20:440 S20 ; define mesh grid
                              ; Heaters
                              M308 S0 P"bedtemp" Y"thermistor" T100000 B4725 C7.06e-8 ; 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 A11 C99000 D2000 B1 ; enable bang-bang mode for the bed heater and set PWM limit
                              M140 H0 ; map heated bed to heater 0
                              M143 H0 S120 ; set temperature limit for heater 0 to 120C
                              M308 S1 P"spi.cs1" Y"thermocouple-max31856" ; configure sensor 1 as thermocouple via CS pin spi.cs1
                              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
                              M308 S2 P"spi.cs2" Y"thermocouple-max31856" ; configure sensor 2 as thermocouple via CS pin spi.cs2
                              M950 H2 C"e1heat" T2 ; create nozzle heater output on e1heat and map it to sensor 2
                              M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
                              M308 S3 P"duex.e2temp" Y"thermistor" T10000 B3950 ; configure sensor 3 as thermistor on pin duex.e2temp
                              M950 H3 C"duex.e2heat" T3 ; create chamber heater output on duex.e2heat and map it to sensor 3
                              M307 H3 A11 C99000 D2000 B1 ; enable bang-bang mode for the chamber heater and set PWM limit
                              M141 H3 ; map chamber to heater 3
                              ; Fans
                              M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
                              M106 P0 S1 H-1 ; set fan 0 value. Thermostatic control is turned on
                              M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
                              M106 P1 S1 H2 T45 ; set fan 1 value. Thermostatic control is turned on
                              M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
                              M106 P2 S1 H1:2 T45 ; set fan 2 value. Thermostatic control is turned on
                              ; Tools
                              M563 P0 S"MAIN EXTRUDER" 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
                              M563 P1 S"SECOND EXTRUDER" D1 H2 F0 ; define tool 1
                              G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets
                              G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C
                              ; Custom settings are not defined
                              ; Miscellaneous
                              M575 P1 S1 B57600 ; enable support for PanelDue
                              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
                              T0 ; select first tool
                              ; homeall.g
                              ; called to home all axes
                              ;
                              ; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Oct 13 2020 21:14:55 GMT-0500 (Central Daylight Time)
                              G91 ; relative positioning
                              G1 H1 Z500 F6000 ; lift Z relative to current position
                              G1 H1 X-465 F8000 ; move quickly to X endstop and stop there (first pass)
                              G1 H1 Y-465 F8000 ; move quickly to Y endstop and stop there (first pass)
                              G1 H2 X5 Y5 F6000 ; go back a few mm
                              G1 H1 X-465 F360 ; move slowly to X axis endstop once more (second pass)
                              G1 H1 Y-465 F360 ; then move slowly to Y axis endstop
                              G1 X235 Y235 F6000 ; Prob at Center
                              M558 F600 A1 ; Dive fast once
                              G30 ; probe Z
                              M558 F300 A10 ; Slow second dive with more accuracy
                              G30 ; probe z again
                              1/31/2021, 11:51:21 PM: M122: === Diagnostics ===
                              RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet Ethernet 1.02 or later + DueX5
                              Board ID: 08DLM-996RU-N8PS0-7J9D8-3S86T-1B8VP
                              Used output buffers: 3 of 24 (24 max)
                              === RTOS ===
                              Static ram: 23460
                              Dynamic ram: 70344 of which 40 recycled
                              Never used RAM 18236, free system stack 210 words
                              Tasks: NETWORK(ready,173) HEAT(blocked,309) DUEX(blocked,35) MAIN(running,452) IDLE(ready,19)
                              Owned mutexes:
                              === Platform ===
                              Last reset 00:02:05 ago, cause: power up
                              Last software reset at 2021-01-31 23:46, reason: User, GCodes spinning, available RAM 18236, slot 0
                              Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                              Error status: 0x04
                              Aux0 errors 0,0,0
                              MCU temperature: min 26.3, current 26.8, max 27.1
                              Supply voltage: min 25.0, current 25.0, max 25.1, under voltage events: 0, over voltage events: 0, power good: yes
                              Driver 0: position 0, standstill, SG min/max not available
                              Driver 1: position 0, standstill, SG min/max not available
                              Driver 2: position 0, standstill, SG min/max not available
                              Driver 3: position 0, standstill, SG min/max not available
                              Driver 4: position 0, standstill, SG min/max not available
                              Driver 5: position 0, standstill, SG min/max not available
                              Driver 6: position 0, standstill, SG min/max not available
                              Driver 7: position 0, standstill, SG min/max not available
                              Driver 8: position 0, standstill, SG min/max not available
                              Driver 9: position 0, standstill, SG min/max not available
                              Driver 10: position 0
                              Driver 11: position 0
                              Date/time: 2021-01-31 23:51:20
                              Cache data hit count 194997097
                              Slowest loop: 8.94ms; fastest: 0.21ms
                              I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                              === Storage ===
                              Free file entries: 10
                              SD card 0 detected, interface speed: 20.0MBytes/sec
                              SD card longest read time 3.9ms, write time 2.4ms, max retries 0
                              === Move ===
                              DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
                              === MainDDARing ===
                              Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                              === AuxDDARing ===
                              Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                              === Heat ===
                              Bed heaters = 0 -1 -1 -1, chamberHeaters = 3 -1 -1 -1
                              Heater 1 is on, I-accum = 0.0
                              === GCodes ===
                              Segments left: 0
                              Movement lock held by null
                              HTTP is idle in state(s) 0
                              Telnet is idle in state(s) 0
                              File is idle in state(s) 0
                              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
                              Daemon is idle in state(s) 0
                              Autopause is idle in state(s) 0
                              Code queue is empty.
                              === Network ===
                              Slowest loop: 25.61ms; fastest: 0.07ms
                              Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                              HTTP sessions: 2 of 8
                              Interface state active, link 100Mbps full duplex
                              === DueX ===
                              Read count 0, 0.00 reads/min

                              **The Problem now when I click HomeZ only driver number 6 moves down (!exp.e6stop) and if press any end-stop it will stop it but the rest they do not move at all this is the problem I have I don't know if the Duex5 is bad and not communicating effectively with the duet ethernet board. **

                              1 Reply Last reply Reply Quote 0
                              • undefined
                                Phaedrux Moderator
                                last edited by Phaedrux 2 Jan 2021, 06:51 1 Feb 2021, 06:50

                                @Phaedrux said in G32 ERROR:

                                M98 P"config.g" and post the results?

                                And just to confirm, you have all Z motors and endstops connected to the Duex?

                                And your duex is wired up for power/ground as shown here?

                                https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring

                                Z-Bot CoreXY Build | Thingiverse Profile

                                1 Reply Last reply Reply Quote 0
                                • undefined
                                  moe.adams9093
                                  last edited by 1 Feb 2021, 13:27

                                  1/31/2021, 11:51:56 PM: M98 P"config.g": HTTP is enabled on port 80
                                  FTP is disabled
                                  TELNET is disabled
                                  Error: bad grid definition: Too many grid points; suggest increase spacing to 21.0mm
                                  Warning: Macro file config-override.g not found

                                  sorry I thought I did post my M98. but everything works correctly on my duex5 except my end stops. If I run M564 S0 H0 all Zmotors work correctly. the duex5 is wired correctly as and all endstops wired correctly as well

                                  1 Reply Last reply Reply Quote 0
                                  • undefined
                                    fcwilt
                                    last edited by 1 Feb 2021, 13:34

                                    @moe-adams9093 said in G32 ERROR:

                                    M569 P8 S0 ; physical drive 7 goes Backwards

                                    The comment says 7 the command specifies 8.

                                    Have you manually activated each Z end stop sensor, one at a time, and run M119 to verify the reported end stop state?

                                    Frederick

                                    Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                                    1 Reply Last reply Reply Quote 0
                                    • undefined
                                      moe.adams9093
                                      last edited by 1 Feb 2021, 14:20

                                      Yes I did and they all trigger as Z max endstop on m119

                                      undefined 1 Reply Last reply 1 Feb 2021, 16:28 Reply Quote 0
                                      • undefined
                                        moe.adams9093
                                        last edited by 1 Feb 2021, 14:29

                                        M569 P5 S1
                                        M569 P6 S1
                                        M569 P8 S0
                                        M569 P9 S0
                                        Yes this is the correct format for all of my z axis motors 2 motors are mirror to the other 2 thats why I have p8 s0 and p9 s0

                                        1 Reply Last reply Reply Quote 0
                                        • undefined
                                          fcwilt @moe.adams9093
                                          last edited by 1 Feb 2021, 16:28

                                          @moe-adams9093 said in G32 ERROR:

                                          Yes I did and they all trigger as Z max endstop on m119

                                          Great.

                                          Can you easily remove the bed assembly so we can test each Z stepper one at a time?

                                          Frederick

                                          Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

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