#emc-devel | Logs for 2005-12-08

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