On 06/12/16 10:30, Andreas Pettersson
wrote:
I just assumed someone would know.. Someone did the changes.
Best thing i've seen so far in the code seems to be memory
management and middlware changes.
Making it more reliable and im guessing fast.
It was way less dependencies when compiling from source as well
thats nice. didnt have to go exploring outdated
packages from some distribution no one wants to use anymore (for
other reasons).
You did mention the mesa driver emulator for DS0-Nano tho, would
that make the nano a "general" IO card or could it
run stepper and servo cycles as well?! Seems like an interesting
low cost fix for the expensive mesa cards (even though i have a
pile of em).
The DE0-Nano-Soc is a development board for FPGA programming
It runs and ARM image of MK with the FPGA programmed to act as a
5i25, I have run my mill from one using the 7i76 (stepper) firmware,
I think there is a 7i77 one and some others too
https://github.com/machinekit/mksocfpga
https://github.com/machinekit/machinekit/issues/915
http://blog.machinekit.io/2016/11/you-will-recall-that-while-back-charles.html
http://blog.machinekit.io/2016/11/de0-nano-soc-update-on-sd-card-images.html
// Andreas
On 06/12/16 10:05, Andreas
Pettersson wrote:
Well the intention is not to judge anything in comparison..
Both has their own good and bad sides im guessing.
Would still be interesting out of a feature perspective to
know what makes them differ.
I do think machinekit is the way togo, i have found LinuxCNC
being tad bit outdated in several ways when compiling and
modifying the code in it. And machinekit seems to have
breathed some fresh air into it out of that regard.
And well i have been fiddling with LinuxCNCon and off for
the past 6 years tech knowledge no issues, compiling and
modifying it
for different hardware no issues there either. I actually
got both machinekit and linuxcnc running on the lattepanda
as of late yesterday.
Running them under Linuxmint 18, thats Ubuntu 16 if i
remember correctly it was not that "plug and play" as it
could have been.
But really not an issue either if you have some basic
knowledge of Linux overall.
I was just curious.. excuse my curiosity.. Both machinekit
and linuxcnc communitys seems to take offense at straight
forward questions
regarding the code base is there so much prestige invested
in them ?? really.. its just code..
I am not taking offence, the 'straight forward question' is just
so general with no advantage to anyone to research, it has not
been done.
This a collaborative open source project, no one makes money
from it, so don't have much interest in evangelising it
'advantages'.
If you have specific questions, they are much easier to cater
for.
it should stand up to a straight down comparison
to see what fits the individual why is that so hard to
understand.. and no i dont talk about mach don't know how
that could even be compared.
But apprently i should stop being curious. It's better to
just accept things as is and never question anything. Thats
the way to go.. *the stupid way*
Is there a good page for illuminating the
differences between linuxcnc and machinekit.. how far
apart are they these days since the first fork ??
No, I don't think anyone is interested in being judged in
comparison to linuxcnc (or Mach for that matter)
You can diff the repos and look at the documentation for
specific features / differences.
Is any of the core parts of linuxcnc project
maintained, like the updated motion planner , new mesa
drivers and such?
The new tp planner was not in linuxcnc when Machinekit was
forked. It is in both projects.
What 'new' mesa drivers are you referring to?
Machinekit has mesa support and even has support for Soc
FPGA boards emulating Mesa boards which is unique to
Machinekit.
I'm heavily consdering swapping linuxcnc for machinekit
on my lattepanda + mesa card project.. Because the old
linuxcnc is horrible to get working and perform well.
You are not going to find Machinekit any easier if you don't
have the technical knowledge.
There is no distro to install and the full images available
are for BBB and Rpi 2-3 only.
By the look of the lattepanda it was designed as a windoze
10 board and any linux support is fledgeling.
The fact that it is an Atom processor does not fill me with
joy, Intel actually produced some of these for tablets etc
that were so tied into windoze, you could not run linux on
them.
It also uses UEFI boot, with no obvious info as to whether
this can be disabled, further restricting choice and
complicating matters.
A quick search leaves me uncertain what linux system is
actually supported, Ubuntu 16 does not seem to run on it.
There might be Debian Jessie support, but the link just
takes you to a blurb about the Debian distro.
The LUbuntu link is dead.
The libraries required by machinekit mean you would need
Debian Wheezy or Jessie preferably, to be able to use the
packages available.
Looks like a technically interesting project, but if you
actually want to cut metal in particular, putting the Mesa
board(s) into a x86 desktop
is a much easier solution.
regards
But if it lacks features or differs to
much.. then that would be non-benficial. =)
--
website: http://www.machinekit.io
blog: http://blog.machinekit.io
github: https://github.com/machinekit
---
You received this message because you are subscribed to
the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
--
website: http://www.machinekit.io
blog: http://blog.machinekit.io
github: https://github.com/machinekit
---
You received this message because you are subscribed to a
topic in the Google Groups "Machinekit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/machinekit/w9poGXTfzYI/unsubscribe.
To unsubscribe from this group and all its topics, send an
email to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
--
website: http://www.machinekit.io
blog: http://blog.machinekit.io
github: https://github.com/machinekit
---
You received this message because you are subscribed to the
Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
--
website: http://www.machinekit.io
blog: http://blog.machinekit.io
github: https://github.com/machinekit
---
You received this message because you are subscribed to a topic
in the Google Groups "Machinekit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/machinekit/w9poGXTfzYI/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
--
website: http://www.machinekit.io
blog: http://blog.machinekit.io
github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google
Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
|
