dan_falck: not really a record, we had over 40, but it's not nice either
I don't seem to be getting a proper install of AXIS from the cvs today.
EMC2 - pre-2.1 CVS HEAD
Machine configuration directory is '/home/rayh/emc/emc2/configs/nist-lathe/'
Machine configuration file is 'inch.ini'
Can't execute DISPLAY program /home/rayh/emc/emc2/bin/axis
did you cvs up -dP ?
did this emc2 work with axis earlier?
did you run make?
Yep to cvs up
yep to make
I don't know about axis earlier. This is the first I've tried with it's code in cvs.
did you remove share and lib/python ?
cd emc2; rm -rf share lib/python
cvs up -dP
checking /Python.h usability... no
checking /Python.h presence... no
checking for /Python.h... no
sudo apt-get build-dep emc2-axis
rayh: regarding the email you sent on the users list.. are you sure that the EMC on BDI 4.38 does have HOME_OFFSET ?
rayh: cause I really don't know..
Yes it does.
And having said that I'll got start up the box.
ok, you probably know more than me about that :)
Yep it's in there.
But you did make me look.
sorry for that :)
I'm not. Just been a long time since I'd worked with that system.
made you waste some time though :D
Do we want to put user and integrator "config" files in configs?
Or is it better to separate by chapter.
fortunately cradek can fix up the cvs if we make changes.
I'm not following..
what do you mean by putting user and integrator "config" files in configs ?
anything relevant to config goes in there
or should it be docs/src/kinematics
except hal stuff
that can work too, although maybe motion/ is a bit more general
and can hold a bit more than just the kins
TP and other bits and pieces
Okay. kins will go in motion
as will leadscrew comp.
I've got a ways to go with the python stuff and then I'll work some on getting kins in place.
ok, I added the first few bits to the integrator manual
I saw that. Thanks
Still have a problem with axis.
Linking python module hal.so
/usr/bin/ld: cannot open output file ../lib/python/hal.so: No such file or directory
did you cvs up -dP after the rm?
then a new configure && make ?
Yes to both.
and it did say I've got python stuff.
the hal.so needs to be built by the make process
but maybe the dir isn't there?
okay let me add a directory.
odd the dirs were in place and part of python built
the second make and I've got axis executable now.
nope the sim spindle is not set up in nist-lathe.
I think max has a simulated spindle
nist-lathe is the actual config that runs that lathe
* rayh looking
Shall I make a docs/src/motion directory in cvs?
Then kins and motmod lyx would reside there?
sounds good to me