Mach4 Industrial allows multiple instances of the full system including
gcode interpretation. It is only being supported with 6 instances but
the design is not limited. Lua scripts can start with
inst = mc.mcGetInstance()
if (inst == 0) then
so full coordination between instances and scripts
On 9/25/2015 4:31 PM, Ron Ginger wrote:
> Mach4 Industrial allows multiple instances of the full system including
> gcode interpretation. It is only being supported with 6 instances but
> the design is not limited.
That's really nice! :-)
Dave
---
This email has been checked for viruses by
> ..
> What would be useful in such a setup is an ability to pass information
> directly from one LCNC host to another to coordinate functions such as
> transferring a pallet with work on it to another machine for additional
> operations.
>
> One example would be two machines doing an
Actually this problem touches the independent axes problem that I
foresee in my sliding head lathe where an axis that will be cutting
later needs to start part way though another's coordinated move in
order to save time.
Dave Caroline
On 24/09/2015, andy pugh wrote:
> On 24
On 24 September 2015 at 02:18, Jerry Scharf wrote:
> I now need to extend it to run two separate robots off the same linuxcnc
> controller and receiver program
If you need the robots to synch then I think you need to be a bit cleverer.
If you imagine one robot moving in XYZ
Sounds to me like one 5 axis machine. You should be able to issue one line
of code. All 5 axes should move coordinated in relation to each axis home
position no matter the distance or orientation of the components.
On Thu, Sep 24, 2015 at 5:21 AM, andy pugh wrote:
> On 24
On 24 September 2015 at 12:44, Dave Caroline
wrote:
> Actually this problem touches the independent axes problem that I
> foresee in my sliding head lathe where an axis that will be cutting
> later needs to start part way though another's coordinated move in
> order
might be better to let the two talk to each other in some way so move
starts/runs are really synchronised properly rather than rely on
buffers.
eg classic ladder or some clocking or whatever
Dave Caroline
On 24/09/2015, Jerry Scharf wrote:
> Hi,
>
> I have hacked up a simple
On 9/24/2015 12:57 AM, Dave Caroline wrote:
> might be better to let the two talk to each other in some way so move
> starts/runs are really synchronised properly rather than rely on
> buffers.
> eg classic ladder or some clocking or whatever
>
> Dave Caroline
That sounds good. What you Do Not
It doesnt sound like the task is well defined here on mail list.
If the 2 independent(?) systems do not require interpolation _between_
them, then M65 thru M66 could provide the 'handshaking'.
Each would have a 'busy' and a 'fin' signal.
This is extremely sequential.
Else please explain more,
Hi,
These are two completely independent machines with no coordination. Many
times only 1 will be operating. I am trying to work out what happens when
both are operating at the same time. It would be simpler to have two
separate controller, but that's not where we are at right now.
jerry
On
FWIW,
The Modbus TCP interface in Classic Ladder supports both a client and a
server, so peer to peer networking with connections to Hal and Gcode
interlocks would be possible with the standard software.
Dave
On 9/24/2015 7:44 AM, Dave Caroline wrote:
> Actually this problem touches the
From: Jerry Scharf [jsch...@finsix.com]
Sent: Thursday, September 24, 2015 8:05 AM
To: Enhanced Machine Controller (EMC)
Subject: Re: [Emc-users] multiple gcode streams in parallel
Hi,
These are two completely independent machines with no coordination. Many
times only 1 will be operating. I
>>It would be simpler to have two
separate controller, but that's not where we are at right now.
Simple is good.
For another $200 you can get a second PC.
If this is a one-off project I'd strongly consider throwing more
hardware at the project.
I don't know what your labor rates are, but $200
On 24 September 2015 at 19:24, Jerry Scharf wrote:
> There is an axis for the second robot and the hal files are all set up.
> This is about the python interface and running two separate motion commands
> at the same time.
The Python interface sends MDI, MDI commands run in
On Thursday 24 September 2015 04:00:46 Gregg Eshelman wrote:
> On 9/24/2015 12:57 AM, Dave Caroline wrote:
> > might be better to let the two talk to each other in some way so
> > move starts/runs are really synchronised properly rather than rely
> > on buffers.
> > eg classic ladder or some
There is an axis for the second robot and the hal files are all set up.
This is about the python interface and running two separate motion commands
at the same time. If I can do that, then a simple threading system works,
otherwise it needs to be fancier...
jerry
On Thu, Sep 24, 2015 at 10:47
Dave,
This is what I thought and after talking to the person, we can wait the few
days to get a separate system in for him. Everyone will be happy this way.
It's a small system so I am going the BBB/cape/machinekit way (I hate it
when the controller is larger than the machine.).
Sounds like
thanks for the input so far.
I know a second controller would be a better solution, but I need something
this week... I will look at some hardware for the next couple weeks. A
couple hours of programming now would save us time, which is our critical
resource.
I know about machinekit, but had
I suspect there is actually a lot of interest in being able to run
multiple paths at the same time, but I also think it is likely a lot of
development work to make it happen.
Dave
On 9/24/2015 4:05 PM, Jerry Scharf wrote:
> Dave,
>
> This is what I thought and after talking to the person, we
On 24/09/2015 12:44, Dave Caroline wrote:
> Actually this problem touches the independent axes problem that I
> foresee in my sliding head lathe where an axis that will be cutting
> later needs to start part way though another's coordinated move in
> order to save time.
>
> Dave Caroline
>
yep i
On 9/24/2015 1:20 PM, Dave Cole wrote:
> I think everyone is trying to find a way to do what you want with the
> existing software.
>
> In order to run two different Gcode programs at the same time, you would
> need two gcode interpreters and two planners running at the same time.
>
> That is not
> ...
> I now need to extend it to run two separate robots off the same linuxcnc
> controller and receiver program. This brought up a question about the
> python interface.
Add an extra axis ?
--
I think everyone is trying to find a way to do what you want with the
existing software.
In order to run two different Gcode programs at the same time, you would
need two gcode interpreters and two planners running at the same time.
That is not possible with the existing software that I am
24 matches
Mail list logo