Best posts made by fcwilt

@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

Hi,

Just for fun I have been experimenting with dual Z endstop sensors, a "normal" one and a "early warning" one.

My current two printers have moving beds on the Z axis and the beds have quite a bit of mass. To avoid possibly slamming into the endstop switch (or end of travel) and possibly causing damage I have tended, in the past, to home at a "safe" speed.

But when I noticed that in firmware 203 that you can specify which physical endstop input to use it occurred to me that it might be possible to change the active endstop input while homing. Short answer - it is.

So I installed two endstop sensors about 30mm apart. Just to be safe, for this test, I used IR sensors which involved no physical contact. I fit a "beam break blade" to the bed that spanned the 30mm so both sensors, when homed, would be activated.

Homing consists of selecting the lower of the IR sensors and moving at a higher than "safe" rate until that sensor is activated. The bed does indeed come to an abrupt and somewhat startling halt.

Now the upper IR sensor is selected and the "normal" home operation is performed at a nice safe rate and the actual home operation is completed.

Now starting homing when the sensors are already activated is a bit different. The lower sensor is selected AND inverted so it is possible for a "pre homing" command to move DOWN, away from home, until the lower sensor is no longer activated. Then the two "normal" homing commands are issued.

When the lower sensor is already cleared the "pre homing" command doesn't have any effect so there is no downward movement at all.

The same could be done with micro-switches with a somewhat different physical arrangement.

So for the effort of adding an extra endstop sensor and setting them up so they function as described I get high speed Z homing with no wasted motion.

Now I need to see what the long term reliability of this approach is.

Frederick

@jrcl

Always glad to be of help when I can. I remember starting out with my first 3D printer and having to climb the learning curve. Pretty soon it will all be second nature to you.

Frederick

@nightowl999 said in Minty Release Manager Install:

@fcwilt

As Minty responded installing it for one browser will not affect the other.

And under Duet firmware 3.4 you can do some truly useful things with the most recent version of BtnCmd.

Motivated by some recent discussions here I set out to devise an easy way to create a variety of heightmaps without having to edit code.

Here is what I was able to do with BtnCmd, a set of controls modifying global memory settings which control the generation of the heightmap.

Each heightmap file created is given a unique name based on the selected settings so I can view or use them as needed.

I'm happy as a clam at high tide.

Frederick

Hi,

You firmware is rather out of date.

I think the current v2 firmware is 2.05.1.

I know that it worked with switches connected to end stop inputs. I had one button that forced a restart (M999) and another that forced an emergency stop.

I have migrated to v3 firmware and no longer have my v2 config file but I think you are missing the T parameter which specifies the trigger number.

T0 specifies an emergency stop.

Frederick

@nedmo

Glad to hear you got it sorted.

Frederick

@bot said in Feedback wanted: conditional GCode without indentation:

I don't see the need for a begin keyword. If is the keyword that starts the block.

Perhaps if a keyword is required at the beginning, we could borrow some LUA parlance and use THEN, so that the parser knows when the conditional is over.

Well in Delphi if you only have one statement after the condition you don't need the begin/end pair. You use them when you have more than one statement.

I always thought that NOT always requiring begin/end even for one statement was a mistake.

Frederick

@hebigt

Not a good idea.

In the course of a day's printing the printer will be homed many times.

There is nothing to be gained by having it home on power up and it's possible that something could go wrong.

Frederick

Hi,

As the capabilities of the Duet firmware have expanded so has the number and complexity of .G files that I am installing on the Duet boards.

The limitations of the DWC editor make creating/maintaining these files less than "fun".

I have been using a Windows based editor for years now, for general text file creating/editing (as opposed to a document creation/editing tool like Word).

I recently looked into the capabilities of this editor to deal with files on an FTP server. The Duet firmware offers the needed FTP services.

I am happy as a clam at high tide. I have all the power of this editor and it makes dealing with the files being on the Duet about as simple as could be expected.

If anyone is interested I could go into greater detail.

Frederick

@Kolbi said in Automatic Bed Leveling with Conditional Gcode Iterations:

Thanks @fcwilt! I didn't know I was messing that up. I re-read the gcode documentation on this, I believe the following would be the most efficient.

M104 S[first_layer_temperature]                  ; set extruder temp
M140 S[first_layer_bed_temperature]              ; set bed temp
M116                                             ; waits for all temperatures

Yes that should work fine.

Now what I and others do is start the heating and then do other things that don't need to wait on the temps, like homing.

When all of the "other" things are done then you can use the M116 to wait before proceeding to the next steps.

It can save a bit of time.

Frederick

Hi,

Before we get to your question just a quick note regards M208 and G91/G92

You can use a single M208 to set both min and max values

M208 A-63:63 B-63:63 U-63:63 V-63:63

You might find that a bit easier to use.

You can put G91 and G92 on their own line since they set a mode which remains until changed. So the second G91 is redundant.

Now to your question.

Do you have an end stop defined at the min end of axis B?

The G1 H1 B-1 F6000 is a command to move along the B axis in the min direction until the end stop is activated or the movement covers the length specified.

However if the end stop is already active at the start of the move nothing will happen other than setting the position of B to the axis min of -63.

That sounds like what is happening.

Frederick