I’m a little confused on how to interface the Cetus gui with Machinekit on
my new Linux based development PC on which I have already installed
Machinekit as run in place. I’m running on Linux Mint 18.3 with kernel
4.9.98-RT. The Machinekit appears to be running fine and I have down loaded
C
I have been setting up a new development system using Mint 18.3 and also a
Windows box using Win7 and have noticed that there is a problem getting
Machinekit logging working properly on Mint every time 'sudo make setuid'
is run. So to help others here is my consolidated fix to overcome this.
T
Schooner in reference to your comment:
"I am confused by your use of 'remote'. Gmoccapy is not a remote GUI, but
you were using it.
Are you just referring to accessing the controller machine remotely from
another computer?
Or are you intending to use an actual remote interface via a loader a
To day I decided that the cause of my problem is most likely the version
of gmoccapy available with machinekit. I had modified my configuration
files to make gmoccapy happy but it appears that there are still
incompatibilities and do not wish to spend more time on.
I used my Mesa 7I80 flash de
I have Machinekit running now as a run in place with no error but having
issues correctly addressing pins in my Mesa 7i80HD-25 board.
To help resolve this problem I have attached my custom PIN_CNC1_V1_72.vhd
file which is human readable. My install of Machinekit is a cloned install
from git hu
Yes, It looks like I'm getting closer to having a working configuration
that is getting close to being suitable for further testing and development
work.
I did purchase a second Mesa 7i80 card and flashed it with my custom bit
file so that I would not have to use the actual card and milling mac
Schooner I think that I pushed a wrong buttons while posting and messed
things up a bit. I got a new computer and build a new configuration since I
think the old machine may have gotten corrupted while attempting to solve
issues. I will rebuild it later. Machine kit loadsrand runs now but I'm
c
On Wednesday, May 16, 2018 at 7:06:51 AM UTC-8, Schooner wrote:
>
>
> On 15/05/18 08:29, fairbanks-john wrote:
> > I just made a fresh install from the git hub clone today and wondering
> > if I did something wrong since there are a lot of warnings and notes
> > in
On Monday, May 14, 2018 at 11:29:45 PM UTC-8, fairbanks-john wrote:
>
> I just made a fresh install from the git hub clone today and wondering if
> I did something wrong since there are a lot of warnings and notes in the
> installation log which I have attached..
> The .hal f
I'm finally continuing my work on building a new gui and switching this in
progress work from linuxcnc to machinekit. I'm using my ACRA milling
machine as a test bed which I do need to be able to use normally while this
work progresses. It runs on linuxcnc 2.8pre with gmoccapy.
The interface b
I was going to order a BeagleBone Black (BBB) computer board today but read
about MutliKore and put the BeagleBone Black order on hold since I would
really like a board that has multiple CPU cores to be able to implement
MultiKore features in machinekit. I read that the DE0-NANO-SoC board was
b
i/rsyslogd-machinekit.conf file does need to be
copied to /etc/rsyslog.d/ if it is not there and then the logging service
needs to be restarted with sudo service rsyslog restart.
On Saturday, July 15, 2017 at 9:52:48 AM UTC-8, fairbanks-john wrote:
>
> I have been setting up linuxcnc and mac
I have been setting up linuxcnc and machinekit as a rip install on
linuxmint 18.1. When running sudo make setuid on the final part of the
machinekit install I there is an error due to no log test entry being
detected. This appears to be an error in the script file for the sudo make
setuid
I have been considering replacing my desktop PC with a Beaglebone board but
not sure how this will work for me. My Milling machine has a Mesa 7i80
board that handles all interfacing to the machines hardware. Communication
with the Mesa 7I80 board is on a dedicated port and not shared. How would
I was able to get my configuration working by adding loadrt tp (not sure
what that does), and changing some joints to axis names, and also modifying
some gmoccapy pin names from the newer 5 axis version that I was using with
linuxcnc to the 4 axis version of gmoccapy that comes with machinekit.
I have been looking into this a little further and find that there is a big
difference in the hm2_eth.c driver files used by machinekit and those used
by linuxcnc. This could be the cause as to why the present configuration in
the 7i80 card could not be read by machinekit. Does the 7i80 card
16 matches
Mail list logo
