damn you guys talk a lot
and then run away
gotta go out in the garage and do some machining
if seb shows up, somebody come out and get me
I think I have new-run-from-line working here
the question is what to do with it now
you can prepare the machine for restart using any function of manual or mdi modes, then it starts reading gcode at the line you specify, completely ignoring everything above it in the file
you can even set variables in MDI before running
I've tried all sorts of restarts in different files and I am always able to "get what I want" using this method
yay - more tomorrow - goodnight
[Global Notice] Happy Software Freedom Day! I hope you're all marking the day and spreading the word -- if you haven't yet considered marking SFD, check out http://cgi.softwarefreedomday.org/map.shtml
to see if there is a local event you can attend! Have a great day!
cradek: sounds good, did you try messing with o-word loops and functions?
.. the case I specifically wonder about is where functions are defined at the top and called after the restart point ..
it would be nice if that worked, though you could also adopt a "functions at the bottom" style
jepler: I think you need to define a function before you call it
otherwise the interp starts opening files with the same name as the function name.. I think
If it can't find a file by that name, then it searches the current file to the end.
ah, ok.. so that works then :)
Yes. Although it is not clear that the order I do things is the "best" order.
oh, surely each other order will have it's supporters :D
I did it that way to avoid searching the entire file.
It winds up that the whole idea of multiple files is a loser because the rest of the system (GUI, etc) doesn't support it.
A better approach, I think, might be to have a (for Axis) filter that reads the file and incorporates any necessary files into what is passed to Axis.
For non-Axis users, the files could be processed by a script after they were created.
I've written a version that goes through a directory tree and includes everything. A future version could incorporate only those that are referenced.
hmm.. short question
how hard would it be to interpret a file up to a certain line, and generate a list of modal codes up to there?
then check that against the current modal codes, and generate a diff..
I'm thinking about run-from-line..
if you select you want to restart from line 1000
Off hand, I don't know. Remember though, that with o-words, running up to a certain line is not a complete description since the line might be executed multiple times.
yeah, I'd be tempted to disallow run-from-line inside o-word or such
otherwise you get to implement a complete debugger
with run from line, step into, step over, set params, whatever..
Correct. Wouldn't that be nice to have? :-)
well.. nice .. maybe ;)
The interpreter "know" what modal codes are set at any point in execution. We could add an option to output the line number and the current modal codes as each line is executed.
That would provide all the information you need. Process it with some scripts.
Of course, that assumes there is no probing or other input operations that can change the flow of control.
For reasonably sized files, we could add a structure in memory to keep track of all of that.
I assume that modal codes includes things like Swords (speed), current coordinate system, values of offsets in each coordinate system, etc.
That can amount to a lot of stuff. In fact, all of the variables need to be saved. That includes both numeric and named parameters.
To make it *always* work, you need to have *everything*.
Assuming that there are no probes, I think the best way is to actually run up to that point, but disable all motions.
hmm.. that's tricky
imagine Mxx commands that generate fixture moves or whatever
ah the good old days http://axis.unpy.net/01102370471
(that was 2004)
(I wish it would show the date on the entry page -- I should fix that)
GMT: Mon, 06 Dec 2004 22:01:11 GMT
jepler: import time
I know how to convert that number to a date
I just have to write the code to display it on the page
yeah, I know :)
[13:38:29] <alex_joni> http://www.epochconverter.com/
<- handy convert codes in a couple of languages/environments
aha, that's better. http://axis.unpy.net/01102716853
jepler: I think it's pretty clear that won't run the function, it'l give an error that the function isn't defined
oh I forgot that 'verify' is killed by this change
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/images/ (12 files): new classicladder screen shots
how do I unremove a file from a cvs remove that I have not commited yet?
EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/gcode/main.lyx: add g95 is not for threading
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/images/ (4 files): add the rest of the graphics
anyone know what \menuseperator does when loading classicladder?
BigJohnT: It's intended as a standard way to mark up the location of an item inside a menu. You'd use it where you might instead write ">" to denote "File > Open"
it seems like classicladder is on the menu of Axis loaded or not
or do I misunderstand what you mean :)
BigJohnT: maybe I misunderstood what you are asking
it was in the docs...
docs/src/ladder/classic_ladder.lyx:539:--help \SpecialChar \menuseparator
no, one moment
in the classicladder manual it showed an example of loadusr classicladder --nogui \menuseperator
i was wondering what the \menuseperator did when loading classicladder...
ok then I am answering the right question
The LyX source says "\SpecialChar \menuseparator". In the lyx gui and in the pdf files, this gives a closed, right-pointing triangle which is intended to separate parts of a menu.
It is intended to be used in place of ">" to denote the location of an item inside the menu, the "File > Open" example I mentioned a moment ago
ok I understand now
I don't know who used that here, or why -- I don't think it's a sensible use of it
np it's gone :)
but in any case, the html documentation doesn't translate it correctly, it just writes \menuseparator into the output
thanks for the help jepler
hm what was the name of that extra package for building docs in TRUNK?
my memory is too short
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/common/Linux_FAQ.lyx: added info about the magic -L to find
EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/common/Linux_FAQ.lyx: added info about the magic -L to find
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/ (classic_ladder.lyx ladder_intro.lyx ladder_intro_fr.lyx): almost done adding new classicladder info
EMC: 03jepler 07TRUNK * 10emc2/docs/src/lyxtree.py: handle 'menuseparator' special character
(huh, \SpecialChar \menuseparator got turned into \backslash menuseparator somewhere there in history .. I wonder how ..)
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/ladder/classic_ladder.lyx: what comes first spell checking or commiting :) fix a bunch of typos
EMC: 03seb 07TRUNK * 10emc2/docs/man/man9/hostmot2.9: Made raw.dump_state a HAL_IO pin, which is what it is. Minor documentation improvements.
EMC: 03seb 07TRUNK * 10emc2/src/hal/drivers/mesa-hostmot2/ (README TODO raw.c): Made raw.dump_state a HAL_IO pin, which is what it is. Minor documentation improvements.
jepler: I just did a grep on \menuseperator and it is no longer in any docs in trunk
nore is it in 2.2.x, it must have been something in the text file that Chris Morley sent me :)
wow, ladder docs - that will be nice.
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf.lyx: add charge pump info
EMC: 03bigjohnt 07v2_2_branch * 10emc2/docs/src/config/stepconf.lyx: add charge pump info
I never did understand how to use classicladder till I was forced to figure it out to write how to do it in the docs :)
I never did understand it until I needed to use it and then figured it out
the blank window is daunting
like the old wordprocessor I had on dos 3.somthing or other
fire it up and you get a prompt
demo_sim_cl is very useful. you can run it and see how the estop chain can work
I think understanding emc's estop is very confusing without an example
there's that "request enable" pulse that you have to latch somehow
there is a hal module for it (somehow) but doing it in ladder is so easy and flexible
I'll add that to the classicladder docs
it would be great to point people there when they ask about estop config
well, it's nap time for this almost old geezer :)
do you plan your naps? mine just happen.
nope the feeling just comes over me and I obey
well have a nice one.
ok talk to you later
dream about classicladder
did that last night
now it's e-stops :O
see you later
I wonder how it's like to dream about e-stops
do you wake up from time to time?
make: *** No rule to make target `../docs/src/ladder/ladder_action_load.png', needed by `depends/ladder/ladder_intro_fr.d'. Stop.
did my docs just build at a bad moment or is there a file missing?
I think BigJohnT removed some files, put new ones in place.. might be a missing dep
Failed to remake target file `../docs/src/ladder/ladder_action_load.png'.
it needs to be docs/src/ladder/images/ladder_action_load.png
the _fr doc is not updated
I couldn't get make to tell me what it was
oh, I have a lyx on this system
hang on, I'll commit a fix now
hmm.. looks ok in the document
maybe jepler's lyx2html doesn't support subdirs?
huh -- now it works
I thought I changed something in a lyx file but cvs diff doesn't show it
maybe, if several times I didn't successfully delete the old dep file
heh.. probably :)
alex_joni: hm, see the e-mail from Steve Hobbs? I don't know why this would be disabled, but it sure is
grep FTDI_SIO config-2.6.24-16-rtai
# CONFIG_USB_SERIAL_FTDI_SIO is not set
(that's the config in linux-image-2.6.24-16-rtai_2.6.24-16.30.linuxcnc.2_i386.deb)
it probably was disabled in the regular kernel aswell..
not at all
I use that driver
/usr/src/linux-source-2.6.24$ grep CONFIG_USB_SERIAL_FTDI_SIO debian/Config/config.i386
jepler: you must have built at a bad time to get the error
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/gcode/main.lyx: add G95 not for threading
jepler: odd then
I had to do a make clean here
EMC: 03bigjohnt 07TRUNK * 10emc2/docs/src/config/stepconf.lyx: fix ref to pyvcp
well, my quest to get the altera devkit installed on virtualbox windows and modify the pluto firmware worked first try
yay me :-P
now pluto_step will tristate all outputs until the first full write cycle, which avoids the "amps turn on for a moment at startup" problem
* jepler wanders off again