Ok. I can try as I said before.
But this needs to be clear to me, this is, the task(s) that I will make.
I think that the best would be:
A list, similar to a bug traking system,BUT ONLY for patches (that
normally the creator already tested).
I can try to read each one, and talk
On Wed, Jan 08, 2014 at 09:21:08AM +, Filipe Tomaz wrote:
But this needs to be clear to me, this is, the task(s) that I
will make.
Hi Filipe,
Like others, I thank you for offering to do this, and I think it
would be a big help to the project.
I agree we should talk a bit about
About me:
I have a degree in computer engineering and I work in metalworking for
more than 15 years.
The two both combined resulted in interest in CNC and lately in linuxcnc.
I have built from scratch machines, and also rebuilt several machines.
Mostly (or all) are for sale, were I also give
Todd on the forum brought up
http://www.linuxcnc.org/index.php/english/forum/10-advanced-configuration/27368-new-trajectory-planner-testersprograms-wanted
I think you guys working on this are defonately on the right track. It
can offer a significant improvement depending on the code used.
I
First of all, thanks for spreading the word! I think you did not a great
job explaining what these changes are, and what people should expect.
As for adding other axes, I'm working on the math for that, though it won't
be a quick fix because it needs a bunch of new data structures and support
I am working to add some Modbus functions to mb2hal (Modbus to Hal,
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?ModbusToHal).
Where should i submit the patch ?
Thanks you,
Víctor
El 07/01/2014 01:29 p.m., Sebastian Kuzminsky escribió:
On 1/6/14 22:36 , Chris Morley wrote:
Date: Sun, 5 Jan 2014
On 1/8/14 14:21 , Victor Rocco wrote:
I am working to add some Modbus functions to mb2hal (Modbus to Hal,
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?ModbusToHal).
Where should i submit the patch ?
I'm not Filipe, but I think this question is answered by the
Contributing to LinuxCNC document:
Hi All,
After fixing a few persistent but minor issues with arc blending, I think
the code is ready for beta status. I've pushed a branch on my github fork
called circular-blend-arc-beta:
https://github.com/robEllenberg/linuxcnc-mirror/tree/circular-blend-arc-beta
This branch has code that does
WOOHOO... Thanks!
EBo --
On Jan 8 2014 3:16 PM, Robert Ellenberg wrote:
Hi All,
After fixing a few persistent but minor issues with arc blending, I
think
the code is ready for beta status. I've pushed a branch on my
github fork
called circular-blend-arc-beta:
I should point out that there are still interactions that are hard to test
for on my equipment, such as 4+ axis behavior, spindle synchronization,
rigid tapping, and digital / analog inputs. The changes shouldn't affect
these areas, but it is possible that subtle bugs could affect these
functions.
Fare enough. I just wanted to give a little thanks and encouragement
for gettin' her done ;-)
EBo --
On Jan 8 2014 3:39 PM, Robert Ellenberg wrote:
I should point out that there are still interactions that are hard to
test
for on my equipment, such as 4+ axis behavior, spindle
Seb and others,
I remembered that the doc you referenced mentions the LCNC repo on git hub.
That made me think that using git hub may save reinventing the wheel here...
I'm thinking that fork then pull request is favorable over push patch.
Instead of developing patches against the repo in
The process is the same as before and can be looked for in the
Contributing to LinuxCNC document.
The patch submission change/method is currently being discussed as can
be see on this mailing list, so things are not exactly clear (at least to
me).
My opinion, is to have something like:
13 matches
Mail list logo
