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

    BLTouch Zprobe marche pas

    Scheduled Pinned Locked Moved Solved
    Firmware installation
    2
    50
    1.8k
    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 @chris974M
      last edited by

      @chris974M said in BLTouch Zprobe marche pas:

      G31 P500 X390 Y250 Z3.71 ; set Z probe trigger value, offset and trigger height

      Don't forget to fix this.

      Z-Bot CoreXY Build | Thingiverse Profile

      1 Reply Last reply Reply Quote 0
      • chris974Mundefined
        chris974M
        last edited by

        oui j'ai corriger cette erreur mes sa ne marche toujours pas

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

          @chris974M said in BLTouch Zprobe marche pas:

          ; Z-Probe
          M950 S0

          This is wrong. It should be M950 S0 C"duex.pwm5"

          Z-Bot CoreXY Build | Thingiverse Profile

          chris974Mundefined 1 Reply Last reply Reply Quote 0
          • chris974Mundefined
            chris974M @Phaedrux
            last edited by

            @Phaedrux j'ai corriger toujours rien

            1 Reply Last reply Reply Quote 0
            • chris974Mundefined
              chris974M
              last edited by

              ; Configuration file for Duet WiFi (firmware version 3)
              ; executed by the firmware on start-up
              ;
              ; generated by RepRapFirmware Configuration Tool v3.1.4 on Sat Oct 03 2020 15:26:33 GMT+0200 (heure d’été d’Europe centrale)

              ; General preferences
              G90 ; send absolute coordinates...
              M83 ; ...but relative extruder moves
              M550 P"MonsterPrinter" ; 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 S0 ; physical drive 1 goes forwards
              M569 P2 S1 ; physical drive 2 goes forwards
              M569 P3 S1 ; physical drive 3 goes forwards
              M569 P5 S1 ; physical drive 5 goes forwards
              M569 P6 S1 ; physical drive 6 goes forwards
              M569 P7 S0 ; physical drive 7 goes forwards
              M584 X0:5 Y1:6 Z2:7 E3 ; set drive mapping
              M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
              M92 X100.00 Y80.00 Z400.00 E420.00 ; set steps per mm
              M566 X900.00 Y1400.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
              M203 X9000.00 Y9000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
              M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
              M906 X800 Y1950 Z1400 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
              M84 S30 ; Set idle timeout

              ; Axis Limits
              M208 X-6 Y-10 Z0 S1 ; set axis minima
              M208 X780 Y510 Z350 S0 ; set axis maxima

              ; Endstops
              M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
              M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
              M574 Z1 S2 ; configure Z-probe endstop for low end on Z

              ; Z-Probe
              M950 S0 C "duex.pwm5" ; créer la broche servo 0 pour BLTouch
              M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
              G31 P500 X0 Y20 Z3.71 ; set Z probe trigger value, offset and trigger height
              M557 X40:780 Y80:510 S100 ; define mesh grid

              ; Heaters
              M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; 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 B0 S1.00 ; disable 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
              M305 P1 T4606017 B5848 C5.548428e-8 R4700 H0 L0
              M308 S1 P"e0temp" Y"thermistor" T4606017 B5848 ; 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 A580.4 C256.6 D6.4 S0.50 ; disable bang-bang mode for heater and set PWM limit
              M143 H1 S493
              ; 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 T45 ; 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
              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
                last edited by

                Try M950 S0 C"!duex.pwm5"

                Z-Bot CoreXY Build | Thingiverse Profile

                chris974Mundefined 1 Reply Last reply Reply Quote 0
                • chris974Mundefined
                  chris974M @Phaedrux
                  last edited by

                  @Phaedrux not work

                  1 Reply Last reply Reply Quote 0
                  • chris974Mundefined
                    chris974M
                    last edited by

                    G28
                    Error: Z probe was not triggered during probing move
                    Error: Homing failed

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

                      Does the BLTouch do a self test on power up with the pin deploying correctly?

                      Check your wiring for continuity.

                      Are you sure you are connected to Duex5 PWM5?

                      Can you try PWM1 instead?

                      Z-Bot CoreXY Build | Thingiverse Profile

                      chris974Mundefined 1 Reply Last reply Reply Quote 0
                      • chris974Mundefined
                        chris974M @Phaedrux
                        last edited by

                        @Phaedrux said in BLTouch Zprobe marche pas:

                        Does the BLTouch do a self test on power up with the pin deploying correctly?
                        Yes
                        My wiring is perfect
                        yesterday i check that before the maj and he is working corrct

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

                          Can you please send M122 and report the results.
                          Also send M98 P"config.g" and report the results.

                          Z-Bot CoreXY Build | Thingiverse Profile

                          1 Reply Last reply Reply Quote 0
                          • chris974Mundefined
                            chris974M
                            last edited by

                            @Phaedrux said in BLTouch Zprobe marche pas:

                            M122

                            M122
                            === Diagnostics ===
                            RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later + DueX5
                            Board ID: 08DLM-996RU-N8PS4-6JKD8-3S06T-KBVRN
                            Used output buffers: 1 of 24 (10 max)
                            === RTOS ===
                            Static ram: 27980
                            Dynamic ram: 94224 of which 44 recycled
                            Exception stack ram used: 264
                            Never used ram: 8560
                            Tasks: NETWORK(ready,416) HEAT(blocked,1224) DUEX(suspended,160) MAIN(running,1824) IDLE(ready,80)
                            Owned mutexes: WiFi(NETWORK)
                            === Platform ===
                            Last reset 00:01:17 ago, cause: software
                            Last software reset at 2020-10-08 00:05, reason: User, spinning module GCodes, available RAM 8560 bytes (slot 1)
                            Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
                            Error status: 0
                            MCU temperature: min 23.8, current 24.4, max 24.9
                            Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
                            Driver 0: standstill, SG min/max not available
                            Driver 1: standstill, SG min/max not available
                            Driver 2: standstill, SG min/max not available
                            Driver 3: standstill, SG min/max not available
                            Driver 4: standstill, SG min/max not available
                            Driver 5: standstill, SG min/max not available
                            Driver 6: standstill, SG min/max not available
                            Driver 7: standstill, SG min/max not available
                            Driver 8: standstill, SG min/max not available
                            Driver 9: standstill, SG min/max not available
                            Date/time: 2020-10-08 00:07:10
                            Cache data hit count 133234046
                            Slowest loop: 5.10ms; fastest: 0.12ms
                            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.5ms, write time 0.0ms, max retries 0
                            === Move ===
                            Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
                            Bed compensation in use: none, comp offset 0.000
                            === MainDDARing ===
                            Scheduled moves: 0, completed moves: 0, 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, chamberHeaters = -1 -1 -1 -1
                            === GCodes ===
                            Segments left: 0
                            Movement lock held by null
                            HTTP is ready with "M122 " 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
                            Daemon is idle in state(s) 0
                            Autopause is idle in state(s) 0
                            Code queue is empty.
                            === Network ===
                            Slowest loop: 15.65ms; 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.23
                              WiFi MAC address f4:cf:a2:66:94:6a
                              WiFi Vcc 3.43, reset reason Unknown
                              WiFi flash size 4194304, free heap 26096
                              WiFi IP address 192.168.1.122
                              WiFi signal strength -57dBm, reconnections 0, sleep mode modem
                              Socket states: 0 0 0 0 0 0 0 0
                              === DueX ===
                              Read count 1, 0.77 reads/min
                            1 Reply Last reply Reply Quote 0
                            • chris974Mundefined
                              chris974M
                              last edited by

                              @Phaedrux said in BLTouch Zprobe marche pas:

                              M98

                              M98 P"config.g"
                              HTTP is enabled on port 80
                              FTP is disabled
                              TELNET is disabled
                              Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C
                              Error: M305 has been replaced by M308 and M950 in RepRapFirmware 3
                              Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 605C

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

                                @chris974M said in BLTouch Zprobe marche pas:

                                M305 P1 T4606017 B5848 C5.548428e-8 R4700 H0 L0

                                Remove that line, though it's not related to the bltouch issue.

                                Are you able to try PWM1?

                                Z-Bot CoreXY Build | Thingiverse Profile

                                1 Reply Last reply Reply Quote 0
                                • chris974Mundefined
                                  chris974M
                                  last edited by

                                  ok i try

                                  1 Reply Last reply Reply Quote 0
                                  • chris974Mundefined
                                    chris974M
                                    last edited by

                                    que faut il que je change pour PWM1

                                    1 Reply Last reply Reply Quote 0
                                    • chris974Mundefined
                                      chris974M
                                      last edited by

                                      Example 4 (BLTouch on Duet WiFi) - old code:

                                      M558 P9 H5 F120 T3000 ; BLTouch connected to Z probe IN pin
                                      M307 H3 A-1 C-1 D-1 ; free up heater 3 to use as BLTouch servo pin
                                      ...
                                      M280 P3 S10 I1 ; send control signal to BLTouch through heater 3 pin
                                      New code:

                                      M558 P9 C"^zprobe.in" H5 F120 T3000 ; BLTouch connected to Z probe IN pin
                                      M950 S0 C"exp.heater3" ; create servo/gpio 0 on heater 3 pin on expansion connector
                                      ...
                                      M280 P0 S10 ; send control signal to BLTouch through servo/gpio 0

                                      1 Reply Last reply Reply Quote 0
                                      • chris974Mundefined
                                        chris974M
                                        last edited by

                                        M558 P9 C "^ zprobe.in " H5 F120 T3000; BLTouch connecté à la sonde Z IN pin
                                        M950 S0 C "duex.pwm1"; créer servo / gpio 0 sur l'élément chauffant 3 broches sur le connecteur d'extension
                                        ...
                                        M280 P0 S10; envoyer un signal de commande à BLTouch via servo / gpio 0

                                        Like that or nope

                                        Phaedruxundefined 1 Reply Last reply Reply Quote 0
                                        • chris974Mundefined
                                          chris974M
                                          last edited by

                                          Avertissement: le réchauffeur 0 semble être suralimenté. S'il est laissé allumé à pleine puissance, sa température devrait atteindre 365 ° C.
                                          Avertissement: le réchauffeur 1 semble être suralimenté. S'il est laissé allumé à pleine puissance, sa température devrait atteindre 605 ° C

                                          is it normal ?

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

                                            @chris974M said in BLTouch Zprobe marche pas:

                                            Avertissement: le réchauffeur 0 semble être suralimenté. S'il est laissé allumé à pleine puissance, sa température devrait atteindre 365 ° C.
                                            Avertissement: le réchauffeur 1 semble être suralimenté. S'il est laissé allumé à pleine puissance, sa température devrait atteindre 605 ° C

                                            is it normal ?

                                            Yes. https://duet3d.dozuki.com/Wiki/FAQ#Section_M307_Heater_1_appears_to_be_over_powered_If_left_on_at_full_power_its_temperature_is_predicted_to_reach_521C

                                            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