Hi There,
I am looking for someone willing to develop Machinekit based customized CNC
Machine Interface and Machinekit Image for one of our Product.
Kindly contact for further details.
Pranav
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/mach
Sure, push the updates.
Il giorno martedì 2 ottobre 2018 15:18:53 UTC+2, Schooner ha scritto:
>
> Good to hear.
>
> It just makes the minimal changes, as it appeared the only thing that had
> changed was the base address.
>
Agree, I was going to a lot more of non-necessary code
> If you are
Good to hear.
It just makes the minimal changes, as it appeared the only thing
that had changed was the base address.
If you are happy with that, I can push a PR, so it is in the
packages.
On 02/10/18 13:39, mngr wrote:
I tested you
I tested your branch, everything is working fine, it loads and the spi
writes.
Il giorno domenica 30 settembre 2018 22:55:45 UTC+2, mngr ha scritto:
>
> It will probably take me more of a evening because the next couple of days
> is already full. Maybe I will test your version and then make anot
The easiest thing to do would be to do this beforehand.
There is no conditional checking available within an ini file, since
this file
is read by other programs and does not of itself do anything.
Run from a script and check for the existence of the joystick
You can have as many RIP builds as you like.
They will not conflict, unless you try to run them one after another
from the same terminal session,
with the pathspec for the last one still set.
You should preferably not have a binary install (from packages) on
Hi
I note in the instructions it says that MK will conflict with an LCNC
install, is this only for OS-level realtime builds ? I have ROS (Robot
Operating System) on this system and would like to try some things out, but
I also have RIP builds for LCNC on this machine too.
Cheers
Ross
--
web
