Have to restart for first layer to be correct
-
I will change that now and let you know when this print finishes if it makes a difference.
-
Same problem with homey.g
The signs on these moves need to be swapped.
G1 Y5 F6000 ; go back a few mm
G1 S1 Y-305 F360 ; move slowly to Y axis endstop once more (second pass) -
And for homez you may want to have it move to the center of the bed first same location as in homeall if you want more consistent probe results. But for that to work x and y must be homed first.
And obviously you'd have to uncomment the g30 command and comment out the g1 z move to endstop commands.
But only after you verify that a single manual probe works.
I think those fixes will get your homing working properly now.
-
It's better but still not perfect. I tried a G30 from the center of the bed and it skips a little at first run to the edges then when it's finished all hell breaks loose. I am at a loss right now.
-
@kuntry3d First step is to get X and Y moving in the right direction and homing correctly. Once that is sorted then we can work on G30 bed probing. Once that works just issuing G30 without sending it to a particular X and Y position then we can combine it back together into the desired homeZ.g homeall.g etc.
So to start with follow the X and Y section here:
https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_X_and_Y -
@kuntry3d said in Have to restart for first layer to be correct:
It's better but still not perfect. I tried a G30 from the center of the bed and it skips a little at first run to the edges then when it's finished all hell breaks loose. I am at a loss right now.
So when you issue a G30 manually from the console at the centre of the bed it moves in X and Y as well as in Z?
-
Yes. It does like a triangle in x and y then probes and then tries to exit the printable area and then parks at the front of the bed.
-
Tomorrow sometime I can video exactly what it is doing and send you a private link to view it if that is an option. It may be helpful vs just the config files to actually see what is happening.
-
Sure. I'm at a loss as to why it would behave like that during a manual probe.
Are you sure there are no deployprobe.g and retractprobe.g files in the system folder?
-
I must have missed that question. Yes they are there, I thought they were there just because they are needed. I also have homedelta.g. I used the configurator online and these are the files it gave me so I thought they were needed.
-
After it's done that can you run M122 in the console and paste the results here?
Grasping at straws here, but is there a reason you've chosen 32 microstepping as opposed to 16 with interpolation to 256?
And prints are working properly?
-
You can delete homedelta.g.
What are the contents of the deploy and retract files? I don't think your probe type needs to be deployed and retracted, correct? You can delete those as well if that's the case.
-
Ok, I will get those out tomorrow and test again. I am printing again. Hopefully this one will finish, I am having a problem with this thing breaking off small hollow columns. Several hours into prints it will break a necessary part off and then I quit. This print has none of that so I will let you know. Again, thank you for all your help.
-
Retract
; Probe retraction routine for Mini Kossel
M564 S0 ; don't apply limits
G1 Z40 F10000 ; raise head
G1 X-59 Y66 Z35 ; move over the post
G1 Z7 F500 ; push probe down on post
G1 Z35 F10000 ; raise head again
G1 X0 Y0 ; move to somewhere sensible
M564 S1 ; apply limits againDeploy
; Probe deployment routine for Mini Kossel
M564 S0 ; don't apply limits
G1 X25 Y93 Z40 F10000 ; put probe arm next to belt
G1 X-5 F500 ; move probe arm across belt
G1 X12 F1000 ; move probe back
G1 X0 Y0 F10000 ; move to somewhere sensible
M564 S1 ; apply limits againHomeDelta
; Homing file for RepRapFirmware on Mini Kossel
G91 ; use relative positioning
;******* Change F250 in the following line to F2500 when you are finished commissioning
;******* Change 320 in the following to a higher value if your Kossel has taller towers
G1 S1 X320 Y320 Z320 F2500 ; move all carriages up 320mm, stopping at the endstops
G1 S2 X-3 Y-3 Z-3 ; move all carriages down 3mm
G1 S1 X6 Y6 Z6 F250 ; move carriages slowly up 6mm, stopping at the endstops
G1 Z-5 F2000 ; down a few mm so that we can centre the head
G90 ; back to absolute positioning
G1 X0 Y0 F2000 ; centre the head and set a reasonable feed rate -
@phaedrux said in Have to restart for first layer to be correct:
G90 ; absolute positioning
G30 ; probe the bed
G1 Z5 F100 S2 ; uncomment this line to lift the nozzle after homingJust FYI, I had to kill the print so I restarted with the files removed and now all of the things work as they should, G30 and G29. I will let you know progress. And thanks again.
-
Yeah those files don't belong on a CoreXY. Not sure what selections the configurator had to give you those. You could probably lose bed.g as well if you intend to use mesh grid compensation anyway, which you should. If the build plate is flat you can just use a sparse grid for the same results as the 5 point probing.
Glad homing is sorted. Hopefully with proper z height now you won't have any more collisions.
Have you run a PID tune on the bed and hot end? Calibrated the extrusion factor? That can help with collisions as well (over extrusion, bed expansion)
-
Yes sir, All of that (PID, Extrusion, ETC...) was done. I will leave bed.g as the entire frame, bed frame too is printed so I may need to change to G31 instead of G29 S1 in my script. If you would like to see the printer I have the entire build on YT. Kuntry3D on YT let me know what you think. I had to re-flow the solder for the main DC power in on the Duet this morning as that was what was causing my failures due to voltage inconsistencies. Once I fxed that my voltage is steady and everything is now sorted. Thank you for all of your help, you have been very patient with me and my questions.
-
No problem at all. Glad it's all working out. I'll definitely check out your channel.
-
@phaedrux said in Have to restart for first layer to be correct:
Grasping at straws here, but is there a reason you've chosen 32 microstepping as opposed to 16 with interpolation to 256?
I just saw this.
"Grasping at straws here, but is there a reason you've chosen 32 microstepping as opposed to 16 with interpolation to 256?"Can you tell me how to do this?
-
The M350 command in your config.
Simply change it to 16 and add I1 (that's a letter I as in I love you man)
Your steps per mm should already be set for 16 microstepping as the duet will make adjustments for you if you change it after. But double check just to be sure.
Give this section a read it'll have some more detail but I think you're good to go.
https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Movement_section
