Messages

101

Mach4 General Discussion / Re: TOOL changer problems after update

« on: July 27, 2019, 09:14:44 PM »

Try updating to the latest development version.

ftp://anonymous:guest@ftp.machsupport.com/Mach4/DevlopmentVersions/Mach4Hobby_Installer-4.2.0.4261.exe

Let me know if it helps please.

102

Mach4 General Discussion / Re: TOOL changer problems after update

« on: July 27, 2019, 12:51:22 PM »

The wait period must be larger than the minimum time it will take your motion device to receive, process and return it. 4 is not enough.

103

Mach4 General Discussion / Re: Mach4 build 4225 - Plasma feature instability

« on: July 27, 2019, 12:44:01 PM »

I would get the latest dev build and do a clean install of it, copy the default plasma profile as something unique and configure that unique profile for your machine. Old screens modules, macros, profiles, etc. may cause problems.

Yes, the THC module uses an OB axis to control the extra moves of the Z to maintain the set distance from the material. The reason it uses an OBA is because the only way to control a coordinated axis is through Gcode. OBA gives us a layer we can control independent of what the coordinated axes are doing.

Sounds like you should be running in Digital mode with the up and down outputs of your THC is mapped to the thc up and thc down input signals in Mach. Also make sure you have set the configure/plasma screen config. settings. What ever OBA you use, its motor should have the same motor tuning settings as your Z.

Make sure you play with the THC settings to get it all dialed in for your machine. Adjust rate, min, max, etc. I would start with very low adjust rates and a large window (min, max).

Not all motion devices support OBA. I know THC works well with the ESS.

It is a software solution and while not as fast as hardware it should be fast enough for the vast majority of users.   

The way it works is really pretty simple. If the THC sends an up or down signal a velocity jog of the OBA at the adjust rate is started in the right direction. When no signal exist, your slower than anti dive rate, THC is off, etc. a velocity jog stop is called.

M5 basically just turns off the torch and moves the OBA back to 0.000 where it should have been when the M3 began.

104

Mach4 General Discussion / Re: TOOL changer problems after update

« on: July 26, 2019, 10:59:08 PM »

Either of these should work for checking your rc.

wx.wxMessageBox(mcErrorCheck[rc])
mc.mcCntlSetLastError(inst, (mcErrorCheck[rc]))

105

Mach4 General Discussion / Re: Mach4 automatic ways oiler

« on: July 25, 2019, 04:07:01 PM »

I just added pmc to the allowed attachment file type list............. if you want to try attaching it again. I'm pretty sure it was added before as pcm. If computers are so smart I don't know why they don't know what we were trying to say. 

Garbage in = garbage out.

106

Mach4 General Discussion / Re: X move starts before Z move finishs

« on: July 25, 2019, 09:36:49 AM »

Well, the CV table was given so that users could truly tune their CV behavior. For that it works really well and just as intended. But it would take a lot of testing and just plain work to optimize it. Some did it but most want something that will get them a lot closer a lot faster and easier.

It just uses accel of the included axis motors to determine the worst case. This is why when designing a machine, it's good to have as much accel as possible and that all axes can run at the same accel rate without issue. Without issue being the most important part. Knowing accel you can calculate bend radius at any speed. Knowing that radius you can then calculate the max distance from corner it would be at that speed for each angle. Naturally it does not take any machine design flaws (flex, backlash, etc.) into account so again, best to eliminate those in machine design.

Most machine to a tolerance. +/- .010 for example. They want to run the path as fast as possible while staying within tolerance. That was the whole idea of the wizard. Increasing the tolerance will decrease the run time and make it smoother but keep the path within the given tolerance. Unless something (like backlash or flex) lets it exceed the tolerance.

Thanks!

107

Mach4 General Discussion / Re: X move starts before Z move finishs

« on: July 24, 2019, 07:49:25 AM »

 

The CV distance tolerance wizard is one of the funnest things I have had a chance to do.

Glad it worked well for you.

108

Mach4 General Discussion / Re: X move starts before Z move finishs

« on: July 23, 2019, 09:26:05 AM »

Good point Steve and it may be exactly what he needs to do.

If you do not have mcCvDistToleranceV001 in your wizard list you probably need to update.

109

Mach4 General Discussion / Re: X move starts before Z move finishs

« on: July 22, 2019, 10:34:54 PM »

Run the CV distance tolerance wizard and read each screen............ the documentation is built in.

110

Mach4 General Discussion / Re: Digitizing in Mach 4

« on: July 19, 2019, 10:14:53 AM »

It is definitely doable in Mach4 but there is no plugin or script included that will. You will have to do some scripting. I did post some script on this forum sometime ago that does most of what you want though. It should get you off to a real good start. See what you can do and myself and others will try to help.

https://www.machsupport.com/forum/index.php?topic=35896.msg246530;topicseen#msg246530