Hello Guest it is March 28, 2024, 02:32:10 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 - rrc1962

131
General Mach Discussion / Re: Version .066 Arc Issue
« on: October 26, 2013, 01:55:29 PM »
M1101 just turns on the THC and there is not motion controller.  Just PP to a PMDX bob.  It only happens when there is more than one compete circle in a row.  It will cut arcs all day long in either direction and will cut circles in either direction as long as the circles are not back to back.  If you cut a 1" circle followed by another 1" circle it will fail on one or both of the circles.  If you cut a 1" circle followed by something that is not a complete circle then another 1" circle, it all works fine.

If I make the G02/03 code modal it all works fine, which may be why the issue doesn't come up all that often.  Most, if not all, CAM programs post modal code.

132
General Mach Discussion / Re: Version .066 Arc Issue
« on: October 25, 2013, 10:45:11 PM »
062 does the same thing.  I know 022 works, so I started there and found that 024 works and everything later does not.  I can change the post to produce modal arc codes, but shouldn't the Mach be able to process both modal and non-modal code? 

133
General Mach Discussion / Re: Version .066 Arc Issue
« on: October 25, 2013, 08:49:17 PM »
The problem appears to be only with non-modal code.  Modal commands seem to be fine.  Is there an archive where I can download .062? 

134
General Mach Discussion / Version .066 Arc Issue
« on: October 25, 2013, 08:25:47 PM »
So I decided to try .066 and everything seemed fine until I tried running G02/03 commands.  Mach completely ignores both sometimes.  It's always either one or the other.  This issue does not occur in Version .022.

Has anyone else seen this?  In the code below, the G02 is ignored on V.066 and runs fine on V.022.  Did .066 bring about a difference in the way Mach handles G02/03.  The code below is non-modal.  If I change.....

G02 X6.06 Y3.03 I-3.03 J0   

to....

G02 I-3.03 J0

It runs.  Why is that and is there a setting in Mach so that it will run non-modal code.

Thanks

G20
G90
G91.1
M1102
M1112
G00 Z0.5
G00 X4.5 Y3.03
(CUT INNER DIAMETER)
G28.1 Z0
G92 Z0.1
G00 Z0.2
M03
G4 P0.2
G00 Z0.14
F80
M1101
G03 X4.5 Y3.03 I-1.47 J0
M05
M1102
G00 Z0.5
M01
G00 X6.06
(CUT OUTER DIAMETER)
G28.1 Z0
G92 Z0.1
G00 Z0.2
M03
G4 P0.2
G00 Z0.14
F80
M1101
G02 X6.06 Y3.03 I-3.03 J0  (This line is completely ignored)
M05
M1102
G00 Z0.5
M01
G00 Z2
G00 X0 Y0
M30

135
Easiest way is to get the specs on the motors and call Gecko.  They will set you up with drives for your motors and tell you what you need for a power supply.  For a BOB, I like PMDX.  The 122 is simple and inexpensive.  That's pretty much all you need....motor drives, power supply, BOB and Mach3.

136

If I leave the THC speed below 28IPM It seems to work . that's probably fine for flat stuff, I'm more worried about cutting thinner materials at high speed...N

The other issue you'll have with a THC using Mach3 inputs is bouncing.  Because there is no acceleration...or deceleration applied, the axis will always overshoot a little when your THC turns off the output.  This causes it to read high...or low, and correct in the opposite direction.  That continues causing a sine wave cycle.  The higher the THC feedrate, the worse it is.  You can minimize the effect by programming a "dead zone" in the THC.  That would basically stop the Z motor before your actual set point.  If it's set right, the axis would stop right n the set point.  The downside to a dead zone is that as increase it, you lose sensitivity.


137
If the THC is stand-alone, then it controls your Z axis, not Mach3.  That being the case, Anti-dive should be designed into the THC.  If it has no anti-dive, it's missing a critical feature.  Without anti-dive, you'll dive into corners and dive during a lead-out. 

138
General Mach Discussion / Re: ARC not OK
« on: May 21, 2013, 07:42:55 PM »
Put an ohm meter on pins 12 and 14 on your TD automation cable.  That will tell you if it's the plasma.  With a good arc, you should see continuity between pins 12 and 14.

139
General Mach Discussion / Re: Hall of shame
« on: May 16, 2013, 08:36:46 PM »
Doesn't really matter where it comes from.  Like most legit resellers, if we encounter a bogus license, we sell the customer a license.  We've encountered two such licenses doing controller retrofits on Chinese machines.  I don't think the customers knew that the licenses were bogus.  They buy these machines from China (EBay) and just assume that the software and licensees are good.  There is no need to make any of it public because eventually they will need help...Especially if they were unfortunate enough to buy Chinese junk.  All we have to do is make it clear that there will be no help until they buy a license.  Most won't let $175 get in the way of getting their machine running.

I think most Chinese machines are coming with bogus licenses.  Anyone looking for help with such a machine should be questioned regarding the license.

140
General Mach Discussion / Re: Hall of shame
« on: May 16, 2013, 01:59:55 PM »
When we purchase licenses, I send Scott an email with the name of the customer.  He then emails the license which displays the customer name in the title bar.  I also keep all customers licenses on file.  I don't know if Scott keeps a record of who the license was sold by.

Did you make an arrangement with Scott or is that a standard practice?


I didn't make any specific arrangements.  it's just the way we've always done it.  We order licenses as we need them, so we know who they are going to.  If there were a price break on bulk orders, I might do that....Or there might be and I just don't know about it. :)