Auto leveling Issue

[Iakouben]

Hi pknoe3lh,

I started playing with your software last night, and I tried to do the auto leveling procedure. After playing with the settings, I stumbled upon the same result as user McNugget6750 has. My machine completes the G28 sequence, moves to [10, 10](my defined start point for the auto leveling) and sends the command G1 Z-5, after which the procedure stops. I have tried both marlin 1.0.2 and 1.1.0 RC7, and I'm getting the same issue for both firmware versions. After aborting the auto leveling procedure, I used M119 to check if the Z probe is triggered and it is.

As far as I am aware, marlin doesn't echo the Z location, or a Z trigger event on completion of the G1 command, it will just complete the command and wait for further input. G30 is used to probe for the Z location, and it will echo at what point the Z axis was hit at.

I'm not sure if I'm doing something wrong though.

Best regards, Nikolai Iakoubenia.

[im-pro-at]

Hello lakouben,

I programmed the auto leveling long time ago ... I use the following Firmware: https://github.com/pknoe3lh/Marlin My last commit was Oct 31, 2015 so its far behind....

My Marlin version echo a end stop hit event ....
I cannot upgrade because i use a lot of modified stuff ...

Can you send me a correct sequence what the application have to send to get the hit report. And what it will get when there was no hit? Then i can modify the code ;-)

I now playing around with grbl so there will hopfully be an update soon :-)

greetings Patrick

By the way you also always welcome to contribute code changes!

[skulbl4k4]

Hi, i have the same problème, :( its a good contrôler. you are fixe the problème ?

see you soon.

[im-pro-at]

I used Auto leveling again and had not problems! Please send me the setup and settings and i can try to understand the problem.

greetings Patrick

[skulbl4k4]

Hi,you can send the firmware (marlin and cnc gcode controlleur) for the lasted version of your CNC ? thanks ! De Blaireville Gaël Chemin du Ruz-d'Agiez 16B  1350 Orbe  +41 79 391 74 01 theboum69@yahoo.fr

Le Mercredi 28 décembre 2016 13h20, Patrick Knöbel <notifications@github.com> a écrit :

I used Auto leveling again and had not problems! Please send me the setup and settings and i can try to understand the problem.greetings Patrick— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[theinlinaung2010]

I also have the auto levelling issue. I can home the Z axis but the Z carriage still descends despite the trigger of the probe. I am using Marlin.

[im-pro-at]

Ok I dont have a Marlin Setup.

So can you tell me what commands are needed and what response is given.

greetings Patrick

[tomtenberge]

such a pitty noone followed up on this :( the command for marlin is "G30"

Picture of the communications : (https://i.gyazo.com/7e87c0b7b6f0b0dc10f39a078f7617fa.png)

hopefully this helps ps, this is with a offset of 0 on the probe

[MattRSON]

Is there any update with this? I am having the same problem with it probing one point then sitting there till it times out. I have tried G30 and I think that is the way to go but don't know how to implement it so that it uses the echo and moves to the next point.

[McNugget6750]

I'm forcing my way through this as your software has the only actually working auto-level feature for pcb milling I have found so far. I'm using GRBL-MEGA 1.1 latest.

Sequence:

1. Go manually close to the surface using the jog controlls
2. G92Z0
3. Lift 5mm
4. hit auto level start.
5. The head now moves down slowly until it hits the surface after which the following ALERT appears which also disconnects from GRBL (a feature that I'd like to remove. Disconnecting at any alert or error is not a good idea). ""Timeout: No end stop hit!""

I tracked down the error to JPanelAutoLevel.java but I can't work out how the system processes the responses from GRBL to determine that there was a contact or not. Could you please help me find the code section I should be looking?

One note: In GRBL 1.1 the probe pin reporting is different from 0.9 and earlier. It directly reports that a probe pin was hit, not a Z-axis endstop. I assume the issues could be there.

GRBL reports the hit correctly but the hit is not understood:

Any ideas?

[im-pro-at]

Hallo,

I upgraded to GRPL 1.1 and the only thing that was not working out of the box was to get the position update! I fixed that right now.

You can also see in the log "INFO: Received Z hit at: -22.1620" So the system is reporting it correctly!

Then its also correctly Asking for the Position!

But it does not report it and this should be fixed now ;-)

greetings Patrick

[im-pro-at]

Oh you also need to set the following settings in GRBL to report the WPos: $10=2

[McNugget6750]

Hey Patrick,

Excellent! I pulled your last changes and it works! Thank you very much for checking this out for quickly!

[im-pro-at]

You are welcome ;-)