I also cant see why it works ok in manual calls with no code loaded (see video) but fails when in code mode?

Ok, i'm getting closer

It seems if i call all tools my the MDI it works, but will verify this with a repeat TC code program in a minute.
When you call a tool by MDI using M6T100 the Z DRO does NOT change.

Now, before i always set my Haimer probe by typing 100 in "Current Tool" DRO on the 2010 screen-set - do this and the Z DRO gets TLC applied to it - this is the cause of my issues i think, looks like the "Current Tool" DRO runs G43 H********* when you press enter on it - thus the cause of my lost Z travel.

I'm off to run some more tests but it feels like I will have to remove the "Current tool" DRO for safety reasons and do it all MDI, no biggy.

Nope, failed again

I manually ran through my whole tool rack, 20+ tools using MDI TxxM6 G0Z0 and every time it worked perfectly 100% tool on the TOM.

Loaded up the code, soft limit on Z Min warning, bypass, crash(e-stopped to avoid) The Z axis just dives.

Here is the screen after i stopped - the Z axis is at +85 and the code is calling for Z2 ??


The Offsets screen...


The Z of 186mm is about right - i had the z at about +30 when zeroing with the Haimer which is about 150mm long.

So, i'm stuck again - it works well in manual but can't run code


Have attached the exact code file below.

Probably digging myself in deeper here but could it be how i have my tool table setup?

I measure all my tools in a height-setter which feeds the result straight back to Mach TT, all tools have a height including the Haimer probe.

Now, i just went back and put the probe back in the spindle, and the Z was off by exactly the height of the probe - this is why it crashes.

BUT why only in code and not manual - it works perfectly in manual.

So confused now.

hi,

is it possible that your are doing th TLC twice ?

1. with the c-axis (knee)
2. SetCurrentTool(Tool) (m3 internal TLC)

just thinking while i went through your post's.

Thomas

I was unaware what setcurrenttool actually did - that may be a lead there, thanks.

If i leave setcurrenttool out, any idea what would happen??

do a little test to see what Setcurrenttool does.


-load 1024.set
-put in the tooltable  height 10.0 for tool1
-enter tool 0 in the tool Information dro
-push zerro z button
-enter tool 1 in the tool Information dro
-watch z coordinates

Thomas

If i leave setcurrenttool out, any idea what would happen??

i think, as far i have walked through your code,it will work like you expected,
because the TLC is done by your c-axis.

Thomas

That was my conclusion, off to try as soon as i stuff this sandwich down

Quote from: Davek0974 on January 28, 2018, 07:15:11 AM

If i leave setcurrenttool out, any idea what would happen??

i think, as far i have walked through your code,it will work like you expected,
because the TLC is done by your c-axis.

Thomas

NAILED IT!

Well spotted, TPS,

removed the Setcurrenttool line and it all fell into place

You can use the "Current tool" DRO anymore as it has no idea what the current tool is but i can live with that, i guess it could be fixed by adding a line to the macro that sets a pseudo current tool DRO on =screen to show the last selected tool call.

But its all working, part made, no mess ups.