jepler: haltcl sounds neat. If i understand, one can include both current hal files and .tcl files in the ini file as long as the appropriate syntax is used in each?
for interactivity, tkcon might be useful -- you can source a tcl file and then open the powerful tkcon console
there's already a tcl interface to hal, but this makes tcl files usable as [HAL]HALFILEs and adds some sugar like automatic [expr] for the argument of setp..
good morning all
EMC: 03micges 07joints_axes3 * r9d8a404ed4ea 10/src/emc/usr_intf/axis/scripts/axis.py: Make override limits working in Axis
EMC: 03micges 07joints_axes3 * rd644a65c0866 10/src/emc/usr_intf/axis/scripts/axis.py: Fix bug that override limits is grayed out when machine is on limit
SWPadnos_ is now known as SWPadnos
I think feedoverride shouldn't be applied to jog moves, what do you think?
micges_work: why not?
because it doesn't work in ja3
that's not a reason ;)
when you operate machine by FO, when you stop machine you don't have to mess up with FO to fast jog machine to show material cutted
but maybe thats also not a reason ;)
our solution was added "M50 P0" to escape key
but thats is less important
EMC: 03micges 07joints_axes3 * r31e2431ecd5c 10/src/emc/motion/ (control.c mot_priv.h motion.c): Add joint free planner current velocity HAL pin
alex_joni: Played with the puma560 - very neat. cool seeing it virtually cut tux ;)
skunkworks928: run it in sim, not RT, if you can
I saw that the kins have some issues once in a while
sometimes the joint values passed to the kins are 0,0,0,0,0,0
and that's a singularity where the inverse doesn't work
skunkworks928: you can switch to joint mode, jog the joints to another configuration, then switch back to world mode, and play with it some more
and the ABC mappings aren't quite right
actually .. they are right, but hard to define ;)
I think you can have more than one set of ABC angles for the same orientation
I did have some issues where it seemed like I couldn't issue a mdi command. It would seem like it would start to move then stop. could jog though
then the mdi commands seemed to work.
did you try to MDI outside the working range?
I don't think so because I could jog it there.
and then it went there after I jogged - but I will play with it some more :)
the abc mapings are a bit above my head (hard to wrap my head around the movements. seems to keep tool tip in the correct location though :)
bbl - have to go to work
yeah, the kins seem to be working ok
once it's working ok, we'll have to add a tool ;)
I am surprised how well the kins are working
:) I am not
EMC: 03micges 07joints_axes3 * r352c55515bf3 10/src/emc/motion/control.c: Execute free mode planner calculation only when joint is active, some small cleanup
skunkworks928: at about 5800 lines of code, I am
EMC: 03alex_joni 07master * rc3c910214b0b 10/lib/python/vismach.py: remove debug prints
[Global Notice] Hi all, I'm about to do some re-hubbing and take some servers down in preparation for todays maintenance, it will be somewhat noisy as I swap things around but shouldn't take particularly long. Apologies for the inconvenience, thank you for flying freenode and have a great day!
[12:24:01] <alex_joni> http://juve.ro/blog-files/puma/puma-tux2.jpg
hm -- the hostmot2 5i20.ucf file doesn't specify the IOSTANDARD of the IOBITS<> pins. Are they LVTTL?
EMC: 03jepler 07master * r776f70787178 10/src/autogen.sh: make sure timestamps are updated
Oops, probably relied on the GUI for setting the IOSTANDARD and missed something
I'll fix that and update the 5I20 bit files.
Unfortunately the source has diverged significantly because I changed the setup to 1 file per
pinout (so there's no longer a giant ball of all pinouts file) and got rid of the per card type top level files
thanks for the clarification
I don't think we have any local changes in the firmware files; they'd be useless since we don't build the firmwares ourselves anyway
but if explicitl IOSTANDARD settings are in the source next time we update the files, that'd be dandy
I think JMK made soe scripts for command line building that my new source will break :-(
he and I have both worked on that at times, but none of it is actually being used
I still would like to be able to do a commandline build from our source tree but I'm short on round tuits, and the practical benefit is small
I think the new source will actually make it easier FWIW
So I'll fix the .ucf file and make new 5I20 bitfiles.
What to do about the source? (many files deleted and added)
unless you want to learn git, I guess just send a zip or tar file and we'll replace what's there now with the new stuff
the new source control management software is much better about adding/removing files and directories than cvs was
bbl, it's lunchtime here
OK I'll send a snapshot
File "/home/chris/emc2.trunk/lib/python/rs274/glcanon.py", line 78, in draw_dwells
if lathe: axis = 1
NameError: global name 'lathe' is not defined
thanks, will look
I did most of the gl refactor in a private branch, but I did push the first commit :-/
wheeeee! my "new" servo amps work
I have to turn all the little knobs a bit more, but things look good.
what a relief
if you just want to get running, delete the 'if lathe' line
I hope to push a fix in just a minute
cradek: from moses?
nope, from ebay
the stuff from moses is not exactly the same - good for parts
wow - cool
EMC: 03jepler 07master * rb6eee9ec1bd6 10/ (2 files in 2 dirs): fix failure to load lathe programs with dwells
git rebase is cool
jepler: this wasn't a lathe
cradek: it wasn't?
oh I guess it wasn't ..
so my commit message was pretty bad, wasn't it
I think the fix is right
anyway, with rebase I've been able to work on this branch for days, make multiple commits, and just now incorporate the fix I made on master
all with a nice linear history, so I can post it as a changeset if I want
uh-oh, help me with git here
oh, you had your local edit and then pulled?
no, I haven't pulled yet
then you want to 'git checkout glcanon.py' before you do
cradek: still have the spindle problem?
locally, I have a (now out of date) master with random_toolchange merged into it
should I reset --hard to origin/master, then pull, then remerge?
seems like a plain pull won't just work
skunkworks928: yep but I have a vfd on the way (should be here tomorrow)
as long as you don't have any changes not on origin/master or origin/random_toolchange
throw money at it - problems go away
oh just try a pull?
.. that you want to retain
oh you're saying that yes I should do what I said earlier?
yes, I think that's a sensible thing to do as long as you don't have any local changes (committed or uncommitted) that you care about
in the branch you're currently on
right, I don't
though just fetching and merging origin/master might be fine too
after discarding the change to glcanon.py that would generate a merge conflict, anyway
looks like it worked...
cradek, what VFD u replacing with? im still looking around whats out there for our spindle motor
a reliance electric 7.5hp 230v drive
jepler: that fixed it - thank you
with brake resistors? have to let us know how it works out be very intrested to see how responsive it is
aah baldor drives i did take a look at theres
cradek: thanks for noticing it
it's a reminder that maybe I should do more than load the splash screen