@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

@amimafe

Thanks for the feedback.

Frederick

@amimafe said in Layer change detection job.layer:

Yes, that's the other option I had thought of, but I preferred to do it by daemon.g and if a third party manages the machine, everything is integrated with the firmware.

Thank you.

Understood - but the slicer knows what is going on. How would the firmware identify a layer change?

Frederick

@amimafe

All of the slicers I have used have a place to put user code to be called on layer changes.

This is a screen shot from Prusa showing where the code can go:

Frederick

@BDPrinters said in Calibration factors do not equal number of leadscrews:

Yes, that actually seemed to be the problem for the calibration factors not equaling the number of leadscrews. Things seem to be working fine now.

That seems odd since the docs for G30 without a P parameter state the having an S0 parameter is the same as not having the S0 parameter

A few things come to mind:

• the code for G30 S0 has a bug and it doesn't work like the documentation says it should
• the documentation for G30 S30 is wrong
• you changed something else at the same time which actually fixed the problem

I haven't a clue what is going on.

Frederick

@claustro

How many "adjusters" do you have - 3 or 4?

Frederick

@BDPrinters

I think you M671 is wrong.

I think the X50.8 should be the in the 2nd position based on the three G30s but perhaps they are out of order.

Frederick

@BDPrinters

The last G30 P2 has F550 instead of Y550

Frederick

@DieterSw said in 6HC inductive 4 wire endstop wiring:

@Mr-Crispin Why do you think that? I connected BN to 5V_EXT, BU to GND. And BK to iO.in. I might switch black/white to use the NO closed contact but the rest seems correct I think?

Aside from the issue of the signal level being invalid you have it wired correctly in regards to what wires are going where.

I don't know that switching to the NO connection would change the signal level.

If memory serves me I went with NPN devices (rather the PNP) just for this signal level problem. I also remember during testing creating a voltage divider using two resistors to get a suitable signal level.

Frederick

@airscapes said in During Bed Probe G29:

Can you explain the P25 to P500?

When triggered my BLTouch probes read 1000. When not triggered they read 0. The setting of P500 is midway between 0 and 1000.

It has always worked for me.

Frederick

@airscapes said in During Bed Probe G29:

This probe has been in place for a year I have made other maps and tend to reuse them. This has happened with the failure before complete one other time.

M558 P9 C"^zprobe.in" H3 F100 T6000 A3 R1.25 S0.01 B0.
G31 X0 Y-21 Z1.57 P25 ;

In M558:

Change the S0.01 to S0.03

Change the R1.25 to R0

In G31:

Change the P25 to P500

Let us know if those changes help.

Frederick