BL-Touch - multiple problems -



  • Hey,
    My first start with the new Duet is a bit problematic. The BL-Touch isn't retract or deploying by itself.
    While the BL doing its self test, it has retracted and deployed normally. But this was the only time the BL was moving by itself.
    Push the BL stick in is working.
    Errors:
    G30 - error: Z probe already triggered at start of probing move.
    Or G29
    Error: Z probe already triggered before probing move started.
    Sry
    Just saw the guide for posting problems. I'll describe it better in future.
    Thanks to all


  • Moderator

    We will need to know more info.

    What Duet board?
    What firmware?
    How is the BLTouch wired?
    Post your config.g, deploy retract macros, homing files.

    Then we can get an idea on what's happening.



  • @Phaedrux @Phaedrux
    Of course!! First of all I have to say thank you for the good support in this forum. It is very goood!!! thanks

    -Duet3 6hc + expansion (not connected yet, could be in seconds)
    -Board: Duet 3 MB6HC (MB6HC)
    DSF Version: 3.1.1
    Firmware: RepRapFirmware for Duet 3 MB6HC 3.01-RC9 (2020-04-21b1)
    Wiring:
    BL ---------Duet
    White - io7.in
    Black - GND
    Yellow - io7.out
    Red - 5v

    codes:
    config.g---------------------------

    ; Configuration file for Duet 3 (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 22:36:44 GMT+0200 (Mitteleuropäische Sommerzeit)

    ; General preferences
    G90 ; send absolute coordinates...
    M83 ; ...but relative extruder moves
    M550 P"Duet 3" ; set printer name

    ; Drives
    M569 P0.0 S1 ; physical drive 0.0 goes forwards
    M569 P0.1 S1 ; physical drive 0.1 goes forwards
    M569 P0.2 S1 ; physical drive 0.2 goes forwards
    M569 P0.3 S1 ; physical drive 0.3 goes forwards
    M569 P0.4 S1 ; physical drive 0.4 goes forwards
    M569 P0.5 S1 ; physical drive 0.5 goes forwards
    M569 P1.0 S1 ; physical drive 1.0 goes forwards
    M569 P1.1 S1 ; physical drive 1.1 goes forwards
    M569 P1.2 S1 ; physical drive 1.2 goes forwards
    M584 X0.0 Y0.1 Z0.2:0.3:0.4:0.5 E1.0:1.1:1.2 ; set drive mapping
    M350 X16 Y16 Z16 E16:16:16:16:16:16 I1 ; configure microstepping with interpolation
    M92 X80.00 Y80.00 Z1600.00 E1600.00:1600.00:1600.00:92.70:92.70:92.70 ; set steps per mm
    M566 X900.00 Y900.00 Z12.00 E120.00:120.00:120.00:120.00:120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
    M203 X6000.00 Y6000.00 Z3600.00 E3600.00:3600.00:3600.00:1200.00:1200.00:1200.00 ; set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z20.00 E250.00:250.00:250.00:250.00:250.00:250.00 ; set accelerations (mm/s^2)
    M906 X1200 Y1200 Z3000 E3000:3000:3000:1200:1200:1200 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 X800 Y800 Z800 S0 ; set axis maxima

    ; Endstops
    M574 X2 S1 P"!io3.in" ; configure active-high endstop for high end on X via pin !io3.in
    M574 Y2 S1 P"!io0.in" ; configure active-high endstop for high end on Y via pin !io0.in

    ; Z-Probe
    M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
    M558 P9 C"^io7.in" H15 F120 1400 ; set Z probe type to bltouch and the dive height + speeds
    G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
    M557 X15:650 Y15:650 S30 ; define mesh grid

    ; Heaters
    M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
    M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
    M307 H0 B0 S0.10 ; disable bang-bang mode for the bed heater and set PWM limit
    M140 H0 ; map heated bed to heater 0
    M143 H0 S90 ; set temperature limit for heater 0 to 90C
    M308 S1 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
    M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
    M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

    ; Fans
    M950 F0 C"out3" Q500 ; create fan 0 on pin out3 and set its frequency
    M106 P0 S0.8 H-1 ; set fan 0 value. Thermostatic control is turned off
    M950 F1 C"out7" Q500 ; create fan 1 on pin out7 and set its frequency
    M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
    M950 F2 C"out8" Q500 ; create fan 2 on pin out8 and set its frequency
    M106 P2 S1 H T45 ; set fan 2 value. Thermostatic control is turned on

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

    ; Custom settings are not defined

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

    deploy----------------------------
    ; deployprobe.g
    ; called to deploy a physical Z probe
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 22:36:44 GMT+0200 (Mitteleuropäische Sommerzeit)
    M280 P0 S10 ; deploy BLTouch

    retract.g--------------------------------
    ; retractprobe.g
    ; called to retract a physical Z probe
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 22:36:44 GMT+0200 (Mitteleuropäische Sommerzeit)
    M280 P0 S90 ; retract BLTouch

    homez.g-------------------------
    ; homez.g
    ; called to home the Z axis
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.3 on Thu Jun 25 2020 00:21:12 GMT+0200 (Mitteleuropäische Sommerzeit)
    G91 ; relative positioning
    G1 H2 Z5 F6000 ; lift Z relative to current position
    G90 ; absolute positioning
    G1 X15 Y15 F6000 ; go to first probe point
    G30 ; home Z by probing the bed

    BL- Touch does the selfest. Its retracting and deploying when starting power.

    thanks a lot,
    the support here is very good. I started in februar with 3d Printing. If I dont understand something direct: I´m Sorry



  • sos
    I think @Phaedrux lives in a different time zone and I don´t wanna stress anybody.
    Can anybody else help me?
    thanks


  • Moderator

    @barbarossa-cologne said in BL-Touch - multiple problems -:

    RepRapFirmware for Duet 3 MB6HC 3.01-RC9

    To begin with, update your firmware to 3.1.1

    Does your BLTouch respond if you send M401 and M402 to deploy and retract the pin?

    Does it respond if you send it the command to enter test mode? M280 P0 S120

    What version of BLTouch is this?



  • @Phaedrux
    short describtion for update firmware?
    with pi 4

    M401 / M402 are not working. The web control shows the normal green button on rigth bottom screen but no moving.
    When I connect the BL the test move happens.......

    M280 P0 S120

    • green button on screen, no moving or something else.

    I don´t know which version. Can I see it on the wire colours?
    Original from antlabs and bougth last week.
    thanks to canada



  • This post is deleted!

  • Moderator

    @barbarossa-cologne said in BL-Touch - multiple problems -:

    short describtion for update firmware?
    with pi 4

    https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware

    M401 / M402 are not working. The web control shows the normal green button on rigth bottom screen but no moving.
    When I connect the BL the test move happens.......
    M280 P0 S120

    green button on screen, no moving or something else.

    It sounds like a wiring issue. The probe is getting power and ground, but no signal. Triple check your wiring and crimps. A good test is to connect the short leads from the BLtouch directly to the board to eliminate the extension wires.



  • @barbarossa-cologne

    I saw this settings made in the configuration tool. I tried to change the settings manual. Maybe I made somethig wrong there?

    z.jpeg io.mapping.jpeg


  • Moderator

    That all looks ok as long as you're actually wired up to the io7 in and out pins.



  • @Phaedrux
    ok. I´ll check everything-



  • @Phaedrux
    What do you mean with ´´actually wired up to the ioin and out pins´´?


  • Moderator

    I mean that your config looks ok, now the wiring must be correct for the config to work.



  • @Phaedrux
    ok sry.
    I tested the wiring. Its not the problem....
    this is the last problem I have to solve before starting. Thats really bad.


  • Moderator

    If that's the case and the wiring is good please update your firmware (as linked above for the Duet + SBC). Send M115 after to verify.

    Then please send M98 Pconfig.g and report any errors.



  • @Phaedrux
    M98 Error: Non-empty string expected
    firmware is updated


  • Moderator

    That's a weird error. You're sending this exactly?

    M98 Pconfig.g



  • @Phaedrux said in BL-Touch - multiple problems -:

    M98 Pconfig.g

    yes


  • Moderator

    try M98 P"config.g"



  • @Phaedrux said in BL-Touch - multiple problems -:

    M98 Pconfig.g

    ´´´Response to long, see console´´.
    I havent connected the expansion board, yet. Is this a problem?


  • Moderator

    Are you in the DWC gcode console when you send that?



  • @Phaedrux yes



  • I homed z again. It's homing without triggering manual the BL.

    Also when I go down with the z axis... doesn't care which amount and then homing z, the z motors are turning back always the same amount and it stops.
    --> I hope that helps


  • Moderator

    I'm not exactly sure what you mean.

    Looking back over your config.g I notice two things on your M558 command that we can try changing.

    M558 P9 C"^io7.in" H15 F120 1400

    First, you're missing the T in front of the 1400 to define the travel speed between probe points.

    Second, try removing the ^ from in front of io7.in. I think it's only zprobe.in that requires the pullup.

    I'd still like to see what the gcode console output is from sending M98 P"config.g" It should echo SOMETHING back.



  • M558 P9 C"io7.in" H15 F120 T1400 ----> doesn´t work

    M98 P"config.g"
    --> response to long, see console

    Should I buy a other sensor?
    My motivation after a few days is down.....


Log in to reply