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

    Mini 5 (with toolboard) and leveling using X2 Motors

    Scheduled Pinned Locked Moved Solved
    General Discussion
    4
    25
    967
    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.
    • JayJayundefined
      JayJay
      last edited by JayJay

      So the final hurdle in setting up my new Mini 5 plus!!

      I cant get the levelling using x2 Z axis motors to work.

      I previously had a Duet-2 Wifi installed and everything worked with it (including the two motor leveling)

      I had a Genuine Duet IR sensor installed and when i went to initiate G32 it would home fine (the probe showed as having triggered in the DWC momentarily showing a value of 1000), but as soon as it sent the probe to the designated point beside the first leadscrew it would probe but not trigger the probe (no value change) but no head crash occured and the same thing happened to the second probe point, after completion DWC reported the failure due to the probe not being triggered.

      I thought my IR probe was now somehow faulty, and as i have a genuine BL touch spare i fitted and set that up. i can carry out homing with that, the probe deploys and the head drops, and as soon as the probe touches the bed the head lifts back up but when i tell it to carry out a G32 command it homes (as i have a G28 in my bed.g) the BL touch probes and the head lifts up again but the DWC doesnt report that the probe has triggered and G32 fails saying that the probe was not triggered but i am physically watching the BL touch react and again the head doesnt crash.

      I have attached my config.g and bed.g but please remember this only started when i swapped over to the new mini 5 and a toolboard with my Duet-2 everything worked on the same settings..

      any idea's ?

      im considering a temporary rewire to bypass the toolboard so see how that effects things.

      ;  Mega-3-Mini 5 config.g
      
      ; 1. General Preferences 
      G90                                                                            ; Machine movement to use absolute coordinates
      M83                                                                            ; Extruder to use relative moves
      M550 P"Mega-3"                                                                 ; Machine name
      
      ; 2. Network
      M552 S1                                                                        ; Network is enabled and acquires a dynamic address via DHCP
      M586 P0 S1                                                                     ; HTTP is enabled
      M586 P1 S0                                                                     ; FTP is disabled
      M586 P2 S0                                                                     ; Telnet is disabled
      
      ; 3. Drives
      M669 K0                                                                        ; Select kinematics type
      M671 X-70:410 Y170:170 S10                                                     ; The Z axis pivot point locations to allow levelling to be undertaken
      M569 P0.0 S1                                                                   ; Drive 0.0 (Y Axis Motor) goes forwards
      M569 P0.1 S1                                                                   ; Drive 0.1 (Z1 Axis, Left Motor) goes forwards
      M569 P0.2 S1                                                                   ; Drive 0.2 (Z2 Axis, Right Motor) goes forwards
      M569 P0.3 S1                                                                   ; Drive 0.3 (X Axis Motor) goes forwards
      M569 P121.0 S1                                                                 ; Drive 121.0 (E0, Extruder Motor) goes forwards and is mapped to the Tool-Board-LC1
      M584 X0.3 Y0.0 Z0.1:0.2 E121.0                                                 ; Drive mapping
      M350 X16 Y16 Z16 E16:16 I1                                                     ; Microstepping with interpolation
      M92 X80.00 Y100.00 Z400.00 E409.00                                             ; Steps per mm
      M566 X900.00 Y900.00 Z60.00 E120.00                                            ; Maximum instantaneous speed changes (mm/min)
      M203 X6000.00 Y6000.00 Z180.00 E1200.00                                        ; Maximum speeds (mm/min)
      M201 X500.00 Y500.00 Z20.00 E250.00                                            ; Accelerations (mm/s^2)
      M906 X1200 Y1200 Z800 E800 I30                                                 ; Motor currents (mA) & motor idle factor %
      M84 S30                                                                        ; Idle timeou
      
      ; 4. Axis Limits
      M208 X0 Y0 Z-1 S1                                                              ; Axis min
      M208 X350 Y350 Z350 S0                                                         ; Axis max
      
      ; 5. Endstops
      M574 X1 S1 P"121.io1.in"                                                       ; X Axis endstop is at the low end and mapped to pin 121.io1.in on the Tool-Board-LC1
      M574 Y1 S1 P"io1.in"                                                           ; Y Axis endstop is at the low end and mapped to pin io1.in on the Main Board
      M574 Z1 S2                                                                     ; The Z probe acts as a Z axis endstop & is located at Z axis's minimum & mapped/connected to the io0 port on the toolboard LC1
      
      ; 6. Z-Probe
      
      ; 6.A BL-Touch code
      M950 S0 C"121.io0.out"                                                         ; Servo pin 121.io0.out for the BL-Touch
      M558 P9 C"121.io0.in" H5 F100 T6000                                            ; Signal pin 121.io.in for the BL-Touch
      G31 X-32 Y-1 Z0.777 P25                                                        ; Probe's trigger value, offsets & trigger height
      ;M557 X5:270 Y0:280 S44                                                        ; Mesh grid parameters
      
      ; 6.B IR sensor code
      ;M558 P8 C"121.io0.in" H5 F100 T6000                                           ; The Z probe is of type 8 & is mapped/connected to 121.io0.in port on the toolboard LC1 
      ;G31 P50 X11 Y0 Z1.298                                                         ; Z probe trigger value, offset and trigger height
      ;M557 X45:370 Y8:330 S20                                                       ; Mesh grid parameters 
      
      ; 7. Heaters
      M308 S0 P"temp0" Y"thermistor" T100000 B4138                                   ; Sensor 0 is a thermistor on temp0
      M950 H0 C"out0" T0                                                             ; Bed heater is on output on out0 & mapped to sensor 0
      M307 H0 R0.885 C213.4 D5.27 S1.00                                              ; Bed heater is set to PID mode & set PWM limit
      M140 H0                                                                        ; Bed heater is mapped to heater 0
      M143 H0 S120                                                                   ; Temperature limit for the bed heater is set to 120C
      ;
      M308 S1 P"121.temp1" Y"thermistor" T100000 B4138                               ; Sensor 1 is a thermistor & mapped to pin 121.temp1 on the Tool-Board-LC1
      M950 H1 C"121.out0" T1                                                         ; The Hot end heater outputs on 121.out0 and is mapped to sensor 1 on the Tool-Board-LC1
      M307 H1 A312.4 C202.6 D15 S1 V23.6                                             ; The Hot end heater is set to ise PID & set PWM limit
      M143 H1 S310                                                                   ; Temperature limit for the Hot end heater is set to 310C
      
      ; 8. Fans
      M950 F0 C"121.out1"                                                            ; The part cooling fan (fan0)is mapped/connected to out1 on the toolboard LC1
      M106 P0 S0 H-1 C"Part Cooling Fan"                                             ; The part cooling fan (fan0)is set to value 0 & thermostatic control is turned off
      M950 F1 C"121.out2"                                                            ; The hot end cooling fan(fan1)is mapped/connected to out2 on the toolboard LC1
      M106 P1 S255 H-1 C"Hot End Fan"                                                ; The hot end cooling fan(fan1)is set to value 1 & thermostatic control turned off
      
      ; 9. Tools
      M563 P0 S"Hot-End" D0 H1 F0                                                    ; Define tool 0
      G10 P0 X-40 Y0 Z0                                                              ; Set tool 0 axis offsets
      G10 P0 R0 S0                                                                   ; Set initial tool 0 active and standby temperatures to 0C
      
      ; 10. Miscellaneous
      ;T0                                                                             ; Select first tool
      
      
      ; Bed.g file called to level 2 Z axis motors via G32
      
      G28                         ; Home all axis's
      G30 P0 X50 Y170 Z-99999     ; Probe near the left lead-screw
      G30 P1 X350 Y170 Z-99999 S2 ; Probe near the right lead screw 
      G30 P0 X50 Y170 Z-99999     ; Probe near the left lead-screw (Second Pass)
      G30 P1 X350 Y170 Z-99999 S2 ; Probe near the rear lead screw (Second Pass)
      G1 X170 Y170 F8000          ; Position the nozzle at the centre of the bed
      G30                         ; Probe and set the height as probed
      G29 S1 P"heightmap.csv"     ; Load the height map
      
      
      1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti
        last edited by Veti

        dont load the heightmap in bed.g

        bed.g should only execute the probing. and that only once.

        so remove the second probing, g30 and g29.

        can you connect the probe to the mini 5 and retest?

        did you update the firmware on the toolboard to match the one on the mini 5?

        JayJayundefined 1 Reply Last reply Reply Quote 0
        • JayJayundefined
          JayJay @Veti
          last edited by JayJay

          @Veti

          I had an issue with miss-matched firmware earlier in the week which left me with a heater issue, the toolboard update took but the mainboard firmware didnt.

          I had updated it (or so i thought) but the update hadnt taken, until it was done manually again, that updated evertything fully to the latest release candidates.

          the final G30 in my bed.g was the result of a thread here on the forum which recommended a final G30 to re-set the Z datum in the middle of the bed after the leadscrews had carried out their compensation actions.

          i commented it out the final G30, and the G29 that made no difference .

          Although im puzzled why it would be a problem to load the height map aftwards when everything worked perfectly well on my Duet-2 with the same firmware and same bed.g .

          i will make up a loom to remove the toolboard from the equation to see how that works

          Vetiundefined 1 Reply Last reply Reply Quote 0
          • Vetiundefined
            Veti @JayJay
            last edited by

            @JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:

            the final G30 in my bed.g was the result of a thread here on the forum which recommended a final G30 to re-set the Z datum in the middle of the bed after the leadscrews had carried out their compensation actions.

            best to do that in a macro.

            JayJayundefined 1 Reply Last reply Reply Quote 0
            • JayJayundefined
              JayJay @Veti
              last edited by

              @Veti

              what difference does it make where it is done ?

              Vetiundefined 1 Reply Last reply Reply Quote 0
              • Vetiundefined
                Veti @JayJay
                last edited by

                @JayJay
                so it makes things like this
                https://forum.duet3d.com/topic/20598/bed-g-repeated-execution-based-on-deviation-results
                easier

                JayJayundefined 1 Reply Last reply Reply Quote 0
                • JayJayundefined
                  JayJay @Veti
                  last edited by JayJay

                  @Veti said in Mini 5 (with toolboard) and leveling using X2 Motors:

                  @JayJay
                  so it makes things like this
                  https://forum.duet3d.com/topic/20598/bed-g-repeated-execution-based-on-deviation-results
                  easier

                  Thanks but i dont need that, and doesnt actually help me with the issue i am encountering.

                  i wired the Bl touch directly to the mini 5 and the problem still exists, i tried my IR probe direct to the board too and it too encounters the issue, really considering putting my Duet 2 back in at least i know it works.

                  EDIT

                  I just tested the probe(s) in all the other IO ports and the probes dont work in io0 or io4 dont know if that is relevant or not.

                  Vetiundefined 1 Reply Last reply Reply Quote 0
                  • Vetiundefined
                    Veti @JayJay
                    last edited by

                    @JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:

                    I just tested the probe(s) in all the other IO ports and the probes dont work in io0 or io4 dont know if that is relevant or not.

                    io0 and io4 are not pwm capable.

                    see
                    https://duet3d.dozuki.com/Wiki/Duet_3_Mini_5plus_Hardware_overview#Section_IO_port_pin_capabilities

                    1 Reply Last reply Reply Quote 0
                    • JayJayundefined
                      JayJay
                      last edited by

                      ok.

                      i tried homing Z at the points where my bed.g would probe to level the leadscrews and that works.

                      so its only when G32 is requested that the probe is not being seen

                      1 Reply Last reply Reply Quote 0
                      • Vetiundefined
                        Veti
                        last edited by

                        i am running bed leveling on my mini 5 fine using an ir probe.

                        only difference i see is that i have the M671 after the M208, but that should not matter

                        so its only when G32 is requested that the probe is not being seen

                        could that be a problem with the wiring?
                        maybe at the probing position the wires are not making a good contact

                        JayJayundefined 1 Reply Last reply Reply Quote 0
                        • JayJayundefined
                          JayJay @Veti
                          last edited by

                          @Veti said in Mini 5 (with toolboard) and leveling using X2 Motors:

                          i am running bed leveling on my mini 5 fine using an ir probe.

                          only difference i see is that i have the M671 after the M208, but that should not matter

                          so its only when G32 is requested that the probe is not being seen

                          could that be a problem with the wiring?
                          maybe at the probing position the wires are not making a good contact

                          if it was a wiring issue then when i home at the probe points that would fail too, its only when G32 is requested, the probes work fine on the toolboard too when requsted to home at those points which rule out the wiring.

                          As i said in my post about the heaters which turned out to be the firmware, im confident in my wiring

                          1 Reply Last reply Reply Quote 0
                          • Vetiundefined
                            Veti
                            last edited by

                            @JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:

                            G30 P0 X50 Y170 Z-99999
                            G30 P1 X350 Y170 Z-99999 S2

                            can you issue those commands manually? whats the output in the console

                            JayJayundefined 1 Reply Last reply Reply Quote 0
                            • JayJayundefined
                              JayJay @Veti
                              last edited by

                              @Veti said in Mini 5 (with toolboard) and leveling using X2 Motors:

                              @JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:

                              G30 P0 X50 Y170 Z-99999
                              G30 P1 X350 Y170 Z-99999 S2

                              can you issue those commands manually? whats the output in the console

                              i issued both manually

                              G30 P0 X50 Y170 Z-99999 completes fine (shows green in the console)
                              G30 P1 X350 Y170 Z-99999 S2 shows: Error: Z probe was not triggered during probing move

                              but i can physically see the probe operate and the Z axis react and the head lifts back up

                              1 Reply Last reply Reply Quote 0
                              • Vetiundefined
                                Veti
                                last edited by

                                and a g29 across the bed works?

                                JayJayundefined 1 Reply Last reply Reply Quote 0
                                • JayJayundefined
                                  JayJay @Veti
                                  last edited by JayJay

                                  @Veti

                                  yes it does.

                                  I re-installed my Duet-2 all is working again with the same bed.g file.

                                  i have compared my Duet-2 & mini-5 config's and i can see nothing wrong with the mini-5 config

                                  Vetiundefined 1 Reply Last reply Reply Quote 0
                                  • Vetiundefined
                                    Veti @JayJay
                                    last edited by

                                    @JayJay

                                    neither can i. and the probing working sometimes is not something you can configure.

                                    JayJayundefined 1 Reply Last reply Reply Quote 1
                                    • JayJayundefined
                                      JayJay @Veti
                                      last edited by

                                      @Veti said in Mini 5 (with toolboard) and leveling using X2 Motors:

                                      @JayJay

                                      neither can i. and the probing working sometimes is not something you can configure.

                                      Thank for the help, i will just wait and see what any of the duet team have to say , this board was a christmas gift so i will ask my uncle where he bought it

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

                                        Firmware version? Can you post the results of M122?

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        JayJayundefined 1 Reply Last reply Reply Quote 0
                                        • JayJayundefined
                                          JayJay @Phaedrux
                                          last edited by

                                          @Phaedrux said in Mini 5 (with toolboard) and leveling using X2 Motors:

                                          Firmware version? Can you post the results of M122?

                                          The Board is removed so the M122 will show some errors i think.

                                          i installed the board (and toolboard) in my core-xy , which normally has a duet-3-6hc fitted and the mini-5 runs fine in there, so im not sure why it doesnt like being in my hacked up i3, and even stranger that my Duet-2 wifi runs fine when i put it back into the i3, both printers sit side by side so its not a location related issue.

                                          i have been racking my brains with this one as it makes no sense at all.

                                          M115:

                                          FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.2-RC2 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2020-12-24

                                          M122
                                          === Diagnostics ===
                                          RepRapFirmware for Duet 3 Mini 5+ version 3.2-RC2 running on Duet 3 Mini5plus WiFi (standalone mode)
                                          Used output buffers: 3 of 40 (11 max)
                                          === RTOS ===
                                          Static ram: 98732
                                          Dynamic ram: 107196 of which 496 recycled
                                          Never used RAM 38792, free system stack 140 words
                                          Tasks: NETWORK(ready,192) HEAT(blocked,316) CanReceiv(blocked,947) CanSender(blocked,372) CanClock(blocked,360) TMC(blocked,123) MAIN(running,444) IDLE(ready,20) AIN(blocked,267)
                                          Owned mutexes: WiFi(NETWORK)
                                          === Platform ===
                                          Last reset 00:01:54 ago, cause: power up
                                          Last software reset at 2020-12-30 22:53, reason: User, GCodes spinning, available RAM 38752, slot 2
                                          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00451000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
                                          Error status: 0x00
                                          Aux0 errors 0,0,0
                                          Aux1 errors 0,0,0
                                          Supply voltage: min 0.0, current 0.9, max 0.9, under voltage events: 0, over voltage events: 0, power good: no
                                          Driver 0: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
                                          Driver 1: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
                                          Driver 2: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
                                          Driver 3: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
                                          Driver 4: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
                                          Driver 5: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
                                          Driver 6: position 0, ok, SG min/max not available, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0
                                          Date/time: 2021-01-01 15:00:52
                                          Cache data hit count 222524317
                                          Slowest loop: 5.31ms; fastest: 0.11ms
                                          === Storage ===
                                          Free file entries: 10
                                          SD card 0 detected, interface speed: 22.5MBytes/sec
                                          SD card longest read time 4.2ms, write time 0.0ms, 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, chamberHeaters = -1 -1
                                          === 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
                                          SBC is idle in state(s) 0
                                          Daemon is idle in state(s) 0
                                          Aux2 is idle in state(s) 0
                                          Autopause is idle in state(s) 0
                                          Code queue is empty.
                                          === Network ===
                                          Slowest loop: 10.70ms; fastest: 0.00ms
                                          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                                          HTTP sessions: 1 of 8

                                          • WiFi -
                                            Network state is active
                                            WiFi module is connected to access point
                                            Failed messages: pending 0, notready 0, noresp 0
                                            WiFi firmware version 1.25beta0
                                            WiFi MAC address f4:cf:a2:6f:bd:af
                                            WiFi Vcc 3.37, reset reason Power up
                                            WiFi flash size 2097152, free heap 25264
                                            WiFi IP address 192.168.0.115
                                            WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
                                            Clock register 00002002
                                            Socket states: 0 0 0 0 0 0 0 0
                                            === CAN ===
                                            Messages queued 1015, send timeouts 1012, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 16
                                          Phaedruxundefined 1 Reply Last reply Reply Quote 0
                                          • Phaedruxundefined
                                            Phaedrux Moderator @JayJay
                                            last edited by

                                            @JayJay said in Mini 5 (with toolboard) and leveling using X2 Motors:

                                            the mini-5 runs fine in there, so im not sure why it doesnt like being in my hacked up i3

                                            That is confusing. An intermittent short in something connected?

                                            Z-Bot CoreXY Build | Thingiverse Profile

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