#emc-devel | Logs for 2008-08-17

Back
[00:10:27] <cradek> haha
[00:10:39] <cradek> you tease
[00:11:38] <jepler> cradek: well .. I dunno what the UI should be like, but maybe you have some ideas
[00:11:54] <jepler> hm I bet there are some units problems in that new code to use the status buffer ..
[00:18:42] <mozroute> jepler: looks like in your idoubler you change banks with every change of select
[00:19:06] <mozroute> so one bank is read when select is high and one when select is low
[00:19:19] <jepler> mozroute: yes, I think that's what I wrote
[00:20:27] <mozroute> if (!select) {
[00:20:27] <mozroute> select = !select;
[00:20:27] <mozroute> return;
[00:20:27] <mozroute> }
[00:20:59] <mozroute> if I add the above right under the ;; line that should make it read only on a high right?
[00:22:08] <mozroute> that's what I need for this. the inputs switch with every high-going edge
[00:22:29] <jepler> hmm -- how do you know which bank you're reading, then?
[00:23:03] <mozroute> hmm, I'll have to keep track of that somehow
[00:23:05] <jepler> you will have to make more changes, 'b' is based on 'select' .. you'll have to base it off something else
[00:23:15] <mozroute> that's right
[00:23:28] <jepler> but that piece of logic you wrote may be part of the puzzle
[00:23:41] <mozroute> can I create a variable that will stay between calls?
[00:23:55] <mozroute> a pin variable would work I guess
[00:24:25] <jepler> you'll probably find that having a parameter or a pin for the value will be useful for debugging
[00:24:53] <jepler> you can also declare a 'variable': variable int odd_or_even;
[00:25:04] <jepler> you can see the use of 'variable float old' in the ddt example at the top of http://linuxcnc.org/docs/html/hal_comp.html
[00:26:16] <mozroute> ok. I was reading in that doc. but I haven't seen yet if a variable stays between calls
[00:26:32] <jepler> one that is above the ";;" persists
[00:28:06] <mozroute> ok. it looks like you can have multiple instances of a component? I guess I could put a bob on three parports...
[00:28:48] <jepler> yes usually you can have a number of any component
[00:29:00] <jepler> it's very useful to have multiple stepgens
[00:29:42] <mozroute> true, but I can see that some components you may want only one.
[00:30:12] <jepler> when you declare a 'variable' you get one for each component
[00:32:04] <mozroute> i saw that. i meant you may want only one instance of some components
[00:32:36] <jepler> oh -- yes
[00:32:49] <jepler> in that case you say 'option singleton;' in the top part
[00:32:53] <jepler> or something like that
[00:33:14] <mozroute> now i've got to make sure i start up reading the same bank each time emc starts...
[00:33:17] <mozroute> ok!
[00:33:32] <jepler> what resets it to a known bank?
[00:34:34] <mozroute> not sure :-)
[00:35:14] <mozroute> hadn't thought about that until just now. I better look at some datasheets...
[00:36:52] <jepler> I envisioned something like a 74*157 2-input multiplexer..
[00:38:36] <mozroute> it's a 74*244
[00:39:57] <jepler> so at any time just one of the "enable" inputs on the 244 is active
[00:40:17] <jepler> and pairs of outputs are simply wired together
[00:40:30] <mozroute> I didn't design the circuit, but Tom said it switched on a rising edge
[00:40:39] <mozroute> looks like that's correct
[00:41:55] <alex_joni> good night all
[00:42:09] <jepler> see you alex_joni
[00:42:16] <jepler> I'd better go forage for dinner..
[00:42:29] <mozroute> hmm, maybe it does switch between high and low
[00:49:42] <mozroute> is this a userspace or realtime component?
[00:50:04] <jepler> you get a realtime component unless you ask for a userspace one
[00:50:43] <mozroute> should it be realtime or does it matter?
[00:51:48] <mozroute> I looked at the schematic and it does switch banks based on the state of the select pin, not on a pulse...
[00:51:51] <jepler> I'd leave it as realtime. you want to have a guarantee that these inputs are read in a timely fashion. For instance, f you read the home switch 100ms late then your home position is shifted.
[00:52:08] <mozroute> maybe i was thinking of the output circuit
[00:52:16] <mozroute> ok, will do.
[00:53:19] <mozroute> I get these warnings when I install the comp
[00:53:22] <mozroute> WARNING: "hal_ready" [/tmp/tmpiNJ7u9/idoubler.ko] undefined!
[00:53:22] <mozroute> WARNING: "hal_export_funct" [/tmp/tmpiNJ7u9/idoubler.ko] undefined!
[00:53:22] <mozroute> WARNING: "hal_pin_bit_newf" [/tmp/tmpiNJ7u9/idoubler.ko] undefined!
[00:53:22] <mozroute> WARNING: "hal_malloc" [/tmp/tmpiNJ7u9/idoubler.ko] undefined!
[00:53:22] <mozroute> WARNING: "rtapi_snprintf" [/tmp/tmpiNJ7u9/idoubler.ko] undefined!
[00:53:22] <mozroute> WARNING: "hal_init" [/tmp/tmpiNJ7u9/idoubler.ko] undefined!
[00:53:24] <mozroute> WARNING: "hal_exit" [/tmp/tmpiNJ7u9/idoubler.ko] undefined!
[00:53:32] <mozroute> is that normal?
[00:54:50] <jepler> yeah it is harmless
[00:55:31] <jepler> there is some boring technical reason why those "undefined" warnings are actually just fine, but they're hard to silence
[07:36:37] <CIA-35> EMC: 03seb 07TRUNK * 10emc2/docs/man/man9/hostmot2.9:
[07:36:37] <CIA-35> EMC: Give HAL interfaces to all IO pins, not just the full GPIOs. IO pins
[07:36:37] <CIA-35> EMC: used by active module instances have restricted interfaces.
[07:36:37] <CIA-35> EMC: Improved IO Port handling. Support open-drain pins.
[07:36:37] <CIA-35> EMC: Updated README to reflect reality.
[07:36:38] <CIA-35> EMC: Report firmware timestamp when loading.
[07:36:42] <CIA-35> EMC: Improved config string parsing.
[07:36:47] <CIA-35> EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/mesa-hostmot2/ (8 files):
[07:36:47] <CIA-35> EMC: Give HAL interfaces to all IO pins, not just the full GPIOs. IO pins
[07:36:48] <CIA-35> EMC: used by active module instances have restricted interfaces.
[07:36:50] <CIA-35> EMC: Improved IO Port handling. Support open-drain pins.
[07:36:52] <CIA-35> EMC: Updated README to reflect reality.
[07:36:56] <CIA-35> EMC: Report firmware timestamp when loading.
[07:36:58] <CIA-35> EMC: Improved config string parsing.
[12:32:44] <CIA-35> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gui/images/tool_estop.gif: add images to the toolbar section
[12:37:19] <CIA-35> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gui/images/ (16 files): add images to the toolbar section
[13:13:40] <BigJohnT> EMC2 Axis Calibration window... when you press the Test button what should it do?
[13:30:44] <cradek> move the axis back and forth
[13:50:58] <BigJohnT> does it just test to see if it moves or does it move a specific distance so you can measure steps?
[13:57:50] <rayh> There is a little test window that pops in.
[13:58:31] <BigJohnT> hi Ray
[13:59:19] <rayh> Hi John
[13:59:31] <rayh> Thanks for all the good editing.
[13:59:36] <BigJohnT> the test window doesn't say anything about what it does...
[13:59:43] <BigJohnT> your welcome
[13:59:57] <rayh> I could capture that window if you want.
[14:00:35] <BigJohnT> would it be different from the one I see here?
[14:01:55] <rayh> I doubt it.
[14:02:01] <BigJohnT> when the EMC2 Axis Calibration window pops up I see where I can change the scale and the maxaccel and test and refresh
[14:02:40] <BigJohnT> if I press test I don't see anything on the live plot or see any diff in the popup window
[14:03:28] <rayh> Oh. Then what I see here is different.
[14:03:42] <rayh> I'll paste in a minute.
[14:03:48] <BigJohnT> ok
[14:07:35] <skunkworks> BigJohnT: your using the axis calibration thru the gui.. I think ray is talking about stepconf - test axis
[14:08:06] <skunkworks> the axis calibration 'test' just puts your pid feed forward into hal to test its tuning.
[14:08:07] <BigJohnT> yes I am using the one from the AXIS menu
[14:08:31] <rayh> Oh. Okay.
[14:08:42] <micges> logger_dev: bookmark
[14:08:42] <micges> Just this once .. here's the log: http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2008-08-17.txt
[14:09:17] <rayh> I believe that is intended to tune servo systems.
[14:09:49] <skunkworks> yes. Although I think you can also change the input scale.. Which could come in handy at times.
[14:09:50] <skunkworks> yes. Although I think you can also change the input scale.. Which could come in handy at times.
[14:09:54] <skunkworks> oops
[14:10:25] <BigJohnT> the only items that show up are the scale and maxaccel, is that because I've opened up a stepper one?
[14:10:35] <skunkworks> probably
[14:10:44] <rayh_> Yes.
[14:11:03] <rayh_> I believe it will show the pid and scale and maxaccel if you open a servo system.
[14:11:09] <rayh_> I've not tried it of late though.
[14:12:21] <BigJohnT> I just tried it and got the same as a stepper
[14:12:49] <rayh_> try servo sim
[14:13:06] <BigJohnT> glancing through emccalib.tcl it looks like it is suppost to save the entries to your ini file...
[14:14:05] <BigJohnT> rayh that one came up with tkemc interface...
[14:14:06] <rayh_> http://imagebin.ca/view/DYQSrWAl.html
[14:14:34] <rayh_> Yes and the calibration screen is under settings
[14:15:02] <rayh_> It is the same program however.
[14:15:43] <cradek> yes it does rewrite the ini for you
[14:15:45] <BigJohnT> that makes a lot more sense
[14:15:55] <cradek> 'morning ray
[14:16:09] <rayh_> Hi Chris. How's the lathe.
[14:16:28] <cradek> coming along. everything takes longer than I expect (but I know to expect that)
[14:16:40] <rayh_> Yep.
[14:16:56] <cradek> it's possible today that I will have the amps running again (but no feedback yet)
[14:17:13] <rayh_> I'd put that estop relay on the AC side for those drives.
[14:17:32] <cradek> you mean the transformer primary?
[14:17:52] <rayh_> Between the transformer and the rectifier.
[14:18:51] <rayh_> Although the line side should be okay also.
[14:19:16] <rayh_> Are you planning on the PC being in the cabnet with the drives and all?
[14:19:24] <cradek> is there an advantage to one side or the other?
[14:19:43] <cradek> no the amps are in a separate box.
[14:20:01] <rayh_> Ah good man.
[14:20:02] <cradek> the computer is in the box with all the opto stuff
[14:20:10] <rayh_> Great.
[14:20:35] <cradek> the vfd doesn't fit anywhere yet unfortunately
[14:20:47] <cradek> but that's the only piece I still have to fit in
[14:21:05] <CIA-35> EMC: 03bigjohnt 07TRUNK * 10emc2/tcl/bin/emccalib.tcl: add Servo to screen title
[14:21:15] <rayh_> How you handling the 3 phase to the coolant pump?
[14:21:51] <cradek> I am going to try using just a run cap to make the extra phase
[14:22:10] <cradek> I got a variety of values and hope maybe one will run it reliably
[14:22:35] <BigJohnT> cradek: what hp is the coolant motor?
[14:22:35] <skunkworks> if all else fails - low hp vfd's are really cheap.
[14:22:46] <rayh_> That works. They make little static converter boxes. We were using a little vfd ($99) there as well.
[14:23:40] <rayh_> Gotta run to a Bday party. Catch you guys later.
[14:23:41] <cradek> BigJohnT: 1/6
[14:23:55] <cradek> have fun!
[14:24:05] <cradek> hm, now I want some cake
[14:24:08] <rayh_> The little AD vfd ran it really well.
[14:24:19] <rayh_> Okay. Next day air?
[14:24:28] <BigJohnT> I've run small fractional three phase on single phase without anything for a long time
[14:24:58] <rayh_> As long as it starts spinning that would work.
[14:25:00] <cradek> rayh_: thanks, but I bet I could find some locally faster
[14:25:06] <BigJohnT> never seemed to bother it, of course when I discovered that I connected the third phase
[14:25:23] <cradek> BigJohnT: haha
[14:25:40] <cradek> BigJohnT: I bet with the cap it will be fine. we'll see.
[14:25:52] <BigJohnT> I would bet too
[14:26:19] <BigJohnT> if it will start on single you will not have to rig up a start cap
[14:27:13] <cradek> yeah I hope it will start with just the run cap. it will be very easy to rig up if so.
[14:27:50] <BigJohnT> if not then you just need a potential relay for the start cap from graingers
[14:30:03] <CIA-35> EMC: 03bigjohnt 07v2_2_branch * 10emc2/tcl/bin/emccalib.tcl: add Servo to screen title
[14:34:40] <CIA-35> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gui/axis.lyx: adding menu items
[14:39:53] <BigJohnT> my favorite phase converter page http://homemetalshopclub.org/projects/phconv/phconv.html
[16:34:13] <alex_joni_> alex_joni_ is now known as alex_joni
[20:47:47] <CIA-35> EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/gui/images/ (17 files): add tool bar icons
[20:49:10] <CIA-35> EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/gui/axis.lyx: add tool bar icons