Hello Guest it is April 24, 2024, 09:25:56 PM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - archerks

Pages: 1 2 3 »
1
Mach4 General Discussion / Mach4 build 3390 - Keyboard Inputs
« on: May 27, 2017, 01:47:47 AM »
On build 3390 the Keyboard Inputs seem to be messed up. On the Inc (XplusINC and etc.)  ones I can't make them work without a hotkey, they always control the X axis. This is on the demo version. Anyone else have this problem.

2
Yes, they seem to be correct. Checked the keyboard inputs and Mach input signals.


3
The first one is for Feed Hold which works, the commented out one is for the stop which does not work when the comments are removed.

4
Another error when entering message. The actual code does use input 62 not the 623 that I show above.
I have to learn to type more accurate and reread my messages.
Below is a copy and paste of what is in Mach4

if mc.mcSignalGetState (mc.mcSignalGetHandle (inst, mc.ISIG_INPUT63)) == 1 then
    -- mcSignalWait(inst, ISIG_INPUT63, WAIT_MODE_Low, 0)
    mc.mcCntlFeedHold (inst)
else
    --   Do something else
end

--------------------------------------------------------------------------------------

--if mc.mcSignalGetState (mc.mcSignalGetHandle (inst, mc.ISIG_INPUT62)) == 1 then
--    mc.mcCntlCycleStop (inst)
--else
--    --   Do something else
--end

5
Thanks, but i do have with as mc.mcCntlCycleStop with the capital C's in the code I was trying. I just didn't get it right when I typed my question in the forum.
Dave

6
The Feed Hold does work when I press the Space bar. Using it as an example I tried to make the Esc key do the stop function but it errors out on me. Below is the code...
Any suggestions will be greatly appreciated.

--this works for the Feed Hold
if mc.mcSignalGetState (mc.mcSignalGetHandle (inst, mc.ISIG_INPUT63) == 1 then
     mc.mcCntlFeedHold (inst)
else
     --  Do something else
End

_________________________________________________________________

--This errors out
if mc.mcSignalGetState (mc.mcSignalGetHandle (inst, mc.ISIG_INPUT623) == 1 then
     mc.mcCntlcycleStop (inst)
else
     --  Do something else
End

7
General Mach Discussion / Z axis count loss after running 3d profile
« on: July 02, 2009, 11:12:12 AM »
I have a small router table. The 3 axis all check out fine when you put a dial indicator and run a test back and forth. But when I run a 3D file that has a lot of Z up and down movement, it seems to loose some counts. The file takes about 8 minutes to cut and the Z axis will usually be .003 to .005 inches lower than when I started. So I have to rezero the Z after every run. All motors are the same and the velocity set to 150 ipm, the acceleration to 6 and the step pulse to 2. For the Z, I have tried different velocities, down to 50 ipm and different accelerations but they don't affect the lost .003 inches after every run. Any suggestions on what to try to improve this will be greatly appreciated.

Note.. all motors are steppers with gecko drives
Dave

8
General Mach Discussion / Re: Toolpath Display
« on: May 20, 2009, 04:55:21 PM »
Hood,
Checking the Tool Position, looks like that took care of it. It now works with my modified and the original 1024.set file.
Thank you
Dave

9
General Mach Discussion / Re: Toolpath Display
« on: May 20, 2009, 04:49:36 PM »
There is no G92 in the code....
Dave

10
General Mach Discussion / Re: Toolpath Display
« on: May 20, 2009, 04:41:39 PM »
Here is the xml file
Dave

Pages: 1 2 3 »