so - anyone know why Windows XP (home) would suddenly decide to ignore keyboard input?
across reboots, using "last known good" configuration, and with an external USB keyboard as well?
(note that the keyboard functions well enough to select the last known good config, so it's physically functional)
part of Micro$oft's strategy to get you to upgrade to vista?
you know you're asking in the wrong place, right?
what's XP anyway?
of course - it's a rhetorical question - I jus spend an hour on the phone trying to help a friend figure it out
Xtreme Poop edition
hmm looks like steplen/stepspace parameters affect the maximum velocity (I get the error when I turn the machine on), do you guys think it's only the error or does setting steplen/stepspace to 2 each actually drop the maximum speed obtainable by 50% ?
if you set both to 2, then yes
if it's only 1 set at 2, then you get 66%
alex_joni: ;) thanks, looks like I need to find a way around that then
alex_joni: you're supposed to be in bed, young man! ;-)
jtr: who says I'm not?
Rugludallur: any reason to do that? (stepper driver weirdness?)
Rugludallur: I don't suppose you can krank BASE_PERIOD down?
alex_joni: got one driver on my z axis which requires larger steps
alex_joni: If I lower base period that lowers my max speed for the other axis
I meant lower period, faster freq
btw.. you know you can set steplen only for Z-axis.. right?
alex_joni: I might be able to push it a bit, I'm at 15000 at the moment and I might get to about 12000
alex_joni: Might be time to refresh the computer :D
just remember that newer isn't always better
my advice: get a LiveCD with you when you're shopping for a new PC ;)
alex_joni: (just kidding), I'm sure I can find some way
run a latency test in the store :P
people usually look pretty weird at me when I do that
alex_joni: bring an emc live cd along
Rugludallur: that's what I do ;)
alex_joni: s/in bed/asleep/ ;)
jtr: who says I'm not? ;-)
alex_joni: do you know if RT will be treaded any time soon ?
this might be an AI programm trained with 3 years of IRC logs
Rugludallur: didn't get that..
alex_joni: err threaded
alex_joni: would be neat to run multiple RT threads in parallel without impacting each other
well.. it is like that
except that there's a big bottleneck ;)
and that's the CPU and time granularity
which means at some point the threads would have to execute at the same time :)
but mostly they are not influenced by each other
(think base thread and servo thread)
alex_joni: yeahh, but I was wondering if they can run on seperate cpu's
alex_joni: would jmk's new stepgen core allow the flexibility Rugludallur needs?
jtr: Rugludallur doesn't need flexibility
Rugludallur simply needs more cojones
alex_joni: or reduce my microstepping :P
it's not a limitation on how stepgen works.. it's simply a timing issue
if you need to wait a certain time between steps, then you can't krank up the step frequency indefinately
I'm thinking it will allow finer adjustment of the timing parameters.
jtr: I seriously doubt that
you can output pulses (actually changes, for pulses you need 2 periods), once every BASE_PERIOD
so you either output a pulse, or not
if he needs to wait two base periods between pulses.. then there's not much another stepgen might do better
alex_joni: Is there any reason why steplen/stepspace would need to affect the max velocity ?
steplen + stepspace = period
1/period = frequency (aka ~ max velocity)
actually frequency / INPUT_SCALE
so it's something like this:
BASE_PERIOD * (steplen + stepspace) / INPUT_SCALE
1 / ( BASE_PERIOD * (steplen + stepspace) * INPUT_SCALE )
* alex_joni is tired this late
Rugludallur: but you should get the idea :D
alex_joni: I do
ideally steplen and stepspace are 1
that way you have the max pulse period = 2
you said you have 15000 for BASE_PERIOD?
steplen and stepspace?
I was testing steplen 2 and stepspace 2
alex_joni: the sad part is I only need steplen 2 and stepspace 2 for one axis
oh, that's quite much
Rugludallur: you can set it only for that axis then
and limit the speed on that one
alex_joni: I did, but I still get the warning
on axis X & Y you get max 33.3 kHz pulses
what's your INPUT_SCALE's ?
on all 3 ?
alex_joni not Z, just Y and X
alex_joni: ) have 6.5m with a resolution of 0.002mm :D
so X & Y are 214.592 units/sec max
I assume mm?
ok.. so roughly 200mm/sec
alex_joni: I dn't run them much over 180 though
at 200mm/sec in the ini you shouldn't get a warning for X & Y
now lets look at Z
BASE_PERIOD is 0.000015 (in seconds)
steplen + stepspace = 4
1/(base*4) = 16666 pulses / sec
is this also 155.333 pulses/mm ?
alex_joni: I realized where you going with this and just fixed it :D
Rugludallur: no problem ;)
glad you got it
alex_joni: gotcha. I'm confusing steplen/stepspace with setup delays for the direction signal.
jtr: that's a different issue.. but also needed to be taken into account for
this might be interesting to read
[01:09:42] <alex_joni> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?TweakingSoftwareStepGeneration
alex_joni: I have been reading it for the last hour :D
alex_joni: or tweakin based on it
Rugludallur: when in doubt read #1.5
Thanks. i also realized - it's still a software DDS - still CPU limited. Gotta run feed the cat.
jtr: the 5i20 based stepgen will be something else ;)
yep - looking forward to it. good night.
* alex_joni runs to bed
Rugludallur: let me know how it works
(the whole machine I mean)
alex_joni: I will, and I will make plenty of videos
that's great ;)
alex_joni: I'm also testing jeplers gantrykins
maybe we can work a short technical description for www.linuxcnc.org
alex_joni: but they seem to be broken atm
Rugludallur: broken how?
alex_joni: hope to catch him tomorrow and tell him
* alex_joni might know
alex_joni: No signal gets sent to slaved axis
I recently used them..
hmm.. that's odd
did you set them up right?
alex_joni: I used a stepper config btw
[01:17:11] <Rugludallur> http://pastebin.ca/389646
[01:17:11] <Rugludallur> http://pastebin.ca/389648
alex_joni: As far as I could tell from the documentation this is the right way
AXES = 3
you need 4 there
otherwise motion will only enable 3 joints
alex_joni and the HOEM/COORD to go with it
you can skip that .. but it can't hurt to make it nice
*blush* it's a real mess atm
programs that read the ini from all over the place
[TRAJ]HOME shouldn't be used in your case..
COORDINATES is only read by some GUIS to display the letters (I think tkemc is one of the few)
oooh.. do you need such a fast cycle_time ?
alex_joni: I use tkemc :D
alex_joni: because I run remote X session and gl stuff gets messed up
alex_joni: I can reduce cycle time to 0.010
Rugludallur: I was just curious why you need such a fast cycle_time
alex_joni: i honestly can't remember when I "upped" it
let me know if the AXES=4 fixed it
alex_joni: just did a hw test
alex_joni: everything works :D
alex_joni: the gantry ends sync up and all D:
alex_joni: Now, I need to clean up the THC stuff, move it to this config and I am done
close to done
alex_joni: btw, I made a seperate config I called stepper-gantry and a new thc config called plasma-tch
you need to document it really nicely..
then you are done
alex_joni: Do you think gantry kinematics will make it into emc anytime soon ?
alex_joni: into cvs that is
alex_joni: when that happens I can update the sample configs, remove the dallur one and add stepper-gantry and plasma-thc
Rugludallur: yeah, but probably it will be called something else
it's much more generic than gantrykins
it basicly allows for easy trivkins mapping
alex_joni: hmm, the best analogy I can think off is "master-slave"
Rugludallur: you can also do simple mappings like : joint 0 is Y, joint 1 is A
not related to master-slave
[01:30:12] <alex_joni> http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?IniChanges
alex_joni: so you might change the way trivkins are done today and inc. gantrykins into that ?
probably trivkins is ok for most machines
then there are some other trivkins machines that lack one or the other axis/joint
as it is now, you need to define the missing axis, but simply not use it
alex_joni: I see, hmm I wish I had the time to motorise my lathe :D
Rugludallur: we're not going anywhere :P
alex_joni: nahh but I need to go sailing
alex_joni: in 1 year
isn't it dark for that?
alex_joni: I need to build the boat first, :D
any parts done yet?
alex_joni: which has just become much easier thanks to the fact that I can sync up the two sides of the gantry on my plasma table
hmm.. seen a nice CNC once, for making sails
alex_joni: ahh one of those things that lay down strands for carbon sails
alex_joni: those are brilliant, they use the same machines for carbon fiber for the stealth jets
alex_joni: enables you to individually place every fiber in a carbon structure based on a cad drawing, can't get much more detailed than that (or more strenght for weight)
I liked the harness for people that need to do some tweaks on the sails
they had a bag like a sleeping bag, or like the one on a glider..
alex_joni: The bad part is that the sails only last for one race
Rugludallur: ouch.. then it gets quite pricey I imagine ;)
alex_joni: Yeah, they look just like hang gliding harnesses
wonder if the fighter also lasts for one flight?
alex_joni: They don't know yet, but they promise to test fly one soon
anyways.. what ind of boat will yours be?
alex_joni: did you hear about the f22 raptor date line thingyu
* alex_joni knows squat of boats..
alex_joni: cruiser, liveaboard
oh wait.. I have a rowboat
not quite squat
alex_joni: I just want to relax for a couple of years, get away from it all
alex_joni: brb, going outside to the shop to smoke my celebration cigar (20 sec
03jepler 07TRUNK * 10emc2/src/hal/user_comps/hal_input.py:
fix error if a -SUBSET was not specified:
NameError: name 'parts' is not defined
Rugludallur: that fast?
Much better (im on the cnc controller machine now)
alex_joni: I live in my shop
alex_joni: nice :D
This is the z axis: http://dallur.com/typo3temp/pics/acdd160271.jpg
nice.. what torch is that?
alex_joni: Thermal Dynamics PCM100 but it's highly modified
I was studying a plasma last week
alex_joni: actually it's about stock in that picture but I changed it quite a bit for the sensor
PO-S 70 from Kjellberg ;)
that's a *monster*
alex_joni: I wish I could affor Kjellberg :D
the 70 stands for material thickness it cuts
alex_joni: lol, my 100 stands for Amps :P
alex_joni: only 25mm
I know.. that's the usual way to spec it
70mm, 300A or so
whats the big roll of wire in the pic?
jmkasunich: shielded CAT5 wire, I used it for all limit/home signals and used RJ45 shielded connectors
ok, you just happened to have the roll sitting on the machine table...
Rugludallur shield rj45 ???
jmkasunich: yup :D
that must be an EU thing
Jymmmm: Yup, you can get shielded cat5 and cat6 cabling and rj45 plugs to go with it
* Jymmmm has NEVER seen SHIELDED RJ45 connectors
actually it's not just an EU thing, but I needed full shielding for everything and it's cheap
I've mever seen nor heard pof shielded cat 5 over here
it's called STP
shielded twisted pair.. comes in Cat 5, etc
wierd, it's not that hard to find here but it's not installed unless you really know what you are doing
there is also FTP
if you hook up regular cables to shielded panels you essentially have a panel with dozens of mini antennas, not a good idea
FTP is foil shielded.. a bit worse than STP
I use FTP indoors usually
and STP for anything more prone to problems
[01:51:31] <petev> http://www.ramelectronics.net/html/cat5_cables-shld.html
if you guys are looking for easy cabling for sensors it's about as good as it gets -> http://dallur.com/typo3temp/pics/e0a7596c4b.jpg
Jymmmm: never seen those connectors? the ones from petev's link?
I don't know of any other system that's that compact and cheap
alex_joni: Nope, but it doens't look like you get 100% shield coverage either.
[01:53:36] <Jymmmm> http://www.pacificcable.com/Picture_Page.asp?DataName=R45SLD
yes, the place where you crimp is plastic
Rugludallur: why not use regular rj45 sockets?
[01:55:22] <alex_joni> http://www.tlc-direct.co.uk/Images/Products/size_3/CM2181.JPG
alex_joni: because I had to solider resistor and cross connect ,, converting from pnp to npn sensors and such
back in 90
Rugludallur: oh, ok
I also found great connectors for the motor cabling, now I can disconnect everything in 10 sec
[01:58:51] <Rugludallur> http://dallur.com/typo3temp/pics/997fdbc739.jpg
Are those Neutrik?
jtr: not the cheapest ones but they work really well
Rugludallur: those are common on TIG welders (but with 3 pins only)
alex_joni: I don't think I have seen em on TIG welders, but I when I build a "quick connect" system for my plasma cutter I used a 5pin one for the trigger and signals
They also have a 4pin twist connector that is rated at 800v which I used for the HF connector
Rugludallur: on the signals from the torch usually
err 5p (I didn't want to be able to connect anything the wrong way)
Rugludallur: I usually use Harting connectors
or ILME (same sh*t but italian brand)
[02:06:54] <alex_joni> http://www.ilme.de/produktdb/produkte/bilder/fcdf64.jpg
alex_joni: those look pretty robust
Rugludallur: not quite cheap though
a complete connector (one side) is about 40-50 EUR
case + insert + pins
Rugludallur: but it will work in 10 years
I still can't beleave that everything works now , after a year and half the table is done :D
03cradek 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: like angular, let the user specify the max jog speed of the linear axes
cradek: I will make them tomorrow, now it's beer and cigar :D
03cradek 07v2_1_branch * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: like angular, let the user specify the max jog speed of the linear axes
hmm, 200mm per second isn't that fast but for plasma cutting it should be more than enough
03cradek 07v2_1_branch * 10emc2/debian/changelog: improve mixed linear+angular gui
* alex_joni heads to bed
good night all
goodnight (again) alex
night alex, and thanks for the help
Rugludallur: glad it works
good night guys, im off to bed, thanks for the help
been digging in the Wiki
still lists the latest release as 2.1.0 on the main page
also - I agree with the canned cycles defined by an ini file, that would be handy to allow use of code posted for a different machine.
skullworks-PGAB: wiki fixed, thanks
03petev 07TRUNK * 10emc2/src/emc/motion/usrmotintf.cc: -Cleaned up access to INI file.
03cradek 07TRUNK * 10emc2/src/emc/motion/control.c:
turning a jogwheel during a keyboard jog should not increase the
velocity for the rest of the jog.
is there a simple method to limit the current available to an H-bridge - other thand a fastblow fuse?
03cradek 07TRUNK * 10emc2/src/emc/motion/ (control.c command.c): fix another runaway due to interaction between jogwheel and jog messages
03cradek 07v2_1_branch * 10emc2/src/emc/motion/ (command.c control.c): backport fixes of interaction between jog wheel and jog messages
03cradek 07v2_1_branch * 10emc2/debian/changelog: another bug squashed
* skullworks-PGAB grumbles about having to reset all the pc clocks...
you and me both
I use XP to play games... Any serious work is still done in W2K or Linux.
M$ says XP sp2, W2003, or Vista get patched - otherwise your SOL
Atleast my EMC2 box gets a pass - it has a dead CMOS backup batt anyway.
[05:30:45] <SWPLinux> http://www.intelliadmin.com
go to downloads, the first one in the free section is a Windows timezone patcher
which works on Win2k (or at least appeared to for me)
there's no microsoft update?
not for 2k, unless you have $4000 sitting around
I had heard that, but figured it was a microsoft-hating rumor
but that's a steal - it covers your whole enterprise
it is in part, but it's true
wonder what percentage of that $4000 goes to ... oh forget it
they're only giving the patch to companies that have long term support contracts, and the minimum cost for that is $4k
so it's not strictly a cost for the patch ...
it's nice to have control of my own computers.
not sure I would want the M$ monkeys poking around on my corp network... I have friends who work help desk for M$ internal support - they tell me scary stories
even without an official patch, you could still do the updates yourself - on Win or Lin
they have a program called tzedit, which you can use to edit timezones
or is that the Linux program? - I forgot
yeah - but I have to do each box... too many flavors to do a network push
I don't know, but I should probably figure it out pretty soon
the intelliadmin program is very painless - one click
for Linux systems, there's a timezone compiler I can't remember the name of
* skullworks-PGAB starts looking for a spare USB penn drive...
don' t forget to check your cars, phones, VCRs, and a host of other things (time clocks/punch cards, printers, ...)
and the all-important microwaves/coffee makers
VCR and Microwave have not had he correct time in years
but then the only time I watch TV is after I download a HDTV video torrent...
Oh yeah - its also the recommended date to change out any Smoke or CO detector batteries.
skullworks-PGAB: that's not going to work so well now that standard time only lasts 4 out of 12 months
true - and most devices now tap into wall current
an up-to-date ubunty system should deal with the time change without much trouble, right?
as of last week or so
I've got ubuntu installed now so I can test gcam on it now
well, I saved the best for last... the "update_freq" function
the "pretuned position loop" code is hairy
Twingy: cool. is your system x86, x86_64, something else, SMP ...?
it's a dell D420 subnotebook
what does that mean? ;)
means I've got a dedicated linux box to test on now instead of just freebsd
a notebook isn't a box
you generally work on bigger iron - I'm assuming the code is (expected to be) 64-bit clean?
does it take advantage of SMP/multicore?
nah, no point yet
my last project was all about high performance/smp
building my realtime raytracer for the army
very nice :)
this one is just slow and pedantic
minimal optimizations have been made thus far
with the focus on features
the folks at SolidWorks claim that there's no point in making a CAD program multithreaded, beyond separating the UI task from "processing"
ok by me
so long as the interface doesn't encumber the ability to work from small to large scale it's ok by me
right. I'm not sure I can think of any real improvements to be made with SMP - maybe calculating multiple tool passes simultaneously
you could... but alot of that stuff happens in seconds
Solidworks on a laptop = Catia on a AS400
and you usually only do it a few times
right - I didn't say it would be a useful optimization ;)
next release of gcam will have spur gears
jmkasunich: you can check the timezone info by running zdump -v "America/New_York" | grep 2007
you should see Mar 11 and Nov 4 as the changeover dates
or I can wait another 19 minutes and see what happens
Twingy: what's the underlying model engine like? (NURBS, parametric like parasolid, triangles ...)
right now just lines and arcs
ok - 2.5D?
I wrote a NURBS modeler a while back called nurbana
atm, yes 2.5D
at some point I may throw beziers in b-splines in
I remember hearing about nurbana....
I don't want it to get too complicated just yet
needs to stay clean, intuitive, and ellegant
a reasonable goal
gcam is a walk in the park compared to previous projects
not like I'm juggle quaternions and udp packet filters
that's - err - good? :)
means I can sit down, throw some code in and leave without a headache
* Twingy crawls off to bed
indeed. good night
Good Morning All
martin:r u from france
hmm, yes, I live there, but I am swedish
Martin: All axis movement is working now with gantry homing and all, starting plasma work now :D
is jlmjvm your permanebt nick?
Rugludallur, nice, this will be interesting
Martin: yup, I'm moving/making the ui in pyvcp this time around
if you want that breefing on my hack...
Martin: I took a look at your code, M103/M105, that's instructions to move torch down to material and then pierce delay right ?
kind of, with the help from the hacked HAL timedelay
there is a fat if clause that will determin state and what to do
in the hacked timedelay
M103 to assist M3 and M105 to assist M5
Is pyvcp labelframe broken atm ?
hello Geust856 :D
err Guest856 :D
I am not an expert
Rugludallur: i havent updated in a while, what did you see happen?
tomp: labelframes are not rendered from the looks of it
tmop: Tried with the demo from the manual, blanco
tomp: might actually depend on python versions and such, let me make sure everything is up to date before I start whining :P
Rugludallur: well I better clean up the panels I got and move up, pyvcp is my current focus again...
tomp: I'm moving my stuff from vcp to pyvcp today, I will let you know if stumble upon any issues
Rugludallur: thanks, your stuff is always interesting
tomp: same thing :/
Rugludallur: will look after reboot rqd by update. by for now
rayh: good morning
Hi Dan. How's the family?
Ben is taller than me by an inch
and taking martial arts classes too
I remember the feeling of my first son doing that.
so I better watch out !
Time to stop the spankings.
rayh: I want to set up the gantry for digitizing and have played with halvcp on this workstation
digitizing using probe?
So, I need to bone up on the Hal stuff. Where should I start?
I will make a probe with a simple switch at first
Sure. That will work.
Just make a grid array of probe points and save em.
Is that a stepper gantry?
So, I'm looking for where to start in the documentation
but I can change it to a servo/step machine pretty quickly
Right. In your case, I'd start by running emc2 using the stepper_inch config.
halshow will help you find your way into it.
I really recommend starting with the hal document, the hal sections of the user doc but with a running hal and halshow.
how do I run halshow?
Hal is self documenting.
From tkemc script menu
axis has it under a menu also.
The halshow tree is pretty self explanitory.
ok, found it under Axis
The tree refresh can be a bit slow.
I'd start by expanding pins
and looking at parport
You're familiar with parport pins so you can quickly grasp how HAL deals with one.
yes, I see it now
looks like pins 10,11,12,13,14,15 all have inputs
Notice the output pin 2.
07 bit IN FALSE parport.0.pin-02-out <== Xdir
It's type bit, It is false right now. It's name is parport.0.pin-02.out
Notice the <==
That indicates a link from a signal names Xdir
To that pin.
You can look at signals in the tree, expand x and you'll see what is connected to Xdir.
Now suppose that you want to add an experimental signal.
Let's say an external estop button.
you can make a signal named extestop
using the little entry widget below the show tab.
type in newsig extestop bit
while still in signals?
Now if you look under signals in the tree you'll see it there.
halshow is multitasking.
ok, did it
the tree is a passive display that keeps querying the running hal.
it put it under iocontrol
Now let's connect that new signal to a parport in pin.
the command is linksp extestop parport.0.pin-10-in
that is link signal to pin and the signal is extestop and the pin is parport.
Now if you have a breakout board, connect pin ten to a momentary and to ground.
and you can watch that pin change state as you press the momentary.
You've just done your first custom hal.
You can't save it from halshow
I'm not in the shop at the moment, but I will try this today
ok, how do you save it?
but you could add the list of commands you just executed to a .hal file and add it to the end of the list of .hal files to look at during startup.
You can even put dans.hal in the config and in the ini
ok, from the text editor then
Now to use that external estop is a bit different task.
The way I'd do it is work from a config, demo_step_cl
because that config starts a stepper but adds classic ladder.
The first run of the ladder is estop
The first line of the estop run is internal (emc's estop)
The second run is an external estop.
line not run
If you edit the ladder so that the second line is connected rather than the first you have an external estop button.
ok, now I'm there with demo_step_cl
sorry I was slow getting there
You want to look at the "section display."
I see it
Drag emc out of estop and you'll see the ladder show the path.
Is it %|1 that I should connect?
You can erase the line in front of %1O on the first line
and put a line in front of %I1
use modify on the window that editor pops up.
delete current rung?
sorry, I behind on the cl stuff too
It took me days to get this far.
erase is the parallelogram to the right of the arrow on that editor screen.
you should see it after you press modify.
so, modify, select the parallelogram, the delete?
Once the eraser is active, move the mouse pointer over the leftmost end of the line on the section display.
and click. the line should go away.
finally caught up with you guys, the parallogram is like a stack of papers , 2nd icon on widget palette
ok, got it now
while still in 'modify' mode this works
ok, it's done
modify also stops the ladder run so you'll see changes in emc
now click the horizontal line button or image in modify
move it to the left of the %I1 contact.
and click the mouse again.
Now you'll see that you can not come out of estop.
Now let's look at HAL again using halshow.
I'm running Tkemc here, I see Hal scope and Hal meter under tools
notice that pin 01 is connected to extestop
Right it's under scripts.
legacy error or confusion.
ok I'm there
now back to ladder and look for the ladder signal name for the coil pulled in rung 1
you'll see it's Q0
ok see it
the coil is the rightmost element of a rung.
and back to halshow and we see that Q0 out zero is connected to iocontrol.0.emc-enable-in
That should be good.
Now the only thing we don't know from this is which parport pin %I1 is connected to.
How can we know this?
MIN_FERROR = 0.002
more paste than I wanted.
is the signal we want to see.
sorry, I had switched between Axis and Tkemc somewhere
demo_step_cl uses tkemc
You could change that in it's ini file.
halshow says signal ext-estop is connected like this.
bit TRUE ext-estop
I interpret this as saying parport.0.pin-10-in is connected to classicladder.0.in-01 using a signal named ext-estop.
so the state of pin 10 has taken the place of EMC's internal estop.
I have a ERROR: duplicate signal 'extestop 'HAL:21: newsig failed
brb looking for a parport cable
DanielFalck: you got hardware on the parport?
no, this is my 'inside the house' workstation
I have a boatload of boxes in the garage to play with though
i got a parport breakout, buttons & leds, it's handy to follow this with.
ok, I see where we are now
I had pressed return twice while setting up the newsig
be right back
back -- got distracted
rayh: after doing the modifications to HAL and classicladder, how do you save your changes?
With demo_step you don't need to create an estop signal. I did it for you in the hal file
hence the duplicate error
The only easy way to save is to write out or copy and paste your commands in halshow to a hal file.
and then restart the configuration.
I think there is a way to reload hal but I've not used it.
Now I've got a momentary connected to pin 10 and ground.
Ok, I see it in demo_step_cl.hal
Now back to halshow and click the watch tab
then click on the signal ext-estop
and press the momentary
the "led" should change from yellow to brown.
if it does, move to the ladder view.
I'm running without a par port on this machine in the house
continue on thought
Here I had to click out of the editor in ladder so that my changed wire is put in there.
I'm clicking on the little button in the Vars window to light up the ladder
rayh: exiting does some write?
Now I see the estop momentary affect the rung.
I'm seeing some kind of error here. The momentary signals limit switches as well.
ah there it is.
07 bit OUT FALSE parport.0.pin-10-in-not ==> limit-reached
so pin 10 is doing two things at once.
We could move estop to another pin or remove the limit-reached signal. I'll do that for this test.
got the same error
in the entry widget in halshow
ok, that took it out
aha. Now the external button moves emc from an estopped condition to estop reset.
This setup will not turn emc's machine to on.
that's alright though. The operator needs to intervene at this point
So the external button signals an estop but you will have to reset machine on.
So that is todays HAL lesson.
operator wakes up from day dream about new bike
thank you Ray! I see how to get started now
With all those fancy titanium parts made in portland;)
Glad you guys followed along.
rayh: I need to set up for digitizing some guitar bodies for Jim
HAL is really a fantastic ability.
I have the Microscribe arm for Rhino, but I really want to do it all open source
Did he get a router
no, he's still doing it all by hand
but, this is the first step toward CNC for him
he's jobbing it out
are you probing z or xy?
so, I'm doing the CAD for him
I really just need to do the outside profile first
then the Z depth stuff
He does some pretty fancy curved front guitars, doesn't he?
I checked out the gridprobe.ngc file in examples and it worked with one of the example configs
most of them are carved tops
but we are trying out some simpler stuff to get started
* rayh adds that to memory. I may not last long but it's there now.
top -- that's the word I was looking for.
Tell him hi from me next time you talk.
ok, will do
I will probably incorporate Varkon into the whole project at some point
One last HAL button thought.
If you start up halui when HAL starts you have access to lots of the signals we used in the tcl interfaces.
There is one important difference.
for example, program run.
It will work like cycle start the first time you press a button connected to it.
subsequent presses will raise an error message.
So to do this you'd need to run it through ladder and trap out presses if it's already working.
got a question about user/operator expectations
if X is in the middle of a homing sequence, should the operator be allowed to jog Y or Z?
I wouldn't even try it on a machine.
we can home X and Z at the same time on our lathes at work
DanielFalck: home 2 at once is easy
homing multiples at once is not a prob
Most controls allow for home home home
like to avoid bumping something he sees while homing?
rayh: how about home X, and jog Z in the meantime?
seems like we can do that on Wasino LG8s. I might be wrong though
we basically have three sources for jog type motion - GUI jog commands, the jogwheel, and homing
that is a really scary thought.
and we are trying to deal with some interactions
homing more than one creates a known set of moves.
homing one at a time is better though
yeah, but tossing jogging in there leads to chaos
Yes it really does.
DanielFalck, rayh: homing one or more than one is already covered very well in emc2
the reason this was never an issue before is that everybody thought like ray: thats scary, I'm not gonna do it
the problem is with another source (like a jogwheel) in the equation
Sets my teeth on edge just thinking about the possibility
well, cradek is a good tester - he tried it to see what happened
and it wasn't pretty
so we need to fix it
rayh: so I guess your answer is _not_ to allow it ?
one way would be to lock out all jogs if any axis is homing
did he do it on his machine?
DanielFalck: a brave guy
I think it shouldn't be allowed
its a sherline class machine
not so bad then
Perhaps we need a trap in home routines that raises a message "I'm homing, dammit, wait your turn."
DanielFalck: I kinda agree it shouldn't be allowed
tomp brought up the only case that might make me hesitate about locking it out
when the end of travel is ten seconds away, it doesn't take much bravery at all
hi guys you talking about homing axis all at once
the "dodge an obstacle" case
I could see a big crash on my mill with that one
if user cabt jog out of danger ( tool coming close to a clamp) what are the options? abort? estop?
roltek: no, we're talking about jogging (another axis) while homing one
but if it's a large fast machine, it can be dicey
but the operater is more likely to jog into an obstacle than away from one IMO
tomp: yeah, to both
very dangerous on big machines
roltek: the question is.. is it usually allowed?
even if dangerous?
I'd suggest that if the operator sees an obstacle, he should hit estop, not try to drive around it
I guess I was thinking about 'homing' two axis at once
If the operator pressed home while x was 20 inches away, I'd be inclined to tell him to abort, jog x and then restart the home routine.
jmkasunich: right.. in the time he figures out which way to go it's too late
DanielFalck: we already have good sequencing for multi-axis homes
rayh: right, sounds sane
it occurs more with a full workspace, where visibility is limited and the machine was down. maybe allow jogging before home? or fake home? at least let him overrride speed
I think we all think jogging while homing shouldn't be allowed
you can say in your config "don't home Z unless X is already homed" or "you can home X and Y at the same time, but not Z"
and all kinds of other variations
tomp: jogging before home is allowed
big machines rapid at 3600 inches a min
k didnt know that
tomp: some people (with small machines) never home
you can tell emc2 to save the position on shutdown, and it'll use that the next time
jogging, before home is good
you might need to get the tool out of a bored hole
IMO the feature of saving position is really dangerous.
you should alwys be able to jog machine around before you home
Even if it is an attempt to match a mach feature.
rayh: you need to enable it for it to work
when I requested it, I had no idea mach had one
and then that night after the machine is shut down, the janitor spins a wheel.
anyways.. back to handling homing, jogging and jogwheel
rayh: on big machines I would suppose you had brakes when off, and home switches :)
rayh: thanks for the lesson. I'm off to see what I can do in the shop.
no need to use the position remember there..
are we all in agreement that from the beginning of a possibly multi-axis homing sequence until the very end, all jogs (wheel and GUI) should be locked out?
Yes and you'd have real feedback and home stuff so saving would be worthless.
if you finish up the day after a tool change when the machine is at home you have to jog it off home and then home machine
I vote for jmkasunich last statement.
* alex_joni too
lemme add something:
btw, about homing..
are we all in agreement that from the beginning of a possibly multi-axis homing sequence until the very end, all jogs (wheel and GUI) on all axes should be locked out?
Except the abort button.
can you home Z first the X and then Y
You should be able to anonimasu
anonimasu you can set up all kinds of sequences in the ini file
supporse the operator does try to jog away from a crash? should you put up a message to use estop, or stop the homing process?
how can you jog machine with out jog wheel
roltek: traditional jog commands
keyboard arrows, jog buttons on the gui
real machinist don't use buttons
on the real mills you can still jog with the buttons before the homing sequence..
for emc, jogwheel is new, the buttons have been around forever
but the jogwheel is locked out until your homed and activate it..
anonimasu: not before... during is the question
why locked out before though?
lock out during homing sequences.
that might be but what way are you headed back in the past
Not locked out before.
well, you can still jog to the home switches.. manually
and still home..
too many people talking at once
* rayh shuts up.
roltek: we're not heading back in the past! EMC used to have jog buttons only, now it has wheels too - that moving forward
rayh: yeah while acutally in motion it's locked out..
anonimasu: the question was if it's allowed to jog while homing, guess the answer is not
then we have to make the wheels work all the time
alex_joni: you can do homing manually
anonimasu I want to talk about why wheels might be locked out (by other controls) prior to homing - we don't do that
anonimasu: homing for me is an automatic sequence
alex_joni: like push the jog keys until it hits a switch..
alex_joni: well, if you push home it'll home..
anonimasu why would you ever do that?
alex_joni: it's for avoiding clamps and stuff I think..
true but what do you do if your sitting on the switch
roltek: jog out, then home
if you need to avoid stuff, you should jog until you are in the clear and near the switch, then hit home
with a hand wheel
roltek: you dont..
wheel or buttons, I don't see any reason we'd enable one and not the other
i do every day
anon says some machines enable the buttons and not the wheel at times, and I'm trying to understand why
roltek: well, your setup apparently allows for it to happen
jmkasunich: I think it's because handwheel is a toggled function..
jmkasunich: that's the only reason I think..
they disable it to prevent a jog if somebody bumps it?
thats reasonable, but it has nothing to do with whether you are homed or not, you might want to disable it later for the same reason
I tend to thing of a "handwheel mode" like manual or auto
yeah, but that's done after homing..
in the manual mode..
You have to go there before the handwheel is activated.
so you cant switch it on until you are homed..
anonimasu I see no reason to prevent wheel mode when not homed
so why are you saying "you can't switch it on unless homed"
I've watched roltek home his mill, He'll handwheel until he's near home position then press the home button for that axis.
handwheel should be in manuaul mode with a switch to tell it what axis it is in plus another switch for what increment
jmkasunich: that's how it works on a real control.., perhaps not how it should work in emc..
roltek: thats how our wheels work now
anonimasu you mean "thats how it works on a particular real control" roltek has a real control too, and it works different
well, the heidenhain's do it that way..
I guess you can toggle it to be default on somehow..
unless you say so, we're gonna assume that when you say "a real control does XXX", you mean "EMC should also do XXX"
jmkasunich: that's a stupid statement.
one more reason for system wide configuration
the key word was 'manual mode' which is not exactly translatable to emc. in heidenhain, you vant get to manual mode till after homed
anonimasu this is IRC, I can't tell what you are thinking when you make a statement
some integrators want it one way some another.
tomp: that sheds some light on things
jmkasunich: I can only say "this is how my machine works", and well, then we can talk about how it should work..(how my machine does it may be wrong)
emc has manual mode, that is the default when you start up
anonimasu agreed - but you didn't say anything about how it should work, so I was forced to assume
There is one thing about manual mode before home that is different than manual mode after home -- soft limits
if you said "heid locks out jogs until after homing, and I think that sucks" then I'd know what you were thinking ;-)
it locks the joghweel.. not jog :)
A non-homed machine can be commanded past soft limits.
It has to be able to do this.
right, because it has no clue where the soft limits are
In case it was shut down far away from home.
well when it hits a limit it'll be homed :)
rayh: only if it doesn't remember where it is (j/k)
again im only talking about my machine..
if you do jog it manually for some reason to a limit switch..
anonimasu: it knows when it hits a limit switch and homes the axis?
you can usaully jog it off
an alarm should come up
that's in the pre manual mode..
and you can only jog off not past
"pre-manual mode" thats a new one for me ;-)
heid allows jog buttons before home, and respects limits switches (TNC 306 406 & 416 ) these limits are non fatal
anonimasu: nevermind the mode, but usually limit switches aren't as accurate as home switches
well, "homing mode"
you are in reduced speed also..
lets see a show of hands - how many people think EMC should have a pre-manual mode ?
Right. Those abilities to limit jog direction are a thing on the motor drives not a command thing.
(reading what premanual might mean.... not getting it )
it's a mode where you have the jog keys working..
anonimasu: so you're saying that after it has hit an limit switch, it gets homed, and you don't need to home it anymore to switch to manual?
and a selection for homing X Y or Z
a manual mode before home?
something tells me it would apply from power on until all axes have been homed
jmkasunich: that's right
anonimasu: so you're saying that after it has hit an limit switch, it gets homed, and you don't need to home it anymore to switch to manual?
and in pre-manual mode, wheel jog is disabled, button jog is at a reduce rate, and the home buttons work, and thats it
but this is kind of awkward..
the limit switches are small blocks where it detects the edge of..
allow for jogwheel or joystick in the pre homed condition.
anonimasu: that kinda sux.. I assume these machines do homing based on index pulse?
then hitting a limit would be way worse in precision
alex_joni: yeah but it goes to the very end of each axis first..
it's a inductive sensor..
rayh: so far, we're not even sure we want a pre-homed condition, I'm just trying to make sure we all understand what it is on anon's machine
I hear you.
alex_joni: it's linear scaled with index pulses..
alex_joni: this silly "home on limit" thing is a bit of a digression I think
alex_joni: it is a 'near home ' switch, the actual mark is on the scale, not the switch
we are NOT going to do that
it's probably the wrong thing to call it..
but they use the same sensor for homing then it back off to a index..
we can do that too
I know :)
yes, the sensor is 'near home' , it is not home proper
but what has alex wondering is the idea of homing on any limit any time you hit it
rather than one limit (one end of travel) and only when doing a home command
I "think" they use the other limit switch signal as limit..
I assume 3 switches on one axis (min-limit, max-limit and home)
and I don't expect them to work the same
anonimasu: so I guess they really use only 2, one is shared home and max-limit
the heid swittches are hardlimit- near-home hardlimit+
anonimasu: so jogging onto the hardlimit- doesn't 'home' the axis.. right?
as long as the limit isn't going to trip the estop in hardware, you can use one limit as home in emc
you probably know more then I do.. I just see one inductive sensor :)
ah, one sensor, two targets
alex_joni: thats right
anonimasu: that makes more sense
so the machine doesn't know which end of the travel its at when the sensor trips
you can easily set it up in emc2 that way too
ok, I think we've settled the limit/home switch thing
jmkasunich: you cant end up at a limit without jogging the machine
jmkasunich: I think it assumes based on the direction of travel
unless you put the lever on there..
lets get back to jogbuttons/jogwheels/homing and what should be locked out when
alex_joni: the only way to get past a limit switch is for the linear encoder to die..
we all agree that all jogs on all axes are locked out when any axis is homing
while any axis is homing (sounds a bit more clear to me)
we all agree that all jogs on all axes are locked out while any axis is homing
yes for me
jmkasunich: you mean "in motion"
no, I mean "homing"
oh, then I dont..
there are short pauses after hitting a switch, before backing off to find the index, etc
don't want a jog in there either
before I push the "auto home" button I want to be able to jog
homing starts when you hit the home button, and ends when the axis is homed
if that's the case I agree
between those two there are a dozen states
before you push the home button, you aren't homing, you are in manual
* alex_joni agrees with jmk's above statement too
ain't communication fun...
good thing I started coding 20 minutes ago :P
and the jog or handwheel should work then
I see what you were thinking - the heid comes up in "homing" mode, right?
you can only go to a home(limit) and the machine homes automatically or push auto to home it..
that's homing mode :)
Good jog steering that discusion guys.
btw, did you look at the tuxcnc stuff?(offtopic)
emc comes up in manual, and you can push the home button to start a home sequence - the sequence ends with the axis in home position, and the machine is still in manual
rayh you in a better mood now
during the sequence, we're going to lock out jogs
now - what about mixing jog buttons and wheels?
You get figured out the motor problem, roltek
if you are wheeling X, you should be able to button jog Y probably
not yet but will
if you are wheeling X, should you be able to button jog X? or vice versa?
no 2 drivers for 1 car
If you need, I can set up a parallel mesa system here. Take a while though.
but one thing needs to take precendence over the other
anonimasu: the first one active
after it finished the other one can work too
heid stops motion when 2 commoand go to 1 axis ( like x+ & x- siimultaneous )
they cancel each other out
or x + and wheel
tomp: I've yet to try the jogwheel on motion :)
i had my jog wheel go out lately if you jog button also amchine goes down
cradek fixed a couple nasty bugs that happened if you wheel and jog at the same time
but we realised this morning that its bigger - like the jog X while homing Y thing
so we want to figure out the "Right Thing" to do and then go in the -dev channel and figure out how to do it
i guess one controlER (button mdi wheel ) per axis is ok, and independant
never 2 controlERs per axis
also, I think heid has the switch on the jog wheels because they ripple when you've got them activated.. and in manual..
the trick is dealing with timing and race conditions - who gets there first
most critical is not losing a "jog button release" message
jmkasunich: dosent that solve the issue?
when I was woking up... I had a dream. I had a dream...
jmkasunich: the wheel wont give data when not rotating..
doesn't what solve the issue?
I had a dream that all my brothers and sisters, of all race and color...
or something to that effect...
while the button can stick the wheel cant..
anyways... I was thinking how do I calculate a nesting problem for bar stock.
the bug that cradek found was: start button jog, then spin wheel and release button jog while wheel is turning - wheel jog causes button release message to be lost
jog keeps going even after wheel stops
jmkasunich: wheel should have been ignored
I think we now know what it should do, we just gotta make it do that
jmkasunich: sorry about confusing you
i had a gui btn and a real button, a gui led and a real led.
i had no success getting >either< button to change >both< leds.
Some signals always got disconnected when a subsequent linkxx was executed.
So, I'm not clear on the rule set concerning assignment ( like how many elements on a net, and what happens when a previously used signal/pin is used again)
this was in pyvcp (doh!)
tomp: only one thing can drive a signal
so you can connect the real button and have it drive both leds, or you can connect the GUI one and have it drive both LEDs
if you want both to drive the leds, you need some logic
OR gate, AND gage, ladder rung
HAL has the gates already
ok, so i treid or2's and got the diconnected signals
pastebin your "show sig"
i'll pastbin em
it'll be a while, i just re-upped cvs
it'll be a long while....
# make sure you 'loadrt or count=1' and 'addf' the function!
net button1 vcp.button => or.0.in-0
net button2 hardware.button => or.0.in-1
net led or.0.out => vcp.led hardware.led
i did loadrt or2 count=2 and is there a funct for the the or2?
i got 'exported functs' 06 e0cfc180 e0f3a1b0 NO 0 or2.0 06 e0cfc180 e0f3a1c0 NO 0 or2.1
tomp: that's correct
but also some time params for the ors
yes, looks like the function to update or.0.out is 'or2.0'
the function is called or2.0 and or2.1
one for each OR2 gate
right, the functs are automaticly added, do i need to concern with the time params?
you need to add them to a thread
addf or2.0 servo-thread
addf or2.1 servo-thread
the 'time' and 'tmax' parameters are informational, you usually don't need to pay any attention to them
jepler: thanks, just a screw loose on this side of the operator panel ;)
halcmd show --> http://pastebin.ca/390864
hal file -----> http://pastebin.ca/390867
tho hal shows pins and signals connected, the original pin ( no biblical reference ) will change state, but the connected pin will not
the gui xml http://pastebin.ca/390872
once i did what jepler said to do it worked fine. i never saw more than 3 elements in a net before
03jmkasunich 07TRUNK * 10emc2/src/emc/motion/control.c: comment the behavior of do_homing_sequence() so us slow people can follow it
03jmkasunich 07TRUNK * 10emc2/src/emc/motion/control.c: meaningless comment and format tweak
# the 'net' format requires a named signal, it must be 1st,
# and the ==> is not neccesary,
# everything after the 1st arg are pins that are shorted together
# the order of arg 2 thru n is not important
thanks, this is a nice app
I don't succeed in using the manual tool change feature in AXIS
it works with the sim configuration available in the tree
that's all I've used it with either
I copied the axis_manualtoolchange.hal in the directiry where I've my configuration file
added it in my ini file
what behavior do you get?
added in my ini file the line with the tool change position
TOOL_CHANGE_POSITION = 0 0 2
added, at the end, after the tooltable file
did you add something like this to your ini as well, to specify the location to move to when changing tools?
yes, copied the line from the axis.ini in the sim directory and added it in my ini file
when I launch axis, the small windows about the manual tool change opens
but If I type M6 T1 in the MDI, nothing happens
if I type T1
and after, M6, it says that it needs tool Txx prepared
do you have the loopbacks?
xemet: you need 2 loopbacks for toolchanging to work
do you intend those in the axismanualtoolchange.hal
they are in manualtoolchange.hal
yeah, but usually in the normal halfile aswell
net hal_manualtoolchange.change iocontrol.0.tool-change => hal_manualtoolchange.change
I've added it in my directory and in my ini file
net hal_manualtoolchange.changed hal_manualtoolchange.changed => iocontrol.0.tool-changed
net hal_manualtoolchange.number iocontrol.0.tool-prep-number => hal_manualtoolchange.number
net iocontrol.0.tool-prepare iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
these are the nets you should end up with
well, I think those are in the axis_manualtoolchange.hal file that is used in the sim configuration
[21:08:57] <xemet_> http://www.pastebin.ca/391023
xemet_: lets see MiniMillpinout.hal
[21:09:51] <xemet_> http://www.pastebin.ca/391024
[21:10:45] <xemet_> http://www.pastebin.ca/391026
xemet_: show us the output of 'halcmd save netla | grep tool' to make sure the pins are hooked up as expected
03alex_joni 07TRUNK * 10emc2/src/emc/motion/ (command.c control.c mot_priv.h motion.c motion.h): add free_tp_source to make a difference between jog, jogwheel and homing all driving the same free TP. this way one cannot jog while homing, but it should also catch any problems (runaway jogs and such)
ok wait a moment
I'm using the lates development version run in place, is it influent?
not that I know fo
jepler: sorry, where should I type the command you gave to me?
i can't find some halui pin for "home all" when using axis and home sequence
for do that i using classicladder
daniel: I think that there is no pin for home all
danile: I was searching for it too yesterday
xemet_: at the shell prompt
jepler: without emc running?
witk it running
a halui pin for home all will be great
jpler: sorry, how I get the halcmd prompt while emc is running?
xemet_: many different ways. One is to just open another terminal
03cradek 07TRUNK * 10emc2/src/emc/motion/control.c: only update the target if it's safe for the jogwheel to take control
[21:23:45] <xemet_> http://www.pastebin.ca/391037
...trying to get halcmd prompt
yes, when using run-in-place you have two choices: always use a path to the commands, or always use ". scripts/emc-environment" once per shell session
I always say "halcmd", not "bin/halcmd"
ok , I was not thinking about the fact I was using the run in place
[21:27:29] <xemet_> http://www.pastebin.ca/391044
I think this is the output
15:58:06 <jepler> net iocontrol.0.tool-prepare iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
I don't see the "prepare" loopback
net hal_manualtoolchange.number iocontrol.0.tool-prep-number => hal_manualtoolchange.number
I try to add it
uhm...just for curiosity, why it works in the sim configuration?
xemet_: no, that was from your file
linkpp hal_manualtoolchange.number iocontrol.0.tool-prep-number
*is* in the axis_manualtoolchange.hal file
16:28:16 <jepler> 15:58:06 <jepler> net iocontrol.0.tool-prepare iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
alex_joni confused things by mentioning the tool-prep-number
ah! yes sorry, now I see it
tool changing has two steps: preparing the tool (e.g., turning a tool carousel to the right position) and actually transferring it to the spindle
iocontrol.0.tool-prepare => iocontrol.0.tool-prepared makes the request to prepare the tool always finish right away
xemet_: the linkpp iocontrol.0.tool-prepare iocontrol.0.tool-prepared is usually in the standard_pinout.hal
ah! now I understand...I copied the file axis_manualtoolchange, but don't cared about the pinout
jepler: when will be possible emc2 use fixed rack for toll change?
danielbr: I don't know anyone who is planning to add that feature.
what's fixed rack for tool change?
a shelf with various positions for the individual tools?
03cradek 07TRUNK * 10emc2/src/emc/motion/control.c: don't allow jogwheel while homing
tools in a solid row of position, chuck has to go grab them, tool id is alligned to position
now it works! thank you
this is very good for little machines
very inexpensive tool changer
danielbr: it might be possible to change emc2 to do so, but you need a bit of coding skills
as it is now, it's not supported
i don't have these skills
danielbr: then I guess you might try to submit a feature request
and one day it might get added :)
about that, but currently you have a fixed position for toolchange using the manualtoolchange
if the ini file ToolChangePosition and ToolHolderClear could be written during the program executuion, then the tool prep for tool N would get the positions for tool n and transfer them to the variables ToolChangePosition & ToolHolderClear ( but they are not variables :(
to use this rack would be sufficient to have more tool change positions?
yes... the sacrifice is the machine tool must go fetch each one ( grab drop raise etc... )
slow but cheap
also sacrifice a bit of table space
is it so difficult to change the the code in order to specify one tool change position for every tool? for example in the tbl file?
xemet: not that dificult, only quite a bit of work
if you know your way around the code, then I guess less than a day
if you don't ... then it can be more than a week :D
yes...I can imagine...after working on the nurbs code
xemet: io sono grato
daniel: sei italiano?
xemet: have you ever seen him? :P
an interesting rack tool changer: it is concealed until wanted ( notice lid... the rack seems to pop up ) http://www.datrondynamics.com/options.htm#anchorATM
brasil is beatiful...
yes so much problems but beatiful
daniel: I'm from sicily...a lot of problems here too but beautiful
xemet: as long as you don't end up having horses heads in your bed it's perfect
I know I enjoyed it a lot
Siracuse I mean
my descendance is 50% italian(veneto) 50% germany
danielbr: so you speak some german ?
* alex_joni heads to bed
good night all
03cradek 07v2_1_branch * 10emc2/src/emc/motion/ (motion.h motion.c mot_priv.h control.c command.c): backport free mode planner fixes
hmm, toolchanging is a mess..
03cradek 07v2_1_branch * 10emc2/debian/changelog: backport alex's more comprehensive fixes to free mode planning
[22:25:30] <robin_sz> http://www.quacky.co.uk/~robin/Bike/img001.jpeg
I spenmt half the afternoon polishing it :)
03cradek 07TRUNK * 10emc2/src/emc/motion/control.c: fix race condition that allowed runaway
03cradek 07v2_1_branch * 10emc2/src/emc/motion/control.c: fix race condition that allowed runaway
"ooooh, shes a little runaway .."
coo, Brad Delp is dead :(
a little young for that bike?
ejholmgren, who me?
kid looking out the doorway ;)
oh him :)
mmm ... hes been on it once :)
you know .. Boston, great music ... but ...
well, when you see the video, you can;t help thiking you are watching Spinal Tap :)
[23:19:28] <robin_sz> http://www.youtube.com/watch?v=UFwIgbyrNhw
the drummer in the "caveman" outfit, the moustaches, the hair. the lycra bodysuits!
hilarious, but sounded good :)