* BigJohnT says good night Gracie
seb_kuzminsky: is there a way to turn off the smart quotes on the compiler output, or else somehow cause it to render correctly in the browser?
I know I've fought with this before but I don't remember the answer
oh hey, if I tell firefox to use unicode encoding, it looks right
(still, I think ascii would be better so we can cut/paste it etc.)
cradek: you mean in the buildbot?
$ gcc fnoodle.c
fnoodle.c:1: error: syntax error before ‘blooze’
$ LANG=C gcc fnoodle.c
fnoodle.c:1: error: syntax error before 'blooze'
maybe you can't see it, but the second variation is dumb quotes
ah, so it's easy
btw, I used 2.3.0~beta1 yesterday for some work - I didn't see any problems (not to anybody's surprise I suppose)
still nice to hear it :)
i'll try to teach the buildbot to run with LANG=C
the most exciting moment was when I thought "maybe it'll drill anyway" and went ahead and used the drill with the bogus-looking point
(thanks, harbor freight)
it was supposed to be a split point, but the split was splitted too far and it didn't really have a point
it did drill for a bit, but then sort of exploded
i like when they grind the angle on the drill face backwards
cradek: I'm glad you don't blame emc2 for that
heh, not sure I've seen that one
jepler: emc2 should have an explosion sensor so it knows to stop
well really that sensor should be in your external estop chain
is that like a caffeinated beverage on monitor sensor?
does that one test for its presence or its absence
I want a N.C. explosion sensor.
even better would be a sensor that would hear the little "tink" of the cutting points coming off, shortly before the explosion
try drilling at 56 IPM into steel with an F bit :/
well, 56 seems a little fast to me
how about 2 instead
it goes about 0.050" deep before it explodes
at least there's no drill left in the work then
somehow my tool table had three drills with over 30 IPM
no bits that I could see were left in the work
that just does not seem right.
tool table and 30 IPM?
MC tool table
it does my g code
* alex_joni only knows MC hammer table
BJT-Work: I was just discussion tool compensation with a friend
and I was wondering if you could add an example for an inside square
or some figure where the "smart" algorithm against gouging is visible
any ideas on what that would look like?
ok I think I know
I'd plunge in the center somewhere and then go out and cut the square
if I was being fancy I'd use arcs to enter and exit the cut tangentially
that would give a better finish
like this? http://heekscnc.blogspot.com/2009/03/profile-section-of-sketch.html
at the entrance and exit
yes also a slanted plunge would be easier on the end mill
programming the square is easy (well, now) but knowing how to do a smart entry is harder
fenn: looks to me like that path will leave dimples on the sides
and why two cuts?
uh, i'll ask
how about a spiral entry to a pocket
certainly not like this: http://4.bp.blogspot.com/_lpgMldGi1O4/Saxn-bSoLfI/AAAAAAAAAIw/bMmj_OLtr6M/s1600-h/adaptivesketch.png
like this? :) http://heekscnc.blogspot.com/2009/03/sketch-as-boundary-for-adaptive.html
alex_joni: haha wtf
time to start drinking :)
"red means OK right?"
BJT-Work: those lines only get more vurved from drinking :P
maybe I don't understand that picture
I'm sure I don't understand it
I think it counts as "art"
it's high speed machining
I'd say too high speed ;)
is it a Japanese dragon head?
slow down and color inside the lines!!
machining by numbers?
yeah the red lines being outside is wrong
"machining by numbers" isn't that funny really :/
is that like "coding by patterns"?
it was supposed to be like "painting by numbers" ;)
guess it should be "machining by feeling"
maybe blind machining using braille
[17:34:22] <cradek> http://www.codinghorror.com/blog/archives/000922.html
cradek: the dimples were on purpose, as an example for tabs so the part doesn't fall out (or similar)
fenn: oh I see
[17:37:54] <BJT-Work> http://imagebin.ca/view/XuXltO.html
* BJT-Work heads out of the shop
you and your fancyschmancy software
i dont get it]
talk to you guys later
this is interesting: http://bikeshed.com/
cradek: I agree with a lot of that blog entry
I do too
(I don't always agree with that guy)
I often say "don't worry about consensus, just do what seems right if you know what it is" and "you don't WANT any more opinions - so don't ask for them" -- both often poorly-received
fwiw the boundary wasn't the border of the pocket, it was just a "machine the surface in this area only" directive
alex_joni: that only makes me wonder who Brett Glass is...
it was linked from the page you pasted
hm, I'm worried about that heekscnc application. "HeeksCNC uses libarea for the "Pocket" operation" "HeeksCNC Code License: New BSD License" http://code.google.com/p/heekscnc/
"[libarea is] Derived from the kbool library written by Klaas Holwerda" "libarea code license: GNU General Public License v3" http://code.google.com/p/libarea/
"The [kbool library] code is written by Klaas Holwerda, it is free to use for non commercial open source projects licensed as GPL." http://boolean.klaasholwerda.nl/bool.html#copyright
so it's a BSD-licensed program that depends on a GPL3 library that is "non commercial GPL"
* jepler 's head explodes
(to be fair to the kbool project, it includes a copy of GPLv3 and each source file I looked at refers the reader to that file for the full license text. it's his wording concerning the availability of the code also under some proprietary license that confuses things)
i chalk it up to language barrier
what's wrong with BSD code depending (for some functions) on a GPL library?
EMC: 03alex_joni 07TRUNK * 10emc2/configs/cooltool/ (17 files): initial version
EMC: 03alex_joni 07TRUNK * 10emc2/configs/cooltool/README: add README. will need to add more info later
EMC: 03alex_joni 07TRUNK * 10emc2/src/Makefile: install emc.nml and core_stepper.hal to cooltool sample configs dir
EMC: 03alex_joni 07TRUNK * 10emc2/configs/cooltool/.cvsignore: silence
fenn: if I send you a.out compiled from bsd.c and gpl.c, I can't take advantage of the main feature of the BSD license compared to the GPL: to withhold the source bsd.c from you
fenn: because to obey the license of gpl.c, I have to follow one of the various "complete corresponding source code" provisions of the GPL
jepler: what is?
alex_joni: having a cooltool config
cd cooltool && ls *.ini | wc -l
if one wants to develop a C++ frontend for emc2
it will take how many sleepless nights to do a minimalistic GUI
interacting with hal & sending nml messages
that depends on your C++ skills
just a rought approximation
for an intermediate c++ devel
maybe 2-3 weeks for a rough approximation ;)
under a week for an more advanced devel
it is silly to ask someone you don't know how long it will take you to do something
and for a total noob ;)
you should study the problem and then you will know
maybe 2-3 lifetimes :P
look at xemc.cc and shcom.hh
obviously the answers above are pretty useless
I suppose it's fun to see the range of answers
you take all the parts out of xemc that aren't the GUI you want, then add in all the parts that are
or else you start with the APIs defined in shcom.cc plus some amount of setup code that you would glean from xemc.cc or a user of shcom and add to it everything that makes your GUI
I hav totaly forgot about xemc
have only studied tkemc
code and though that I would have to mix tk with c++
with tkemc you need to look at the tk part and emcsh for the connection to emc2
(somehow like axis with tk)
axis only uses tk because I chose it. there's nobody with a gun forcing you to use tcl/tk
there's some old sample code written with Qt
I'm not sure where it is
It would be very handy to see it
especially that I will 90% use Qt
does anybody else knows?
I think it's on the linuxcnc.org site somewhere, but I'm not sure where
it's far from complete. I think we managed to get it to show some numbers in a DRO component, via NML
I don't know how much more was ever done
I think there is a newer Qt-lib that allows connecting to emc2
but I'm not sure it has been published yet
yeah, part of that
It's a little more appealing now that Qt45 is also LGPL
stupid laptop keyboards
QTEMC_PLUGIN = /usr/share/eztrol/lib/libqtemc-2.3.cvs-head.so
QTEMCHAL_PLUGIN = /usr/share/eztrol/lib/libqtemchal-2.3.cvs-head.so
and who's developping eztrol?
(don't want to reinvinte the weel)
(sorry I'm french don't know if it's the approriate
word reinvinte maybe rediviseis better)
"reinvent the wheel"
as long as it's a wheel of brie or cheddar, I'm happy
(I have a problem with the "e" even redivise is wrong :p)
blame it on the keyboard
I usully do :)
stupid laptop keyboards
stupid laptop keyboards
* fenn wonders why the topic keeps coming back to cnc machined cheese
this C++ program uses shcom.cc to send an nml message (estop) and look at nml status (print position: http://emergent.unpy.net/files/sandbox/sp.tar.gz
if you want an automatic cheese cutter, that's your deal
compile it, then while emc is running, invoke it: "/path/to/sp axis.ini"
there is very little boilerplate required, as you can see
you can quickly get to the business of writing Qt code
but I'm currently still working on my Qt app for converting
DXF to g-code specifically for plasma cutters
will leave the Qt Gui for later
have you looked at dxf-to-gcode?
(possibly without the dashes)
yes but it python
oh. well in that case ...
I mean for windows users it will be less complicated to get a Qt
app to work under Ms win than a python one
for windows users why not wxwidgets?
because Qt is now LGPL also, duh! :)
but, er.. huh.
and in addition I'm doing this as part of my
end of studies project
an even better reason to keep the code secret
(dunno if my literal french to english tranlation is good)
those professors can be so nosy
Will close source everything than and switch to Visual studio :p
no seriously I consier that my little work will help the community
to whom I'm greatfull
and of course satisfy by the way those nosy profs
there is also http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?GCncCam
have took a look at it
but I'll use ribbonSoft libDxf
it had proven itself for a while now
as Qcad uses it flawlesly
good night all :)
see ya Alex
invite|MkS: bon courage!