Duet 2 Wifi - TRONXY Z Probe Woes:



  • I am trying to use a Tronxy NPN/NO Probe with my Duet 2 Wifi board.

    After spending hours collecting bits of information from a terribly bad organized Wiki, i finally managed to get the Probe running - Duet Web Control 2 now shows probe activation.

    Buit there are 2 issues:

    1. I can activate my Z Probe on my duet 2 Wifi if i enter : "M558 P5 I1" in the Duet web Control. But if i put "M558 P5 I1" into the config.g and upload and restart, it does not.

    2. the Printer does not stop homing Z, even when the probe ist triggered.

    BR, Norbert



    1. when the M558 is in the config. what is the output of M558 without parameters
    2. What is the output of M119 when its not triggered, when its triggered? post your config.g and homing files.


  • THX, i really appreciaty your help!

    untriggered: M119
    Endstops - X: not stopped, Y: at min stop, Z: not stopped, Z probe: not stopped

    Triggered: M119
    Endstops - X: not stopped, Y: at min stop, Z: not stopped, Z probe: at min stop

    my config.g:

    ; Configuration file for Duet WiFi (firmware version 1.21)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Thu Aug 01 2019 18:14:47 GMT+0200 (Mitteleuropäische Sommerzeit)

    ; General preferences
    G90 ; Send absolute coordinates...
    M83 ; ...but relative extruder moves

    M669 K2 Z3 ; Select CoreXY mode

    ; Network
    M550 P"Tronxy 400" ; Set machine name
    M552 S1 ; Enable network
    M587 S"XXX" P"34211190" I192.168.1.19 J192.168.1.1 K255.255.255.0 ; Configure access point and IP addresses. You can delete this line once connected
    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 S1 ; Physical drive 1 goes forwards
    M569 P2 S0 ; Physical drive 2 goes backwards
    M569 P3 S1 ; Physical drive 3 goes forwards
    M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
    M92 X80.00 Y80.00 Z400.00 E98.00 ; Set steps per mm
    M566 X600.00 Y600.00 Z12.00 E120.00 ; Set maximum instantaneous speed changes (mm/min)
    M203 X18000.00 Y18000.00 Z180.00 E1500.00 ; Set maximum speeds (mm/min)
    M201 X3000.00 Y3000.00 Z100.00 E10000.00 ; Set accelerations (mm/s^2)
    M906 X950.00 Y950.00 Z950.00 E950.00 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 X400 Y400 Z400 S0 ; Set axis maxima

    ; Endstops
    M574 X1 Y1 S0 ; Set active low and disabled endstops

    ; Z-Probe
    M574 Z1 S2 ; Set endstops controlled by probe
    M558 P5 I1 ;H5 ;F1200 T6000 ; Set Z probe type to modulated and the dive height + speeds
    ;G31 P6000 X100 Y100 Z0 ; Set Z probe trigger value, offset and trigger height
    M557 X15:15 Y15:315 S20 ; Define mesh grid

    ; Heaters
    M305 P0 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 0
    M143 H0 S120 ; Set temperature limit for heater 0 to 120C
    M305 P1 T100000 B4138 R4700 ; Set thermistor + ADC parameters for heater 1
    M143 H1 S280 ; Set temperature limit for heater 1 to 280C

    ; 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 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

    ; 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

    ; Automatic power saving
    M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss

    ; Custom settings
    M558 P5 I1

    ; homeall.g
    ; called to home all axes
    ;
    ;

    G91 ; relative mode
    G1 S2 Z4 F200 ; raise head 4mm
    G1 S1 X-240 Y-240 F3000 ; move up to 240mm in the -X and -Y directions until the homing switches are triggered
    G1 S2 X4 Y4 F600; move slowly 6mm in +X and +Y directions
    G1 S1 X-10 Y-10 ; move up to 10mm in the -X and -Y directions until the homing switches are triggered
    G90 ; back to absolute mode
    G1 X100 Y100 F2000 ; put head over the centre of the bed, or wherever you want to probe
    G30 ; lower head, stop when probe triggered and set Z to trigger height

    ; homex.g
    ; called to home the X axis
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Thu Aug 01 2019 18:14:48 GMT+0200 (Mitteleuropäische Sommerzeit)
    G91 ; relative positioning
    G1 Z5 F6000 S2 ; lift Z relative to current position
    G1 S1 X-405 F1800 ; move quickly to X axis endstop and stop there (first pass)
    G1 X5 F6000 ; go back a few mm
    G1 S1 X-405 F360 ; move slowly to X axis endstop once more (second pass)
    G1 Z-5 F6000 S2 ; lower Z again
    G90 ; absolute positioning

    ; homey.g
    ; called to home the Y axis
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Thu Aug 01 2019 18:14:48 GMT+0200 (Mitteleuropäische Sommerzeit)
    G91 ; relative positioning
    G1 Z5 F6000 S2 ; lift Z relative to current position
    G1 S1 Y-405 F1800 ; move quickly to Y axis endstop and stop there (first pass)
    G1 Y5 F6000 ; go back a few mm
    G1 S1 Y-405 F360 ; move slowly to Y axis endstop once more (second pass)
    G1 Z-5 F6000 S2 ; lower Z again
    G90 ; absolute positioning

    ; homez.g
    ; called to home the Z axis
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Thu Aug 01 2019 18:14:48 GMT+0200 (Mitteleuropäische Sommerzeit)

    G91 ; relative mode
    G1 S2 Z4 F200 ; raise head 4mm to ensure it is above the Z probe trigger height
    G90 ; back to absolute mode
    G1 X100 Y100 F2000 ; put head over the centre of the bed, or wherever you want to probe
    G30 ; lower head, stop when probe triggered and set Z to trigger height; homez.g
    ; called to home the Z axis
    ;
    ; generated by RepRapFirmware Configuration Tool v2 on Thu Aug 01 2019 18:14:48 GMT+0200 (Mitteleuropäische Sommerzeit)

    G91 ; relative mode
    G1 S2 Z4 F200 ; raise head 4mm to ensure it is above the Z probe trigger height
    G90 ; back to absolute mode
    G1 X100 Y100 F2000 ; put head over the centre of the bed, or wherever you want to probe
    G30 ; lower head, stop when probe triggered and set Z to trigger height



  • You have two M558 commands in your config

    you have a commented G31 line. This needs to be uncommented.
    also the P Value is to large. It ranges from 0-1000. Try 500.
    Dont forget to calibrate the Z value afterwards.

    Your thermistor values are most likely wrong. B4138 is the default and need to be replaced with the correct values of your thermistors. Find out what thermistors you are using and look up the beta value.



  • Thanks for the fast reply - will check ASAP



  • Same result - after uploading the new configuration.zip, the board does not show z probe activation. If i put in "M558 P5 I1" manually via the gcode window in the Duet web Control it works - it shows when the probe is triggered - but the z homing still does not stop even when the probe is triggered.

    I have no idea.



  • @veti said in Duet 2 Wifi - TRONXY Z Probe Woes::

    what is the output of M558 without parameters

    please answer this question.



  • M558
    Z Probe type 0, input 0, invert no, dive height 5.0mm, probe speed 0mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03



  • if i activate the probe via "m558 P5 I1" and the sensor is not triggered it says:



  • M558
    Z Probe type 5, input 0, invert yes, dive height 5.0mm, probe speed 120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03

    and if it is triggered:
    M558
    Z Probe type 5, input 0, invert yes, dive height 5.0mm, probe speed 120mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03

    So i guess my problem is "input 0"



  • @xxexx said in Duet 2 Wifi - TRONXY Z Probe Woes::

    if i activate the probe via "m558 P5 I1"

    before you manually put in that command



  • If i restart the board (sensor does not show red "1000" when triggered:

    M558
    Z Probe type 0, input 0, invert no, dive height 5.0mm, probe speed 0mm/min, travel speed 6000mm/min, recovery time 0.00 sec, heaters normal, max taps 1, max diff 0.03



  • there must be something wrong with the lines you put in. Maybe hidden control characters
    please delete the existing M558 lines completely and retype the M558 P5 I1 command by hand into the config.g. and check with M558 after restarting



  • I did exactly that - i commented the old m558 command and pasted "M558 P5 I1" into the config.g. Then i packed it into a new config.zip and uploaded it + restarted the board: sensor cannot be triggered.

    Then i pasted and send "M558 P5 I1" manually - it works. (sensor lights up in the web configurator).



  • @xxexx said in Duet 2 Wifi - TRONXY Z Probe Woes::

    I did exactly that

    no you did not. please reread what i wrote.



  • ok, now i deleted all M558 lines and manually retyped "M558 P5 I1", uploaded and restared - no change



  • if i type the same command it works

    My config.zip includes on "SYS" folder with all the *.g files.

    Z-Probe
    M574 Z1 S2 ; Set endstops controlled by probe

    M558 P5 I1 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
    G31 P500 X100 Y100 Z0 ; Set Z probe trigger value, offset and trigger height
    M557 X15:15 Y15:315 S20



  • that is very strange. what firmware version are you running?

    also please post your config.zip file



  • M115
    FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.02(RTOS) ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2018-12-24b1



  • I see some of these reports have a probe speed of 0 and others 120. That looks odd to me.


Log in to reply