cradek: oh, is the low feedrate important?
I was so bored
thanks for finding and fixing
though I would have sworn I watched the first pass of the program..
thank heavens, that other commit I mentioned is something I've rashly backported to 2.3 as a performance fix
man. I really wish I had taken the time to write the "pyvcp panel generator" I started on
you need it now?
to generate a panel for all pins that match a given pattern
well, it would help with jimbo655 I think
generate a m5i20.0.*din* panel
so you'd get a bunch of LEDs that would be connected to all the inputs
twiddle switches and you can see which inputs change
yeah, some diagnostic panels could be handy.
I guess that would be doable with a generic LED array panel and some shell scripts
for a in `halcmd -s show pin $PATTERN` ...
all he needs to do is read the halcmd output, it isn't that hard
it's easier to look at a panel of LEDs to see which one toggles
or halscope or a bunch of halmeters
I was doing that tonight with the Hal Configuration window
you click on the watch tab I think? and select a pin and it puts an led up for it
I think that may update slowly or something
but it showed me that my multiplexed input was working when I shorted the switch...
the led blinked on and off...
EMC: 03micges 07master * r86253a297b84 10/src/emc/rs274ngc/ (interp_array.cc interp_check.cc interp_convert.cc): Add M67/M68 Enn Qnn - set analog output
EMC: 03micges 07master * rf1bd83105044 10/src/emc/task/emctaskmain.cc: Reenable code to check time spent in main task loop
EMC: 03micges 07master * r9c0e8f4c1a6f 10/src/emc/rs274ngc/ (interp_check.cc rs274ngc_return.hh): Improve P-word error detection and message
EMC: 03micges 07master * r2a8a98616eec 10/src/emc/rs274ngc/ (interp_check.cc rs274ngc_return.hh): Cleanup and update interp_check error messages
EMC: 03jepler 07master * r7058bc071cbd 10/ (4 files in 2 dirs): add a spindle speed output which is in revolutions per second
micges: on M67/68 how many outputs do you have?
as many as analog inputs
M67 is sync with motion like m62?
and M68 is like M64 turn on immediately?
exactly, (M67 will be, I'm writing code for this now :))
I saw your commit so I was trying to update the manual :)
Q is a float?
BigJohnT: imo to early for this commit
ok, I'll wait
there is no G5.2 G5.3 entry of manual
err gcode manual
what is it?
be back in a bit breakfast time
some high level NURBS gcode , ask cradek e will be know all info
I don't know much about it, but I have this file: http://timeguy.com/cradek-files/emc/Leto_art837759.pdf
it has some documentation, but not all
EBo is our expert in the nurbs code
YEA! you can cut and paste into lyx 1.5.3 with the keyboard
(the testing jeff and I did makes us think the nurbs code is not working right)
we did not spend much time on it.
should I wait to add it to the manual?
well part of why we couldn't test it is because we weren't sure how it works
I don't know what to recommend.
if it is not documented, surely nobody will ever use it
if nobody ever uses it, it will not get fixed
but, if we don't have a maintainer, it probably won't get fixed no matter what
I can add that it is experimental
and if that's the case, maybe it should be left undocumented or even removed.
ok that sounds smart
micges: one thing I'm thinking about (albeit not very much) is making the digital and analog inputs/outputs to belong to different modal groups
that way you can have both on the same line
but if they all use Pxx then forget it ;)
alex_joni: cool idea
micges: it can be needed sometimes
set an analog voltage, then set a DO to trigger something that works based on the voltage
I have M68 En Qn so it is possible
alex_joni: question I would like to ask is: why M66 have timeout defined in whole seconds not ms like everything else? (I problABLY asked this already)
micges: I looked at G4 I think
I don't remember any g-codes that work in msec ..
sorry. I mean I can G4 P0.2 and it will be wait 0.200ms, but when I M66 Q0.2 then will be no wat
even in message sended from canon timeout is integer field
hmm.. then it probably should :)
BigJohnT: Dallur said you are rewriting the thc stuff as a component?
yes I am
for a Mesa THC card
I see. will it be generic enough to work with others?
EMC: 03micges 07master * r1230f5972873 10/src/emc/rs274ngc/interp_convert.cc: Add check for correct digital P index with M62-M65
if they are sending a freq based on voltage
I'm going to try as I get some time to get the latest candcnc thc working in emc...
does it take over the Z axis like most others?
it sends up and down signals via two parport pins
the voltage is read in the thc card.
so it just has two bit pins that say go up or go down?
yes. it functions basically the same as the MP1000 that Dallur wrote his config for (same company made his)
so your comp needs to know when to apply the correction and how fast to move...
hmmm, yes I think. it would read the pins, and move Z up or down as fast as it can based on the inputs.
the speed would be limited by the settings in emc I guess
or maybe another setting
there is another pin to indicate a good arc, and there should be no movement without that.
in a nutshell I'm adding an offset to the commanded position if the torch is on and the X+Y velocity is above a threshold
once the torch goes off and the Z is moving up I remove the offset at a rate no faster than the Z is moving
anyhow, I thought I might could help on your component instead of duplicating efforts if it would work
so the Z only moves if X and Y are moving?
yes, you set the desired velocity and if it is within the velocity tolerance the offset is applied
kinda like a automagical corner height lock
oh I see. but otherwise you move the Z up and down based on the voltage reading.
so the Z slows down or stops moving as the x+y slows or stops for corners etc.
I guess the mesa card has a way to indicate if there is a good arc?
the plan at the moment is for no offset to be added if the X+Y velocity is below the min
no, that comes from the plasma cutter
how does it get to emc?
is it just a switch contact?
yes it is a dry contact inside of the plasma torch connected to a parallel port pin
I have a floating head with a micro switch.
so I Z down until the switch closes then move up a known distance then set Z to 0
that's what our setup uses as well, for touch off
then I move up to peirce height start the torch and wait for the arc ok from the plasma torch
after the peirce delay I move to cut height and take off
as soon as the velocity is up I'll make corrections as needed
sounds the same as our system.
how far along is your component?
about 3/4 I guess
I've chopped it up into bits to focus on each part of the process
yeah. best way I know. let me know if I can help on it.
I have not checked it in since I chopped it up so what is in dev is not working yet
I'm thinking the main part will be about the same as our thc. if the freq voltage reading were separated out to a different component, the thc component could have two input pins for up and down.
then those pins could be attached either to parport pins, or two the output pins from your component which reads the freq voltage from the mesa card
that would make it more compatable with the expensive THC systems
and that would make each comp simpler
I work for Tom at candcnc btw in case you didn't know...
I remember :)
I'm doing the emc stuff on my own time right now, but he wants me to get all our stuff working with emc at some point.
EMC: 03micges 07master * r0f15040e4f86 10/src/emc/ (6 files in 4 dirs): Allow M66 timeout to be fractional number
the only thing I can think of that you loose with a digital up/down is how much up and down is needed....
if it is a lot move faster if it is less than some distance don't bother moving...
a lot of move needed
hmm, the way ours works is it keeps the up/down on until the voltage is correct. the z should move until the signal turns off.
the z has to move fairly fast anyhow because the x+y on plasma move pretty fast.
we do some filtering and averaging in our thc processor, and don't move if the voltage is not far from the set point.
on our new thc most of those settings are adjustable (dead band, averaging)
so in your case if your split out the voltage reading part you could do some averaging in that comp.
I guess how fast the Z needs to move depends on the X+Y velocity and the lumpyness of the material
perhaps also have a z feedrate setting in the thc comp that could be set through a pin or something?
I'm thinking at the moment of using the set velocity to determine how fast the Z moves times some kind of parameter
if I set the velocity target to 100 move the Z at n speed and if it is 400 it would be n*4 or somthing like that
as far as I've seen it doesn't hurt anything for the Z to move faster even when the machine is not, or the material is flat.
but if it's too slow if definitely causes problems
it's basically a like a servo loop. just slower than an actual servo motor.
I'm just thinking of if it moves real fast when going slow there might be some over shoot
yea, I have a pid loop in there :)
why would the x+y velocity affect the over shoot of the z?
if there is overshoot there would be all the time wouldn't there?
at a given z speed that is...
I'm not sure, but my thought process is the slower your cutting the slower your correction needs to be...
and maybe I'm over complicating it
I think maybe so. you want the z to maintain the correct height as much as possible in spite of the cut speed - I think...
as long as it's not too fast that it overshoots and goes into oscillations...
it would be fairly easy to calc a correction speed based on a correction rate setting and set velocity
I don't guess I follow you there.
EMC: 03cradek 07master * r2947e10bd049 10/src/.gitignore: ignore tags files
EMC: 03cradek 07joints_axes3 * r730ea6ebfa33 10/src/emc/ (6 files in 5 dirs): Add analog_input and digital i/o to emctop
EMC: 03cradek 07joints_axes3 * ref2d09cca6b9 10/src/emc/usr_intf/axis/scripts/axis-remote.py: add axis-remote --mdi
EMC: 03cradek 07joints_axes3 * r8ef53f36ce7d 10/src/emc/usr_intf/axis/scripts/axis.py: Fix the previous commit.
EMC: 03cradek 07joints_axes3 * r4b145e62eed3 10/src/emc/rs274ngc/interp_read.cc: Allow N words before O words
EMC: 03cradek 07joints_axes3 * rf1bd83105044 10/src/emc/task/emctaskmain.cc: Reenable code to check time spent in main task loop
EMC: 03cradek 07joints_axes3 * ra5c7ab2f5ffa 10/src/emc/usr_intf/axis/scripts/axis.py: Added send_mdi_command to provide ability to send mdi commands remotely.
EMC: 03cradek 07joints_axes3 * rc296015c0a59 10/src/emc/usr_intf/stepconf/stepconf.py: . is dash-compatible, source is not
EMC: 03cradek 07joints_axes3 * r8890a5695ab0 10/debian/.gitignore: a new generated directory
EMC: 03cradek 07joints_axes3 * r86253a297b84 10/src/emc/rs274ngc/ (interp_array.cc interp_check.cc interp_convert.cc): Add M67/M68 Enn Qnn - set analog output
EMC: 03cradek 07joints_axes3 * r480301507e4b 10/tcl/bin/pickconfig.tcl: fix systems where the directory name "Desktop" is localized
EMC: 03cradek 07joints_axes3 * r9c0e8f4c1a6f 10/src/emc/rs274ngc/ (interp_check.cc rs274ngc_return.hh): Improve P-word error detection and message
EMC: 03cradek 07joints_axes3 * ra154c59995e9 10/src/emc/usr_intf/axis/extensions/emcmodule.cc: Fix incorrect backplot when motion is very slow
EMC: 03cradek 07joints_axes3 * r2a8a98616eec 10/src/emc/rs274ngc/ (interp_check.cc rs274ngc_return.hh): Cleanup and update interp_check error messages
EMC: 03cradek 07joints_axes3 * r0737558561d8 10/src/hal/user_comps/pyvcp.py: Add usage info to / cleanup of changes to pyvcp
EMC: 03cradek 07joints_axes3 * r7058bc071cbd 10/ (4 files in 2 dirs): add a spindle speed output which is in revolutions per second
EMC: 03cradek 07joints_axes3 * r1230f5972873 10/src/emc/rs274ngc/interp_convert.cc: Add check for correct digital P index with M62-M65
EMC: 03cradek 07joints_axes3 * r0f15040e4f86 10/src/emc/ (6 files in 4 dirs): Allow M66 timeout to be fractional number
EMC: 03cradek 07joints_axes3 * r74d5e3f2bdba 10/src/emc/usr_intf/axis/extensions/emcmodule.cc: Remove more unused fields from emc.stat
EMC: 03cradek 07joints_axes3 * rd6266fd4b92f 10/src/emc/ (5 files in 4 dirs): Add analog_input to EMC_MOTION_STAT and emctop
EMC: 03cradek 07joints_axes3 * r2947e10bd049 10/src/.gitignore: ignore tags files
EMC: 03cradek 07joints_axes3 * r5cfc9cc48a95 10/src/emc/ (4 files in 2 dirs): Remove old AUX io code
EMC: 03cradek 07joints_axes3 * rdf5c85a65c92 10/src/emc/motion/ (command.c control.c mot_priv.h motion.c motion.h): Enable analog_input code in motion
EMC: 03cradek 07joints_axes3 * r8665663b5a8d 10/src/emc/ (4 files in 2 dirs): Remove unused EMC_AUX_AIO_WRITE
EMC: 03cradek 07joints_axes3 * r3b99b93a100a 10/src/emc/usr_intf/stepconf/stepconf.py: stepconf fixes for non-standard directory installs
EMC: 03cradek 07joints_axes3 * r99db5d2e7d40 10/src/emc/ (task/emctaskmain.cc usr_intf/axis/extensions/emcmodule.cc): Add ability to change digital/analog output from python code
was that a "keep the branch current" push?
on the commit list, each commit is tagged with the original author's name, but in here they are all cradek
yes that's all it was
here the name is the 'pusher', in the email it's the author
cradek: will be ok that I will work little on joint_axes3, or you have some bigger stuff to work at it?
I'm not working on it, I'm only keeping it up to date so interested persons can work on it easily
it runs but I have not even tested it much.
I just did a small edit on main.lyx and now I get some errors when I run make http://pastebin.ca/1483975
is your disk full?
I don't know... let me check
I don't really a meaningful error except broken pipe on write - maybe I'm just not spotting it
the docs/src/lyxtree.py stuff
and the lyx2lyx
I've never seen that before
yeah I see that, but it doesn't mean anything to me :-)
sorry for being obscure
still guessing full disk or something else goofy like that
it says I have 164 Gb free space
might have to wait for jepler - I don't know what it means
ok, thanks for looking
meanwhile, I'm procrastinating cutting a single point thread on a $45 part that has to be perfect - and I only have one
don't have any test material laying about?
it's steel and I don't have any other steel that big
I guess I really should cut it in Al first though.
it won't act too differently I suppose
Just this once .. here's the log: http://www.linuxcnc.org/irc/irc.freenode.net:6667/emcdevel/2009-07-04.txt
* alex_mobile is a daddy
alex_mobile: everyone doing well??
bjt: that error doesn't mean anything to me. if you can send me the file you were editing (gcode_main.lyx?) can see if it happens here.
there are two python tracebacks there. the top one seems incomplete. the bottom is after the error occurred, whatever it was, and is only a symptom, not a cause
cradek: yeah, everyone doing well
it looks like it's probably my own fault that the top one is incomplete. but I still will need the lyx file to diagnose / fix the problem.
good night all
yay, my tricky thread came out right
EMC: 03jepler 07master * r373fc0df17ee 10/docs/src/gcode/main.lyx: fix typo
g-G95 is Units per Reveloution Mode.
+G95 is Units per Revoloution Mode.
well I *tried* to fix the typo
EMC: 03jepler 07master * ra94d9a9ddc63 10/docs/src/gcode/main.lyx: fix typo harder
well "reveloution" is pretty amazing
EMC: 03jepler 07v2_3_branch * r2462dbce0902 10/docs/src/gcode/main.lyx: fix typo
how'd I do this time?
I'm scared to look
I don't blame you
I am tempted to do this and push the result: $git merge --strategy=ours origin/joints_axes origin/joints_axes2
(while on joints_axes3)
what does ours do?
it means "make the result of the merge exactly what's in this tree" (it ignores the actual contents of the other two trees)
you could rename them (all three) so it's obvious which are the old ones
this makes them all lead into the current branch. then, in git rules, you can delete the other branches
it's probably not really a sensible thing to do
EMC: 03jepler 07master * r5b74f31c07be 10/src/emc/sai/saicanon.cc: print out this canon message