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 E-
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 a
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
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 stop
Just curious if anyone knows what goodies are in the pipe?
2.7 has been such a big improvement (now that it has stabilized a bit), that
expectations are high for what new surprises might be coming along. I really
haven't looked at Master much since 2.7 to know what if much of anything is
comin
There are a lot of things that I can think of that would be cool in master
Things I am interested in...
JA - I have only lightly tested this.
UVW blending - probably done the most testing and so did Todd...
Reverse run - Maybe slightly heaver testing - but still light.
M98/M99 - slightly tested
sy
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 b
> 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 fe
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 a
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 unl
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 NML-over-T
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 NML-over-T
Here's a 3D printer manufacturer that decided to skimp on the failsafes. They
figured that their proprietary software and insisting that the printer be sent
back to fix *any* problem, including clogged nozzles, would suffice. (Somebody
didn't read about the Therac 25. Should be mandatory for any
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 f
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.
Accelerat
I couldn't find many new x86 systems with wired Ethernet for under $100
today. Intel has WiFi only x86 media PC's starting at ~$70.
ZOTAC ZBOX's start at ~$120
http://www.amazon.com/CoreAll--Mini-PC-Express-Chipset-ZBOXHD-ID40-U/dp/B004FPYL9M/ref=sr_1_2?s=pc&ie=UTF8&qid=1458670729&sr=1-2&keyword
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 l
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
18 matches
Mail list logo