#emc-devel | Logs for 2010-04-13

[06:43:43] <ries_> ries_ is now known as ries
[07:46:37] <micges_machine> hi all
[07:46:58] <aystarik> hi
[07:48:18] <micges_machine> I have VOLATILE_HOME axes on that machine, but I would like my axes to unhome only in estop mode not in machine off
[07:48:31] <micges_machine> could we add such functionality?
[07:52:45] <aystarik> 'machine off' implies you remove power from motor drivers. Then you re-apply the power, driver _may_ move the motor, so your home position is lost.
[07:54:18] <aystarik> stepper drivers for example initialize either with one or both phases on, regardless of the state they were at power off.
[08:01:53] <micges_machine> I know that, we don't disable drivers until estop here
[08:02:59] <micges_machine> I know i implies but on few machines easier is to don't disable drivers than destroy material
[08:06:44] <aystarik> so, don't do 'machine_off' at all then?
[08:10:11] <micges_machine> heh
[08:44:03] <micges_machine> it would be enough, but emc don't unhome axes after estop at all
[08:44:18] <micges_machine> I've just notice it and it's bug
[08:45:50] <aystarik> estop in axis seems to do machine off, so unhome happens after all...
[08:46:31] <micges_work> nope
[08:47:07] <micges_work> there is other execution path when external estop is raised
[08:48:18] <micges_work> F1 F2 generates nml commands, estop goes directly to task main loop
[08:51:16] <aystarik> I mean, if I press F1 in AXIS, in order to have machine working again, I need to press F1 and F2.
[08:57:40] <micges_work> yes but as I said F1 or F2 generated nml that unhome axes, estop directly from machine is readed in main loop below nml processing
[09:05:29] <micges_machine> aystarik: this it patch that fixes it: http://pastebin.com/pujYytYm
[09:06:41] <aystarik> cool!
[10:39:38] <micges_machine> JT-Dev: on docs :http://linuxcnc.org/docs/2.4/html/gcode_main.html#sec:Quick-Reference-Table
[10:39:58] <micges_machine> there are not mentioned all axes that can be used in specific gcodes
[10:41:04] <JT-Dev> you mean like the parameters column?
[10:56:38] <micges_machine> yes
[10:59:44] <JT-Dev> not any room left in the width of the page for the pdf docs i think to add anything to that chart
[11:01:29] <JT-Dev> I was looking at some of the descriptions the other day trying to shorten them up to get the chart a bit more narrow the other day so it fits better
[11:02:04] <micges_work> ok we can think about it later, glad you know about it
[11:03:39] <JT-Dev> I wonder how much the Parameters section helps without descriptions to someone?
[11:04:34] <JT-Dev> I never look at it when I use the chart but just find the description of what I'm looking for then click on the link
[11:04:36] <micges_work> I think it's used as a summary of used words in gcode
[11:08:14] <JT-Dev> do you think the parameters are useful in that list without and info on what they are?
[11:09:48] <micges_machine> I suppose not
[11:12:20] <JT-Dev> my thought is if you know the g code well enough to know what the words mean your probably not even going to look at the list
[11:12:52] <JT-Dev> if you don't know what g code does what you want you'll look at the list then click on the link to find out how it work
[11:13:01] <JT-Dev> works
[11:13:51] <micges_work> so it can be deleted
[11:14:00] <micges_work> I mean paramters
[11:14:14] <robh__> this is where u need a programing manual maybe
[11:14:14] <JT-Dev> that's what I'm thinking at the moment
[11:14:30] <JT-Dev> a g code manual?
[11:15:01] <robh__> like fanuc give u with a new machine, a manual that shows u Gcode, a short program exsample and info on what it does and what needs to be obayed etc
[11:15:46] <micges_work> gcode manual is below that table
[11:15:51] <JT-Dev> I got one with my Anilam 80's mill like that and used it a lot in the beginning
[11:16:57] <robh__> yea list should be kept a quick ref like it is, i like it , look up threading, aah thats what it is, then i can get a quick description what each paramiter is, as i know how to use it so i dont need to know tht
[11:18:15] <JT-Dev> just looking at the user manual and it's only 135 pages long with most of them for g and m codes so it does not make much sense to split it out
[11:19:24] <robh__> back to work i go
[11:19:35] <JT-Dev> It was over 400 pages a few years ago
[11:19:44] <robh__> was just a throught tht was all
[11:19:54] <JT-Dev> back to my second cup of joe
[11:20:37] <JT-Dev> some of the g codes are a bit hard to grasp at the moment from the manual
[11:23:18] <JT-Dev> Does G4 have a L parameter now? I see it listed in the Parameters column but not in the description for G4
[11:25:10] <micges_work> no
[11:25:25] <JT-Dev> ok
[11:29:43] <micges_work> there are missing G17.1 g18.1, g19.1, g28.1, g30.1, G43.1,
[11:35:49] <JT-Dev> ok, thanks
[12:23:37] <CIA-2> EMC: 03jthornton 07v2.4_branch * r1904aa313f17 10/docs/src/ (common/User_Concepts.lyx gcode/coordinates.lyx): add a bit more on coordinate systems
[12:23:40] <CIA-2> EMC: 03jthornton 07v2.4_branch * r893b9628d5e4 10/docs/src/gcode/main.lyx: remove words from quick reference table
[12:24:20] <JT-Dev> hi ho, hi ho it's off to work I go
[13:26:30] <JT-Work> would this be a better g/m code quick reference style? http://pastebin.com/wKjYjMd9
[13:27:17] <skunkworks_> JT-Work: I think all the float pins in classic ladder are for convenience. the out pin just converts the s32 to a float.
[13:27:38] <JT-Work> skunkworks_: thanks, I'll update the manual
[13:28:09] <JT-Work> brb
[14:01:36] <micges_work> JT-Work: looks nice
[14:15:46] <JT-Work> I'm back
[15:34:10] <skunkworks_> SWPLinux: where in the world?
[15:49:56] <SWPLinux> skunkworks_: Las Vegas
[15:50:19] <SWPLinux> strange. when I reconnect to freenode, I get a message that I'm banned from #emc
[15:50:26] <SWPLinux> and I have to /rejoin manually
[15:51:24] <skunkworks_> well - you must not lead a pure life..
[15:54:38] <SWPLinux> I guess not
[15:55:16] <SWPLinux> well, time to get to the conference. see you later