@o_lampe said in Simple bed leveling program:
nested for X/ for Y loops
You got me thinking. So I just made an additional 'layer' to my projects' file, and labeled it bed-leveling. I then exported that G-code file to my SD card, and viola, it works! first time ever making anything move from scratch. Thanks so much for your assistance.
Ron
The simplest solution to my want of incorporating photo-optic end-stops, was to add a separate 24v supply for the 'PM-K45-P-C3' PNP sensor. Then simply connect its collector-output to one of the opto-isolated channels 5 thru 8. Testing of the X-axis was flawless and most accurate. No more mechanical switches. Now I just need to fabricate the mounting for all axes.
Having great success using LightBurn to create a path for fly-cutting a thin layer off the sacrificial table.
Thanks for the great advice. Hope to finish an ongoing project this weekend, then plan to update. Don't want to take any unnecessary chances, that might cause unexpected results.
I'm currently running with 3.4.5 and just wondering if I should upgrade to a more current version, for operating my augmented Indy-Mill engraving aluminum router.
Thanks, Ron
Well....... Duh. Yes Sir, that's what I need! excuse my novice ignorance. I'm guilty of reading thru the tutorials much too fast. I will try my best to comprehend that whole Mesh process. Might need help to fully grasp the challenge. I've never tried to 'edit' the Gcode before, for fear of ruining it. Give me some time to experiment. Should I post my config.g for scrutiny?
After running a bed-leveling macro, is it possible to 'record' multiple values of Z-probing made across the bed surface? Then implement those values to create offsets for Z, that results in a near perfectly flat surface. While my talents lie mostly with electronic design and playing guitar, I'm a fish out of water when it comes to programming.
Having great success using LightBurn to create a path for fly-cutting a thin layer off the sacrificial table.
@droftarts Well, that's a lot of information for me to digest! Lol. Might I see an example of code where M669 has been implemented?
@jay_s_uk said in Cancel Print/Job not immediate.:
M669 T1 S1
Thanks for the suggestion, but I'm not very keen on how to implement what you're talking about.
@Valveman I'm expecting a new cutter today. Plan to post my results asap.
If some reason, I choose to cancel a Job that is running, cancel only takes affect after the current motion has completed. Is that normal, as I'm new to all of this? Is an update to DWC or the 6XD a solution?