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

[20:53:37] <alex_joni> cradek: still around?
[20:54:06] <alex_joni> oh.. I only noticed now how late it is.. you're probably heading home
[20:54:36] <cradek> I'm still here for a few minutes at least
[20:55:13] <alex_joni> I want to add optional stop
[20:55:21] <alex_joni> and I was wondering if you can help GUI wise
[20:55:41] <alex_joni> e.g. add a small button to AXIS
[20:56:19] <cradek> I'd have to think about a good place for it
[20:56:27] <cradek> it should be a checkbutton I suppose
[20:56:43] <alex_joni> or at least a button which stays pushed
[20:56:50] <cradek> you should be able to change it even while the program runs
[20:56:55] <alex_joni> indeed
[20:57:14] <cradek> there's no such thing as a button which stays pushed :-P
[20:57:23] <alex_joni> are you sure?
[20:57:29] <alex_joni> there are stuck buttons all the time
[20:57:43] <alex_joni> at least on touchscreens usually
[20:58:12] <alex_joni> I see you looked at it before (even if briefly)
[20:58:26] <alex_joni> I'm thinking NML message to change the state
[20:58:26] <cradek> they might be an exception - I think normal widget sets that work with the mouse don't have that
[20:58:40] <alex_joni> one that can get sent at any time
[20:58:50] <cradek> yes I think I agree that's what you want
[20:59:22] <alex_joni> I'm only concearned about readahed ans such
[20:59:25] <alex_joni> and such
[20:59:35] <alex_joni> argh.. my typing sux :(
[20:59:43] <cradek> like pause, you can't read ahead past that
[20:59:43] <alex_joni> readahead
[21:02:58] <jepler> I have no idea what the icon would look like but I think this would belong in the toolbar, where there *are* buttons that stick up and down
[21:03:05] <jepler> it certainly can't go inside the tabbed area
[21:03:30] <jepler> I'd like to know how the "optional stop" is used in the real world -- I don't understand it
[21:03:33] <alex_joni> jepler: maybe something involving pause in the icon
[21:04:04] <cradek> say you want to change the tool when it gets dull
[21:04:09] <alex_joni> basicly (as I understand it) you have some checkpoints in the program, where you could change some things
[21:04:13] <cradek> you might put optional stops in the program when the tool is safely in the air
[21:04:27] <alex_joni> if you activate it, then it stops, if not.. it just goes ahead
[21:04:51] <cradek> When the Interpreter is integrated with the EMC system, the controller checks the optional stop switch when the OPTIONAL_PROGRAM_STOP canonical function call is executed and either stops (if the switch is on) or not (if the switch is off).
[21:05:28] <alex_joni> jepler: on the robots I work with there are means to read data from the user during a program, but that can be set up using optional stops. so if the user decides he wants to change something (like part numbers or whatever), he activates it
[21:05:30] <cradek> they constantly talk about a switch, but I think it should probably be in the gui too
[21:05:57] <alex_joni> I think they meant a switch in the GUI
[21:07:17] <cradek> ok
[21:07:24] <cradek> I can't tell that but it's possible
[21:07:41] <alex_joni> anyways, beeing part of a GUi, it will be in halui aswell
[21:07:42] <cradek> they say 'cycle start button' etc too
[21:07:46] <cradek> yes
[21:07:47] <alex_joni> so it can be a switch too :)
[21:08:49] <jepler> OK that helps me understand what it's for
[21:09:21] <jepler> so basically you want to stop at the next checkpoint (determined by whoever wrote the g-code)
[21:09:47] <jepler> does it stop or does it pause?
[21:09:49] <alex_joni> there's a G-code for the optional stop
[21:09:51] <alex_joni> it pauses
[21:10:05] <alex_joni> and you can resume the normal way
[21:10:51] <jepler> and hitting this code removes the "stop at next optional stop" condition as well?
[21:11:09] <alex_joni> didn't quite get that..
[21:11:30] <jepler> never mind
[21:11:30] <cradek> I don't think any m/gcode changes the state of the optional program stop switch itself
[21:11:39] <alex_joni> once pushed (optional stop on) it will stop at any checkpoints
[21:11:57] <alex_joni> is that what you asked?
[21:12:14] <jepler> so it's like a checkbutton, except for the normal NML problems with having anything that isn't just a momentary switch
[21:12:50] <alex_joni> basicly it's a checkbutton with multiple points of control
[21:12:52] <cradek> I don't see that it's different from the other checkbuttons
[21:12:58] <alex_joni> you can either set it or reset it
[21:13:06] <alex_joni> the GUI should display based on status value
[21:13:09] <cradek> there will be on and off nml messages
[21:13:14] <cradek> right
[21:13:20] <alex_joni> only one message with value as param
[21:13:25] <jepler> we have checkbuttons like that in axis already -- spindle brake for instance
[21:13:34] <alex_joni> don't want to clutter it more than necessary
[21:13:49] <alex_joni> jepler: right
[21:15:48] <jepler> If you implement this in emc I'll add it to axis
[21:15:59] <alex_joni> I'm digging through it
[21:16:03] <alex_joni> it won't be long
[22:05:09] <danex> * danex is away: Away at the moment