Hello Guest it is April 25, 2024, 03:52:04 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 - stirling

881
Mach Screens / Re: Half the DRO
« on: February 13, 2013, 09:45:11 AM »
OK I think maybe this is the common problem of folks asking how to implement THEIR solution rather than asking for A solution to a problem. No worries - happens all the time. ;D

Put the following code into the button of your choice...
Code: [Select]
X = getOEMDRO(800)
If X <> 0 Then 'x has changed
  Code "G0 X" & X/2
Else
  Y = getOEMDRO(801)
  If Y <> 0 Then 'y has changed
    Code "G0 Y" & Y/2
  End If
End If

and then do this...

1) touch off your first side and zero both X and Y via the buttons next to the axis DROs
2) touch off your other side AND THEN RAISE Z to a SAFE HEIGHT
3) hit the button. The axis will move to the mid-point and show its coordinate of course in the DRO
4) Zero the DRO

Of course this could be automated even more and various safeguards put in place but it's a starter.

My usual terms & conditions - you use this code at your own risk - if it breaks anything including your heart you get to keep the pieces.

If you want to try it BEFORE you stick it in a button just run it from the CB editor.

Ian

882
Mach Screens / Re: Half the DRO
« on: February 13, 2013, 09:25:04 AM »
Kenneth - with respect if I understand your requirements correctly I'd suggest you're going about this in a rather tortured way.

Why not...

touch off one side - zero that DRO
touch off the other side and then have simple button code to...

raise to safe Z
move to the mid point
zero the axis

job done - one button - no DROs - simples.

Ian

883
General Mach Discussion / Re: edge finding/2.5D probing
« on: February 13, 2013, 03:58:08 AM »
This software has been withdrawn and is no longer supported.

However this error probably means it's failing to store parameters in the registry, probably the user you installed under doesn't have the required access rights.

884
General Mach Discussion / Re: Trigger macros broken?
« on: February 12, 2013, 05:10:34 PM »
Thank you Gentlemen

..........and the piss-taking-award goes. to........

http://www.youtube.com/watch?v=KHJbSvidohg

 ;D ;D ;D ;D ;D ;D
Ian

885
General Mach Discussion / Re: Trigger macros broken?
« on: February 10, 2013, 03:02:06 PM »
;D  You made me Google Sisyphus.
;D Rock 'n' roll  ;D

Ian

886
VB and the development of wizards / Re: Mach3 script editor bug?
« on: February 10, 2013, 01:13:14 PM »
OK - I think I see what you're trying to do but it's all getting a little bit messy. If I understand your requirement you want to rough down in rough steps until you're at some level or at a point where another rough step would be a step too far. From there you want to finish down in finer steps until you're done, but again mnaking sure you don't go beyond the finish level.

Here's the pseudo code - untested of course so the usual applies - if it breaks your machine or your heart you get to keep the pieces. :)

currentX is where you're at at any time
roughStepX is your roughing stepover
fineLevelX is where you want to fine cut from
fineStepX is your fine stepover
finishLevelX is where you want the whole shabang to stop

while ((currentX - roughStepX) > fineLevelX)
  currentX = currentX - roughStepX
  G1 currentX
wend

while ((currentX - fineStepX) > finishLevelX)
  currentX = currentX - fineStepX
  G1 currentX
wend

if (currentX > finishLevelX) then
  G1 finishLevelX
end if

Note that all tests are exclusively > so a) the = and < are handled implicitly i.e. by drop throu - so no possibility of an infinite loop (well unless you set the stepovers to zero! in which case you deserve all you get ;D) and b) we don't give a monkey's about decimal places and such. Also all numbers can be set at the top and therefore do not appear as "magic" numbers in the code proper.


887
General Mach Discussion / Re: Trigger macros broken?
« on: February 10, 2013, 12:46:40 PM »
OK Brett - thanks. I'm trying to get some progress on making my probing (and other things) boiler-plate and I'm starting to think Sisyphus had it easy. Mach's breaking/fixing/breaking obsession is making me think I might just have to wait for 4. :-\

Ian

888
General Mach Discussion / Re: Trigger macros broken?
« on: February 10, 2013, 11:47:04 AM »
Sorry guys, you've lost me. What's the relevancy of this to my question? Brett - I thought by your first reply you knew of something that 3.043.022 had something to do with it - I was trying to find out what  :)

Ian

889
General Mach Discussion / Re: Trigger macros broken?
« on: February 10, 2013, 03:53:58 AM »
Brett,

I checked the change log and there's no entry for 3.043.022 so I'm none the wiser!

It jumps from 3.042.039 to 3.043.036 and the only possibly significant note I see is...

Quote
//Many updates added and debugged to get to this stage...

What was the deal with 3.043.022?

Ian


890
General Mach Discussion / Trigger macros broken?
« on: February 09, 2013, 11:54:48 AM »
Anyone know when trigger macros stopped working properly? The associated macro now doesn't run until all movement has stopped rather than when the trigger atually fires. OEM triggers appear to work as normal. (currently using R3.043.066).

Ian