Dc42 IR probe not triggering DuetWifi on Rostock MaxV2



  • I recently purchased a DuetWifi and an IR probe (along with a few other bits) to upgrade a Rostock Max machine at work (Naval Aeromedical Research). I'm having issues with the IR probe output not being triggered during autocal. I followed dc42's instructions for initial probe calibration and entered values into the config, but then when I run auto calibration it won't trigger. I clearly see the LED turn on and output values (such as 465) via the web interface and on the the LCD while manually calibrating the probe, yet during auto calibration it won't trigger. I've likely missed something or misunderstood and any help would be appreciated!

    ; Configuration file for testing Duet Ethernet and Wifi

    ; Communication and general
    M111 S0 ; Debug off
    M208 S1 Z0 ; set minimum Z -0.2
    M555 P2 ; Set output to look like Marlin
    G21 ; Work in millimetres
    G90 ; Send absolute coordinates…
    M83 ; ...but relative extruder moves
    M550 Prostockmaxv2_01 ; Machine name and Netbios name (can be anything you like)
    M551 Prostock ; Machine password (used for FTP)
    ;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
    M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address

    ;*** Networking - Enable for both WiFi and Ethernet boards.
    M552 S1 ; Turn network on
    M552 P0 ; (0 = DHCP)
    M554 P192.168.1.255 ; Gateway
    M553 P255.255.255.0 ; Netmask

    ; Fans
    M106 P0 S0 I0 F100 H-1 ; Layer fan Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
    M106 P1 S1 I0 F100 H1 T50 ; Heatsink fan Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
    M106 P2 S0 I0 F100 H-1 ; duet board cooling Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off

    ; Axis and motor configuration
    M569 P0 S0 ; Drive 0 goes backwards - X tower
    M569 P1 S1 ; Drive 1 goes forwards - Y tower
    M569 P2 S0 ; Drive 2 goes forwards - Z tower
    M569 P3 S0 ; Drive 3 goes forwards - extruder
    M569 P4 S1 ; Drive 4 goes forwards
    M574 X2 Y2 Z2 S1 ; set endstop configuration (all endstops at high end, active high)
    ;*** The homed height is deliberately set too high in the following - you will adjust it during calibration
    M665 R143 L300.15 B140 H359.8 ; set delta radius, diagonal rod length (Trick Laser 300.15), printable radius and homed height
    M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them
    ;M350 X16 Y16 Z16 E16:16 I1 ; Set 16x microstepping with interpolation
    M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
    M92 X80 Y80 Z80 E92.65 ; Set axis steps/mm
    M906 X1000 Y1000 Z1000 E500 I60 ; Set motor currents (mA) and increase idle current to 60%
    M201 X1000 Y1000 Z1000 E1000 ; Accelerations (mm/s^2)
    M203 X20000 Y20000 Z20000 E3600 ; Maximum speeds (mm/min)
    M566 X1200 Y1200 Z1200 E1200 ; Maximum instant speed changes mm/minute
    M84 S60 ; idle timeout

    ; Thermistors
    M305 P0 T100000 B3950 R4700 H30 L0 ; Put your own H and/or L values here to set the bed thermistor ADC correction
    M305 P1 X200 ; Put your own H and/or L values here to set first nozzle thermistor ADC correction
    M570 S180 ; Hot end may be a little slow to heat up so allow it 180 seconds

    ; Heaters
    ; Bed H0
    ;M301 H0 P1 P39.62 I0.73 D536.1 T1.1 S1 W300 B30 ; negative P means use bang-bang control
    M307 H0 A96.9 C445.6 D23.0 B0
    ; Heater 1
    M143 S305 ; Set maximum heater temperature to 305C, using E3D v6 & PT100 sensor and amp board
    ;M301 H1 P11.27 I1.16 D27.37 T1.1 S1 W300 B30
    M307 H1 A340.7 C160.0 D3.5 B0

    ; Adjustments for J-heads used as dummy heaters on test rig
    ;M307 H0 A250 C140 D5.5 B1
    ;M307 H1 A250 C140 D5.5 B0
    ;M307 H2 A250 C140 D5.5 B0

    ; Tool definitions
    M563 P0 D0 H1 ; Define tool 0
    G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
    M92 E92.65 ; Set extruder steps per mm

    ; Z probe and compensation definition
    ;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
    M558 P2 X0 Y0 Z0 H5 F120 T6000 ; Z probe is an IR probe and is not used for homing any axes
    G31 X0 Y0 Z0.40 P500 ; reads 537??? Set the zprobe height and threshold (put your own values here)
    ;M558 P2 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to modulated, the axes for which it is used and the probe + travel speeds
    ;M557 R140 S20 ; Define mesh grid

    ;*** If you are using axis compensation, put the figures in the following command
    M556 S78 X0 Y0 Z0 ; Axis compensation here

    T0 ; select first hot end
    ;M80 ; Turns on the ATX power supply
    ;M81 ; Turns off the ATX power supply
    ;S106 P2 S0.6 ; Turn on fan 3 to cool Duet board
    ;G28



  • I believe you want mode 1, not mode 2.

    https://duet3d.com/wiki/Connecting_a_Z_probe

    Perhaps something like this:
    M558 P1 X0 Y0 Z0 ; Set probe type and if it's used for axis homing
    G31 Z1.50 P500 ; Set the probe height and threshold (smaller number = further away from bed)



  • Hmm, I was basing my type2 choice off of these instructions
    https://miscsolutions.wordpress.com/2015/02/05/upgrading-the-mini-kossel-to-duet-electronics-part-4-the-z-probe/

    And here it calls the sensor modulated IR…
    https://www.filastruder.com/collections/electronics/products/mini-differential-ir-height-sensor

    My sensor output does in fact RISE as it gets closer to the bed. 0 is output when the carriages are all homed at the top of the towers. And 537 is output when the probe is very close to the bed. It reads 467 @~1mm from bed, then @ ~0.45mm from bed it reads 537.



  • If it is the T3P3 DC42 IR Sensor then those figures are about right and it is defo a P1 it is not a modulated IR Probe as such it is a differential one



  • Thanks for the input folks, I just switched to P1 and now it seems to work OK. Need some further calibrating as it gets much closer to the bed in on the right half than the left, but at least now it's workable.

    I figured I'd throw a print at it and see just how far off it is, but wouldn't ya know it…doesn't print. I load the gcode, hit print, bed heats up, nozzle heats up, G28 homes all three axis, it immediately quits and says print completed... lol


  • administrators

    To confirm, P2 in M558 is for a dumb modulated probe for which the Duet has to provide the modulation signal. My IR probe has its own microcontroller to implement the 3-way modulation scheme, so P1 must be used. See https://duet3d.com/wiki/Connecting_a_Z_probe#Mini_differential_IR_sensor_by_dc42.



  • David - perhaps worth re-wording the Duet and miscsolutions pages to explicitly specify P1 for your sensor?


  • administrators

    @elmoret:

    David - perhaps worth re-wording the Duet and miscsolutions pages to explicitly specify P1 for your sensor?

    It was already mentioned twice in the Commissioning section to use M558 P1, but I've added another short paragraph to make it clear that this applies not only during commissioning.



  • So I just got back to working on the upgrade, got the probing working fine. I ended up having to paint the back of the glass with high temp matte black paint! But that works great now and autocalibration works and all seems to be well… EXCEPT

    I cannot get anything to print for the life of me! I've sliced and diced, I've read and read, I feel like I'm missing something, but no extrusion from a sliced gcode.

    I can manually extrude, the machine moves to given coordinates just fine. If I tell it to print a sliced model, it just heats up the bed, heats up the nozzle, homes all three towers and just stops. No errors are given. It just says the print is 100% completed.

    HELP!? - new thread?


  • administrators

    Please post a link to the gcode file you are trying to print



  • The print going to 100% reminds me of other threads. As well as posting a link to the gcode file, can you also humour an old man and let me know what you have after M555 in your config.g file.

    Edit. Just looked up a few posts and I see it's set to P2 so unless that has changed, just ignore me.


  • administrators

    @superpotatofudge:

    So I just got back to working on the upgrade, got the probing working fine. I ended up having to paint the back of the glass with high temp matte black paint! But that works great now and autocalibration works and all seems to be well… EXCEPT

    I cannot get anything to print for the life of me! I've sliced and diced, I've read and read, I feel like I'm missing something, but no extrusion from a sliced gcode.

    I can manually extrude, the machine moves to given coordinates just fine. If I tell it to print a sliced model, it just heats up the bed, heats up the nozzle, homes all three towers and just stops. No errors are given. It just says the print is 100% completed.

    HELP!? - new thread?

    This usually means that you are trying to print with no tool selected. But you must have had a tool selected when you extruded manually.



  • So here's a link to the MatterControl sliced gcode https://pastebin.com/7UYKev5G

    Yea I'm definitely selecting T0 at the end config.g and again in the custom start code for MatterControl



  • Line 25 "MM17". Duet won't know what to do with that odd gcode command. Wonder if that's was causing it….........



  • Wow, can't believe I didn't see that! It could possibly be, but I'll have to try removing it when I get back to the office. That was there when my Rostock was being run by its original Rambo board….at least I'm fairly sure it was...or I could totally have fat fingered it from an M117 which is likely given the context.

    Sometimes I love what a fresh pair of eyes spots!



  • Let us know if that was the cause - it's just a guess.



  • Well that was it….thanks for catching my glazed over eyeballs! Removed that, works perfectly fine other than the nozzle thinking 5mm above bed is Z0, so now to re-calibrate and print for real.


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.