[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.
Re: [Machinekit] Re: Problem with new install errors, warnings and notes
On 17/05/18 09:45, fairbanks-john wrote: 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. Without seeing what you read, hard to comment. All the docs come from Linuxcnc and have not been changed. Mesa cards are re-flashed with mesaflash if needs be, to change the config. hm2_pci just needs to be passed the number of stepgens etc in the config string. You might be getting mixed up with the DE0-NANO-Soc FPGA boards, which take a config string which specifies a .dtbo file on a given path. 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 Looks like you are mostly there. Don't know where the path for the protobuf files came from in the last print, maybe you had added it to the PATH at some point? Gmoccapy has not been updated for a while and frankly very few people use it. It starts hitting problems when you get to Buster and when packages for it get backported to Stretch. I had to disable the attempts by it to play audio files in Buster, because the library it relies upon has been deprecated. Anything based upon python2 is probably on its last legs, despite the python.orgs spectacular own goal in coming up with a non backwardly compatible python3 and expecting everyone to just adopt it. One of the major widget libs used in pyvcp is due for deprecation shortly too, which is going to force a major re-think on GUIs both here and in Linuxcnc. -- 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 a
[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.
[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.
