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 DIS
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
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
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 pac
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
O
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?
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 Nie
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
knowle
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 Machin
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,
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 bein
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
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
diff
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
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
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 comp
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
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 enou
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
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/i
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 b
21 matches
Mail list logo
