This will bring the pin HIGH when the pin is not connected to ground, and set it to trigger LOW.įrom my Primo configuration.h: #define ENDSTOPPULLUPS #define Z_SAFE_HOMING_Y_POINT Y_CENTER // Y point for Z homingĬommenting out the #define Z_SAFE_HOMING will disable the homing point in the center of the defined bed, too.įor the Z endstop, you will need to enable the pullup resistor. #define Z_SAFE_HOMING_X_POINT X_CENTER // X point for Z homing In the event that X and Y are not homed, it should generate an error (Insufficient axes homed) because it doesn’t know where that safe spot is.įrom the configuration.h for my old printer: #define Z_SAFE_HOMING This can happen in Marlin if the “Z_SAFE_HOMING” is enabled, where it tries to move the carriage to a “safe” spot before homing it. If I program “G28 Z” in a custom menu, it will lift Z then shoot X & Y axis across the bed. Baby steps I guess.Īny one have any ideas what else to try? I am sure I am only one or two settings away from getting this to work. I could not get it to do anything except go mad using G28 so at least now the Z starts to home, it just does not see the probe. I got the extra menus to eventually work with the G38.2 code. I am not giving up, going to try inverting the Z min next, waiting for it to compile. I have defined FIX_MOUNTED_PROBE and Z_MIN_PROBE_REPEATABILTY_TEST I have tried both Z_MIN_PROBE_PIN Z_MIN_PIN and Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN, and not the V2 board which makes all the difference. Found out that I have the V1.2 board with V2.0.2 software. Elegoo nano pinout software#I did not make it any easier on myself in mistaking the V2 software revision for the board revision so of course wasted most of the weekend panicking and wandering why I could not get the board to work after the first flash. Elegoo nano pinout code#I have reverted to ‘classic’ UI reluctantly but even setting up the probe using the code that I got to work with Ramps, I am not succeeding. Shoo, this is proving to be very frustrating. if I cant work it out, then I guess I have to go with changing to the Marlin GUI. I have ready through all the documents and videos I can find but still none the wiser. Has anyone played with these boards and able to offer any advice. I cannot see anyway to stop that or to zero position. sets the Z level, but then proceeds to try and move the X axis to a "home’ position which of course i don’t want. I tried connecting probe to the Z min no problem, I set up auto level through the menu and it works to a point, i.e. I guess that sort of comes with the territory. The manufacturers support has not been able to assist me except to say “try the Marlin Classic UI” which to me sort of defeats the point somewhat as I really like the way the touch screen is set up.Īlso I can find no way to keep all the settings I have programmed thus far to get things going without having to do a complete upload of a new Marlin Build. Elegoo nano pinout how to#Than I hit a blank about how to set that up through the touch screen menus. (Dragged into the 21st century) and touch screen convenience.Įverything was going swimmingly and my Primo working as it should very quickly…until I tried to get my Z touch probe to work. Elegoo nano pinout 32 bit#My RAMPS 1.6 started to reboot for no reason half way through jobs so I thought it was time to change and go with a 32 bit board. Also the appeal that I can just upload program changes to marlin through the SD card. I have just brought 2 of the Makerbase MKS Robin Nano boards enticed by the TFT35 touch screen convenience and also that it is (I thought) easy to set up using only the touch screen and not having to be hooked up to a laptop or dismantling my MPCNC to take the RAMPS board to a pc for reprogramming.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |