6040Z controller

[RichardR]

I did what you said for the Y and X axis and that was ok but it would not move on the Z axis but mach 3 asked how far it moved, also it is now not operating on the G code I put in G0 Y20 X20 also when I tried a manual jog it moved a minute distance but only every time I pressed the keyboard jog button. I had a look around mach 3 but could not find what the problem is

[JAZZCNC]

I did what you said for the Y and X axis and that was ok but it would not move on the Z axis but mach 3 asked how far it moved, also it is now not operating on the G code I put in G0 Y20 X20 also when I tried a manual jog it moved a minute distance but only every time I pressed the keyboard jog button. I had a look around mach 3 but could not find what the problem is

Ok regards the Z axis then you need to enter a negative number, all Z moves are usually negative moves. So try something like -20. If you don't enter a value after it moves then Mach3 will default back to what was entered before.

I'm not clear on what your saying regards it not moving.? I think your saying it's NOT moving when you enter g0 Y20 X20 into the MDI.? If this is the case then make sure you are not at those coordinates already as this about the only reason I can think of why it wouldn't move.!

Best thing to do is ZERO each axis then enter G0 Y20 X20. If it doesn't move then I can't imagine why not as just setting the steps per with the calibration tool shouldn't stop it moving unless something went badly wrong. What are the numbers entered into the Steps Per for each axis.?

Regards the tiny move distance then make sure you haven't accidentally put it into Step Mode. Click the TAB key and the Jog tab will come out from the side. In there you will see JOG MODE button which will cycle between Step and continous Mode.

[RichardR]

I don't know what I did but I got it all moving on the manual jog , then realised that it was a negative movement, so all working, I checked the amount it moved after my G code input and it was within a 0.??mmm I guess that due to the pitch on the screw thread it is as near as possible, or should I change to inches and try that?

[Clive S]

I don't know what I did but I got it all moving on the manual jog , then realised that it was a negative movement, so all working, I checked the amount it moved after my G code input and it was within a 0.??mmm I guess that due to the pitch on the screw thread it is as near as possible, or should I change to inches and try that?

You can work in mm or inches by using G21 or G20 at the top of the gcode.

How near is 0.??mm. Now you have it running cut a square out and measure the square with a vernier
Also you can measure the diagonals to see if the gantry is out of square.

Edit: Joking aside you have coma a long way from spitting the dummy out.

[RichardR]

Not quite ready to do any cutting, I need to understand how to set coordinates, also I need to fit a sacrificial board and do a levelling sweep which will be good practise, I think a probe plate would be a good idea, then I would know the exact distance the top of the tool is before I start any job, all this will take me a little while.
It's a shame I did not get the CD with it as I understand it has some test programmes which would probably have given me some idea of programming jobs.

[JAZZCNC]

Not quite ready to do any cutting, I need to understand how to set coordinates, also I need to fit a sacrificial board and do a levelling sweep which will be good practise, I think a probe plate would be a good idea, then I would know the exact distance the top of the tool is before I start any job, all this will take me a little while.
It's a shame I did not get the CD with it as I understand it has some test programmes which would probably have given me some idea of programming jobs.

Richard, you are along way from needing a probe plate, it's not just a case of pluging in the probe plate. You need a macro that works out the tool offsets and some other magic behind the scenes, you will also need a modified screen set.
Also you will be better learning how to set it manually as the probe plates are not always possible to use on some jobs so understanding how it all works is worth the time it takes to learn.

Now regards the movement and whether to use MM's or Inch then it doesn't matter because if your Steps per setting are wrong they will be wrong for both. It's also more involved because you will have convert metric pitch to imperial which uses turns per inch.

The steps per setting isn't something you can guess at, it's a calculated figure based on several components like I mentioned in my last post. If it's wrong by even a few digits then it will affect the accuracy. If you don't know the ballscrew pitch and the micro stepping so it can be calculated then you have to use the measurement method like I showed you. The accuracy of the Steps per then depends on how accurately you measure the distance it moved, measure it wrong and it will move the wrong distance.
This is the Same whether you use Imperial or Metric units so changing to INCH units won't make a jot of difference. It will still be wrong in either units.

Clive's suggestion to use G20 for inch is a workaround if you are using imperial G-code but it's less than ideal if you are using on a machine set for Metric units because it only takes into account the coordinates and not the feed rates. To see this in action try one of the G-code files included with mach3 like the roadrunner.
This code was written for Imperial units and if you run it on a machine set in metric units using G21 then it will cut very small, 25.4 times smaller to be precise, because when it commands a move like X10 it actually means move X 10 inch but instead will move 10mm.

Now if you use Clive's suggestion and type G20 this will put you into Imperial units and the size will be correct as X10 will move 10inch but what it doesn't do is take into account the feed rates. The imperial code will command a feed based on imperial units so lets say it calls for F100 it actually means move at 100 inch/min ( 2540mm/min) but because your system is set and tuned to metric units the feed will actually be 100mm/min and the G20 code doesn't do anything to change this.
To get around this and use imperial code the best approach is to create another separate profile with the machine tuned for imperial units. Then when cutting imperial G-code you just load this profile and all will work correctly.

If you would like me to explain how the coordinate systems work and how to setup cutting a job just ask.