Machsupport Forum
Mach Discussion => General Mach Discussion => Topic started by: Telad on December 05, 2012, 08:12:54 PM
-
Hello,
I have used an old version of Mach 3 at a friends house for some time. I setup my machine and have the table working and cutting correctly.
Each of the axis's move in inches and I have verified the machine actually moves 1 in when I tell it to.
Now my problem, the units/unit still seems like it is displaying in cm. I have the system configured for in (config-units).
Any ideas what I have missed?
Thanks
-
What version of Mach are you using?
RICH
-
Mach3 R3.043.066
I have confirmed it's units of mm/min.
-
Bit confused to what you are saying, if you command a move of 1 inch you say it moves 1 inch then you say you think it is displaying in mm/min?
Can you try and explain a bit better?
Hood
-
On the control screen there is a section called Feed Rate. The units/min is displaying the speed the machine is moving in mm/min.
I have set the units as inches however this seems to still want to use mm.
-
Attach your xml please.
Hood
-
see attached
-
Working fine here, if I MDI a G1 with a F20 then it moves at 20 IPM, F50 it moves 50IPM, F85/85IPM.
Are you running coe when you are seeing the feerate showing high? If so could the code be written in metric, ie has a G21 in it?
Hood
-
Attached is the Gcode I ran. It cuts out the part just fine but the section I have pointed to in the pic is wrong.
-
Attach the code and say what the units /min DRO says.
Hood
-
What do you mean by units/dro? I don't have any feedback connected.
Attached is the gcode.
-
The DRO you have arrowed is Units Per Minute DRO, what is it saying when running the code as you are saying it is wrong.
Hood
-
Your code does not have a G1 at the start of the first part so it will run as G0 moves (rapid speed) as that was the last command, so even though there is a F2 there it will be ignored. If you put a G1 on line N112 like below it should work
N112 G1 X1.1701
Hood
-
While its milling (after the tool change) it says it's cutting at ~46. While jogging I get ~200.
During both operations the feed rate override was left at it's default position (100%).
In response to your last post during the first stage the machine is drilling holes not milling. It is desired to move at full speed to the next point then move the z-axis at the slower speed.
There is no way my machine is moving in excess of 200ipm as that would clear my 12x24 table in 7 seconds :)
By the way thanks for your rapid responses.
-
When I jog one axis it shows 85IPM as it should as that is your rapid. If You jog two axis together or command a GO move of multiple axis then that DRO will show the blended feedrate, I suspect that is what you are seeing.
Hood
-
When I jog one axis I get 172-176... almost exactly twice the actual value.
It looks like it's not a unit issue, but i'm still not sure what's the issue.
My driver boards are setup for microstepping... but turning it off make the machine run slower not faster and the distance jogged is accurate.
-
Ok its just dawned on me you are using the pokeys as a motion controller. That could well be where the issue is as it may be reporting the feed incorrectly. One thing to try is go to Config then Ports and Pins and set the Frequency to 25KHz and see if that makes a difference, you will likely need to restart Mach after you change it.
If that doesnt help then possibly ask on the Pokeys section as it may be a known issue. The SmoothStepper suffered from that problem in the beginning if the frequency on Ports and Pins was set at anything other than 25KHz. It was just a reporting issue rather than a real one and I am thinking that is likely the case with you and the PoKeys.
Hood
-
Just a quick update. You solution may be the cause however changing the freq had no effect.
I posted on the other forum as requested however the moderator could not confirm if it was a know issue until he talks to someone from Mach3.
It has been over 10 days since his last response.
After further production runs we have determined it seems to be more then 2x the actual.
Any help you can provide would be greatly appreciated.
-
Is it actually moving at the correct rate and just the reporting that is wrong?
Hood
-
That is correct
-
Ok then its not so bad as you can at least still use things. As I mentioned earlier this was an issue with the SmoothStepper in the early testing of it and was seen, if I recall, if you had the kernel set to anything other than 25KHz. Might be worth trying different kernel settings in Mach and restarting to see if any correct the reporting issue. As the pulsing is done externally in the PoKeys changing the kernel will not, or at least should not, affect motion.
Failing that helping then I am afraid you will just have to press NeaTO for some action.
Hood