Thor, or should that be Zeus?

[Chaz]

Can anyone help with some Fusion 360 and post processing.

I use the standard Mach 3 post processor and override G28 in the options.

However in the code I keep getting this. This command tells my machine to home the Z axis but always hits the top limit. So I manually delete it each time (which is a pain to do).

Why do I get this and what does it mean / what is the purpose?

I refer to the G43 line at the bottom. It seems to use the machine coord not the Z that I zero manually.

7007)
(T2 D=10. CR=0. - ZMIN=-29.99 - FLAT END MILL)
G90 G94 G91.1 G40 G49 G17
G21

(ADAPTIVE3)
M5
M9
T2 M6
S4000 M3
G54
M8
G0 X41.253 Y-56.367
G43 Z15. H2

[AndrewMawson]

But the G43 is a tool length compensation, so perhaps something is set wrong in your Fusion Tool Table ?

[Ger21]

More likely your Mach3 tool table.
G43 does not use machine coordinates. But it does change Z zero to correspond to the length of tool #2 (H2) in your tool table.

[Chaz]

It uses the one height set in the operation, but seems to ignore that it's not machine values and basically tries to go past the machine 0 and of course hits the limit.

I'll snoop around later and do some testing.

[Chaz]

Thor's Z Axis is alive. Short vid of it running on my very wonky table at 5000mm/min - 25mm cycles via the PID tuner. No tuning has taken place yet, Ill do this once mounted and limit switches have been installed.

[AndrewMawson]

Vertical Video Syndrome !!!!!! :

https://www.youtube.com/watch?v=Bt9zSfinwFA

[Chaz]

Vertical Video Syndrome !!!!!! :

https://www.youtube.com/watch?v=Bt9zSfinwFA

Lol, sorry.

[Davek0974]

Thor's Z Axis is alive. Short vid of it running on my very wonky table at 5000mm/min - 25mm cycles via the PID tuner. No tuning has taken place yet, Ill do this once mounted and limit switches have been installed.

Looking good, try tuning manually - adjust the I & D values, there are documents online about doing this but its also in the CS-LABS booklet. The delay between reverse is a homing error - its not settling at at the zero point fast enough you should see the numbers very slowly retuning to zero and then the green LED comes on in the tuning page. Tweak the values and you should see following error drop and the cycle time rise - in the end it will be going bang-bang-bang one way then instantly the other. You need fast homing (return to zero) and not a slow creep.

The auto-tune is pretty pants really, always tune with the final load, rough tuning is fine for tests but when finished and assembled tune again with all load attached.

[Chaz]

Looking good, try tuning manually - adjust the I & D values, there are documents online about doing this but its also in the CS-LABS booklet. The delay between reverse is a homing error - its not settling at at the zero point fast enough you should see the numbers very slowly retuning to zero and then the green LED comes on in the tuning page. Tweak the values and you should see following error drop and the cycle time rise - in the end it will be going bang-bang-bang one way then instantly the other. You need fast homing (return to zero) and not a slow creep.

The auto-tune is pretty pants really, always tune with the final load, rough tuning is fine for tests but when finished and assembled tune again with all load attached.

Thanks. Ye, its dwelling too long before it finds 0 / Green LED. Playing with the values will improved that. Ill sort that out once its mounted properly and I have limit switches to stop a run away / something going wrong.

The Panasonic drives also offer a lot of tuning. I am not sure how the CS Labs and Panasonic tuning will go exist. Ill likely set the drive to be on a mild auto tune and then use the CS Labs for the overall tuning.

Very curious too to understand how the setup can deal with inertia / whiplash. I refer to demos where they move something that has a ball on a stick and tune the drive that basically shows no 'pendulum' effect when the device stops and starts in different directions.