#emc-devel | Logs for 2006-05-08

[12:10:00] <jepler> where are the tarballs of 2.0.0? Of the 3 "ways" linked from http://linuxcnc.org/index.php?option=com_content&task=view&id=22&Itemid=6&lang=en one is some rambling page, one is to a tarball on viewcvs, and the other is instructions on CVS.
[12:10:29] <jepler> there should be a definitive place to download emc2, and it should probably not be my relatively slow dsl connection.
[12:11:08] <jepler> (not that I've noticed a problem, but this is the first weekday after the release)
[12:48:19] <SWPadnos> jepler, can you add a script to the cvs server that dumps a new tarball on www.linuxcnc.org when there's a new checkin?
[12:48:34] <SWPadnos> then we can link to the copy
[12:50:01] <alex_joni> morning ray
[12:50:06] <alex_joni> hi guys
[12:50:12] <SWPadnos> hi Alex
[12:56:40] <alex_joni> jepler: ok, I'll upload one to Sourceforge
[12:57:33] <rayh> Hi guys. Off reading mail.
[13:06:24] <rayh> I'm getting a lot of interest in halui.
[13:25:50] <alex_joni> rayh: really?
[13:28:26] <rayh> Several calls asking how to do it and if it has a specific command yet.
[13:32:01] <alex_joni> command?
[13:32:43] <alex_joni> http://sourceforge.net/project/showfiles.php?group_id=6744 <- release
[13:33:25] <jepler> SWPadnos: I can't add scrips on the CVS server
[13:33:38] <jepler> scripts either
[13:34:57] <rayh> Any of the commands like those issued by a tk button.
[13:35:14] <rayh> run, pause, abort,
[13:35:28] <rayh> manual, auto, mdi
[13:36:00] <rayh> One guy said he's been waiting years to connect a hard wired control panel
[13:36:32] <alex_joni> rayh: why didn't he say anything :D
[13:37:05] <alex_joni> rayh: manual, auto, mdi already work
[13:37:32] <alex_joni> but the problem is to follow the NIST way (multiple places of control), that means momentary pushbuttons
[13:37:55] <rayh> Yes but halui can easily handle these.
[13:38:22] <alex_joni> no, I mean that halui NEEDS to work like that in order to make it fit well into emc
[13:38:49] <rayh> Okay.
[13:38:52] <alex_joni> there are some things which are HARD to implement as momentary controls
[13:38:59] <alex_joni> like the feed override slider
[13:39:20] <alex_joni> if it's a hardware slider, I would use a rotary knob (resistor)
[13:39:31] <rayh> For all of these, I'd like to see a rotary encoder.
[13:39:37] <alex_joni> but that doesn't follow the NIST way, as the value set by a GUI (tkemc) won't update it
[13:39:49] <rayh> rather than a fixed voltage in.
[13:39:52] <rayh> easier also.
[13:39:55] <alex_joni> right, I can see that
[13:40:04] <alex_joni> easier .. not necessarely (setting up I mean)
[13:40:18] <rayh> Right.
[13:40:37] <alex_joni> rayh: definately something to talk about later today if you care
[13:40:45] <alex_joni> * alex_joni is still caught up at work right now
[13:40:55] <alex_joni> s/care/can/want/
[13:40:57] <rayh> You bet.
[13:41:29] <rayh> I'm writing on emc, baking bread, making soup, and packing stuff for fest.
[13:41:42] <rayh> So I'll be around.
[13:43:28] <alex_joni> cool.. I just finished doing the release at Sourceforge
[13:45:09] <alex_joni> jepler: please let me know if www.linuxcnc.org is still somehow unclear, or if you have an idea how to improve it
[13:50:10] <jepler> alex_joni: yeah, it was hard in axis to get the slider to work (be manipulable, but also reflect emc's idea of the feed override if it was changed in some other way)
[13:50:46] <SWPadnos> much easier with software - you don't need motors to move the sliders around ;)
[13:50:57] <rayh> Tkemc still has a goofy slider thing left over from something Fred P did.
[13:51:43] <jepler> SWPadnos: the problem was that the slider would jitter back to the last setting seen in the stat buffer until the set command was acted upon
[13:52:05] <SWPadnos> right - "user experience" issues
[13:52:15] <SWPadnos> those are always annoying
[13:52:42] <rayh> If the "scale" variable was stubbed into HAL, we could/could we use an instance of the encoder counter module to read a rotary encoder and set the value of that pin.
[13:53:53] <SWPadnos> I think that part is pretty easy now. it's things like switches that are harder to deal with
[13:54:23] <SWPadnos> any hardware UI device has to have either a display device for feedback, or powered controls
[13:54:33] <SWPadnos> otherwise there's no indication of current settings
[13:55:02] <rayh> In ladder we could make toggles into one-shots.
[13:55:32] <rayh> But we would need ways to tell the operator that was the case.
[13:55:40] <SWPadnos> but the toggle switch is still sitting in the "up" position, even if something else changes the setting to "down"
[13:56:31] <cradek> seems like you'd want a center-off toggle that's momentary in both directions, along with an indicator
[13:56:36] <SWPadnos> lighted pushbuttons are probably the easiest control/indicator
[13:56:51] <cradek> yeah or that
[13:56:51] <SWPadnos> yep - or a mom-off-mom + lights
[13:57:13] <SWPadnos> or the optimus keyboard ;)
[13:57:50] <fenn> just get a touchscreen sheesh
[13:57:53] <rayh> These are good solutions.
[13:57:59] <SWPadnos> optimus is way cooler
[13:58:30] <rayh> IMO this is an integrator issue.
[13:58:49] <fenn> emc2 is "more customizable than you can shake a stick at"
[13:59:06] <rayh> If an integrator wants/needs to violate the NIST ideal, we should allow that.
[13:59:26] <SWPadnos> they can do what they want, but it 's hard
[13:59:41] <rayh> Hell I had a guy call frustrated the other day cause his axes wouldn't move.
[13:59:47] <SWPadnos> you need mux2's for everythijng, and a way of changing the selector
[14:00:00] <rayh> Powered up,
[14:00:22] <rayh> He even tried a battery box on the servo dynamics cards and nothing.
[14:00:47] <rayh> estop, was pulled and he didn't even see it on the display.
[14:00:56] <SWPadnos> heh - oops
[14:00:57] <rayh> doh.
[14:01:14] <rayh> I didn't have the heart to send him a bill.
[14:01:21] <SWPadnos> PEBCAD - Problem Exists Between Chair And Screen
[14:01:48] <rayh> Yep. Probably tension with his switch to emc2.
[14:02:26] <fenn> so rayh how do your customers find out about you? i mean i've never seen any ads for emc2 consulting or anything :)
[14:02:53] <rayh> word of mouth or just dumb luck.
[14:03:27] <fenn> pay no attention to emc2sa.com
[14:05:34] <rayh> that's the other emc2 only it's emc superscript 2.
[14:47:22] <alex_joni> or www.emc2.de
[14:52:15] <alex_joni> * alex_joni heads home
[14:52:19] <alex_joni> laters everyone
[19:27:34] <alex_joni> hello all
[19:27:38] <alex_joni> rayh: still around?
[19:28:34] <rayh> zYep
[19:28:55] <rayh> and not typing very well.
[19:31:07] <alex_joni> no biggie :)
[19:31:22] <alex_joni> I had a couple of people screaming at me for the last 3 hours.. so you're excused
[19:31:33] <SWPadnos> yell yell YELL!
[19:31:40] <SWPadnos> err... hi ;)
[19:31:40] <rayh> yuck. irc or for real?
[19:31:48] <alex_joni> * alex_joni just came home from the opera ;)
[19:31:54] <alex_joni> rayh: kidding
[19:31:58] <SWPadnos> bummer
[19:32:07] <alex_joni> but they sang as loud as they could :D
[19:32:10] <SWPadnos> I'd have to bring a walkman or something
[19:32:33] <alex_joni> SWPadnos: it's really nice, if you can get in the mood to appreciate it
[19:32:36] <rayh> oh the opera.
[19:32:51] <SWPadnos> hasn't happened yet, but I suppose it's possible
[19:32:55] <rayh> I was once. (in the mood)
[19:33:36] <alex_joni> so.. wanna talk about halui?
[19:41:13] <rayh> You bet.
[19:41:45] <rayh> let's start with an existing set of signals.
[19:42:05] <alex_joni> ok, got anything specific on your mind?
[19:42:10] <rayh> Let me get a copy running.
[19:42:18] <alex_joni> ok..
[19:42:30] <rayh> what do i put in [HAL] to do that?
[19:42:38] <alex_joni> * alex_joni goes look..
[19:42:44] <alex_joni> these things slip my mind easily :D
[19:43:11] <rayh> me to.
[19:43:19] <alex_joni> HALUI = halui
[19:43:22] <alex_joni> I think :)
[19:43:30] <rayh> sounds like it.
[19:44:05] <alex_joni> this isn't fully decided yet, that's why I tend to forget it
[19:44:23] <alex_joni> because all make sense: [IO] [HAL] and even [DISPLAY]
[19:44:51] <rayh> okay I don't see any parameters for it.
[19:45:01] <alex_joni> there are no parameters
[19:45:08] <rayh> but quite a few pins.
[19:45:20] <alex_joni> right.. simple push-button thingies
[19:45:28] <rayh> 08 bit -W FALSE halui.flood.is-on
[19:45:28] <rayh> 08 bit R- FALSE halui.flood.off
[19:45:28] <rayh> 08 bit R- FALSE halui.flood.on
[19:45:46] <rayh> Okay the is-on is the status pin right.
[19:45:48] <alex_joni> momentary buttons to start & stop flood, and feedback to tell it's on
[19:45:51] <alex_joni> exactly
[19:46:10] <rayh> now I could connect a signal to flood-on
[19:46:20] <alex_joni> you could.. and you should :D
[19:46:22] <rayh> and make that signal true.
[19:46:41] <rayh> what happens then if tkemc turns flood off.
[19:46:49] <alex_joni> and it should turn on (and you'll see it on all the GUI's connected), and the iocontrol.0.... should turn on
[19:46:57] <alex_joni> then is-on will turn false
[19:47:01] <rayh> * rayh tries it.
[19:47:26] <alex_joni> but remember .. you shouldn't keep the signal = true (although that won't affect the is-on to turning false)
[19:48:35] <alex_joni> the state of the halui data is changed on a false->true transition, and only then
[19:50:51] <rayh> Right that is exactly my point.
[19:51:28] <rayh> If you wanted a toggle flood on off switch outboard. It would need to turn either on or off
[19:52:05] <jepler> with hal_speaker you sure hear the decel at the joining of colinear moves
[19:52:26] <rayh> but the hardwired switch would not necessarily reflect the state of the third pin.
[19:52:36] <alex_joni> rayh: you need a lamp for that
[19:52:57] <alex_joni> and a momentary push-button, that goes to either on or off (based on the state)
[19:53:02] <alex_joni> you can do that easily in CL
[19:53:15] <alex_joni> or a simple mux2 will do
[19:53:17] <rayh> or a switch that is centered whenever that signal is false.
[19:53:17] <cradek> I think you would want a button for on and a button for off, or a momentary-off-momentary toggle switch
[19:53:31] <cradek> the toggle would be nicest
[19:53:55] <alex_joni> cradek: a simple momentary is enough too (toggle is nicest), with a lamp to tell you what's happening
[19:54:09] <rayh> That is easiest, but the point is that a hard wired, hard positioned switch does not violate the nist principle all by itself.
[19:54:15] <alex_joni> then you connect that to a mux (selection by is-on), and outputs to both on and off
[19:55:26] <alex_joni> rayh: a hard positioned switch doesn't really fit into the NIST principle.. unless I'm missing something
[19:55:55] <rayh> The nist idea is that a system's state can be read or changed from any of several locations.
[19:56:08] <alex_joni> right..
[19:56:09] <rayh> The hard wired switch does not show the state properly.
[19:56:15] <rayh> but it does not latch it either.
[19:56:19] <alex_joni> and it can't be changed
[19:56:56] <rayh> Sure it can. It is only the edge from false to true that is seen on the emc side of halui.
[19:57:30] <alex_joni> no, I mean you can't physicly change the position of the switch
[19:57:44] <alex_joni> so an operator looking at it has no way of knowing if that's the state or not
[19:57:58] <rayh> not unless you put an actuator out there that does that when the state pin changes.
[19:58:13] <alex_joni> to move a switch?
[19:58:17] <rayh> True enough but wait. This is not an emc or hal problem.
[19:58:28] <alex_joni> I didn't say it was
[19:58:49] <rayh> The fact that the switch does not reflect the true state of emc is an integrator or panel maker problem.
[19:58:55] <alex_joni> I just said that to confirm with the nist principle, the best choice is to use momentary pushbuttons
[19:59:05] <alex_joni> that doesn't mean you can't use other buttons
[19:59:13] <rayh> So I don't see why what you have done is not perfectly acceptable to the emc community.
[19:59:23] <alex_joni> it is.. who said it's not?
[19:59:35] <rayh> Right but that doesn't affect what you have done designing halui.
[19:59:47] <rayh> It affects the way that I might interface to it.
[19:59:59] <alex_joni> you can interface any way you like :)
[20:00:03] <rayh> should interface.
[20:00:24] <rayh> The jmk discussion the other night, if I remember it right
[20:00:36] <alex_joni> he said basicly the same thing.. but with other words
[20:00:42] <rayh> had to do with whether halui had to be written a different way.
[20:00:53] <alex_joni> oh, probably missed that one..
[20:01:05] <rayh> I think that halui is off to a great start.
[20:01:43] <rayh> I'd like to see active axis for manual mode settable there.
[20:02:02] <rayh> I'd like to see jog increment settable there.
[20:02:24] <alex_joni> active axis & jog increment are a bit tough..
[20:02:33] <rayh> If I had those two things, I could implement the handwheel for the mazak while at fest.
[20:02:40] <alex_joni> those aren't global to emc, but they are implemented in the GUIs
[20:02:47] <rayh> Right.
[20:02:55] <rayh> That's why I picked on them.
[20:03:45] <alex_joni> ok, those need to get implemented as a state inside halui
[20:04:28] <rayh> That would certainly be one way.
[20:04:53] <alex_joni> or extend emc to take care of that, which would complicate the hell out of task, which I'd rather not do
[20:05:25] <jepler> I don't see any reason to complicate task
[20:05:43] <cradek> the jog canon interface is currently so simple, I'm with jepler on that
[20:05:43] <alex_joni> jepler: as in keep the stuff in halui?
[20:05:52] <jepler> yes
[20:05:54] <alex_joni> right, that's what I was saying
[20:06:03] <jepler> we all agree
[20:06:04] <alex_joni> it wouldn't really add much..
[20:06:05] <alex_joni> :D
[20:06:06] <jepler> so now alex_joni shall implement it
[20:06:17] <alex_joni> I thought we just agreed I shouldn't do that
[20:06:21] <cradek> haha
[20:06:22] <alex_joni> lol
[20:06:34] <jepler> oh I'm so confused
[20:06:41] <jepler> * jepler crawls back under the rock where he was snoozing
[20:06:53] <alex_joni> jepler: busy day ? ;)
[20:06:58] <alex_joni> too much snoozing?
[20:07:19] <alex_joni> * alex_joni is about to add another config to HEAD.. hope you guys don't mind
[20:08:11] <jepler> at some point we might want to get choosy about the ones we install as examples
[20:08:15] <jepler> but beyond that I don't care
[20:08:23] <cradek> I don't either
[20:08:40] <cradek> and jmk isn't here
[20:08:56] <cradek> I know he's going to raise an objection about configs in cvs one of these days
[20:09:35] <alex_joni> cradek: maybe we should group/rename them (trivial_foo, simple_foo, extended_bar)
[20:09:39] <cradek> it's not clear to me how you would use the jog api with a jogwheel.
[20:10:29] <rayh> each pulse from the handwheel implements an incremental jog of xxx distance.
[20:11:01] <rayh> Most of the handwheels I've used do that increment at rapid.
[20:11:49] <alex_joni> ideally the handwheel would go into emc as position-feedback
[20:11:52] <SWPadnos> I think that's one of the reasons jmk wanted the "delta" output
[20:11:58] <alex_joni> and then moving it will make emc track it
[20:11:58] <SWPadnos> for the canonical encoder
[20:12:55] <cradek> yeah, I'm not sure you can stack up a bunch of EMC_AXIS_INCR_JOG and get what you want
[20:14:03] <cradek> but if the wheel would count independently, and you poll that count and use INCR_JOG for the difference between this and the last polls, it would probably work fine
[20:14:10] <SWPadnos> that's where the jogwheel software (probably halui) needs to be a little smart - it should change to continuous jog at some velocity
[20:14:28] <cradek> no I think it should always use INCR_JOG
[20:14:36] <SWPadnos> (velocity = pulse rate from the handwheel)
[20:14:54] <cradek> I disagree, the handwheel should be absolute positioning
[20:15:02] <cradek> for instance two spins around = 2 inches
[20:15:26] <rayh> No commercial handwheels don't vary rate of motion based on delta between command and actual.
[20:15:26] <cradek> or whatever scale you want
[20:16:03] <cradek> rayh: I don't understand, are you agreeing or disagreeing with me?
[20:16:05] <rayh> Absolute positioning is my preference but we are working in software here and a single parameter could select the mode for us.
[20:16:16] <cradek> ok I think that's agreeing :-)
[20:16:38] <rayh> Yep. It's late in a days worth of contract reading.
[20:16:53] <rayh> and my head is really heavy right now.
[20:17:44] <rayh> One other thing I'm thinking of is a toggle pin for things like flood.
[20:17:55] <cradek> so I think that's the algorithm, poll the count, and periodically issue an incr jog for the differences
[20:17:57] <rayh> If such a pin existed pressing it would swap state.
[20:18:42] <rayh> incr jog does give soft limit protection.
[20:18:54] <cradek> all jogs do
[20:19:06] <rayh> which a simple x follows handwheel doesn't
[20:19:06] <alex_joni> I think any movement does
[20:19:40] <rayh> I'm imagining a hal only implementation.
[20:19:41] <alex_joni> rayh: even the motion controller checks for limits before outputting movement
[20:19:58] <alex_joni> hal only might be trouble
[20:20:09] <cradek> s/might be/is/
[20:20:41] <alex_joni> cradek: you might get lucky and get away with it.. if you're carefull
[20:21:01] <alex_joni> but you certainly can violate all of the machine constraints
[20:21:16] <alex_joni> e.g. start moving the handwheel during a move & so on
[20:21:26] <fenn> crash into a wall
[20:22:20] <cradek> motion has a nice scheme for getting to a destination without violating constraints - if we need to add a canon call to update the goal position, we can
[20:22:54] <cradek> but I think we can get by with only incr jog (updates the goal position relatively, which is what we get from an encoder anyway)
[20:23:29] <alex_joni> cradek: I think halui should only take the delta from an encoder driver
[20:23:31] <alex_joni> then reset it
[20:23:54] <rayh> a long time ago an incr jog during an incr jog used the start of the second at the point of issue of the second.
[20:23:56] <cradek> that would be fine, the encoder drivers all have resets I think
[20:24:00] <alex_joni> or well.. make it calc a new delta since the next time
[20:24:09] <cradek> rayh: that's long fixed
[20:24:09] <alex_joni> s/since/till/
[20:24:09] <rayh> rather than appending successive jogs.
[20:24:21] <rayh> good.
[20:24:37] <cradek> (he says without checking)
[20:24:49] <rayh> np we'll get the chance to test it.
[20:24:53] <cradek> I think I might have even fixed it, I know I looked at it
[20:25:00] <rayh> mdi did the same sort of goofy thing.
[20:25:05] <alex_joni> rayh: what's urgent on halui?
[20:25:25] <alex_joni> start, stop, pause?
[20:25:29] <fenn> displaying estop?
[20:25:35] <rayh> I'd like to implement some buttons on the mazak while there.
[20:25:36] <alex_joni> fenn: it does that
[20:26:02] <rayh> handwheel, perhaps remote jog buttons, and cycle start.
[20:26:13] <cradek> cycle start = run?
[20:26:16] <rayh> which in that case is a simple run
[20:26:18] <rayh> yep.
[20:26:22] <cradek> pause? step?
[20:26:30] <rayh> For now anyway.
[20:26:47] <rayh> Some makers use cycle start even for home.
[20:26:58] <rayh> but we don't need that now.
[20:27:17] <cradek> would you have an encoder per axis for jogs?
[20:27:25] <rayh> some even implement jogs in two steps. select the jog speed and distance and then cycle start.
[20:27:38] <cradek> yuck, that sounds terrible
[20:27:50] <alex_joni> cradek: or select axis
[20:27:52] <rayh> I think the simple pendant I'm thinking of is just jog buttons.
[20:28:08] <rayh> perhaps axis select
[20:28:12] <cradek> ok
[20:28:19] <cradek> we can do any of those schemes I'm sure
[20:28:20] <alex_joni> I think halui needs to do the same as iocontrol does
[20:28:24] <alex_joni> export all kinds of things
[20:28:36] <alex_joni> and the user/integrator only takes the one he needs/wants
[20:28:43] <cradek> one wheel seems like it might be confusing - which way do I turn it again for the direction I want?
[20:28:50] <rayh> That is my thinking on it.
[20:29:11] <cradek> the maxnc software I used made you select the axis and then push one of the shift keys for +/-
[20:29:16] <rayh> clockwise is plus, counter is minus
[20:29:19] <cradek> I could never get the hang of it, it sucked
[20:29:37] <cradek> I drew arrows with a sharpie on the keyboard and I still would go the wrong way sometimes
[20:29:45] <rayh> although I'd think that could be hal connected as well
[20:29:55] <rayh> I know that feeling.
[20:30:16] <cradek> I *never* go the wrong way with emc's jog keys
[20:30:32] <cradek> sorry, just thinking out loud
[20:31:33] <cradek> ok, I have to go, be back late tonight maybe
[20:32:21] <rayh> see you.
[20:32:22] <alex_joni> ok, bye
[20:32:46] <alex_joni> rayh: I'll try to do cycle-start (aka run), pause, step & stop in a bit
[20:33:05] <rayh> Fantastic.
[20:33:14] <rayh> What do you think of the toggle pin?
[20:33:17] <rayh> idea
[20:33:47] <alex_joni> which one?
[20:33:55] <alex_joni> you mean for flood on/off ?
[20:34:01] <rayh> yes.
[20:34:08] <alex_joni> you can use it as halui is written now
[20:34:30] <alex_joni> say your toggle has: TON and TOFF (toggle on & toggle off)
[20:34:35] <rayh> with a block or two four rungs of ladder.
[20:34:38] <alex_joni> put TON, the flood will turn on
[20:34:49] <alex_joni> next you select flood off from tkemc
[20:35:00] <alex_joni> flood will be turned off, even if TON is still selected
[20:35:26] <rayh> I was imagining a single pin that changed the state of flood.
[20:35:43] <rayh> any time it went positive it swapped the state.
[20:37:09] <alex_joni> you can do that with a single mux2
[20:37:35] <rayh> right
[20:37:38] <alex_joni> single pin -> mux2 -> on & off
[20:37:46] <alex_joni> select on the mux2 from the state
[20:38:09] <rayh> okay you win.
[20:38:37] <rayh> and the repair guy wonders what all those blocks are doing in there.
[20:39:02] <rayh> gotta run to town for a bit. bbl
[20:39:32] <alex_joni> ok, catch you later..
[20:39:48] <alex_joni> the alternative would be to have a foo-toggle pin from halui which does that
[20:40:02] <alex_joni> but that would mean quite a bit more pins
[20:40:09] <rayh> That can wait for 4.2
[21:11:02] <globoudou> Hi, I'm a beginner in linuxcnc. My goal is to use it for basix xy stepper table, no problem with this, bur for practice a little more I want to try to command a stepper robot arm. I understand the kinematics definition is in the source code, but I don't really understand the way to redefine it. Is there a documentation that I can start with? Sorry for my english.
[21:12:33] <alex_joni> globoudou: 1. your english is fine
[21:12:43] <fenn> i believe it uses standard denavit hartenberg notation
[21:13:08] <alex_joni> 2. the kinematics gets implemented in emc2/src/emc/kinematics/
[21:13:36] <fenn> 3. you need to port the robot arm kinematics code from emc1
[21:13:40] <alex_joni> if you want a stepper robot arm, then you probably want to look at the puma kins (those are in emc1, but no reason why they won't work in emc2)
[21:13:57] <alex_joni> fenn: port=move & adapt makefile
[21:14:16] <fenn> well thats easy eh
[21:16:20] <fenn> i was wrong, it doesnt have a way to change alpha
[21:16:49] <alex_joni> alpha?
[21:17:20] <fenn> erm.. *scrambles around looking for a picture*
[21:17:45] <alex_joni> you mean R ?
[21:18:13] <fenn> http://www.ee.unb.ca/tervo/ee4353/dhxform1.gif
[21:19:37] <fenn> i wonder how well that code works with different tool lengths
[21:41:08] <rayh> globoudou, We could put a french section on linuxcnc.org and give you access if you'd like.
[21:43:34] <globoudou> Thanks, it's a good idea. I need to work a little bit on linuxcnc before, and when I've few pages, I'll contact you, I think in few weeks.
[21:44:15] <rayh> good. Thanks.
[21:46:42] <alex_joni> rayh: run works from halui ;-)
[21:46:51] <alex_joni> but pause/resume won't.. investigating now
[21:49:05] <rayh> wow that was quick
[21:50:09] <alex_joni> ok, I have an idea what's wrong ..
[21:50:25] <alex_joni> how do you feel about an abort button?
[21:50:39] <alex_joni> there is no program.stop afaik
[21:51:09] <rayh> Yes I think abort is of real value.
[21:52:25] <fenn> i use abort all the time :)
[21:53:40] <alex_joni> ok, this works ok.. as long as you don't try to break it
[21:53:45] <rayh> In mini i implemented feedhold/resume using "scale 0" and "scale $oldscale."
[21:53:57] <alex_joni> it's pretty alpha.. not very rugged
[21:54:09] <rayh> I know a guy who can break most anything.
[21:54:21] <alex_joni> that's why I said that...
[21:54:24] <alex_joni> lol
[21:54:30] <rayh> so when you are ready for a real test, I'll show him how to do it.
[21:54:50] <alex_joni> oh, there is a guy? I thought you were talking about yourself :D
[21:54:53] <rayh> you've gotten to know me pretty well.
[21:55:21] <rayh> yep. but there are a couple of fellows that are even better than I am.
[21:55:28] <alex_joni> ;-)
[21:55:52] <alex_joni> ok, the halui stuff goes in now.. if anything is not 100% .. 'I told you so' :)
[21:56:36] <rayh> thanks for that alex.
[21:56:51] <rayh> I'll get it in a bit and test.
[21:57:08] <alex_joni> no problem