Andy,

>> No, that does seem wrong and strange. I wonder if it is a synch problem,
one part of the code not updating because it thinks nothing has changed on
the basis of an internal value but another part of the code getting the
information from the not-updated section? <<

I have used this basic technique to offset tools in the past without
problem, which is why this is so strange. The biggest difference I can see
is that this application makes extensive use of external named subroutines.

I have controllable X,Y,A, and B axes, however Z is just a two position
pneumatic air cylinder. Asserting the output, waiting for the head-up or
head-down input, adding a dwell, etc. adds up to 5 or 6 lines of G-Code for
every head up or head down, so I implemented them as named subroutines.

It seems that no matter where I am in the execution of the main program, at
the time of a stop, pause, etc. the line reporting back as the current line
is invariably in one of these subroutines. This has caused some problems in
my custom user interface, which I have mostly worked around, but have not
dug into the EMC code to see what is really going on.

I posted a question about this and how Axis dealt with it on the developers
list a few weeks back but never saw a reply.

Regards,
Eric




------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to