00:53:51 jmkasunich has joined #emc-devel 00:54:01 hey there jmk 00:54:19 hi 00:54:23 seen lerman around? 00:54:32 nope 00:54:36 I think he forgot to commit a file... 00:54:58 he said something earlier about taking care of some kids, and that he hoped to be able to log on from there 00:55:14 interp_o_word.cc 00:55:29 I did a cvs up, and it doesnt compile 00:55:36 yep - he probably forgot to cvs add it again 00:55:43 I can check it in if you like 00:55:52 went to check the farm, and found out that the power supply died :-( 00:55:58 bummer 00:56:07 how big a supply, and whayt kind? 00:56:10 uh-oh 00:56:14 "hmm, why hasn't it done a compule since 12/2" 00:56:29 fortunately it is a old server, with redundant supplies 00:56:42 I was only using one, shifted the power cord to the other and its up again 00:56:54 unfortunately that means a replacement won't be simple 00:57:15 ok. presumably there are replacements in the dumpster somewhere? ;) 00:57:16 gotta check ebay 00:57:31 thats one thing I didn't grab extras of 00:57:33 how big are the supplies? 00:57:47 or, what brand of computer? 00:58:04 Cubix 00:58:23 hmm 00:59:06 356W 00:59:12 422peak 00:59:34 are they load sharing, or failover types? 00:59:52 presumably it doesn't matter, since you've been running on one this whole time 00:59:55 5V @ 57A, 12V @ 4.5, 12V @ 15.2 -12V at 1.2 and -5V @ 0.5 01:00:37 the system is called "ERS Fault Tolerant II" so I assume failover 01:00:45 oh great - SF is having CVS issues now 01:00:47 there are PS OK lights on the front for both supplies 01:00:54 ok. 01:01:36 I may be able to get you a giant 600W dual, non-hotswap, supply from an Antec case 01:01:44 I assume it's AT style, not ATX? ;) 01:01:52 lot of shoehorning to get it to fit 01:01:58 yep 01:02:15 I figure the 900W triple redundant hotswap one has no chance :) 01:02:29 I am a power electronics engineer, so maybe I can repair this one ;-) 01:02:41 get out the smoke detector 01:02:41 (would be easier with a schematic tho) 01:02:55 and look for capacitor juice - that's always good 01:03:14 http://64.173.211.7/support/techinfo/system/ersft2/info/intro.htm 01:04:23 hmm, do I dare?? 01:04:39 * jmkasunich rips off the "Warrantee void if removed" tag ;-) 01:04:41 well - unplug it first, and wear gloves 01:05:11 the busted supply is definitely unplugged, I pulled it out of the chassis 01:05:23 (nice chassis, 30 seconds to swap supplies) 01:05:46 I was talking about if I dared to rip the label... ;-) 01:05:51 ah 01:05:58 them fsckers 01:06:01 I was thinking of the search for capacitor juice ;) 01:06:09 under the label is a tamper resistant torx screw 01:06:23 wow - there's someone selling a machine like yours on eBay for $1500 01:06:26 O_O 01:07:11 I don't suppose they'd sell me a supply cheap... 01:07:30 they must be smoking something anyway.. they're 200MHz for crap sake 01:07:42 no - this is the 406/33 version 01:07:46 486 01:07:51 heh 01:08:41 oh wait - this one might not be - there's another auction for a 486DX2/66 unit ;) 01:09:07 work scrapped three chassis and about 20 or more CPU blades 01:09:18 damn 01:09:29 I have about 4-5 spare blades, but I didn't think to snatch a spare supply 01:09:44 of course, for a workstation, a single Athlon 3000 or so would save you enough in power to justify the cost ;) 01:09:44 (or if I did, I forgot where I stashed it) 01:10:13 hard to run five distros at once tho 01:10:23 yes (unless vmware counts) 01:10:31 and the power biss isn't so bad 01:10:34 actually - vmware is the perfect siolution to the compile farm 01:10:49 no high end graphics cards, one HD per slot, no other periphials 01:11:19 how about no video needed, one HD shared by all distros, and a single CPU shared as well 01:11:39 all running at the same time? 01:11:44 yep 01:11:50 slower than native, but still running 01:12:20 and you can do a direct from CD-ROM BDI install? 01:12:22 my Opteron 244 (single CPU at a time) runs Windows 2000 fast enough for SolidWorks (3D CAD) and Altium (high end electronic design) 01:12:32 actually - direct from ISO, no CD needed ;) 01:12:57 the install is "normal", you don't have to hack anything? 01:13:20 the performance in vmware is roughly equivalent to an Athlon XP3000 01:13:37 right - just set up a VM with IDE as the virtualized controller, and installed BDI onto it 01:13:47 also puppy, and windows 01:14:02 can run all of them at once, though things slow down a little 01:14:05 you want to host the compile farm? 01:14:09 (but not compared to a P-200) 01:14:12 nope ;) 01:14:19 why not? 01:14:20 that's my main work machine 01:14:35 what about an older one then... 01:14:47 If I can get a spare athlon or something, then I may 01:15:15 the actual load isn't much - each slot does a cvs up once per hour, takes 30 seconds or less unless there has been a truly massive commit 01:15:35 if there was a change, it does (./configure;make clean;make) 01:15:41 I might donate a computer to you for it - I'm not exactly a shell guru, and have no idea how the scripts riun 01:16:24 if you help with the vmware stuff, I'll handle the scripts 01:16:38 I can do that 01:16:59 what are the CPUs in the machine now? 01:17:00 actually, they were written with distributed use in mind 01:17:07 Pentuim 200, 128M ram 01:17:11 ok 01:17:26 shouldn't be too hard to get that level of performance out of a modern processor 01:17:49 anybody could check the scripts out of cvs and with help from me (or a single page of instructions I should write one day) have their box act as a slot 01:18:05 cool 01:18:05 the farm takes 11 to 25 mins to do make all, depending on the distro 01:18:24 that's one reason I want to be able to compile on the Opteron 01:18:32 the fastest is the BDI-2.18 slot 01:18:42 the slowest is BDI-Live 01:18:43 this machine takes 15 minutes to do a full (all modules) kernel compile 01:19:07 how long for emc2 make clean;make? 01:19:17 kernel make clean ; time make bzImage modules = 15 minutes 01:19:23 can't tell, I have no RT on this machine 01:19:28 (I've never done a kernel build, that benchmark is meaningless to me) 01:19:39 I can boot the BDI and check though - hold on 01:20:31 well - it's around 100M of source, if that gives you a comparison to emc ;) 01:21:09 heh 01:21:53 though I shouldn't say it's an "all moodules" build - it's just a rebuild of the stock ubuntu kernel and modules, which support most everything ;) 01:21:54 finally un-tamper-proofed the screws and got the cover off 01:21:59 heh 01:22:28 dusty 01:23:03 this is (was?) a quality supply 01:23:16 fat wires eh:? 01:23:39 fuse in a clip, actually replacable without soldering 01:23:47 (and not blown... surprizing) 01:24:02 OK - I have emc2 doing a full make on the BDI virtual machine 01:24:39 no cap juice in sight 01:24:40 jmkasunich: did you ever figure out the compile problem? 01:24:59 the lerman one? 01:25:08 he forgot to cvs add a new file 01:25:28 his mods to the existing file (and the makefile) are there, but the new file isn't 01:25:57 OK - 1 minute, 48.511 seconds 01:26:20 jmkasunich: want me to go fix it? 01:26:39 if you can, I thought lerman would have to do it 01:26:49 interp_o_word.cc 01:26:51 the file is still there in the lerman-interp branch 01:27:02 let me go look at it 01:27:53 neat... the supply is locked into the hot-plug slot by a little bracket 01:28:08 which hits a microswitch and shuts it down before you can disengage it 01:28:15 cool 01:28:32 in its day, this was some first class gear 01:28:40 I like working on that kind of stuff 01:28:44 I think the antec has similar features - the thing I didn't like about it is that all 3 supplies are fed from the same IEC inlet 01:29:11 yeah, this one had 2 01:29:28 smarter that way - you can actually use separate UPSes 01:29:49 mine still has a simgle point failure mode 01:29:52 single 01:30:18 there are 5 installs in the compile farm (at this point), right? 01:30:22 well unless you are in a rather exotic building, they all do - the grid 01:30:28 yes 01:30:38 one is just a router, 4 are doing compiles 01:30:39 no - UPSes would solve that, for some amount of time 01:30:42 ok 01:31:24 I think that a reasonable low level Opteron or A64 machine would outperform the compile farm using vmware for the 4 guest (client) installs 01:31:43 a reasonably fast Athlon XP would likely match it as well. 01:32:32 in practical terms, even a 1G machine would probably surpass it 01:32:41 jmkasunich: fixed 01:33:03 the slots aren't synchronized, so its rare that all four fire off at once 01:33:12 ah 01:33:23 with only one running at a time, the full power (almost) of the host can do the make quickly 01:33:43 true 01:34:14 hmmm - I've actually run emc in stepper mode under vmware - maybe I'll look at how bad the pulse outputs are with the scope ;) 01:34:15 of course, when I replace a power supply, then all four start up at once (or close, I login and kick the scripts off manually, never bothered with cron or anything like that 01:34:45 the scripts should be in a cron job - no reason to have them doing their own timing 01:35:02 unless you don't want to depend on cron (or install) 01:35:03 sleep 3600 is easier than learning cron 01:35:07 heh 01:39:05 hmm, mosfets seem fine, no shorts on the primary side of the switcher 01:39:46 can you see (or smell) burnt chips? 01:39:54 no bad smells 01:39:57 no smoke stains 01:40:00 odd 01:40:14 did you check the fuse? ;) 01:40:23 yes 01:40:26 phew 01:40:37 I hate it when I forget the basics 01:40:53 20:23:38] fuse in a clip, actually replacable without soldering 01:40:53 [20:23:46] (and not blown... surprizing) 01:40:53 [2 01:40:59 and 3 hours later smack myself in the head 01:41:03 ah - misse that 01:41:11 along with the 'd' in missed 01:41:12 I'm wondering if there are some basics here... 01:41:38 IEC socket contacts still connected, ... 01:42:22 so - shrinking the terminal window sped up the compile - it was 1:34.214 for the newly downloadde HEAD 01:42:24 the PS plugs into the huge backplane, and the IEC sockets are connected in back 01:42:32 ah - oK 01:42:35 heh 01:43:10 can't rule out something as dumb as the IEC cord working loose, but I think I checked that kind of thing before I switched over to the backup 01:43:34 are the old BDIs still available? I should just make sure they'll install on this kind of hardware (and software) 01:45:17 I think you can still get 2.18 (or 2.20) and Live RC46 isos 01:45:28 ok 01:45:37 TNG isos got hard to find a while back, but I think I have a copy 01:46:06 I can make you a login on cncgear.com if you'd like to upload 01:46:44 cncgear? thats one of the mirrors, right? 01:46:49 yep 01:46:55 is that you? didn't know that 01:47:08 petev has joined #emc-devel 01:47:12 yep - a hosting service, but mine 01:47:33 actually - I was going to mention them as a viable candidate for linuxcnc.org 01:47:50 I would like to preserve the TNG, even tho Paul has written it off 01:48:07 what was it based on? 01:48:09 lemme check if I still have the isos, might only have em on CD 01:48:11 RH7.3 01:48:13 a classic 01:48:15 heh 01:48:23 but you shouldn't drive classics - they lose value 01:49:37 http://www.isw.uni-stuttgart.de/personen/t_franit/echtzeitlinux/download.html 01:49:45 thats where I got them from, seem to still be there 01:50:27 amazingly, I actually saved the URL in the same directory as the isos.... 01:50:32 ok - I'll download it 01:50:35 heh 01:50:36 probably because it was a bear to find in the first place 01:53:05 rayh has joined #emc-devel 01:53:42 Hi ray 01:54:16 jmkasunich: is that the last bdi capable of running emc1? 01:54:35 BDI-Live will run emc1 01:54:38 cradek, TNG? 01:54:42 that came after TNG 01:54:44 TNG is old 01:54:47 ah, ok 01:55:13 TNG is RedHat 7.2,3 01:55:26 2.x is oldest (based on RH6), then TNG (based on RH7.2) then Live (based on Morphix/Knoppix), and finally 4.x based on Debian 01:55:33 BDI-2.xx is Red Hat 6 01:55:46 ok, got it 01:55:54 and they can all run emc1 except the 4.x family 01:56:03 yay, one slot is reporting a good compile now 01:56:12 the others should finish over the next 10 mins or so 02:04:39 rayh: did you see the changes I checked into halcmd today? 02:07:07 No I didn't get away from customers until just now. 02:07:14 Will get em now. 02:07:25 ok - how'd it go? 02:07:36 Can you describe a bit of what you did with the show 02:07:42 yep 02:07:52 Oh Good. They were tickled with HAL and CL. 02:07:58 headers are gone (no "components" "name FP, etc") 02:08:03 excellent 02:08:28 component names are printed instead of ID numbers with show pin, param, and func 02:08:47 Okay. 02:08:54 there is exactly one format for the value - no extra hex version on the U8 and U16 types 02:09:16 threads are printed one per line - shows the normal info, then the functions in the thread, separated by spaces 02:09:16 that'll help 02:09:20 same deal with signals 02:09:59 the arrows still print, so each connected pin is two tokens, like "==> ppmc.0.stepgen.00.value" 02:10:30 getting it now. 02:10:31 just do some command using the option -s, you'll see the differences 02:10:41 (but be careful - it's ugly to the human eye ;) ) 02:11:10 okay 02:11:26 I spent some thought time on the nodes idea. 02:12:02 actually - to see the differences, do 'bin/halcmd show all > foobar', then 'bin/halcmd -s show all > foobar2', and look at the differences 02:12:17 ok - what did you come up with? 02:12:33 For pins we loop through the pin name 02:12:55 the base of the name ppmc.0 becomes the main node 02:13:30 for that set 02:13:37 yep 02:14:04 then digging down one sub part of the name produces that level of nodes 02:14:05 similar to a directory tree, which gets split at '/', this would be split at '.' 02:14:38 Right. What I want to do for some of the names like we were looking at last night 02:15:03 there were as many as three chunks . separated before we got to any changes 02:15:13 I'd like to make all of that the top node. 02:15:39 we should talk more about the naming conventions though - I don't think we really finished that last night 02:15:42 The exact sort is a bit confused in my head yet. 02:15:54 No we didn't. 02:16:13 That is one thing I'd really like to see happen before the release. 02:16:24 how do you like the idea of just "ppmc.0.dout-00"? 02:16:25 yes 02:16:50 the dout is complete 02:17:03 ? 02:17:34 * rayh takes a minute to look at ppmc pins 02:17:39 hehe 02:17:57 right now it's "ppmc.0.dout.00.output" or something like that 02:20:34 ppmc.0.dout.00 does not cause any confusion as far as I'm concerned. 02:20:47 I agree 02:20:51 the din signals have both in and invert 02:20:55 and conversely ppmc.0.din-00 02:21:11 and I'd make the invert a parameter, just like the outputs 02:21:44 oh. That took a minute. Sure a param sets the signal polarity. 02:22:02 keeps symmetry with the outputs 02:23:26 SWP: 02:23:35 invert on inputs shouldn't be a param 02:23:48 you might need both inverted and non-inverted versions 02:24:16 you can always use an inverter block if that's necessary 02:24:16 although depending on the situation, CL might be able to take care of that for you. 02:37:45 phone 02:38:09 ok - and TP discussion ;) 02:39:27 here we go again 02:39:32 heh 02:39:40 you know, I intended to not turn on IRC, and just code tonight 02:39:45 sorry to bow out - I'm not sure I can be of much help there 02:39:56 but the missing file had me looking for lerman, and...... 02:40:01 yep 02:40:08 did you see the halcmd changes? 02:41:54 yes, haven't run it, but read the commit message 02:41:56 looks good to me 02:43:13 ok - let me know if you think of any changes to the output 02:52:37 Good job on this stuff guys. I'll go test now. 02:53:16 good. let me know if you need any changes 03:02:41 rayh has quit 03:03:06 rayh has joined #emc-devel 03:03:37 HAL:14: ERROR: parameter 'ppmc.0.stepgen.00-03.pulse-width' notfound 03:03:41 back so soon? ;) 03:03:51 machine swap 03:04:29 show param ppmc.0.stepgen, see what the name really is 03:04:52 I'll have to comment these in the hal in order to get that far. 03:05:26 * jmkasunich bites his tongue 03:05:39 Ah. I know the problem. config is pwm, and board is usc 03:05:55 ? 03:06:10 or the other way round. 03:06:12 if the config was pwm, it should be looking for ppmc.0.pwm.something 03:06:17 other way around, yes 03:06:33 you really need two little scripts ray: 03:06:42 Yes I do 03:07:02 start: sudo realtime start; bin/halcmd -kf 03:07:34 stop: sudo bin/halcmd unloadrt all; sudo scripts/realtime stop 03:07:35 phone again 03:07:55 good, I can re-do those without all the mistakes I made the first time ;-) 03:08:09 start: sudo scripts/realtime start; sudo bin/halcmd -kf 03:08:28 that one loads realtime and your hal file 03:08:43 then you can do halcmd show, or whatever you want 03:08:55 the -k will make it keep going after errors 03:09:13 incidentally, I added a prompt for -f (stdin) mode 03:09:16 stop: sudo bin/halcmd unloadrt all; sudo scripts/realtime stop 03:09:26 but left it out in script mode 03:09:27 that one stops and unloads stuff 03:09:33 saw that too, nice 03:09:43 do you think it should be there in script mode as well? 03:09:45 where are you gonna add readline()? 03:09:54 no, not in script mode 03:10:02 s/where/when 03:10:06 ;-) 03:10:13 we had discussed the fact that it would be a "done" indication 03:10:21 for a piped halcmd 03:12:55 SWPadnos: what was that -s thing again. 03:13:15 bin/halcmd -s show pin ppmc 03:13:23 to get the unreadable version ;) 03:14:29 odd no difference here 03:14:46 must not have gotten the good stuff. will try again 03:16:31 if you run bin/halcmd -h, do you see the -s option in the help? 03:26:28 hal_ppmc bit R- FALSE ppmc.0.stepgen.03.enable 03:26:37 That look like your work? 03:27:02 yep 03:27:03 I made a mistake during transfer and compile. To many phone calls. 03:27:08 heh 03:27:35 so hal_ppmc is the owner of the pin 03:27:55 yep 03:28:00 yes 03:28:10 instead of "03" or whatever the module ID was before 03:28:28 hal_ppmc has a bit, read (by the module), currently false, called ppmc.0.(etc) 03:31:49 I'm not sure I like the way signals are printed at the moment 03:33:24 in -s? 03:33:44 the arrows are kinda lame ;-) 03:33:46 yeah 03:33:54 I had considered walking the list twice, so I could print the outptut pin first, then the input 03:34:01 read my mind again 03:34:04 but if there's no output connected, ... 03:34:09 or no input 03:34:21 so you still need to indicate direction in the print 03:34:26 name !no-driver !no-load 03:34:41 or name driver-name !no-load 03:34:58 or name !no-driver loadname1 loadname2 loadname3 03:35:00 or 03:35:14 name driver ==> load1 load2 load3 03:35:18 I like the last best 03:35:25 name ==> load(s) means no driver 03:35:36 ok - that should work 03:35:38 name driver ==> \n means no loads 03:35:42 easy to code too 03:35:45 name ==> means nothing 03:35:50 and easy to parse 03:35:58 right - that was the other problem 03:36:12 actually - it's not as easy to parse with script language 03:36:16 s 03:36:26 they usually work at the word level 03:36:40 though I'm sure it's possible to iterate through the tokens in some fashion 03:36:55 got to bail. started to early today. see you guys tomorrow. 03:37:03 ok - see ya 03:37:15 did just a bit of work with -s and it looks great to me. 03:37:23 rayh has quit 05:59:48 jmkasunich has quit 06:15:47 SWPadnos_ is now known as SWP_Away 07:27:31 alex_joni has joined #emc-devel 07:38:45 petev has quit 14:44:04 chinamill has joined #emc-devel 15:27:05 alex_joni has quit 16:45:13 alex_joni has joined #emc-devel 21:26:54 chinamill has quit 22:16:13 logger_devel has joined #emc-devel 22:16:13 topic is: "Welcome to the Enhanced Machine Control development place. | Regular Developers' meetings 24/7 !" 22:16:13 Users on #emc-devel: logger_devel alex_joni SWPadnos SWP_Away @ChanServ @cradek 22:18:57 alex_joni has quit 22:33:50 petev has joined #emc-devel