On Thu, 24 Mar 2016 20:54:56 -0500
Jeff Epler wrote:
> I dared myself to fix nml-over-tcp, and got it working this evening.
> There are still no working sample configs (I think there's something
> buggy in configs/common/{client,server}.nml) but on my local machine the
>
On 10/16/2016 11:47 AM, Chris Albertson wrote:
> On Sun, Oct 16, 2016 at 1:13 AM, Nicklas Karlsson <
> nicklas.karlsso...@gmail.com> wrote:
>
>> .
>>> The master board sends the latch command on the parallel
>>> port bus to other boards on the bus, as well as the
>>> computer. The computer would
On Sun, 16 Oct 2016 09:47:26 -0700
Chris Albertson wrote:
> On Sun, Oct 16, 2016 at 1:13 AM, Nicklas Karlsson <
> nicklas.karlsso...@gmail.com> wrote:
>
> > .
> > > The master board sends the latch command on the parallel
> > > port bus to other boards on the bus, as
On Sun, Oct 16, 2016 at 1:13 AM, Nicklas Karlsson <
nicklas.karlsso...@gmail.com> wrote:
> .
> > The master board sends the latch command on the parallel
> > port bus to other boards on the bus, as well as the
> > computer. The computer would have the luxury of responding
> > before the next
On Sat, 15 Oct 2016 16:06:23 -0500
Jon Elson wrote:
> On 10/14/2016 12:09 PM, Erik Friesen wrote:
> > I guess I am not following how a hardware interrupt gets mapped to the
> > userspace/lcnc servo thread. Any pointers on this?
If the thread is implemented as a function
On Sat, 15 Oct 2016 16:06:23 -0500
Jon Elson wrote:
> On 10/14/2016 12:09 PM, Erik Friesen wrote:
> > I guess I am not following how a hardware interrupt gets mapped to the
> > userspace/lcnc servo thread. Any pointers on this?
> >
> >
> Supposedly, this is fairly easy
> >> ... It looks like it might
> >> be easier with the uspace / rt-preempt kernel than with
> >> rtai. It would reduce latency/jitter to ns levels.
If you build the system so that within servo period is OK things will get a lot
easier and will fit with ordinary theory fo real time scheduling,
On 10/14/2016 09:50 PM, Chris Albertson wrote:
> No, it would not get you to ns levels.
>
>
>I've
>> wanted to set this up on X86 through the parallel port for
>> some time (since about 2002, in fact) but it would take some
>> serious hacking on the PPMC driver. It looks like it might
>> be
On 10/14/2016 12:09 PM, Erik Friesen wrote:
> I guess I am not following how a hardware interrupt gets mapped to the
> userspace/lcnc servo thread. Any pointers on this?
>
>
Supposedly, this is fairly easy to do on the rt-preempt
kernel. It seems it was harder to do this through RTAI.
Michael
No, it would not get you to ns levels. The reason is that the
computer is not always in a state where it can be interrupted. The
hardware trigger (line going low) would happen but it has to wait
until the computer looks at the trigger signal. It only does this
between machine instructions
On Fri, Oct 14, 2016 at 08:11:38AM -0500, Charles Steinkuehler wrote:
> Setup a Mesa card with a periodic timer that triggers a capture of the
> current position and generates an interrupt (the Mesa VHDL code
> already supports this). In the servo thread, instead of waiting on a
> software timer,
<emc-users@lists.sourceforge.net>
> Subject: Re: [Emc-users] Linuxcnc on arm
>
> I guess I am not following how a hardware interrupt gets mapped to the
> userspace/lcnc servo thread. Any pointers on this?
As far as I know this is only done currently with Machinekit
(so their
I guess I am not following how a hardware interrupt gets mapped to the
userspace/lcnc servo thread. Any pointers on this?
On Fri, Oct 14, 2016 at 11:45 AM, Jon Elson wrote:
> On 10/14/2016 08:11 AM, Charles Steinkuehler wrote:
>> On 10/14/2016 7:11 AM, Erik Friesen
On 10/14/2016 08:11 AM, Charles Steinkuehler wrote:
> On 10/14/2016 7:11 AM, Erik Friesen wrote:
>> @Sebastian Kuzminsky Thanks for those docs.
>>
>> @Charles Steinkuehler
>>
>> How would you link an interrupt to linuxcnc?
> Setup a Mesa card with a periodic timer that triggers a capture of the
>
On 10/14/2016 7:11 AM, Erik Friesen wrote:
> @Sebastian Kuzminsky Thanks for those docs.
>
> @Charles Steinkuehler
>
> How would you link an interrupt to linuxcnc?
Setup a Mesa card with a periodic timer that triggers a capture of the
current position and generates an interrupt (the Mesa VHDL
@Sebastian Kuzminsky Thanks for those docs.
@Charles Steinkuehler
How would you link an interrupt to linuxcnc?
On Thu, Oct 13, 2016 at 9:15 PM, Charles Steinkuehler
wrote:
> On 10/13/2016 8:01 PM, Chris Albertson wrote:
>>
>> For sophisticated motion control you
I forgot to mention the system clock. As is in the software libraries it is
a variable although in almost all applications I have written clock
frequency is assumed to be constant. Then I started to program I usually
defined clock frequency to be constant since it is known at compile time. I
do
It might you used to register call back style functions but it is a lot
simpler to tell which functions will be called if function calls are added
in interrupt handler. The software I write usually is very simple and one
of the reasons is I use the static approach, it have limitations but are
You can choose to any of several libraries. I have an ARM M3 right
now using the Arduino IDE. Can't get much simpler than that.
Another one, an M4 here is being programmed using "mbed" library
because I need to do something more complex that needs an RTOS but
mbed is also very simple,
> TheCortex M is more like the Arduino then Pi. The M rarely runs an
> operating system and the software burned into flash and from an end
> user's level the software never change. You see the Arm Cortex M
> inside things like inkjet printers and microwave ovens and the like.
The librarys
On 10/13/2016 8:01 PM, Chris Albertson wrote:
>
> For sophisticated motion control you really need both. (my internet is
> in robots, no as much CNC) One to run an OS and drive a user interface
> and screen and talk over a network and so on. and a smaller processor
> to make I/O lines go up and
On 10/13/16, Erik Friesen wrote:
> To clarify my question, I am trying to understand at what level lcnc
> accesses hardware peripherals. For example, suppose I build a board with
> an spi dac peripheral to the arm, as well as write the kernel driver, if
> necessary. What type
king a sim runtime mode
(Todd Zuercher)
4. Re: Linuxcnc on arm (Erik Friesen)
--
Message: 1
Date: Thu, 13 Oct 2016 14:24:54 -0400
From: Erik Friesen <e...@aercon.net>
Subject: Re: [Emc-users] Linuxcnc on arm
To: &
s Karlsson)
3. Re: Hacking a sim runtime mode
(Todd Zuercher)
4. Re: Linuxcnc on arm (Erik Friesen)
--
Message: 1
Date: Thu, 13 Oct 2016 14:24:54 -0400
From: Erik Friesen <e...@aercon.net>
Subject: Re: [Emc-users]
Interesting info on spidev, but it doesn't surprise me. Isn't that
because they are non blocking read/writes to manage slow spi clocks,
etc? The calls end up in spi_sync, that says "This call may only be
used from a context that may sleep" so I would expect not so good
performance with this. My
If your device uses PREEMPT-RT realtime, then you can use any userspace
interface (ioctl, read, write, recv, send, etc) that gives you
acceptable latency in practice. Otherwise, you basically get to do
direct memory-mapped control of the applicable registers in your SOC,
because for xenomai and
On 10/13/2016 12:24 PM, Erik Friesen wrote:
> To clarify my question, I am trying to understand at what level lcnc
> accesses hardware peripherals. For example, suppose I build a board with
> an spi dac peripheral to the arm, as well as write the kernel driver, if
> necessary. What type of glue
Haas drives are basically pwm amplifiers that apparently need a 5v+- signal
120 degrees apart. Why bother with pwm, why not just put a good spi dac
controlled from the i.mx6? Then add a couple encoder ic's, or run a pic32
or similar to handle the qei.
On Thu, Oct 13, 2016 at 2:58 PM, Nicklas
Then you would need a powerful analog amplifier, unless it is a control signal
for a driver. An analog amplifier waste energy, a more efficient method is to
use an inverter card and then you use the PWM module in the micro controller to
generate signals for the inverter.
You also need to chose
In this scenario, the dac would be driving a bldc, so it would need to be
updated around 4-8khz.
On Thu, Oct 13, 2016 at 2:24 PM, Erik Friesen wrote:
> To clarify my question, I am trying to understand at what level lcnc
> accesses hardware peripherals. For example, suppose I
To clarify my question, I am trying to understand at what level lcnc
accesses hardware peripherals. For example, suppose I build a board with
an spi dac peripheral to the arm, as well as write the kernel driver, if
necessary. What type of glue do I need to provide in this situation?
On Thu, Oct
On the Cortex-M* model usually used on micro controllers there use to be a
reference manual. Usually there is register to configure pin functionality,
GPIO is a common default value and a register to select direction input or
output.
There use to a library but software complexity become lower
Resurrecting this thread, can anyone point me to docs, or other info what
it takes to link GPIO, or SPI devices into linuxcnc on an arm? On what
level does this happen? Userspace, Kernelspace, etc? I have done a bit of
kernel programming for the i.mx6.
On Thu, Mar 24, 2016 at 8:19 AM, Ron
On 2016-05-12 03:49, Jeff Epler wrote:
> On Thu, Mar 24, 2016 at 08:54:56PM -0500, Jeff Epler wrote:
>> The work is on a branch, "[origin/]jepler/master/nml-tcp" and will not
>> make it into a release branch anytime soon.
> I changed my mind about this. The branch has now been merged into
>
> On Thu, Mar 24, 2016 at 08:54:56PM -0500, Jeff Epler wrote:
> > The work is on a branch, "[origin/]jepler/master/nml-tcp" and will not
> > make it into a release branch anytime soon.
>
> I changed my mind about this. The branch has now been merged into
> master, so nml-over-tcp may be a
On Thu, Mar 24, 2016 at 08:54:56PM -0500, Jeff Epler wrote:
> The work is on a branch, "[origin/]jepler/master/nml-tcp" and will not
> make it into a release branch anytime soon.
I changed my mind about this. The branch has now been merged into
master, so nml-over-tcp may be a working feature in
> On Sun, Mar 20, 2016 at 04:51:39PM +, Ralph Stirling wrote:
> > The MachineKit folk are a year or two ahead of you guys
> > in thinking about the distributed control approach.
> [snip]
>
> The original "NIST EMC", a distant ancestor of LinuxCNC, already had a
> distributed control approach
> one change/improvement I see is a move towards linear motors instead of
> spindle/belt drives. And parallel kinematics (tripod, hexapod) seem to
> become more popular, mainly because the required algorithms can now
> fairly easily be implemented due to plenty of processing power.
>
> ...
>
>
Hi everyone,
On 26.03.2016 17:40, Dave Cole wrote:
> On 3/26/2016 3:59 AM, Nicklas Karlsson wrote:
>> Electronics have improved but then it come to mechanics or servo drives are
>> there any new innovations?
>
>>> Electronics have improved but then it come to mechanics or servo drives are
>>>
nhanced Machine Controller (EMC)" <emc-users@lists.sourceforge.net>
Sent: Saturday, March 26, 2016 12:00:44 PM
Subject: Re: [Emc-users] Linuxcnc on arm
All technology is like that. When it is new change happens very fast and
then as in matures the rate of change becomes slower. An e
All technology is like that. When it is new change happens very fast and
then as in matures the rate of change becomes slower. An example is
airplanes. We know what a Write Flyer looked like on 1905 but by 1915 the
planes used in world war I were much different and by the 1930, another 15
years
On 3/26/2016 3:59 AM, Nicklas Karlsson wrote:
> Electronics have improved but then it come to mechanics or servo drives are
> there any new innovations?
>>Electronics have improved but then it come to mechanics or servo drives are
>>there any new innovations?
Yes, they make and sell things now
My tractor is very old, probably more than 40 years and is still used. Motor
broke down once more than 15 years ago but is fixed. There are still spare
parts available. Tractors built the same way today so there are no new
innovation.
Electronics have improved but then it come to mechanics or
Sounds great.
I spent the last months working on servo drives, in particular to get some
hardware easy to work with built from not to expensive parts. Soon I will move
to higher level and hopefully be able to contribute something to Linuxcnc.
Regards Nicklas Karlsson
On Thu, 24 Mar 2016
wow! thx Jeff
tomp
On 03/25/2016 09:54 AM, Jeff Epler wrote:
> I dared myself to fix nml-over-tcp, and got it working this evening.
>
--
Transform Data into Opportunity.
Accelerate data analysis in your applications
I dared myself to fix nml-over-tcp, and got it working this evening.
There are still no working sample configs (I think there's something
buggy in configs/common/{client,server}.nml) but on my local machine the
linuxcncrsh-tcp test passes, and by using edited copies of its tcp.nml I
used axis and
Depending on the machine and the original construction, the iron can
last a lot longer than the controls if it is well maintained and lubed.
I've worked on many 40+ year old machines but almost all of them were
pre-1970 vintage. Heavy iron and built with replaceable/regrindable
ways etc.
On Thursday 24 March 2016 08:19:12 Ron Ginger wrote:
> I was helping a commercial screw machine shop that had a couple little
> KX1 mills. One was getting rather tired after 5 or 6 years of
> production use and having repeatability problem. I was speaking with
> the general manager and asked
> - Original Message -
> From: "Dave Cole" <linuxcncro...@gmail.com>
> To: emc-users@lists.sourceforge.net
> Sent: Wednesday, March 23, 2016 9:45:31 PM
> Subject: Re: [Emc-users] Linuxcnc on arm
>
> Who wants to use and maintain (if it is poss
I was helping a commercial screw machine shop that had a couple little
KX1 mills. One was getting rather tired after 5 or 6 years of production
use and having repeatability problem. I was speaking with the general
manager and asked "well how long do you expect a machine to last?" and
without a
so popular.
- Original Message -
From: "Dave Cole" <linuxcncro...@gmail.com>
To: emc-users@lists.sourceforge.net
Sent: Wednesday, March 23, 2016 9:45:31 PM
Subject: Re: [Emc-users] Linuxcnc on arm
Who wants to use and maintain (if it is possible) an original CNC control
m
>>doing it with x86 isn't very feasible.
Why not? Unless you have serious space or cost constraint issues
going with a PC based solution is still your best bet. What are the chances of
you finding a replacement ARM board of the
proper type 10 years from now.Siemens routinely uses PC
There isn't a need to exchange parts once they are in place. Board
manufacturers get by with flash gold plated connectors because they are lower
cost and the flash plating is only good for so many swipes before the connector
cannot meet its original spec of contact resistance, current
1. I have a chosen a DRV8824 for stepper while you use DRV8825 and I think only
maximum current is different.
2. You talk about TS-4900 or BBB with Cortex-A* CPU there I had chosen an
ordinary computer.
3. Instead of FPGA I have chosen cheap STM32 micro controllers.
I work with electronic
Do you have to exchange your SATA and PCIe devices very often? I only do
with my test systems. The controllers for machines might get a SATA or
PCIe device swapped once in it's lifetime of several years.
On 03/23/2016 02:28 PM, ceen...@in-front.com wrote:
> I second the point about not using a
I second the point about not using a PC. Most of the CNC reliability issues I
see are with backplane card edge connectors for DC servo drives and connectors
subject to vibration/chafing of gold plating and oxidation of tin plating. A
consumer grade PC motherboard is not meant for machine
ARM-Cortex-M* CPUs have a nested vectored interrupt NVIC controller with
selectable interrupt priorities. The NVIC is suitable for real time scheduling
according to rate monotonic, FreeRtos may be added on top if needed, in
particular there is nothing uknown disturbing. There are plenty of
ed Machine Controller (EMC)" <emc-users@lists.sourceforge.net>
Sent: Wednesday, March 23, 2016 7:22:39 AM
Subject: Re: [Emc-users] Linuxcnc on arm
Anyway, that is just dreaming. Reality is that when you want to sell
equipment, most will run far and fast from self retrofits.
On Wed,
I don't want bang for my buck. What I want is a control board I can drop
into my haas, and doing it with x86 isn't very feasible. Dropping a
embeddedarm ts4900 on a custom baseboard would be real slick, and it seems
that it could surely compete with the 1990's era motorola running at 40mhz.
In diagram there are first NML and then shared memory. If I put shared memory
buffer in micro controller it would talk NML with the EMCTASK.
> nml is the protocol/library between UIs and task, as well as between task
> and iocontrol. task (not realtime) uses a shared memory interface to
> talk
Then it come to 3D graphics this is the strong point on ordinary computer.
Strong point of micro controller is: 3D graphics, hard drives or other unknown
will not disturb execution, they are very simple and run software from the
internal flash.
My idea is to split linuxcnc in two and only run
nml is the protocol/library between UIs and task, as well as between task
and iocontrol. task (not realtime) uses a shared memory interface to
talk to motion (realtime).
Jeff
--
Transform Data into Opportunity.
I spent the past few days looking over the current state of ARM SOC's
for Linuxcnc and the open 3D driver situation hasn't changed much.
i.mx6 uses a Vivante GPU and you can build RT kernels and build from
open GPU driver source. The problem is NXP sells their 1-cores for ~$15
and their duals
I read the diagram and EMCTASK is connected by NML:
First step would be to get it to work again.
Second to move lower parts to micro controller.
Then lower parts are on micro controller there is no need to care about real
time perfomance in GUI.
Are all NML communication paths via
On Sun, Mar 20, 2016 at 04:51:39PM +, Ralph Stirling wrote:
> The MachineKit folk are a year or two ahead of you guys
> in thinking about the distributed control approach.
[snip]
The original "NIST EMC", a distant ancestor of LinuxCNC, already had a
distributed control approach with
On Tue, Mar 22, 2016 at 3:31 AM, Nicklas Karlsson <
nicklas.karlsso...@gmail.com> wrote:
> No the real time tasks in the work shop may be running by themself or
> waiting for answer from GUI but you can't trust the emergency stop. If you
> are on the beach emergency stop will not matter anyway
On 03/22/2016 11:13 AM, Nicklas Karlsson wrote:
>>
> User interface in a telephone may not be the most useful application but
> would be a possibility. To separate real time from others would however be
> useful. The procotol in between might also be useful to control machine via
> software on
> On 03/22/2016 05:15 AM, bari wrote:
> > But if my phone has the GUI and I'm at the beach do I need to run an
> > extra pair of conductors back to the machine?
> >
> > On 03/20/2016 01:22 PM, Jon Elson wrote:
> >> On 03/20/2016 11:57 AM, bari wrote:
> >>> How real time do you want the GUI? Is a
On 03/22/2016 05:15 AM, bari wrote:
> But if my phone has the GUI and I'm at the beach do I need to run an
> extra pair of conductors back to the machine?
>
> On 03/20/2016 01:22 PM, Jon Elson wrote:
>> On 03/20/2016 11:57 AM, bari wrote:
>>> How real time do you want the GUI? Is a few second lag
Well I'm glad that machinekit now has this scenario covered.
> On 03/22/2016 05:31 AM, Nicklas Karlsson wrote:
>> No the real time tasks in the work shop may be running by themself or
>> waiting for answer from GUI but you can't trust the emergency stop. If you
>> are on the beach emergency
No the real time tasks in the work shop may be running by themself or waiting
for answer from GUI but you can't trust the emergency stop. If you are on the
beach emergency stop will not matter anyway unless you are machining a large
bomb.
> But if my phone has the GUI and I'm at the beach do
On 03/22/2016 11:15 AM, bari wrote:
>>> How real time do you want the GUI? Is a few second lag behind the
>>> machines state ok? How about E-stop or Start/Stop from the UI? What's
>>> safe? 1 second max, 10 seconds? If you are milling while at the beach
>>> miles away does it matter? What problem
But if my phone has the GUI and I'm at the beach do I need to run an
extra pair of conductors back to the machine?
On 03/20/2016 01:22 PM, Jon Elson wrote:
> On 03/20/2016 11:57 AM, bari wrote:
>> How real time do you want the GUI? Is a few second lag behind the
>> machines state ok? How about
555 ( hahaha in Thai )
no! use old hammond organ for that buzzy sound
reminds me of herbie hancock 'rockit'
https://www.youtube.com/watch?v=GHhD4PD75zY
tomp
On 03/21/2016 01:50 AM, bari wrote:
> It sounds like it's more fun than practical. My Android phone hardly
> works as a phone. I can't
Then it come to telephones real buttons are at an advantage then dialing. The
touch screen is however nice for other purposes.
On Sun, 20 Mar 2016 12:50:44 -0500
bari wrote:
> It sounds like it's more fun than practical. My Android phone hardly
> works as a phone. I
m out, don't rely on my summary.
>
> -- Ralph
>
> From: bari [bari00...@gmail.com]
> Sent: Sunday, March 20, 2016 10:02 AM
> To: emc-users@lists.sourceforge.net
> Subject: Re: [Emc-users] Linuxcnc on arm
>
> How have they lowered the cost of the control and GUI h
Micro controllers with SPI or UART is the cheap stuff for control of switches
for servo motors. Ether with or without cat is the expensive stuff at least
compared to the cost of a cheap micro controller. One important point is also
communication distances within a CNC machine is usually short.
Same problem as ordinary software except the emergency stop. I expect there
would be big red hard wired button for emergency stop as usual.
The problem solved is demand for GUI is same or at least similar as for other
software.
On Sun, 20 Mar 2016 11:57:18 -0500
bari
> > > > I am thinking about split in two with real time threads on micro
> > > > controller and the computer for the user interface. It would also be a
> > > > flexible solution then it come to choice of user interface but require
> > > > extra hardware.
> > > >
> > >
> > > If I were designing
On 03/20/2016 12:02 PM, bari wrote:
> How have they lowered the cost of the control and GUI hardware?
>
>
Pololu-style drivers are under $5 from China, I use the 8825
version, good up to about 2 A at modest voltage.
The CRAMPS board (that I make to Charles Steinkuehler's
design) is $79.95, and
On 03/20/2016 11:51 AM, Ralph Stirling wrote:
> The MachineKit folk are a year or two ahead of you guys
> in thinking about the distributed control approach. You
> ought to go over to their site and study their roadmap in
> detail before spending lots of time reinventing wheels again.
> They use
On 03/20/2016 11:57 AM, bari wrote:
> How real time do you want the GUI? Is a few second lag behind the
> machines state ok? How about E-stop or Start/Stop from the UI? What's
> safe? 1 second max, 10 seconds? If you are milling while at the beach
> miles away does it matter? What problem are we
It sounds like it's more fun than practical. My Android phone hardly
works as a phone. I can't imagine using it to control a VMC. I'd like to
see an old 60's TV as a GUI with a re-purposed Calliope used for a
keyboard or similar.
On 03/20/2016 12:19 PM, Ralph Stirling wrote:
> I don't think
, March 20, 2016 10:02 AM
To: emc-users@lists.sourceforge.net
Subject: Re: [Emc-users] Linuxcnc on arm
How have they lowered the cost of the control and GUI hardware?
I'd like to have a machine controller and GUI for less than the cost of
a new low cost x86 PC and display. Is there a worki
On 03/16/2016 08:25 AM, W. Martinjak wrote:
> It's emty.
>
> http://buildbot.linuxcnc.org/dists/wheezy/2.7-rtpreempt/binary-armhf/
> http://buildbot.linuxcnc.org/dists/wheezy/master-rtpreempt/binary-armhf/
We build and test on arm, but we currently don't produce debian packages.
LinuxCNC 2.7 and
How have they lowered the cost of the control and GUI hardware?
I'd like to have a machine controller and GUI for less than the cost of
a new low cost x86 PC and display. Is there a working BOM yet for this?
On 03/20/2016 11:51 AM, Ralph Stirling wrote:
> The MachineKit folk are a year or two
How real time do you want the GUI? Is a few second lag behind the
machines state ok? How about E-stop or Start/Stop from the UI? What's
safe? 1 second max, 10 seconds? If you are milling while at the beach
miles away does it matter? What problem are we solving?
On 03/20/2016 02:10 AM, Nicklas
From: Chris Albertson [albertson.ch...@gmail.com]
Sent: Sunday, March 20, 2016 9:38 AM
To: Enhanced Machine Controller (EMC)
Subject: Re: [Emc-users] Linuxcnc on arm
On Sun, Mar 20, 2016 at 12:10 AM, Nicklas Karlsson <
nicklas.karlsso...@gmail.com> wrote:
> > > I am thinking abo
On Sun, Mar 20, 2016 at 12:10 AM, Nicklas Karlsson <
nicklas.karlsso...@gmail.com> wrote:
> > > I am thinking about split in two with real time threads on micro
> > > controller and the computer for the user interface. It would also be a
> > > flexible solution then it come to choice of user
> Preempt-RT will be mainlined into stock linux fairly soon now so its just
> becomes a kernel config option but I doubt real time kernels will ever be
> standard for common desktop distributions as they typically have
> lower performance (excluding latency) than non RT kernels
There exist
FYI, the nxgen controller runs around $15K.
On Wed, Mar 16, 2016 at 12:10 PM, andy pugh wrote:
> On 16 March 2016 at 15:52, W. Martinjak wrote:
>
> >> The problem with the Pi is that the obvious choice for IO, Ethernet,
> >> is connected via the USB
On 16 March 2016 at 12:17, Erik Friesen wrote:
> I have been doing some work with an i.mx6 of late, and wonder why the quad
> couldn't do linuxcnc? It seems there is some obscure reason I read
> somewhere.
http://buildbot.linuxcnc.org/
Shows that we are building an armhf
On Sunday 20 March 2016 04:28:35 Gregg Eshelman wrote:
> Somewhere back in the archives of thedailywtf.com is one about when
> the company that wrote Wireshark got bought by another company. During
> integration of the two companies systems, the Wireshark guys used it
> to help sort things out,
> > I am thinking about split in two with real time threads on micro
> > controller and the computer for the user interface. It would also be a
> > flexible solution then it come to choice of user interface but require
> > extra hardware.
> >
>
> If I were designing this in the current century
> Real time is not one of the main concerns of the kernel devs. The kernel
> has graphics drivers that interfere with real time as well as X.
Probably right no one are interested enough. Good real time performance require
proper priority of everything handled from interrupts, I also read system
On 03/16/2016 10:17 AM, andy pugh wrote:
> On 16 March 2016 at 16:03, W. Martinjak wrote:
>
>> Ok, and any suggestions for the toolchain and build sequence?
>
> Probably simplest to compile on the device itself rather than get
> involved in the complexities of
RTAI patches the kernel with an interrupt pipeline and handler that can
take over real time interrupts but drivers can still interfere with it.
Things used to be worse. Especially with integrated GPU's. We did lots
of RTAI development over the past few years and we had difficulty
building
Hi,
I think Raspberry Pi Module 3 is a good choice, I'll try it when I get a
board soon.
Regards,
Yanjun Luo.
2016-03-16 23:25 GMT+08:00 bari :
> The i.mx6 can easily run Linuxcnc. The issues that you'll run into are
> the high cost of the i.mx6 boards and getting the GUI
Wow, 25% more expensive.
:/
http://www.shop.cncmonster.de/LinuxCNC/FPGA-Karten/USB/Parallelport/7I90HD-Parallel-SPI-Anything-I-O-card::393.html?MODsid=ab1fd9c2053920f289f27a2a6c15f815
Do you know some cheaper offers on this side of the pond?
On 2016-03-16 17:33, andy pugh wrote:
> On 16 March
higher priority then where does the real time kernel of the
LinuxCNC fit in?
John Dammeyer
> -Original Message-
> From: Nicklas Karlsson [mailto:nicklas.karlsso...@gmail.com]
> Sent: March-16-16 9:42 AM
> To: Enhanced Machine Controller (EMC)
> Subject: Re: [Emc-users]
1 - 100 of 150 matches
Mail list logo