Centering a print
-
@Derek-F You'll need to redo all your homing files. The origin is now set as the centre of the bed so if you want to probe the bed in the centre, you'll need move the print head to X=0 Y =0. i.e this line "G1 X200 Y200 F6000 ; go to first probe point" needs to be changed to "G1 X0 Y0 F6000 ; go to first probe point
Note that the position of the end stops can stay the same. Note also that any files you previously sliced with the origin set to one corner of the bed will need to be re-sliced because they will contain moves in the range zero to circa 400 whereas with the origin in the slicer set to the centre, the moves need to be in te range minus circa 200 to plus circa 200.
Edit posted while DC was typing. also, it appears my PC has the wrong time set.
-
@deckingman Thank you for your replies.
Before I switch on the printer, I'd like to have some idea of the procedure I'm going to follow to recover from the crash. Some time after power off, I tried unsuccessfully to raise the gantry slightly and take the pressure off the nozzle. When powered up, I can't use the move buttons until a homing operation is performed first (which I obviously cannot do).
If I opened the printer console and sent one of these commands, would it lift the gantry?
G1 Z10 F300
G1 Z+10 F300
G1 Z10
Or something else?
Do I need a G90 or G91 first?I am seriously concerned that the gantry is no longer level (ie: parallel with the bed) since it crashed in one corner and I tried to lift it slightly.
How should the gantry be leveled again?
Will my Z offset be incorrect?Cheers,
Derek
-
@Derek-F use
M564 H0to allow jogging of the axis without homing -
@jay_s_uk Thank you. That allowed me to move the nozzle away form the bed.
I have changed my two M208 lines back to the 'as supplied' figures where the zero is at the front left corner. I think it prudent not to change to zero at the bed center until I understand every implication of doing so.
How do I get the gantry parallel to the bed now?
I see this code in config.g but when is config.g run? (is there a command in the print file?)
; --- z-axis stepper leveling configuration ---
M584 X0 Y1 E3 Z6:5:8:7 ; four motors, at 5, 6, 7, and 8
;M671 X420:420:-100:-100 Y380:-115:-115:380 S20 ; Z belts at 4 corners
M671 X-100:-100:420:420 Y380:-115:-115:380 S20 ; Z belts at 4 cornersDoes the above actually level the gantry?
Finally, will the crash have affected my Z offset?
Cheers,
Derek
-
@Derek-F config.g is ran at boot and loads all of your printers parameters into the firmware so it can be setup correctly.
G32would go through the levelling process. This runs the bed.g file, which contains the locations to probe the bed for levelling -
@jay_s_uk It's idle and powered on. Should I just send G32?
Or do I need to home it first?
Cheers,Derek
-
@Derek-F you need to home first
-
@jay_s_uk That was all successful. Thank you.
Do you think I need to reset my Z offset after the crash?
Cheers,
Derek
-
@Derek-F you may do depending how hard the nozzle crashed into the bed.
You should also be running G32 before a print as the gantry/bed may have dropped whenever power has been turned off -
@jay_s_uk OK, I'll try a print and see how it goes.
Just checked and G32 is in my Start G-code routine.
BTW, is the following line bad to constantly write to memory (like the WiFi credentials)?
M550 P"VIVEDINO" ; Set machine name
-
@Derek-F no, thats fine. that just sets the machine name in the firmware
-
@jay_s_uk Everything is working again! Thank you!
Z offset looks ok. I'll monitor on further prints.
And I have centered the print, simply by changing the X5 to X0 in the 'M208 S1' line (M208 X0 Y0 Z0 S1) and adjusting the X size of the bed in the slicer. (I clearly don't know enough to safely set zero at the center of the bed at the moment).
The printer already had a macro for WiFi ON and I just had to change the credentials to my set. I have commented out M587 in config.g .
I do have a couple of other unrelated questions but I should probably start new threads for those (unless you want to continue here).
Thanks to both of you for your gracious replies and patience with my lack of knowledge.
Cheers,
Derek
-
@Derek-F probably best to start a new thread. Then we can tackle the subject of getting you upgraded to 3.5.2
