EMC: 03bigjohnt 07v2_3_branch * r03045fce5e39 10/docs/src/gcode/coordinates.lyx: Update G92 offsets section and some general clean up.
EMC: 03bigjohnt 07v2_3_branch * ra5c23a8f8b96 10/docs/src/gcode/main.lyx: Add G10 L2 example
in the modbus component (gs2_vfd.c) I notice that some hal pins are declared as pointers and some not. Why?
It looks like the ones that are not pointers are RW and the pointers are IN or OUT. is that how it needs to be?
pins are pointers and parameters are not.
jthornton_ is now known as jthornton
so are the HAL_RW items parameters?
mozmck: in hal.h I see that RO/RW are for params, IN/OUT/IO are for pins
look at the name of the function that creates the item
a form of hal_pin_new vs hal_param_new
and yes the values for "direction" are also different
aha! thanks! I missed that it was hal_param for the ones created with RW.
mozmck: ideally everything should be pins
we started changing some params to pins, but it's a pita to get everything right
* alex_joni borked a couple things doing this, so I learned my lesson ;)
so what is the difference between them practically speaking?
Is there a way to get axis to display a message from a hal component?
be nice if it could
yeah, our THC sends an error code that I'd like to display as a human-readable message.
how is your thc component coming btw?
been side tracked working on getting radio line of sight internet
got that all hooked up now I just need to bury the conduits from the house to the garage for everything to go in
I just finished a 1' wide 18" deep ditch from the house to the garage... some was tough digging
about 120' long
ah, I need to finish a ditch about like that from house to shop about 180' long - for water and network cable and some other cable
yea, I'm tossing in datacom, water, power everything but the cat
is your error code an ascii string?
I dug most of the ditch a couple years ago by hand, but didn't have the materials or time to finish so it's halfway filled up now.
coming from the thc it is a byte where each bit means a different error.
mozmck: if your component uses rtapi_print
then it'll get to AXIS
you would not dig one here by hand all rock with red clay to hold it together
and get displayed
then I parse it in the component and make it a string.
alex_joni: this is a userspace component - can I use that from this?
[19:37:55] <jthornton> http://www.linuxcnc.org/docview/html//man/man3/rtapi_print.3rtapi.html
black clay here pretty bad. you can't dig if it's wet at all, and gets real hard when dry. I use a grubbing hoe and sharp-shooter.
thanks! says it can be called from user code...
what is a sharp-shooter?
hmm, long, narrow shovel with a short handle.
ok, know what that looks like
mozmck: yeah, from there too I think
grubbing hoe is like a pickaxe but with a heavy 3" wide end on it.
mozmck: the difference between params and pins is only philosophical :)
and besides you can't link things to params
think they call that one a maddax around here
I see. :-)
otoh a pin can behave exactly like a param (you use setp to set a value for it)
jthornton: here's some sharp-shooters. The top middle is what I'm used to http://www.hisco-okc.com/category.asp?idCategoryID=20
the middle picture on this page is what we call a grubbing hoe, looks like they call it a mattock: http://www.easydigging.com/Garden_Tool/pick_mattock.html
take a look at weighted_sum.c for some rtapi_msg examples
alex_joni: I'll just use pins then.
ok, thanks jthornton
* jthornton likes grep