hello ... i wonder about the "dapper" problems... is the problem in the install or the running of EMC?
it's in extensive testing before releasing the stuff ;9
Hehe .. .yeah .. testing always takes time...
and it presumes a lot of different machines & setup
does it appear to be stable so far?
but I think the dapper stuff is pretty much ok to be used
Lerneaen_Hydra: heard of no problems
I could test it if you show me where to get the stuff
(I'm going to need to update to the newest head soon anyway, to get jogwheels)
Lerneaen_Hydra: just like for breezy, just substitute the name breezy with dapper in the install script
oh, so it's in the apt-get script cradek made?
but that script has breezy all over it
you just need to edit it, and add dapper
I'll test that today
but running a "simulated" EMC isnt a problem in other words? i dont got a machine right now ... soo ...
bullzebub: the problem with emc2 right now is that it lacks a non-RT simulator
there is a simulating mode, but it also needs RT stuff
Lerneaen_Hydra: drop me a line in here with your results
alex_joni: sure thing
even if I'm not around
* alex_joni heads for work
alex_joni: how would I install only emc2 from head and not the stable branch, yet still get rt kernel?
ok ... ill just stick to breezy then
cradek's script and then apt-get remove emc-axis?
just run cradeks script, that will get you RT kernel, rtai, emc & axis
if you want head, you'll need to get the sources from CVS in some dir, and configure --enable-run-in-place
after that you'll have 2 emc's on your machine
oh, so I'll have two versions at once? that doesn't cause any issues?
not if the CVS one is configured to run in place (in it's dir)
you can have unlimited versions like that :D
I have about 5 or 6
right, I'll do that and post the results here
anything in particular I should test?
how easy it is, and if you run into any problems
please make notes if so..
exact error messages ;-)
Lerneaen_Hydra_ is now known as Lerneaen_Hydra
Lerneaen_Hydra: yesterday I finished g43 (position offset from the tool table) for lathes
cradek: when you have 20 minutes, can you redo the dapper repository?
sure, working on it now
alex_jon1 is now known as alex_joni
SWP_Away is now known as SWPadnos
I envision using the nice Axis backplot/UI but having the large convincing coordinate display a la. tkemc in a vcp panel.
I just don't understand users
you need multiple monitors for a *really* convincing DRO :)
nah, you need nixies
I could probably sell that
that would be cool
cool and stupid
but still cool
right, and stupid
many cool things are also stupid
(smoking, leather pants, harleys ...)
wait, leather pants are cool?
well, some people think so
and on some people, it may be so
maybe I guess
but it's a stretch I bet
it's not hard to make an ugly, bug dro with python+tkinter. http://emergent.unpy.net/index.cgi-files/sandbox/dro.py
er, "big dro"
View > [ ] Ugly big DRO
View > [X] Ugly big DRO
jepler: can you make a snapshot of that?
* alex_joni wonders how it looks like
oh, ok.. nm .. I read what it does
anyone around who knows his way around sscanf ?
alex: sure - shoot
I have a string I read in from serial
<ch><ch><6 digit data><6 digit data>...
including the angle brackets?
one char, one char, 6 chars that form a double?
and so on..
ok, so a string of characters, like 23476058339201
but they are hexa from what I've seen
and it's a totally fixed-width format?
I'd just split the string up and use atoi or the like
are the 6 characters for the float the hex representation of float data, or ASCII that's missing the decimal point?
it's not really clear from the docs
ok. if the later chars are hex, then it would be best to figure out what they mean ;)
wanna look at the manual?
[16:25:30] <alex_joni> http://www.utilcell.com/ClientData/download/DAT400/DAT%20400%20Manual%200.4-En.pdf
do you have sample data from it?
not right now, it's switched off.. :(
ok. getting there :)
that manual sux badly
what mode are you using?
but the format isn't speciafied for cont. ... :(
so I presume it's the same as for Demand
they say that "the above three modes use this format" ... on page 20
oops - "the above modes do this ..."
ok.. missed that ;)
In the above modes, the transmitter sends serial data using the format shown below:
right (me so lazy)
ok, so I wonder about <net weight>
yeah - they don't say how it's printed
was wondering if a sscanf(buff, "%c%c%6x%6x%6x%d%2x%c"..)
wonder if that would work ?
something like that should work, yes
not sure about %6x
is that OK?
though the %6x might need to be %6d or %6f
I think so
yep - "an optional decimal integer which specifies the mqaximum field width" ...
maximum, that is
where do you have that from?
x is for hex, e,f, and g are floats
google -> man sscanf
[16:33:14] <SWPadnos> http://www.die.net/doc/linux/man/man3/sscanf.3.html
that should also work from a terminal ;)
gotta run - see you later
oh - you may have to install the package gcc-doc (or similar) to get manpages for all the C functions
I'd guess that the "6 ascii characters" are ascii representation of decimal numbers, not hex, although it doesn't say
so you should use %6d
or maybe u
I can't guess what they mean by "the result of the above calculation equals 1 character"
should be easy to figure out what's happening by looking at the stream
I just noticed I missed this conversation by two hours
cradek: sounds promising
what is the format of the new table?
hmm pastebin is slow today
yes, I noticed that before too...
POCKET FMS LENGTH DIAMETER COMMENT # MILL TOOL FORMAT, OR:
POCKET FMS ZOFFSET XOFFSET DIAMETER FRONTANGLE BACKANGLE ORIENTATION # LATHE
1 1 0.5 0.5 0.1 0.0 0.0 9
it will read either format (compatible with old mill tool tables)
the angles aren't used yet, I'm not sure how to define them
there will have to be a picture in the documentation
cradek: do you need more clarification?
is there a standard for how to specify the angles for each orientation?
I have an image on the wiki. It's the format that my cam app uses, and it can (AFAICT) support all possible positions.
there is no standard as such though
[22:14:32] <Lerneaen_Hydra> http://wiki.linuxcnc.org/uploads/angles.png
I'm not sure how to define the angles when using tooltype 2 for example
for a 60 degree threading tool, that would make the angle 60 and 120?
I guess you would base it on the same base
uh, wouldn't that be 60 and 150?
oh, then that's correct (if it's a tool that's facing from behind (like the tool on the picture is))
seems strange to me
uh, you can make any system you want
if it's more sane
why there should be an extra 90 on the right side
there is no real standard as such
that number will never be less than 90
if the tool is 8-sided
and the front angle is 90 and rear something less than 90
that's true I guess
I can't imagine there is such a tool though
oh, very large rough turning lathes use them because of the strength
if you only have gouge protection on one side, is the 92 angle used for anything?
I think I want to include it anyway, so AXIS can draw the tool shape correctly if we decide to do that
it should be able to be left blank (=!0) and then no correction should be applied
yes, that sounds nice
ideally there should also be an edge length parameter (for the GUI) but that could be hardcoded to fit most lathes (maybe 5mm or so)
maybe the tool table should have just what's required for emc, and other settings for the gui should be made in the gui
I hate to make the tool table much larger with unimportant things
hmm, I still can't seem to think of a good universal (applies to all tooltypes, 1-9) angle setup system
the one my cam app uses rotates the origin depending on the tool position
so a type 2 tool would still have the same values as a type 3, as long as the cutter had the same shape
it should be something easy to describe in the documentation, ideally without any special cases
so maybe a system where all angles are based from the -Y axis?
like trailing edge is now, but also leading edge?
so a threading tool for use in your lathe would have 30° for both values
I thought about that too, but it doesn't seem natural for 5/7
and one for a tool-behind center would have 150/150
a threading tool seems like both numbers should be the same, whether they are 30, 60 or 90+60
(I'm agreeing with you)
what if the system only goes clockwise or counterclockwise?
that's an interesting thought
so a threading tool in your lathe would have 30 and 330?
and a threading tool in a tool-behind would have 150/210
I don't see where you get 30/330
seems like 240,300 to me
oh, I was thinking that the tip of the tool is in 0,0
so that 6 instead of being at the top as it is now would be at the bottom
haha I don't follow what you mean at all
ok, I'll draw it up
I'm going to bed soon
I'll upload the image and hope you get it ;)
I'll be here tomorrow though
[22:41:39] <Lerneaen_Hydra> http://img217.imageshack.us/my.php?image=safeposition19tm.png
[22:42:17] <Lerneaen_Hydra> http://img74.imageshack.us/my.php?image=safeposition20tk.png
I took a counterclockwise base as the tool orientation numbers go counterclockwise
not that it really matters though
(the image is a real hack job, the tool-centers are not alligned and so on, but I think you get the idea
g'night cradek, I hope that was enough to explain
as I said before though, I'll be here tomorrow