Back
[00:27:51] <DanielFalck> rayh: hi
[00:32:31] <rayh> Hi Dan
[00:32:49] <DanielFalck> Jim Triggs is coming out this way in February
[00:33:18] <DanielFalck> we should set up a CNC router for him sometime
[00:33:21] <rayh> Neat.
[00:33:31] <rayh> You making parts for him now?
[00:33:35] <DanielFalck> yep
[00:34:00] <DanielFalck> I pulled my old gantry router out of the corner last night
[00:34:11] <DanielFalck> time to set up another emc box
[00:34:12] <rayh> Ah.
[00:34:27] <DanielFalck> I'm playing with networking right now
[00:34:36] <rayh> I'm installing 6.06 on a mini itx right now
[00:34:36] <DanielFalck> ssh
[00:34:41] <DanielFalck> cool
[00:35:03] <rayh> ssh seems to work okay for me
[00:35:36] <DanielFalck> I set up an older computer in the garage with emc2 and have been ssh'ing into it
[00:35:44] <DanielFalck> from this desktop
[00:36:03] <DanielFalck> right now I'm playing with qemu a bit
[00:36:27] <DanielFalck> still have to use Autocad sometimes
[00:36:39] <DanielFalck> wine is getting better for that though
[00:36:50] <rayh> That's good to hear.
[00:37:06] <rayh> I've not tried wine at all.
[00:37:26] <DanielFalck> banished the last of my windows machines a while ago
[00:38:19] <rayh> wine is able to install autocad on a ext3 file system?
[00:38:29] <DanielFalck> yep
[00:38:38] <rayh> neat.
[00:38:42] <DanielFalck> rhino and vectorcam too
[00:38:52] <rayh> great.
[00:39:06] <rayh> Are you able to use all of vector?
[00:39:29] <DanielFalck> As far as I can tell, everything seems to work with vector now
[00:40:04] <rayh> you had problems with that a few years ago.
[00:40:11] <DanielFalck> yes
[00:40:28] <DanielFalck> seems good now
[00:40:42] <DanielFalck> I'm working on the desktop cam stuff a lot this week
[00:40:59] <rayh> nice.
[00:41:02] <DanielFalck> I have a 'Shuttle' pentium 4 box here, in the house
[00:41:10] <DanielFalck> pretty fast machine
[00:41:26] <DanielFalck> connected to an older 1.0 Gig Amd in the garage
[00:42:12] <DanielFalck> this machine (shuttle) really rocks
[00:42:20] <DanielFalck> 3.0 gig processor
[00:43:11] <DanielFalck> I am setting up ubuntu 6.0... on all the machines here
[00:43:20] <DanielFalck> with emc2 on the older slower boxes
[00:43:43] <rayh> That's about what I've done here.
[00:44:11] <DanielFalck> by the way, I know how to get the 'open in terminal' thing happening in Nautilus now
[00:44:17] <DanielFalck> had to install from synaptic
[00:44:21] <DanielFalck> ls
[00:44:25] <DanielFalck> sorry
[00:44:43] <DanielFalck> bbl
[00:56:16] <DanielFalck> back
[00:56:24] <DanielFalck> qemu is fun
[00:57:34] <fenn> fpga's are fun! so i hear.
[00:58:06] <DanielFalck> hi fenn!
[00:58:11] <fenn> hello!
[00:58:26] <fenn> what ever happened with that opencascade project?
[00:58:41] <DanielFalck> we put it on hold for now
[00:59:07] <DanielFalck> we are demoing UGS NX for linux/OS X at the moment
[00:59:47] <DanielFalck> but, it's still conceivable that we might use some opencascade code
[01:00:32] <DanielFalck> too many irons in the fire, as usual
[01:00:46] <rayh> DanielFalck: What was the package name that you added to nautilus to get the "0pen a terminal" ability?
[01:01:43] <DanielFalck> I think it was 'nautilus-open-in-terminal'
[01:01:49] <DanielFalck> I'll look no
[01:01:50] <DanielFalck> now
[01:02:37] <DanielFalck> nautilus-open-terminal
[01:03:13] <rayh> thanks
[01:03:40] <DanielFalck> once you're in the directory, right click
[01:12:19] <rayh> Hi roltek. Just got that mini-itx board running with ubuntu.
[01:21:36] <roltek> did you just pull it out of box
[01:22:08] <rayh> Yep. I've got one of those automotive cases.
[01:22:16] <roltek> what you use for a case for it ray
[01:22:29] <rayh> just used the back panel to mount it and a mini drive
[01:22:28] <roltek> the blue 1
[01:22:41] <rayh> Yep the blue one.
[01:22:53] <rayh> That case is made for the automotive power supply.
[01:22:57] <roltek> did you put a messa card in it
[01:23:05] <rayh> I used the tiny 12 volt direct plug in model
[01:23:09] <rayh> not yet.
[01:23:24] <roltek> do you think it will fit
[01:23:53] <rayh> I believe that I could add a mesa with a riser card and the mesa folded over the mobo
[01:23:58] <rayh> But I'll have to try that later.
[01:24:06] <roltek> neet
[01:24:33] <roltek> i was looking at them on the dsl site
[01:24:52] <roltek> about $75.00
[01:26:07] <rayh> Right. That's the one.
[01:27:13] <rayh> Nope. The two slot riser board is taller than the inside space in the blue box cover.
[01:28:06] <rayh> The top slot on the 2 slot riser will let the mesa fold over the mobo.
[01:28:43] <rayh> makes a really nice compact system that way.
[01:29:51] <roltek> chek your e-mail ray
[01:30:02] <rayh> 7"x7"x4"
[01:30:30] <rayh> That is all of it but the 12 volt dc supply.
[01:33:15] <rayh> gotta run.
[06:53:39] <aip_tom> aip_tom is now known as aip_tom1
[07:51:44] <aip_tom> aip_tom is now known as aip_tom1
[11:34:37] <lerneaen_hydra> 'lo
[12:14:14] <tomp> good morning
[13:34:47] <Bo^Dick> hi acemi
[13:35:04] <acemi> hi
[13:35:25] <Bo^Dick> i have a question for you
[13:35:31] <acemi> yes?
[13:35:32] <Bo^Dick> in this schematic,
http://www.kg-uitdaging.nl/COlabvoeding/CO%20labvoeding%20V2%20schema.pdf i'd like to know if the bottom rail in the picture is supposed to be below or above the ground level
[13:37:31] <acemi> i don't know
[13:52:44] <lerman> If, by bottom rail, you mean the lowest horizontal line, it is below ground level.
[13:53:15] <lerman> You can tell that because the positive side of C4 is connected to ground and the negative side is connected to that line.
[14:44:12] <etla> hi
[14:44:30] <lerneaen_hydra> 'lo
[14:47:15] <etla> I'm testing the new m5i20 configs Peter W sent me...
[15:05:34] <etla> so anyone know how I can replace the fpga config with a new one ??
[15:05:47] <etla> I now got the old one working OK
[15:08:29] <etla> anyone ??
[15:12:14] <etla> hi ray
[15:12:29] <rayh> what's up?
[15:12:52] <etla> I'm trying to test some new m5i20 configs peter wallace sent me
[15:13:06] <etla> but I haven't gotten very far
[15:13:08] <rayh> Ah. I saw that exchange.
[15:13:31] <etla> Jon E's amps want 50 kHz, so 50kHz it shall be
[15:13:43] <rayh> Okay.
[15:14:16] <rayh> Let me see if I understand your setup.
[15:14:21] <etla> do you know exactly what happens when I say 'loadrt hal_m5i20' ?
[15:14:25] <rayh> mesa card producing pwm
[15:14:32] <etla> I need to change the .bit file that is loaded to the fpga
[15:14:39] <rayh> pwm sent to pico amps
[15:14:41] <etla> yes, pwm from mesa card
[15:15:12] <rayh> Back in the old days, before PeteV produced the stock mesa install
[15:15:37] <rayh> We had to load the fpga code using a little linux script that mesa wrote up for me.
[15:16:37] <rayh> I really don't know how to change the current fpga load and mesa run.
[15:16:37] <etla> but is it done by the hal_m5i20 driver now ?
[15:16:42] <jepler> there is a program "m5i20_cfg" in bin/
[15:16:45] <jepler> er, no _
[15:17:24] <etla> but there's also the load_fpga switch when loading hal_m5i20 ?
[15:18:04] <rayh> This selection of the "desired" configuration of the anything io card is a topic that needs to be addressed.
[15:18:58] <jepler> etla: ah -- yes, that loads the firmware image specified at compile time, apparently in src/hal/drivers/m5i20_HM5-4E.h
[15:19:26] <etla> jepler: yes, looks like that...
[15:20:58] <jepler> I'm not sure what process transforms the .bit file into that header file
[15:21:04] <jepler> I don't think it's automatic
[15:21:50] <etla> the .bit file is binary, I get all kinds of funny characters with 'more xyz.bit'
[15:21:58] <jepler> yep me too
[15:22:50] <rayh> I see that there is an arg during startup that allows not to load the fpga.
[15:23:23] <rayh> halcmd loadrt hal_m5i20 [loadFpga=1|0] [dacRate=<rate>]
[15:23:33] <etla> exactly
[15:23:56] <etla> and loadFpga=1 presumably loads src/hal/drivers/m5i20_HM5-4E.h onto the fpga
[15:24:09] <etla> but that .h file is not in the same format as the new .bit files I got from Peter W
[15:24:18] <SWPadnos> nope
[15:24:43] <SWPadnos> there's a utility: src/hal/drivers/utils/m5i20cfg.c
[15:25:27] <SWPadnos> the bitfile converter is supposed to be in there as well, but it doesn't look like it is
[15:25:54] <SWPadnos> it's a pretty simple program to write: read in bytes as binary, output bytes as hex numbers separated by commas
[15:26:01] <etla> I don't even have a /utils on my HEAD checkout ??
[15:26:13] <SWPadnos> huh?
[15:26:24] <SWPadnos> src/hal/utils - sorry
[15:26:29] <etla> right.
[15:26:37] <rayh> bbiab
[15:26:47] <SWPadnos> right you don't have that one either, or right now you found it?
[15:26:51] <SWPadnos> see you Ray
[15:26:55] <etla> I now found it ;)
[15:26:58] <SWPadnos> ok :)
[15:27:18] <etla> is m5i20cfg.c compiled during the normal 'make' process ?
[15:27:33] <jepler> yes I think so
[15:27:36] <jepler> I have a bin/m5i20cfg program
[15:27:38] <SWPadnos> I'm not sure - I'm looking at the source on the web from Windows ;)
[15:28:11] <jepler> it looks like m5i20cfg HOSTM54E.BIT produces that .h file
[15:28:26] <SWPadnos> oh, ok. I thought it would actually load the bitfile onto the card
[15:28:30] <jepler> it can do that too
[15:28:32] <jepler> .. I think
[15:28:45] <SWPadnos> that's what it looked like the initial comment said ...
[15:29:49] <etla> it actually outputs to the screen a whole lot of hex numbers.
[15:29:50] <jepler> I think the card number is not really optional when using m5i20cfg to program the fpga
[15:30:01] <etla> the I get 'Successfully programmed xxx bytes'
[15:30:14] <etla> I wonder if it actually programs the card or just outputs the .h file to the screen
[15:30:25] <jepler> I believe that in that mode it outputs the .h to the screen
[15:30:39] <etla> so I'll pipe it to a file
[15:30:43] <jepler> give it a card number to actually program: m5i20cfg HOSTM54E.BIT 0
[15:30:49] <SWPadnos> it looks like there's an option (called PrintConfig in the source) for that
[15:31:36] <etla> m5i20cfg hostmot5_4eh.bit 0
[15:31:38] <etla> gives me an error 'Can't enable direct port access.
[15:31:38] <etla> '
[15:31:53] <jepler> may have to "sudo" since it directly accesses the hardware
[15:31:56] <SWPadnos> you probably need to run as root
[15:32:20] <etla> yep, now it looks like it worked.
[15:32:27] <SWPadnos> ok - if argc==2 PrintConfig = 1, so leaving off the card number will print the bytes to the screen
[15:32:29] <etla> Let's try with the highwer pwm rate... wait a bit
[15:33:36] <etla> hrmmm...
[15:33:52] <etla> now the Hz calculation when running the driver is probably way off
[15:34:06] <etla> previosly when you set 32000 it would turn out pretty close to 32kHz
[15:34:17] <etla> now when I put 50000 I get about 18kHz
[15:34:27] <SWPadnos> I thought the PWMs were fixed frequency
[15:34:44] <SWPadnos> config dependent, not parameter dependent
[15:34:46] <etla> you give hal_m5i20 an argument when you load it
[15:34:54] <SWPadnos> hmmm
[15:34:58] <etla> the config determines a master clock
[15:35:01] <SWPadnos> ah, ok
[15:35:03] <etla> 33MHz in the old ones
[15:35:08] <etla> now I have one with 100 MHz
[15:35:32] <etla> now I need a spreadsheet to calculate a bit...
[15:36:21] <SWPadnos> eyah - it's a 16-bit number, with the base clock as a constant
[15:36:36] <SWPadnos> pCard16->pwmRate = dacRate * 65536 / 1000 * 1024 / 33000;
[15:36:52] <etla> right.
[15:37:00] <SWPadnos> if you want 50000, I bet you need to ask for 50000/3, or 16666
[15:37:03] <etla> but I have 100MHz instead of 33
[15:38:49] <SWPadnos> right, so all other things being equal, you should get a PWM rate that's 3x what you ask for
[15:38:55] <SWPadnos> 100/33
[15:39:10] <etla> ok, I'll try that
[15:39:26] <etla> asking for 50000 was probably too much, as about 97kHz is max with a 100MHz clock
[15:41:09] <etla> hmm... what's the default behaviour for loadfpga ? I may just have overwritten my new config...
[15:41:36] <SWPadnos> default is 1 :(
[15:42:50] <etla> Yes! now it works, I measure 50.25kHz on the scope
[15:42:53] <etla> great!
[15:42:58] <SWPadnos> cool
[15:43:24] <etla> the process of loading different configs probably should be made a bit easier if people want to use them in the future
[15:43:26] <SWPadnos> I guess ytou need 16583 then :)
[15:43:48] <SWPadnos> well, loadfpga=1 makes sense, since a driver will likely not work with the wrong firmware
[15:44:23] <etla> the driver would also need some work to support the 8-axis cofig which is available
[15:45:03] <SWPadnos> yep - it could auto-detect what's there, and barf if the wrong ID is found (or any non-supported ID)
[15:45:18] <etla> maybe I should check if I can still do cvs update ? anyone know where the scratch.txt is for testing ?
[15:45:20] <SWPadnos> it's probably better to do that, and have loadfpga=0 by default
[15:45:36] <etla> er... cvs commit I mean
[15:45:51] <SWPadnos> I think you're on the list - you got the mesa email, right>
[15:45:52] <SWPadnos> ?
[15:45:59] <etla> yes
[15:46:22] <SWPadnos> ok. that was generated from the list of people with commit access, plus a few others
[15:47:34] <etla> so would you say it's OK to commit these to HEAD even though they are not tested and loading them is a bit tricky
[15:48:03] <SWPadnos> good question. Peter sent me a copy as well, but I haven't wanted to commit without being able to test
[15:48:44] <SWPadnos> I also have the update that fixes the index pin error, but again, I couldn't regenerate the bitfile from source, and I couldn't verify the changed behavior ...
[15:48:54] <etla> the change from 33MHz to 100MHz seems to be working
[15:49:05] <SWPadnos> other than all the time scales being off :)
[15:49:10] <etla> what was the index pin error ?
[15:49:24] <jepler> I would prefer to see anything committed to CVS to be buildable from source with the xilinx tools
[15:49:42] <etla> Peter W sent the sources for everything also I think
[15:49:47] <SWPadnos> actually, I Think it was the secondary indexes
[15:49:48] <jepler> oh good
[15:49:49] <etla> at least there are a lot of .vhd files
[15:50:02] <etla> yes, the secondary encoders were all over the place
[15:50:03] <SWPadnos> he sent the sources, but I'm not sure anyone has actually generated an identical bitfile
[15:50:11] <etla> or I mean they are, in the current config
[15:50:17] <SWPadnos> or a provably equivalent one
[15:50:35] <SWPadnos> probably not in the 100MHz config you have
[15:51:10] <etla> yes, Peter wrote that he fixed the secondary encoders a long time ago, so they are probably OK in all the new configs
[15:51:30] <etla> I'll try committing them and see what happens :)
[15:51:39] <SWPadnos> heh
[15:52:01] <SWPadnos> make sure you regenerate m5i20cfg.h (or whatever it is) from the HOSTMOT5-4E bitfile
[15:52:26] <SWPadnos> m5i20.h, that is
[15:52:43] <SWPadnos> oops - m5i20_HM5-4E.h :)
[15:53:08] <etla> I think I won't mess with the current config, just add the new ones to cvs so they are available for all
[15:53:30] <SWPadnos> I wonder if separate dirs are warranted?
[15:53:45] <etla> probably a good idea
[15:54:02] <etla> I have four new .bit files
[15:54:06] <SWPadnos> but impossible to remove, so I'd make sure someone other than me agrees :)
[15:54:15] <etla> huh? impossible to remove ?
[15:54:25] <SWPadnos> directories from CVS
[15:54:31] <etla> how come
[15:54:48] <SWPadnos> though I guess jepler or cradek can just delete them from the repository
[15:55:07] <SWPadnos> CVS keeps the dirs around even if you delete all files and the dir, because you have to be able to check out a previous version
[15:55:39] <SWPadnos> (which contains it)
[15:57:40] <SWPadnos> ah, ok. the primary index inputs are on the B connector instead of A, and the secondary inputs are kind of interleaved instead of on separate 4-bit blocks (due to a set of typos)
[15:58:41] <SWPadnos> hmmm - that would be a problem for replacing the "standard" 4-axis config, since anyone who has a machinewould need to rewire their index mask inputs (if used)
[15:59:53] <SWPadnos> hmmm - I'll have to look at that a bit more, later.
[15:59:56] <SWPadnos> bbl
[16:00:00] <etla> later
[16:03:47] <etla> so how does cvs commit work anyway ??
[16:06:41] <jepler> you add or edit your files, then "cvs commit", verify it's the list of files you expected to be added or modified, then enter a message explaining the purpose of your changes.
[16:07:59] <etla> I get:
[16:08:04] <etla> cvs [commit aborted]: could not open lock file `/cvs/emc2/,TODO,': Permission denied
[16:08:35] <jepler> is this a developer checkout or an anonymous checkout?
[16:08:56] <aip_tom1> aip_tom1 is now known as aip_tom
[16:08:59] <etla> ah, there is a difference ?
[16:09:03] <jepler> "Permission denied" messages typically indicate that you have an anonymous checkout
[16:09:18] <jepler> cat CVS/Root
[16:09:22] <etla> OK, I see, I probably need a developer checkout
[16:09:37] <etla> yep, anon@...
[16:09:41] <jepler> anon(ymous) can check out files, only developers can check in new files
[16:10:42] <jepler> have you gotten a developer release before on the machine you're using right now?
[16:10:47] <jepler> er, a developer checkout
[16:11:06] <etla> yes, I think so, I modified some docs earlier
[16:12:18] <etla> now it asks for a password, should it do that ?
[16:12:32] <jepler> no, only use of SSH keys is permitted
[16:13:09] <etla> does the username need to be the same as my unix username ?
[16:13:23] <etla> I'm logged in as 'etla' on this machine
[16:13:28] <jepler> it has to be whatever username chris used when he set up the CVS server
[16:13:37] <etla> but I think my emc developer username was 'awallin'
[16:14:00] <jepler> then you'd use :ext:
[email protected]/cvs
[16:14:51] <etla> that gives me the password prompt
[16:16:11] <jepler> you may have to wait until chris is around, he'll be able to help you
[16:16:23] <jepler> cradek: ^^^
[16:16:48] <etla> OK
[16:16:53] <tomp> the cnc_toolkit group have spawned some 5 axis hardware (A , B&C)
http://www.doughtydrive.com/
[16:17:55] <jepler> interesting
[16:18:28] <jepler> looks like the wiring for the spindle would be a challenge
[16:20:17] <etla> jepler: what do you think about doing VCP type stuff with Python ?
[16:21:23] <jepler> etla: I think python might be a good language for it, and if we have competing GUIs then why not competing VCPs?
[16:22:03] <jepler> I don't need a VCP personally so I haven't really done any work on it
[16:22:13] <etla> OK. I'm just a bit frustrated by the lack of widgets currently in VCP. I can fairly easily do better with Python and TkInter
[16:22:30] <etla> But I don't have the skills to write a parser for a .vcp file
[16:22:46] <etla> so anything I write would be pretty specialized for my machine only
[16:23:12] <jepler> I'm not sure whether compatability with .vcp files is important
[16:23:19] <jepler> there are not a whole ton of them out there yet
[16:23:21] <etla> but maybe it can be cleaned up later if it's useful
[16:23:23] <etla> nope ;)
[16:23:45] <jepler> if you come up with something flexible in python+tkinter I will be interested in integrating it with axis
[16:24:04] <etla> sounds good. I'll see what I can come up with.
[16:24:08] <jepler> so that they can appear in the same window -- placing the vcp widgets on a new pane on the right side, for instance
[16:24:27] <etla> Now that I have the vmware thing on my laptop I don't have to sit at the cnc mill when developing
[16:24:47] <jepler> linux or windows as the host OS?
[16:24:50] <etla> winXP
[16:25:29] <etla> it even runs the RT kernel, no need to do any special sim or non-RT tricks
[16:25:47] <jepler> I use ubuntu and --enable-simulator on my laptop
[16:25:57] <jepler> and have XP inside vmware for the rare occasions it's useful
[16:26:07] <jepler> actually while working on pluto-p it's been a necessity
[16:26:26] <etla> what's pluto-p ?
[16:27:02] <skunkworks> jepler: you have xp running within ubuntu?
[16:27:18] <jepler> it's a parallel-port FPGA board.
[16:27:56] <jepler> about the board:
http://www.fpga4fun.com/board_pluto-P.html what I've been doing with it:
http://cvs.linuxcnc.org/cgi-bin/cvsweb.cgi/emc2/docs/src/hal/pluto_servo.html?rev=HEAD;content-type=text%2Fplain
[16:29:47] <etla> can you remind me how I generate the ssh key files that I need to send to chris ?
[16:30:25] <jepler> ssh-keygen -t rsa
[16:30:44] <jepler> then you send the ~/.ssh/id_rsa.pub file to chris
[16:31:11] <etla> passphrase ?
[16:31:27] <jepler> you can leave that blank if you like
[16:32:43] <etla> can these keys be used on many machines ? or just the one their generated on ?
[16:32:57] <jepler> you can use the same identity on multiple machines by copying .ssh/id_rsa to the other machine
[16:33:54] <etla> thanks.
[16:34:39] <tomp> etla: pygtk and/or pyqt have the widgets you need? ( i made analog vscale for VCP, like a slide pot that ties to an analog output, maybe thats useful )
[16:37:46] <etla> tomp: I have not looked at pygtk/qt. are they included in the default emc2-dev packages ?
[16:37:55] <jepler> no they are not
[16:40:43] <etla> so it might be a good idea to use only tkinter, since it's there by default
[16:40:51] <tomp> they have lotsa widgets & interface to python, allowing interpreted consoles that connect to HAL. I've made some simple things work for the STG2.
[16:41:42] <tomp> if std toolbox is important, then just use tk tcl tkinter python & c ;)
[16:42:39] <jepler> it looks like python2.4-gtk2 is part of the base installation of ubuntu, so it's not an extra requirement for most users
[16:42:56] <jepler> but only python+tkinter will integrate with axis -- so consider that when deciding
[16:44:34] <tomp> jepler: i gotta study the new links you provided this morning to cadcamdro, like 'jdi', thanks
[16:45:01] <wb9mjn> I have a 100 mm slide pot in my junk box....
[16:45:10] <wb9mjn> 10 KOhm...
[16:47:21] <wb9mjn> .15 % linearity....made in Switzerland...
[16:48:34] <wb9mjn> That is an acuracy of +/- .006 inches across the 100 mm ...
[16:49:02] <rayh> The m5i20 manual says that there is C code in the zip file that can be compiled under Linux.
[16:49:58] <rayh> in fact there is a /UTILS/LINUX/ directory with the code in there.
[16:50:23] <tomp> to test the board or realtime ?
[16:50:48] <rayh> To upload a bit file to the fpga.
[16:51:06] <rayh> In fact mesa compiled that into an executable in that directory.
[16:51:10] <tomp> utils for etla :)
[16:51:17] <rayh> yep.
[16:53:23] <etla> rayh: I got that sorted out already. the utility comes with emc2
[16:53:42] <etla> the new config works fine, I get 50kHz PWM
[16:53:48] <rayh> I saw that from your post.
[16:54:15] <rayh> I will answer that post with a couple of questions.
[16:54:30] <etla> OK
[16:54:36] <rayh> What should happen if I have more than one m5i20 aboard?
[16:54:45] <etla> wb9mjn: are you sure that linearity == resolution
[16:55:22] <etla> we probably need a new parameter <boardnr>
[16:55:33] <etla> all the HAL pins have the stupid zero there anyway !
[16:55:35] <rayh> What procedure should be added to the loader to assign specific configs to specific boards?
[16:55:52] <rayh> Yes they do.
[16:56:34] <rayh> [board1=xxy board2=xyy]?
[16:57:02] <etla> can you load hal_m5i20 only once ?
[16:57:14] <rayh> The reason I ask is that I've got a 2 board controller in process.
[16:57:32] <rayh> I'd think that if you tried it twice it would say it's already loaded.
[16:57:33] <etla> for the mazak ?
[16:57:53] <rayh> The mazak would be an excellent example of a two board solution.
[16:58:12] <rayh> we used an older ISA card along with the motenc
[16:58:54] <etla> the pwm rate could probably be made into a parameter ?
[16:59:02] <etla> instead of being specified when loading the driver
[16:59:49] <wb9mjn> Yep....just like an encoder, only linear....
[17:00:51] <wb9mjn> Its a linear pot...has a rod that goes back and forth to operate the wiper contact....
[17:01:19] <etla> wb9mjn: but I'm not sure that a good linearity means equally good resolution/hysteresis etc.
[17:01:47] <wb9mjn> .006 is not great resolution...
[17:02:04] <wb9mjn> So, I think yes...its probably that accurate...
[17:02:18] <wb9mjn> Probably near the practical limit for linear pots....
[17:03:06] <wb9mjn> If the wiper is connected on two ends, with the center contacting the resistive element, hysteresis would be
[17:03:09] <wb9mjn> very small....
[17:03:27] <wb9mjn> Connections on ends of wiper inline with motion...
[17:03:29] <etla> so do you have any practical use for it ?
[17:03:46] <wb9mjn> Nope....came out of something I scrapped, do not even remember what....
[17:04:34] <wb9mjn> Probably a printer....
[17:04:34] <wb9mjn> old...
[17:04:54] <wb9mjn> although 4 inches is too short for a printer....
[17:05:42] <wb9mjn> Did not read the whole thread there, and the pot was in a can on the desk here.....
[17:05:52] <wb9mjn> Put two and two together and got 3...hi...
[17:06:14] <wb9mjn> They were talking about virtual basic er software on-screen operators....
[17:08:37] <etla> gotta go now, I'll be back later.
[18:25:13] <awallin> still no luck with cvs...
[18:33:33] <cradek> hmm
[18:38:13] <cradek> looks like I did get your key in there right, I just checked
[18:39:27] <cradek> nope, my screwup, try again
[18:41:18] <awallin> yes! thanks, now the dev checkout works.
[18:41:36] <cradek> yay
[18:41:37] <cradek> sorry
[18:48:08] <awallin> hmmm, how do I create a new directory with cvs ?
[18:54:35] <CIA-8> 03awallin 07HEAD * 10emc2/src/hal/drivers/m5i20/hostmot5_4/hostmot5_4.bit: this is the bugfixed hostmot-4 with 33MHz pwm clock
[18:55:33] <CIA-8> 03awallin 07HEAD * 10emc2/src/hal/drivers/m5i20/hostmot5_4/REGMAP4E: register map for hostmot-4
[18:55:36] <lerman> cradek: I need developer privs. What do I need to send you and where should I send it?
[18:57:10] <awallin> lerman: you need to create an ssh key pair
[18:57:23] <awallin> ssh-keygen -t rsa
[18:57:25] <awallin> I think
[18:57:32] <awallin> then you email the .pub to chris
[18:57:53] <lerman> I saw the message telling you to do that. OK. I need an email for chris.
[18:58:43] <awallin> chris at timeguy dot com
[18:59:11] <lerman> thanks.
[19:00:34] <CIA-8> 03awallin 07HEAD * 10emc2/src/hal/drivers/m5i20/hostmot5_4eh/hostmot5_4eh.bit: this is the new hostmot-4 config with 100MHz pwm clock
[19:03:28] <lerman> OK. That's been sent off to cradek.
[19:03:49] <CIA-8> 03awallin 07HEAD * 10emc2/src/hal/drivers/m5i20/hostmot5_8/hostmot5_8.bit: new 8-axis hostmot-8 with 33MHz pwm clock
[19:05:18] <lerman> awallin: I gather that you're in about the same position as I am. I checked out some stuff as anon, I've modified it, and now want to commit it back. Can I just do that from the directory I started with (the anon one)? Or am I going to have to create a new release, put in the same mods, and then commit that?
[19:06:44] <CIA-8> 03awallin 07HEAD * 10emc2/src/hal/drivers/m5i20/hostmot5_8eh/hostmot5_8eh.bit: 8-axis hostmot-8 with 100 MHz pwm clock
[19:13:10] <CIA-8> 03awallin 07HEAD * 10emc2/src/hal/drivers/m5i20/hostmot5_src/ (33 files): these are the vhdl source files for the hostmot-4 and hostmot-8 fpga configs
[19:19:55] <CIA-8> 03awallin 07HEAD * 10emc2/src/hal/drivers/m5i20/README.txt: info about the different configs and how to use them
[19:20:30] <awallin> lerman: you can only commit from a devel checkout
[19:20:46] <awallin> so you need to do a new checkout with <username>@cvs.linuxcnc.....
[19:20:50] <awallin> and then commit from there
[19:21:18] <awallin> you can probably do a diff/patch between your anon and devel checkouts to save some manual typing
[19:22:26] <awallin> anyone know where a more detailed TODO list is kept ? or should I just add stuff to /src/TODO
[19:22:50] <lerman> But can I fool cvs by changing the CVS/Root file? Since all of my changes are in a single directory, I should be able to just copy the Root file from the new one to the anon one and then check in my files.
[19:24:55] <SWPadnos_> copy the modified files into the non-anonymous checkout dir
[19:25:20] <SWPadnos_> SWPadnos_ is now known as SWPadnos
[19:26:11] <lerman> Yes. But I have to do those one at a time.... Can you say lazy? And I have to know which were modified (yes cvs diff).
[19:26:42] <SWPadnos> your mods should be only in the rs2764ngc dir, right? (or at least most of them)
[19:26:47] <SWPadnos> -6
[19:26:58] <lerman> Correct.
[19:27:03] <jepler> awallin: whee, thanks for your work on this mesa stuff
[19:28:01] <SWPadnos> copying the CVS/ dir is equivalent to copying the files, either is a little dangerous if you didn't start from a fresh checkout
[19:30:17] <goslowjimbo> Not sure what the correct etiquette is here. Can anyone jump in with their "opportunities", or is that impolite?
[19:30:33] <lerman> I've got a version with name parameters ready to commit.
[19:30:38] <SWPadnos> it's not impolite
[19:30:46] <CIA-8> 03awallin 07HEAD * 10emc2/src/hal/drivers/m5i20/README.txt: further info on m5i20 configs
[19:31:10] <SWPadnos> cvs ci <list of filenames>
[19:31:17] <lerman> We all talk at once on many topics. It's not impolite, but you may get ignored by people who are thinking about something else.
[19:31:32] <lerman> Is it cvs ci or cvs commit?
[19:31:45] <SWPadnos> when the editor pops up, enter a nice descriptive comment (use several lines if you need to), and save the file
[19:31:54] <SWPadnos> ci is the same as commit, I think
[19:31:55] <SWPadnos> checkin or commit
[19:31:59] <SWPadnos> ci = checkin
[19:32:01] <awallin> jepler: thanks for noticing! I don't have much time for emc now but I try to do something...
[19:32:02] <lerman> I need to get back on the developers list.
[19:32:07] <SWPadnos> (like co=checkout)
[19:32:18] <SWPadnos> ok - time to run again
[19:32:20] <lerman> Shades of RCS.
[19:32:23] <SWPadnos> bbl
[19:32:28] <lerman> cu.
[19:32:34] <SWPadnos> CVS = RCS, for very small values of CVS ;)
[19:32:49] <lerman> Yes.
[19:33:49] <goslowjimbo> I am having "opportunities" with setting a thread in HAL. Sometimes it will accept the following command, and sometimes it will come back with a illegal character error msg.
[19:35:36] <lerman> gsj: sorry I can't help. I run emc1 on my real hardware and my only emc2 experience is with simulation.
[19:35:50] <goslowjimbo> "halcmd loadrt threads name1=base-thread fp1=0 period1=50000 \ name2=servo-thread period2=1000000"
[19:37:02] <lerman> Does it tell you what character it is? Or the position on the line? Or anything useful?
[19:37:41] <awallin> what's the backslash ('\') for ?
[19:38:56] <lerman> I assume to split the line. Are you using the '\' in the command you are giving? Is that the problem?
[19:39:24] <goslowjimbo> No, just that is has encountered an illegal character. I've tried the -v and -V options, but it didn't change anything. I don't know what the backslash is for. It is just like the one shown in the EMC2 user manual.
[19:40:35] <lerman> That is probably the problem. Type the whole thing on one line without the '\'. That was probably in there because the command wouldn't fit on one line in the manual.
[19:41:25] <goslowjimbo> OH, I thought it might be a delineater between the definitions of the 2 threads.
[19:41:35] <jepler> goslowjimbo: do it all on one line without the \
[19:43:29] <jepler> In Unix commandline shells, \ as the last character on a line means the command continues on the next line -- but it's often best just to take the simple approach and write it all on one line
[19:44:13] <jepler> also, "fpX=0" or "fpX=1" will not work if you are using emc 2.0.x, that was added later but somehow crept into the 2.0.x documentation
[19:45:51] <awallin> what does fp do ??
[19:46:09] <jepler> awallin: it specifies whether that thread can use floating-point calculations or not
[19:46:33] <jepler> you can specify 'fp1=0' to turn off floating point for that thread, and maybe make it take a microsecond less to execute
[19:47:07] <CIA-8> 03awallin 07HEAD * 10emc2/TODO: added hal_m5i20 driver to-do list
[19:47:42] <awallin> OK, so then you can't hook up any floating point signals/operations or anything to that thread ?
[19:47:58] <goslowjimbo> how do you eliminate the floating point for emc 2.0.x?
[19:50:34] <jepler> goslowjimbo: leave fp1= and fp2= off the loadrt line and don't worry about it
[19:51:03] <goslowjimbo> OK. Thanks
[19:51:07] <jepler> awallin: each function must specify whether it uses FP or not. If it says it uses FP it can't be put in a no-fp thread
[19:51:37] <jepler> awallin: if the thread really does use FP, but says it doesn't, and you add it, you get an error in your system log and emc stops working until you restart it
[20:03:53] <SWPadnos_> SWPadnos_ is now known as SWPadnos
[20:20:27] <awallin> jepler: are you still there ?
[20:22:12] <awallin> I am wondering about the 3D view in AXIS
[20:22:56] <awallin> It's done in OpenGL ? but are you using some kind of toolkit on top of OpenGL ? or are you just using the standard OpenGL commands to draw everything ?
[20:23:18] <awallin> is it fast enough when implemented in Python, or is it written in some faster language ?
[20:30:00] <jepler> awallin: I use my own wrapper of opengl
[20:30:48] <jepler> awallin: drawing the preview plot is just one OpenGL call: glDrawList or something like that
[20:31:14] <awallin> ok
[20:31:16] <jepler> some other parts of the drawing are done in C
[20:31:22] <jepler> it has evolved over time
[20:32:16] <awallin> I'd just like to have something which can plot stuff (lines in 3D mostly)
[20:32:38] <awallin> but there are a lot of advanced toolkits around, I'm wondering if they are worth it
[20:32:49] <awallin> or if I should just stick to plain openGL
[20:32:56] <jepler> one of the "must have"s for AXIS was working within a Tk application
[20:32:59] <huggyb> Hi, I am having trouble configuring EMC to run python scripts
[20:35:34] <jepler> huggyb: the stuff described in "Program Filters" in the online manual (e.g.,
http://linuxcnc.org/docs/devel/html/gui/axis/) wis a new feature that will be in emc2.1, but isn't in emc 2.0.x.
[20:36:01] <jepler> huggyb: so if that's what you're trying to do, that's probably why it's not working. but if you're using the development version, or that's not what you meant, I'll try to help you out.
[20:36:48] <jepler> in emc 2.0.5/axis 1.4a0, a much more limited "filter" was supported -- it wasn't very useful, really
[20:36:49] <huggyb> That explains it. I have the ubuntu sruff installed
[20:37:39] <huggyb> Maybe I should try the development build, thank you.
[20:38:05] <jepler> you can compile the development version yourself -- instructions are on our wiki
[20:38:20] <jepler> there isn't a prepackaged version yet
[20:39:46] <huggyb> are you looking for developers?
[20:40:27] <jepler> yes -- It would be crazy to turn down a developer!
[20:40:58] <huggyb> that's because you don't know me ;-)
[20:42:17] <jepler> do you have some ideas about what you'd like to change/improve in emc2?
[20:44:07] <huggyb> Not really... I'm a simple C++/Java guy that got a sherline mill for xmas
[20:44:47] <huggyb> I want to learn python doing wizards and other gcode generation stuff
[20:45:36] <jepler> good
[20:46:11] <jepler> are you familiar with stuff like CVS then?
[20:46:27] <huggyb> sure
[20:46:49] <jepler> read around on this page:
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Installing_EMC2#Getting_the_source_with_CVS
[20:47:01] <huggyb> ok
[20:47:09] <jepler> actually you should start at the top of section 3
[20:48:05] <jepler> once you've compiled the CVS version (either v2_1_branch or HEAD) you'll be able to use [FILTER] stuff like the manual shows
[20:48:29] <huggyb> great
[20:48:54] <jepler> I'll be in and out this afternoon, but if you get stuck just ask for help again
[20:49:05] <huggyb> thanks...
[20:49:30] <lerneaen_hydra> lerneaen_hydra is now known as Lerneaen_Hydra
[20:50:13] <Lerneaen_Hydra> logger_emc: bookmark
[20:50:15] <Lerneaen_Hydra> Just this once .. here's the log:
http://www.linuxcnc.org/irc/irc.freenode.net:6667/emc/2006-12-30.txt
[20:50:56] <Lerneaen_Hydra> Lerneaen_Hydra is now known as lerneaen_hydra
[21:20:13] <aip_tom> off to Slab City for new year's.. see ya alls
[21:21:08] <skunkworks> making some brandy slush right now..
[21:25:34] <Jymmmm> what a waste of brandy =)
[21:26:15] <Jymmmm> skunkworks: 500cc of Brandy IV Push =)
[21:26:25] <skunkworks> :)
[21:27:50] <Jymmmm> Jymmmm is now known as Jymmm
[21:43:32] <Jymmm> If anyone has any ideas... My Sony TV no longer has color on the tuner or video inputs, but does have color on the OSD. I cracked the back cover on it, but I didn't see any loose connectors. Any Ideas?
[21:48:55] <skunkworks> odd
[21:48:59] <skunkworks> no clue - sorry
[21:56:27] <skunkworks> subject of email - At warm in voltmeter
[21:57:06] <skunkworks> first line of emal - You got this message, so you lucky man. It is your chance!!
[21:57:19] <skunkworks> just odd..
[21:57:22] <skunkworks> random
[22:03:28] <Jymmm> I'd try to reseat the modular boards, but not sure how to safely discharge the flyback
[22:03:38] <lerman> Anyone seen cradek recently? I need to get added to the cvs developers list. I did send him email.
[22:04:25] <lerman> I just wrote a test program for my changes. It 'mills' a flowsnake.
[22:04:31] <Jymmm> "Just say no to cradek!"
[22:04:55] <lerman> (And hope he doesn't say no to me.)
[22:05:10] <skunkworks> fowsnake?
[22:05:19] <skunkworks> flowsnake?
[22:05:22] <lerman> I'm on a roll. I'd like to get those changes in, so I can add some more.
[22:06:25] <lerman> http://www.meden.demon.co.uk/Fractals/flowsnake.html ...
[22:07:05] <lerman> It is the first gcode I've written that uses recursion. It's fun -- if not very useful.
[22:07:49] <skunkworks> cool
[22:11:47] <lerman> Anyone know if there is a packgage to install Qt on ubuntu using apt-get? and what the name might be?
[22:14:05] <cradek> apt-cache search libqt
[22:14:28] <lerneaen_hydra> I just couldn't resist:
http://lerneaenhydra.shacknet.nu/index.php?option=com_rsgallery2&Itemid=32&page=inline&id=16&catid=3&limitstart=0
[22:15:33] <lerman> cradek: did you get the email with my ssh public key? I'm hot to get my tuff out there.
[22:15:34] <cradek> lerneaen_hydra: I thought you already had commit access, but I see now you don't
[22:15:47] <cradek> I'll do it now, one sec
[22:15:54] <lerneaen_hydra> cradek: I take it you mean lerman ?
[22:16:33] <lerman> I used to. With a password. That was before the change to ssh.
[22:18:51] <cradek> oops, yes, lerman
[22:19:04] <lerneaen_hydra> hmm, link should be working now
[22:19:07] <cradek> l[tab] gives me one of you two at random :-)
[22:19:26] <cradek> lerman: give it a shot now
[22:20:17] <cradek> looks like it works
[22:20:40] <lerneaen_hydra> whee
[22:21:13] <lerman> Yeah. It's doing something.
[22:21:42] <huggyb> I am trying to get the torus png sample working on my machine but I get an "Exit code 1" when I load the file. Can anyone help? I just compiled the latest emc from cvs.
[22:22:43] <cradek> did you try it with the sim/axis configuration?
[22:23:04] <huggyb> yes
[22:23:23] <cradek> do you get the image-to-gcode window where you can configure the settings?
[22:23:39] <huggyb> not even
[22:24:01] <cradek> any errors on stdout/stderr?
[22:24:11] <huggyb> I can get holecircle.py to work
[22:24:35] <huggyb> I get "No module named numarray"
[22:24:39] <cradek> oh :-)
[22:24:40] <lerman> Is HEAD the default when I co? If not, what do I do to get HEAD?
[22:24:43] <cradek> you should install numarray
[22:24:46] <cradek> lerman: yes
[22:24:58] <lerman> thanks
[22:25:03] <cradek> huggyb: sudo apt-get install python2.4-numarray
[22:25:09] <huggyb> ok
[22:26:02] <cradek> lerman: funny photo!
[22:26:16] <lerman> Which one?
[22:26:44] <cradek> arrgh
[22:26:52] <huggyb> I also need ImageTk... do you know the full package name?
[22:26:53] <cradek> lerneaen_hydra: funny photo!
[22:27:05] <cradek> python2.4-imaging-tk
[22:27:13] <lerneaen_hydra> cradek: the wonderous days of highschool ;)
[22:27:52] <huggyb> Its working now, thanks :-)
[22:28:35] <cradek> huggyb: I still haven't used that to mill anything - let us know how it works if you do
[22:29:16] <huggyb> When I use any of the python scripts, how can I save the gcode? cut & paste don't seem to work from the console
[22:29:49] <cradek> you can run the python program at the shell and redirect its output to a file
[22:30:49] <huggyb> great. This is cool stuff, by the way
[22:31:54] <cradek> glad to hear that
[22:35:27] <Bo^Dick> guys, i have a question...
[22:35:43] <Bo^Dick> about this powersupply design,
http://www.kg-uitdaging.nl/COlabvoeding/CO%20labvoeding%20V2%20schema.pdf
[22:37:05] <cradek> Bo^Dick: might be better to ask on #electronics
[22:40:06] <Bo^Dick> prolly
[22:41:35] <goslowjimbo> Does anyone know what the ground pins are on a parrallel port? The halscope says I'm not getting into the computer, but I'm driving it with a encoder. The ground pin is the only other thing I can think of.
[22:42:22] <cradek> goslowjimbo:
http://www.google.com/search?q=parallel+port+pinout
[23:03:08] <lerneaen_hydra> hmm, interesting
[23:03:28] <lerneaen_hydra> within minutes of me uploading images to my site there are hits on the images O.o
[23:03:42] <cradek> lerneaen_hydra: I'm reading your webpage - I didn't know you got two of those lathes, and for free, that's very cool
[23:04:00] <lerneaen_hydra> cradek: oh, that explains a bit
[23:04:04] <cradek> they're pretty good, aren't they? ballscrews?
[23:04:08] <lerneaen_hydra> cradek: yes, I really lucked out
[23:04:17] <lerneaen_hydra> cradek: they are ballscrewed, yes
[23:04:30] <cradek> very nice find
[23:04:31] <lerneaen_hydra> yeah
[23:04:47] <lerneaen_hydra> how's the latency of the site?
[23:04:50] <lerneaen_hydra> acceptable?
[23:04:53] <cradek> it seems fine
[23:05:17] <lerneaen_hydra> great
[23:05:36] <lerneaen_hydra> (it's just hosted on a computer at home)
[23:05:37] <cradek> The requested URL /images/files_projects/compact5/img_5238.jpg was not found on this server.
[23:05:51] <cradek> I think all the emco images are broken
[23:06:29] <lerneaen_hydra> hmm
[23:06:29] <lerneaen_hydra> oh
[23:06:30] <lerneaen_hydra> right
[23:06:35] <lerneaen_hydra> I just moved them over to the gallery
[23:06:42] <lerneaen_hydra> haven't fixed the article yet
[23:06:49] <cradek> ah
[23:07:36] <cradek> did you ever get threading on that lathe?
[23:07:42] <cradek> I remember it had the sensor already
[23:07:55] <lerneaen_hydra> the article should be fixed now
[23:08:00] <lerneaen_hydra> yeah, threading works now
[23:08:08] <lerneaen_hydra> quite well actually :)
[23:08:12] <cradek> cool
[23:08:15] <cradek> using the counter module?
[23:08:23] <lerneaen_hydra> yeah
[23:08:25] <cradek> you should make a new video :-)
[23:08:32] <lerneaen_hydra> ooh, that would be nice
[23:08:44] <lerneaen_hydra> I'll have to do that soon
[23:08:52] <lerneaen_hydra> then I can add a video to the gallery too :)
[23:09:29] <cradek> neat
[23:09:39] <cradek> hmm your AXIS is not in lathe mode
[23:09:40] <fenn> nice bathtub
[23:09:58] <cradek> or maybe the photo is old (before there was a lathe mode)
[23:10:29] <cradek> forget it - the next photo is
[23:10:28] <lerneaen_hydra> yeah, that's an old image
[23:10:28] <CIA-8> 03lerman 07HEAD * 10emc2/nc_files/flowsnake.ngc: Add a sample program using named parameters.
[23:10:34] <lerneaen_hydra> yep
[23:11:14] <cradek> http://lerneaenhydra.shacknet.nu/images/rsgallery/original/img_5398.jpg
[23:11:16] <cradek> much better
[23:12:15] <lerneaen_hydra> I've even updated the images now ;)
[23:12:25] <CIA-8> 03lerman 07HEAD * 10emc2/src/emc/rs274ngc/ (8 files):
[23:12:25] <CIA-8> Add support for named parameters. Should not break any existing
[23:12:25] <CIA-8> programs.
[23:12:41] <cradek> lerman: cool
[23:13:22] <lerman> Try it, you'll like it. The flowsnake is pretty cool -- although I wouldn't want to try machining it. Engraving it would work, though.
[23:13:34] <lerneaen_hydra> joomla is really nice to work with after you've adjusted to it
[23:13:51] <lerneaen_hydra> looks nice and doesn't take too much work
[23:14:45] <cradek> flowsnake works here
[23:15:38] <lerman> That was quick. Of course that one works. If you have anything you can use for regression testing, it would be appreciated.
[23:16:26] <lerneaen_hydra> heh, one of those fractal triangles would be cool
[23:16:31] <cradek> useful-subroutines.ngc works too - I think that's the most new interp features I've ever used
[23:19:23] <cradek> lerman: it's strange (but correct) to see it do the whole shape with just line 13 highlighted
[23:19:54] <lerman> Why is that correct?
[23:20:17] <cradek> because line 13 is the G1 that causes the motion
[23:20:36] <skunkworks> works here also :)
[23:20:39] <lerman> I'd rather see it step through the calls and everything whether it does motion or not.
[23:21:27] <cradek> lerman: the interpreting and the motion happen at very different times. I think having it highlight as it reads ahead would not be very useful
[23:22:15] <lerman> Useful, I think, but differently useful. It would be nice to be able to single step through the code to debug it.
[23:22:44] <lerman> From the user (machine operator) standpoint I think it does what it should.
[23:23:36] <lerman> I'm going to take a look at debug comments. (debug, a param #1 another param #$foo$)
[23:24:16] <fenn> lerneaen_hydra: do you know martin persson?
[23:24:22] <lerneaen_hydra> cradek: heh, the distribution of hits on my articles is interesting
[23:24:24] <lerman> One issue I has is where do we output this? If we do it like msg, it requires an ack for each output. That would be a pain.
[23:24:23] <cradek> using single step on flowsnake has a surprising result
[23:24:29] <lerneaen_hydra> fenn: I recognise the name
[23:24:36] <fenn> he's a staff member at chalmers i think
[23:24:49] <lerneaen_hydra> oh
[23:24:50] <fenn> anyway that's neat
[23:24:49] <lerneaen_hydra> hmm
[23:24:56] <cradek> (well, not surprising to me - I knew what it would do, which is why I tried it)
[23:25:04] <fenn> he is xarragon on freenode
[23:25:13] <lerneaen_hydra> fenn: I don't think I've met him
[23:25:17] <lerneaen_hydra> ooh, haha, cool
[23:25:49] <lerman> How do you get it to single step? Once you hit run, it starts. Do you have to stop it and then single step? Then you couldn't step from the beginning.
[23:26:01] <cradek> you have to run, then pause, then step
[23:26:16] <lerneaen_hydra> fenn: oh, now that I look at what he's done I think he may have held a presentation/lecture when we started about global warming
[23:27:03] <fenn> right.. he says he's working on doing dsp algorithms in an fpga right now
[23:27:03] <skunkworks> spiro program works also
[23:27:06] <lerman> Watch that first step; it's a lulu. :-)
[23:27:15] <cradek> heh
[23:27:19] <lerneaen_hydra> fenn: oh, cool
[23:27:27] <cradek> skunkworks: that's good to know, it was pretty complex too
[23:30:53] <lerneaen_hydra> has etla changed his name?
[23:31:35] <lerneaen_hydra> hey, fenn wait a sec, how do you know martin?
[23:32:15] <fenn> we were making fun of bo^dick in ##microcontrollers last night
[23:33:00] <lerneaen_hydra> O.O
[23:33:02] <lerneaen_hydra> haha
[23:33:19] <lerneaen_hydra> is he often there?
[23:33:30] <lerneaen_hydra> err
[23:33:33] <lerneaen_hydra> there often
[23:34:13] <fenn> hm.. not sure, but i see him in ##electronics from time to time
[23:34:32] <lerneaen_hydra> ok
[23:36:44] <jepler> which channel do you guys use to make fun of me?
[23:36:58] <cradek> #kick-jepler
[23:37:17] <SWPadnos> I use #jepler-has-a-funny-hat
[23:38:00] <cradek> -!- Irssi: #jepler-has-a-funny-hat: Total of 1 nicks [1 ops, 0 halfops, 0 voices, 0 normal]
[23:39:08] <skunkworks> you guys are so mean :)
[23:39:14] <skunkworks> I like it
[23:39:19] <SWPadnos> #skunkworks-has-a-funnier-hat
[23:39:42] <jepler> :-P
[23:39:54] <SWPadnos> sorry jepler - I know you like your funny hat :)
[23:40:06] <lerneaen_hydra> what is this hat you're talking about?
[23:40:11] <SWPadnos> it's in my mind, I think
[23:40:14] <skunkworks> #skunkworks-can't-spelll
[23:40:26] <SWPadnos> ##bad_speling
[23:40:36] <lerman> Again-- looking at: 'm going to take a look at debug comments. (debug, a param #1 another param #$foo$)
[23:40:37] <lerman> One issue I has is where do we output this? If we do it like msg, it requires an ack for each output. That would be a pain.
[23:40:39] <lerman> cradek, jepler, SWPadnos, any thoughts on this?
[23:40:57] <cradek> lerman: I think stderr, at least for now
[23:40:57] <lerman> I could just output it to a log.
[23:41:19] <SWPadnos> I think it should be identical to the current msg facility
[23:41:20] <lerman> Where does stderr go (these days) -- in axis?
[23:41:39] <cradek> stderr is stderr, it goes to the controlling terminal unless it's redirected somewhere else
[23:42:02] <SWPadnos> and there isn't one if you run from an icon (is there?)
[23:42:11] <SWPadnos> I guess it would go to the X console
[23:42:16] <lerman> Well, the neatest thing would be if axis added a third page (manual control, mdi, LOG).
[23:42:51] <SWPadnos> there's already a way of handling messaged - I'd just improve that by adding formatted parameters to it - don't change how it works though
[23:43:01] <lerman> stderr get us nothing. I'd rather create a log file and output to that. At least you could then tail -f it to see the results.
[23:43:02] <SWPadnos> s/messagesmessages/
[23:43:04] <SWPadnos> argh
[23:43:16] <cradek> SWPadnos: currently you have to click OK after each one
[23:43:26] <SWPadnos> that's fine
[23:43:27] <lerman> The problem I see is that each msg requires an OK (cradek is faster).
[23:43:46] <SWPadnos> if that's what a message is supposed to do, then ones with parameters in them shouldn't be any different ...
[23:43:56] <cradek> that's an interesting point.
[23:44:00] <SWPadnos> you are, after all, messaging the operator
[23:44:02] <cradek> ok I agree with SWPadnos
[23:44:17] <SWPadnos> maybe there should be another command added: (log, blah blah)
[23:44:37] <lerman> Well, for now I'll write the code like that. I notice that the MESSAGE function calls some python stuff.
[23:44:45] <SWPadnos> and "print" - to go to stdout/stderr
[23:44:56] <SWPadnos> in the interp?
[23:45:32] <lerman> It really isn't for the operator (although it could be used for that). Once the code is there to insert params, we could have several versions.
[23:45:37] <cradek> lerman: you're just going to call MESSAGE() right?
[23:45:47] <lerman> For now; yes.
[23:46:02] <cradek> lerman: ok, you could make another canon call later.
[23:46:12] <SWPadnos> I think if you want to add some logging or error capcability, that shouldn't be a nsg - it should be called something else
[23:46:20] <SWPadnos> msg, that is
[23:46:36] <SWPadnos> nsg would work, but nobody would understand it :)
[23:46:52] <cradek> I think print or printf - and it goes to stderr.
[23:46:59] <lerman> I wasn't calling it msg -- msgf, or debug. Calling it msg would break any existing messages that had the character '#' in it.
[23:47:24] <cradek> true
[23:47:34] <cradek> I didn't think of that
[23:47:53] <SWPadnos> ah - ok. debug to stderr and print/printf to console
[23:48:17] <lerman> To console == msg with formatting?
[23:48:29] <SWPadnos> unless the code looks at the #xxx token, and outputs it unchanged if there's no xxx defined ...
[23:48:52] <SWPadnos> sure, anything you're adding can have formatting built in from the start
[23:48:56] <lerman> But there might be one defined?
[23:49:07] <SWPadnos> but you have a good point about breakage with existing msgs
[23:49:14] <lerman> ^H over the ?
[23:49:17] <SWPadnos> sure - in that case you'd get something funny looking
[23:49:51] <SWPadnos> something like "change to tool #47" could be an issue :)
[23:52:44] <lerman> Of course, if someone has a comment that looks like (debug, whatever) I've already broken it. But my view is that it's pretty unlikely. Rumley had added (in emc1) the ability to have simple .ini file stuff. I was thinking that an ini file entry saying "USE_EXPANDED_COMMENTS" would at least allow the inegrator to guarantee compatibility here.
[23:53:04] <lerman> Yes SWPadnos -- that was exactly the problem I had in mind.
[23:57:53] <lerneaen_hydra> 'night all
[23:57:59] <cradek> lerneaen_hydra: bye
[23:58:10] <lerneaen_hydra> bb tomorrow or so
