Initial Homing issues - Sequence of Errors
-
Your M208 and G1 commands say it should be allowed to move more than 80mm. Are you certain the steps/mm is correct?
-
@b0m0a0k said in Initial Homing issues - Sequence of Errors:
M587 S"Removed" P"Removed" ; Configure access point. You can delete this line once connected
Delete that line now that you've connected to the wifi router.
@b0m0a0k said in Initial Homing issues - Sequence of Errors:
M350 X128 Y128 Z128 E16 I0 ; Configure microstepping without interpolation
M92 X80.00 Y80.00 Z400.00 E100.00 ; Set steps per mmIt's a good idea to stick to x16 microstepping with interpolation to x256 and calculate your steps per mm based on x16 at least until everything is working properly, then if necessary you can experiment with other microstepping values, but generally, x16 interpolated will give the best results.
@b0m0a0k said in Initial Homing issues - Sequence of Errors:
M203 X6000.00 Y6000.00
100mm/s might be a little slow for travel moves.
@bearer said in Initial Homing issues - Sequence of Errors:
Are you certain the steps/mm is correct?
I think your microstepping being set to x128 is making your steps per mm value of 80 incorrect. 80 may be correct for x16 though. This would explain why the axis isn't moving as much as you are requesting.
-
OK, so thanks to the combined suggestions of @bearer and @Phaedrux we have progress. I changed the line;
M350 X128 Y128 Z128 E16 I0 ; Configure microstepping without interpolation
to
M350 X16 Y16 Z16 E16 I0 ; Configure microstepping without interpolation
as per your suggestions. The I re-ran all the home commands one axis at a time. Movement was much similar to what it had been with the old Melzi board setup. All axes homed to the stop switches, backed off a little and then slowly recontacted with the stop switches. They all stopped their movement with the stop switch activated (all red stop switches on the board active).
I'm not sure if this is a new feature that I need to get used to (and I can see it in the config files for each axis), but before starting the Home process on X & Y they all raise Z before proceeding.
The one that worries me here is the Z axis. When it triggers the stop switch it is pressed hard against the bed, so I need to back that off a little. I have tried lowering the bed as much as it will go and its still pressed hard.
-
@b0m0a0k said in Initial Homing issues - Sequence of Errors:
M350 X16 Y16 Z16 E16 I0
you'll get the same movement but smoother motion if you change the I0 to I1 to enable interpolation.
-
@bearer said in Initial Homing issues - Sequence of Errors:
M350 X16 Y16 Z16 E16 I0
you'll get the same movement but smoother motion if you change the I0 to I1 to enable interpolation.
Thanks, am giving that a try now.
-
I am wondering if the issue with the Z axis hitting the bed is because I am using a glass plate as the bed surface. The end stop switch was adjusted to allow for this, but I am wondering if there is a need to allow for that in the homez.g file?
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v2 on Wed May 29 2019 19:19:18 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 Z-400 F1800 ; move Z down until the endstop is triggered
G92 Z0 ; set Z position to axis minimum (you may want to adjust this); Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 S2 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning -
@b0m0a0k said in Initial Homing issues - Sequence of Errors:
The one that worries me here is the Z axis. When it triggers the stop switch it is pressed hard against the bed, so I need to back that off a little. I have tried lowering the bed as much as it will go and its still pressed hard.
Not quite sure how this is built, but sounds like you need to move your z-switch. but strange if it worked before you replaced the board.
-
@bearer said in Initial Homing issues - Sequence of Errors:
.. but strange if it worked before you replaced the board.
Yes, that's what bothers me as well.
-
Not familiar with the printer, maybe you could add a picture showing the bed, the switch and the axis raised, and showing the bed, switch and axis lowered?
or maybe first double check that the switch triggers correctly again, it really shouldn't need any force at all.
-
I think I have fixed the Z-Axis issue. By moving the Z-Axis up by hand prior to each homing test I had inadvertently unbalanced the Z-Axis (the left hand was at a different level to the right). I have now re-balanced the Z-Axis and this time, when I tested homing I was still able to get the paper under with enough room to adjust the bed height.
I'm going to run that test a couple more times just to be sure.
-
It's there commands that are raising the z axis before each homing move.
G1 Z5 F6000 S2 ; lift Z relative to current position
This is to give the nozzle some clearance before moving things around.
In the Z homing files you can have it automatically raise the z axis again to give some clearance as well.
; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 S2 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioning
So if you remove the ; on those lines it will raise another 5mm for clearance.
@b0m0a0k said in Initial Homing issues - Sequence of Errors:
The one that worries me here is the Z axis. When it triggers the stop switch it is pressed hard against the bed, so I need to back that off a little. I have tried lowering the bed as much as it will go and its still pressed hard.
Is the endstop trigger height modifiable? Either with a set screw, or moving the switch mount position? You could also add a spacer if you need it to trigger sooner.
Does the switch stop movement if you trigger it by hand before the nozzle hits the bed?
-
@b0m0a0k said in Initial Homing issues - Sequence of Errors:
I think I have fixed the Z-Axis issue. By moving the Z-Axis up by hand prior to each homing test I had inadvertently unbalanced the Z-Axis (the left hand was at a different level to the right). I have now re-balanced the Z-Axis and this time, when I tested homing I was still able to get the paper under with enough room to adjust the bed height.
I'm going to run that test a couple more times just to be sure.
Yes that could definitely explain it. The X axis must be parallel to the bed.
If you have 2 Z motors you can hook each up to a separate driver and then use a self leveling routine to get them evened before printing. You'd need a Z probe for this to be most effective.
https://duet3d.dozuki.com/Wiki/Bed_levelling_using_multiple_independent_Z_motors
-
@phaedrux OK, so I wasn't going to mention this until I was happy that basic operation was working properly, but I have a BLTouch sitting here ready to be installed as well. Am looking forward to adding that once the basic operation with the new board has been confirmed.
Next step is to "Home All" and see what happens.
-
Is it normal for the printer to return to needing Home on all axes every time you move something on the bed. Seems like each time I move something and then go to use "Head Movement" I get this sort of thing;
M120
G91
G1 Z5 F6000
M121Error: G0/G1: insufficient axes homed
-
Did you send that sequence of commands?
-
That was the sequence I uncommented in an attempt to get the extruder to raise a little off the bed after homing.
-
I guess I'm confused by the M120 and M121.
So after homing all you can't move the axis with the jogging buttons on the machine control tab?
-
After you do Home All, do all of the homing buttons in DWC change colour from orange to blue (meaning that the axis has been homed)?
-
@phaedrux I'm pretty sure its not you, it's my horribly green newbie understanding of how to work GCode. I'm learning on the fly.
-
@dc42 Yes, they do.
At this stage I usually need to disable the steppers so I can move the printer head back the centre of the printer so I can run the test again for confirmation. That's the point at which I usually see the "Error: G0/G1: insufficient axes homed" message on one or more of the axes. I'm just trying to make sure that this is normal and not indicative of a problem.