Part one: The obsolete S and H parameters warning is now gone so I think I have that fixed... Right now I had manually put the core XY and the bed in to the home positioning and then restarted the machine. I am NOW getting movement, however its grinding all over the place as I'm sure nothing is aligned and needs to be set up, however how do I do that when its freaking out like that?? Below is the config file. Do you need ALL of the homing files to look at? And is it okay to post it like the config file below? Thank you BOTH for all of your help !

Finally figured out how to set the M569 V so I'm going to test out: ; Stealthchop2 M569 P0 S1 D3 V78 ; Drive 0 goes backwards M569 P1 S0 D3 V78 ; Drive 1 goes backwards M569 P2 S0 D3 V111 ; Drive 2 goes backwards M569 P3 S0 D3 V45 ; Drive 3 (E0) M569 P4 S0 D3 V45 ; Drive 4 (E1) M569 P5 S0 D3 V45 ; Drive 5 (E2) M569 P6 S0 D3 V45 ; Drive 6 (E3) Drive 6 tpwmthrs 45 (40.6 mm/sec) Drive 5 tpwmthrs 45 (40.6 mm/sec) Drive 4 tpwmthrs 45 (40.6 mm/sec) Drive 3 tpwmthrs 45 (40.6 mm/sec) Drive 2 tpwmthrs 111 (16.9 mm/sec) Drive 1 tpwmthrs 78 (120.2 mm/sec) Drive 0 tpwmthrs 78 (120.2 mm/sec)

hrmmm.... since I am heater 6... so this means: M42 P6 S10 would fire the laser on low power (hopefully..) I did read somewhere on the forum that you can not fire without moving... they said made a macro for it.. but Don't know how.... Would you or anyone kindly share how? thanks Tony

Can you upload that gcode file somewhere online and link it here?

@Rat_Patrol said in How do I enable MESH leveling for the print?: Tried the same script now using a Maestro, and it doesn't work. If you used G29 S1 and it didn't work, what exactly didn't work about it? Typically you'd put G29 S1 in the slicer start gcode. Or even at the end of homeall.g (called by G28) if you wanted it to be active at all times to protect the nozzle from contacting the bed surface if you happen to have a less than perfectly flat bed.

Yes that makes sense. You can do it, though your offset will need to be spot on since you won't be using the probe to home Z. Otherwise your heightmap could have a larger than expected offset. The trigger height of the switch would need to be offset to exactly where the nozzle would be touching the center of the bed. You could find this offset with gcode as well. Touch the nozzle to the bed, use G92 to set Z0, You'll need to use M564 S0 to allow movement beyond the set axis limits and then jog the nozzle until it just triggers the switch and note the Z position. It'll be a negative value. This value would also change any time the bed was releveled. This is a disadvantage to not using the probe to home. Your homeall.g could be modified to move the print head to where it needs to be, configures the endstop, and then triggers it setting the Z position with a G92. Then you'd have to return back above the bed surface and move to a safe location to start the print from. For the probing of the mesh you could edit bed.g to configure the probe, prompt you to ensure it's mounted, and then execute a G29 to generate the heightmap, and then prompt you to reinstall the nozzle. Hopefully that makes sense. Let me know if you want more detailed macro examples.

I liked the previous version, but had left you with some crude code ~20 July, and comments related to my simple needs, but I had abandoned use of DueUI as I thought you had abandoned this project as there had been no response and looked like there would be no support. I notice babystepping is now included - thanks? Is there anything critical that is new? Although I can implement and customise this I am not conversant with JSON in general & my brain will take some hours to reboot into this project.

@littlehobbyshop please pass along your experience going forward. I occasionally add a 4th axis (currently just for indexing) to my Duet controlled micro mill. https://forum.duet3d.com/topic/11581/duet-controlled-micro-mill My CAM outputs 4th axis though I have yet to dedicate the time to explore simultaneous work. My current focus is an ATC for the machine but plan to start working again on the the "A" axis soon after that is complete

I bet it's because software e-stops are on enabled and he's commanding it to a negative value.

Wired it on second terminal and works! Thanks

@spllg said in is the duet 3 board able to kill an attached raspberry?: visually checked and measured the resistance between can be tricky to locate a fault in a system that moves and heats up though. the meter also use much lower voltage to test, so if you have a leakage and not a straight up short it won't find it. I should get some new terminals and housings one of these days, so I could try adding an isolator to my setup, but admittedly for the Pi to risk any damage odds are you're also risking damaging the Duet3, so imho it makes more sense to focus on protecting the Duet3 in the first place. edit: just finished planning out the txs0108e, if anyone decides to try DO NOT use 5v to power the isolator on either the SBC or Duet3 side, both sides need 3.3v and you'll need to find 3.3v somewhere else on the duet (IO port, temp daughter board, swd port etc)

It is working properly now, thanks!!!

M591 configured as a simple switch should do what you need. https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_filament-out_sensors The pause and resume macros are also configurable to do what you wish. See the recent discussion here: https://forum.duet3d.com/topic/13972/filament-out-sequence-of-actions

@dc42 really? That's amazing! Thank you!

@chrishamm @chrishamm Appreciate you looking into this thanks! Ill report back if 1.2.4 fixes this!

That looks correct.

If the corexy link above doesn't get you sorted out please post your homing files as well.

Check things that get loose or worn over time. Loose belts, loose bowden tube connectors, loose bed mounts, loose hotend, etc.

@Phaedrux Yeah after reading a bunch of forums and blobs related issue I start to regret about using bowden, until now... will see, keep tweaking. Still thinking would be better to come back on using PA, just need more time for tweaking I guess.