Mesh bed Leveling with differention IR-Probe Problems

  • Hi,
    i have been dealing with this problem quite a while now and at this stage i am not willing to deal with my problem alone anymore.

    I will describe my problem below:

    Probe is set correctly.
    Normal Z-Homing is performing nicely.
    Starting to get to Mesh bed leveling G29 S0, the printer performs a axis homing correctly, then performs 2 or 3 mesh probings correctly and then it will push the nozzle in the bed and comes with the error: "Error: Z probe was not triggered during probing move"

    I got the printer to complete the mesh bed leveling once. But since then i wans't been able to get it to work again.

    The IR-Probe is connected correct and flashes 4 times during startup.

    Here is my Config.g:

    ; Configuration file for Duet WiFi (firmware version 1.20 or newer)
    ; executed by the firmware on start-up
    ; generated by RepRapFirmware Configuration Tool on Sat Nov 25 2017 11:49:47 GMT+0100 (Mitteleuropäische Zeit)

    ; General preferences
    M111 S0 ; Debugging off
    G21 ; Work in millimetres
    G90 ; Send absolute coordinates…
    M83 ; ...but relative extruder moves
    M555 P2 ; Set firmware compatibility to look like Marlin
    M911 S12 R21 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"
    M208 X0 Y0 Z0 S1 ; Set axis minima
    M208 X210 Y297 Z220 S0 ; Set axis maxima
    M915 X Y S10 F0 H300 R3 ; Cofigure Stallguard
    M376 H10 ; Set bed compensation Taper

    ; Endstops
    M574 X1 Y1 S0 ; Set active low endstops
    M574 Z1 S2 ; Set endstops controlled by probe
    M558 P1 H5 F600 T6000 ; Set Z probe type to unmodulated and the dive height + speeds
    G31 P500 X-14.5 Y0 Z0.8 ; Set Z probe trigger value, offset and trigger height
    M557 X15:195 Y10:285 S20 ; Define mesh grid

    ; Drives
    M569 P0 S1 ; Drive 0 goes forwards
    M569 P1 S0 ; Drive 1 goes backwards
    M569 P2 S1 ; Drive 2 goes forwards
    M569 P3 S1 ; Drive 3 goes forwards
    M569 P4 S1 ; Drive 4 goes forwards
    M350 X16 Y16 Z16 E16:16 I1 ; Configure microstepping with interpolation
    M92 X80 Y80 Z4000 E476.5:500 ; Set steps per mm
    M566 X2000 Y2000 Z2000 E120:120 ; Set maximum instantaneous speed changes (mm/min)
    M203 X15000 Y15000 Z100 E6000:6000 ; Set maximum speeds (mm/min)
    M201 X1000 Y1000 Z1000 E6500:6500 ; Set accelerations (mm/s^2)
    M906 X1700 Y1700 Z1700 E1200:1200 I30 ; Set motor currents (mA) and motor idle factor in per cent
    M84 S30 ; Set idle timeout

    ; Heaters
    M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
    M305 P0 T100000 B4725 C7.060000e-8 R4700 ; Set thermistor + ADC parameters for heater 0
    M143 H0 S120 ; Set temperature limit for heater 0 to 120C
    M305 P1 T100000 B4725 C7.060000e-8 R4700 ; Set thermistor + ADC parameters for heater 1
    M143 H1 S280 ; Set temperature limit for heater 1 to 280C
    M307 H1 A282.9 C101.7 D4.0 B0 ; PWM for bed
    M307 H0 A131.7 C221.6 D2.4 B0 ; PWM for Hotend

    ; Tools
    M563 P0 D0 H1 ; 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 D1 H1 ; 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
    M572 D0 S0.2 ; Pressure Advance Drive 0
    M572 D1 S0.2 ; Pressure Advance Drive 1

    ; Network
    M550 PHephestos 2 Enhanced ; Set machine name
    M552 S1 ; Enable network
    M587 S"XXXXXXXXXXXXX" P"XXXXXXXXXXXXXX" ; Configure access point. You can delete this line once connected
    M586 P0 S1 ; Enable HTTP
    M586 P1 S1 ; Enable FTP
    M586 P2 S1 ; Enable Telnet

    ; Fans
    M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F500 H1 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P2 S1 I0 F500 H1 T45 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

    ; Custom settings are not configured

    ; Miscellaneous
    T0 ; Select first tool

    Oh and my Hardware is an BQ Hephestos 2 with an Prometheus system.
    And Firmware settings are:

    Firmwarename: RepRapFirmware for Duet WiFi
    Firmware Elektronik: Duet WiFi 1.0
    Firmware Version: 1.20 (2017-12-23)
    WiFi Server Version: 1.20
    Web Interface Version: 1.2


    If anything else is needed please let me know.

    Would be pleased if anyone could help me.


  • By the way, forget to mention that the bed isn't the glas one anymore. I installed a Filabase with a filaprint surface.
    but i can't get the mesh bet leveling (G29) to work anymore.
    As described the first till fith or so probes are fine but then the probe triggers but the axis keeps on driving the nozzel to the bed.

    Nobody a clue?

  • administrators

    When the motor drives the nozzle into the bed, are you certain that the IR probe has triggered? What Z probe reading do you get at that point? You can temporarily reduce the Z moor current to avoid damage.

  • Hi, the LED on the Probe definetly lights up so i assume the probe itself is fine.
    Cant tell exactly what the reading is at the point of impact, because the web interface is nat that fast with the updates.
    But i will look into it today.

    greetings Kai

  • administrators

    Jog the nozzle slowly down over the point where probing fails, check that the LED lights up before the nozzle touches the bed, check that the web interface shows a Z probe reading in DWC is around 535, and measure the trigger height at that point to check that is isn't too different from the 0.8mm that you have configured in the G31 command

  • Hi testet it now, the reading when it fails lies beneath 500, ist around 470.
    But when i jog the printer manually down on that position the probe reads 535 just fine.
    I don't know what the problem is. There are no loose wires or cold solderspots.
    Its confusing that somtimes the probe doesn't get over 480 and when i do the same spot manually it works perfecly fine and reads 535 repeatingly.

  • Solved the problem.
    Did a hole new wirering of the printer with shielded network cable.
    Now the sensor behaves repeatingly trustfull.
    Thanks for the Help so far.


Log in to reply