EMC: 03jepler 07TRUNK * 10emc2/src/emc/rs274ngc/interp_read.cc: fix reporting of error with illegal character values above 127
sadly, all my matrox cards that gave me direct rendering without latency problems on dapper fail to do that same thing on hardy
that sucks.... would be interesting to see the driver diffs to see what they broke
it's no big deal - direct rendering isn't needed for AXIS
EMC: 03seb 07TRUNK * 10emc2/src/libnml/nml/nml.cc: fix a segfault (robotic code review ftw)
EMC: 03seb 07TRUNK * 10emc2/src/hal/utils/halrmt.c: fix an array overrun
think I wrote that one...
EMC: 03seb 07TRUNK * 10emc2/src/libnml/cms/tcp_srv.cc:
EMC: Fix a segfault.
EMC: unregister_port() dereferences client_ports willy-nilly, so let's only
EMC: call it if client_ports is not NULL
EMC: 03seb 07TRUNK * 10emc2/src/libnml/buffer/memsem.cc: fix a segfault
EMC: 03seb 07TRUNK * 10emc2/src/hal/utils/halrmt.c: fix a memory leak
EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/ (5 files): changes to put filename into shared memory so ladder remembers filename when GUI is reloaded-fixes SAVE button not working when GUI is loaded with axis
EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/config_gtk.c: fix update of MODBUS request array
EMC: 03seb 07TRUNK * 10emc2/src/emc/ini/initraj.cc: reverse the order of the checking to avoid an access-past-end-of-array error
EMC: 03cmorley 07TRUNK * 10emc2/src/hal/classicladder/zEMC_README.txt: update
Just this once .. here's the log: http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2008-11-21.txt
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/classic_ladder.lyx: remove note about save not working thanks for fixing this Chris
EMC: 03cradek 07TRUNK * 10emc2/debian/changelog: another new feature
what does halui.max-velocity.count do?
it lets you hook up an encoder to control the new velocity limit, I imagine
halui stuff has 'counts' wherever a normal gui would have sliders
does that have a corresponding enable input (like the various jog count inputs)?
so you can share a single encoder among several .count inputs
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gui/axis.lyx:
EMC: another new feature to the manual
SWPadnos: no, I think that is missing from all the halui inputs
right, encoder jogging was moved into motion
which has them
I assume without testing that increase and decrease are for a faster and slower button of some sort either real or pyVCP ...
works just like the feed-override inputs
increase/decrease by 'scale' value, and/or use counts
I was just fixing to ask that one :)
I agree that someone should add enables to the halui encoder-type inputs
if that was the question
I also agree that someone should do that
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gui/halui.lyx: add max vel info
I third the motion
I nominate SWPadnos to do this, since he brought it up
thanks, I accept
I second the nomination
there's no time limit though, right?
before 2.3 comes out
it'll only take you a few minutes
(really, I bet so)
ok, as long as we delay 2.3 untli I'm done ;)
* BigJohnT goes to throw more wood on the fire and find his hip boots
well, it would take someone else just a few minutes, but I'd have to make a macro-like thing for all of the "standard" kinds of things that halui uses, like toggles and encoders and stuff
otherwise it would be hack-ish
huh, now what's missing from these photos? http://cgi.ebay.com/HIGH-TORQUE-1125-OZ-IN-STEPPER-MOTOR-42-FRAME-STEP_W0QQitemZ260294804197QQihZ016QQcategoryZ41942QQssPageNameZWDVWQQrdZ1QQcmdZViewItem
well it may be hidden, but it's hard to tell
(here's a hint, how does the electricity get into the motor?)
it's like all laptop auctions on ebay: "think it works but I can't check because I don't have <this>"
I'm thinking it may be a new motor for the, um, wireless age :)
we have a ton of steppers that have screw terminals under the back cover
can you send me a few?
heh - I think all we have are accounted for projects.
I've got a G540 on the way, and I have no motors to run with it
I don't want to spend a lot on motors just so I can make an EMC2 config for it :)
$19 from automation direct
yeah, tiny though
yea, how big do you need?
well, I'd like them to be potentially useful
whatever that means
LOL, did you purchase the 540 with a project in mind?
no, Mariss is sending it to me on a 1E6 year loan :)
what is 1E6?
1 * 10^6 (1 million)
that is a long time
yeah. I hope he doesn't mind if I forget by then :)
he seems like a nice guy to deal with the time I spoke with him
so nema 23 size?
actually, NEMA34 could be directly attached to my Bridgeport for testing
I guess the G251 specs limit the motor size a bit anyway, so maybe I will get some from AD
the 23's are $29 and $39
I use the $39 ones on my plasma table
how do they perform?
they do real will with the G203v
are you around 50V?
oh, right :)
no I'm at 60+ I forget exactly
ah, ok. that's the 276 oz-in one, at 3.82 mH
62.54V is optimal
I think it is the Antek ps-6n63rxx at 63 nominal
(according to the 32*sqrt(L) formula)
yep, should be about perfect
a bit high for the G251 though, which tops out at 50V
I had to look all that up when I bought it :)
the 166 oz-in motor from AD is pretty ideal for the G251, but they're out of stock (and seem so small ;) )
I ran them for a while on a 24v power supply here in the beer cave and got the results I expected from the lower voltage
I thought the 540 was only good for 3a or there abouts
It is a nice package.
* BigJohnT heads for town
talk to you guys later
EMC: 03cmorley 07v2_2_branch * 10emc2/src/hal/classicladder/ (5 files): change to put filename into shared memory so CL remembers filename when GUI closes-makes SAVE button works in AXIS. Also fix so CL will load a new ladder progra-if REopenned with a filename- instead of ignoring it
Hi guys ! small question. How does one set the level so that rtapi_print_msg are printed?
scho level > /proc/rtapi/debug_level I think
check the proc dir for the correct name :)
no rtai in my proc directory
it's only there when the RT system is loaded
and it's RTAPI, not RTAI
(lower case though)
sorry ya thats what I meant
Then how do I get debug messages to print when running simulator code?
uh. good question
maybe I wasn't clearr about what I am doing..
you can set debug level in an ini file, but I don't know for sure if that affects the "RT" debug level
in classicladder someone wrapped my lines like this: rtapi_print_msg(RTAPI_MSG_INFO, "Loading ladder GUI\n");
Now I want it to print
I read some where that I have to set a 'level' not exactly sure what was meant..
well, for an RT system you'd use the /proc entry. I'm not sure how to do it for a sim system
Is there a level for EMC that is set when run?
yes, that's DEBUG_LEVEL in the ini file, but I'm not sure if that affects the "RT" system
EMC also has its own message levels
K I'm sure that is what is meant- how do you set them?
edit the ini file
but again, I don't know if that sets the RTAPI message level
right ok. There must be another way -I hope not using EMC just HAL
well, lemme look around (and hope somebody who knows the answer shows up in the meantime :) )
lol ok Thanks. I checked man pages they don't even mention rtapi_print_msg
huh. it looks like all messages are printed in sim, they just go to stdout vs. stderr
depending on the level
and anything other than RTAPI_MSG_ALL goes to stderr
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gui/halui.lyx: a bit more for max vel
next dumb question how do I see stderr ? :)
run in a terminal and you'll see both stderr and stdout
Lerman_____ is now known as Lerman
SWPadnos ok I didn't know they both were displayed . Thanks
you can pipe them to different files if you like
something like emc 2>stderr.txt
that would send stderr to the text file, but still show stdout
on the terminal
It doesn't display the messages though there must be more to it. I see I can run halrun with -v for more messages but that seems to fail...
I may be wrong about it, but looking at the source leads me to believe that's how it's done (msg_all prints to stdout, all else to stderr)
I see in the man pages : int rtapi_set_msg_level(int level) so something has to set it to make it print...
oh hmm. that's just one mesasge handler I looked at
the level is set to some default, I'm just not sure what that default is
of course, if you're already compiling for yourself, you could just change the default in src/rtapi/sim_common.h
it's probably something simple that I'm missing or it's impossible :)
ya I agree.. I will leave a message in the maillist ! thanks for your help though!
are you compiling for yourself?
Yes I maintain Classicladder for the EMC group.
heh, didn't know that
And try to hide my ignorance ...lol
so change the default and recompile
it should only take a couple of minutes
FWIW, I don't see the message you pasted here, but I do see a couple of others from CL (specifically one whenever I close the GUI)
though I should update and check again
Some messages are not wrapped so they will print no matter what.
are you talking about the '\n's?
ah, wrapped in rtapi_print_msg instead of stock printf?
some messages just use rtapi_print
I think Chris broke CVS with his last commit :)
uumm no it was John!
I guess I was last
hmm, cvs.linuxcnc.org must be broken
indeed. and yet jepler is still attached (or so it seems)
I'll reboot the hosting machine in a few minutes
that should bring it back
I wonder if it noticed that there's a new version out
oh it hasn't been updated in years
that's probably not it then :)
(jus a coincidence that I got an update email a few minutes ago)
cvs should be back now
huh. interesting dm_crypt question
I wonder if that affects RT latency