OK, I think I got it, was not hard to figure out. Seems M584 is order driven. I just changed Z2:4 to Z4:2 and it seem to be working.

Joel

I am using 2.04 for Duet WiFi and DWC.

I have no issue with just using my macro. I was playing with various features of DWC when I noticed the pull down way to run the bed mesh and it did not work the same way.

Thanks
Joel

So, my printer build table is 330x330, the probe is on the left ( min ) side of the nozzle. I have defined the max to this size ( M208 X330 ). If I set M557 to be X0:350, G29 puts the probe at 0 ( seems the right thing to do ) when X position is set to 0, but the X stops when the nozzle hits 330 when trying to do the far side. So to get the probe to be as close to 330 as I can go ( can't quite reach it because of mechanical limitation ), I reset M208 X to allow the probe to reach the end of the bed. I reset M208 to be X330 when done with running the bed mesh.

This is odd to me because I also have dual Z drivers and set up bed.g to auto level the lead screws. It uses,
G30 P0 X0 Y165 Z-99999
G30 P1 X320 Y165 Z-99999 S2

this places the probe at X320 ( as close to the edge as I can go, the nozzle would be at X350 ). This seems to work even when M208 X330 is set.

So G30 seems to override what's set by M208 and G29 does not.

In my marco I temporarily redefine M208 X, but can not see how to do that when using the GUI control. I can run my macro from the gui which works fine, but there is also a way to run bed mesh from a pull down menu that I don't know how to change what it is doing. I looked at the manual for DWC but did not fine a way to customize that control.

Thanks

Joel

Hi

I wrote a macro to have a button on my LCD to do a bed mesh. To get the Z probe as close to the max X of my table I put an override in so the z probe is at the edge and the nozzle is past the edge. I also modified config.g M557 setting to have the extended max Z. This all works fine from my macro, but if I do a bed mesh from the dashboard, it truncates the last point. Is there a way to modify how the dashboard control calls executing a bed mesh command?

Thanks

Joel

OK, I think I got it, was not hard to figure out. Seems M584 is order driven. I just changed Z2:4 to Z4:2 and it seem to be working.

Joel

Sounds fine to me. I am getting used to this way of dong things. So far I like it better, just some things to learn and understand.

Thanks
Joel

Hi,

I set my Duet Wifi up to run dual Z drivers. Everything works OK except that when I do the bed leveling for the lead screws, my results diverge instead of converge. Can I fix this in a config or do I need to get to the Duet ( requires some disassembly ) and swap the Z and E1 cables around?

Thanks

Joel

With the help of folks here, I now have my X5SA printing with the Duet Wifi, Thanks!

I'm used to MKS control boards and using Arduino to modify the config file, then recompiling and uploading Marlin firmware to the controller.

In the config file for Duet, there are a lot of machine definition settings. Do those always have to be reloaded each time you turn on the machine ( it appears to me config.g get run at every power on )? Would an M500 permanently store those things? Does it matter?

I read through the docs and pick up bits and pieces, but this is still a question to me.

Thanks
Joel

@Phaedrux

I fixed the Z Offset macro this morning and now everything is working fine.

I was able to do a print as expected. Now to fine tune a few other things.

Thanks Again!!
Joel

From what I have been seeing, that makes sense. I will fix the z offset macro and see what happens.

Thanks!
Joel

I removed most things from my slicer startup. Right now it's G28, G1 E8.
Attached are the config.g and the macros I'm using to set the Z Offset. For bed mesh, I have a macro that just sends G28 followed by G29. I noticed in some cases, I seem to loose the Z homing.

config.g

Z Offset.g