I think this means your forward and reverse kinematics don't match.
If you take a position with BC /= 0, and feed it through the inverse
kins, then feed that result through the forward kins, you should
get the same position you started with. I think you will find that
you don't.
Cheers,
Chris
On Mon, Mar 20, 2023 at 12:21:17PM -0500, Jon Elson wrote:
> Will people who plan to attend (weekend of April 22-23)
> please confirm?
I also plan to attend!
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
On Mon, Nov 08, 2021 at 06:31:20PM -0700, Sebastian Kuzminsky wrote:
>
> This will make it much easier for people to try out LinuxCNC, and will
> greatly increase our visibility in the CNC software world.
>
> This is an exciting time for LinuxCNC, and we could not have done it
> without
Hi Bob,
This is wonderful, thank you for working on this after almost 6
years!
Did you see that there's a test, tests/interp/5440 that is partly
disabled because of this bug? When you build your pull request it
would be great if it included a commit that reenables this test
fully, confirming
On Mon, Jul 26, 2021 at 01:31:11PM -0400, Feral Engineer wrote:
> An example would be setting a work offset:
>
> G10 L2 P1 X#5021 Y#5022
Sam's answer (use G28.1 or G30.1) is one way to get the number you
want. Also, you can access the current position WITH offsets
applied, and then subtract
On Sat, Jan 25, 2020 at 07:50:44AM -0500, Gene Heskett wrote:
> =
> checking for libgnomeprintui-2.2... no -- printing from classicladder
> will not be possible
> =
>
> Does this mean that classicladder will not be able to prompt the user for
> a required option? That seems rather
On Thu, May 23, 2019 at 10:11:26AM +0100, andy pugh wrote:
>
> Already done, I have the .iso and .iso.zsynch files ready and tested.
Awesome, I wasn't able to get it to work yet. Got up to isolinux
failing (no such package available), and went to bed.
Would you push your changes to live-build
On Wed, May 22, 2019 at 01:31:15PM +0100, andy pugh wrote:
> We have a LiveCD based on Wheezy and RTAI but that is currently somewhat
> broken (the apt sources list points at files that are no longer there now
> that Wheezy is a long way past EOL)
> I have tried to respin that ISO using the
On Sun, May 05, 2019 at 05:00:38PM -0500, Jon Elson wrote:
> Thank you! Now, there were some grumblings about the Wiki
> being outdated and useless.
> Is that actually the feeling in general? I hope not, but
> maybe we need to clean up some of the obsolete items there,
> as LinuxCNC has been
With Stephen's help I finally got access to the machine and then was
able to patch it up. There were several confounding problems due to
upgrades at the hosting site, one of which was that my ssh key was
in an old format that has been deprecated.
I don't know who gets those webmaster emails
On Tue, Feb 26, 2019 at 06:21:13PM +0100, wi...@erste.de wrote:
> the second idea was: using both edges of a binary signal
> for motor stepping doubles the speed or bisects the bandwidth.
>
> but I found no way to do this, without patching stepgen.c
Have you considered the quadrature scheme,
On Tue, Oct 02, 2018 at 12:16:54PM +0100, andy pugh wrote:
> https://github.com/LinuxCNC/linuxcnc/blob/b948dba1af9e63f26498cf005d6693cec30458a9/src/emc/rs274ngc/interp_convert.cc#L3302
>
> There seem to be a lot of things that are not allowed with cutter comp
> enabled, and it isn't immediately
On Thu, Jul 05, 2018 at 07:49:29PM +0100, andy pugh wrote:
>
> I have been using it that way for over a year with no problems, can I
> push the mod?
This looks like a bugfix to me, so if you're waiting for my input, I
say push away.
Chris
On Thu, May 10, 2018 at 09:11:17PM -0500, Jon Elson wrote:
> Wow, thanks, guys for locating the source of the trouble!
> Geez, I have two variables with the SAME name!
> I can't imagine how this bug hasn't come up for a whole
> year! I wish I could just say I was drunk when I coded
> that,
On Thu, May 10, 2018 at 12:57:06PM +0100, andy pugh wrote:
> https://en.wikipedia.org/wiki/General_Data_Protection_Regulation
>
> I hadn't really given it much thought until the Octoprint developer
> said that it was proving to be a lot of trouble to her. (and that she
> might have to move to an
On Wed, May 09, 2018 at 08:06:02PM -0500, Jon Elson wrote:
>
> Can somebody give me some instructions so I can find exactly
> what changes were made between
> the 2.7.8 release and the 2.7.9 release? The git history
> REALLY doesn't show any other changes.
git fetch
gitk v2.7.8..v2.7.9
You
On Thu, Jul 06, 2017 at 09:56:26AM -0400, Dave Cole wrote:
> 10 mpg is great for a bus!
> Chris what do you have powering your bus?
It's a 93 Blue Bird, it has the Cummins 6BTA and much-feared
Allison AT545.
--
Check
On Wed, Jul 05, 2017 at 06:29:04PM -0500, Jon Elson wrote:
> No, just single. But, it is still QUITE the machine!
> Pretty amazing the thing is still in good condition, since
> it is 49 years old. He figures it has about 3 million miles
> on it, as it was used by a bus service between 2
On Wed, Jun 21, 2017 at 11:38:42PM +0100, andy pugh wrote:
> Looking at the code, I get the impression that the ability to load a saved
> data file back into Halscope isn't implemented. Am I correct?
Yes
--
Check out
On Thu, May 25, 2017 at 02:41:51PM +0100, andy pugh wrote:
> I thought that it was possible to compile kinematic modules with
> halcompile, but it appears not:
>
> https://forum.linuxcnc.org/10-advanced-configuration/32814-scara-hand-region-issues?start=10#93615
>
> I assume that there is a way
On Wed, May 17, 2017 at 09:08:00PM -0500, Jeff Epler wrote:
> How do developers of LinuxCNC feel about the idea of moving the
> primary git hosting from git.linuxcnc.org to GitHub?
I'm pretty sure I'm in favor of it, and I have an open mind and look
forward to hearing what other devs say.
Also
On Mon, Mar 27, 2017 at 05:21:57PM -0400, Kurt Jacobson wrote:
>
> Is this expected behavior of stat.gcodes or is this a bug in the Python
> Interface, or elsewhere?
This is expected, but is fixed in a branch that will be merged in
the future, called statetags.
That branch is really close to
On Thu, Dec 08, 2016 at 06:10:09PM +, Robert Ellenberg wrote:
> Hi All,
>
> Does anyone use a spindle encoder with only position output? In other
> words, encoder position linked to motion.spindle-revs, but no input to
> motion.spindle-speed-in?
motion.spindle-speed-in IN FLOAT
On Wed, Nov 16, 2016 at 08:15:42AM -0600, dragon wrote:
> Below is a link to an email thread where Ben Potter submitted a patch
> set to implement g71 into the interpreter in 2012. It was never accepted.
>
>
On Tue, Nov 08, 2016 at 09:56:15PM +0200, tero.kaarl...@eka-sorvaus.fi wrote:
>
> Would it be possible to add INI entry for TOOL_CHANGE_MOVE_ORDER
> parameter?
It would be possible, but I think it would be wasted effort, because
you can easily use remap of M6 to do whatever kinds of motion
On Fri, Oct 28, 2016 at 09:29:29AM -0500, Jim Craig wrote:
> What is your opinion of this general method of working with a running
> HAL configuration?
I think using experimental loading of a hal component after the user
provides the arguments (to see what pins and parameters it presents)
is a
On Sat, Oct 01, 2016 at 10:59:54PM +0300, tero.kaarl...@eka-sorvaus.fi wrote:
>
> GET_EXTERNAL_FEED_OVERRIDE_ENABLE()
> GET_EXTERNAL_SPINDLE_OVERRIDE_ENABLE()
> Always return 1. I am afraid. Maybe because in saicanon.cc we have:
>
> /* MGS - FIXME - These functions should not be stubbed out to
On Mon, Sep 26, 2016 at 10:18:33PM +0300, tero.kaarl...@eka-sorvaus.fi wrote:
> Hi,
>
> Thank you for reminding me about docs. I did update quickref and
> also gcode.txt. It also describes that P word is an optional Dwell
> at the bottom of thread.
Great!
> I tried to find Pause disable from
On Fri, Sep 23, 2016 at 09:50:32PM +0300, tero.kaarl...@eka-sorvaus.fi wrote:
> Hi,
>
>It seems I was wrong. DISABLE_SPEED_OVERRIDE and
>DISABLE_FEED_HOLD do work. Using halmeter for pin
>motion.spindle-speed-out confirmed correct behaviour. Also
>Feed_hold_disable works but it
On Tue, Jun 28, 2016 at 11:36:40AM -0400, John Kasunich wrote:
>
> It is only monotonically increasing if you interpret it as two integers
> separated by a dot. Humans can interpret it any way they want, but
> how do programs interpret it?
for debian packages this is really well defined, but
On Mon, Jun 20, 2016 at 10:51:42PM -0500, Jon Elson wrote:
> I notice that when browsing the gitweb history, that lots of
> unrelated "Merge remote tracking branch..."
> entries have moved all the old history of items in the
> configs files off into never never land. So, I can't see
> where
On Mon, Jun 20, 2016 at 10:46:26PM -0500, Jon Elson wrote:
> Well, I haven't done a git pull in some time, it seems my
> password may have expired, or possibly I forgot it.
> (I thought I remembered it...)
>
> My user name is jmelson on git. Not sure who is responsible
> for the git
On Mon, Jun 13, 2016 at 08:44:55PM -0500, Jon Elson wrote:
> I was just informed that there is a quirk in the tool table
> editor. If the existing tool table is of the old style, with
> the column label first line and looks like this :
>
> POC FMS LEN DIAMCOMMENT
> 1 1
On Tue, May 24, 2016 at 02:24:50PM +0100, andy pugh wrote:
> On 24 May 2016 at 13:55, johnson wrote:
> > We use ignore limits and we can jog off.
>
> With an MPG?
I think "override limits" only lets you do a continuous jog. It
might allow incremental but I'm not sure.
On Wed, Mar 23, 2016 at 10:25:30AM -0500, Jon Elson wrote:
> A pecking routine should not need to re-synchronize the Z to
> the spindle. Just keep the Z in synch, and flip the spindle
> from forward to reverse, and the Z should follow the thread
> pitch up and down. So, you would synch to
On Tue, Jan 05, 2016 at 10:08:42AM -0500, tom-...@bgp.nu wrote:
>
> Yes. On the gantry machine we are using this on, one positions
> the touch off point of the torch which may be many feet from the
> initial machine zero and then typically clicks the Touch OFF X,Y
> (or Touch Off X, then Touch
On Fri, Nov 06, 2015 at 10:48:17AM -0600, John Morris wrote:
>
> Thanks, Chris, for the initial (offline) review!
>
> Chris's suggestions are mostly (doc link problem fixed in main commit)
> incorporated in the top commit of [1], above. I'll squash them down for
> the final version, but left
On Thu, Nov 19, 2015 at 12:08:24PM +, andy pugh wrote:
>
> Is world-mode jogging with an MPG and non-trivial kinematics supported
> in any branch of LinuxCNC?
No, unfortunately wheel jogging is only joint mode right now.
I have a fresh rebase of JA almost ready, and Seb is working on a
(lathe-like) test that shows what we know is broken. We should have
this ready for folks to test or work on, soon.
I think JA should be in the next release branch, not next+1.
On Wed, Sep 23, 2015 at 03:32:53PM +0100, andy pugh wrote:
> The last 2 weeks has seen more kinematics questions on the forum than
> the previous 2 years.
> I don't know why, but it does make me wonder if JA is near merge?
>
> Aparently there was a problem with nonconsecutive joints, but no JA
>
On Tue, Sep 08, 2015 at 03:18:42PM +0100, andy pugh wrote:
>
> My proposal is that the homing code would search the INI file for a
> [SPINDLE*] stanza (which already exists in many configs) and if it
> finds one that contains a homing sequence number it would assert the
> spindle-index-enable
On Tue, Sep 08, 2015 at 08:30:13PM -0500, Jon Elson wrote:
> Now, you COULD figure out the right number by modulo
> division and work it that way.
You know, I hadn't thought about this. The original design for
spindle-synced motion was when we had single precision floating
point positions,
On Mon, Jul 06, 2015 at 09:46:12PM -0400, Kenneth Lerman wrote:
When I enabled a tool table in Axis, it started using a lot of CPU time and
became unusably slow.
What version of linuxcnc? Anything on stderr/stdout?
On Wed, Apr 22, 2015 at 03:13:33PM +0100, andy pugh wrote:
Is it possible to get a precompiled Joints_Axes6 (or JointsAxes7) from
the buildbot?
I poked buildbot for you (via the irc message) and the packages
should be available at (for example)
), that will be in 2.5.5 if we ever make it. At this
point you could try the buildbot 2.5 package, or just move to 2.6.
commit 005794703727a88f17426371cc13c3886ed6c466
Author: Chris Radek ch...@timeguy.com
Date: Sun Jun 1 17:08:45 2014 -0500
NURBS: fix biarc G1 continuity
The center
On Fri, Mar 13, 2015 at 09:32:10PM -0400, Brian wrote:
Some bounds checking would be a good idea in addition to making the array
bigger.
Brian do you have this hardware? It would be great if you could fix
and test it.
Chris
On Sun, Mar 08, 2015 at 05:13:35PM -0400, Robert Ellenberg wrote:
I'll take a look at this tonight.
Hi Robert,
Sam might have saved you the trouble by doing a bisect that pointed
me to a little mistake:
On Thu, Feb 05, 2015 at 11:06:22AM +, andy pugh wrote:
The G-code produced by InventorHSM using the generic emc postprocessor
inserts a Z-word in the G43 line.
eg G43 Z-41 H6
Is this a) ignored or b) a motion?
Certainly not ignored. Whether it's a motion or an error depends on
what
On Fri, Jan 30, 2015 at 03:20:03PM -0500, Robert Ellenberg wrote:
The idea is basically to pack the relevant parts of the interpreter's
active state into a minimal size tag, and stick this tag onto every
motion command.
This is great! It's just how we handled the override enables.
I've
On Mon, Jan 05, 2015 at 07:42:52PM +0200, Andrew wrote:
Your link has another link
http://timeguy.com/gitweb?p=linuxcnc.git;a=log;h=refs/heads/synchronized-homing
Looks like a good stab at synchronized homing, why is this left behind? Any
major problem revealed?
No problem revealed -- I
On Wed, Nov 26, 2014 at 10:28:47AM +, andy pugh wrote:
One interesting application for such pins would be to allow
world-space motion from arbitrary HAL components driven by sources
other than G-code. There are probably many potential uses for this in
I like this idea. The
On Thu, Aug 28, 2014 at 03:09:53PM +0100, David Armstrong wrote:
Guy's
i'm having a problem trying to get a analog 10v spinde to scale correctly
There's already a thread going, in response to this, on emc-users.
Let's not have another one here.
David, please make only one post to the most
On Mon, Aug 25, 2014 at 09:47:29AM -0600, Sebastian Kuzminsky wrote:
It somewhat raises the barrier-to-entry for casual contributors: they
now have to know to use the -s flag to git commit. I guess it's easy
enough for the reviewers to inform them about it, or to add the SOB
themselves,
On Sat, Aug 23, 2014 at 02:10:00PM -0500, Jeff Epler wrote:
PROPOSED: That we adopt a signed-off-by procedure as detailed in [1]
and [2] and put in place an automatic check to ensure that all new
contributions are signed off.
I think this is a good idea.
On Wed, Aug 06, 2014 at 03:57:59PM +, Dewey Garrett wrote:
# xhc-hb04 mpg pendant
ATTR{idProduct}==eb70, ATTR{idVendor}==10ce, MODE=666, OWNER=root,
GROUP=users
Two things that may or may not be interesting on my wheezy install:
Other rules on this system have MODE=0666, not 666. I
On Tue, Aug 05, 2014 at 12:37:07PM +0100, David Armstrong wrote:
i'm also receiving an entry error when running my existing config on
loading the hm2_pci.ko
my current line is
loadrt hm2_pci config= num_encoders=1 num_pwmgens=0 num_3pwmgens=0
num_stepgens=5 sserial_port_0=
On Thu, Jul 31, 2014 at 10:59:47AM -0400, Steve Stallings wrote:
Will the s-o-b enforcement mechanism insist on GPL or will
it also allow compatible or partially compatible submissions
such as LGPL (like the original HAL) or totally unrestricted
code (perhaps BSD)?
You snipped both
On Fri, Jul 11, 2014 at 02:45:28AM +0100, andy pugh wrote:
I have the first case apparently working in a sim on top of the
G43.2 branch.
I am very happy to hear this! Thanks for tackling it.
I think it would be great to rebase the G43.2 feature onto master,
and add a sample/demo config that
On Tue, Jun 24, 2014 at 02:46:50PM +0100, andy pugh wrote:
The program 'comp' can be found in the following packages
mailutils-mh nmh in the obvious way.
Maybe we should rename it? It's not a particularly good or
descriptive name.
halcompile?
On Tue, Jun 17, 2014 at 03:52:48PM -0500, Chris Radek wrote:
I built master, ref 377f171, on my wheezy/3.4.55-rtai-2 SMP machine,
which runs 2.6 fine, and upon starting linuxcnc with any config
including sim/axis/axis, I get:
http://timeguy.com/cradek-files/emc/tpSetTermCond.jpg
Good news
I built master, ref 377f171, on my wheezy/3.4.55-rtai-2 SMP machine,
which runs 2.6 fine, and upon starting linuxcnc with any config
including sim/axis/axis, I get:
http://timeguy.com/cradek-files/emc/tpSetTermCond.jpg
tpSetTermCond() is short and sweet and I don't see any obvious
problem with
On Sat, Jun 14, 2014 at 09:43:10AM +0100, Schooner wrote:
It is unclear from the code if it was amended by Robert as part of the
new TP, but in any event could be being affected by it.
I have asked the user to provide full configs and some gcode which will
reproduce the error
Thread is
On Tue, Jun 10, 2014 at 10:01:26AM +0200, Micha?? Geszkiewicz wrote:
You have copy/paste error in halui support
Also I think ini setting for max rapid override is not needed, there is
no move at RO 100.0 %.
You are right about both; I pushed the fixes. Thank you for the
review.
On Mon, Jun 09, 2014 at 06:12:55AM +, Chris Morley wrote:
I built your branch seemed to work for me. I didn't test much.
My 2 cents worth:
Thanks for testing!
If we add the direct-value switch then one could connect
halui.feed-override.value to halui.rapid-override.counts...
oh hmm
On Fri, Jun 06, 2014 at 06:52:03AM +, Chris Morley wrote:
This patch does not add an NML command to control rapid override,
That is beyond my skill and I'm not sure necessary.
Let me take a shot at adding it beside the current FO. I would
really prefer that to having them be completely
On Fri, Jun 06, 2014 at 06:52:03AM +, Chris Morley wrote:
This patch adds a pin to motion that allows rapids to be overridden
from 0 to 100 percent.
connecting this pin to halui.feed-override.value makes GUI's feed override
also control rapids.
This patch does not add an NML command to
On Thu, Jun 05, 2014 at 01:47:43AM -0700, ELHIMA Moustapha wrote:
Dear All,
I'm back to get some help
Hi, please ask for setup/configuration help on the emc-users list or
the forum; we like to keep the emc-developers list for discussion of
development and related topics.
Thanks,
Chris
On Mon, Jun 02, 2014 at 07:05:59PM +0200, bruno wrote:
Hi Chris,
I did not know how to give the first point a weight, in addition I
definitely had a bug in my GCode, in the sense that I wanted points 1
and 3 to have the same lower weight, but not point 2. With this change,
the curve
Hi Bruno,
Investigating this led me to find and fix several bugs in the NURBS
implementation, which will give you a MUCH smoother wrong path when
you run your test program.
But that aside, you are seeing a problem because you have very
different weights on your control points, and that is
On Fri, May 30, 2014 at 09:29:35AM -0400, Jeff Johnson wrote:
As a long time lathe operator and shop owner I hate to see the wheel
re-invented. Operators are taught and used to T the first two digits are
the tool number and the second two are the off-set number.
I sure sympathize with
On Wed, May 14, 2014 at 02:38:55PM -0500, Chris Radek wrote:
OK, I pushed it to circular-blend-arc-rc4 so you guys can have a
look.
I have also rebased joints_axes4 onto circular-blend-arc-rc4. You
can find this work at g.l.o/ja4-onto-cba4
Because of massive changes on both sides
I think the general solution to the specific problem of wanting
separate geometry and wear offsets for lathe tools is to allow the
gcode to request any number of tool offsets simultaneously.
I've implemented that in a very simple way in the cradek/multi-tlo
branch on git.linuxcnc.org, and here
On Thu, May 29, 2014 at 03:37:21PM -0500, John Thornton wrote:
If I understand this say you have T100 as -0.001 in diameter you can do
G43.2 H100 to make your tool effective diameter 0.001 smaller for
G41/42 paths?
So far, this is only about offsets (what we used to call tool
length offset
On Thu, May 22, 2014 at 09:31:56AM -0400, Curtis Dutton wrote:
I don't believe it ever was merged.
It is available here...
https://github.com/OKComputers/linuxcnc-mirror/tree/wj200_vfd
I rebased this onto 2.6 and pushed it for the buildbot to chew on,
so we should know in an hour or two
On Tue, May 13, 2014 at 09:04:32PM -0400, Robert Ellenberg wrote:
Does anyone object to merging into master now?
I've done a pretty-easy rebase that linearizes the branch and puts
it atop master, and I was able to remove a few false starts like the
pair:
Temporary revert from master to see if
On Wed, May 14, 2014 at 03:25:27PM -0400, Sebastian Kuzminsky wrote:
On 05/14/2014 10:50 AM, Chris Radek wrote:
Should I push this as circular-blend-arc-rc4 so you can have a look
at it? Does anyone have strong feelings about merge as-is vs.
a linear fast-forward?
I prefer a linear
On Sun, May 11, 2014 at 07:57:26PM -0500, David Raila wrote:
How does one make a kinematics error do something reasonable, like
report an error and stop motion?
It appears that the return values from the Fwd/Inv kinematics calls are
ignored, at least from my reading of control.c
On Wed, Apr 23, 2014 at 11:56:08AM +0100, andy pugh wrote:
This is much better behaviour than PyVCP, where spinbutton valuyes
don't update even if you do press enter, and in fact you need to press
the up arrow to commit, then the down arrow to get back the number you
typed in.
I think that
On Tue, Apr 22, 2014 at 11:13:45AM -0400, Gene Heskett wrote:
It shows X limits at + and - 100 inches. (radius)
The ini file sets X MIN_LIMIT = -0.500, and X MAX_LIMIT = 1.850 (inches
radius)
This works correctly for me with configs/sim/axis/lathe.ini
Please pastebin or attach your ini
On Tue, Apr 22, 2014 at 12:36:43PM -0400, Gene Heskett wrote:
[AXIS_0]
...
MIN_LIMIT = -100.0
MAX_LIMIT = 100.0
It looks like it's doing what you asked. Please check again?
On Tue, Apr 15, 2014 at 01:21:07AM -0400, Robert Ellenberg wrote:
Well, I did a little more investigating, and it turns out the problem is
deeper (and older) than I thought. The reason the velocity constraints were
being violated here was that the axis_len calculation in emccanon.cc
(ARC_FEED
Hey all, this was an incorrect merge of master into the 2.6 branch.
I used push --force to revert 2.6 to where it was before the merge.
This means if you pulled the 2.6 branch in about the last hour, your
next pull will not be a fast-forward, and you may have to use
git pull --force or similar.
On Fri, Apr 11, 2014 at 08:48:42AM -0400, Robert Ellenberg wrote:
Me too, I've only had time to email a bit due to schoolwork. To answer your
main question: it could make the C++ portions of the code simpler and
easier to maintain.
I see, I was thinking of a bigger goal, which is to eliminate
On Fri, Apr 11, 2014 at 10:38:19AM -0500, Chris Radek wrote:
What do you think of the much bigger proposal of converting to
internal units very early (like how diameter conversion is handled
in Interp::read_x) and removing units twiddling from all the
Minor complexity: we have a freaky
On Thu, Apr 10, 2014 at 10:57:42AM -0500, Jon Elson wrote:
(Mostly I'm going to merge the xxx_motion.hal and xxx_servo.hal
files, there is no rational reason for how these were split up.
Also, I will get rid of as much of the newsig/linksp code as
possible in favor of net commands.)
This
On Thu, Apr 10, 2014 at 03:09:33PM -0400, Robert Ellenberg wrote:
Ignoring the labor involved in doing the conversion, does this sound like a
good idea?
A few of us tossed around some ideas about this in irc; wish you
could join us:
I want to release 2.5.4 soon; there are some important fixes in
there. I'm aiming for around the 16th, a week from today.
In the past I've been asked to give a heads-up because sometimes
people know of a problem, but forget or get distracted until they
see a reminder... So that's this!
Here is
On Thu, Apr 03, 2014 at 06:43:21PM -0400, Gene Heskett wrote:
More gr. Seems google tells me it doesn't exist until 12.04.3.
Seb did the work of backporting libmodbus5 to lucid (and hardy!) to
make this easy for people who don't want to upgrade. Knowing this I
was able to find
On Wed, Mar 26, 2014 at 10:01:05PM +1100, Frank Tkalcevic wrote:
make: Failed to remake makefile `Makefile'.
Yeah, this is not a very good error message. Some help here:
http://wiki.linuxcnc.org/cgi-bin/wiki.pl?FailedToRemakeMakefile
On Thu, Mar 13, 2014 at 06:52:28PM -0500, Charles Steinkuehler wrote:
Testing so far shows that the HOME values from the [TRAJ] section
just aren't getting used somehow.
It would be great to know whether this is fixed in JA4. (Fixing
kins-related problems in any other branches is probably a
On Thu, Mar 13, 2014 at 01:40:42PM -0500, Charles Steinkuehler wrote:
Currently, I can bring up LinuxCNC in joint mode and jog around, but
when I have the joints at their home positions and try to switch to
world mode, I immediately get joint following errors on the x and y
joints.
I do
On Thu, Mar 13, 2014 at 03:06:13PM -0500, Charles Steinkuehler wrote:
When the joints are homed, the Y world coordinate is not zero, and I
don't see how to tell LinuxCNC what the home value is supposed to be
See my other message for more, but for future readers, it's hidden
in here:
Forgive me for replying to such an old question. Sam pointed me to
this, and I think it might be related to the runtest failures in
origin/circular-blend-arc-rc1.
On Thu, Dec 26, 2013 at 12:55:43PM -0500, Robert Ellenberg wrote:
I'm not sure what the original intent of Naive CAM detection
On Tue, Mar 04, 2014 at 05:07:49PM -0500, John Kasunich wrote:
Stepgen, pwmgen, and encoder are the ones I can think of
right now.
There may be code in the wild that we don't know about.
--
Subversion Kills
On Thu, Feb 13, 2014 at 12:00:53PM -0800, David Bagby wrote:
Hence my desire to see the default value of such an option be no
blending between G1 and G0.
This seems the safest, backward compatible approach.
I agree it's safest, but it is not backward-compatible.
LinuxCNC/EMC has always
On Mon, Jan 20, 2014 at 02:11:16AM +0100, Michael Haberler wrote:
Assuming the .so's are built, it comes down to where they are
installed (/usr/lib/linuxcnc?) and tell ldconfig about it (maybe a
linuxcnc entry in /etc/ld.conf.d)
currently we use -Wl,-rpath to do this.
On Sat, Jan 11, 2014 at 10:03:43AM -0700, EBo wrote:
On Jan 11 2014 6:19 AM, Chris Morley wrote:
Chris Radek is the release manager of 2.4.
My personal feeling is 2.4 should be considered end of life.
Releasing the last bug fixes would be fine (most are actually doc
fixes)
Chris
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
On Thu, Dec 26, 2013 at 09:17:18AM -0600, Charles Steinkuehler wrote:
simple move the joint until the switch closes. IMHO there needs to be
a way to write programmable homing routines that can perform coordinated
motion in joint and/or world space, But one thing at a time...
I don't see how
On Thu, Dec 26, 2013 at 11:54:34AM -0500, Robert Ellenberg wrote:
I like this idea, as it would make it much easier to make changes without
messing up other people's work. It would take a bit of reorganization,
since the motion module code is spread out over a few folders. I'm thinking
it
1 - 100 of 300 matches
Mail list logo