#emc-devel | Logs for 2009-05-25

[01:59:31] <SWPLinux_> SWPLinux_ is now known as SWPLinux
[02:51:13] <SWPLinux_> SWPLinux_ is now known as SWPLinux
[06:46:11] <CIA-48> EMC: 03cradek 07TRUNK * 10emc2/src/emc/task/emccanon.cc: fix arcs (and their AXIS preview) in rotated coordinate systems
[06:46:13] <CIA-48> EMC: 03cradek 07TRUNK * 10emc2/lib/python/rs274/interpret.py: fix arcs (and their AXIS preview) in rotated coordinate systems
[06:46:22] <CIA-48> EMC: 03cradek 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: fix arcs (and their AXIS preview) in rotated coordinate systems
[06:52:19] <alex_joni> somebody's up late
[06:52:45] <cradek> had to take advantage of the 5 mins of network...
[06:54:06] <cradek> goodnight now!
[07:05:47] <alex_joni> see you
[12:42:44] <alex_joni> * alex_joni wonders if any fest-ies are around
[12:42:48] <alex_joni> there's a new bug for seb:
[12:42:54] <alex_joni> http://www.linuxcnc.org/component/option,com_kunena/Itemid,20/func,view/id,286/catid,10/limit,6/limitstart,6/lang,en/index.php
[12:43:41] <alex_joni> I think (judging by that report) that the hm2 stepgen doesn't reset it's internal position on index like the software stepgen does. then, when the motion controller resets the position, the hm2 stepgen wants to go towards 0, which can be anywhere..
[12:49:07] <BigJohnT> morning alex_joni
[13:11:16] <alex_joni> hi BigJohnT
[13:23:59] <BigJohnT> what's up today?
[13:27:35] <BigJohnT> what do you think of this question? http://www.linuxcnc.org/component/option,com_kunena/Itemid,20/func,view/catid,9/id,324/lang,en/
[14:10:18] <CIA-48> EMC: 03cmorley 07TRUNK * 10emc2/src/emc/usr_intf/pncconf/ (pncconf.py pncconf.glade): fixed mesa page to load saved data
[14:10:54] <BigJohnT> when you apply G10 L2 Pn Rn is there any indication that it has been rotated?
[14:12:28] <cradek_> in AXIS the axes will rotate if that system is active
[14:12:36] <cradek_> cradek_ is now known as cradek
[14:12:55] <BigJohnT> thanks
[14:13:45] <cradek> if you're writing docs already, you're my hero
[14:17:52] <colin_> anyone willing to write my kine module ?
[14:18:02] <colin_> will donate money beer hardware
[14:18:04] <colin_> ;)
[14:20:46] <BigJohnT> trying to figure it out first then the docs :)
[14:22:08] <BigJohnT> ah, I see it now :)
[14:22:39] <cradek> I think I need to rotate the DRO numbers - that's not done yet
[14:23:34] <BigJohnT> and jogging :)
[14:24:19] <BigJohnT> cradek: this is really cool
[14:24:35] <cradek> thanks
[14:30:16] <CIA-48> EMC: 03cradek 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: machine position shouldn't include the TLO
[14:35:20] <cradek> actually maybe you should wait until it settles... :-)
[14:36:55] <BigJohnT> I see it will take more than 360 degrees for R
[14:37:16] <cradek> yeah, it will take any rotation
[14:44:45] <CIA-48> EMC: 03cradek 07TRUNK * 10emc2/src/emc/usr_intf/axis/scripts/axis.py: when showing the relative position, and the coordinate system is rotated, show the rotated values on the DRO.
[14:54:52] <BigJohnT> while it confused me for a bit jogging the X axis did not go in the direction I expected while it makes sense that only the X axis moved
[14:55:25] <cradek> it feels to me like it should jog in the rotated X direction, but that's currently not possible
[15:16:12] <CIA-48> EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gcode/main.lyx: update docs for g10 l2
[15:16:42] <cradek> BigJohnT: I think the behavior is settled for a while now - if you update you will get the new DRO behavior
[15:17:05] <BigJohnT> ok, I just finished updating
[15:17:29] <BigJohnT> running a file now
[15:18:17] <BigJohnT> seems to be working
[15:18:54] <BigJohnT> Sweet!
[15:20:06] <BigJohnT> * BigJohnT goes back to hooking up the gecko to the 5i20
[15:47:58] <Roguish> morning all. question on 2.3.1
[15:49:42] <Roguish> i'm updating my m5i20 to use hm2 driver. all is going good, except when in axis and i select the 'calibration' nothing happens.
[15:49:57] <Roguish> any clues? am i missing something again?
[15:50:10] <alex_joni> Roguish: most likely nobody tried that calibration lately :)
[15:50:16] <alex_joni> but you can still calibrate using hal commands
[15:50:54] <jmk-wvm> that calibration thing is broken at the moment - I think a bug report has already been filed, but nobody has had a chance to work on it yet
[15:50:59] <Roguish> yeah, i know and am doing that, but the calibration screen is just so handy
[15:51:03] <Roguish> !!!!!
[15:51:14] <Roguish> ok.
[15:51:37] <jmk-wvm> I didn't know it was broken in 2.3.1 - thought it was just in CVS trunk
[15:52:07] <Roguish> pretty sure i'm in 2.3.1, not trunk.
[15:52:21] <jmk-wvm> you say "nothing happens", do you mean really nothing happens?
[15:52:50] <jmk-wvm> here, a window appears, with a picture of the penguin, but the actual calibration info doesn't appear
[15:53:13] <Roguish> nothing pops up at all.
[15:53:17] <jmk-wvm> oh
[15:57:42] <cradek> jmk-wvm: I think there are two problems in the two trees
[15:59:39] <alex_joni> bad apples?
[16:13:16] <Roguish> just updated my 'trunk' version, and
[16:13:40] <Roguish> calibration brings up the penguin window, but not parameters.
[18:12:20] <CIA-48> EMC: 03jepler 07TRUNK * 10emc2/src/emc/usr_intf/emcsh.cc: this fixes emccalib
[18:20:14] <Roguish> here's another potential problem. when i add my PYVCP (for extra screen stuff) 'SHOW HAL CONFIGURATION' stops working.
[18:21:26] <Roguish> also, in 2.3.1, when i run my old m5i20 configuration the 'calibration' works.
[18:21:57] <Roguish> when i run my new hm2 configuration, 'calibration' stops working.
[18:22:29] <Roguish> just FYI
[18:23:05] <BigJohnT> Roguish: show hal configuration works for me in trunk
[18:26:04] <Roguish> ok, works for me also, until i add PYVCP=file in the [display] section of the .ini
[18:26:49] <Roguish> did i miss somethign about PYVCP changing???
[18:27:22] <BigJohnT> I have a pyvcp panel as well on the example I tested just a min ago
[18:27:35] <BigJohnT> 6.06 here
[18:28:53] <Roguish> 8.04 here
[18:29:17] <jepler> it's a known bug that hm2 and calibration don't get along
[18:29:39] <BigJohnT> works on 8.04 too for me with hm2
[18:30:12] <BigJohnT> I have the 5i20 card in my 8.04 machine
[18:30:29] <BigJohnT> show hal I mean works
[18:30:47] <Roguish> ok with calibration and hm2, but this is about 'show hal configuratioon'
[18:30:47] <BigJohnT> calibration does not
[18:31:01] <Roguish> maybe i have an error ....
[18:31:19] <BigJohnT> does your pyvcp screen show up?
[18:31:37] <Roguish> yes, when i add the PYVCP statement.
[18:31:45] <jepler> in the case of hostmot2, it prints an error similar to
[18:31:45] <jepler> Error in startup script: Invalid argument
[18:31:45] <jepler> while executing
[18:31:45] <jepler> "hal getp {hm2_5i20.0.stepgen.[AXIS_0](STEPGEN).position-scale}"
[18:31:54] <jepler> that is, calibration prints that error
[18:31:56] <jepler> and does not start
[18:32:13] <Roguish> seems to be correct
[18:32:13] <alex_joni> ah, because if ini parsing
[18:32:42] <Roguish> don't use STEPGEN here. have 0 stepgens.
[18:32:43] <alex_joni> of*
[18:33:05] <jepler> the similarity of our errors in calibration would be 'invalid argument while executing'
[18:33:12] <alex_joni> Roguish: if you change your .hal file to not contain [] ini lookups, it will probably work
[18:33:15] <jepler> the specific text after the getp will depend on the hal files
[18:34:29] <Roguish> in which hal file?
[18:34:53] <alex_joni> Roguish: ^^ , your hal file
[18:35:05] <alex_joni> the one you're using :)
[18:35:47] <Roguish> have hm2-servo.hal and hm2_io.hal
[18:36:58] <Roguish> -servo.hal is full of [] references. _io.hal has none.
[19:00:52] <CIA-48> EMC: 03jepler 07TRUNK * 10emc2/tcl/bin/emccalib.tcl: paper over a problem for hm2-style inifiles where the parameter being set is the result of an inifile substitution
[19:01:53] <jepler> if you're interested, you can try this change against the emccalib in 2.3: http://cvs.linuxcnc.org/cvs/emc2/tcl/bin/emccalib.tcl.diff?r1=1.41;r2=1.42
[19:02:26] <seb_kuzminsky> jepler: i installed python-tk on the lenny buildslave as you suggested
[19:02:35] <seb_kuzminsky> the commit you just made will test it out
[19:02:40] <jepler> seb_kuzminsky: ok
[19:02:40] <jepler> thanks
[19:02:43] <jepler> drive home go OK?
[19:02:50] <seb_kuzminsky> some rain but not bad
[19:03:01] <jepler> we got a hint of rain here today
[19:03:03] <seb_kuzminsky> looking forward to next Fest :-)
[19:03:24] <seb_kuzminsky> how's zenbot?
[19:05:09] <jepler> the x axis problem is gone since I re-did the wiring
[19:05:30] <jepler> haven't run it around very much, though, since there's a lot of conversation going on today
[19:08:03] <seb_kuzminsky> ok the lenny build is passing again
[19:08:28] <jepler> yay
[19:08:30] <seb_kuzminsky> ok have fun conversations, see you guys later
[19:08:33] <jepler> see you
[19:17:21] <BigJohnT_> BigJohnT_ is now known as BigJohnT
[20:36:09] <robh> Roguish, if you still have problems with the calibration loading up, i found problem to be with the ini varable use when setting the encoder.XX.scale if you change it to setp hm2_5i20.0.encoder.00.scale [AXIS_0]INPUT_SCALE should work fine with a 5I20 that is all other pins can be left as variables from ini file fine
[20:54:42] <Roguish> robh: you mean change [HOSTMOT2](BOARD) to 5i20.0. ???
[20:55:24] <BigJohnT> just up to the current version and it works now Roguish
[20:55:54] <BigJohnT> I just checked it and it calibration works for me now
[20:55:58] <Roguish> works now??
[20:56:36] <BigJohnT> yes calibration works for me now
[20:56:47] <Roguish> in a trunk version? or 2.3.1 ?
[20:56:51] <BigJohnT> I just updated trunk
[20:56:56] <BigJohnT> trunk
[20:57:36] <Roguish> ok. i'll have to update my trunk also. did you change something?
[20:57:39] <Roguish> in trunk?
[20:58:22] <BigJohnT> jepler did
[20:58:35] <Roguish> ok, thanks jepler.
[20:59:35] <BigJohnT> works with steppers too
[21:04:27] <robh> Roguish, yes sorry, thats if u dont want to run trunk etc
[21:07:59] <Roguish> robh: thanks. i'll try both. i'm trying to avoid trunk and any 'work-arounds'