machine is joint space, gcode is world/axis space
it makes no sense to read joint limits into gcode
what is the problem you're trying to solve that led you to think about adding this capability?
cradek: for no tool, i considered making all items 0 -- is that better?
yes I think they should always read as zero. I am not sure but maybe writing to them should be an error
the write has no effect, so I think the user should know that he's doing something unexpected
my tool table is in inches. I programmed G21 and then #5403=1. I get 1 inch, not 0.03937 inch in the tool table. I think this is right but I was a little surprised.
G21 G10 L1 P1 Z1 gives me 0.03937 in the tool table
G21 G10 L2 ... reads mm values for offsets but #5223=1 writes directly always in native units. you have done the same thing for tools which I think is right.
hm there is some incorrect interaction here
T1 M6 => Tool 1, Offset 1, diameter 0.125
G10 L1 P1 Z2 => Tool 1, Offset 2, diameter 0.125
#5410=0.1 => Tool 1, Offset 1, diameter 0.1
expected it to remain at Offset 2
G10 L1 P1 Z3 => Tool 1, Offset 3, diameter 0.125
expected it to remain at diameter 0.1
dgarr: ignore my rambling above "some incorrect interaction"
the values different from the expectations seem like real issues? so now i'm not sure what you are indicating should be ignored?
yes the values different from expected are bugs IMO
not sure what you are asking about ignored?
oh, now i see the "above" -- are the only issues you are remarking on are the values different from expectations after g10?
ignore my talk about units because I think it works right
ok, i'll study that
the thing I think is wrong is how #5410=0.1 changed both offset and diameter in that situation
also wrong that G10 L1 P1 Z3 changed both offset and diameter in that situation
the two methods are fighting somehow
EMC: 03cradek 07master * r2b2ac14fdd9a 10/src/emc/usr_intf/touchy/ (emc_interface.py touchy.glade touchy.py): fill out dro with abcuvw
EMC: 03cradek 07master * ra87ab2420b12 10/src/emc/usr_intf/touchy/ (emc_interface.py touchy.glade touchy.py): support various configurations of axes in touchy
ugh, there's so much more to that
maybe someone else will finish it (ha)
cradek: "Step towards the light" ;)
cradek: and some of it needs redoing for ja4
yeah it doesn't do kins
when (if) we fix jogging/teleop all the guis need a rework anyway
cradek: I just found the PERFECT clock for you... http://shop.tuxgraphics.org/electronic/detail_scope_clock.html
nah, I made my own crt clock
cradek: It's a o'scope clock
yeah, that's the easy way out
[Global Notice] Hi all, due to the memleak issues we are experiencing with hyperion (our ircd) we will be taking a handful of servers out of rotation for the production network in order to utilise them to better test our new ircd; ircd-seven. Affected users will be notified seperately. Apologies for the inconvenience.
EMC: 03cradek 07master * r2c75d7295464 10/src/emc/usr_intf/touchy/ (hal_interface.py touchy.glade touchy.py): Add jogwheel buttons and hal interface for the other axes
in dev is there any hal pin that would have the current programmed feed rate?
32770 float OUT 0 motion.current-vel
that is the current ACTUAL feed rate
current programmed, no
I'm needing to see if I'm within a percentage of programmed feed that that would be 1/2 of what I need
not sure how you would get that - F word is only a request - lots of things can slow you down
yes, and I only want make Z corrections if I'm close to the request
for the THC
would you want feed override included in the requested value?
and adaptive feed?
*that* number you could get with a few changes to motion - F word, no
I could get feed override from halui if needed :)
jt-plasma: I think you want what cradek suggests
for now - couldn't you add a something to halui that you could manually set a number that is the feedrate in the program?
the requested value wtih all overrides applied
skunkworks: the feed in the program is pretty irrelevant
say I program F9999999999999
my machine only does 10 on X, and 20 on Y
alex_joni: I don't think I understand what cradek is suggesting :/
I will be never close to the programmed F word
jt-plasma: let me explain
you have the F-word in the g-code (the F999999999999 above)
that gets scaled based on what the machine could possibly do (XYZ vels and TRAJ vel)
that new scaled velocity is sent to motion
it's still a requested feedrate, not sure the machine is really doing it
that requested feedrate then gets scaled with feed overrides (AF - which is probably 1 for you, and FO - which you can change)
a new requested feedrate is computed, and this one then gets used by the TP to generate the periodic waypoints
ok, but then that is a programming error on the cam side and in my case there would not be any correction and the cut would be bad
(now.. based on blending and whatnot, the real velocity will be similar to the requested, but not always equal)
because the speed is too fast to cut
jt-plasma: maybe it's best if you describe what you want to do
right, and if it is close enough I want to apply Z corrections as needed to maintain tip voltage
I need a couple of things for the THC comp, the requested feed rate and the requested tip voltage.
I think requested feed rate is the clamped velocity as explained above
if the actual feed rate is close enough then apply Z offsets to get the tip voltage within the tolerance window
if you programmed carefully then the clamped velocity == F-word in the g-code
carefully meaning under the machine constraints
go with cradek's suggestion then
23:44 < cradek> *that* number you could get with a few changes to motion - F word, no
jt-plasma: just beg nicely for cradek to add it ;)
* jt-plasma understands now :)
cradek: pretty please add that when you have some spare time :)
I went looking to see how "I" could change it but got lost in the forest because someone picked up my bread crumbs
alex_joni: thanks for clearing that up for me
I think someone ate them
brb, I need to go and check on a sick neighbor who is by himself to see if he needs anything
before it gets dark...
EMC: 03cradek 07master * r19be74094499 10/src/emc/ (5 files in 2 dirs): add motion.requested-vel output for jt's testing
cradek: you are awesome
don't thank me until you check and see if it works...