Re: [Machinekit] machinekit kernel sources??

['schooner30@btinternet' via Machinekit]

You should find the source package in the repo has the full source files

http://deb.machinekit.io/debian/pool/main/l/linux/linux_3.8.13.orig.tar.xz

Don't bother trying to use apt, just download from the http link and 
unarchive it


The config file distributed with the kernel should be able to be renamed 
.config in the source tree root dir and you have the build setup that 
produced the kernel in the package


regards


On 16/02/18 19:18, Damien D wrote:

Hi,

I'm using this working machinekit image: 
https://rcn-ee.com/rootfs/bb.org/testing/2017-02-12/machinekit/


As you might know, this kernel have some USB hot plug issue and I have 
a patch 
 
for it that I would like to apply.


For that I need to (re)compile the kernel and maybe also kernel 
modules (including those from machinekit?)..


At the moment I'm stuck at the easiest part, I cannot find/don't know 
where to look the exact sources that have been used to build the 
kernel within the image 
 I'm 
using.


Does anyone know where I can find sources&makefiles that have been 
used to produce the kernel (3.8.13-xenomai-r83) that is in this image? 
or even for the all rootfs image?


Thanks
--
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.

Re: [Machinekit] Re: Questions over Rpi3 vs BeagleBone

[schooner30@btinternet]

On 22/12/17 06:55, Alexander Rössler wrote:

If you are planning to write the GPIO drivers yourself, you might also
consider the OIDROID C2, as reported here
https://github.com/machinekit/machinekit/issues/1269 it has very low
latency.
Yes see entry at 
https://github.com/machinekit/machinekit/issues/1269#issuecomment-326965404


The main problem I had with getting machinekit to build on a Pine64 was 
the lack of an io.h header.


Mine was not an elegant or definative solution, but it worked.
Don't doubt you could come up with a better solution, looking at 
removing the unsupported low level functions from

an aarch64 build would probably be a better tactic:-)



But, we do not officially support aarch64 yet. Nevertheless, I would
love to see it working.

'Ric W' via Machinekit writes:


Thanks for the info
At the moment I've got a Beagle Bone Green and a Rpi3 handy
so I'll probably try both out and use the BBG as the "Gold standard" to
check for differences in timing / jitter using a scope.
I'll also see if I can get machinekit working under a 64bit os just for fun
on the Pi3

I'm afraid the Pi3 still uses Ethernet via USB so that's not great.
For the hardware I've got a small ooznest Ox CNC, belt driven with a 1.5Kw
spindle / Nema23's
At the moment it's running a Arduino Due / RADDS board / TinyG (G2Core) /
REPS128 stepper drivers but with no end stops
I've also got access to a larger version of the ooznest Ox at the hackspace
in manchester, that one uses a GRBL board.

I'm thinking of writing my own front end using .Net Core (doesn't require
mono) and javascript. Although I'll need to dig into the API's to figure
that one out

You might also want to check out Machinetalk:
https://machinekoder.com/machinetalk-explained-part-1-introduction/


Many Thanks
Richard


On Tuesday, December 19, 2017 at 4:25:27 PM UTC, Ric W wrote:

Hi,
I've recently been looking into setting up my own CNC Electronics.

The first question I've got is over latency performance.
I know the Beaglebone AM3358 has a single core 1Ghz Arm Processor and 2 x
PRU's running at 200Mhz
For the Rpi3 it has a quad core 1.2Ghz Arm Processor - BCM2837 - A53

Now I know that one of the ways machinekit gets low latency is to use the
PRU's for dedicated motion control on the BBB.
But I was wondering if the Pi3 had one of it's cores dedicated to the
Operating system and the other 3 somehow dedicated to motion control then
how would this compare.
One difference the PRU has is that it's instructions take 1 cycle to
complete, but on the other side the Pi3's other cores are running at around
1000Mhz faster with 3 available.
Is this a supported setup from machinekit's point of view (has someone
already done this?)

The next question I've got is regarding hooking up the control board to
seperate stepper driver boards etc.
I know one of the downsides of an Rpi3 is the GPIO count, so I started
looking into different options
I liked the look of EtherCat but I think there's no open source hardware
shields
and most of them just appear to use a netX52 to fire SPI data over
Ethernet.
Since the boards I'm planning on using will all be in the same shielded
case I figured I might just try a shielded SPI cable to each slave board.

There's some discussion online over what the max SPI speed is for an Rpi3,
theoretically 125Mhz although I've not tested that yet.
My plan is to use some TMC2660 Stepper drivers that can give a smoother
waveform (quieter)
and provide feedback on the amount of force the stepper motor is using,
with an auto cut off if the force goes over a certain limit.

If I were to try something like this then I'd guess I'd have to write some
custom HAL modules etc.
But I wanted to get any comments first from the folks here as to what
they're thoughts might be for the hardware.

Also btw I think the search box is broken on the machinekit website

Many Thanks
Richard




--
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.

Re: [Machinekit] build machinekit from source with xenomai 3.0.6, launch failed.

[schooner30@btinternet]

Sorry just re-read this and realised the kernel is 4.1.18 and the 
*xenomai version* is 3.06


Xenomai 3 does not work with Machinekit and there are no plans to 
support it, you will need to use a rt-preempt kernel instead



On 20/12/17 12:17, schooner30@btinternet wrote:




On 20/12/17 09:44, steve.bette...@gmail.com wrote:

Hello, everyone,
  My OS is lubuntu 17.10. My board is a x86_64 platform with ATOM 
CPU. I installed xenomai 3.0.6 with linux 4.1.18. Xenomai latency 
test is ok.


The main question is why Xenomai and why that version?

Xenomai is not good enough for software stepping on x86 and 3.0.6 is 
quite old, the BBB uses 3.18


I build machinekit from source:
cd src
./autogen.sh
./configure --with-xenomai 
--with-xeno-config=/usr/xenomai/bin/xeno-config
from the "configure" output, I can figure out that xenomai user space 
is used.
but when I run "sudo make setuid" "source ./scripts/rip-environment" 
"machinekit"

I just can't start it normally.

The output info is below. Can anyone help? Thanks!
I did not change anything else.

robot@ubuntu:/Downloads/machinekit-master/src$ sudo chmod 777 
/var/log/linuxcnc.log

robot@ubuntu:/Downloads/machinekit-master/src$ sudo make setuid
../scripts/check-build-vs-configure-sha: line 11: in: command not found

WARNING: configure was last run at Wed Dec 20 09:01:15 CST 2017 at 
git version

WARNING: now the git version is: not in a git repo
WARNING: consider executing 'make clean; sh autogen.sh; ./configure ' 
before running make


This is a non fatal warning that the original SHA from autogens 
creation of configure and the repo built differ.

Normally because something changed between running autogen.sh and make



make: Entering directory '/home/robot/Downloads/machinekit-master/src'
test -f ../libexec/pci_read && chown root ../libexec/pci_read && 
chmod 4750 ../libexec/pci_read || true
test -f ../libexec/pci_write && chown root ../libexec/pci_write && 
chmod 4750 ../libexec/pci_write || true
test -f ../libexec/rtapi_app_xenomai && chown root 
../libexec/rtapi_app_xenomai && chmod 4750 
../libexec/rtapi_app_xenomai || true;

make: Leaving directory '/home/robot/Downloads/machinekit-master/src'

robot@ubuntu:/Downloads/machinekit-master$ . ./scripts/rip-environment
robot@ubuntu:/Downloads/machinekit-master$ machinekit
MACHINEKIT - 0.1
Machine configuration directory is 
'/home/robot/Downloads/machinekit-master/configs/sim'

Machine configuration file is 'emcweb.ini'
Starting Machinekit...
Warning - 
/home/robot/Downloads/machinekit-master/libexec/rtapi_app_posix not 
setuid

'sudo make setuid' missing?
/home/robot/Downloads/machinekit-master/scripts/realtime: line 192: 
/home/robot/Downloads/machinekit-master/libexec/rtapi_app_posix: No 
such file or directory

rtapi_app startup failed - aborting


This is telling you that rtapi_hal_posix does not exist

Given that you are supposed to be running a xenomai kernel, then 
something is screwed up.


The most obvious cause, could be that whilst you built a xenomai 
kernel, you have not booted into it and are still running a posix 
kernel, for which you did not build

because you specified the kernel to build for as xenomai


0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted

io started
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted

halcmd loadusr io started
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted

Shutting down and cleaning up Machinekit...
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
Warning - 
/home/robot/Downloads/machinekit-master/libexec/rtapi_app_posix not 
setuid

'sudo make setuid' missing?
Cleanup done
Machinekit terminated with an error. You can find more information in 
the log:

/home/robot/linuxcnc_debug.txt
and
/home/robot/linuxcnc_print.txt
as well as in the output of the shell command 

Re: [Machinekit] build machinekit from source with xenomai 3.0.6, launch failed.

[schooner30@btinternet]

On 20/12/17 09:44, steve.bette...@gmail.com wrote:

Hello, everyone,
  My OS is lubuntu 17.10. My board is a x86_64 platform with ATOM CPU. 
I installed xenomai 3.0.6 with linux 4.1.18. Xenomai latency test is ok.


The main question is why Xenomai and why that version?

Xenomai is not good enough for software stepping on x86 and 3.0.6 is 
quite old, the BBB uses 3.18


I build machinekit from source:
cd src
./autogen.sh
./configure --with-xenomai --with-xeno-config=/usr/xenomai/bin/xeno-config
from the "configure" output, I can figure out that xenomai user space 
is used.
but when I run "sudo make setuid" "source ./scripts/rip-environment" 
"machinekit"

I just can't start it normally.

The output info is below. Can anyone help? Thanks!
I did not change anything else.

robot@ubuntu:/Downloads/machinekit-master/src$ sudo chmod 777 
/var/log/linuxcnc.log

robot@ubuntu:/Downloads/machinekit-master/src$ sudo make setuid
../scripts/check-build-vs-configure-sha: line 11: in: command not found

WARNING: configure was last run at Wed Dec 20 09:01:15 CST 2017 at git 
version

WARNING: now the git version is: not in a git repo
WARNING: consider executing 'make clean; sh autogen.sh; ./configure ' 
before running make


This is a non fatal warning that the original SHA from autogens creation 
of configure and the repo built differ.

Normally because something changed between running autogen.sh and make



make: Entering directory '/home/robot/Downloads/machinekit-master/src'
test -f ../libexec/pci_read && chown root ../libexec/pci_read && chmod 
4750 ../libexec/pci_read || true
test -f ../libexec/pci_write && chown root ../libexec/pci_write && 
chmod 4750 ../libexec/pci_write || true
test -f ../libexec/rtapi_app_xenomai && chown root 
../libexec/rtapi_app_xenomai && chmod 4750 
../libexec/rtapi_app_xenomai || true;

make: Leaving directory '/home/robot/Downloads/machinekit-master/src'

robot@ubuntu:/Downloads/machinekit-master$ . ./scripts/rip-environment
robot@ubuntu:/Downloads/machinekit-master$ machinekit
MACHINEKIT - 0.1
Machine configuration directory is 
'/home/robot/Downloads/machinekit-master/configs/sim'

Machine configuration file is 'emcweb.ini'
Starting Machinekit...
Warning - 
/home/robot/Downloads/machinekit-master/libexec/rtapi_app_posix not setuid

'sudo make setuid' missing?
/home/robot/Downloads/machinekit-master/scripts/realtime: line 192: 
/home/robot/Downloads/machinekit-master/libexec/rtapi_app_posix: No 
such file or directory

rtapi_app startup failed - aborting


This is telling you that rtapi_hal_posix does not exist

Given that you are supposed to be running a xenomai kernel, then 
something is screwed up.


The most obvious cause, could be that whilst you built a xenomai kernel, 
you have not booted into it and are still running a posix kernel, for 
which you did not build

because you specified the kernel to build for as xenomai


0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted

io started
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted

halcmd loadusr io started
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted

Shutting down and cleaning up Machinekit...
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
0"000.000| BUG in low_init(): [main] binding failed: Operation not 
permitted
Warning - 
/home/robot/Downloads/machinekit-master/libexec/rtapi_app_posix not setuid

'sudo make setuid' missing?
Cleanup done
Machinekit terminated with an error. You can find more information in 
the log:

/home/robot/linuxcnc_debug.txt
and
/home/robot/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
--
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.googl

Re: [Machinekit] Re: Machinekit package repo

[schooner30@btinternet]

Thanks Robert,

I'll have a look tomorrow



On 27/10/17 18:14, Robert Nelson wrote:

On Fri, Oct 27, 2017 at 12:11 PM, schoone...@btinternet.com
 wrote:

Hi Robert

Whilst you are looking at this can I pick your brains for the best of your
rt-preempt kernels to upgrade the DE0-NANO-Soc
mksocfpga image with.

I have already upgraded the existing SD image to Stretch and have it
working, but with the old 4.1.22-ltsi-rt23 kernel

I have crossbuild tools installed and can quite happily build one from your
sources if required

I'd use their 4.9.x branch:

https://github.com/altera-opensource/linux-socfpga/branches/all

as that has rt right now:

https://www.kernel.org/pub/linux/kernel/projects/rt/

But as soon as they open up socfpga-4.13 i'd move to that..

Regards,



--
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.

Re: [Machinekit] Motion stuttering in in the beginning of a large NGC file.

[schooner30@btinternet]

Glad to hear you found it.

Logging can cause havoc sometimes, but I have never had that problem 
with machinekit


Obviously a combination of BBB limitations plus unrealised mklauncher 
setting generating mega-messages


On 23/07/17 17:06, Seth Pierson wrote:

I resolved this problem. It was completely logging related.

I had checked my ini file, and Debug was set to zero, logs were still 
coming through at the debug level.


I had also looked at run.py, the file that mklauncher calls to start 
machinekit. There was no cmd line options that changed the logging 
level (or so I thought). After a few hours of head banging I saw this 
line in run.py:

|
launcher.set_debug_level(5)
|

I changed it on a whim to zero: No more debug logging. I had assumed 
that this was the log level for the launcher...It also changes the 
logging level of machinekit. Now I know.


Thank you for assisting me. It is much appreciated.
--
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.

Re: [Machinekit] Machinekit does not have rapid-override?

[schooner30]

I don't know what is wrong with your apt setup.


Just go to http://deb.machinekit.io/debian/pool/main/m/machinekit/

and download the relevant packages of the correct serial number


Install them with

sudo dpkg -i 


Then move the package to /var/cache/apt/archives if you want to retain them


On 11/07/17 17:29, Sag ich Dir nich wrote:
okay i have found the version and it is a older version, i did sudo 
apt-get update and sudo apt-get install machinekit but everytime it 
says its the newest version


Am Dienstag, 11. Juli 2017 18:13:50 UTC+2 schrieb Schooner:


On 11/07/17 16:47, Sag ich Dir nich wrote:

so i did sudo apt-get install machinekit-xenomai as well as
update and upgrade but i still dont have rapid override pins :/


halui is in the machinekit package not machinekit-xenomai


Back to my Q of yesterday, find out which package you have installed

It should be
machinekit_0.1.1499676489-1mk.travis.master.gitcc2f4453~1wheezy_armhf.deb

That *does* contain rapid-override



Am Dienstag, 11. Juli 2017 16:41:38 UTC+2 schrieb Schooner:


On 11/07/17 15:29, Sag ich Dir nich wrote:



the line "sudo sh -c \
"echo 'deb http://deb.machinekit.io/debian
 wheezy main' > \
/etc/apt/sources.list.d/machinekit.list""
also dont seem to change something, it still tries to
download from deb.dovetail-automata.com



Check that machinekit.list points to deb.machinekit.io
 and that the dovetail-automata
entry is not in /etc/apt/sources.list

Then *apt-get update* and it is not possible for it to still
be looking in dovetail-automata





Am Dienstag, 11. Juli 2017 15:58:59 UTC+2 schrieb Schooner:


On 11/07/17 14:29, Sag ich Dir nich wrote:

Get:1 http://deb.dovetail-automata.com/
 wheezy/main
machinekit armhf
0.1.1499676489-1mk.travis.master.gitcc2f4453~1wheezy
[6,287 kB]


That has not been the correct debian repo for years

You need to change your apt settings to use
http://deb.machinekit.io

See the website documents
http://www.machinekit.io/docs/getting-started/APT-packages-wheezy/


Then remove the machinekit-dev package, it is optional
so nothing else depends upon it.

*Then* you will be able to update and download the
latest packages

-- 
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.
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+...@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.

Fwd: [Machinekit] Announcement - package changes

[schooner30]

This sound familiar?


There is no machinekit-dev package any more


On 03/07/17 08:56, Schooner wrote:
This is to advise a change to package contents, effective from today 
at build serial **0.1.1499017896-1**


From hereon, the package *machinekit-dev *is deprecated and the 
contents of that package will be found in the *machinekit- 
package (eg /machinekit-xenomai/)


The reason for this is that comp and instcomp have not worked for 'out 
of tree' builds on armhf, since the current build system was introduced.
Limitations on available time for package builds to complete led to 
the machinekit-dev package being built on posix only.
This seemed reasonable for something that just holds a binary, headers 
and a few other files. :)


An unforeseen knock on of this, was that Makefile.inc, which is used 
by comp and instcomp to get basic system flavour settings amongst 
other things, is
generated from the setting of the current build and was just showing 
posix threads in use.


This is why people have been trying to build components for xenomai 
say and comp is failing because it cannot find the posix folder or 
just producing a posix module

instead of the required xenomai one.

Please test builds on package based armhf systems, using these new 
packages, and report back.


All packages have been checked and have the Makefile.inc set to the 
flavour of the containing package, so they should work now


regards

--
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.

Re: [Machinekit] Machinekit does not have rapid-override?

[schooner30]

On 10/07/17 18:17, Sag ich Dir nich wrote:
i do believe its Machinekit 7.11 with Xenomai (3.8.13-xenomai-r79) 
Kernel and Debian Wheezy OS (Debian 4.6.3-14) (i have downloaded the 
Machinekit Image long ago and worked on this version since then and 
doing upgrades and updates so should be up to date).

No such thing as Machinekit 7.11

https://askubuntu.com/questions/15452/how-can-i-find-the-version-number-of-an-installed-package-via-dpkg



i have created a sim config but have not found rapid-override, only 
spindle and feed-override


You don't have to create one, just run axis_mm from the sim/axis/ 
section of the installed sample configs


If it does not show, you don't have the new package



Am Montag, 10. Juli 2017 18:52:52 UTC+2 schrieb Schooner:


On 10/07/17 17:25, Sag ich Dir nich wrote:

so i did Sudo apt-get update and upgrade but it still says the
pin does not exist, how did you get that?


A bit of precision please

What machinekit package version do you have installed, on which
kernel flavour and OS?

What command are you trying to execute and what is the exact error
message?

The pins exist

https://github.com/machinekit/machinekit/blob/master/src/emc/usr_intf/halui.cc#L939


but even if you have the right package version, a misspelt pin
name will get the same error message

Have you run a sim, looked in HAL Configuration at the halui pins?



Am Montag, 10. Juli 2017 17:27:42 UTC+2 schrieb Sag ich Dir nich:

That would be very nice! Thanks for the info :)

Am Sonntag, 9. Juli 2017 17:43:56 UTC+2 schrieb Schooner:


On 09/07/17 15:14, schoo...@btinternet.com wrote:


On 09/07/17 10:06, schoo...@btinternet.com wrote:



It was backported here
https://github.com/machinekit/machinekit/pull/1091

but the changes to halui were not included


This fixes the lack of pins in halui
https://github.com/machinekit/machinekit/pull/1233


Will take a while to get tested / merged and then
packages produced

Check its status tomorrow and test the new packages


They are in the process of building now, should all be
ready in an hour or so

machinekit-* 0.1.1499613980*gitc713d606*.deb of today's
date refers

Proof of life attached

-- 
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 .
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.

Re: [Machinekit] Re: Machinekit not starting after compilation

[schooner30]

On 24/05/17 11:36, michelvanderbregge...@gmail.com wrote:
Strange thing is that the same config file works when I start it with 
the prebuild machinekit on the same machine.


It looks like the rtapi_app fails, or is unresponsive for some reason


It is always possible that this is just where it got to when the process 
died, so not directly relevant.


Do what Bas suggested and use DEBUG=5 and look at /var/log/linuxcnc.log 
after a failure


libwebsockets is optional now since 
https://github.com/machinekit/machinekit/commit/320e76dbd51ab5bd2fa8a04dcb4ea90f2394bfbe


If you built a RIP without enabling libwebsockets, it will be undefined, 
even though the library is still there, should not be connected to your 
problem.






Op woensdag 24 mei 2017 11:44:45 UTC+2 schreef Schooner:

It is saying it cannot find the section [DISPLAY] INTRO_GRAPHIC

can't say further without your .ini file

You should not need INTRO_GRAPHIC or INTRO_TIME, but if you do
have them
what they point to must be valid



On 24/05/17 10:32, michelvand...@gmail.com  wrote:
> Can not find -sec DISPLAY -var INTRO_GRAPHIC -num 1
> 2511
>   PID TTY  STAT   TIME COMMAND
> Stopping realtime threads
> Unloading hal components

--
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.

Re: [Machinekit] Re: Machinekit not starting after compilation

[schooner30]

It is saying it cannot find the section [DISPLAY] INTRO_GRAPHIC

can't say further without your .ini file

You should not need INTRO_GRAPHIC or INTRO_TIME, but if you do have them 
what they point to must be valid




On 24/05/17 10:32, michelvanderbregge...@gmail.com wrote:

Can not find -sec DISPLAY -var INTRO_GRAPHIC -num 1
2511
  PID TTY  STAT   TIME COMMAND
Stopping realtime threads
Unloading hal components


--
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.

Re: [Machinekit] hb04 Pendant integration

[schooner30@btinternet]

On 12/05/17 17:56, Mike Cinquino wrote:
 /var/cache/apt/archives only has in it 1 directory called "partial" 
and one file called "lock"? I am not sure where to find the package name?
It is probably set to delete the packages after install, to save space, 
not to worry


I attached the config sim folder. This is auto generated from the 
Configuration Selector.

It looks OK, you can check the contents against the repo to be sure

What I need is the error output when the sim is launched and 'does not work'





On Fri, May 12, 2017 at 11:55 AM, schoone...@btinternet.com 
 > wrote:



On 12/05/17 16:30, Mike Cinquino wrote:

The image I burned in relation to last message
was: bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img


Today I did:

sudo apt-get update
sudo apt-get dist-upgrade

on the above system.

I read the email string and am trying to figure out what other
than that I would need to do. I do not see that he is getting the
same error as I am.

After doing the above I get the same result.

I also tried:

Downloaded file from:

https://github.com/machinekit/machinekit/blob/master/configs/sim/axis/xhc-hb04



The .hal files from the above link do not appear to be correct.
They gave errors and I replaced with sim files generated through
Configuration Selector.

Same result.

I also tried:

user@INTEL-i7:/usr/src/machinekit/src/hal/utils$ realtime restart
user@INTEL-i7:/usr/src/machinekit/src/hal/utils$ halcmd loadrt
debounce
user@INTEL-i7:/usr/src/machinekit/src/hal/utils$ halcmd show
pexists debounce.0.0.in 
Exists
user@INTEL-i7:/usr/src/machinekit/src/hal/utils$ halrun -U

I am confused by this as the sequence of commands went in with no
errors but nothing visible happened. Is the object of this to get
the return "Exists" back? If so I got it back.

Thank you for you patience. I am slowly learning I think well
I am trying anyway :)


That shows that you have a working version of halcmd :)

The XHC is a horrible mess of tcl code, which checked for pins by
parsing the output from halcmd show pin {pinname}

The problem with that was that the output changed some years back
from the original in Linuxcnc and it had not worked since.
I replaced the parsing with a new function which just emits
'Exists' if the pin name is valid, simplifying everything and ensuring
it works even if further formatting changes are made to halcmd.

Changes on 7th February 2017 clobbered the fix and the halcmd part
was fixed again on 6th March 2017.

If you still get an error running the sim, you will need to attach it.
I cannot be the same as you had previously, but there is still
scope for problems :)

Also look in /var/cache/apt/archives and see what the exact file
name of the main machinekit package is, which will pinpoint exactly
what you have installed
If you updated today, it should probably be
machinekit_0.1.1493733523-1mk.travis.master.git06e9c856~1jessie_armhf.deb








On Fri, May 12, 2017 at 1:11 AM, schoone...@btinternet.com
 mailto:schoone...@btinternet.com>> wrote:

Please read the previous thread I linked

You can't just burn AN updated image, from the ancient one
you were using.

You need to use an image which has the halcmd pexists fix
reinstated after the multicore merge.



On 12/05/2017 01:33, Mike Cinquino wrote:

I burned an updated image. Looks like I made some progress.
It looks like it found it. I get the following error.

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=/usr/libexec/linuxcnc/inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
MACHINEKIT - 0.1
Machine configuration directory is
'/home/machinekit/machinekit/configs/sim.axis.xhc-hb04-1'
Machine configuration file is 'xhc-hb04-layout2.ini'

INIFILE=/home/machinekit/machinekit/configs/sim.axis.xhc-hb04-1/xhc-hb04-layout2.ini
PARAMETER_FILE=sim-9axis.var
TASK=milltask
HALUI=halui
DISPLAY=axis
Starting Machinekit...
Starting Machinekit server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting Machinekit IO program: io
io started
halcmd loadusr io started
Starting HAL User Interface program: halui
Shutting d

Re: [Machinekit] time vs timev2

[schooner30@btinternet]

On 28/04/17 17:38, Alexander Vasilevski wrote:


I can't use


# Servo task period, in nano-seconds

*SERVO_PERIOD =   7*

tryed 10 ->BBB almost "frozen"

so

set *SERVO_PERIOD =   50*

reset button works



OK, the problem is the limited power of the BBB, not the actual component.

You will ned to tune your threads to suit







On Friday, April 28, 2017 at 6:30:57 PM UTC+3, Schooner wrote:


On 28/04/17 15:53, schoo...@btinternet.com  wrote:


On 28/04/17 15:41, Alexander Vasilevski wrote:

machinekit@beaglebone:~$ sudo dpkg -l | grep machinekit
ii  machinekit
 0.1.1491990670-1mk.travis.master.git992d53e8~1jessie  
 armhfPC based motion controller for

real-time Linux
ii  machinekit-xenomai
 0.1.1491990670-1mk.travis.master.git992d53e8~1jessie  
 armhfPC based motion controller for

real-time Linux


That is the latest build, don't understand what the problem is,
will have a think.


I don't know what the problem was, but I cannot reproduce it on
amd64 Jessie.

I have produced a sim config which contains a pyvcp panel to
display the program run time.
This config uses the time component

Unzip the zip file and place the folder /time-sim into your
~/machinekit/configs dir

Then run machinekit and select the My-Configurations drop down and
select time-sim/axis_mm.ini

Once homed run the demo Machinekit gcode and the cycle time
counter will increment.
Stop the code and it will stop
Press reset and it will zero the counter

It is a very crude counter, but shows time.icomp is working

See screen capture

regards

--
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.

Re: [Machinekit] HAL driver dev: call a function when update a parameter

[schooner30@btinternet]

On 24/02/17 17:41, Matteo Facchinetti wrote:

Hi,

I'm writing an HAL driver that I want to push when I'll finish but I 
have a question about RW parameters and the possibility to call a 
function when user update its value.


In detail, I have a complicated control word with more bits with 
different meanings and values and a constraint like this:

"if you set a flag, the software should reset others".

I created a parameter for each flags/property that user can control 
and in my driver I like to call a control function that update the 
control word each time user update value of the related parameter with 
setp command.


Is possible to associate a function to the update parameter event?


The easiest is probably just to store the 'old' value and at every poll, 
check this against the current

value.
If they are different execute the code you want to.

Just need to make sure you initialise the param value properly when the 
component starts.




Or is there an other way to make that?


Thanks in advance,

Matteo



--
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.

Re: [Machinekit] Re: de0 nano soc for MK

[schooner30@btinternet]

On 14/02/17 17:32, Klemen Zhivko wrote:

The image you are pushing  - this is pre multicore image right?
If yes - why not have latest multicore with corrrect rfb-s (if they 
exist) ?


No it is not, it was created today, just check the git history

Just download the image, write to SD and run it

If you start 'updating' or doing anything else before establishing it 
runs, you are on your own.




Is this shomewhere available to download?


Maybe I am hitting something that ArcEyed described as:
"
Do a /sudo apt-get update/ and install any extra packages you require,
but do NOT /apt-get upgrade /if you are using this image, because 
there is a later one, and upgrading will overwrite its components and 
I could not get that one to work.

"

??



That is taken from and even older blog entry and relate to the problem 
that was solved some time back.






Dne torek, 14. februar 2017 18.25.20 UTC+1 je oseba Schooner napisala:

I have just pushed a new image to the server.

Give me 5 minutes to move it to where it should be and I will give
you a link to download from

I suspect you are mixing old and new, it just isn't worth messing with

On 14/02/17 17:09, Klemen Živkovič wrote:

With SIM it's same:

machinekit@mksocfpga:~/git/machinekitOff/src$ DEBUG=5
machinekit@mksocfpga:~/git/machinekitOff/src$ machinekit
~/git/machinekitOff/configs/hm2-soc-stepper/5i25-socfpga.ini
MACHINEKIT - 0.1
Machine configuration directory is
'/home/machinekit/git/machinekitOff/configs/hm2-soc-stepper'
Machine configuration file is '5i25-socfpga.ini'
Starting Machinekit...
io started
:0: Component 'iocontrol' ready
:0: Program 'io' started
halcmd loadusr io started
hm2-soc-ol-stepper-5i25.hal:29: Realtime module 'trivkins' loaded
hm2-soc-ol-stepper-5i25.hal:33: Realtime module 'tp' loaded
hm2-soc-ol-stepper-5i25.hal:37: Realtime module 'hostmot2' loaded
hm2-soc-ol-stepper-5i25.hal:40: Realtime module 'hm2_soc_ol' loaded
hm2-soc-ol-stepper-5i25.hal:40: rc=-1:
hal_call_usrfunct(newinst,--
config="firmware=socfpga/dtbo/DE0_Nano_SoC_DB25.7I76_7I85S_GPIO_GPIO.dtbo
num_stepgens=4 num_encoders=1 num_mencoders=4") failed: -1 -
Operation not permitted
Shutting down and cleaning up Machinekit...
:0: Realtime threads stopped
:0: Realtime module 'hm2_soc_ol' unloaded
:0: Realtime module 'hostmot2' unloaded
:0: Realtime module 'tp' unloaded
:0: Realtime module 'trivkins' unloaded
:0: Realtime threads stopped
Cleanup done
Machinekit terminated with an error.  You can find more
information in the log:
/home/machinekit/linuxcnc_debug.txt
and
/home/machinekit/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the
terminal

There are rbf files:

machinekit@mksocfpga:~/git/machinekitOff/src$ ls
/lib/firmware/socfpga -R -all
/lib/firmware/socfpga:
total 5036
drwxr-xr-x  3 root root4096 Nov 12 16:33 .
drwxr-xr-x 17 root root4096 Nov 12 16:31 ..
-rw-r--r--  1 root root 1790908 Oct 28 21:21
DE0_Nano_SoC_DB25.7I76_7I76_7I76_7I76.rbf
-rw-r--r--  1 root root 1709760 Oct 28 21:21
DE0_Nano_SoC_DB25.7I76_7I85S_GPIO_GPIO.rbf
-rw-r--r--  1 root root 1634572 Oct 28 21:21
DE0_Nano_SoC_DB25.7I77_7I76_GPIO_GPIO.rbf
drwxr-xr-x  2 root root4096 Nov 12 16:33 dtbo

/lib/firmware/socfpga/dtbo:
total 40
drwxr-xr-x 2 root root 4096 Nov 12 16:33 .
drwxr-xr-x 3 root root 4096 Nov 12 16:33 ..
-rw-r--r-- 1 root root 1001 Oct 28 21:21
DE0_Nano_SoC_DB25.7I76_7I76_7I76_7I76.dtbo
-rw-r--r-- 1 root root 1046 Oct 28 21:21
DE0_Nano_SoC_DB25.7I76_7I76_7I76_7I76.dts
-rw-r--r-- 1 root root 1001 Oct 28 21:21
DE0_Nano_SoC_DB25.7I76_7I85S_GPIO_GPIO.dtbo
-rw-r--r-- 1 root root 1047 Oct 28 21:21
DE0_Nano_SoC_DB25.7I76_7I85S_GPIO_GPIO.dts
-rw-r--r-- 1 root root 1001 Oct 28 21:21
DE0_Nano_SoC_DB25.7I77_7I76_GPIO_GPIO.dtbo
-rw-r--r-- 1 root root 1046 Oct 28 21:21
DE0_Nano_SoC_DB25.7I77_7I76_GPIO_GPIO.dts
-rw-r--r-- 1 root root  940 Oct 28 21:21 Makefile
-rw-r--r-- 1 root root 1007 Oct 28 21:21 template.dts

BUT these might come from ArcEye's image and not from build I
just make. I am not sure who or how this rbf files could be
(re)created...



On Tue, Feb 14, 2017 at 6:05 PM, schoo...@btinternet.com
 > wrote:


On 14/02/17 16:50, Klemen Zhivko wrote:

In dmesg Iget:

[ 4054.891575] fpga_manager fpga0: writing
socfpga/DE0_Nano_SoC_DB25.7I76_7I85S_GPIO_GPIO.rbf to
Altera SOCFPGA FPGA Manager
[ 4055.106816] fpga_manager fpga0: Error after writing
image data to FPGA
[ 4055.113936] failed to load fpga image

This shows that the config string was passed OK to the
hm2_soc_ol driver, but there was a problem
either with the board

Re: [Machinekit] 5i25 hostmot2 problem

[schooner30@btinternet]

I did look at that, as all my configs have values there.
However it should just mean the maximum possible as you say, so it 
didn't seem to be wrong.


Glad you have it sorted

On 30/01/17 17:31, Curtis Dutton wrote:

SOLVED!

Thanks for your help.

The stepgen maxaccel and maxvel values were being set to 0 in my 
config.. In linux cnc this was ok. The documentation states in 
machinekit and linuxcnc that when set to 0 that the stepgens will only 
be limited to the step timing settings and otherwise are not limited. 
This does not seem to be the case as when I set the values of maxaccel 
and maxvel on the stepgen to more than 0, then the stepgen works.




On Monday, January 30, 2017 at 11:22:35 AM UTC-5, Curtis Dutton wrote:

Ok I was running a rip build from master. Commit:
079b1ed4adb30c60079d0d43a173002201f34538. Which appears to be the
latest commit.

Do you know what commit your sim is running from? I'd like to
build that version and see if I get a better result.

So I guess the hm2 driver now just exposes everything in the
config of the 5i25 and doesn't need the commit string?


I'll try the sim here later today to see if it works for me.

Thanks,
  Curt



On Sunday, January 29, 2017 at 6:33:44 AM UTC-5, Schooner wrote:

If you run the hm2_stepper sim you should see position-fb
updated when you jog, as per screen shot.
Does that work?

Your test does not run
*newthread servo-thread cpu=0 100*
is asking for a new thread called /servo-thread/, of a period
/cpu=0/

Next the hm2_pci config string
*loadrt hm2_pci config="num_mencoders=0 num_stepgens=5
num_pwmgens=1"*
AFAIK has not been used for some while and will also not run
hence

https://github.com/machinekit/machinekit/blob/master/configs/hm2-stepper/5i25.ini#L11



https://github.com/machinekit/machinekit/blob/master/configs/hm2-stepper/hm2-stepper-5i25.hal#L44



the configuration is whatever the 5i25 is flashed as.

All of which raises the question of what you are running and
on what platform.

On a recent pull of machinekit on a amd64 computer running
Jessie, the 5i25 works fine, I have used my
5i25/7i76 combo a lot just recently.

On 28/01/17 20:26, Curtis Dutton wrote:

Ok I have attached a halcmd file that demonstrates the issue.

The debug.txt contains the output of the halrun session.

Notice that after the position-cmd is set, position-fb has
not changed.

The firmware on the 5i25 is 5i25_7i85sspx2


Thanks,
   Curt

On Saturday, January 28, 2017 at 2:43:18 AM UTC-5, Schooner
wrote:

Without seeing your configuration files, we cannot even
begin to guess.

If you have done the same as John Fairbanks on the 7i80
post, you may have omitted the trajectory planner

*loadrt tp*

after trivkins or whatever is loaded and not specified

*tp=tp kins=trivkins* at the end of the motmod
configuration line

These are specific to Machinekit and without them your
config will act more like a sim.

See the sample configs for using 5i25 with Machinekit


https://github.com/machinekit/machinekit/blob/master/configs/hm2-stepper/hm2-stepper-5i25.hal#L33



regards



On 27/01/2017 22:07, Curtis Dutton wrote:

I'm experimenting with running my laser engraver with
machinekit. Currently I'm running linuxcnc master and
have it set up and operating properly.


The trouble I'm having is that my stepgens and my pwmgen
doesn't seem to be working properly. The signals are all
wired up properly, I have my threads scheduled properly
etc


The stepgen shows it is enabled.

Anyhow when I send my position command to the stepgen
nothing seems to happen The position-feedback from the
stepgen does not change.

I also have a 7I84 hooked up to the 5i25 through
sserial. All of those pins show up in hal so
communication is working properly there. I can set pins
on the 7i84 interface and have physically verified that
they are changing properly.


It looks like the 5i25 is not responding even though it
works properly under linuxcnc.


Any suggesstions on what could be going on? Any tips or
  

Re: [Machinekit] Slow BBB MachineKit GUI's and Alternatives.

[schooner30@btinternet]

On 19/01/17 23:51, Oliver Rew wrote:
/"I've used a couple of J1900 motherboards and they work great. 
Together with a 5i25/6i26 + 7i76 mesa card"


/Which J1900 motherboard did you use with the 5i25? The only one I saw 
on newegg with a full PCI slow is the quad-core version(as I 
understand it, this is undesirable for LinuxCNC). Thanks!


If you are just using a servo thread and hardware step generation (ie 
mesa cards ) it really does not matter.  The servo thread max jitter 
with a rt-preempt kernel is low enough for that.


I have a quad core mini ITX Pentium that I run a 5i25/7i76 combo from 
and found that having a
50K dummy base thread (running but nothing attached to it) kept the cnc 
code on one core mostly and brought the servo thread max jitter down 
from 100K to about 28K


If you are using a parport on a base thread, then you will probably need 
to use `isolcpus 1,2,3` kernel parameter to isolate 3 of the 4 cores to 
get the best latency, that is if you are using linuxcnc and a rtai 
kernel ( as opposed to machinekit, which no longer supports rtai )


On Thursday, January 19, 2017 at 12:31:42 AM UTC-8, Bas de Bruijn wrote:



On 19 Jan 2017, at 08:45, "schoo...@btinternet.com "
> wrote:




On 18/01/2017 22:10, Oliver Rew wrote:

Hi, I recently got very exciting about running my CNC from
MachineKit on a BBB, but after getting a BBB and a cape, my
hopes were quickly deflated by the lethargic performance of the
GUI's on the BBB. I have tried tkMachineKit and it is indeed
faster, but is nowhere near the convenience and speed of
GMOCCAPY or AXIS running on a very old x86.

Retrofitting old CNC's is a hobby of my father and myself, and
my hope with MachineKit on BBB was for a small, simple, drop-in
system that didn't require me to search for a big and old x86
box and deal with all it's ambiguities in order to run LinuxCNC.
However, these limitations on GUI's have dashed my hopes.


Not sure how running on a x86 can be described as full of
ambiguities compared to a BBB!

People have been doing it for years before the BBB was even made.

A BBB feels slower than running on an old x86, because it is.

I would suggest that you have a basic level rethink and look at
the available mini ITX boards available like the J1900, which are
known to work well and have 10x the processing power of a BBB,
with inbuilt graphics that work well.


I've used a couple of J1900 motherboards and they work great.
Together with a 5i25/6i26 + 7i76 mesa card.



Some of the fanless ones take a 12v supply and can quite easily
be built into a controller head for instance.


I have attempted to research the underlying problems with the
GUI, but these discussion quickly go beyond my knowledge. As far
as I can tell, it mostly has to do with the 3D g-code preview
window and the graphics driver behind it. Is the problem that
the driver doesn't run well on the BBB, or that any sort of 3D
g-code simulation is too process intensive for the BBB? People
have said disabling the g-code simulation does increase speed
significantly, but g-code simulation is a standard feature on
most CNC softwares and is very handy for the end user.

Are there any current, more feature-rich GUI's that work well on
the BBB? Are there any in development?


Have a look at the remote GUI capabilities of qtquickvcp and Cetus.



Thanks!

-- 
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 .
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+...@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 

Re: [Machinekit] Re: axis, configuration

[schooner30@btinternet]

On 04/01/17 17:06, Jeff Pollard wrote:

Hi,

  I think you are looking for what is described in section 1.11.7 here:

http://linuxcnc.org/docs/2.4/html/gui_axis.html


Or better still you could use our own docs, which we spent a lot of time 
getting up together.


Especially as the Axis in Machinekit contains several enhancements, 
including one which

specifically does this
http://www.machinekit.io/docs/gui/axis-machinekit-enhancements/#preview-disable

regards


Jeff

On Wednesday, January 4, 2017 at 8:50:15 AM UTC-8, Marco Negrini wrote:

Hi everyone,

i was looking in the ini file, and i was wondering if i can set
axis to do NOT check the gcode before running.

--
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.

Re: [Machinekit] Beagle Bone Version

[schooner30@btinternet]

On 22/12/16 04:16, Merik Karman wrote:

Hi everyone

I have a PocketNC 5 Axis milling machine and it is driven via a BBB 
and a custom Cape.

The system ships with (I think) an older version of debian and machinekit.


At this point you are going outside the scope of the forum, we have no 
knowledge of what other 3rd party

manufacturers do with Machinekit, once they get their hands on it



I have tried to load the latest version


What do you mean by this, load what, from where?


but still find that Axis comes up as version 0.1
This is my only point of reference to the version of machinekit. Is 
this correct?


0.1 is the place marker version of Machinekit, not Axis, this has been 
the same since the rebranding from the Linuxcnc logo.
We don't go for versions, it is a continuous integration and evolution 
project.




I have seen screen shots showing much later versions of Axis.


Not any time recently, they would have been images of Linuxcnc, where 
again the version is not that of Axis but the underlying linuxcnc




Any pointers to the best site for BBB Machinekit images would be 
appreciated.


The problem is that we have no knowledge of what PocketNC have done to 
the (presumably) standard BBB SD card image.


Assuming that the only addition is a configuration for the PocketNC, you 
could backup your SD card and then update from packages via apt.
Or you could try a newer SD image from elinux, 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian and transfer a copy 
of your configs





Or am I on the wrong track and should stay with the older version?


I would say go to the PocketNC forum, but having read this reply, 
perhaps don't bother :)

https://groups.google.com/forum/#!category-topic/pocket-nc/software/ZP6XY5VReZI


Regards

Merik
--
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.

Re: [Machinekit] mk not starting under debian jessie + xenomai on a pentium 4 64 bits

[schooner30@btinternet]

Hi

You may have installed xenomai but looks like you are trying to run a 
non-existent posix build


Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=22f2d706-9cf3-4605-b603-76d17a7ce420 ro quiet


Did you reboot and select the xenomai kernel?

regards

On 28/11/16 18:45, Raul Nieves Pardo wrote:

hi!
maybe someone can help, i'm pretty sure i'm doing something stupid

i just installed jessie+lkde on a pc (pentium 4 64 bits)

followed this
http://www.machinekit.io/docs/getting-started/APT-packages-jessie/

then this
/sudo apt-get install linux-image-xenomai.x86-amd64 /

and this
sudo apt-get install machinekit-xenomai machinekit-dev

(i got some warning about missing free drivers(?¿) )


i ran the stepconf wizard and copy my linuxcnc configuration without 
problems


when i lauch mk using the icon i get in the desktop i get

/mk@mkP4:~$ linuxcnc /home/mk/machinekit/configs/ilaro400/ilaro400.ini/
/MACHINEKIT - 0.1/
/Machine configuration directory is 
'/home/mk/machinekit/configs/ilaro400'/

/Machine configuration file is 'ilaro400.ini'/
/Starting Machinekit.../
/Warning - /usr/libexec/linuxcnc/rtapi_app_posix not setuid/
/'sudo make setuid' missing?/
//usr/bin/realtime: line 192: /usr/libexec/linuxcnc/rtapi_app_posix: 
No such file or directory rtapi_app startup failed - aborting/
/halcmd: cant connect to rtapi_app: -1 (uri= 
uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout/

/
/
/halcmd: the rtapi:0 RT demon is not running - please investigate 
/var/log/linuxcnc.log/

/io started/
/halcmd: cant connect to rtapi_app: -1 (uri= 
uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout/

/
/
/halcmd: the rtapi:0 RT demon is not running - please investigate 
/var/log/linuxcnc.log/

/halcmd loadusr io started/
/halcmd: cant connect to rtapi_app: -1 (uri= 
uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc(): reply timeout/

/
/
/halcmd: the rtapi:0 RT demon is not running - please investigate 
/var/log/linuxcnc.log/

/Shutting down and cleaning up Machinekit.../

i think the 'sudo make setuid' is relating the building mk...
i attach the console error...

thanks a lot!
R
--
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.

Re: [Machinekit] unable to connet to 7i90 from RPI2

[schooner30@btinternet]

On 29/10/16 17:33, Janos Bujtar wrote:



Mixing two projects is never a good idea, except having good
knowledge of both.
And then showing minimalistic logs and no configs is the second
bad idea.

Sorry, maybe I misunderstood something and asked the question not in 
right place?

Or what I did wrong?


I think that the main problem is that no-one on this forum has ever 
claimed that you can use a 7i90 from a rpi2


The way to do this is to get it running with whatever the author of that 
thread at the Linuxcnc forum used.


If you then want to use machinekit, you will need to ensure that all the 
elements of the config are the same, or adjust accordingly.


You can't just use a a Machinekit SD image and ask why it doesn't work.

regards


The config files are exactly like here  
(https://github.com/tinkercnc/spi-fpga-driver/tree/master/RaspberryPi/configs/machinekit/hm2-stepper)


Does this part of log file help more? If not what else should I look for?
Oct 29 16:20:00 machinekit msgd:0: startup pid=2676 flavor=rt-preempt 
rtlevel=1 usrlevel=1 halsize=524288 shm=Posix gcc=4.6.3 version=v~~

Oct 29 16:20:00 machinekit msgd:0: ØMQ=4.0.4 czmq=2.2.0 protobuf=2.4.1
Oct 29 16:20:00 machinekit msgd:0: configured: Apr  9 2015 14:05:43 
sha=not in a git repo
Oct 29 16:20:00 machinekit msgd:0: built:  Apr  9 2015 14:08:03 
sha=not in a git repo
Oct 29 16:20:00 machinekit msgd:0: publishing ZMQ/protobuf log 
messages at ipc:///tmp/0.log.a42c8c6b-4025-4f83-ba28-dad21114744a
Oct 29 16:20:01 machinekit msgd:0: rtapi_app:2681:user accepting 
commands at ipc:///tmp/0.rtapi.a42c8c6b-4025-4f83-ba28-dad21114744a
Oct 29 16:20:01 machinekit msgd:0: hal_lib:2681:rt hm2: loading Mesa 
HostMot2 driver version 0.15

Oct 29 16:20:01 machinekit msgd:0: hal_lib:2681:rt Base:hm2_7i90.0
Oct 29 16:20:01 machinekit msgd:0: hal_lib:2681:rt hm2: llio reports 
invalid number of I/O connectors (0)









--
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.