ANYBODY HAVE EXPERIENCE W/ ‘auto#.g’ FILES?
Posted: Sun Jan 21, 2018 1:32 am
- Holds g-code that gets executed on startup.
- Files go in root of SD card.
- Having limited success:
- Not sure what “normal” behavior should be, but...
- ...What I’m observing on startup:
-- Display shows ‘auto0.g’ (and executes the code), but
-- ‘...Ready’ does NOT appear, though system seems ready.
- And, having issues with homing (G28) via auto0.g:
-- Printer auto homes, but motors then deenergize, and values not stored.
-- Tried explicit call to energize motors (M17), but too late, apparently, so to no avail
-- Tried explicit call to store values (M500), but to no avail
- Am having success turning on fans, though (electronics/coldend).
So, auto homing on startup is not required, but adds a level of safety when subsequently executing absolute moves of the nozzle, as system must initially get x, y, z values from endstops to know reference for origin. Of course, auto homing on startup does present its own potential problem: if bed is not clear, things could collide
This is important to me, as I’m implementing the latest Marlin (1.1.8)/Arduino (1.8.5) on Makergear M2 to add some features via an LCD controller (Viki 1). Among these is an assisted bed leveling via CUSTOM_USER_MENUS. These simply move the nozzle to strategic locations (center, over adjustment screws, & each corner) - but this needs the proper origin reference!
(FYI, by default, Marlin only supports 5 custom menu items, but I hacked the firmware, and now you get 10! And, more are possible, if desired.)
OK, I realize this is a rather esoteric aspect of the firmware, but I’m hoping some clever, experienced programmers are here and can shed some light...