Greetings.
I have been modifing classicladder- I wanted to fix a couple bugs and add a feature.
I am VERY new to c programming ( read that learning by doing) so I really want to compile and link often to check what I have done. Is there a way to just compile/link classicladder while leaving the r
When you type "make", it's only supposed to recompile the parts of emc
that changed. However, when you change the source code to one kernel
module, the linux kernel makefiles insist on re-linking each module (I
don't understand why).
If you use the simulator (./configure --enable-simulator
--enab
Hi Chris
Thanks for taking up the task. I don't know of any public
configurations that use w variables in CL. Neither demo_step_cl nor
demo_sim_cl do. I will check the mazak before I fire it up with your
revisions. I know that SWPadnos and others have worked on some turret
position routines i
Ray
For your info. The changes I made are of course not in any EMC branch- But are very easy- I think it was about 4 lines of code in one file. I don't know what the procedure or policy is for uploading changes but I could email the code to someone. As I said I am very new to programing and don't
On Fri, Mar 16, 2007 at 11:00:44PM -0500, Stuart Stevenson wrote:
> Gentlemen,
>I am looking at putting EMC2 on a CNC tool and cutter grinder. This
> machine is an eight axis machine. Is it possible to extend the axis quantity
> to eight or more? What would be the limiting factor? Processor spe
Today EMC 2.1.3 is released with the following changes:
* make 'load' button work in classicladder
* add french translation of axis
* improve italian translation of axis
* make 'milltask' not consume all CPU after 'run from line' has been used
* new userspace component: hal_input for all Linux-rec
On Sunday 18 March 2007, Chris Radek wrote:
>Today EMC 2.1.3 is released with the following changes:
>
>* make 'load' button work in classicladder
>* add french translation of axis
>* improve italian translation of axis
>* make 'milltask' not consume all CPU after 'run from line' has been
> used *
If you don't enjoy the minutae of working with CVS, it's a great time to
go back to using the prepackaged version -- updates to emc appear
automatically.
Otherwise, instructions to check out a fresh copy of the 2.1.3 source
with CVS are on the wiki:
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl
On Sunday 18 March 2007, Jeff Epler wrote:
>If you don't enjoy the minutae of working with CVS, it's a great time to
>go back to using the prepackaged version -- updates to emc appear
>automatically.
>
>Otherwise, instructions to check out a fresh copy of the 2.1.3 source
>with CVS are on the wiki:
Gentlemen,
In my limited experience with the handwheel control on this machine I see
what I consider over run. I know it is the accumulated pulses the machine
has not completed. When the handwheel is turned faster than the machine is
able to respond the actual position lags behind the commanded
Stuart Stevenson wrote:
> Gentlemen,
>In my limited experience with the handwheel control on this machine I
> see what I consider over run. I know it is the accumulated pulses the
> machine has not completed. When the handwheel is turned faster than the
> machine is able to respond the actua
An approach that may work good for something like this might be to limit the
following error for handwheel moves, and it could be a parameter that could
be set by the user. Just a thought.
Roger Neal
- Original Message -
From: "John Kasunich" <[EMAIL PROTECTED]>
To: "Enhanced Machine
How about:
IF following error is large (set by user?)
AND handwheel counts have stopped increasing/decreasing for a short time (1/4 second? user set?)
THEN stop the axis.
Then slower hand moves will still move exactly (because small follow error) and very fast moves will stop before trouble arrive
13 matches
Mail list logo
