i sjeff still around?
I have one question about the recent rtapi_request_region
we just got back to the motel, he may go right to bed
he and I left "early" tonight
ok, then maybe tomorrow morning :)
yeah, I can see that 'early'
it seems strange that rtapi_request_region returns -1 for platforms that don't have request_region.. that will make it always fail... I think?
hmm, I'm sure he intended it to always succeed
that's what I thought too..
well not sure, but I think he said something about that being the intent
maybe it's just a mistake
well, otoh it's early here.. I might be reading the commit diffs wrong
tomorrow/later can you help us add a couple gcodes and an nml message? we're doing edm stuff (feed override from a hal pin) and need gcodes to enable/disable the adaptive feed
I tried a little today but it didn't work out for me
can you be a bit more specific?
doesn't the comment say 0 (NULL) is failure and any other value is success? that's the behavior of the kernel 2.6 API.
so I can start working
Maybe returning 1 would be better than -1
I don't know
did we decide to use g50 and g51?
I think so
G50 = enable adaptive feedrate control
the message should be something like ENABLE ADAPTIVE_FEED / DISABLE_ACTIVE_FEED
G51 = disable adaptive feedrate control
the motion controller part is under construction now
the canon call should be named something similar
the interface in motion.h is already defined, and I can write the function(s) in taskintf.cc
good question, should it be functions (one to enable, one to disable)?
or one functions to set either on or off
MIST_ON(), MIST_OFF() seem to be how canon usually works
ok, consistency is good
ok, so basicly G50 & G51
G50 = on, G51 = off
any other params?
any limitations? as in what other g-codes are allowed on the same line?
wow questions I wouldn't even think to ask
* alex_joni is thinking about the group to stick them in
don't think so... on or off remains in effect until changed
similar to mist on/off, flood on/off, etc
ok, I'll look & see ;)
those aren't really g-codes afaik :D
are they M codes?
if ever used :)
but that shouldn't matter
this sounds more like Gxx than Mxx (the adaptive stuff)
but are m codes more appropriate?
mist and flood have no effect on motion, so they're a bit different
I think Mxx is appropiate for I/O
maybe that's the difference
and Gxx for motion
or any other related stuff
this is essentially g33, with a different pin used for the sync input
SWPadnos: don't go there .. or chris will want the G33 to work as on/off ;)
that's what I want, so :P
wait - maybe that isn't what I want
SWPadnos: face it.. you don't know what you want
this is strange, here are all the people I know well; at the workshop are some similar people but they're sort of strangers still
it's probably just one of those strange 2am feelings
2am - argh!
some are stranger than others
cradek: does it consolate you if I feel the same?
I resemble that remark
although I don't know the fest people at all :))
alex_joni: a little
alex_joni: they seem familiar somehow
familiar: a msall animal, used to hold your magic powers
i cnat ytpe at 2am
we cna rdea tohugh
crap - I have a customer who's going to call at ~10 this morning. I guess it's time to get to sleep
sounds like it..
nighty night folks.
jmkasunich: I just did most of the upper parts
1. task to recognize the new NML message
2. usrmotintf.cc to provide some functions for starting/stopping the adaptive control
3. task calling those
jmkasunich: bring specific questions in here
will do that
got the big picture?
I see START_ADAPTIVE_FEED() in emccannon.cc
thats the problem
ok, that sends a NML message
I know I need to write something in taskintf.cc, but I have no idea how it gets from START_ADAPTIVE_FEED() to the funct I will write
START_ADAPTIVE_FEED() sends a NML message to task
task traps it in one of those big switches
and calls the usrmotintf.cc function
lets do it like this:
you implement the taskintf function
and let me worry about task in a couple of hours (1-2)
the big switches are in emctaskmain.cc, right?
try following EMC_MOTION_SET_DOUT
the new one will be similar to EMC_TRAJ_SET_SCALE I think
named EMC_TRAJ_something anyway
the userintf.cc function(s) can be done one of two ways
1) one for one, one for off
2) one funct, passed a param for on or off
I kinda want do do "int emcTrajSetAdaptiveFeed(int enable)"
will that work for you?
I did only one NML message to keep the count down
int status (status=0 disable, =1 enable)
but taskintf.cc is more appropiate
sorry, stepped away for a big
more like a byte :)
but me too..
taskintf.cc part is done....
waiting for the mails
ok, looks about right ;)
I'll do the rest in a short while.. ok?
alex_joni: I'm not sure what part I'm missing, but I think I have it mostly right
unfortunately you can't load any gcode without an error
do you want me to check it in so you can figure out what I did wrong?
yup, that sounds ok
ok just a sec
it's not TESTING.. so ho ahead
what's the actual error?
if I mdi g50 it says 'two g codes used from same modal group'
I think I also get various other errors loading programs
that's an odd snip of code generating that error message
oh, finally got to understand it ;)
alex_joni: are you getting anywhere?
cradek: just starting, but I have a hunch
give me a couple of minutes
ok, I think I spotted it
I even tested ;)
ok, task is next
jepler: could you ask cradek if this fixes it?
what is g50/51? scaling and mirroring?
skunkworks: no, it's for EDM
starts/stops automatic adaptive feed based on a feedback (arc voltage or whatever)
some input controls feed
right, but only slowing down
alex_joni: we're looking
I still am seeing weird behaviour
somehow the wrong NML message seems to get sent
hm I wonder if the numbers got assigned wrong or something
programs that don't use g50/g51 run, though?
and g51/g50 can be issued
hang on 5 more minutes
we've got 5 minutes
can you ask jmk or cradek how I know if the stuff reached motion?
only the debug print to syslog?
yes, the debug prints are the way
it might be there already
yeah, they are
and they show up :) yay
G50 -> off ?, G51 -> On?
motion has it backwards :D I'll change
ok cradek says that was backwards too
over here we've hard-coded the override on, and cradek and jmk are changing the lathe speed with a joystick
I'll soon be done, I want to add it to the current active gcodes
or whatever it's called
speaking of which, in axis I need to know how many items are in the active gcode array. how can I tell that?
hm, can I use sizeof()?
oh forget it, they're constants already
if you say so :P
^^^ in axis code
#define ACTIVE_M_CODES RS274NGC_ACTIVE_M_CODES
make sure you bump RS274NGC_ACTIVE_G_CODES
make abi bunp
do we have an ABI?
ok, now it's the proper way around (hint: don't mix 'int' with 'unsigned char')
jepler: hopefully not
I think the ABI is "if it's broken, you should recompile"
now they've discovered some breakage in pause and abort for g33 apparently caused by the feed override changes
jepler: can you try the latest fix on AXIS? (active g-codes)
I only have an installed axis, along with emc2 (2.0.0)
yes I will change it
but we've got a bigger problem: all blending seems to have been disabled
oops.. was that by the adaptive stuff ?
I'm not sure yet
I'm trying to isolate the change
I'm looking at http://cvs.linuxcnc.org/cvs/emc2/src/emc/kinematics/tp.c.diff?r1=1.48;r2=1.49
, wonder where the setVscale is now..
oh, nm.. I get it now (it's handled in the motion controller, already scaled, not in the TP anymore)
so.. what else are you working on now?
I think the bug was introduced between 8:15 and 8:30 UTC
you can find those commits on the list
alex_joni: smithy is taking us all to dinner now
after that I intend to get enough sleep for one night, but I think the rest will come back
but it's likely to be 2 hours
so "see ya tomorrow"
ray is talking about having a board meeting but I don't know the details
ok, I guess I won't stay up another 2 hours ;)
maybe something like 10-15 minutes
catch you tomorrow
ok someone on the board will let you know about the meeting
ok, I'll be online tomorrow throughout the day, except between 2PM and 6PM GMT I think
ok, I'm off to sleep
catch you guys later (in a couple of hours)