oooh, it looks really promising
cradek: fake tach>?
it moves smoothly - needs tuning
hope the tach input on the amp adjusts far enough - this voltage is a lot lower
Jymmm is now known as Red70sShow
Red70sShow is now known as Jymmm
wow - I think I have a shift component that I can test..
rough around the edges - but a good starting point.
cradek: are they 60v tachs?
heh - that probably doesn't make sense.
are they 60v at top rpm?
Jymmm: thanks :) I think with the right hal component - we could take over the world!
skunkworks: Jsut keep saying "I think it can! I think it can!"
hmm, it works just as well with the tach unhooked
hooking it up stomps on the dac output
I think it's driving 6kohms so it seems like it should be ok
I'm going to try hooking up 5v directly to the 7i48
the measured load is 6k and it completely flattens the dac output
something is not right here
oh - I bet it's wired backward - duh
[01:21:06] <skunkworks> http://www.youtube.com/watch?v=o70K3mvduqw
(running with a 12v charger ;))
haha I'm an idiot
how long did that take me to figure out!?
heh - try not to think about it to hard..
no, that was my problem in the first place.
hey now the knobs work!
holy crap it works
it sounds smoother than it ever has
cool beans :0
so - are you going to convert all the other axis?
I'm now wondering if X would sound better if I did
little tiny blips of .0005 ferror at the beginning and end of accel, on 450ipm rapids
the real thanks goes to seb_kuzminsky for all the work he did on the high quality encoder velocity
and of course hostmot2 for having the timestamps that make it possible
skunkworks: you moved your machine!?
haha the world went upside-down at the end there as you got more and more breathless :-)
that was dad - I have been sick :)
he was running it with a 6/12v charger
so not quite closed loop control yet :-)
do you have the amps that you'll use?
closed loop soon then...
EMC: 03cmorley 07v2.4_branch * r526292394aa6 10/src/emc/usr_intf/pncconf/pncconf.py: change XML entry from stepconf to pncconf
EMC: 03cmorley 07v2.4_branch * r920af707dc64 10/src/emc/usr_intf/pncconf/pncconf.py: Fix - spaces are not allowed in machine names
EMC: 03cmorley 07v2.4_branch * r642dd1d57d8e 10/src/emc/usr_intf/pncconf/pncconf.py: fix mesa pinnames when using a different locale
EMC: 03cmorley 07v2.4_branch * rc2463dc28e20 10/src/emc/usr_intf/pncconf/pncconf.py: ready pncconf for parport and spindle helpfiles
SteveStallings is now known as steves_logging
i am having a stupid newbie problem, i am running the livecd installed and upgraded to compile emc18.104.22.168pre. I run an emc config .ini file and if fails with error "waiting for s.axes"
the config runs fine in the default emc2.3.0 version, anyone know what is happening?
changes are required for a 2.3 configuration to work with 2.4 and later. check the UPDATING page on the wiki.
OKay i got the updating thing sorted i think, now i have a problem with simulator loading???
emc says 'Waiting for ./test to become ready.....'
i have a 'loadusr -W ./test' in my hal
the test file is a python script similar to the pumagui one
You probably need to specify the component name in the loadusr command
if it is different than "./test"
example: loadusr -Wn mycomponent ./test
i think its a path problem
yes, it is path, if i copy test to the emc bin dir then it loads
now i got more errors
EMC: 03jepler 07master * r144bb6f33b47 10/configs/smithy/ (4 files):
EMC: Adds the 622keyence configuration for the machine at Champion Spark Plug. An
EMC: external digital depth sensor (appearing as an encoder input) is read via M66
EMC: and various pyvcp widgets are used to aquire user input and display process
EMC: variables using M68.
EMC: 03jepler 07master * r7f34a3cc5012 10/src/hal/drivers/serport.comp: serport: improve error on failure to register
EMC: 03jepler 07master * r44780f562246 10/configs/smithy/ (12 files):
EMC: Improves system behavior by pausing the program when a guard is opened during a
EMC: program. When the door is closed the spindle will restart, but the operator will
EMC: have to manually resume axis motion. This gives the spindle time to reach the
EMC: programmed speed and improves operator safety.
EMC: 03jepler 07master * r9a21aa6fa588 10/src/emc/task/emctaskmain.cc: Fix RFL when starting between a sub definition and its call
EMC: 03jepler 07master * r66893f0e9cf9 10/docs/src/hal/ (3 files in 2 dirs): add second reader to graphic
EMC: 03jepler 07master * r046d44714200 10/ (VERSION debian/changelog): release version 2.4.3
EMC: 03jepler 07master * rc3c8d9a74249 10/docs/src/hal/comp.lyx: replace the reference to bool with int
EMC: 03jepler 07master * r2728cb469aad 10/src/Makefile: install emctool.h
EMC: 03jepler 07master * re1ee4f0a1f1d 10/src/configure.in: configure: detect missing library
EMC: 03jepler 07master * r6b46f8ce9fc4 10/src/configure.in: configure: fix truncated warning
EMC: 03jepler 07master * r1bd62994ff1f 10/docs/src/hal/comp.lyx: markup fixes
EMC: 03jepler 07master * re4612d45f220 10/debian/rules.in: Don't compress sample configurations
EMC: 03jepler 07master * r1cf6dc1cad70 10/src/emc/motion/usrmotintf.cc: when sending command to motion fail, print reason in terminal
EMC: 03jepler 07master * r06683ff84199 10/src/emc/usr_intf/axis/scripts/axis.py: Improve an error message by making it more vague
EMC: 03jepler 07master * r433974fabe5d 10/src/emc/usr_intf/axis/scripts/axis.py: print 's.axes' warning fewer times
EMC: 03jepler 07master * rc2463dc28e20 10/src/emc/usr_intf/pncconf/pncconf.py: ready pncconf for parport and spindle helpfiles
EMC: 03jepler 07master * r526292394aa6 10/src/emc/usr_intf/pncconf/pncconf.py: change XML entry from stepconf to pncconf
EMC: 03jepler 07master * r920af707dc64 10/src/emc/usr_intf/pncconf/pncconf.py: Fix - spaces are not allowed in machine names
EMC: 03jepler 07master * rbf0cccc8078c 10/docs/man/man9/.gitignore: add bldc_hall3.9 to .gitignore
EMC: 03jepler 07master * rbec24629de85 10/ (27 files in 9 dirs): Merge remote branch 'origin/v2.4_branch'
EMC: 03jepler 07master * r51aeaaaf830e 10/src/emc/usr_intf/axis/scripts/axis.py: axis: gray out 'run from here' on right click menu when emc is not enabled
EMC: 03jepler 07master * r642dd1d57d8e 10/src/emc/usr_intf/pncconf/pncconf.py: fix mesa pinnames when using a different locale
merging 2.4 into master
yeah, it's not as much as it looks like
my configuration system has created its first working conf
but would be nice if i knew how to specify the path of a component in 'loadusr'???
Just like you did: ./test
but when the *component name* is different than the first argument (e.g., "test" vs "./test") then you have to specify the component name
loadusr -Wn test ./test
and for the removal of doubt, remember that "the current directory" is "the directory containing the inifile"
ooh, right i missed that
i will remove the test file from the emc bin dir just to check
but when the command is not found at all there's a different error
$ halcmd loadusr -W this-command-does-not-exist
<commandline>:0: execv(this-command-does-not-exist): No such file or directory
<commandline>:0: this-command-does-not-exist exited without becoming ready
oooooopps, i got it test ./test
as they dont match with the extra path chars
yeah it all works now
right, and yay
there might be a better heuristic for the component name, such as "cut off everything up to and including the last slash" and "cut off everything from the last dot to the end" (so loadusr -W ./test.py would wait for 'test' by default)
I'd be happy to review a patch to halcmd that makes it work that way
probably for master only, due to the small risk of breaking an existing configuration which actually names a component "./test.py" for this very reason..
unfortunatly im working on something else, which maybe ready in a couple of weeks
im too much of a newbie to start hacking halcmd
anyone know about linking homing to pyvcp joints?
seems if i move joint past 180 degrees then home the axis, then jog in reverse the pyvc dial does not move anymore??
are there any docs on how the 3d drawing functions work and how the puma560gui works?
moopy: what kind of docs?
do you mean vismach?
I've been looking at EMC2 for awhile now. I've been focused on planning for the conversion of an old VMC to EMC2 from the current archaic that's on it. While reading up on the EMC's current state I've become quite amazed with HAL. Has any thought ever been given to moving HAL to its own git tree? It seems that HAL could potentially see much wider use that just EMC if it became a project unto itself.
there was an initial attempt to do that
but so far all HAL developers are also emc2 developers
voxadam: I think it's always been part of the design that they're useful separately - but no I don't think anyone's currently serious about splitting them
and separating the two just for the fun of it, ain't gonna happen
actually even now, they're quite separate aside from being in the same repository
I think it'd be more useful to talk about changing emc2 so that it can be configured for hal only, or splitting packages so that hal is in a base package that emc depends on
especially as that will mean quite a lot of work for packaging and making them work together
as a release manager of emc2 I don't want to complicate things by having another git repository to make releases from
I can understand that.
I've considered/designed a hal-only (or hal-and-ladder-only) project and always figured I'd install emc but then just not use all of it
but by all means use hal in your own project without emc. I think there are some stuff it would be great for
i need doc to workout how the HalRotate and HalTranslate commands work
realtime start / halcmd whatever
I've been thinking about using HAL and CL to automate some things that I've been working on in my head.
moopy: there is no doc, except for the many examples
HalTranslate is obvious
just translate the object with some X.Y.Z offsets
HalTranslate works by getting a value from hal and then performing an OpenGL operation that depends on that value
same for HalRotate although the angles might not be obvious if you don't know 3D ops
glPushMatrix and glTranslatef are Python wrappers of standard OpenGL API calls, you'll find them documented online
HalTranslate([tooltip], c, "tool_length", 0,0,-1)
what do the arg represent?
move tooltip -1 in z direction?
c is the hal component
"tool_length" is the name of the pin
0,0,-1 is the direction of the translation
[tooltip] is the list of items to translate (a single item in this case)
that should be of great help... thanks jepler
so this says: when drawing this HalTranslate object, first translate by tool_length * <0,0,-1>, then draw tooltip, then undo the translation
what.... undo it?
in opengl a transformation stays in effect until it's undone
but objects like HalTranslate that work by applying OpenGL transformations always undo them after drawing the contained objects
so if i make another translation its relative to the original coords?
i think i need to go away work things out and comeback with some more questions
moopy: you should play with it! maybe the best way is to modify some of the existing examples and see what they do.
thanks for the help
[21:57:35] <jepler> http://glprogramming.com/red/chapter03.html#name8
vismach uses opengl so its transformations work like this ^^
just one more question actually..... HalRotate([tool],c,"joint4",1,0,-1,0)
rotate around the axis <0,-1,0> (i.e., the negative Y axis) by 1*joint4 degrees
what are the last 4 arg in hal rotate.... a x,y,z coord + angle?
def __init__(self, parts, comp, var, th, x, y, z):
I didn't remember that; I looked at the __init__ and saw that they're th (theta), x, y, and z
glRotatef(th * self.comp[self.var], x, y, z)
okay i think i got plenty to be getting on with...... i now need a copy and paste and a few hours to understand things
thanks again for the help
vismach "sun and planet" demo: http://emergent.unpy.net/files/sandbox/solar.hal http://emergent.unpy.net/files/sandbox/solar.py
jepler: got a png?
[22:36:47] <jepler> http://emergent.unpy.net/files/sandbox/solar.png
the earth is square so that you can tell it's rotating
the blue spot is where the backtrace comes out of
the moon is missing :)
backplot, not backtrace
I knew that wasn't the right word
gdb hovering around