00:36:47 * petev is away: eating 00:41:31 jmk_eating is now known as jmkasunich 01:00:07 * petev is back 01:00:20 you eat less than jmk 01:00:27 yeah 01:00:29 [01:25] * jmkasunich is now known as jmk_eating 01:00:30 [01:26] * SWPadnos is now known as SWP_Away 01:00:30 [01:42] * petev has joined #emc-devel 01:00:30 [02:36] * petev is away: eating 01:00:30 [02:41] * jmk_eating is now known as jmkasunich 01:00:32 or at least faster 01:01:02 I had to finish cooking it first 01:01:15 red beans and rice.... tasty! 01:01:15 ahh, I just had a sandwich 01:01:29 * alex_joni made some chilli today 01:01:34 that was yummy 01:02:20 did u guys talk to cradek about the scope of a new branch for some of the code I started? 01:02:45 this is the first I heard of it 01:03:06 ok, I sent him some emails earlier to see what he thought 01:03:06 petev: you are welcome to add your code in a branch at anytime.. 01:03:15 I was hiding yesterday, so I could actually do something instead of talking all night 01:03:20 he prefered a branch, but wanted the scope narrow 01:03:28 if it doesn't involve adding a lot of new dirs.. 01:03:31 I was thinking something like "experimental" 01:03:44 jmk: yeah, I noticed you hidding the last couple of days 01:04:04 just yesterday 01:04:08 alex: I want to get rid of the rs274ngc dir and add an interpreter dir 01:04:19 Thursday I wanted to hide, but wound up on IRC anyway 01:04:22 and move the rs274 there? 01:04:25 that dir will hold the base class and dirs for other interps 01:04:31 right.. 01:04:33 a subdir to interpreter 01:04:36 sounds ok to me.. 01:04:50 the only problem is dirs are visible to head 01:04:50 agreed 01:04:55 but the code is a bit extensive, from task to canon 01:04:55 or from a branch to another 01:05:06 petev: no kidding ;) 01:05:10 yeah, I suggested emc3 module, but cradek didn't like it 01:05:18 nah.. that's bad 01:05:27 yeah, so what to do? 01:05:33 that would be a fork even before emc2 had it's first release 01:05:38 go ahead with a branch 01:05:41 agreed with alex: modules should only be added when we're damn sure that is the way we're going 01:05:55 ok, so how broad a scope? 01:06:05 didn't get that.. 01:06:13 cradek was thinking petev_interp, but I think thats too narrow 01:06:27 interp_rework ? 01:06:27 and I don't want guys to feel like it's my private stuff and they can't touch it 01:06:41 I'm going to replace task, interp, and canon 01:06:48 and maybe some config stuff 01:06:57 task? 01:07:02 thats a lot ;-) 01:07:05 yeah, emc task 01:07:05 * alex_joni is all eyes 01:07:17 explain please!!! 01:07:25 yeah, I want people to critique and work on it if they want to 01:07:28 I'm excited.. :) 01:07:34 the code is a mess 01:07:40 no kidding 01:07:40 alex: and iocontrol too.... ;-) 01:07:41 :P 01:07:46 jmkasunich: buggeroff 01:07:47 I looked at fixing it, but I think it's easier to replace it 01:07:48 :P 01:07:52 lol 01:08:10 I want to expand canon to be the machine view for all, not just interp 01:08:12 jmkasunich: waiting on some feedback from you in the board room ;) 01:08:27 petev: if task gets rewritten 01:08:36 I want to have a task object, interp object, canon object, and config object 01:08:41 we should get rid of machining specific stuff from there.. 01:08:44 alex: yes? 01:08:49 yes 01:08:55 seriously tho, I think there is no longer any real reason for IO to be done in user space.... mix the IO commands with the motion commands, send both thru the same queue to the motion controller, and let it twiddle the HAL pins 01:09:05 I want all machine specific stuff to be a call to canon 01:09:24 canon will be the interface to motion, and IO it we keep it 01:09:30 it/if 01:09:32 petev, jmkasunich: those 2 are related 01:09:45 alex: which 2? 01:10:05 IO mixed with motion commands, and sent to motion controller 01:10:14 petev: can you receive a 1.5 MB mail? 01:10:17 jmkasunich: same for you 01:10:18 sure 01:10:27 yes 01:10:45 jmk: did alex see the doc and pic yet? 01:10:54 (alex: not blowing off the board channel, just can't talk about two things at once) 01:10:55 no I didn't 01:11:03 sending you guys a mail now 01:11:17 pete: no 01:11:37 ok.. this is a software I came across the other day 01:11:49 it basicly isn't much.. some windows CNC software 01:11:57 but I really liked the GUI 01:12:11 not so much the GUI itself, but the things you can set-up, and the way you set them up 01:12:28 I took some snapshots with relevant parts.. 01:12:33 alex: just sent u the docs 01:12:46 docs? 01:13:00 some notes on changes and a pic jmk made to illustrate 01:13:39 so does an "experimental" branch sound too broad to u guys for this? 01:13:59 it sounds too.. unknown 01:14:03 I have no problem with pv-experimental 01:14:04 not saying much 01:14:12 I want to keep initials 01:14:32 jmk: I thought u might use it for the new HAL and TP as well though? 01:14:33 so other folks down the road can use the word experiemntal too 01:14:34 I would want to know what it's about by looking at the name.. 01:14:46 it would be the place to build the new user/RT interface 01:14:49 alex: in that case, emc2.... 01:14:50 petev: there is a hal-refactor 01:15:11 pete: the hal changes are largely unrelated 01:15:30 jmk: which, the meta data stuff or the new motion/TP interface? 01:15:34 I don't want branches with unrelated changes, because management and merging will be a mess 01:15:55 so how will new motion/TP interface stuff be tested? 01:16:07 things like metadata are indepenendt - they are improvements to hal 01:16:14 petev: got my email? 01:16:18 and have nothing to do with emc 01:16:23 I can make an NML canon to test my stuff with emc 01:16:27 alex: yes 01:16:36 alex: got it 01:16:47 I was thinking about the IO mainly 01:16:49 jmk: agreed on the meta data 01:16:59 I like the way you can setup up signals 01:17:02 name them 01:17:06 connect them to M-codes 01:17:11 and to physical pins 01:17:27 where is that (looking at the first pic right now) 01:17:59 I gotta say I prefer a new module for this, emc3 01:18:11 image7 is naming 01:18:16 cool7 I mean 01:18:26 cool8 is connecting to m-codes 01:18:30 rayh: in the long run I agree 01:18:43 ray, that was my first thought, but I don't care, I just want to get it done 01:18:49 because there would/will be massive changes to directory layout, files, etc 01:18:55 not just changes within files 01:19:30 but I fear the "what the hell is emc3" reaction 01:19:35 ahh.. let's not forget our favorite.. 01:19:43 nml ;) 01:20:04 alex: are u referring to the pic 01:20:15 didn't get that far.. 01:20:21 oh 01:20:30 still reading 01:20:36 the colours aren't very helpfull 01:20:54 I also prefer a good release of emc2 before we get to much time drained away for 3 01:21:05 rayh: I agree... 01:21:15 hi all, I'm back 01:21:23 next time use RED and GREEN and BLUE, something to stick out.. but fuchsia and turqoise.. are hard to read 01:21:32 although right now, Pete is doing 99% of the "emc3" work, and he's not involved in the emc2 release 01:21:49 alex: are u using kwrite or MS word? 01:22:05 ms word 01:22:14 and it's 03:21 am 01:22:22 alex:hmm, looks good in mine, that's strange 01:22:42 it looks good, but they are pretty close together.. not something to stick out in front of tired eyes 01:22:52 ahh 01:23:42 also keep in mind that that doc is the product of many days of discussions, and alex is getting it dumped on him 01:24:02 true 01:24:02 I'm trying to figure out who said what in what order ;) 01:24:15 and more discussion after that, that's not covered in there 01:24:27 we talked, then I wrote the doc 01:24:33 then comments were added 01:26:18 is there a way to have a module that doesn't show in the CVS web browse? 01:27:22 yeah.. use a different CVS 01:27:29 hmm 01:28:13 kidding.. not really 01:28:41 alex, how do the custom M codes work in that CNC? do they just flip an IO? 01:29:00 yeah 01:29:08 also they can start a macro 01:29:19 cool9 01:34:21 petev: what percentage of the emc2 code do you expect to retain in your experimental version? 01:35:12 it depends 01:35:21 I can make an NML server on the GUI end 01:35:26 and an NML canon 01:35:36 would that be your choice? 01:35:39 this would allow the new stuff to work with emc2 as is 01:35:51 no, but I think it's probably needed 01:36:15 we need some bridge so everything doesn't need to be done at once 01:39:46 petev: what do you mean NML server on the GUI end? 01:40:30 alex, I want to isolate the comm mechanism from the objects 01:40:43 ok.. 01:40:44 I don't like the way it polutes the EMC code now 01:40:58 it's like a wrapper that talks to the objects 01:41:06 the same way RPC will be done 02:18:18 that's nice 02:18:29 sorry I was away for a while.. finished reading 02:18:33 petev: still there? 02:18:35 ok 02:20:16 so.. that's awfull lots of changes 02:20:54 not that I don't like it.. 02:25:05 petev: not that I want to cut your enthusiasm.. but are you aware of what the extent of that is? 02:28:55 yes 02:29:20 ok.. just making sure ;) 02:29:42 I don't think it's as bad as the emc code makes it look ;-) 02:30:18 well.. I started by wanting to do minor stuff.. 02:30:25 and it's taking me a few years ;) 02:30:43 rayh has left #emc-devel 04:00:17 alex_joni has quit 05:59:43 petev has left #emc-devel 07:27:53 jmkasunich is now known as jmk_sleep 11:06:25 rayh has joined #emc-devel 11:08:24 logger_devel: bookmark 11:08:24 See http://solaris.cs.utt.ro/irc/irc.freenode.net:6667/emcdevel/2005-12-11#T11-08-24 11:38:17 Got any ideas what the hard coding of a,b,c as angular is going to have on folk who wish to use these axes as linear? 13:49:16 alex_joni has joined #emc-devel 13:57:22 martin has joined #emc-devel 14:03:55 martin is now known as chinamill 14:04:46 /msg NickServ IDENTIFY gurrag 14:05:13 that didn't work as it should have :P 14:05:18 :) 14:21:43 rayh is now known as rayh_away 14:26:46 okalleo has joined #emc-devel 14:37:25 chinamill has quit 14:57:13 okalleo is now known as chinamill 15:07:42 alex_joni has quit 16:04:28 rayh_away has quit 17:05:02 alex_joni has joined #emc-devel 18:03:16 For the logger: After changing values to vel and acc in core stepper I got rid of the following errors and the overshooting disapered. 18:06:02 great 18:07:39 * chinamill is away: eat 18:12:49 petev has joined #emc-devel 18:17:15 hi pete 18:17:57 hi alex 18:18:38 hi guys 18:18:49 hi steve 18:18:49 alex_joni_ has joined #emc-devel 18:18:59 got disconnected 18:19:04 hi alex 18:19:05 how's the plans for the branch? 18:19:14 (that's about all you missed) 18:19:24 cradek wanted me to wait until the emc2 release 18:19:40 so I setup a CVSNT server on my machine last night 18:20:58 hopefully the emc2 release will be soon, and then we can cut over to SF 18:21:14 yeah.. working towards that 18:29:22 I'm working on the runscript right now 18:34:08 man - I'm looking at emc.hh (in relation to the multi-axis homing question) 18:34:17 there's a lot of crap that can be ripped out of there 18:36:26 SWPadnos_: check the docs 18:36:36 I spent a few days keeping track of those 18:37:34 alex_joni has quit 18:37:45 alex_joni_ is now known as alex_joni 18:39:10 petev: it would be ok to start the branch now.. but that would also have some problems 18:39:33 any development on HEAD that you need (like HAL for example), is frozen 18:39:37 in your branch at least 18:39:45 one sec on phone 18:39:46 and you'd have to merge it all manually in there 18:39:51 * alex_joni holds his thought 18:39:51 jmk_sleep is now known as jmkasunich 18:40:00 morning sleeping beauty :P 18:40:27 I woke up about 2 hrs ago, was having breakfast, walking the dog, and such 18:40:45 nice ;) 18:40:52 * alex_joni is cleaning up the run script 18:41:01 still need to sleep about 10 more hours to catch up 18:41:17 petev and swp are evil I tell you... 18:41:19 you? 18:41:29 keep me up all night on IRC 18:41:31 how long last night? 18:41:44 last night I quit at 2:30am I think 18:41:50 that's early :P 18:41:57 but they did it almost every night during the week 18:42:05 it really sucks when you have to get up at 7am 18:42:06 then not.. 18:42:15 kick em 18:42:20 or you want me to do it? 18:42:21 :D 18:42:34 I can't kick anybody, no ops 18:42:43 I was kidding.. 18:42:50 I need to learn to kick me 18:42:53 try /quit nickname 18:42:58 like /kick petev 18:43:03 like /quit petev 18:43:04 :D 18:43:48 I need to just stop IRCing and focus 18:44:25 what needs done for the emc2 release? 18:44:43 I want make install to work properly 18:44:47 (I want to work on my VCP stuff, but I suppose that isn't the highest priority right now. 18:44:55 ray said about bridgeport equivalence 18:45:12 wanna finish the configs/foo/ stuff today 18:45:29 anything I can do to help? 18:45:48 hmm, I have a PROM from JonE for the UPC, I should finish that testing 18:45:50 not really.. maybe look at the stuff I do, proof-reading / testing 18:46:05 hi - I'm back 18:46:18 * jmkasunich hides 18:46:39 must... not.... talk.... about.....emc...3..... 18:46:53 how about emc2 then ;) 18:47:05 depends 18:47:24 hey -what's t he new prom supposed to do? 18:47:38 make it a ppmc? 18:47:47 turns it from USC to UPC 18:47:55 ok 18:47:55 so I can test the PWM gen code 18:48:18 I was going to email him about the bugs we found in the FPGA code (the mysterious +4 or 5) 18:48:32 I already griped at him about it 18:48:42 ok, good 18:49:01 I think he actually knew, and either didn't care (the loop compensates for it) or embedded the fix in the code and didn't bother to fix the docs 18:49:26 there are docs? ;) 18:49:43 if the pwm works, I'm gonna close the tracker and call it done... he can test the other stuff (or not) 18:50:06 yep 18:50:14 sounds good 18:50:30 I wish he didn't fake out input 15 18:50:35 ehwn SSR8 is off 18:50:38 when 18:51:07 that whole estop thing is fscked IMO 18:51:15 yep 18:51:19 yep - that's what I meant ;) 18:52:26 alex - which docs wid you mean regarding emc.hh? 18:52:34 s/wid/did/ 18:52:53 there's a csv file, I can send you that 18:53:05 ok, I'd like to see it 18:53:05 petev: back? 18:53:10 yeah 18:53:15 damn, the US Postal service bent the snot out of the prom leads... 18:53:30 needlenose pliers and patience are required 18:53:37 or great soldering skill ;) 18:53:46 pliers 18:53:55 yuo'd think that the pins would be in foam or something 18:54:12 petev: the thing cradek was worried about is that once you branch devel is frozen 18:54:13 thanks 18:54:29 and if there's improvement in some places (like HAL), you won't get that on your branch 18:54:35 unless you merge it in manually.. 18:54:41 he stuck it in a tiny (1/2" square) piece of foam, stuck thatin a hole cut in a piece of cardboard, and stuck that in an ordinary envelope 18:54:44 alex_joni: hmm, seems easy enough to jus merge the stuff that's unchanged again 18:55:03 if you branch of a release, then it's most likely to work for a long time.. 18:55:12 combined thickness of the cardboard (especially after the post office got done with it) was less than the original height of the part 18:55:16 perhaps a piece of cardboard folded over the foam would have been better (or just stick the pins in the cardboard itself) 18:55:52 alex_joni: yeah, the CVSNT is working now, so it's not a big deal, hopefully emc2 release won't take long 18:55:57 right now it kinda looks like a SMT leadform... 18:56:05 except they are bent in instead of out 18:56:18 J lead 18:56:29 ok - the original SMT style (J-lead) 18:56:37 yeah :D 18:56:40 yeah 18:56:50 heh 18:57:22 SWPadnos_: need help decifering that? 18:57:32 maybe - le t me open it first ;) 18:57:42 any spreadsheet will do 18:57:49 that can open csv files 18:58:26 damn its hard to work with a cat in your lap 18:58:57 OK - I remember this file (from way back) 18:59:34 I was thinking more of the data in status 18:59:46 all the PIDFF, backlash, etc aren't needed, since the data is in HAL 19:00:29 maybe this would be more appropriate for emc3, but just tossing the idea out: 19:00:41 where do u draw the line between what's in INI and HAL when HAL can pull from INI? 19:00:58 what if all the emcmot_set_foo commands were replaced by hal parameters (still pulled from ini) 19:01:03 petev: not talking about ini, looking at emc.hh status struct 19:01:09 oh 19:01:13 back to coding 19:01:20 but ini is another thing I was thinking about 19:01:27 emc.hh defines all the NML messages, and a lot of them are just setting values 19:01:35 yes 19:02:43 actually, there should just be a generic "EMC_{GET,SET}_HALPIN" nmesasge, that takes a name and either a value or a pointer to a value 19:03:01 param, not pin 19:03:13 true - for these kinds of things 19:03:56 this is yet another example of what robin used to gripe about with NML 19:04:10 yep - 1000 messages where 2 or 4 would do 19:04:15 if you send "set name, value", only the sender and receiver need to understand name 19:04:31 if the message has the name hard coded into it, then entire transport layer must know 19:04:36 clean it up, it will make the new NML servers easier ;-) 19:04:46 and you end up with 480-line switch statements 19:05:05 unforch I bet the GUIs (thru emcsh) send some of those messages 19:05:18 for instance, in emc1, you could tune PID using the gui 19:05:28 it sent SET_PID_GAINS messages 19:05:32 yep - that's what Ray is working on now 19:05:36 for emc2 19:05:41 if we cleaned up, the GUIs would need rework 19:06:08 unless he's ripping that stuff out anyway 19:06:09 do u really think u should be able to tune PID from the GUI? 19:06:09 actually, don't the GUIs use emcsh? 19:06:19 maybe some special integrator tool 19:06:20 SWPadnos_: only tcl ones 19:06:25 ok 19:06:39 those are the most commonly used though (and cradek and jepler can fix AXIS ;) ) 19:07:08 the GUIs use emcsh, so we'd have to fix both emcsh and tkemc and mini 19:07:34 the trouble is that with HAL, there's a higher level of configuration - you don't know where to send the joint 0 P value until there's a HAL connection 19:07:35 emcsh so it would no longer send the old messages, and tkemc and mini so they would no longer request them 19:07:38 fixing emcsh would be mostly deleting code 19:07:47 maybe the same for the GUIs 19:08:04 still a lot to do. would delay the release 19:08:13 the GUIs should be asking to set the P value of joint 0, so what emcsh does should be transparent 19:08:15 save that for 2.1 I think 19:08:26 (should be) 19:08:51 with HAL, that still demands a lot more smarts from emcsh 19:08:53 what about just having emcsh turn em into NOPs? 19:09:06 no - they should stiull perform the function 19:09:18 oh, that's a lot of work 19:09:22 if they aren;t gonna do anything, then they should be removed from the menus to avoid confused users 19:09:22 if they don't, then people wonder why nothing changes when they retune 19:10:04 if the user changes them from the GUI, he surely expects the changes to persistst 19:10:11 dam I can't type 19:10:17 yes 19:10:22 how will the persistance be handled? 19:10:29 and thats why emc rewrites the ini file 19:10:31 good question 19:10:31 the param settings need to be saved 19:10:34 (something I find offensive) 19:10:42 the connections as well 19:10:46 yep 19:10:53 HAL configurator 19:10:59 rip it outa the GUIs 19:11:06 incidentally, that was something I couldn't find - where the heck is the code that rewrites the ini file? 19:11:29 I searched the entire tree for OUTPUT_SCALE, and didn't see anything that looked like an ini *write* 19:12:01 but u confirmed it was being written? 19:12:06 yes 19:12:09 it is written 19:12:15