headers
Jon Elson | 1 May 2009 03:11

Re: For Chris Radek and John Kasunich

John Kasunich wrote:
> John Kasunich wrote:
>
>   
>> I'm not going to go through that 
>> learning curve again just to try to find a bug in proprietary code.
>>     
>
> Perhaps that was a bit too dismissive.  I'm not going to try to figure 
> out the code at home by myself, but I am willing to study it at the 
> workshop in Wichita (assuming you are there).  The difference is that 
> I'll be able to ask you questions.
>
>   
The problem is that I won't have the software to change the FPGA code 
with me at the Fest.
But, maybe I can now use the free version of Xilinx Ise that runs under 
Linux.  I'll see about getting that on one of the computers I bring to 
the fest.  But, I think I have already found a potential bug, while 
trying to write up how it works.  The "index pulse seen" logic is 
totally separate from the "reset count on index pulse" logic, which 
seems on the surface to be a "really bad idea"!  I just can't explain 
the sensitivity to a specific thread pitch, or the frequency of 
ocurrence.  It looks to me like it should only fail when a VERY rare 
number of critically timed events happen just so.  I have to go over the 
driver code again, but I think the logic there was that I KNEW, at the 
time, of this critical timing sensitivity, and so I required the spindle 
sync to be turned on for so many servo cycles before it was tripped, to 
be sure the driver couldn't have gotten the pulse seen signal before the 
reset counter logic had been activated.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Buesch | 2 May 2009 17:31
Picon
Favicon

[PATCH] Fix x86_64 crash

Hi,

I already sent this patch some weeks ago and I think it was
applied to 2.3 branch (which was trunk back then).
But today I noticed that the -msse2 was re-added to the Makefiles
and thus the crashes on circular moves came back.

So here's the patch for 2.3-branch (I didn't check trunk, but it
may also need this) which fixes a hard machine crash due to
invalid opcodes.

Signed-off-by; Michael Buesch <mb@...>

---

Index: 2.3-branch/src/Makefile
===================================================================
--- 2.3-branch.orig/src/Makefile	2009-05-02 16:35:44.000000000 +0200
+++ 2.3-branch/src/Makefile	2009-05-02 16:36:30.000000000 +0200
 <at>  <at>  -557,7 +557,7  <at>  <at> 
 	-I$(BASEPWD)/emc/nml_intf -I$(BASEPWD)/emc/kinematics -I$(BASEPWD)/emc/motion \
         -DSEQUENTIAL_SUPPORT -DHAL_SUPPORT -DDYNAMIC_PLCSIZE -DRT_SUPPORT -DOLD_TIMERS_MONOS_SUPPORT -DMODBUS_IO_MASTER
 ifeq ($(RTARCH),x86_64)
-EXTRA_CFLAGS += -msse -msse2
+EXTRA_CFLAGS += -msse
 endif

 ifeq "$(USE_STUBS)" "1"
Index: 2.3-branch/src/Makefile.modinc.in
===================================================================
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 3 May 2009 21:06
Picon
Favicon

[ emc-Bugs-2786229 ] A Axis does not stop

Bugs item #2786229, was opened at 2009-05-03 15:06
Message generated for change (Tracker Item Submitted) made by bigjohnt
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106744&aid=2786229&group_id=6744

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: GUI - AXIS
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: John Thornton (bigjohnt)
Assigned to: Chris Radek (cradek)
Summary: A Axis does not stop

Initial Comment:
In 2.3.0 Axis if you use the keyboard to jog a linear axis and at the same time use the mouse to start the A axis
jogging then release the keyboard axis before the A axis the focus shifts to the linear axis and the A
continues to rotate forever. If you then select the A axis with the mouse and press either the plus or minus
buttons the A axis will stop. This does not happen if you use the keyboard for the A axis.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106744&aid=2786229&group_id=6744

------------------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
SourceForge.net | 4 May 2009 19:31
Picon
Favicon

[ emc-Bugs-2786752 ] jog U, V, W in world mode not working

Bugs item #2786752, was opened at 2009-05-04 17:31
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106744&aid=2786752&group_id=6744

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: GUI - AXIS
Group: None
Status: Open
Resolution: None
Priority: 5
Private: Yes
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Chris Radek (cradek)
Summary: jog U,V, W in world mode not working

Initial Comment:
With non trivial kinematic, it is not possible to jog axis U,V in world mode. Axes X,Y e.g. work fine with same kinematic.
MDI and G-Code works also. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106744&aid=2786752&group_id=6744

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeff Epler | 5 May 2009 23:59
Favicon

documentation tool changes on TRUNK

Since we will drop Dapper support for emc 2.4, that means we can finally
move beyond Dapper's LyX 1.3.6.  I'm about to check in some changes that
do this.  After this, the correct system to edit HEAD's docs will be
Hardy.  (v2_3_branch docs are still to be edited on Dapper only!)

Seb, this will require you to remove some slaves from buildbot, such as
dapper-x86-trunk-realtime-deb -- basically, anything that is on dapper
or older, builds trunk, and uses --enable-build-documentation.

