The value passed to Q seems to "cascade" down to R, and then persists if R is not specified in successive calls.  Feature? Known issue? Already fixed?

I was playing around a little more with this today, and the cascading effect I thought I had seen yesterday is gone.  The more I think about it, the more I think that I made it up by happenstance.  Plus I was really tired.  But the persistence is still there.

Whereas Param1() and Param2() always return -1 if P and Q, respectively, are left out of the macro call,  Param3() will return whatever value was last used with R.  It's even persistant between different macros.

I can confirm that. It seems to be a bug.

Test

'm1009 test macro
Message "" &param1 &param2 &param3
end

create macro then add params to the macro call. The values will show up in the mach message line. Then call the macro without params and it displays
-1,-1, what ever number that was in R.

I'd suspect that this is tied up with cypress enable's appaling stack handling which is and allways has been broken.

Is that also why we can't nest macro calls?  It sure is tough to develop a general purpose macro library without nesting...

Is that also why we can't nest macro calls?

What happens?

HIYA Stirling, question ,there is a fellow doing probing of an engine intake ports. Can your crawler routine probe the inside of a 3d object such as a port?

HIYA Stirling, question ,there is a fellow doing probing of an engine intake ports. Can your crawler routine probe the inside of a 3d object such as a port?

Hi - It's basically a bed o' nails with the added benefit of only probing inside a prescribed boundary. As you know a standard or dumb bed o nails only probes inside a defined rectangle which can mean it spends an inordinate amount of time probing useless space. All I can sugest is your fellow gives it a whirl. Don't know if you've seen it but there's an Italian company in this thread www.machsupport.com/forum/index.php/topic,4352.msg97649.html#msg97649 that has a couple of nice vids on their site and youtube of the routines in action.

Let me know how you get on.

Cheers

Ian

HUM there is really nothing to probe in the Z axis just a big hole. The area to probe would be in the X/Y directions and step down in z as it goes deeper into the port.

Your crawler routine works great but I don't think it will work in this application unless it could be modified to crawl the perimeter from the inside out then step down.

(;-) There IS a market for a PORT probing routine to do this IF you are interested.

I have seen your routine do the combustion chambers of the head, that IS a perimeter and bed of nails type of probing solution

Thansk

Quote from: flick on April 27, 2010, 12:31:25 PM

Is that also why we can't nest macro calls?

What happens?

Hrm, can't find it anymore, thought I'd read it wasn't allowed. Brain fart?