Topics created by mendelevium

@mendelevium if you're still out there kicking this around
https://forum.duet3d.com/topic/11581/duet-controlled-micro-mill?_=1746675486410

@mendelevium Things to try. 1. I have never seen such a high pressure advance setting (S1.25). Are you sure that's right? Try reducing or even disabling it just to see what difference it makes. 2. Do the blobs coincide with retractions? If so,look at your retraction settings but note that there is an interaction between PA and retraction so do the PA first. Using firmware retraction wil enable you to change settings "on the fly". 3. You haven't specified what filament you are using. Have you printed a temperature tower to ascertain the correct value to use for your machine! If not, do so. 4. If the blobs are seemingly random, try another reel of filament but do (3) first. 5. Try an extrusion multiplier of 0.95 or even 0.90 just to see if that helps.

@mendelevium
Basically, the PS-ON pin supplies a switched negative ground. Taking a positive from the PSU 12v provides a supply of 12vdc. I use simplify 3d so I put M80 in my start script when a print is started and M81 when a print is finished after all cools down and machine returns to idle state. This can be used to trip my contactor and switches everything off. Thanks for the tip DIY-O_Sphere.

Will it be possible to determine backlash with the X-carve XYZ touch probe?

I'm sure there's a macro to find the center of the XY-hole, but can it spit out backlash numbers, too?

@PCR unless you are running at 10,000mm/s^2 acceleration in z then I think gravity should still win right? Unless there is an awful lot of 'stiction' in the z bearings.

If it is from Z hop, surely you are always approaching the axis from the same direction (downwards), so backlash shouldn't be an issue? Or am I being naive and missing something...?

@jay_s_uk

G91 ;realtive mode
G1 Z275 F1000 H1 ; move Z rapidly / 300mm up/ until Homing is triggered - the 275 is larger than the stroke.
G90 ;absolute mode
G1 Z256 F10 ; retract z 3mm slowly (Z 259 reaches the microswitch) so it backs off 3mm)
G91 ;realtive mode
G1 Z5 F0.1 H1 ; rehome at slow speed (then home very slowly)
G90 ; return to asoute mode
G1 Z261 ; back off (this goes down a bit away from the switch)

The exact details on how to find your probe offset using G30 S-1 can be found here: https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing

Then you can use G30 to accurately home the Z axis to find the Z0 point using the probe.

G29 uses a series of G30 probes are various points to make the map.

If you're using an endstop at the high end of Z travel for homing, use that first for course homing, and then use a G30 at the center of the bed to establish the true Z0. If you use only the endstop at the high end you're likely to have an offset and inaccurate z position unless you measure the distance from the bed at z0 to the endstop at zmax very accurately.

@Phaedrux
that worked thank you!

@mendelevium said in precisionpiezo adaptaion:

M558 P1 I0 C"zprobe.in" H5 R0.2 F1000 X0 Y0 Z100 ; piezo

I0 is not used in RRF3. If you need to invert the probe signal, use a ! before the pin name, like this `C"!zprobe.in"

That may be the source of your probe already triggered message.

I don't understand what you're trying to do with the Z probe zeroing macro. With the steps you're using the G30 S-1 will give you the height you started it from, which is probably why you have a G31 Z of 12mm, which is obviously wrong.
I think you should follow these steps instead.
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing#calibrate-the-z-probe-trigger-height

The piezo board should receive power from the Duet.
you are using the Z probe in connector on the Duet right?

@jay_s_uk That servo arm is as cute as a button, I like it.

@dc42
took off that comment and the error vanished... thanks so much
the matter is closed..

If you have your M208 limits set correctly the firmware should already prevent travel beyond the limit switch or defined printable area. Otherwise remapping to a estop trigger is the best option.

@mendelevium said in LASER Filament sensor issues still haunting me:

I have firmware version 3.

Exactly which version? Send M115 to find out.

@mendelevium said in Filament Monitor problem:

My slicer profiles I have created them to suit different printers and I have them sub divided with different materials @dc42, I have not tried it yet but I think it makes sense that the commands are put in the starting scripts with different R values according to the sensitivity of material being used.
"M591 D0 P6 C"E0stop" R40:120 E3.0 S0
M591 D1 P6 C"E1stop" R40:120 E3.0 S0"
what do you think about this idea?

When using the laser filament monitor, that makes sense. In general it should not be necessary when using the magnetic filament monitor, except possibly when using TPU.

https://duet3d.dozuki.com/Wiki/Pressure_advance

@mendelevium
I have reduced the jerk value considerably an have have obtained good results. IT is obvious that when the ratio of motor movement to axis movement is high as in the case of a ball-screw,the jerk is magnified. I have reduced the value of M566 from 900 to 120 and all the noise has vanished and there seems very little reduction in speed I have another tweak in the pipeline but will open a new post as it is not related exclusively to jerk issues

@mendelevium, M900 sets pressure advance in Marlin. For some reason they chose not to use the M572 code to control pressure advance, which we had introduced and allocated in the RepRap wiki several years previously.

It's not common to set pressure advance in the GCode file. You would normally set it in config.g or in the filament files. So I suggest you remove that M900 command from your slicer start code.