Hello Guest it is December 09, 2023, 04:42:56 AM

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 - mastersniper

Pages: 1
General Mach Discussion / Re: noob looking for guidance
« on: April 10, 2009, 11:37:37 PM »
indeed debugging intermittent issues can be a real pain in the butt. Unless I run into a problem with the debounce up at 2000 is there a particular reason to lower it?

If I understand the option correctly: 2000*40us = 80ms., so if a signal is 79ms long it ignores it but if it's 81ms then it triggers (+- 1ms or something close depending on kernal speed).  if the axis is moving at 60 in/min = .08"  (60/60,000 = .001 inch/ms * 80ms debounce) so I might get up to .1" or so over travel while it is waiting for the debounce timer I guess that could be an issue if I overran limits at my full slew rate. 

So much math so few brain cells working today  ;)

General Mach Discussion / Re: noob looking for guidance
« on: April 10, 2009, 09:38:30 AM »
I believe Hood hit the nail on the head with the noise idea, setting debounce to 2000 and I ran 8+ hours without a stop error yesterday.

General Mach Discussion / Re: noob looking for guidance
« on: April 09, 2009, 03:46:11 AM »
Thanks for those replies, I didn't think about it but noise makes a lot of sense, I will bump up the debounce and see how that works out tomorrow.   I am in a cramped condo so right now my cable routing is not the best with power and data runs intermingled I will also sort out that cabling to eliminate that as a noise problem spot as well.

  I was looking for a PCI parallel port yesterday but the 2 stores I went to didn't have any, planning on going to Fry's tomorrow at lunch time they will almost certainly have some in stock.  the drive and encoder cables are standard Taig cables  that I believe are shielded but will check on that.

   My name is Mark and by profession I am a programmer (Delphi, C, SQL)/DBA but dabble in photography, astronomy,  some electronics and riding my motorcycle.  I recently purchased a Taig DSLS and I am coming to grips with the whole CNC thing primarily as a way to prototype PCBs but also for making some parts for my other hobbies.  So far made a few tooling plates from HDPE and 6061, a hand full of t-nuts from some 1/2" bar 6061 I had and done some PCBs and some engraving little name plates and stuff.   


General Mach Discussion / noob looking for guidance
« on: April 09, 2009, 02:45:28 AM »
Have had my taig DSLS running Mach 3 for a couple weeks now and it usually runs perfectly fine through anything gcode I throw at it.  But sometimes it stops with a 'limit switch' error though it is far from any limits, this might happen 30 seconds into a run or 2 hours into a run.  I believe this is the clasic missed steps error being caught because the encoder/move got out of sync but feel free to correct me if I am misunderstanding.  With maybe 40-45 hours on the clock I have had just 5 of these stops.

Being new I looked around but am still a little confused on the correct interpretation of the driver test and motor tuning options.  I am pretty zelous about keeping the ways cleaned and lightly oiled and it does not seem to be any binding or undue looseness (.0015 x, .0010y backlash).  The stall can happen either in x or y so I lean away from a mechanical issue.  as a test on the last stop I just restarted the spindle and hit cycle start and it picked up and ran through the rest of the gcode (albiet out of alignment) I also reran the gcode on a new block of material and it ran through to the end without a problem.  I have run the driver test and it reports excellent at all speeds 25k up to 100k.  I went through motor tuning and had it set at 80 ipm 5 accel which worked fine but backed it down to 60 ipm 2 accel after the second stall and it still stalls.  This is on a Compaq desktop, athlon 3500+, Xp home, 1.5GB RAM, PCI video.   I am using the built in parallel port, and the BIOS on the compaqs are not really full featured but if there are specific setting I should look for I will dig through there and see what options are available.

Any ideas where to focus my attention to eliminate these random stops would be appreciated, it's getting annoying to hit a stall after 2 hours in a 3 hour run, I suppose once I get better at repeatible zeroing the axis it might not be as bad, right now I usually just chuck the stalled jobs in the recycle bin because getting back withing .005 seems to be the best I can do and doing PCB etching that does not cut it.

Thanks for any insight you more experienced folks can pass down.

Pages: 1