On 04/05/2017 05:39, David Bynoe wrote:
Thank you so much for doing that! This is awesome.
I am not a programmer (but learning, slowly.) But I will play around
with it, out of curiosity, what do you mean by problems with running
actual gcode?
The config is just a sim of a conventional milling machine.
If you try to run the Machinekit demo for instance you will see:-)
You need to test within your actual machine configuration.
Good luck
The machine fortunately is rather robust, worse case scenario is the
head whips around and I spend a few minutes untangling some string,
which I am getting pretty good at.
On Tuesday, 2 May 2017 02:38:54 UTC-7, Schooner wrote:
On 02/05/17 10:10, schoo...@btinternet.com <javascript:> wrote:
On 01/05/17 17:58, David Bynoe wrote:
Thank you for the tips, that relink solves the install problem
but it doesn't fix the insmod errors, I get the same ones as
before.
The kinematics file I want to use is this one:
https://github.com/dbynoe/Spark-Drawbot/blob/master/kinematics/drawbotkins.c
<https://github.com/dbynoe/Spark-Drawbot/blob/master/kinematics/drawbotkins.c>
That version has automatic homing features and some other stuff
that will be removed but its known working on linuxcnc. It was
built for this machine:
https://www.youtube.com/watch?v=hrsDBdnj5E8
<https://www.youtube.com/watch?v=hrsDBdnj5E8>
I am curious about what changed, I thought the whole point of
comp was that it allowed the building of hal components and
kinematics files outside of the source tree. Seems crazy that a
full rebuild/reinstall is necessary for one minor piece of
translation code.
comp has never been for compiling kinematics files outside the tree.
It is for building realtime modules from scripts requiring the
minimal C knowledge by the user.
It might be possible to build your file with comp, if you specify
the correct linkage, but you will notice that all the other
kinematic modules are
not built using it.
The kinematics file you are trying to use has no support for
vtables, that is at the heart of the problem and is what has
changed since it allegedly 'worked OK'
If you switch on debugging before launching and look at
/var/log/linuxcnc.log you will find the point of failure as (yes
I have built it)
*May 2 09:15:17 INTEL-i7 msgd:0: hal_lib:22291:rt
halg_reference_vtable:104 HAL error: vtable 'drawbotkins' version
1000 not found**
**May 2 09:15:17 INTEL-i7 msgd:0: hal_lib:22291:rt MOTION:
hal_reference_vtable(drawbotkins,1000) failed: -2*
You need to read
https://github.com/machinekit/machinekit/issues/438
<https://github.com/machinekit/machinekit/issues/438>
and look at the changes made to kinematics.h and trivkins.c to
use vtables
I have built the drawbotkins module in the file tree and created
a demo sim for it as per the screenshot attached.
It is of general interest as it demonstrates the vtable code
required and for the amended kinematics module itself, so I will
get it included in the
repo kinematics code and it will be in the packages in a day or so.
regards
The PR is at https://github.com/machinekit/machinekit/pull/1205
<https://github.com/machinekit/machinekit/pull/1205>
You can see the code changes etc in that and watch it to see when
it is likely the new packages will be available (about 3 hours
after merge)
The sim is just to demo loading and homing, if you try to run
gcode you will get in all sorts of problems :-P
It would be good if you could provide a better sim in due course.
I have an older version of a machine kit image on a beaglebone
circa 2015 and comp just worked out of the box. Wanted to
modernize so I could use a touch screen and wifi. Here is it
running before:
https://www.youtube.com/watch?v=z0YQYwmbbT0
<https://www.youtube.com/watch?v=z0YQYwmbbT0>
On Monday, 1 May 2017 07:03:13 UTC-7, Schooner wrote:
On 01/05/17 14:11, Marius Alksnys wrote:
> AFAIR I used this command:
> sudo ln -s /usr/lib/linuxcnc/xenomai /usr/lib/linuxcnc/posix
>
> After that comp installs components correctly.
That will get around the issue of posix flavour and give
somewhere to
install to and source from, certainly.;-)
There may well be an issue still with the kinematics linkage
as per the
previous message I quoted, that is
best dealt with by building within the source tree.
Give comp a try and see what happens, if you get an insmod
error that it
is unable to find vtable or similar
you are back to a source build
>
> 04/30/2017 09:48 PM, David Bynoe rašė:
>> I am having issues getting custom kinematics modules
compiled and
>> working on the debian jessie machinekit system image for
beagle bone
>> black. (full system details below)
>
--
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+...@googlegroups.com <javascript:>.
Visit this group at https://groups.google.com/group/machinekit
<https://groups.google.com/group/machinekit>.
For more options, visit https://groups.google.com/d/optout
<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+...@googlegroups.com <javascript:>.
Visit this group at https://groups.google.com/group/machinekit
<https://groups.google.com/group/machinekit>.
For more options, visit https://groups.google.com/d/optout
<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
<mailto: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.