@dc42 said in [Dave's so proud]

So if P7 worked, he must have his BLTouch connected to the Z endstop input; whereas P9 requires it to be connected to the Z probe input.

One thing I have noticed is that folks who are not good at attention to details often struggle with configuring 3D printers (and other things as well).

Aside from the occasional mistake they we all make from time to time it is clear you very much know what you are doing.

Thank you for your hard work, the Duet family of products has made building my printers so much easier and enjoyable.

Frederick

@dc42

1 - END by itself is easy but if you don't see it in context you don't know what it is the end of. It might be better to have unique keywords - ENDWHILE, ENDIF or something along those lines.

2 - I would make the use of the new keywords mandatory. Yes existing users would have to do a bit of work but it would keep things simple and consistent for all in the future.

3 - While you are implementing the change I would also suggest that a REPEAT/UNTIL or a DO/WHILE loop be implemented - the type of loop that always runs once.

Frederick

@kwad3d-0 said in BL Touch Issues... Again and Again...:

@fcwilt my height map looks better then that however still lifts off on one side by about 1mm. So You don't know what your talking about and are just trolling at this point. You have not contributed anything at all besides criticizing my terminology I use. I don't want you to comment any longer and be on your way now...

I think you are confused about who may be a troll.

But since you are so wise I'm sure you can solve this simple problem on your own.

Have a great day!

Frederick

@alankilian said in My wish : Inputs debouncing:

Thank you for letting me get confused at times.

We all get confused, make mistakes, make assumptions, read things wrong, etc.

It's just the nature of forums.

Generally we as a group get it sorted in the end.

Frederick

@dc42

I am very happy with RRF v3.

I did not find the changes from v2 to v3 as extensive as I first imagined.

As I have progressed from v3.0.0 to v3.1.1 to v3.2.0 to v3.2.2 I have not encountered any changes I had to make.

I did make changes to take advantage of new features but they were changes I chose to make, not had to make.

I am very impressed with the folks who are developing the firmware for the various products.

As in many aspects of life some few folks are hard to please and I see little reward in trying to.

Kudos to you all.

Frederick

@BDPrinters

The last G30 P2 has F550 instead of Y550

Frederick

@fcwilt

Hi,

Here is a link to a quick-and-dirty video showing the mini linear guide at work.

Mini Linear Guide At Work

It was hard to get a good view - sorry.

Frederick

Hi,

It would be nice if you could add some white space at the left margin of the editor.

As it is the cursor tends to be hard to see when at the left margin.

Thanks.

Frederick

@apairofcleats

Just remember to follow the correct procedure.

You must first update to 3.0.0 then to 3.1.1

Upload Duet2and3Firmware-3.0.zip

When asked let the update proceed.

Upload Duet2and3Firmware-3.1.1.zip

When asked let the update proceed.

If all goes well you should be running firmware 3.1.1 and Duet Web Control (DWC) 3.1.1

Frederick

@cando415

You have this in your Y homing file:

G1 H1 Y+360 F6000 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000       ; go back a few mm
G1 H1 Y+360 F360  ; move slowly to Y axis endstop once more (second pass)

All three of those moves are in the same direction.

Based on the G1 H1 moves the G1 Y5 should be G1 Y-5.

Frederick

@micaheli said in Dual Z endstops and G30:

@fcwilt OG is "original gangster". Means old school.

I guess I just have hope that there would be a fancy new way that works better. Guess not. Boo.

I have tried many and they often sound great but end up disappointing.

The BLTouch may be old school but it just works.

Here is how the coil will be mounted (more or less)

@micaheli said in Dual Z endstops and G30:

@fcwilt I just can't do it. I have BL touches on my other printers... But it's just such an OG.method. I wanted something fancier.... I guess nothing exists... Klicky? Lol

OG? What does that mean.

I have tried my every type of Z probe I was able to get and I have returned to the BLTouch.

Inductive are quiet but not very accurate.

The Euclid involved mounting it and dismounting it.

A BLTouch type from another company simply didn't work and I tried six of them.

IR types are fussy about bed surfaces and I use a magnetic system with different surfaces, and that got the IR kicked to the curb.

Now with the SZP the BLTouch is only clicking when setting the Z=0 datum (one click) or probing for bed leveling (three clicks) so the annoying noise is not an issue.

Frederick

@micaheli said in Dual Z endstops and G30:

@fcwilt Are you just referring to the Duet3D Scanning Z Probe/SZP/Coil? That's what I'm using too. I just don't consider it a viable touch probe. Yet.

Yes, which is why you see a BLTouch there as well.

Frederick

@micaheli said in Dual Z endstops and G30:

@fcwilt what makes that an E3D scanning probe?

The design is not complete yet.

The SZP board is there.

I'm working on mounting the coil.

Give me 5 minutes and I can show you the first attempt.

Frederick

@micaheli said in Dual Z endstops and G30:

@fcwilt unfortunately my z probe is the scanning probe, and consistent it is not for single "touch" probes.

Which is why all of my printers now have, or will shortly have, both regular Z probes (BLTouch types) and the E3D Scanning Z probe.

I was working on the design for the last printer just before I saw your reply.

Frederick

@micaheli said in Dual Z endstops and G30:

@fcwilt So you recommend having a hard min stop adjusted to nozzle height for the actual bed itself, rather than a nozzle style? I liked the concept of having a nozzle tip = zero every time probing method. Regardless of nozzle. The way you describe would need offset tweaking every time I swapped nozzles and such.

I do like the simplicity of your method and I even started designing mounts around that, but veered off into the method I have now.

Either way, that document needs to be updated.

I also have a Z probe and use that, when needed, to establish the Z=0 Datum.

So with the two Z end-stops you get the benefit of fast and simple homing along with the leveling of the bed, even if it is not perfect it can be very close, and with the Z probe you get the accuracy you desire.

Another minor benefit of homing Z first is you don't have to do any fussing about with moving Z "out of the way" before homing X and Y, you just end Z homing by moving to, say, Z=5.

You can then use the Z probe to do auto bed leveling (see G32) where it will tweak the individual Z steppers as needed to get the bed as close to perfect as the Z probe allows.

And then anytime you can use the Z probe to set the Z=0 Datum. The auto bed leveling will do a great job but it can throw off the Z=0 position a smidge so it is advised to always follow auto bed level with setting the Z=0 datum.

I had a printer with three Z steppers and it was fast and quite amazing at get the bed level.

Just as a reminder you should set the Z=0 datum:

• before creating a height map
• before loading a height map
• after auto leveling the bed

Frederick

@micaheli said in Dual Z endstops and G30:

@fcwilt They are sexbolt style endstops. So the nozzle touches each of them, then moves to the other and back, etc.. To level the bed. Each endstop has it's own input io3.in and io7.in. Each ties to it's own stepper for the corresponding side.

They are not end-stops then.

Z end-stops require not XY motion, they are triggered by the Z axis reaching a certain position.

If you have two Z steppers you need one end-stop for each.

Then in the config file you specify the configuration something like this:

M574 Z1 S1 P"pin-name-for-endstop-1 + pin-name-for-endstop-2"

When done this way each Z stepper is run until its associated end-stop is triggered.

If the end-stops are carefully positioned the bed ends up level.

I highly recommend using two actual Z end-stops.

It makes homing the machine simpler by removing any interaction between axes.

Frederick

@dc42

I agree that adjusting M208 is the most practical solution given the number of customers that would benefit from you spending time doing something in the firmware.

I have one routine that I can pass a tool number, a probe number or put/get flag and it adjusts M208 for each situation.

The code is not complicated, relies on axis and offset values from the object model to do most of the work.

The only hardcode values are those that "expand" M208 to allow safe access to the tool docks.

The only thing I haven't solved is a way to create a "barrier" around the Z axis hardware, which can be struck when doing put/get moves if the put/get code has a flaw.

I quite pleased with the result.

Frederick

@micaheli

Are the physical endstop sensors that are connected to the board?

Frederick

@dc42 said in Object Model value never seems to change:

@fcwilt object model field heat.heaters[N].state should change when you cycle the heaters in that way.

Yes I did locate that.

I was thinking (wrongly so) that if the tool heater was on standby the tool itself would have to be on standby.

It appears that the state of the tool being active/standby in my mind is more like selected/not selected

Thanks for the help in understanding things.

Frederick