Printing too high.
-
g31 trigger height is 8mm where does this go?
FIRMWARE_NAME: RepRapFirmware for Duet 2 Maestro FIRMWARE_VERSION: 2.05.1 ELECTRONICS: Duet Maestro 1.0 FIRMWARE_DATE: 2020-02-09b1
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Macro file config-override.g not found -
nothing else changed so far except the beautiful new UI, but the motor noise doesn't sound healthy
-
@evilfknpotato said in Printing too high.:
g31 trigger height is 8mm where does this go?
8mm? Are you sure about that? When mounted correctly as suggested by Antclabs the BLTouch body should be 8mm above the nozzle which leads to a trigger height of about 2mm.
-
@evilfknpotato said in Printing too high.:
but the motor noise doesn't sound healthy
Which motor? All of them? What moves are you doing?
Can you record a video to show it?
-
@Phaedrux yes that seems correct its a stock creality metal mount and re measured and the trigger height is correct at 3.2mm
-
@Phaedrux all of them on homing and g1 moves
How do I upload a video? -
@evilfknpotato said in Printing too high.:
@Phaedrux yes that seems correct its a stock creality metal mount and re measured and the trigger height is correct at 3.2mm
Alright, so with that G92 Z0 removed from the homeall.g file does the nozzle touch the bed when you tell it to move to the Z0?
@evilfknpotato said in Printing too high.:
How do I upload a video?
On a desktop you can drag and drop a file onto the post text box to upload it, or you can put it on dropbox or google drive if it's too big and share a link.
-
yes it always did move to Z0 before printing and now it prints at correct height thank you so much!
Now its just the strange motor problems, if it were my wiring it would have done this before updating firmware. uploading video -
-
Maybe if have to compare to how it sounded before but that doesn't sound too bad to me.
You can try reducing the motor current a bit. Try 600 or 700 instead of 800.
-
@Phaedrux it was silent before this sounds like back emf or something
-
@evilfknpotato reduced current to 600 and still the same
-
is it worth upgrading to v3.0?
-
@evilfknpotato said in Printing too high.:
is it worth upgrading to v3.0?
I wouldn't think it would make a difference but I also wouldn't have thought moving from 2.0 to 2.05 would have changed anything either.
Going to rrf3 would require changes to your config file. If you wanted to test it you should back up your current config files and then generate a new config from the online tool for rrf3 to test with.
-
@Phaedrux exactly my thoughts but something must have changed, voltages?
-
try changing the M569
M569 P0 S1 D3 V40 ; physical drive 0 goes backwards
M569 P1 S1 D3 V40; physical drive 1 goes backwards
M569 P2 S0 D3 V40; physical drive 2 goes forwards
M569 P3 S1 D3 V40 ; physical drive 3 goes backwardsprint the output of
M569 P0 afterwards -
@Veti you sir are very helpful, that worked like a treat, what did this do?
-
@Veti M569 P0
Drive 0 runs forwards, active low enable, step timing fast, mode stealthChop, ccr 0x00053, toff 3, tblank 0, hstart/hend/hdec 5/0/0, tpwmthrs 40 (234.4 mm/sec) -
in newer version of the firmware the switchover from stealthchop to spreadcycle was implemented.
spreadcycle is louder
above like 10mm it will switch to spreadcycle by default.
this increases the limit.
however stealthchop is weaker, so it might cause layer shifts.
if your extruder is skipping, i would suggest that you switch that over to spreadcycle
by just changing
M569 P3 S1 D2 -