LinkBack URL
About LinkBacks
Does the program maybe have G43 - tool length offset from tool table? If so it may be compensating for the tool length (thinks its longer than it is).
Mike
| | |
Something wrong with "Z" axis The machine was working great. And then suddenly when I load a new G-Code in it the Z axis only goes about the half way depth then I have put in G-code. For example if I put to mill down .030 it actually mill about 0.013 - 0.015. But it only happens with the program loaded. When I jog it will go exactly as I put.
I'm using probotix USB board and drivers. Software is Planet-CNC.
I forgot to mention that I have calibrated all 3 axis using a digital dial indicator.
Last edited by Pysiek; 04-09-2012 at 09:46 PM. Reason: forgot to mention the dial indicator
Does the program maybe have G43 - tool length offset from tool table? If so it may be compensating for the tool length (thinks its longer than it is).
Mike
There is no G43 code. Is it possible that the program is so big that the board can't handle it?
Sent from my HTC Sensation 4G using Tapatalk
If Mach3 is missing the license file, it has a line number limit.
I'm using Planet-CNC software
Oops, sorry. Missed that.
Double check your z-axis calibration and make sure that it is not set to metric.Originally Posted by Pysiek
I already triple check it. And it's not set to metric
does it only happen with only one specific GCode or all loaded GCode files?
No. It happens with all the gcodes. I already reset the software to default settings but still no luck. Also I disconnect all limit switches and still have the same problem. Next time I will try to put software on my spare laptop amd try it from there
Sent from my HTC Sensation 4G using Tapatalk 2
If the software is set up properly ( including the lead screw TPI setting, the TPI on my z-axis lead screw is different that the ones on the x and y axis ) then you are likely looking at a hardware issue. So here are some things to look for.
1. The driver that the motor is connected to may be causing the problem.
*** Try hooking the motor up to one of the other drivers
and see if you get the same or different results.
2. It is possible that your wiring connections are not as solid as they should be.
*** I had some issues with that when I set up my bluemax. I ended up stripping a longer length of the wire, folded it over and twisted it together in order to make a more solid and stronger contact within the screw clamps on the connectors.
Bear in mind that the wiring can be hard to determine if it is properly seated. Give each of the wires on your z-axis a bit of a tug. If one comes out, you have most likely found your problem.
3. If your z-axis stepper is connect via a rubber or vinyl hose to the lead screw, it is possible for that to slip.
*** Placing a mark on the connector that you can easily see will make it easier to determine if the connection is slipping. If that turns out to be the case, put a small zip tie around it and use a pair of pliers to get it as tight as possible. The extra pressure will stop the slippage if there is any.
4. Check your driver's jumper switches and verify with your manual that those are set correctly as well.
5. It is unlikely that the z-axis is binding but you should check for that as well.
6. You can test the motor itself by swapping it out with one of those that are not causing you problems.
You've no doubt gone over these things already, but these are the only things I'm aware of that can cause the problems your experiencing.
Hope this helps.
Scott A Tovey
Since he states that jogging moves the Z axis exactly the right amount it does not seem to be anything hardware related but purely in the software.
Sounds like it is only getting half the set value (or close too) from the Gcode. Did this start AFTER a calibration or what was changed before this started acting strange.
MP*10
Posting Permissions
| | |
