Hello Guest it is April 17, 2024, 10:27:17 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 - Cbyrdtopper

621
Mach4 General Discussion / Re: Finish Z Move before X or Y
« on: March 02, 2018, 03:36:47 PM »
Thanks for the input Steve.  I thought there was a One Shot Exact Stop, I couldn't remember what the code was.  Thanks for bringing that to Light as well, that would be my preferred method as well.

622
Mach4 General Discussion / Re: Finish Z Move before X or Y
« on: March 02, 2018, 02:36:10 PM »
I'm assuming this is plunging into material and then cutting.  Adding G04 P50 on each Z Plunge move will fix your issue.  

If you are using a post processor, this could be annoying to change each instance.  But it will fix your issue.

G01 Z-20. F2031.24 (here is where it happens)
G04 P 50 (Add this line here)
Y100.806 F3562.48 (this move begins before the Z is in position. I have even tried to program a P5.0, but no effect)

623
Mach4 General Discussion / Re: Finish Z Move before X or Y
« on: March 02, 2018, 02:26:02 PM »
If I'm not mistaking, it is because you are in CV mode and your Z move is a G01 Feed move, mach is smoothing the transition from 1 line to the next.

Page 27 from the Mill GCode Programming Manual explains Exact Stop vs Constant Velocity.

624
Mach4 General Discussion / Re: Control is delayed after MDI or G Code
« on: February 28, 2018, 11:23:27 AM »
Brett,
The computer I was using is now being used for our shops PA system (break bells, time to go home bells, etc.)  But it still has the Mach stuff on there.  When I was having issues before, it didn't matter if I was using the SIM or if I was using the HiCON as my motion controller. 
Two weird things happened. 
1.  Now, since I don't have the HiCON on this computer anymore, I ran the SIM.  It works just fine on the Original Screen that I gave you.  Annoying.
2.  Your C8-2.set isn't allowing me to use Cycle Start, Feedhold, or Stop.

625
Mach4 General Discussion / Re: Control is delayed after MDI or G Code
« on: February 28, 2018, 09:38:02 AM »
Brett,
Here is the exact Screen I was using.  Although, I will say again, this was happening off the stock Mill and Lathe Screens as well.
Windows 7 Professional 64 Bit

626
Mach4 General Discussion / Re: Control is delayed after MDI or G Code
« on: February 28, 2018, 08:12:34 AM »
This must have been a processor issue.  I changed to a new (new) computer and the problem is gone.

627
Mach4 General Discussion / Re: Tools led
« on: February 24, 2018, 02:05:47 PM »
You need to change 1 thing and it will work.

if (currenttool == 1) then         Don't put the numbers in  " ".   
if (currenttool == 2) then 

I put tested this code in the PLC script and it works just fine. =)

local inst = mc.mcGetInstance()
local currenttool = mc.mcToolGetCurrent(inst)

if (currenttool == 1) then
     scr.SetProperty("TestLED", "Value", "1")
else
     scr.SetProperty("TestLED", "Value", "0")
end

628
Mach4 General Discussion / Control is delayed after MDI or G Code
« on: February 21, 2018, 02:27:23 PM »
I'm trying to get a new lathe working but I keep running into this issue. 

Whenever I run anything from MDI or G Code, Mach Control is delayed for something like 6 seconds before I can do anything again.  This is the first time I've ever had this issue.

I thought it may have been the additional scripts I added in, so I removed the CustomFunctions Module I made, and removed any custom scripts from the Screen Load and PLC scripts.  Still had the issue. 

Thought is may just be the lathe profile so I ran the unmolested Mach4Mill Profile.  Same issue.

I unistalled Mach4 altogether.  Same issue, mill and lathe.

Any Ideas?

629
Peter, thosj's post answered this question.
Bryanna posted this on the linked thread. 
https://www.machsupport.com/forum/index.php/topic,36545.msg250346.html#msg250346

630
Mach4 General Discussion / Re: Message Box with Cancel?
« on: February 10, 2018, 05:10:27 PM »
Daz,
Thanks for the video.   I had that error pop up yesterday, didn't know what it was.   I'm guessing once you close it out the first time, you're good to go until Mach gets shutdown and turned back on again?