@dc42 I have calibrated the inductive sensor Z with the tutorial that you have passed me, the problem is that when I define the new Z = 0 with G92 and modify Z in G31 in the config.g file, the board resets and when loading the file it returns to take Z = 0 with respect to the limit switches so that the nozzle collides with the bed again. I have added the instruction G30 S-1 in the cura code and then a G92 X0 Y0 Z0 E0, it looks more or less good, but a high tilt with respect to the bed and when using self-compensation in some areas it stays a little more raised with what some layers do not weld well. I also wanted to ask if in the config.g file, when I define the Z ofset in G31 is the distance left to the nozzle to touch the bed or when it starts printing is what goes down to reach Z = 0?
Latest posts made by Kurn
-
RE: Duet Ethernet Mesh bed compensation
-
RE: Duet Ethernet Mesh bed compensation
Ok, so I guess I should tell the beginning of the cura code to take Z = 0 when I use G30, is that so?
-
RE: Duet Ethernet Mesh bed compensation
Great, now the errors don't come out. I wanted to ask you several questions, the first is that when you use the M557 command and define the final distance in X and Y, would that be the position of the nozzle or the sensor? Now, when printing, I am compensated, but the nozzle is very close to the bed and I have to use Z Baby Stepping, is it a failure to define Z in G31 or can it be a cura failure? (I enclose the gcode of the beginning of cura) Should I remove the initial gcode of cura?
-
Duet Ethernet Mesh bed compensation
Hello, when I try to do the self-calibration map from the web panel with the G32 command, I get an error in the console that I could not go through several points. Once finished, I save it with the M374 command in the bed.g file. Then at the end of the config.g file, I have since every time I start the controller, load the compensation plane with M375, but it tells me that it cannot load it. When I print a piece, the compensation of the bed does not apply and I don't know why it is due. I use an NPN inductive sensor. I attach files to see if someone can tell me where the problem is.
0_1565215339988_console (1).txt
0_1565215441371_config.g
0_1565215468105_homeall.g
0_1565215485610_heightmap.csv
0_1565248428949_bed.g