ojasV
About
- Username
- ojasV
- Joined
- Visits
- 99
- Last Active
- Roles
- Member
Comments
-
Yes I've kept it disabled since I didn't fully understand it while building the firmware. One more thing, my extruder steps/mm are 95. It uses a 1.8 degree 1.5A motor. How do I find out the maximum retraction speed it can achieve?
-
So I read a little and I understand that the firmware values are used if AutoRetractConvert is enabled. Else, slicer values are used. Is that correct?
-
ojasV said: So for retraction, the printer will always use: RETRACTION_LENGTH 3 RETRACTION_SPEED 40 RETRACTION_Z_LIFT 0 right? And it won't make any difference what values I give to "Retraction Distance", "Extra Restart Distance" & "Retr…
-
When exactly are G10 and G11 used, if for all printing moves the slicer dictates the retraction values? - G10 S retracts filament according to stored setting- G11 S = Undo retraction according to stored setting I understand that G1 X Y Z E will c…
-
So for retraction, the printer will always use: RETRACTION_LENGTH 3 RETRACTION_SPEED 40 RETRACTION_Z_LIFT 0 right? And it won't make any difference what values I give to "Retraction Distance", "Extra Restart Distance" & "Retraction Vertical Lif…
-
Repetier said: max. prinable radius is a contrain and remember that to issued coordinates you have to add z probe offsets to see what it will really test and which position needs to be valid. At a position like 100,100 your radius is 142 plus…
-
Alright. But I still don't understand why Repetier Host stopped responding when I changed printer radius to 142 and ran bed height map tool. Should I try a higher value, say 150 and run it again to see what happens?
-
Repetier said: G33 omits edges if you have compiled it with the flag set. Can you please explain? I have mentioned my distortion parameters in an earlier comment. Moreover G33 isn't omitting anything, it is measuring all points of a 5x5 m…
-
Actually G33 is using a proper 5x5 point matrix whereas the Bed Height Map tool isn't using the four corner points. So (-100,-100), (100,-100), (100,100) and (-100,100) are not being measured by the Bed Height Map tool. Shouldn't it be the reverse? …
-
My Z_PROBE_BED_DISTANCE was set to 10. I started the "Bed Height Map" tool at Z=10 and that cleared the confusion. However, I still have a few queries. Here are my distortion correction values: #define DISTORTION_CORRECTION 1 #define DISTORTION_COR…
-
Alright, so turns out the diagonal rod length and printer radius both were off. My bad. I fixed them both, re-uploaded the firmware, did the entire calibration routine and hit no snags. One question though. While calculating tower endstop offsets us…
-
I don't think it's an inductive one. I'm attaching a picture here. No the extruder doesn't have any offset. What error do you think it might be, so that I can investigate further?
-
Okay, I played around a bit, and set Z_Max_Length to 311.51, coating to 1, and Z-Probe Height to -1.90 After running G32 the printer height got calculated as 311.52 which is pretty close. Now my question is, how did this work? Also I lowered the ext…
-
I updated Z-probe height to 2.38 and ran G32 again. The newly calculated printer height is 314.94 What has gone wrong?
-
Yes I fetched the EEPROM values from Repetier host. As per the video "Z levelling for Delta printers", I have executed till G32. The remaining part from "bed height map tool" and onwards is yet to be done. So I just have to update Z-probe height usi…
-
Repetier said: Ok, wrong direction. Increase Z_PROBE_HEIGHT by 2.2mm then. I always mix the directions. Can you explain to me why this is required? I calculated the Z-probe height using the metal block method given in the "Z-probing" arti…
-
Here is the log following G32 if that helps: 12:07:06.852 : N202 G32 S2*89 12:07:06.860 : Z correction disabled 12:07:07.565 : N203 M105*38 12:07:08.615 : SelectExtruder:0 12:07:08.615 : X:0.00 Y:0.00 Z:310.513 E:0.0000 12:07:10.622 : N204 M105*33 …
-
In EEPROM coating thickness is 0, z-probe height is 0.11 Rest of the values are not present.
-
Z_PROBE_Z_OFFSET 0 UI_BED_COATING 1 Z_PROBE_HEIGHT 0.11 ENDSTOP_X_BACK_MOVE 5ENDSTOP_Y_BACK_MOVE 5ENDSTOP_Z_BACK_MOVE 5 ENDSTOP_X_BACK_ON_HOME 1ENDSTOP_Y_BACK_ON_HOME 1ENDSTOP_Z_BACK_ON_HOME 1
-
Hi @MShievitz I've been reading your posts here and I'm wondering if you used the EEPROM data to build the new firmware and still had the motor control issues and bed levelling issues that you've mentioned in other threads. Turns out, I'm facing a s…