Black printbite and IR Sensor - very inconsistent heights?
-
I'll ask Jason again for a sample of matt black PrintBite to test the IR sensor with.
-
Thanks, David.
It does seem to be something to do with the interaction between the PrintBite and the IR sensor. I'm busy printing a mount for the inductive sensor and will try that later.
Is it possible to connect the NPN inductive sensor yo the Z-probe input of the Duet WiFi through a Schottky diode? Is it the Z-Probe_In pin that I connect to the diode and the sensor and then just set it as a switch input?
Thanks.
Richard
-
Is it possible to connect the NPN inductive sensor yo the Z-probe input of the Duet WiFi through a Schottky diode? Is it the Z-Probe_In pin that I connect to the diode and the sensor and then just set it as a switch input?
Yes, see the wiki. If you use the Z probe input then an ordinary small signal silicon diode will probably work too if you don't have a Schottky one.
-
Hi Richard, Generally it has been positive feedback with the IR sensor on the black (matte) PB. Dave will have some to test early in the week. Possibly a silly question but any surface imperfections or scratches on the PB that might be distorting the readings?
J -
Thanks, I found the new one (the format is growing on me) and got it sorted. The applicable lines in config.g are as follows:
[c]; IR Z-probe
M558 P1 H4 F250 T2000 ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X9 Y21 Z2.26 ; Set Z probe trigger value, offset and trigger height; Inductive Sensor
M558 I1 P5 H4 F250 T2000 ; Set Z probe type to digital and the dive height + speeds (I1 = invert signal)
G31 X9 Y21 Z2.26 ; Set Z probe trigger value, offset and trigger height
[/c]I'm constantly amazed at the ease of changing things with the Duet!
Richard
(edited to fix typos)
-
T
I'm constantly amazed at the ease of changing things with the Duet!"One firmware binary to rule them all" (all Duets that is) - with apologies to JRR Tolkien.
Seriously, we want you to be able to change ANYTHING that isn't a 1-off requirement by sending the appropriate GCode, either in config.g or live from DWC or USB. I even have a macro for homing my Cartesian printer and then turning it into a pretend CoreXY printer for firmware testing.
In the unlikely event that your requirement is a 1-off (e.g. the user who recently needed to add a 13th stepper driver), RepRapFirmware is open source so you have the freedom to modify it - and it will stay that way.
-
To close this out - I'm now using a TL-W5MC1 inductive proximity sensor and am getting repeatability of about 0.002mm and the PrintBite is showing as flat to all intents and purposes.
I'm adjusting a few things to now get it level but one step closer and that sensor works well - especially at the price! https://www.ebay.co.uk/itm/5mm-Noncontact-Inductive-Proximity-Sensor-Switch-Detect-DC-6-36V-NPN-TL-W5MC1-/253114333447
Richard
-
My results with the matt white Printbite+ with a grid.
I purchased my sensor more than a year ago and it is not a surface mount board. Would it be worthwhile to put some electrical tape in the corners and define points there for probing? I really like both this sensor and Printbite but if one has to go unfortunately it will be the sensor. 
-
I'll ask Jason again for a sample of matt black PrintBite to test the IR sensor with.
Any update on this? I've been waiting to see someone's results for a while as my old gridded printbite gives horrendous IR probe results
-
I've just chased for samples again.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Any chance yet to re-test the IR sensor with PrintBIte?
-
Thanks for the reminder, I've chased again for a sample.
-
Hi,
Would TL-W5MC1 be better than the cylinder inductive sensors or would they be equal in experience and deviation.
Please let us know of ur experience. -
I use the black matte printbite with an ir sensor I got off ebay. It's quite consistent when doing mesh leveling, but sometimes homing is a bit off compared to the leveling.
And here you can see the center point, which is the same as the homing probe point, is off by 0.03mm
-
To get accurate homing, make sure that the XY position at which you home Z coincides with one of the points in the mesh. This isn't as easy as it sounds, because when you execute G30 to home Z, probing is done at the current location; whereas when you use G29 to generate a height map, the nozzle position is adjusted to allow for the offset of the probe. So in homez.g and homeall.g, choose the XY location that you send the nozzle to before you execute G30 so that it is at the location of a probe point close to the centre of the bed minus the Z probe XY offset that you specified in the G31 command.
