Back
[12:51:54] <alex_joni> morning all
[13:17:42] <jepler> hi alex
[13:17:54] <alex_joni> hi jeff
[13:18:24] <alex_joni> what's up?
[13:18:51] <jepler> not much
[13:18:56] <jepler> just thinking it's about time for breakfast
[13:19:16] <alex_joni> hmmm.. I just updated my repo
[13:19:25] <alex_joni> and it seems it fails with some error while building axis
[13:19:41] <alex_joni> /usr/bin/ld: cannot find -lemc
[13:19:41] <alex_joni> collect2: ld returned 1 exit status
[13:19:41] <alex_joni> make: *** [../lib/python/emc.so] Error 1
[13:20:00] <jepler> hm really?
[13:20:51] <alex_joni> maybe I borked up the repo, while deleting some dirs, and afterwards updating ?
[13:20:59] <alex_joni> can't see any other obvious errors
[13:21:19] <jepler> hm
[13:21:20] <jepler> /usr/lib/libemc.a
[13:21:36] <jepler> I had this file, from emc2-dev
[13:21:42] <jepler> when I remove it, axis won't link
[13:21:43] <jepler> I'll fix
[13:21:50] <alex_joni> ok :)
[13:22:08] <alex_joni> I don't think I have emc2-dev installed :)
[13:24:31] <jepler> does it work after that fix?
[13:24:50] <alex_joni> it proceeds further.. thanks
[13:25:16] <alex_joni> I still get some weird CVS messages while updating though (CVS move away foo.py, it's in the way)
[13:25:34] <alex_joni> huh.. make builds the docs now too?
[13:25:40] <jepler> yes, it does
[13:25:48] <jepler> rm -r share lib/python
[13:26:04] <alex_joni> I did before updating
[13:26:05] <jepler> you may need to do that ^^^ as suggested in my mailing-list post last wednesday
[13:26:20] <alex_joni> the rm -r I mean
[13:26:31] <jepler> what is the directory and filename of the file 'in the way'?
[13:27:30] <alex_joni> I'll pastebin it.. a bit long
[13:27:50] <alex_joni> http://pastebin.ca/127776
[13:28:52] <jepler> but you did 'rm -r lib/python'
[13:29:12] <jepler> try removing all of lib/ and use -f if necessary
[13:29:12] <alex_joni> I just did it again
[13:29:57] <alex_joni> I see the first cvs up -dP that pulls them back in, and the next one to cause the errors again
[13:30:29] <cradek> this is what always seems to happen to jmk
[13:30:31] <alex_joni> * alex_joni removes all of lib/
[13:30:48] <cradek> it's something about the D// in the above Entries file
[13:31:40] <alex_joni> hi chris
[13:31:51] <alex_joni> I removed the whole lib dir now
[13:31:57] <cradek> hi
[13:32:13] <alex_joni> ok, that cured it
[13:32:36] <alex_joni> jepler: 'rm -r lib' made it work OK for me, not lib/python
[13:33:59] <jepler> hm
[13:34:02] <jepler> * jepler goes to have breakfast
[13:34:10] <alex_joni> sounds like a wise decision ;)
[13:34:24] <alex_joni> I missed breakfast today .. started with lunch
[13:41:41] <alex_joni> AXIS & emc2 seem to be working great.. no issues
[14:00:25] <jepler> glad to hear it
[14:00:39] <jepler> hi cradek
[14:01:05] <cradek> hi
[14:01:22] <jepler> max running on two CPUs yet?
[14:01:41] <cradek> nope, no combination of those CPUs and power modules worked.
[14:02:01] <jepler> shucks
[14:02:51] <cradek> guess I wasted dollars and dollars
[18:05:16] <jmkasunich> alex_joni: you around?
[18:05:37] <alex_joni> barely... :)
[18:05:58] <alex_joni> watching a movie, but I look in here once in a while
[18:06:08] <jmkasunich> the documentation files that you moved into the main cvs module - you didn't delete them from the documents module yet did you?
[18:06:34] <alex_joni> not yet
[18:06:41] <alex_joni> but I can today
[18:06:50] <jmkasunich> (after the movie ;-)
[18:06:52] <jmkasunich> thanks
[18:07:03] <jmkasunich> I want to see what is left after that is done
[18:07:25] <jmkasunich> once _everything_ we need is moved, it will be time to backport the docs stuff to the 2.0 branch
[18:07:36] <alex_joni> ok
[18:07:48] <jmkasunich> then do some edits on that branch to it describes version 2.0.x
[19:49:59] <jepler> .
[19:50:11] <jmkasunich> ..
[20:05:16] <Lerneaen_Hydra> ...
[20:09:56] <alex_joni> /
[20:09:59] <alex_joni> |
[20:10:01] <alex_joni> \
[20:10:04] <alex_joni> -
[20:10:06] <alex_joni> /
[20:17:13] <Lerneaen_Hydra> █ |
[20:17:25] <Lerneaen_Hydra> █ \
[20:17:30] <Lerneaen_Hydra> █ -
[20:17:35] <Lerneaen_Hydra> █ /
[20:17:43] <Lerneaen_Hydra> █ █ |
[20:17:47] <Lerneaen_Hydra> █ █ \
[20:17:50] <Lerneaen_Hydra> █ █ -
[20:17:53] <Lerneaen_Hydra> █ █ /
[20:18:10] <alex_joni> hmm
[20:18:17] <alex_joni> people completely lost it ;)
[20:28:47] <alex_joni> jmkasunich: did you remove the hal docs?
[20:28:53] <alex_joni> from documents/ I mean..
[20:29:12] <jmkasunich> yes
[20:29:23] <alex_joni> ok.. I'll get at removing the other stuff now
[20:29:30] <jmkasunich> (I think - did you cvs up in that module?)
[20:29:32] <alex_joni> I still want to leave emc1 docs in place..
[20:29:37] <jmkasunich> right
[20:29:42] <alex_joni> yeah, I did.. and now after looking closer, it seems to be gone
[20:29:45] <jmkasunich> I'm only thinking of the lyx/emc2 directory
[20:30:58] <alex_joni> right.. that can go away for good (the whole dir)
[20:33:52] <alex_joni> hmmm.. how about EMC2_Code_Notes ?
[20:33:59] <alex_joni> we seem to have not touched that
[20:34:29] <alex_joni> * alex_joni adds it to emc2/docs/src as included into Master_Developer.lyx
[20:34:32] <alex_joni> how's that?
[20:34:47] <jmkasunich> ok
[20:35:30] <jmkasunich> the homing diagram embedded in there (actually the homing chapter) should be pulled out into a separate doc and included in the users or integrators manual
[20:35:31] <alex_joni> hmm.. we don't seem to have a topic that covers source code
[20:35:41] <alex_joni> it is in the users manual .. iirc
[20:35:50] <jmkasunich> oh, good
[20:36:08] <alex_joni> I think I moved it a while ago
[20:36:37] <alex_joni> yup: Chapter 7.4 Homing
[20:36:46] <jmkasunich> thanks
[20:36:57] <alex_joni> what name should I add for source ?
[20:37:11] <alex_joni> emc2/docs/src/code ?
[20:37:33] <jmkasunich> sure
[20:37:43] <alex_joni> or emc2-internals ?
[20:37:57] <alex_joni> or source ?
[20:38:03] <alex_joni> source-code ?
[20:40:29] <jmkasunich> I dunno
[20:40:42] <jmkasunich> * jmkasunich is trying to figure out how to set up a printer
[20:40:45] <alex_joni> * alex_joni chooses 'code'
[20:40:46] <jmkasunich> it hurts my brain
[20:41:02] <alex_joni> jmkasunich: ok, won't bother you suring that task.. I know it's a PITA
[20:41:27] <jmkasunich> the printer is a network device, I can access it with a browser and generate a test page
[20:41:40] <jmkasunich> but no clue how to actually print to it - googling now
[20:41:56] <jmkasunich> found a howto....
[20:41:58] <alex_joni> smbprint
[20:42:34] <jmkasunich> smb as in samba?
[20:44:32] <alex_joni> yeah..
[20:44:46] <alex_joni> I suspect that it exports a samba printer service..
[20:44:53] <alex_joni> but it might not be true
[20:45:48] <jmkasunich> it seems to export 6 services
[20:45:55] <jmkasunich> Configure Service
[20:45:55] <jmkasunich> Service NamePort Name
[20:45:55] <jmkasunich> BRN_846BE2_P1P1
[20:45:55] <jmkasunich> BINARY_P1P1
[20:45:55] <jmkasunich> TEXT_P1P1
[20:45:55] <jmkasunich> POSTSCRIPT_P1P1
[20:45:57] <jmkasunich> PCL_P1P1
[20:45:59] <jmkasunich> BRN_846BE2_P1_ATP1
[20:46:12] <alex_joni> I recognize PCL and Postscript from there
[20:46:28] <alex_joni> but those are types of the driver
[20:46:35] <alex_joni> Postscript should be the one you want
[20:47:05] <alex_joni> any linux program can output postscript (even if through gs)
[20:49:06] <jmkasunich> the trick is figuring out how to tell linux "theres a printer at 192.168.1.20"
[20:50:15] <jmkasunich> I opened the printers dialog, did "new printer", "network printer", "CUPS Printer (ipp)"
[20:50:20] <jmkasunich> and it wants a URI
[20:51:08] <jmkasunich> it works!
[20:51:22] <jmkasunich> the uri needs to be ipp://192.168.1.20
[20:51:39] <jmkasunich> I originally tried
http://, and then later ipp: but without the //
[20:51:54] <alex_joni> nice
[20:54:27] <jmkasunich> still has issues... tried to print a landscape drawing (pdf) and only got 2/3 of it
[20:55:49] <alex_joni> probably need to rotate it
[20:57:04] <jmkasunich> no, orientation is correct, just shifted off the page
[21:17:22] <alex_joni> jmkasunich: say when you have 5 minutes..
[21:17:36] <jmkasunich> now is as good as anytime
[21:18:01] <alex_joni> there were some hal_* documents still left in documents/lyx/emc2
[21:18:09] <alex_joni> I thought you moved those, but forgot to remove them
[21:18:20] <alex_joni> now I see they aren't in emc2/docs/ yet
[21:18:47] <jmkasunich> they might start with hal_, but they aren't part of the hal handbook
[21:18:50] <jmkasunich> they are emc specific
[21:18:54] <alex_joni> hal_halui.lyx , hal_motion.lyx ,
[21:18:58] <jmkasunich> (halui and the motion controller)
[21:19:03] <alex_joni> right.. both are emc2 specific
[21:19:17] <jmkasunich> hal handbook is not - and will remain that way
[21:19:34] <alex_joni> halui might fit in the GUI part of the manual, even if it's not fully a GUI but an UI
[21:19:37] <jmkasunich> those should probably be chapters in the EMC2 users manual? or integrators manual maybe
[21:19:47] <alex_joni> integrators sounds more like it
[21:19:50] <jmkasunich> yeah
[21:20:06] <alex_joni> but there's no such thing yet :/
[21:21:38] <alex_joni> is emc2/docs/src/hal only hal specific?
[21:21:54] <alex_joni> no emc2-related hal in there?
[21:22:00] <jmkasunich> I believe so
[21:22:19] <alex_joni> hmm.. maybe a hal-emc2 folder then?
[21:22:27] <alex_joni> for emc & hal specific info ?
[21:22:45] <jmkasunich> I haven't looked at halui and hal_motion.lyx
[21:22:53] <alex_joni> they only have a list of pins
[21:23:00] <alex_joni> and description what each does
[21:23:13] <alex_joni> but eventually we'll want to document these interfaces
[21:23:15] <jmkasunich> they are actually chapters about halui and the emc2 motion controller
[21:23:22] <jmkasunich> there is nothing "hal" about them
[21:23:36] <jmkasunich> listing the pins that something exports is just part of documenting that "something"
[21:23:55] <jmkasunich> I'd stick the docs whereever the "something" goes, not in some hal folder
[21:24:01] <jmkasunich> halui goes under gui
[21:24:02] <alex_joni> ok, so the motion.lyx should go to code/
[21:24:06] <alex_joni> and halui under gui/
[21:24:12] <jmkasunich> yes for halui
[21:24:16] <jmkasunich> not so sure about motion
[21:24:49] <jmkasunich> code/ is for stuff only developers care about - the actual internals
[21:24:58] <alex_joni> by reading the file, it describes the HAL pins for io and motion controller
[21:25:11] <jmkasunich> the motion controller is _not_ like that - it is an important part of EMC, and can be described in black-box terms
[21:25:34] <alex_joni> I agree.. but this is not what this file does
[21:25:42] <jmkasunich> yeah it does
[21:25:48] <alex_joni> it should be io&motion_pins.lyx
[21:25:56] <jmkasunich> maybe
[21:26:25] <alex_joni> it's not really documenting anything ..
[21:26:47] <alex_joni> nothing you wouldn't get out of halcmd show pin anyways
[21:27:00] <alex_joni> * alex_joni is tempted not to add it for now
[21:27:05] <jmkasunich> is it literally just a list of pins?
[21:27:11] <alex_joni> yes
[21:27:12] <jmkasunich> no details about them or anything?
[21:27:16] <alex_joni> without descriptions even
[21:27:21] <jmkasunich> then don't add it
[21:27:52] <jmkasunich> it doesn't provide any additional info beyond halcmd show pin, and it will get out of date
[21:27:54] <alex_joni> it just says which are pins and which params
[21:28:00] <alex_joni> but that's all of it
[21:28:15] <alex_joni> and it already is outdated (cause of the spindle moving to motion)
[21:28:19] <jmkasunich> if it had extra details, then the extra info makes the risk of it getting out of date worth taking
[21:28:22] <jmkasunich> dump it then
[21:28:42] <alex_joni> dumped
[21:33:04] <jmkasunich> gotta go, see you tomorrow
[21:35:11] <alex_joni> ok..