Messages

611

Video P*r*o*b*i*n*g / Re: MachCloud point viewer program

« on: October 23, 2013, 09:25:10 AM »

Seb:

  All data should be in cartesion coordinates. The ball method basically rolls a ball bearing of whatever size you dictate across the points. Whenever the ball rests
on 3 points, that creates a triangle for the output. If the angle between any points are higher than the max angle, it is ignored. This helps for some situations
when the ball doesnt quite sit properly on those points.

 Im not sure how many app's are out that do this, it was a theory expressed in a papaer I read, so I write a routine to do it... Seems to work well
under many situations, but I havent used it in years so I cant advise much on how best to use it anymore.

Art

612

Video P*r*o*b*i*n*g / Re: MachCloud point viewer program

« on: October 23, 2013, 01:22:54 AM »

Hard to say, its been years since I ran machcloud... but the dia of the ball is settable, so Id try experimenting to see if you can find
a good setting. MachCloud was experimental when I wrote it, so there no for sure way to run it..

Art

613

Video P*r*o*b*i*n*g / Re: MachCloud point viewer program

« on: October 22, 2013, 08:18:51 AM »

Seb:

  Yes, it deals with a 3d cloud, doesnt matter what dimension..

Art

614

General Mach Discussion / Re: G76 threading issues - any thougts?

« on: April 04, 2013, 04:29:34 PM »

Rich:

  In theory it can work in a limitded instance, but the second one is redundant, once triggered the motion will simply continue
unabated I think. It will have no real effect, but has dangers if one were to string a bunch together as the triggering wont be as one
would expect. I never understood why the G32 advance was written that way, but then as I said, its been too long, like trying to
second judge a project long put away.

Art

615

General Mach Discussion / Re: G76 threading issues - any thougts?

« on: April 04, 2013, 01:55:39 PM »

Hard for me to believe its the index pulse, your time of int seems good on the rotation sensing.. BUT, the program has changed a lot since I was in there, Im still using .028 as my version, but it has changes Ive made for myself over time so Im not great anymore at figuring out whats going
on in generalized sense.. My emco hasnt done threading since I wrote the routines..

Art

616

General Mach Discussion / Re: G76 threading issues - any thougts?

« on: April 04, 2013, 10:55:59 AM »

I just read the entire thread to see if it helps..

>> I can hear the X attempt to get close to the thread OD then there are a couple of missing step sounds 

  THAT sounds like the error. Mach will not know if steps are lost, so the failure may be lost steps beacuse the
X motor stalled. Do you have a way to tell if the emco has lost a few steps. Zero to a known and repeatable spot,
after a filure use a G1 X..Z.. to go back to that spot. Is it off position...if so, thats the problem, we need to figure out why its
lsoing spot. That double G32 HAS to go, two G32's in a row will not reset the WaitForTrigger, there always has to be a G0 or a G1 after a G32, preferable a G0.. ( which cancels threading mode so another can be mode switch can occur. ). SO ensure nowehre is there
two G32's in a row.. that will always fail in one way or another.

Art
 

617

General Mach Discussion / Re: G76 threading issues - any thougts?

« on: April 04, 2013, 10:49:41 AM »

Simon:
 
    I cant tell exactly whats wrong. The numbers dont look particularly bad. They show a slowdown of about 20% during the cut.
   Its been awhile since Ive odne any threading work, couple years anyway, so Im not fully up to snuff of the readings.
   I dont like that the adder value is always zero, but that may be normal in that driver. The adder controls the speed. The error
   controls the adder. Mach3 purposely increases planned speed by 20% so the thread shoudl immediately drop that speed by 20% when the thread starts, thus
   giving the right speed, and allowing it to speed up by at most 20% if the spindle speed should increase. ( yours doesnt increase so thats not an issue).
   
    The reading of pitch of 40 is simply the G1 or G0 at th end of the thread and as a result shows no threading run vaues after the report. ( Thats normal
    in other words..).
   
Thu - 11:07:22 ---Spindle Lock: 5220 , Total Ints: 0, Total Spindle Ints: 0, Error: 811, Adder: 0 LastRot: 6489
Thu - 11:07:22 ---Spindle Lock: 5220 , Total Ints: 5765, Total Spindle Ints: 5220, Error: 545, Adder: 0 LastRot: 6587
Thu - 11:07:22 ---Spindle Lock: 5220 , Total Ints: 11711, Total Spindle Ints: 10440, Error: 1271, Adder: 0 LastRot: 6481
Thu - 11:07:22 ---Spindle Lock: 5220 , Total Ints: 16977, Total Spindle Ints: 15660, Error: 1317, Adder: 0 LastRot: 6549
Thu - 11:07:22 ---Spindle Lock: 5220 , Total Ints: 22206, Total Spindle Ints: 20880, Error: 1326, Adder: 0 LastRot: 6544

  The spindle Lock is the spindle speed in interrupts just before the threading begins. The error is the difference it saw
  in the last rotation.  The resport of a large pitch you can ignore, its just a false report based on the G1 motions post
  threading. The Adder is the only value I dont like, but I cant recall if thats normal or not.
 
 Be nice to know if anyone using threading  gets an adder value in that test, I simply cant recall. The readings other than
   that though, show no failure at all. They seem to track, the errors are what Id expect from a proper thread and they dont
   seem to grow meaning the variations appear to be properly dealt with.
   
    Im assuming you have "Use Actual Spindle Speed" checked in the config? 
   
    Art
   

618

General Mach Discussion / Re: G76 threading issues - any thougts?

« on: April 04, 2013, 01:10:03 AM »

Hi Guys:

 The best way to tell as  I recall, is to select the "Debug" option in the configuration, then try one line of threading. Stop the program and look in the LastErrors.txt fille in the mach3 folder. Post it here if you like, it tells you whats going on during the thread, and why it might fail..

Art

619

Mach3 under Vista / Re: Getting up and running in Vista

« on: August 20, 2012, 10:03:58 PM »

yes, thats the one..set it to 10 and see what happens...just as a test..

What kind of drivers are these, some older drivers needed very long pulse times.. you could test that by checking the
"sherline half-pulse" mode in the config/ports and pins, restart and see if the motors move then. If not, uncheck the "sherline mode".
Sherline mode makes the pulse width very very long, bu is limited to about 12.5Khz output on 25Khz mode..

Art

620

Mach3 under Vista / Re: Getting up and running in Vista

« on: August 20, 2012, 09:12:37 PM »

Ahh, then your port is working fine. No sense screwing in that area anymore. On the motor tuning tab, change the Step Width to 10 to see if it has any effect..try jogging and see if it does anything. If not, set it back to 0 because it doesnt appear to be a width issue. Your breakout baord may require an enable signal on a particular pin or something to turn on motor motion,
its likely that some signal is stopping you...like a required charge pump signal or enable. Your breakout baord specs shoudl tell you if anything else is required, but it sounds to me like
its all working fine, just a matter of enabling the breakout baord. The motor moved from noise when you disconnected the cable, so its likely that the port is pulling an enable pin low, where you
need it to be high..

 

Art