Z axis moves below set zero

[whensparksfly]

I done the automatic motor configuration in the setting menu measured it movement it was correct.
When I toggle the z and y with the arow keys it will work in mm I can be seen that the movment matchs the fro but when z is moved the movement in the dro and a axis will move in inchs

Sent from my SM-G361F using Tapatalk

[magicniner]

When I toggle the z and y with the arow keys it will work in mm I can be seen that the movment matchs the fro but when z is moved the movement in the dro and a axis will move in inchs

Sent from my SM-G361F using Tapatalk

The only way that can happen is if you've got your motor tuning wrong.
Motor tuning units are set for all axes at once so you can't have a mix.
If tuning units are set to mm and X and Y work fine you will get really close if you take the number for "steps per" currently set for Z and multiply it by 25.4, Mach3 can't tell when you instruct it to do stupid things, it simply does what it's told.

- Nick

[lucan07]

When I stated in your previous thread to check wiring you responded I was definitely wrong then that you had found the broken wire.
When I stated the code was wrong and would not run in a different thread, you replied I was wrong and later PM'd me to get the edit to correct that code.
Again I try all axis are using same measurement scales they cannot do otherwise, therefore your tuning steps per unit are incorrect they are for mm's if axis is moving in mm and for Inches or out by a factor of 2540% if axis is moving in inches instead of mm.
There is no alternative computers just do what they are told, you put rubbish in you will only get rubbish out its the way it is.

[magicniner]

out by a factor of 2540%

Can you show your working for the maths that give you this result? ;-)

[lucan07]

Can you show your working for the maths that give you this result? ;-)

1 inch approx 25.4 mm so if moving 25.4 to 1 = 2540%

[JAZZCNC]

Your trying to run before can walk.??

First job before trying to run any G-code is to make sure the machine is setup correctly and know how mach3 works. Ie It's fundimental thing to know why Dro is Red or Green. Means the Axis as been homed or pushed ref all home if no home switches.
I suggets you read the manual and learn Mach basics before trying to run G-code.

It's impossible to Mix Inch and MM in same setup without using a scaling factor. So if this is definatley happening then highly likely your Steps per setting is wrong.

To help you further you need to give more detailed info about your system. Your one line cryptic replies are pretty useless.

Tell us the Micro steps set on drives and the pitch of the ballscrew and if any ratio using timing belts etc and will give you the exact steps per setting. This will remove any guess work on your part.

When the Steps Per setting is correct then any error is either from the G-code or Mechanical. Mach3 just does exactly what it's told.

[JAZZCNC]

1 inch approx 25.4 mm so if moving 25.4 to 1 = 2540%

Mach doesn't scale by percent enter 2540 into the scale Dro and see what happens.!!!

[lucan07]

Mach doesn't scale by percent enter 2540 into the scale Dro and see what happens.!!!

I know how it works it was the factor of the tuning error required to produce results claimed.

[magicniner]

1 inch approx 25.4 mm so if moving 25.4 to 1 = 2540%

Sorry, yes. I didn't read carefully enough.
What confused me was that I'd already given a direct solution by telling the OP to multiply his Z axis steps per by 25.4 rather than spewing out proportions or percentages for the OP to work out, which might confuse him as easily as me ;-)

[lucan07]

I doubt its moving that far I think it may be out but he obviously has not RTFM and in other threads has claimed similar which is where we got to auto tuning as simpler than trying to get information required to do calculations for him. Over several different threads its obvious he doesn't quite understand how Mach works when told its definitely tuned right I tried to point out margin of error that would be required so used 2540% to emphasize enormity rather than 25.4x to attain the results claimed.
I would imagine set z Axis zero to top of table rather than top of material as his sole piece of G-code never goes negative or below 1.5mm, just difficult to get information to help would guess all being done from his phone with the minimal responses.