Dc42 IR probe not triggering DuetWifi on Rostock MaxV2
-
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-sensorMy 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
-
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?
-
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?
-
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.
-
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.
