[Machinekit] Re: Problem with new install errors, warnings and notes

2018-05-17 Thread fairbanks-john


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.


Re: [Machinekit] Problem with new install errors, warnings and notes

2018-05-17 Thread fairbanks-john


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

2018-05-17 Thread fairbanks-john
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] Re: Problem with new install errors, warnings and notes

2018-05-17 Thread 'schoone...@btinternet.com' via Machinekit

  
  

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

Re: [Machinekit] Can't install machine kit on Beagle Bone stock image

2018-05-17 Thread Eric
Schooner & Robert:

I'm running this 
image: 
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit

Please bear with me here, but if I understand this right the image I 
downloaded and flashed (and have booted) has the 3.8 kernel. This kernel is 
not compatible with the wifi chip drivers, I need a 4.1 or later kernel? 
But what you're saying is that there's an experimental build that has a 
later (4.1+) kernel but there's a CPU load issue? You say it might not with 
with "rt requirements" I' assume you mean "real time requirements". So my 
guess is that I run the risk of locking up my machine if I try that image?

That command that you list: CONFIG_PREEMPT_RT_FULL -> CONFIG_PREEMPT_RTB 

What does it mean? I'm assuming it commands the OS to go from full real 
time to something that's buffered, or "preemted?"

Thanks for all of the help, and I apologize for being a bit of a newbie at 
this..


On Wednesday, May 16, 2018 at 12:49:50 PM UTC-4, Robert Nelson wrote:
>
> On Wed, May 16, 2018 at 10:39 AM, Eric > 
> wrote: 
> > I'm guessing that updating the kernel on the Machinekit image isn't as 
> > trivial as installing an app? (can you tell I'm new to Linux! :) 
> > 
> > Where would I find Robert Nelson? 
>
> The image with 3.8.13-xenomai, don't bother trying to update it to 
> 4.14.x-rt so you can get wifi working.. 
>
> Instead use a later stretch build: 
>
> https://rcn-ee.net/rootfs/bb.org/testing/2018-04-22/stretch-machinekit/ 
>
> Currently there's a high cpu load issue on v4.14.x, we think we 
> figured it out, but it involves switching from: 
>
> CONFIG_PREEMPT_RT_FULL -> CONFIG_PREEMPT_RTB 
>
> So it might not work with machinekit's rt requirements... 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

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

2018-05-17 Thread fairbanks-john
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] Help requested with Mesa custom 7i80HD-25 bit file compatibility

2018-05-17 Thread fairbanks-john
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