okite
About
- Username
- okite
- Joined
- Visits
- 9
- Last Active
- Roles
- Member
Comments
-
Hi,I finally found the solution - z-axis had wrong step setup - too many steps, I found the appropriate data for z-axis screws and recalculated. Instead 1600 it is 400 :-).I also use Cura slicer now, giving the best results for this machine. Thanks …
-
It seems I have to "deep dive" to mechanics, as seller is unable to tell me appropriate info for setup (delivered with Merlin). I will investigate, setup and let you know results. Thanks.
-
I think I have found it - 0.3 is first layer height, so I think I must recalculate Z stepping, as I used data from the seller, but its data could be wrong. Printer goes to the first layer, but it is not right height, as stepping is wrong, so the he…
-
Gcode manually: M107M190 S65 ; set bed temperatureM104 S205 ; set temperatureG28 ; home all axesG1 Z5 F5000 ; lift nozzle M109 S205 ; wait for temperature to be reachedG21 ; set units to millimetersG90 ; use absolute coordinatesM82 ; use absolute di…
-
Yes, G1 Z0 works, only one problem which lasts is printing in wrong height.OK, I will send gcodes manualy and will let you know. Thanks.
-
This was caused by Y coordinate, that probe was not 100% above bed, so did not triggered. It triggers, when 100% of the probe area is above the bed. I had to setup Y offset to asure right position above bed and reliable triggering.
-
How to proceed? Is there some config.h I could use to test the printer, or what you would recommend? I think somewhere in the firmware setting (I tested all slicers in R host) is command to rise the level and printer does not go to the Z0 then. When…
-
I have #define ZHOME_PRE_RAISE 0#define ZHOME_PRE_RAISE_DISTANCE 0
-
I see, the error (L/H) was caused by position of the probe - on the bed edge, so it did not triggered. I set up small y offset, and it is OK. You are right, I do not modify Z, it is 0 in slicer (checked all slicers in Repetier Host V2.0.0) but it st…
-
I experimented with changing board from MPX3 to RAMPS 1.4, but x/y movements didnt function well.Compiled completely new dev version, chcecked endstops, did G32 S2 autoleveling Old Z+2 printing level is still there. Homing Z sets the correct Z0... …
-
But after emergency stop homing Z goes to Z0...Reset g92 Z0, then print again (now Z_min is still OK)In fact, after bed heating G1 Z5 F5000 - lift nozzle - waits for heating, then prints in the lift nozzle height - does not go down to the Z0. G-code…
-
Reinstalled DEV, setup new config with config tool, download complete new code. M119: endstops hit: x_min:L y_min:L z_min:L Z-probe state:LG32 S2 autolevelingG1 Z0 - test Z0 (OK)M119: endstops hit: x_min:L y_min:L z_min:L Z-probe state:H PrintM109 S…
-
Missing Z_min is peculiar, as I use the same config.h for dev and stable versions. Stable has z_min, dev not. I will double check again - I think sometimes the configuration tool alters some parameters if I switch dev and stable, so I rather edit co…
-
I changed firmware to 0.9.2.9, probe leveling function better, than Dev (same config.h). Printing: Prusa Slicer - best result, but when printing, it goes into bed, probably - 2 mm :-) // dev goes + 2mmSlicer - good, goes + 2 mmCura - bad, goes + 2 …
-
Gcode: ; generated by Slic3r 1.34.1-prusa3d-win64 on 2017-04-27 at 22:15:03 ; external perimeters extrusion width = 0.40mm; perimeters extrusion width = 0.48mm; infill extrusion width = 0.48mm; solid infill extrusion width = 0.48mm; top infill extru…
-
now playing with g30 on different x/y. When almost on the odge opposite x/y home, G30 causes moving UP with error "could not activate z-probe offset due to coordinate constrains... why? almost all bed G30 is OK... because it could be over config set…
-
17:40:52.342 : g29 s2 17:40:52.470 : Info:Autoleveling disabled17:40:54.113 : Z-probe:1.022 X:0.00 Y:0.0017:40:56.748 : Z-probe:1.251 X:150.00 Y:0.0017:41:00.128 : Z-probe:1.145 X:0.00 Y:180.0017:41:00.128 : Z-probe average height:1.1417:41:00.129 :…
-
Stop before trigger: there is no message in the log. It just stops, no info in the log. Homing with preheat: I have never used this - how to activate? I have found M109 S[temperature] ; set the extruder temp and wait - is that OK? M119 will test whe…
-
g92 does nothing... (any parameter x, y, z)
-
After print:G28G1 Z0it does nothing - it think it has z at 0G1 Z2 goes 2 upG1 Z-2 does nothinghoming Z stops on 2.3 without probe trigger
-
Interesting is, that in the past, with using the recommended Z calibration, once the first layer was OK - but the other were +2.3 mm... then all the time the Z0 is Z0 + 2.3 mm
-
G32, G1 Z0 is Z0 = m114 - 0.00 Print - + cca 2.3 mm, but m114 says z 0.00 #define ALWAYS_CHECK_ENDSTOPS 0 Printer heats, but when heat is OK, go downs to "Z0" which is not real Z0... (+ 2,...mm).
-
Printing adds cca 2.3 mm (from z0) G32 again after print 19:19:52.821 : g32 s219:19:52.914 : Z correction disabled19:19:52.915 : Info:Autoleveling disabled19:19:55.002 : Z-probe:1.259 X:0.00 Y:0.0019:19:56.196 : Z-probe:1.350 X:0.00 Y:60.0019:19:58…
-
I used case 2. I do not understand "includes that z height after probing?" 19:04:02.066 : m11919:04:02.396 : endstops hit: x_min:L y_min:L Z-probe state:L19:04:25.842 : g3219:04:26.461 : Z correction disabled19:04:26.461 : Info:Autoleveling disabled…
-
I changed Z_PROBE_ON_HIGH 0 (was 1), G32 OK, but prints still high - its lower, but not on Z :-(
-
Now endstops m119: x_min:L y_min:L Z-probe state:H but probe is off... (using case 2)
-
OK, thanks!
-
Thanks, so both cases are equal for autoleveling probe as Z-Min without Z-Max endstop? I am little confused, I cant understand the basic principle...
-
So I set and will test: #define ENDSTOP_Z_BACK_ON_HOME 1 #define MOVE_Z_WHEN_HOMED 2 #define ENDSTOP_PULLUP_Z_MAX false#define ENDSTOP_Z_MAX_INVERTING false#define MAX_HARDWARE_ENDSTOP_Z false#define max_software_endstop_r true #define min_software…
-
I can´t find any reason, why it prints 1.9 mm above the surface... Thanks for any idea...