Hello Guest it is April 24, 2024, 10:17:53 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 - stirling

481
General Mach Discussion / Re: Odd glitch in movement?
« on: April 25, 2014, 06:20:04 AM »
Never used 3.043.066 but I believe Hood advises not to use it.

482
General Mach Discussion / Re: Controlling THC?
« on: April 25, 2014, 06:18:11 AM »
M10 & M11 are in-built reserved macros - you can't re-program them. They are designed for laser users and turn on and off designated outputs upon axis movement. It doesn't matter what you put in the TEXT files M10.m1s or M11.m1s - it won't be run.

User macros start at 100

483
General Mach Discussion / Re: Odd glitch in movement?
« on: April 24, 2014, 12:07:08 PM »
I've got a feeling I've seen this before - but my memory's shot. I seem to remember it was only happening on straight line to clockwise arcs - which looks like what you're seeing. I think this was YEARS ago though. What version are you using?

484
General Mach Discussion / Re: stepper motor direction/s
« on: April 24, 2014, 11:33:55 AM »
 :)

Thanks for getting back

485
CV distance is in your machine units. It just says - don't blend until you're at least this close to the join. Sounds great - nice tight (small radius) corners. Problem is - you don't get anything for nothing. The smaller you make this the more the axis HAS to slow down and of course the name of the CV game was NOT to have to slow down.

TBH - my view is really that if you have to start tuning CV you're already in trouble.

Velocity/Accel - always a trade off. Get as much of both as you can. Great velocity with crap accel is no good. Neither is ace accel and crap velocity. If you can't get a good balance that does the job - it's hand in pocket time again.

Ian

486
General Mach Discussion / Re: "run from here" problem
« on: April 24, 2014, 08:23:20 AM »
The suspense is killing me  ;D

 ;D

hopefully you're not the only one  >:D

Ian

487
This is what I know...

I can auto-zero onto my spring loaded plate, then enter G0Z1 on the MDI screen. I then check the bit height with a 1-2-3 block as a gauge and it fits under the bit perfectly time after time.

I understand. If it's doing what you want then to you that's all that matters. From my perspective I like to know WHY things are as they are. Anyway - happy probing.

@michael - no worries.

488
@Michael (mbele) - I'll give you 10 out of 10 for creativity. Sadly your scheme is based on an incorrect assumption. G31 is polled at kernel speed i.e. after each and every single step whereas Mach continues to put out steps for 1/10th second after E-Stop goes active. Surprising perhaps - but true here with the PP.

G31 is step accurate. You can't get more accurate than that.

The fine points on my v carving bits were taking a beating on the fixed plate. Even a slight overshoot can chip the tips

If G31 is used below the speed which requires a deceleration phase then it stops within ONE step - on your machine that's 0.0006 inches. I doubt that movement even gets transmitted to the spring - never mind actually deflects it.

Now they come down on what amounts to a cushion and I don't seem to have to sacrifice accuracy.

How can you NOT be losing accuracy if the plate moves?

I can see only ONE reason why the plate moves if you're probing slow enough and that's because you're not getting good electrical contact. Switch cleaner might be worth a consideration.

Now, stirling got me worried about accuracy/unpredictability of trip point:
Quote
2) Perhaps worse though is that because its attempt to store the stop point may well fail, the retraction will be pretty random/un-predictable and in worst case could seriously crunch your tool tip/plate.
so I'll make rapid retract conditional in respect to current tool position.

You're mis-quoting my quote. You said trip point - I said stop point.

I was pointing out that in the first macro posted, the author was storing the STOP point in the DRO - NOT the TRIP point. More importantly though he then went on to command movement immediately afterwards that was based on that DRO. This is a no-no unless you want tears before bed-time.

489
General Mach Discussion / Re: "run from here" problem
« on: April 24, 2014, 04:50:33 AM »
(;-) I worked on that one for well over a year. Without success, well it could be done with a LOT of block deletes statements but that was a PAIN in itself.

But I will review it ONE more time

(;-) TP

No block deletes needed. ;)

490
Modbus / Re: How to Address Modbus Outputs if you have more than 20
« on: April 23, 2014, 11:51:44 AM »
guess not then...