Stop after G29 Startcode

[Mitch95]

Hey

After some trouble installing the 3D Touch, i was really happy after it works.
But saddly i got a new Problem:
I Put the G29 to my Start Code in Cura, when i Start the Print, it Auto leveling the bed just fine but then it do nothing, like the Print is finished.

Can someone give me a working Start/End Code with Auto Leveling enabled?
I got so much trouble with this Printer, its really sad... Would be Great if someone can help me here

Edit: Normally im using Cura, but today i also tried Slic3r, still no luck.
When i load the Gcode from the SD Card, everthing seems fine.
The LCD screen displays the progress, but as soon as auto leveling is complete, the screen suddenly shows like nothing is printing and returns to home position. No matter what I do or set, before even a millimeter is printed, it finishes the process.

[William]

Hi, In general, only the high limit switch is used (that is, the Z-axis limit switch is located at the maximum Z coordinate), and the Z-axis height test micro switch is attached to the extrusion head, which is suitable for use. The G29 command tests the Z-axis height. Other mechanical configurations are not suitable for the G29 command. The G29 command is configured by firmware.

[Marcellus]

Hello
Same Problem here with capacitive Sensor. But only when i print from sdcard. Very strange, I get the startgcode from the geeetech sdcard testprint with Editor (i just write the G29 in it) ... Then it works??? But now a few days later it does not work??? I dont change slicer or something... Printing with usb connect is no problem with the same startgcode.
Firmware Bug?

Autoleveling does not work good. I must leveling before every Print! Now i have 2 z-offsets! Sometimes 0,6 is good and sometimes 2,2 works. It change and sometimes, if i don't level before print, the nozzle hits the bed at 2,2. Sometimes at 0,6 the nozzle prints in the Air. Very strange. I think geeetech has a bad Firmware.

Sorry for my english...

Greets

[Marcellus]

Hello
Same Problem here with capacitive Sensor. But only when i print from sdcard. Very strange, I get the startgcode from the geeetech sdcard testprint with Editor (i just write the G29 in it) ... Then it works??? But now a few days later it does not work??? I dont change slicer or something... Printing with usb connect is no problem with the same startgcode.
Firmware Bug?

Autoleveling does not work good. I must leveling before every Print! Now i have 2 z-offsets! Sometimes 0,6 is good and sometimes 2,2 works. It change and sometimes, if i don't level before print, the nozzle hits the bed at 2,2. Sometimes at 0,6 the nozzle prints in the Air. Very strange. I think geeetech has a bad Firmware.

Sorry for my english...

Greets

[William]

Hi, you can try to calibrate the extruder and the shaft.

[Marcellus]

Hello William
Thanks for information.
Extruder and shaft still calibrated.
When the Z-Offset is right and i print without sdcard (with usb-connection to pc) all is fine. Quality is good. I can not print from sdcard... and the z-offset changes irregularly.
I think its a firmeware bug...
when can we hope for a new firmware?

greets

[William]

Thanks for your feedback, I will convey.

[Marcellus]

If it helps you...
HW: V3.3
FW: V1.37.58

[Marcellus]

the problem was that I had inserted the G29 command in the startcode.
When it's out, autolevel works and the printer starts to print.
Some things can be so easy ...
No frimware error, it was user error

And now the z-offset is always 0.6, why ever?!?
Now printing is funny thanks for support

[Marcellus]

Here is an update:

The z-offset is still changing irregularly. Even if you do the autoleveling (capacitive geeetech sensor) before each print you are not on the safe side. I dont know where is the mistake.
I came across this post, here it seems to be the same problem:

https://www.geeetech.com/forum/viewtopi ... 1&start=10

Note on G29 in the start code:
When printing from the SD card, do not write G29 in the statrcode.
If you print via USB connection (Simplify3d), the G29 must be in the start code, otherwise the autoleveling will not be executed. Very strange!
This is the current situation, we hope for corrected firmware ...