@MaxGyver i use 2 kinds of probes on my CNC- an aligator clip to connect to the tool/touch-off plate for Z and a baby reinshaw type probe for X-Y.
the touch off plate will probe twice for setting Z.
the X-Y probe i think will only touch once.
I am not currently near that machine but will be over the weekend. i will try to make some experiments and report back.
sinneD
@hpiz i am literally struggling with today too....
I think that Duet for a router or CNC is fine. the problem is we need to config EVERYTHING.
i was thinking that my estop button will cut motor power only, not controller power.
problem is, i think that the system will still try to move the motors with the 5V controller input power.
@chrishamm said in Question about possible firmware change:
I can confirm it works well in v3.5.0-rc.1+.
Is this documentation current?
https://docs.duet3d.com/en/User_manual/Tuning/Macros_tasks#naming-and-ordering-macros
I would like to ask that a verbose option be added to probe commands so the trigger value gets output to the console.
Just like the output of G30 S-1 but continous/ on the fly as the machine probes insead of stopping at the trigger height.
Why? if the probe is configured with an A and S parameter, the probe will re-probe until the probe tollerance is less than the S parameter. I think it is usefull to be able to read those values.
So for example, if you invoke a P parameter for probe point numbers to level the bed via-
G30 P0 X20 Y190 Z-99999 ; probe point 0 near a leadscrew
G30 P1 X180 Y190 Z-99999 ; probe point 1 near a leadscrew
G30 P2 X100 Y10 Z-99999 S3 ; probe point 2 near a leadscrew and calibrate 3 motors
I would like to see the initial Z trigger height and sucessive probes, or at least the deviations from the reference value.
respectfully submitted,
sinneD
@Joeyhershey did you get this sorted?
It took us a while to figure out the RRF behavior when developing Euclid because this wasn't well documented. The RRF2 & RRF3 examples have comments within then with regards to wrapping the gcodes and macros within M401 and M402 sets.
as dc42 explained, RRF's deploy token is checked internally, you want to be consistent with M401/M402. this advice is based on experience, not opinion.
M401 and M402 are the NIST standard gcodes for probe deploy and retract. At least thay have been the gcodes in reprap for 15 years +/- now. They call the deplyprobe.g and retractprobe.g macros. As dc42 pointed out, the associations are built in, don't rename them.
Looking at your files, you have mixed BLTouch commands and Euclid commands. I recommend that you get rid of all the old BLT stuff. I don't know how BLT works with RRF, but the M280 may be triggering the probe token as well.
you can check with something like this-
echo "Probe Value =" ^sensors.probes[0].value[0]
If you are clever, you can write a conditional gcode that could check for probe delployed or not and have that in your files.
Lastly, you might notice why the Euclid examples do not check the check the OM probe variable for deploy: we check the actual probe value to ensure pickup in case of a mis-deploy.
sinneD
@Hernicz you are still not understanding that if you dont reverse the Z axis far enough to clear the backlash/friction of the mechanical system this is not yeilding any real results. All you are measuring the relative slop in the system.
please reread my comment- i said one full MECHANICAL step of the system.
If you are trying to claim any accuracy by 'preloading' the touch probe so it does not have to travel as much, then what happens when you run over a crumb or scar in the bed?
@dc42 said in Secondary Dive height for probing:
@Hernicz I considered this and decided it was a good idea, so I've implemented it ready for release 3.5.0-rc.1.
I tested it by probing 135 points on a E3D tool changer (probing speed 600mm/min) with the M558 A2 S0 parameters used to force two probes per point. With both dive heights set to 3mm the time taken was 3min 20sec. With the dive heights set to 3mm then 0.5mm this was reduced to 2min 27sec.
Can you post up a summary of the trigger values please?
Change it to min dive height of at least a 1 full mechanical step of the Z motion system (ie, > 2mm for a 2mm lead screw) and compare those numbers.
What probe are you using? If you want speed, Euclid with D2F-5 switch, we've gone as fast as 500mm/sec travel speed with repeatable and predicable results. OEM says not faster than 30 operations per minute for electical component life.
@CNCModeller Did you get this working ?
I had my Diabase version connected to my Tiny-M at MRRF and people really liked it.
@Hernicz said in Secondary Dive height for probing:
@sinned6915 I do G32 with 0.001 precision with really good repeatability. Probe also set up to 0.001.
Of course if you probe with different speed or dive height the measurement will be off, but RepRap only renders the probing successful if you have the same values on two consecutive probing moves.
The purpose of this request is to lower the dive height on secondary/finishing probing moves thus speeding up the process
I disagree. That thinking is false economy.
By not reversing the Z motion system past the amount of inherent Z backlash, you are not measuring anything. All you are doing is 'measuring' the turn of a stepper motor withing the backlash amount.
Consider that your claimed 'precision' is 1/3 that of the thickness of the ink drawn with a Sharpie marker or 1/5 the thickness of a piece of lint. Measure those and then re-state your claim.
@infiniteloop i have an optocoupled relay triggerd by PS_ON pin on the Duet2 board and always on 5V power supply.
I see how you have configured the pin state for enabling the PSU, now I am wondering how to combine the two functions- the screen macro and physical button.
This could apply to say dust collection on a CNC machine too.
@infiniteloop said in PanelDue ATX power supply on off toggle?:
@CNCModeller I noticed early that some options will always be missing from the crammed interface of the PanelDue, so I added some physical push buttons which allow me to trigger deliberate actions - one of them is to toggle ATX Power on/off (after a confirming dialog).
How did you do this? I assume that you have some sort of switch connected to an I/O pin?
I was contemplating the same thing, then came here to search if someone had already done something similar. I thought about actually polling the voltage, not status.
if boards[0].vIn.current < 23
M291 S2 R"Power State" P"Turn Printer Power On?"
M292 P0
M80
G4 P1000 ; wait 1 second for power to stabilize
elif boards[0].vIn.current > 23
M291 S2 R"Power State" P"Printer Power Off?"
M292 P0
M81
else
M81
@dc42 said in Secondary Dive height for probing:
@Hernicz are you saying that when doing multiple probes at the same point (i.e. the M558 A parameter is greater than 1), you would like the second and subsequent probes done using a lower dive height, as well as using a different speed?
If so, that sounds like a good idea to me and one that I am prepared to implement.:
Would you then reset the baseline for repeatability and tolerance checking too? Seems that would be in order as well.
But, I have to say that there is a pratical limit to all this and some of this is creating a false sense of precision....
Repeating the same dive height at the same point will only repeat the error of backlash in the mechnical system.
People are chasing phantom 0's just because the software believes that they are there.... 0.0025mm for example is just silly. People really don't understand what it takes to gauge this, let along repeat this measurement in the real world. The slightest breath will throw the needle on a gauge amplifier that much and more. There are reasons metrology is performed in controlled environments. A 3d printer is anything but.
Look closer at the homez.g macro example and the bed4point.g-
homez.g calls for probe deploy, then invokes an M98 to call up bed4point.g
in the documentation we try to describe how to wrap M401/M402 around macros to prevent this.
as those are 2-3 years old at this point, we should probably look at the and add more confitional gcode to see if the probe is deployed or not in bed4point.g
I am having some issues with ftp - the controller seems to limit the file list to about 60 lines and a few characters.
using filezilla with max connections of 1.
feature? bug? easter egg?
i tried seaching the help files but no luck. ftp as a search term is not specific enough.
sinneD
@dmbe11 I am still looking at your files.
question: what memory card do you have in your board? Size? File system format?
@dmbe11 the behavior you describe of moving straight to the dock then shaking is not normal.
the methodolgy is covered i the Eucild help files-
https://euclidprobe.github.io/06_rrf3.html#reprap-firmware-3x-usage-overview
please post your files. we will be happy to help.
sinneD
@jens55 Euclid has sucessfully installed on Ender3's with auto deploy and stow.
You can always simplify and nad deply.
disclaimer: I am the one behind Euclid probe.
@dc42 i am using a detachable probe. here are my configs and macros:
; Mag Probe Settings
; RRF2 was M558 P5 H8 F300 T9000 A1 S.01
; set Z probe type to switch and the dive height + speeds. Probe A times
M558 K0 P8 C"^zprobe.in" H10 R0.5 F360:120 T9000 A5 S0.01
; M558 K0 P5 C"^zprobe.in" H10 R0.5 F200 T9000 A1 S0.03
; K0 for probe 0, P5 for filtered NC switch, P8 for UN-filtered NC switch, C for input pin,
; ^ for enabling the native pullup resistor on Duet2 hardware running RRF3
; H dive height of 8mm, F240/120 probing speed 4-2mm/sec, T9000 travel speed 150mm/sec,
; A3 number of probes 1, S0.01 max tolerance of 0.01
;
G31 K0 P500 X-16.4 Y-29.27 Z3.12 ; for snap action switches DF2 etc
deployprobe.g
; ***********************************************************
; Euclid Probe Fixed Dock M401 Deploy Probe Macro
; saveas system/deployprobe.g
; comments and echo statements throughout are provided for convenience
; ***********************************************************
; echo "Running deployprobe.g"
; echo "Homing Check"
if !move.axes[0].homed || !move.axes[1].homed ; If the printer hasn't been homed, home it
M98 P"0:/sys/homexy.g"
; uncomment next line to echo the probe deploy state
; echo "Object Model Deployuser token =" ^sensors.probes[0].deployedByUser
M564 H1 S0 ; Allow movement BEYOND axes boundaries (for Y to reach probe dock)
G91 ; relative positioning
; echo "Lift Z in advance of deploy"
G1 H2 Z15 F3000 ; move Z 15 for clearance above dock.
; ; need to figure out some safety check on this
G90 ; absolute positioning
; echo "Probe Value =" ^sensors.probes[0].value[0]
if sensors.probes[0].value[0]!=1000 ; if sensor is value other than 1000 do this
; uncomment next line to echo the probe deploy state
echo "deployuser token = " ^sensors.probes[0].deployedByUser
echo "Probe State = " ^sensors.probes[0].value[0]
abort "deployprobe start value Probe already picked up. Manually return probe to the dock"
; if we're here we know it's becasue the above is true which I assume is because you have an NC switch as a probe.
; echo "Passed first logic test to deploy probe"
; Dock side position is at X0 Y20
; Docked probe postion is at X0 Y-16
; Dock exit point is at X65 Y-16
G90
G1 X0.0 Y20.0 F6000 ; move adjacent to probe dock location
M400 ; wait for moves to finish
G4 P250 ; wait 250 msecs
; echo "Probe Pickup while loop running"
; uncomment next line to echo the probe deplot state
; echo "Object Model Deployuser token (before while loop) = " ^sensors.probes[0].deployedByUser
; while sensors.probes[0].value[0]=1000
G90
G0 X0.0 Y-16.0 F3000 ; move over dock
M400 ; wait for moves to finish
G4 P250 ; pause for pickup
; echo "Probe Value =" ^sensors.probes[0].value[0]
G0 X65 Y-16.0 F1200 ; slide probe out of dock - slowly
M400 ; wait for moves to finish
G4 P250 ; pause 1 seconds
; echo "Move to Center"
G1 X150 Y150 F3000 ; move bed to clear probe from build surface
M400 ; wait for moves to finish
G4 P250
; echo "Probe Pickup while loop complete"
; uncomment to echo the probe deplot state
; echo "Object Model Deployuser token (after while loop) = " ^sensors.probes[0].deployedByUser
if sensors.probes[0].value[0]!=0
; uncomment to echo the probe deploy state
echo "Object Model Deployuser token (in abort if section)= " ^sensors.probes[0].deployedByUser
abort "Deployprobe endvalue not 0 Probe not picked up! Deploy cancelled."
echo "Restrict to Print Bed Size"
M564 H1 S1 ; Restrict movement to within axes boundaries (for normal Y movement)
echo "Macro deployprobe.g complete"
retractprobe.g
; ***********************************************************
;
; retractprobe.g
;
; ***********************************************************
; M118 S"Redefine probe as NC"
; M558 K0 P5 C"^zprobe.in" H8 R0.5 F200 T9000 A1 S0.03
; M400
; echo "running retractprobe.g macro"
; echo "deployuser token= " ^sensors.probes[0].deployedByUser
; echo "Probe Value = " ^sensors.probes[0].value[0]
if sensors.probes[0].value[0]!= 0
echo "deployuser token= " ^sensors.probes[0].deployedByUser
echo "Probe Value = " ^sensors.probes[0].value[0]
abort "retractprobe: Probe not currently picked up!"
; echo "pass first logic loop"
M564 S0 ; allow movement outside of print area
; echo "deployuser token= " ^sensors.probes[0].deployedByUser
; echo "Probe Value = " ^sensors.probes[0].value[0]
G90 ; absolute positioning
; G1 X100.0 Y4.0 Z7.89 F12000 ; move to the starting point
; G1 X100.0 Y-27.0 Z7.890 F12000 ; move to the starting point Glass Bed
G0 X100.0 Y-16.0 Z9.0 F12000 ; move to the starting point Bare Alum
G0 X45.0 Y-16.0 F6000 ; move to the entry position for the dock
G0 X2.0 Y-16.0 F3000 ; move to the dock position
G0 X2.0 Y0.0 F12000 ; move to the side adjacent to the dock
M400
G4 P250
G0 X100.0 Y0.0 F12000 ; move to the right to clear dock
G0 X145 Y0.0 F6000 ; move to start point at middle front
M400
G4 P250
M564 S1 ; limit axis to print area
; echo "complete movement commands"
if sensors.probes[0].value[0]!= 1000
echo "deployuser token= " ^sensors.probes[0].deployedByUser
echo "Probe Value = " ^sensors.probes[0].value[0]
abort "retractprobe: Probe not correctly dropped off in dock!"
; echo "deployuser token= " ^sensors.probes[0].deployedByUser
; echo "Probe Value = " ^sensors.probes[0].value[0]
; echo "retractprobe.g macro complete"
@chrishamm so do you you use the 'Filaments' to do things like organize, track usage, retraction and such too?
@tylersuard said in Problems with macros:
Sometimes my nozzle will rake across a particularly rough patch, and cause a layer skip.
THAT would be the thing to spend time on. You should not be getting rough patches like that often enough to want to write a macro to work around it.
An occasional ooze or blob is one thing, but as I read your post, if this happens often, let figure what is causing the condition and fix it.