Topics created by Ray11

@ray11
Is the motor louder or the belt/pulley combo? (2GT and GT2 standards are not exactly the same )
Does the belt rub somewhere (against the idler pulleys)?

@ray11 said in IDEX z probing question:

Do you know if there is an example code I can look up to adjust the leadscrew?

You mean like this? https://duet3d.dozuki.com/Wiki/Using_the_manual_bed_levelling_assistant

this has been done a few times, using metal welding wire as a substrate:

https://hackaday.com/2020/03/31/3d-metal-printer-uses-welding-wire/
https://www.youtube.com/watch?v=odGEzRRDfxo&ab_channel=AdrianGerlich

some even professionally
https://www.youtube.com/watch?v=DKkcBoSeUOg
https://www.youtube.com/watch?v=cKxatmf11D4

This method claims to be able to use any wire that heats enough electrically to melt:
https://www.digitalalloys.com/technology/
(so presumably any wire given a high enough voltage, current and thin enough wire) (and a non oxidising atmosphere)

but as @theruttmeister points out there are lots of challenges. For many metals you will want a non oxidising atmosphere as well.

Here is an example of using a z min probe and z max endstop together.

https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+5:+Upgrades/54#s213

The probe fidns the bed and the z max can be used for power failure resume. There is even a macro that will help measure the exact distance of the zmax endstop and save it.

Please update to the 3.01 full release and see if you still have issues.

In some ways, a short across the power supply, SEPARATE from the Duet, is low risk. Either the power supply will shut down, or something in the short are will "give".

But... that's not absolutely certain. Anything could potentially happen when you start talking shorts. For example if the power supply blows something, it COULD momentarily go to almost any voltage on the +12 or +24 or whatever your using for the thing that got shorted.

Having said all of that... soldering to those kinds of strips can be done, can be tested, and can be sealed under "adhesive shrink" (not regular) or a dab of silicone, or hot melt glue, or something else that makes it physically solid.

And then checked with a meter while you flex it.

Go for it.

@Ray11 said in Panasonic Laser Probe for ABL:

they say this type doesn't work on transparent objects. So I guess there isn't one probe that can tick all the boxes.

the one we use for glass work on transparent objects (well, you can hardly get more transparent than clear glass 😄 ) but considering price I really don't see the point

Diagnostic. Pulsing about 1 or 2 per second indicates normal operation.

@Ray11 said in Duet3 and Pi issue:

Thank you, it seems like I put 2 S parameters in M106 which caused the issue.

Odd, normally it just ignores the second one if you provide duplicate parameters.

@dc42 said in IDEX "Smart" Tool Parking Position:

Thanks, that could be useful; for example, to use G29 to probe just those parts of the bed that will be used.

Already been done: https://forum.duet3d.com/topic/15302/cura-script-to-automatically-probe-only-printed-area

I found out that my tpost0.g is corrupted. Recently after updating the firmware, it seemed like some of my files were corrupted.

"The only remaining scenario where the experimental use exception may be used is in the case of an individual’s general interest without any intention to profit. Even in this scenario, the use must only be de minimis, small-scale tinkering."

https://nysstlc.syr.edu/experimental-use-exception-to-patent-infringement/ It may also vary from country to country. I am not a lawyer.

Anyway, that's an interesting design.

M104 sets the temp and releases control. It doesn't wait.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M104_Set_Extruder_Temperature

M109 waits to within 2.5c

https://duet3d.dozuki.com/Wiki/Gcode#Section_M109_Set_Extruder_Temperature_and_Wait

G10 and M116 has the S parameter to specify the tolerance.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M116_Wait

@Ray11 you can see my whole config here: https://github.com/Duet3D/RRF-machine-config-files/tree/master/Creality_Ender_5/arhi-eth-centreZero-xrail-flex3drive/sys

so in config I do

M558 P1 C"zprobe.in" R2 H5 F1200 T3000 A3 S0.03 K0 G31 X0 Y0 Z0 P780

as config is not probing so I put some "low" value for P there (my probe never go below 780 so I use that but you can use P10)

then for homez:

https://github.com/Duet3D/RRF-machine-config-files/blob/master/Creality_Ender_5/arhi-eth-centreZero-xrail-flex3drive/sys/homez_orion.g

G90 G0 X0Y0 F3000 ; go to center of the bed, complain if X or Y not homed G91 ; relative positioning G0 Z5 F900 H2 ; drop bed for 5mm G90 ; absolute positioning G4S3 ; wait 3sec G31 P{sensors.probes[0].value[0] + 8} G30 ; Probe the bed at the current XY position. ; When the probe is triggered, set the Z coordinate ; to the probe trigger height.

So I set the trigger value dynamically just before I'm calling G30.

For mesh leveling bed.g is called when you call M32 so
https://github.com/Duet3D/RRF-machine-config-files/blob/master/Creality_Ender_5/arhi-eth-centreZero-xrail-flex3drive/sys/bed.g

G29 S2 ; delete compensations M561 ; clear any bed transform G31 P{sensors.probes[0].value[0] + 4} G29 S0

Now, this is actually not ideal, it works for me most of the time but since I don't do mesh probing on every print but only from time to time it's acceptable.

What I plan to do when I get some spare time is to rewrite bed.g to not use G29S0 but to actually manually probe every point like is done in the sample here: https://duet3d.dozuki.com/Wiki/GCode_Meta_Commands (look at the example at the bottom) and I'd then do G31 P{sensor.probes[0].value[0]+4} before each G30. But as is now works and I have more pressing things to attend...

@Phaedrux said in DWC Randomly terminate print at start:

Have you tried recently with DWC 2 and RRF 2.05?

I have not, but thanks for letting me know. I'll check it out at some point when I can afford some down-time 🙂

@Ray11 You are welcome

Hi, I later found out that it was in my config.g file while I configured the end-stop setting wrong. The U axis endstop is set to minimum where in reality it should be homing to the maximum. Thanks for the follow-up.

@Ray11 Glad this wasn't terminal. Always a good idea to use keyed headers and plugs!

Ian