All,
I am getting a "TRAM write error", and not finding much on it in a search. I
am running lcnc 2.8.0-pre1, and using the Mesa 7i43 board. The error occurs
when I physically assert the enable for the third axis. The first two axes
came up fine, but if the only change I make to the
The robot in the videos most defiantly NOT something you would want to use
LinuxCNC for.They do real-time path planning. Today I'm implement that
with something like a self driving fork lift and save the cost of all that
track. The machine would roll on the floor with wheels and if it was
Several years ago I worked on a quote for a job of similar size but the
accuracy had to be much better. I think it had to be plus or minus
0.010 inches or so over the entire 3D space.
A 3D laser tracker was part of the control scheme to track the actual
tool head location.
That way standard
Hmmm, interesting but there's guys already working on that. No, different
application but with some similarities - placing a calculated amount of a fluid
at a specific point or range of points in a 3D space.
> On Aug 22, 2017, at 5:02 PM, Gene Heskett wrote:
>
>> On
On Tuesday 22 August 2017 16:03:45 andy pugh wrote:
> On 22 August 2017 at 13:57, Gene Heskett wrote:
> > The "axis.py" file this patch apply's to, does not exist in the
> > latest (as of yesterday) 2.8-pre install on my raspberry pi running
> > jessie.
>
> If the file
That's why I wonder about rolling my own versus starting with something like
that in the video linked below. Not sure which would be harder, more
expensive.
https://youtu.be/NRO98Rm58-k
> On Aug 22, 2017, at 4:30 PM, Chris Albertson
> wrote:
>
> The resolution
On Tuesday 22 August 2017 13:01:01 Rick Gresham wrote:
> I'm exploring options for a 3 axis controller similar in some ways to
> typical cnc router-like application. What may make my application
> unique is the size of the 3D space in which the tool operates: up to
> about 150' x 150' x 50'. In
The resolution is controlled by the step size of the motor. It's
mechanical. Getting to 1/8 inch over a 100 foot space is easy in terms of
the software but you will need to invent some hardware that holds to those
tolerances.
On Tue, Aug 22, 2017 at 3:35 PM, Rick Gresham
I've only just started trying to learn a little about realtime motion control
so I don't have a good answer re: units. While a complete Star Trek-like plant
console might be really cool, I suspect the investment would be hard to justify
for a largely lights out application.
I don't need the
On 22 August 2017 at 18:01, Rick Gresham wrote:
> I'm exploring options for a 3 axis controller similar in some ways to typical
> cnc router-like application. What may make my application unique is the size
> of the 3D space in which the tool operates: up to about 150'
On 22 August 2017 at 13:57, Gene Heskett wrote:
> The "axis.py" file this patch apply's to, does not exist in the latest
> (as of yesterday) 2.8-pre install on my raspberry pi running jessie.
If the file doesn't exist then you won't be able to run the Axis GUI,
so the
I'm exploring options for a 3 axis controller similar in some ways to typical
cnc router-like application. What may make my application unique is the size
of the 3D space in which the tool operates: up to about 150' x 150' x 50'. In
addition, I need to control tool changes and
On Tuesday 22 August 2017 05:10:18 suavesteve wrote
0001-axis.py-add-support-for-MDI-cursor-movement.patch
The "axis.py" file this patch apply's to, does not exist in the latest
(as of yesterday) 2.8-pre install on my raspberry pi running jessie.
I have a now out of date git pull that I am not
I've ran into this problem, too; best as I could see, it wasn't possible
to use the keys with that particular entry box, so I made a few
modifications to the axis.py script to give me left + right, home and
end keys. It seems to have worked fine for me, for > 6 months.
Philip
>From
14 matches
Mail list logo