[Machinekit] Help request for development PC to use Cetus
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 Cetus, MachinekitSDk, QTQuickvcp, Machinekit-Client and free version of QT5 via web install. I would like to get Cetus working and plan to use as a good starting and learning point to be able to develop in QT. Unfortunately I do not fully understand how to get all the pieces that I down loaded to function as a working system on in my Linux Mint PC right now. It appears to be a somewhat complicated process. My Linux based development PC is attached via a dedicated network to an ACRA milling machine which uses a Mesa pre-programmed 7i80 FPGA interface card. Machinekit running on this PC is connecting to the mesa card and able to get status info from the card inputs via HalShow. I will continue to try to get this PC configured on my own, but does anyone have available some rough information or guide on the best way to get the various pieces that I downloaded talking to each other on the PC? I think that some information that I'm trying to use may not be meant to be used for configuring a PC. After I get everything working on the Linux based PC then I plan to work on my Windows7 based development machine which is not ready to use yet. I plan to use for testing Cetus and other GUI's remotely and also for Qt5 future GUI development work. I have on hand a Raspberry PI-3 and may also use it later for future work as time allows. -- 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.
[Machinekit] Machinekit logging on Linux Mint 18.3
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. To get Machinekit logging working in Linux Mint first edit system file as root: /etc/rsyslog.conf You can open terminal as root and use text editer. Comment out: $PrivDropToUser syslog $PrivDropToGroup syslog Like this: #$PrivDropToUser syslog #$PrivDropToGroup syslog Then save the file and send: sudo service rsyslog restart If you are receiving logging error messages while running the 'sudo make setuid' command the next commands may be needed. To generate a missing '/var/log/linuxcnc.log' file send command: sudo touch /var/log/linuxcnc.log Linux Mint uses rsyslogd instead of the older syslogd. To route log data to the newly generated linuxcnc.log file we must first copy the machinekit rtapi/rsyslogd-linuxcnc.conf configuration file to the systems /etc/rsyslogd folder. sudo cp rtapi/rsyslogd-linuxcnc.conf /etc/rsyslog.d/linuxcnc.conf sudo service rsyslog restart On rate limit error message 'No rate limit in rsyslogd is set': Run this copy command. sudo cp rtapi/shmdrv/limits.d-machinekit.conf /etc/security/limits.d/machinekit.conf -- 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.
[Machinekit] Re: Help requested with Mesa custom 7i80HD-25 bit file compatibility
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 and machinetalk, like Alex's Machineface or Cetus?" Yes. I have been working on a gui for a while to replace gmoccapy on linuxcnc and to be able to run it remotely. But it turns out that I would have use what I consider to be obsolete methods to accomplish that. My goal has thus changed and drifted away from linuxcnc and towards Machinekit and run the gui I'm working on remotely like Cetus. It may end up running on a touch screen laptop. I'm familiar with and have used Labview for programming remote control application for a good number of years and thus my gui is coded in Labview. Unfortunately there is not much information on how to code protobuf related items in Labview so I will need to work that out. Labview has a Zeromq library so that is not problem. As an aid in getting to understand protobuf coding a bit better I could use Cetus and perhaps do a little network snooping to look at the bi-directional data exchanges to help understand the communication process. About gmocappy on being a remote gui. I used gmocappy only as a starting point to get Machinekit installed and do some preliminary testing and do not intend to keep using it. I use gmocappy on my linxcnc controlled milling machine and thus anticipated that using it for testing would be simplest. That turned out to be a mistake due to differences in available gmocappy versions and axis/joint difference requirements between linuxcnc and Machinekit. Gmocappy buttons: I also believe that picture buttons on anything that controls machinery is a very bad idea based on my own experience with working on past NASA related projects. Plainly marked buttons of a size suitable for a touch screen are fine. But finger tip size is not the same for everyone so touch screen buttons tend to grow larger and take up a large amount of screen area. To save screen area pull down menus excel but in general they do not use buttons and thus are not really suitable for touch screens. Touch screens however can use pop up button panels instead for selected items to save screen area and allow for added functionality. -- 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.
[Machinekit] Re: Help requested with Mesa custom 7i80HD-25 bit file compatibility
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 development boards along with HAL show, and tested each I/O pin individually. I was able to verify that all 72 i/o pins were being read correctly. So my linuxcnc Mesa flashed configuration is indeed fully compatible with Machinekit. I also wired in several TTL shaft angle encoders into the X and Y flashed encoder inputs and verified that position data was being read correctly.. The old gmoccapy version is causing to many issues for me so I will need to switch to an up to date remote gui for testing and further development work. I will start digging for information on the best way to do that. The remote Gui will be run on a Window 7 box. -- 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.
[Machinekit] Help requested with Mesa custom 7i80HD-25 bit file compatibility
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 hub and to be used for development work on Debian 9.4 Stretch. In searching for info I read this: From: http://www.machinekit.io/docs/drivers/hostmot2/#pin-files = PIN Files "The default pinout is described in a .PIN file (human-readable text). When you install a firmware package the .PIN files are installed in /usr/share/doc/hostmot2-firmware-/" Firmware The selected firmware (.BIT file) and configuration is uploaded from the PC motherboard to the Mesa mothercard on Machinekit startup. If you are using Run In Place, you must still install a hostmot2-firmware- package. There is more information about firmware and configuration in the 'Configurations' section. I don't understand: "If you are using Run In Place, you must still install a hostmot2-firmware- package." Not sure if this would also apply to Ethernet connected boards. >From this it appears that I may need to satisfy the above requirement, but have no information on how to do that. "My board package" is a Mesa 7i80HD which is installed in a milling machine, has been flashed with my custom .pin file, has IP address 10.10.10.2, and works fine with LCNC. Machinekit connects to the board but does not address the boards pins correctly. I did notice that the hm2_eth.c and hm2_eth.h driver in Machinekit are different from the LCNC version so I assume that Machinekit may handle or reading the boards configuration differently, or that the drivers may just be different versions. I have a second development 7i80HD-25 board with IP 10.10.10.3 with three associated pin-out/protection boards. I'm stuck on proceeding to develop on Machinekit until I'm able to fix this problem. I have searched for more info but have not run into anything useful yet I have attached a copy of the .vhd file in case somebody can point me in the right direction. -- 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. PIN_CNC1_V1_72.vhd Description: Binary data
[Machinekit] Re: Problem with new install errors, warnings and notes
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 machine for some preliminary testing. The machine itself uses and linuxcnc and gmocappy right now but both are planned to be switched out for Machinekit and my Labview based custom gui that I have partially completed. My next step will be to get the gui to interface with Machinekit via the network and hopefully be able to get status info to verify that the interface between Machinekit and my gui is working properly. I'm thinking that the simulation that you suggested will work well for that. Before proceeding further I do need to verify that I can control the milling machine properly with Machinekit with the machines own Mesa 7i80hd Ethernet card. -- 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.
[Machinekit] Re: Problem with new install errors, warnings and notes
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 confused on how machinekit handles Mesa bit files. I have read that they need to be placed in a folder somewhere as a txt file which confuses me more since a bit file that is loaded into a Mesa FPGA board is not a text file. Here are the steps I used to install this new installation using Debian 9.4.0 stretch. # Desktop computer with run in place $ installed Debian 9.4.0 amd64 stretch cd1 free only version $ su usermod -a -G sudo "my user name" $ sudo apt-key adv --keyserver hkp://pool.sks-keyservers.net --recv 43DDF224 $ sudo sh -c "echo 'deb http://deb.machinekit.io/debian stretch main' > /etc/apt/sources.list.d/machinekit.list $ sudo apt-get update $ sudo apt-get install linux-image-rt-amd64 $ reboot $ cd /home $ git clone https://github.com/machinekit/machinekit.git machinekit-dev === # in machinekit-dev folder $ debian/configure -r $ sudo mk-build-deps -ir # say yes to install depends $ sudo apt-get install dirmngr $ sudo apt-get install git dpkg-dev $ sudo apt-get install devscripts $ sudo apt-get install python-avahi $ sudo apt-get install python-dbus python-dbus-dev python-dbus-dbg # some in the above line may not be required $ sudo apt-get install python-glade2 python-gtkglext1 python-gtksourceview2 $ sudo apt-get install python-vte $ sudo apt-get install --no-install-recommends devscripts equivs $ sudo apt-get install memlockd # may not be required # the above line may not be required $ cd src $ ./autogen.sh $ ./configure --with-rt-preempt --enable-build-documentation $ make clean (only if needed to completely make fresh version) $ make $ sudo make setuid $ ../scripts/check-system-configuration.sh $ sudo cp rtapi/rsyslogd-linuxcnc.conf /etc/rsyslog.d/linuxcnc.conf $ sudo service rsyslog restart $ sudo cp rtapi/shmdrv/limits.d-machinekit.conf /etc/security/limits.d/machinekit.conf $ sudo touch /var/log/linuxcnc.log $ sudo service rsyslog restart $ cd .. $ . ./scripts/rip-environment $ export DEBUG=5 $ machinekit /home/cnc/machinekit-dev/configs/cnc1/cnc1.ini # gmoccapy gui comes up ok but its version is too old to be usefull -- 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] Problem with new install errors, warnings and notes
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 the installation log which I have attached.. > > The .hal file I have used before for testing fails to complete > > loading at the below error message: > > > > > > > This bit of the print clearly shows the problem is with your config, > which we have no details of > > /home/cnc/machinekit-dev/configs/cnc1/cnc1.ini:81: executing 'import sys > sys.path.insert(0,"python")' > PythonPlugin: Python '2.7.12 (default, Dec 4 2017, 14:50:18) > [GCC 5.4.0 20160609]' > emcTaskInit: using builtin interpreter > /home/cnc/machinekit-dev/configs/cnc1/cnc1.ini:81: executing 'import sys > sys.path.insert(0,"python")' > PythonPlugin: Python '2.7.12 (default, Dec 4 2017, 14:50:18) > [GCC 5.4.0 20160609]' > is_callable(__init__) = FALSE > is_callable(oword.on_abort) = FALSE > is_callable(oword.on_abort) = FALSE > /home/cnc/machinekit-dev/configs/cnc1/cnc1.ini:81: executing 'import sys > sys.path.insert(0,"python")' > PythonPlugin: Python '2.7.12 (default, Dec 4 2017, 14:50:18) > [GCC 5.4.0 20160609]' > Traceback (most recent call last): >File "/home/cnc/machinekit-dev/bin/gmoccapy", line 30, in > import hal_glib # needed to make our own hal pins >File "/home/cnc/machinekit-dev/lib/python/hal_glib.py", line 20, in > > from machinetalk.protobuf.message_pb2 import Container >File > "build/bdist.linux-x86_64/egg/machinetalk/protobuf/message_pb2.py", line > 16, in >File "build/bdist.linux-x86_64/egg/machinetalk/protobuf/nanopb_pb2.py", > line 26, in > TypeError: __init__() got an unexpected keyword argument 'syntax' > Shutting down and cleaning up Machinekit... > > Run an axis_mm sim, and I expect it will run perfectly, the problem is > with your config / gmoccapy / python > > syntax='proto2' has been in there for 2 years > > https://github.com/machinekit/machinekit/blob/master/src/machinetalk/proto/src/machinetalk/protobuf/nanopb.proto#L8 > > > but I don't use python, protobuf or gmoccapy, so can't help there, other > than wonder why your path to the machinetalk/protobuf files is > completely different > They should be in > > /home/cnc/machinekit-dev/lib/python/machinetalk/protobuf > > Are you using files from another build? > > > Warning: Logging appears to be not working > >Found rsyslogd configuration and /var/log/linuxcnc.log >exists, but a test did not appear in the log. >Please investigate. > > Makefile:842: recipe for target 'setuid' failed > > > This occurs as it says. Sometimes the rsyslogd daemon has died, the > linuxcnc.log has the wrong permissions and cannot be written to, or > similar. > You also do need to check that the setuid part worked, but there is no > indication it did not when realtime was started > > > -- 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.
[Machinekit] Re: Problem with new install errors, warnings and notes
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 file I have used before for testing fails to complete loading at > the below error message: > > Traceback (most recent call last): > File "/home/cnc/machinekit-dev/bin/gmoccapy", line 30, in > import hal_glib # needed to make our own hal pins > File "/home/cnc/machinekit-dev/lib/python/hal_glib.py", line 20, in > > from machinetalk.protobuf.message_pb2 import Container > File "build/bdist.linux-x86_64/egg/machinetalk/protobuf/message_pb2.py", > line 16, in > File "build/bdist.linux-x86_64/egg/machinetalk/protobuf/nanopb_pb2.py", > line 26, in > TypeError: __init__() got an unexpected keyword argument 'syntax' > Shutting down and cleaning up Machinekit... > > Last time I installed Machinekit I was able to load my .hal file but got > stuck on communications to the Ethernet Mesa 7180 board which is till and > issue for me but I do now have a additional board to try to load the bit > file in a different way. This new Machinekit install is to to be used to > work on the interface requirements for the Labview coded gui that I have > partially completed for use with Machinekit. I expect that my biggest > problem with be with the Protocol Buffers encoding/decoding since I do not > have a clear understanding about those methods yet. > -- 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.
[Machinekit] MESA 7i80 hm2_eth unable to read static internal configuration
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 board between the machine is a Mesa 7i80hd board with a custom pre-reloaded and stored bit file file. Linuxcnc has no problem reading the internal programming of the Mesa board and runs mill just fine. Machine kit on the other hand appears to be a little confused as to handle the programming of the board. This to me is strange since the driver that was developed for this board is known to very reliable. So I suspect that machine kit may read and write to this card in a slightly different manner. There does appear to be some differences in the hm_eth driver files used by machinekit and linuxcnc which could be causing a incompatibility issue. As I recall coping the hm_eth driver .c and .h files and recompiling causes a make to fail. I'm thinking that this may be a problem with differences in the way machinekit and linuxcnc communicate with the Mesa card. Something appears to get lost between the TCP network functiosn and the cards input and outputs. I'm open to any suggestions. If it turns out that machine kit needs to load the bit file on each power up it will make things more difficult for compatibility between using and developing for awhile since linuxcnc is not designed to do that to the best of my knowledge. Machinekit's ability to tie into raspberry pi and others makes machine kit very attractive to me. Just for additional info I have attached a file that lists the actual 7i80 pin out. Here are my configurations. >From .INI file HOSTMOT2] # BOARD=7i80hd #board_mac="00:60:1b:11:80:23" DRIVER = hm2_eth board_ip="10.10.10.2" BOARD_IP="10.10.10.2" BOARD=7i80 CONFIG="num_encoders=6 num_stepgens=5 num_pwmgens=1 sserial_port_0=20xx" >From .HAL file loadrt [KINS]KINEMATICS loadrt tp loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[TRAJ]AXES tp=tp kins=trivkins loadrt pid count=7 loadrt hostmot2 loadrt [HOSTMOT2](DRIVER) config=[HOSTMOT2](CONFIG) setp hm2_[HOSTMOT2](BOARD).0.watchdog.timeout_ns 3000 Part of the debug printout. Starting Machinekit... rtapi_msgd command: /home/cnc/cnc-mk1.1/libexec/rtapi_msgd --instance=0 --rtmsglevel=5 --usrmsglevel=5 --halsize=524288 rtapi_app command: /home/cnc/cnc-mk1.1/libexec/rtapi_app_posix --instance=0 io started :0: Component 'iocontrol' ready :0: Program 'io' started halcmd loadusr io started :0: Component 'halui' ready :0: Program 'halui' started cnc1.hal:5: Realtime module 'trivkins' loaded cnc1.hal:8: Realtime module 'tp' loaded cnc1.hal:9: Realtime module 'motmod' loaded cnc1.hal:10: Realtime module 'pid' loaded cnc1.hal:11: Realtime module 'hostmot2' loaded cnc1.hal:12: Realtime module 'hm2_eth' loaded cnc1.hal:13: setting parameter 'hm2_7i80.0.watchdog.timeout_ns' to '3000' cnc1.hal:13: Parameter 'hm2_7i80.0.watchdog.timeout_ns' set to 3000 cnc1.hal:50: Function 'hm2_7i80.0.read' added to thread 'servo-thread', rmb=0 wmb=0 cnc1.hal:51: Function 'hm2_7i80.0.write' added to thread 'servo-thread', rmb=0 wmb=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. hm2/hm2_7i80.0: 72 I/O Pins used: hm2/hm2_7i80.0: IO Pin 000 (P1-01): Encoder #0, pin B (Input) hm2/hm2_7i80.0: IO Pin 001 (P1-03): Encoder #0, pin A (Input) hm2/hm2_7i80.0: IO Pin 002 (P1-05): Encoder #0, pin Index (Input) hm2/hm2_7i80.0: IO Pin 003 (P1-07): StepGen #0, pin Step (Output) hm2/hm2_7i80.0: IO Pin 004 (P1-09): StepGen #0, pin Direction (Output) hm2/hm2_7i80.0: IO Pin 005 (P1-11): IOPort * pin Servo Error hm2/hm2_7i80.0: IO Pin 006 (P1-13): Encoder #1, pin B (Input) hm2/hm2_7i80.0: IO Pin 007 (P1-15): Encoder #1, pin A (Input) hm2/hm2_7i80.0: IO Pin 008 (P1-17): Encoder #1, pin Index (Input) hm2/hm2_7i80.0: IO Pin 009 (P1-19): StepGen #1, pin Step (Output) hm2/hm2_7i80.0: IO Pin 010 (P1-21): StepGen #1, pin Direction (Output) hm2/hm2_7i80.0: IO Pin 011 (P1-23): IOPort * pin Manual Mode hm2/hm2_7i80.0: IO Pin 012 (P1-25): Encoder #2, pin B (Input) hm2/hm2_7i80.0: IO Pin 013 (P1-27): Encoder #2, pin A (Input) hm2/hm2_7i80.0: IO Pin 014 (P1-29): Encoder #2, pin Index (Input) hm2/hm2_7i80.0: IO Pin 015 (P1-31): StepGen #2, pin Step (Output) hm2/hm2_7i80.0: IO Pin 016 (P1-33): StepGen #2, pin Direction (Output) hm2/hm2_7i80.0: IO Pin 017 (P1-35): IOPort
[Machinekit] Is there suggested single board computer board for MuliKore use
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 being used during testing by at least one tester but would like to know if that is the recommended SBC board or if the development work that has been completed recommends another board to insure compatibility with machinekit. -- 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.
[Machinekit] Re: Sudo make setuid logging location error
I went ahead and changed the machinekit script file "check-system-configuration.sh" line 24 to machinekit.log instead of linuxcnc.log to work around the logging ok verification issue that shows with at the end of a current make process on my computer. The /machinekit/src/rtapi/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 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 process. It is trying to read file /var/log/linuxcnc.log which I > believe is not the correct file to use. Machinekit souce was cloned on > 07/15/2017 > > > In machinekit file location /machinekit/src/rtapi/ there are two logging > configuration files, rsyslogd-linuxcnc.conf and rsyslogd-machinekit.conf. > > I suspect that machinekit should be using the > /machinekit/src/rtapi/rsyslogd-machinekit.conf file and then look at the > generated /var/log/machinekit.log file instead of the linuxcnc.log that it > reports to have found with zero entries having been made into that file by > the machinekit logging verify test in the script for sudo make setuid. > > > I ended up copying the /machinekit/src/rtapi/rsyslogd-machinekit.conf to > /etc/rsyslog.d/ and then restarted the logging service with sudo service > rsyslog restart, and found that the logging to file > /var/log/machinekit.log file that was generated automatically was being > logged too just fine. > > > Should the sudo make setuid process not be looking for the logging test > and verify in /var/log/machinekit.log instead of /var/log/linuxcnc.log or > the rsyslogd-linuxcnc.log that is not likely even there? > -- 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.
[Machinekit] Sudo make setuid logging location error
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 process. It is trying to read file /var/log/linuxcnc.log which I believe is not the correct file to use. Machinekit souce was cloned on 07/15/2017 In machinekit file location /machinekit/src/rtapi/ there are two logging configuration files, rsyslogd-linuxcnc.conf and rsyslogd-machinekit.conf. I suspect that machinekit should be using the /machinekit/src/rtapi/rsyslogd-machinekit.conf file and then look at the generated /var/log/machinekit.log file instead of the linuxcnc.log that it reports to have found with zero entries having been made into that file by the machinekit logging verify test in the script for sudo make setuid. I ended up copying the /machinekit/src/rtapi/rsyslogd-machinekit.conf to /etc/rsyslog.d/ and then restarted the logging service with sudo service rsyslog restart, and found that the logging to file /var/log/machinekit.log file that was generated automatically was being logged too just fine. Should the sudo make setuid process not be looking for the logging test and verify in /var/log/machinekit.log instead of /var/log/linuxcnc.log or the rsyslogd-linuxcnc.log that is not likely even there? -- 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.
[Machinekit] Beaglebone and Mesa 7i80 network Connection
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 a Beaglebone with only one network port be able to connect with the Mesa 7i80 board and also handle a remote GUI without sharing the Ethernet port? Is there a plugin board available that would add a second network port? The Beaglebone would fit nicely in the machines controller enclosure and would allow me to reconfigure the Linux based desktop computer to a Windows based for remote control and other CAD/CAM functions. -- 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] Mesa 7I80 ethernet board issue
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. The milling machine moves but will need some additional fine tuning to get all functions working. Right now I wish to proceed to try to link up to machinekit via a TCP link with some manual commands.So I will need to do some research on the format required by machinekit so it understands the commands being sent over the network link and be able to decode and display the information received back.. -- 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.
[Machinekit] Re: Mesa 7I80 ethernet board issue
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 have to be reflashed in a special way to make it compatible with machinekit or should the card be readable in its present configuration that works fine with linuxcnc 2.8 development version? -- 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.
