re:digitisor movie was Re: Digitizers, Renishaw

Hi Ballendo,

Sorry if I misquoted you. I meant that the MaxNC "controller" programs
don't save data. YES, I'm sure the digitizing probe software does!

> Ballendo wrote:
>Alan,
>Please look at some commercial controls (I suggest a current Fanuc
>style and HAAS. As I have previously said one is a longtime standard,
>the other is selling LOTS of machines) and implement variables as has
>ALREADY been done! If you then wish to "add" the functionality
>of 'named' vars, go to it! But we DON'T need another
>gcode 'flavor',IMO! YES, I do know how us programmer types are. :-)
>You already have a parser set up to look for some char(or two),
>followed by whitespace(maybe)and a numerical parm. This means no
>change to the parser structure is necessary if you implement numbered
>vars, as in your NIST eaxample above. When you go to named vars, a
>lot changes... And the BASIC functions of the parser MAY be
>compromised.

The last thing I want is to create another Gcode Flavor! (Baskin
Robbins revisited). V or # is OK. It's just that they remind me of the
earliest microprocessor BASICS, VERY limited. The subroutines vs f(x),
line numbers, limited labels, etc. All very workable, but why not a
'G++' ? Well, I'm mostly kidding. And I don't see my self as
revolutionizing (or even changing) the present Gcode.

Do most of the Gcode implementations do expression evaluation? I saw
Vector (CAD/CAM, not controller) do expression evaluation for the
numeric entry fields, and I really like being able to enter ".375/2", if
I want a radius instead of a .375 dia. or add an offset to a dimension,
instead of having to calculate it first. NIST appears to. Well I guess
I answered my own question, 9 BINARY operations, no LOGICAL operations?
And I thought "UNARY" operations were just '-', not a trig function
divided by another expression. I probably just need to read it a few
more times. I'm sure they got it CORRECT!

Alan KM6VV ATAN[2]/[1/3]


ballendo@... wrote:

>
> Alan M wrote:
> > but I think as Ballendo said, it just stops there, no data
> >collection.
>
> The maxNC digitising probe software DOES data collection.
>
> G31 is 'standard' Gcode for 'go until input bit flips'. G38 is for
> specialised 'feature' probing (usually a tool or hole diameter).
> The difference is the 'smarts' of the routine. G31 is 'dumb'. G38
> is 'smart'(multiple probings, and data collection, differing
> approaches to the probed point, etc., all in the one G38'routine')
>
> >I'd love to watch a digitizer program run!
>
> I'm pretty sure I remember seeing a 'video' of a digitiser at work at
> the super-tech site. Supercam, Dennis Bohlke, etc. If not, then it
> was on a link from that site... Further, I think it was minirobo
> related.
>
> Hope this helps.
>
> Ballendo