3.2 beta 2 and 3 strange behaviour during movements
-
can you put the motors into spreadcyle and test?
if they switch at 70mm/sec it will cause layer shifts.
next thing is to unload the height map. and test again.
also
G31 P500 X3.5 Y0 Z2.253 ; set Z probe trigger value, offset and trigger height
the offset is wrong. there is no way a bltouch can be this close to the nozzle.
-
@deckingman said in Nema17 strange behaviour during movements:
@Touchthebitum After doing what @Veti suggested, also try commenting out the M915 stall detection commands - just to see if that makes a difference. If you still have problems, try commenting out the M569 commands and see if they make a difference.
the problem is still present
-
@Veti said in Nema17 strange behaviour during movements:
the offset is wrong. there is no way a bltouch can be this close to the nozzle.
it has 3.5cm as offset so I think I have to convert in mm (35mm), right ?
-
@Veti said in Nema17 strange behaviour during movements:
can you put the motors into spreadcyle and test?
I don't know how which value to change
-
@Touchthebitum said in Nema17 strange behaviour during movements:
it has 3.5cm as offset so I think I have to convert in mm (35mm), right ?
yes.
what carriage are you using?I don't know how which value to change
M569 P0 D2
M569 P1 D2
M569 P2 D2
M569 P3 D2
M569 P4 D2 -
@Veti said in Nema17 strange behaviour during movements:
@Touchthebitum said in Nema17 strange behaviour during movements:
it has 3.5cm as offset so I think I have to convert in mm (35mm), right ?
yes.
what carriage are you using?I don't know how which value to change
M569 P0 D2
M569 P1 D2
M569 P2 D2
M569 P3 D2
M569 P4 D2I use the BLV Hotend Mosquito NF-Crazy BLtouch version.
-
@Touchthebitum said in Nema17 strange behaviour during movements:
M569 P0 D2
M569 P1 D2
M569 P2 D2
M569 P3 D2
M569 P4 D2same results ... still present
I have to try to turn back on 3.1.1 but it is not simple to turn back from the beta. It doesn't connect anymore -
In your video your belts look to be very loose which could lead to skipping on the idler teeth. I think that's your main problem.
-
@Phaedrux said in Nema17 strange behaviour during movements:
In your video your belts look to be very loose which could lead to skipping on the idler teeth. I think that's your main problem.
Ok, I'll check that. Thanks
-
@Phaedrux said in Nema17 strange behaviour during movements:
In your video your belts look to be very loose which could lead to skipping on the idler teeth. I think that's your main problem.
I tried to tight the belts but it is the same. When I move the carriage (printer powered off) with my hand, the movements are smooth.
-
So the belts aren't flopping around loose anymore?
Can you post a video of the motion now?
It seems mechanical in nature. Check your belt paths closely.
-
@Phaedrux said in Nema17 strange behaviour during movements:
So the belts aren't flopping around loose anymore?
Can you post a video of the motion now?
It seems mechanical in nature. Check your belt paths closely.
When I thight too much, I hear mechanical noises. I have to tight a tensioner more than the other one to have a correct carriage symmetry.
-
I upgraded to the beta 3 and it seems better.
To be tested -
@Touchthebitum said in Nema17 strange behaviour during movements:
I upgraded to the beta 3 and it seems better.
To be testedUnfotunately It was a short time success. It still loses steps.
I turned back to 3.1.1 and this time erverything disappeared. No lost steps anymore. -
Thanks. I've moved to beta firmware forum for @chrishamm to see.
-
Try to install this experimental firmware build by uploading it on the Files -> System page and then confirm the update prompt. That should get you to RepRapFirmware 3.2-beta3+3-ch (check on the Settings -> Machine page).
Please let me know if that resolves your problem.
-
@Phaedrux said in 3.2 beta 2 and 3 strange behaviour during movements:
Thanks. I've moved to beta firmware forum for @chrishamm to see.
@Phaedrux said in 3.2 beta 2 and 3 strange behaviour during movements:
Thanks. I've moved to beta firmware forum for @chrishamm to see.
Thanks