When first editing a file with version 276, make a checkin that does
nothing but the conversion.  This will help isolate your meaningful
changes from the noise created by the version change.  Here's how to
check the version of a file:
    head -2 xxx.lyx
If it prints this:
    #LyX 1.3 created this file. For more info see http://www.lyx.org/
    \lyxformat 221
then do a convert-only check-in: load the file in lyx, add and delete a
space somewhere, then commit it with the checkin messge like "convert to
new version of lyx".  After conversion, the first two lines of the file
should be
    #LyX 1.5.3 created this file. For more info see http://www.lyx.org/
    \lyxformat 276

Unhappily, this interactive conversion process is a *different* output
than is given by lyx2lyx alone, so a purely automated conversion is not
possible.
    $ diff -u comp-edited-to-276.lyx comp-lyx2lyx-to-276.lyx  | diffstat
    721 insertions(+), 208 deletions(-)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Sebastian Kuzminsky | 6 May 2009 08:19
Gravatar

Re: documentation tool changes on TRUNK

Jeff Epler wrote:
> Seb, this will require you to remove some slaves from buildbot, such as
> dapper-x86-trunk-realtime-deb -- basically, anything that is on dapper
> or older, builds trunk, and uses --enable-build-documentation.

That's the only affected buildslave, i've removed it from the buildbot.

--

-- 
Sebastian Kuzminsky
    you press what you hope is the right switch, and you
                   - jump, becoming light

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
Permalink | Reply | 0 comments |
headers
Dewey Garrett | 7 May 2009 22:45
Picon
Favicon

--help patch for emcrsh

For consideration (trunk)
This patch adds --help option for emcrsh and shows some defaults values.
Example usage:

$ emcrsh --help
Usage: 
         emcrsh [Options] [-- emcOptions]
Options:
         --help       this help
         --port       <port number>  (default=5007)
         --name       <server name>  (default=EMCNETSVR)
         --connectpw  <password>     (default=EMC)
         --enablepw   <password>     (default=EMCTOO)
         --sessions   <max sessions> (default=-1) (-1 ==> no limit)
         --path       <path>         (default=../../nc_files/)
emcOptions:
          -ini        <inifile>      (default=emc.ini)

Index: emcrsh.cc
===================================================================
RCS file: /cvs/emc2/src/emc/usr_intf/emcrsh.cc,v
retrieving revision 1.16
diff -u -r1.16 emcrsh.cc
--- emcrsh.cc	8 Apr 2009 15:38:06 -0000	1.16
+++ emcrsh.cc	7 May 2009 20:30:40 -0000
 <at>  <at>  -489,6 +489,7  <at>  <at> 
 const char *commands[] = {"HELLO", "SET", "GET", "QUIT", "SHUTDOWN", "HELP", ""
};

 struct option longopts[] = {
(Continue reading)

Permalink | Reply | 2 comments |
headers
Eric H. Johnson | 8 May 2009 00:21

Re: --help patch for emcrsh

Dewey,

Yes definitely that should go in. If you do not have developer privileges to
check it into CVS, send me either the patch file or the source file and I
will check it in. I probably won't get to it until this weekend however.

Regards,
Eric

For consideration (trunk)
This patch adds --help option for emcrsh and shows some defaults values.
Example usage:

$ emcrsh --help
Usage: 
         emcrsh [Options] [-- emcOptions]
Options:
         --help       this help
         --port       <port number>  (default=5007)
         --name       <server name>  (default=EMCNETSVR)
         --connectpw  <password>     (default=EMC)
         --enablepw   <password>     (default=EMCTOO)
         --sessions   <max sessions> (default=-1) (-1 ==> no limit)
         --path       <path>         (default=../../nc_files/)
emcOptions:
          -ini        <inifile>      (default=emc.ini)

Index: emcrsh.cc
===================================================================
RCS file: /cvs/emc2/src/emc/usr_intf/emcrsh.cc,v
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jeff Epler | 8 May 2009 00:48
Favicon

Re: --help patch for emcrsh

On Thu, May 07, 2009 at 06:21:16PM -0400, Eric H. Johnson wrote:
> Dewey,
> 
> Yes definitely that should go in. If you do not have developer privileges to
> check it into CVS, send me either the patch file or the source file and I
> will check it in. I probably won't get to it until this weekend however.

I checked it in.  Thanks, both of you.

Jeff

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
Permalink | Reply | 0 comments |
headers
Jeff Epler | 11 May 2009 14:44
Favicon

Re: [Emc-commit] TRUNK emc2/docs/man/man9 thc.9, NONE, 1.1

On Mon, May 11, 2009 at 12:42:40PM -0000, John Thornton wrote:
> New file emc2/docs/man/man9/thc.9

For comps, the .9 manpage is automatically generated from the associated
.comp file and should not be added to CVS.  Instead, the .9 file should
be listed in the .cvsignore in docs/man/man9.

Jeff

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
Permalink | Reply | 0 comments |

Gmane