RE: [CAD_CAM_EDM_DRO] Re: Keyboard Typematic rate

Alan:

The Pascal Code looks like this:

Type

ModalGroup = Set Of 0..255;

Const

Group0 {G-Code} : ModalGroup = [4, 10, 28, 30, 53, 92];
Group1 : ModalGroup = [ elements ]; ....

One typed Const, which is equivalent to a C Static variable, is defined for
each group. Then I parse the block and assign the number following the "G"
code to variable GCode. Next, the GCode is copied into a variable -

if GCode in Group0
then GCode0 := GCode;

This results in each of the several groups (both for G and M codes) are
filled with their appropriate codes or with a code that indicates no code.

Since we're getting into the internals of TurboCNC, perhaps we ought to move
this over to the TurboCNC list and save the bandwidth here.

-- Carol & Jerry Jankura
Strongsville, Ohio
So many toys, so little time....


|-----Original Message-----
|From: Alan Marconett KM6VV [mailto:KM6VV@...]
|Sent: Thursday, February 21, 2002 4:14 PM
|To: CAD_CAM_EDM_DRO@yahoogroups.com
|Subject: [CAD_CAM_EDM_DRO] Re: Keyboard Typematic rate
|
|
|Hi Jerry,
|
|"define a set of integers (0..255)" sounds like C's enumeration. I
|don't recognize "if Gcode in Group1 then...", I simply have a set of
|variables for the groups. The enumeration would prevent constants
|(#define G01) from being assigned to a group's enumerated variable
|(compile time), but to my knowledge, does not stop me from assigning a
|variable to the group's variable. Nice thing to have. I suppose one
|could write a "group assignment function" that would complain if the
|parm passed was not one of the "valid" members by using a case
|statement, but it wouldn't be automatic.
|
|By the way, I believe that G80, G81, G82, etc. are ALSO in group1, along
|with G0, G1, G2, etc.
|
|
|Carol & Jerry Jankura wrote:
|>
|> Hi, Alan:
|>
|> |I think I posted some Gcode "grouping" info in response to someone's
|> |questions a little while ago on this list, or CCED. Might help,
|> |although if you're reading NIST, you should have the info. It did take
|> |me a few tries to get the groups right, 'tho.
|>
|> With Pascal, you simply define a set of integers (0..255) and
|then declare a
|> constant for each of the groups. You set this constant to the
|G-Codes that
|> reside in the group. Then it's a simple "if" statement (if GCode
|in Group1
|> then....) to determine the membership. Where I think that I'll
|have a little
|> problem is to implement the rule that says that you can't have
|an element of
|> one group if you have a couple of other G-Codes of another group.
|>
|> I've also got to think about where I'll stick the extra G7x codes that
|> Dave's defined. I'll probably put them in the same group as his
|G8x codes,
|> since they seem to do similar actions.
|>
|> |And as to old DOS; well, I still use them at work for our embedded
|> |product. And the website that was just posted, "Geezer"! Yeah, I guess
|> |that says it!
|>
|> I liked Geezer as well. It describes us retired flatulants quite well! :)
|>
|> -- Carol & Jerry Jankura
|> Strongsville, Ohio
|> So many toys, so little time....
|
|
|Addresses:
|FAQ: http://www.ktmarketing.com/faq.html
|FILES: http://groups.yahoo.com/group/CAD_CAM_EDM_DRO/files/
|
|Post messages: CAD_CAM_EDM_DRO@yahoogroups.com
|Subscribe: CAD_CAM_EDM_DRO-subscribe@yahoogroups.com
|Unsubscribe: CAD_CAM_EDM_DRO-unsubscribe@yahoogroups.com
|List owner: CAD_CAM_EDM_DRO-owner@yahoogroups.com, wanliker@...
|Moderator: jmelson@... timg@... [Moderator]
|URL to this page: http://groups.yahoo.com/group/CAD_CAM_EDM_DRO
|bill,
|List Manager
|
|
|
|Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
|
|
|