Nozzle gets smashed against the bed
-
@MJCT said in Nozzle gets smashed against the bed:
Where do I find "config-override.g " file, maybe is because of that. Maybe it always overrides my new imputes.
You don't have M501 (read stored parameters) in your config.g, so it won't be loading config-override.g (which is usually in the sys folder, where config.g is). You'll only have a config-override.g if you have sent an M500 to store
How old is your BL Touch? I have heard that after a while they can get 'sticky', with the pin not deploying fully, and giving variable results. I believe you can take them apart and give them a clean.
Ian
-
I think I found the reason why I never see a config-override file...
*****“dc42 ADMINISTRATORS 10 Jun 2017, 23:18
If you created your config.g file using configtool, you will have selected whether or not config-override.g is processed.”*****
When I did my config with the config toll I didn’t select the “Read config-override.g file at end of startup process” box at “General”.
One doubt less, but still doesn’t solve my problem -
The file config-override is created if you have executed a M500 command.
I don't have one as created it to have access to the two line of code that were generated by heater tuning.
I copied those lines into config.g and deleted config-override.g
Frederick
-
My BL is new. Version 3.1, the pin deploys fully and the results are consistent.
The problem seems to be that the values that I impute are not taken in to account and the real distance from the nozzle to the bed doesn’t correspond to the distance displayed at the Dashboard for the Z (dashboard always displays a positive value, say 2mm, when the nozzle is already touching the bed).
-
Hi,
After you do a single G30 does the reported value seem to be correct? Does the gap between nozzle and bed seem to match the reported value?
Frederick
-
@fcwilt ~
Nop, last 2 times that that I sent G30 the nozzle smashed the bed
-
@MJCT said in Nozzle gets smashed against the bed:
@fcwilt ~
Nop, last 2 times that that I sent G30 the nozzle smashed the bed
When that happened did the pin drop down at the start?
Frederick
-
@fcwilt
Yes -
@MJCT said in Nozzle gets smashed against the bed:
@fcwilt
YesDid the pin retract when it touched the bed?
It's possible you have an intermittent connection in the wires that carry the signal from the probe back to the Duet.
Frederick
-
@fcwilt
Yes, the pin retract when it touches the bed -
@MJCT said in Nozzle gets smashed against the bed:
@fcwilt
Yes, the pin retract when it touches the bedBut the motion did not stop?
When the pin is in the down position how far below the nozzle does it extend?
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
My last test returned this value
https://drive.google.com/file/d/1EH_a5huQdowrXaahItpsKx0ADAuLq9RX/view?usp=sharingshould I input
G31 P25 X25 Y0 Z0.229
or
G31 P25 X25 Y0 Z2.29 ?
-
@fcwilt said in Nozzle gets smashed against the bed:
But the motion did not stop?
When the pin is in the down position how far below the nozzle does it extend?Yes the motion stoped.
The pin gets +- 3.3mm below the nozle -
@MJCT said in Nozzle gets smashed against the bed:
@fcwilt said in Nozzle gets smashed against the bed:
But the motion did not stop?
When the pin is in the down position how far below the nozzle does it extend?Yes the motion stoped.
The pin gets +- 3.3mm below the nozleWell if the motion stopped how did the nozzle hit the bed?
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
And you enter the value just as displayed.
Frederick
-
@fcwilt said in Nozzle gets smashed against the bed:
Well if the motion stopped how did the nozzle hit the bed?
the problem now is that this thread is getting to long and I’m starting to get confused with all the questions. Kind off... you where asking about the G30, when I home the Z, When I start the machine....???
Well, I entered the value as displayed “G31 P25 X25 Y0 Z0.229”
Seems to work at the beginning. First layer a little bit far from bed, corrected it with baby steps, and printed the rest of the first layer fine.
Second layer moved a lot above what was expected and started to print in the air.
May be the “G31 P25 X25 Y0 Z0.229” was right from the beginning and the problem is Cura?
What other slicers do you use for reprap?Now I’m going home, long day! Thank you all, I really appreciate all your effort!
-
If it moved further than expected, have you got your z steps correct for your machine?
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@MJCT said in Nozzle gets smashed against the bed:
M92 X80.00 Y80.00 Z4000.00 E96.94 ; set steps per mm
Z steps per mm of 4000 doesn't sound correct.
Z_steps_per_mm = (motor_steps_per_rev * driver_microstep) / screw_lead -
@jay_s_uk said in Nozzle gets smashed against the bed:
If it moved further than expected, have you got your z steps correct for your machine?
Yes, I tested it before I started asking questions. Any way If you read this
"Well, I entered the value as displayed “G31 P25 X25 Y0 Z0.229”Seems to work at the beginning. First layer a little bit far from bed, corrected it with baby steps, and printed the rest of the first layer fine.
Second layer moved a lot above what was expected and started to print in the air."
you know that the problem is not Z steps
-
@MJCT said in Nozzle gets smashed against the bed:
you know that the problem is not Z steps
Please fill out the formula above for determining Z steps per mm and show how you arrive at 4000. Thanks.
