alex_joni: did you get anywhere with the single step problem?
16:30:39 -!- skunkworks [email@example.com] has quit ["Visitor from www.linuxcnc.org"]
Day changed to 05 Oct 2006
07:16:17 -!- skunkworks [firstname.lastname@example.org] has joined #emc-devel
skunkworks: nobody said anything between the time you left and the time you came back
skunkworks: not really
Jepler: I saw that. Doesn't mean something was worked on. I was trying to see something like that yesterday but could not.
does jepler get annoyed by everyone - or do I just bring it out of him?
skunkworks: you mean, just now? I wasn't trying to express annoyance.
:) Maybe I am just a bit sensitive this morning. Time for some coffee.
mmmmmmm - coffee
I seem to be seeing some pretty nasty things happening with the interpreter. Stuff like not stepping through a program and running a whole program after switching to mdi.
I'll update to todays code and try it again.
I think alex noticed the same thing yesterday or so
The issues I saw make it impossible
at least it's not just me.
not quite the same .. but there are some issues
It really got dangerous here. Moving the machine all over the place.
I was testing what would happen if a program aborted with a tool diameter offset active.
Then switched to mdi and removed the offset and the program began executing from who knows where.
oops - totally unrelated. I should have said that alex noticed some issues with stepping as well
rayh: basicly pushing the step button very quickly (while on the same segment) causes it to resume the run
and there's an issue with positions off the path while stepping, however I am the only one who saw it so far..
That was not the problem I saw.
I saw it execute most of the entire program while in mdi mode.
I'll run the same tests on today's head.
I'm not having a good day.
cvs wants me to
cvs update: move away `lib/.cvsignore'; it is in the way
and after I do that and it checks out a new, I get the same message the next time.
* alex_joni goes home..
rayh: rm -rf lib
I did that to python dir
trying the lib remove.
is there likely to be a problem with make after this?
no, I don't expect so
thanks running make now.
I'm seeing that step does not honor program end.
It will loop back to the start of the program.
and changing mode to mdi does not remove the program from the interpreter.
I'm really glad that I did not discover this with the mazak.
In fact I'll ask roland to put a "Do not run" tag on that machine until this issue is resolved and the EMC there fixed.
I wonder if the problem existed there
It was head a couple days ago that I installed.
on the Mazak?
2.0.3 would not start up.
The demo_mazak config was trashed by some changes in iocontrol
ah. you need to add a kinematics load line to the HAL/ini file
there was a major change to the estop names in iocontrol
and even with substitution it seemed that there was a change in the logic.
could not get it out of estop.
Head however has a working config.
and shows halvcp and carousel orient.
It seems here that the interpreter also does not read completely through the file.
Almost like the m2 at the end is being processed ahead of some of the other lines.
whee! with a change to the nml file, emc2 --enable-simulator runs on an x86-64 machine in 64-bit mode
--- configs/common/emc.nml2006-06-17 17:19:52.000000000 -0500
+++ configs/sim/emc.nml2006-10-05 17:46:28.000000000 -0500
@@ -15 +15 @@
-B toolSts SHMEM localhost 4096 0 0 5 16 1005 TCP=5005 xdr
+B toolSts SHMEM localhost 8192 0 0 5 16 1005 TCP=5005 xdr
what are the consequences of making this change in the emc.nml file?
hmmm - a larger memory footprint?
of 4K (one page)? Seems bearable.
I'm not sure if there are any other issues, but I think NML was actually well designed, soi I'd be surprised
oops - dinnertime. bbiab
so what happens if a 32-bit machine is communicating with this emcsvr? If the buffers are different sizes it must mean that some of the data has a different size, alignment, and/or offset...
* jepler scratches his head
jmkasunich: I must say, great job on hal, it seems to work just fine on a 64-bit machine
though I suppose I don't know about things like atomicity yet