jepler: src/emc/rs274ngc/tool_parse.cc and .hh don't have a license comment. they're gpl v2, right?
I think that code was directly split out of an existing file - check git history to be sure - if so they have the same license as the original file
of course! I knew they did... I just didn't think about it
for some reason, the comment that wend along with loadToolTable() got lost when the function was put in a separate file
MarkPictor: I think jepler did the split - he will see this and put the license comments in, thanks for pointing it out
It doesn't mention the license, but someone who can commit might want to put it in the new file
the missing comment can be found in http://git.linuxcnc.org/gitweb?p=emc2.git;a=blobdiff;f=src/emc/iotask/ioControl.cc;h=d06c91ce54db36f9a5a6b2149ff83cf39da710ab;hp=c9730c95ff61a82ab07eb5e64f518fcd6c876b43;hb=9e03062a872aaf7f50019b8ea37a5efb6ba71408;hpb=81d7f2a54260347e0a251d7040242308802e0ac5
the new tool table format is pretty stable, isn't it?
I'm thinking of borrowing that code
Re the link to the Honeywell Kitchen Computer (1969) posted earlier by jepler http://en.wikipedia.org/wiki/Honeywell_316#Kitchen_Computer
, don't miss this from the footnotes: http://valerieaurora.org/kitchen.html
EMC: 03jepler 07v2.4_branch * r2c7d59c009f1 10/src/emc/rs274ngc/ (tool_parse.cc tool_parse.h): add missing copyright notices
cool, matt shaver found a copy of "NCMS"
the ngc interpreter was based partly on it
Ah, OK, thanks
it's actually a hideous mess - interesting to see. :-)
KimK: That's ok, I had no clue what it meant either, doubt it stood for what google said =)
comments all over the interpreter talk about [NCMS], but I had never seen a copy
Maybe a copy should be put on the wiki? There should be a place to archive obsolete stuff.
I wouldn't mind looking at it briefly. (Probably very briefly, lol.)
[20:29:00] <cradek> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl/emcinfo.pl?RecentChanges
hm, there's an option to "square off" the corners in cutter comp. page number 109 TTRC Generated Blocks (G39 vs G39.1)
G33 uses F (or E?) to specify thread pitch, and includes Q to specify starting angle and K to specify change in thread pitch per revolution
(page number 120)
g28 actually does homing in ncms
er, G34 takes K; the table with G33 wrongly includes K if you believe the prose
the whole document is a frightful mess
we should send a copy to the fellow who was so disturbed by the state of emc documentation yesterday
and what document would be complete without a table of 7-bit ascii. I should add one to our documentation..
"The previous section to the cutter compensation and TTRC."
^ circled and a "?" written nearby
there's something about random toolchangers on page 75
G10.1 L20 being used to program tool table entries
tool length offset (plus), tool length offset (minus) (page 72)
heh, in their polar mode, X is radius and Y is angle
lots more parameters with defined meanings, page 54ff
I just joined, are you talking about what I think you are?
For example, programming #3006=.1 (Install Tool Number 6); will cause program execution to stop at the beginning of this block and display the message telling the operator to read the comment in the block.
No, clearly not.
SO I won't campaign for #5501 (or something unused) to report the current value of X (for example)
andypugh: that's page 57
Ah, yes I will. 5001 - 5006 could be jolly handy at times.
#5001 to 5006 Coordates of End Point, #5021 to 5026 Coordinates of Commanded Position
Would save frigging it with G92 then G92.2
august 1994, it's not even _that_ old
huh, G38 is hole probing cycle and G38.1 is parallel probing cycle ("paramacro"?)
exponential acceleration? (page 38)
#3002 System Clock - The maximum value for this parameter is 1 year. ... It is incremented by 000005556 every 20 ms.
For induction motors maybe?
ah, what we call probing is G31-G31.4 "External Skip" and/or G37-G37.4 "Tool Gauging"
there are 4 different probe inputs, G31 and G31.1 selecting the first, G31.2 selecting the second, and so on
and probe tip radius compensation is included
I think 5021... and 5041... are offset current position and unoffset current position
I don't see how that works -- even if your motion is strictly in Z that doesn't mean the point of contact between work and probe tip is exactly in the line of the spindle
lol @ 000005556 every 20 ms.
Hmm, with a fresh LiveCD install the SIM-5AXIS won't go into world mode, or run an MDI command (because of that)
don't you have to home first?
Ah, OK. I restarted it and it works. It seems to get stuck if you try to go to MDI mode before homing it.
I think this might be related to Viesturs problem with dropping into joint mode and racking his gantry.
alex_jon1 is now known as alex_joni
should submit a patch via git for the genserkins hacks i made?
it seems to work with linear joints now
Do you have commit access to the repository?
You probably need to make a git diff, then send it to the dev mailing list.
does anyone want to test and submit it for me?
email the diff to the mailing list, then anyone who wants to can test it.
i dunno what access i have probably non, i dont know anything about git
I would anticipate "none" too. The stuff I have done has got in through the mailing list.
want to test it andypugh?
I don't think I know enough about the current Genserkins to usefully test it.
[22:26:36] <moopy> http://soundproofingforum.co.uk/halitosis/
it should all be autoconfigured
i left a couple of demo files in the tar
Looks good, but I am rather busy at the moment (project overload)
holy crap, now they're talking about evacuating the west side of boulder city... 50 mph winds forecast for this evening
you're east, right?
i'm 3 blocks east of the area that's being told to prepare to evacuate
i strategically bought a house downwind from a really expensive neighborhood, so my house will be well protected ;-)
50mph is nothing
it is if there's a dry forest on fire upwind!
not if you have an asbestos house
meh, typos ftw
alex_joni: I speak typo