Posts made by fcwilt

@Dad003

I had my bed being lifted at three points, so as to allow auto leveling.

I used steppers with integral planetary gearboxes. He are most of the parts related to the Z axis. It is quite simple, to my way of thinking.

Regards, Frederick

@Snippy said in Z wont go to the corect dept when printing.:

My problem is that after get a height map from G29 the map does nothing to compensate when printing, Z does not moove in -Z only in Z+.

Well how it should move would depend on the height map values and the height map value nearest to where the Z=0 Datum was set.

If the Z=0 Datum happened to be set equal to the lowest point of the mesh then movement would only be in Z+, as all of the other points, being higher, would need to be lowered.

Frederick

@Snippy said in Z wont go to the corect dept when printing.:

@fcwilt
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_testing#calibrate-the-z-probe-trigger-height
This is why

OK - so the bed was just touching the nozzle at that point when you set Z=0?

Frederick

@Snippy

G1 Z-1.97 F50 ; Nozzle Z0 Y200 X160
G92 Z0
G1 Z5
G30 S-1

Why are you doing the G92 Z0 - that is quite likely going to mess things up entirely.

Before you can use mesh compensation you first have to insure your Z probe is correct configured so that setting the Z**=0 Datum**, using G30, gives the correct result.

After doing a G30 (usually at the center of the bed) you can then, using the DWC, "nudge" the bed toward the nozzle of the hotend. When the bed just touches the top of the nozzle the DWC should report the Z position as 0 (zero).

If it does not you need to adjust the Z trigger height of your Z probe configuration until you do get Z=0 when the bed just touches the nozzle.

It will like take several attempts to find the exact value you need for your Z probe.

Once the Z probe is working then and only then can you create an accurate height map. You must always use G30 to set the Z=0 Datum BEFORE using G29 to create the height map or when loading the height map.

Frederick

@jensus11

In my opinion your best bet is to replace that sheet of magnets with 3M flexible magnetic self-adhesive sheet.

I've used that with all sorts of Z probes and they seem to work just fine.

I used to be a fan of BuildTak until the went with a sheet of little magnets - I've moved on from them.

Frederick

@engikeneer

Thanks for the feedback.

I shall proceed as you suggest.

Frederick

Hi,

As part of my ongoing upgrades to what started life as a small, inexpensive Chinese CoreXY printer, I have added a tool board.

It worked fine so I began to check out input shaping.

I had no issues recording different profiles but am at a loss how to move forward.

Consider the example graph from the Duet documentation:

Just one big peak easy to focus on.

Now here is my recording with no shaping applied:

Big peaks in many locations.

So what is my next step, other than tossing the printer into the nearest dumpster?

Thanks much.

Frederick

@Timothee-Leblond said in Z configuration for sensors:

@fcwilt
Thanks for the tip, I'll do that in the future.

But I'm not sure it will solve my problem right?

No, nothing to do with your problem - it just makes things a bit simpler in that if you make a change to homing code for one axis (X Y or Z) you don't need to make the same change to homeALL.g

Frederick

@Timothee-Leblond

For the sake of simplicity and not duplicating code this is how I code homeALL.g.

M98 P"homeZ.g"
M98 P"homeY.g"
M98 P"homeX.g"

You can change the order as best for your printer.

Frederick

@Timothee-Leblond

And the MicroProbe is responding to M401 and M402?

I was never able to get that working. I will try testing my setup again.

Unrelated but possibly of interest:

In your homing files you have

M400
M913
M400

As far as I know they are serving no purpose.

Also for your "coarse" and "fine" homing moves you have the same F values. Normally the "fine" move is done at a much slower speed. I don't see the need to do the same move twice if they are at the same speed.

Waiting for verification that M401/M402 are working for you.

Thanks, Frederick

@elmoret said in Duet 2/Duex5 looking for a good home:

@fcwilt that’s fine, I can not give you store credit if you insist

support@filastruder.com, let me know box size and weight, I’ll send a label.

I know you all. Store credit is just fine.

Where should I send the package?

Frederick

@elmoret said in Duet 2/Duex5 looking for a good home:

@fcwilt that’s fine, I can not give you store credit if you insist

support@filastruder.com, let me know box size and weight, I’ll send a label.

What store?

Frederick

@elmoret said in Duet 2/Duex5 looking for a good home:

@fcwilt If you can't find anyone, happy to take them off your hands for some store credit and shipping. I post used Duet 2s for ~$25 and they sell.

I'm just looking for someone willing to pay for shipping.

Frederick

@fcwilt

It turns out I have four sets of the Duet2 WiFi/Duex5 combo.

They tell me they are sad that nobody wants to adopt them.

Frederick

@droftarts

I had a bit of time so I setup a Mini 5+ on my bench - updated to 3.5.4.

It has no other hardware - just a minimal config.g.

I also include creating all of the global variables I normal use to see if that was part of the problem.

So far it is staying connected without issues.

Frederick

@thooms

It's important to differentiate between G32 - bed leveling (auto or manual) and G29 (mesh compensation - mesh creation - mesh loading)

Both require setting the Z=0 Datum using G30.

G32 (bed leveling) should be followed by G30.

G29 (mesh creation or loading) should be preceded by G30.

On a machine that allows auto bed leveling you will likely use G32 (bed leveling) followed by G30 (setting the Z=0 Datum) then G29 S1 (mesh loading).

In that case the G30 proceeding the G29 satisfies the need to follow G32 by G30.

The reason for G30 after G32 is that the leveling process can change the Z position of Z=0 - doing the G30 resets the Z=0 Datum correctly.

Hope that clarifies rather than confuses.

Frederick

@droftarts said in WiFi issues with 3.5.4:

@fcwilt it would be good to work out why it disconnects for you. I’ll ask @dc42 what information he needs to troubleshoot, if you’re willing to give it another go. Otherwise you’re going to be stuck on 3.4, because as far as we’re concerned, the issue is fixed.

Ian

I have a couple of other Duet 3 boards I could setup on the bench IF testing without actually being able to print would prove anything.

There could still be connected steppers, temp sensors, etc - just not assembled into a working printer.

Frederick

@droftarts

Well I updated to 3.6.0 BETA 4 and the WiFi connection failed even sooner than it did under 3.5.4.

The features of 3.6 sound interesting but not at the expense of no WiFi connection.

I was able to revert to 3.4.6 so that is good for now.

Thanks.

Frederick

@droftarts

I gather the Duet WiFi Server at version 2.2.1 doesn't need to change?

Thanks.

Frederick

@droftarts

Thanks much.

I will give that a try and let you know.

Frederick