Re: [Machinekit] Re: RPI gipo help

['schoone...@btinternet.com' via Machinekit]

Without precise details of what you are doing, it is impossible to judge.

It is well known that big gcode files will cause Axis to eat all memory 
on small boards when doing a preview, but that is NOT a leak.


Whether that happens more quickly on Stretch, which may well be a 
'heavier' system, I don't know.


You can mitigate it to an extent by disabling previews, has been 
discussed many times on this list.
The only full solution is to use a more capable computer / board or a 
different GUI.


On 12/08/18 14:34, Timothy March wrote:

On RPI using RT kernel with Stretch and it dosen’t matter which RT kernel you 
use. I use Htop to monitor system memory climbs until it is out. This happens 
on RPI and Tinkerboard but not when using Jessie it is a very slow leak

Tim



--
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: RPI gipo help

['schoone...@btinternet.com' via Machinekit]

Can you please quantify the assertion that Stretch has a memory leak 
with Axis.


I have been using Stretch since it was alpha status.  Usually any memory 
leak is with a program and will manifest irrespective of the distro.



On 8/11/2018 8:43 PM, Timothy March wrote:

I have a question for you are you using Jessie or Stretch? Stretch has a memory 
leak with Axis GUI it will eventually use up all memory. I have post in this 
thread on how to setup Jessie light check it out



--
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] machinekit-dev broken?

['schoone...@btinternet.com' via Machinekit]

Just checked, the comp binary and includes etc are in the 
machinekit- not the main one.

It was a while back, forgot which.

The Makefile.inc etc are per flavour, to stop the problems we had with 
machinekit-dev always having a posix flavour

because of the build setup for that package.


On 11/08/18 12:22, Charles Steinkuehler wrote:

I've got the latest machinekit package installed, but I don't see a
comp command.  There's an instcomp binary, but it doesn't like the two
*.comp files I'm trying to compile, reporting:

machinekit@beaglebone:~/embedded/beaglebone$
EXTRA_LDFLAGS="-lprussdrv" instcomp --compile raster.comp
Error: Unrecognized file type for mode compile: 'raster.comp'
machinekit@beaglebone:~/embedded/beaglebone$ instcomp --compile
--userspace BBB_listener.comp
Error: Unrecognized file type for mode compile: 'BBB_listener.comp'

On 8/11/2018 1:10 AM, 'schoone...@btinternet.com' via Machinekit wrote:

HI Charles


Yes Comp, plus headers, Makefile.inc and everything else in the -dev
package was moved into the main machinekit package some time ago.

There are only four machinekit-dev packages left in the repo and they
match the also deprecated wheezy and raspian packages in the repo,

which are retained for completeness of support rather than usefullness.


Regards


On 8/10/2018 10:36 PM, Charles Steinkuehler wrote:

I'm trying to migrate to a fresh install on a BBB and am having
problems building some custom hal components.  The first problem is
the comp command is missing, so I figure I'll just install
machinekit-dev package.  But apt-get complains about broken packages
and how I need a different version of the machinekit package than I
have installed.

I checked on machienkit.io and machinekit-dev version is:

machinekit-dev_0.1.1498834902

...while my installed machinekit package (and the most recent
available on machinekit.io) is:

machinekit/machinekit_0.1.1532446277

So...are the machinekit-dev packages broken, or did the comp utility
move somewhere else and machinekit-dev is now deprecated?





--
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] machinekit-dev broken?

['schoone...@btinternet.com' via Machinekit]

HI Charles


Yes Comp, plus headers, Makefile.inc and everything else in the -dev 
package was moved into the main machinekit package some time ago.


There are only four machinekit-dev packages left in the repo and they 
match the also deprecated wheezy and raspian packages in the repo,


which are retained for completeness of support rather than usefullness.


Regards


On 8/10/2018 10:36 PM, Charles Steinkuehler wrote:

I'm trying to migrate to a fresh install on a BBB and am having
problems building some custom hal components.  The first problem is
the comp command is missing, so I figure I'll just install
machinekit-dev package.  But apt-get complains about broken packages
and how I need a different version of the machinekit package than I
have installed.

I checked on machienkit.io and machinekit-dev version is:

machinekit-dev_0.1.1498834902

...while my installed machinekit package (and the most recent
available on machinekit.io) is:

machinekit/machinekit_0.1.1532446277

So...are the machinekit-dev packages broken, or did the comp utility
move somewhere else and machinekit-dev is now deprecated?



--
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] launching machinekit after build

['schoone...@btinternet.com' via Machinekit]

  
  
If you are building from sources please read the documentation

http://www.machinekit.io/docs/developing/machinekit-developing/

Sounds like you probably have not set the pathspec, which is covered
in this document.

On 08/08/18 11:43, mngr wrote:


  
Hi,


I have build machinekit from source, now I am trying to
  launch it.


marco@tmarco:~/machinekit$ ./bin/machinekit 
  ./bin/machinekit: line 1: linuxcnc: command not found

I tried to make a simbolic link to tcl/linuxcnc.so in
  /usr/lib/ but nothing changed
I am sure I am simply noob, and don't know the standard
  procedure... can you please help me?


now I don't have a kernel-rt, but I will only do test, does
  this change anything?



mngr

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


  




-- 
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] mklauncher "Can not find -sec DISPLAY -var INTRO_GRAPHIC"

['schoone...@btinternet.com' via Machinekit]

On 08/08/18 03:43, Cameron McQuinn wrote:

..was able to successfully start the config several months ago, 
but I had to set the project aside for a while. When I returned, I 
upgraded the kernel from 4.9 to 4.14, and upgraded machinekit and 
QtQuickVcp to the latest versions, but didnt' change anything else.


The error in your title is consequential not causal.

The error is here.
I will leave those who know more about it to pinpoint what caused it.  I 
would tend to suspect the kernel change and wonder if the firmware is 
present or correct.

Aug  8 02:01:24 socfpga rtapi:0: 4:rtapi_app:1890:user hm2_soc_ol: 
soc_program_fpga
Aug  8 02:01:24 socfpga rtapi:0: 4:rtapi_app:1890:user hm2_soc_ol: FPGA overlay 
status: applied
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hm2_soc_ol: failed to 
map hm2-socfpga0 to /dev/uioX
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hm2_soc_ol: 
soc_mmap_fail hm2-socfpga0
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hm2/foo: failed to 
program fpga, aborting hm2_register
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user foo: hm2_soc_ol_board 
fails HM2 registration
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hm2_soc_ol: error 
registering UIO driver: -22
Aug  8 02:01:26 socfpga rtapi:0: hal_call_usrfunct(newinst,-- 
config="firmware=zynq/dtbo/replicookie_7z020_ol.dtbo num_pwmgens=5 
num_stepgens=5" debug=1 already_programmed=1) failed: -1 - Operation not permitted
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hal_call_usrfunct(newinst,-- 
config="firmware=zynq/dtbo/replicookie_7z020_ol.dtbo num_pwmgens=5 
num_stepgens=5" debug=1 already_programmed=1) failed: -1 - Operation not permitted
Aug  8 02:01:26 socfpga msgd:0: hal_lib:1904:user halg_exit:293 HAL: removing 
component 99 'halcmd1904'


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

['schoone...@btinternet.com' via Machinekit]

Dear All,

Some while back I undertook work to split out machinekit into its HAL 
stack and its CNC stack.


This work has reached maturity, to an extent that if the machinekit-hal 
package is installed and then the machinekit-cnc package is installed,

a fully functioning machinekit is available, in tests thus far anyway :)

In preparation for a two package distribution, the existing open Issues 
in machinekit have been copied to either machinekit-hal, or
machinekit-cnc (in a few cases both, with a master issue in 
machinekit-cnc, where they apply to both).


There were 6 exceptions, which were too large to copy over without 
risking data loss and remain in machinekit.
The remaining Open Issues are now Closed, with a reference to the new 
location to be used for future comment.


So, if you have opened, contributed to or just read an Issue in 
machinekit, it can now be found in either

machinekit-hal: https://github.com/machinekit/machinekit-hal/issues
or
machinekit-cnc: https://github.com/machinekit/machinekit-cnc/issues

If you wish to open an issue, please do so in the appropriate repos 
Issues section


If unsure which repo it should come under, generally a look through the 
source files should tell you, there are no duplicates between the repos 
regards actual code.


If still unsure just ask.

If you wish to test the machinekit-hal and / or machinekit-cnc packages, 
please do so, they are available in the main machinekit repo.

Any feedback gratefully received.


regards

--
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: DE10-DE0-Nano - Invitation to collaborate

['schoone...@btinternet.com' via Machinekit]

  
  

On 27/05/18 11:26, Michael Brown wrote:


  

  I dont know if you are aware that capitalization matters
the correct filenames are:
  
  
  /lib/firmware/socfpga/DE10_Nano_FB_Cramps.3x24_cap.rbf
  
  /lib/firmware/socfpga/DE10_Nano_SoC_FB_DB25.7I76_7I76_7I76_7I76.rbf
  
   
  But these will first be in the socfpga-rbf.deb package a
few hours after Charles (or someone else) gets around to
merging.
  :-) 
  

  

You requested review by @cdsteinkuehler, but I have no idea as to
his availability at present.

I am happy to merge if you require the files available and we can
revert if there transpires to be a problem.




  




-- 
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] Any interest in Thermocouple support?

['schoone...@btinternet.com' via Machinekit]

  
  
Hi

Yes, we are trying to get the HAL side of Machinekit as generic as
possible, there is a lot more could be done aside from CNC machine
control.

If you fork machinekit, clone to your computer and then create a
suitably named branch and put your driver in
https://github.com/machinekit/machinekit/tree/master/lib/python/drivers,
that should be about right.

Would like to see a document or example config which shows it's use
too.
If a short doc, it can go in the same directory, if a full config,
needs a suitable entry in
https://github.com/machinekit/machinekit/tree/master/configs
exact placement depending upon whether it requires specific machine
/ hardware etc.
Looks like there is unlikely to be a sim, as it should require
hardware present?

The python string on line one, should specify python2.
This is so that distros that ship with python3 as default can build
without problems.

As for licence, GPL2 is fine
A general boiler plate would be


  

  # This
  is a HAL component
  to 




  


  

  # Copyright date
name 



  


  

  #



  


  

  # This program is
  free software; you can redistribute it and/or modify



  


  

  # it under the
  terms of the GNU General Public License as published by



  


  

  # the Free Software
  Foundation; either version 2 of the License, or



  


  

  # (at your option)
  any later version.



  


  

  #



  


  

  # This program is
  distributed in the hope that it will be useful,



  


  

  # but WITHOUT ANY
  WARRANTY; without even the implied warranty of



  


  

  # MERCHANTABILITY
  or FITNESS FOR A PARTICULAR PURPOSE. See the



  


  

  # GNU General
  Public License for more details.



  


  

  #



  


  

  # You should have
  received a copy of the GNU General Public License



  


  

  # along with this
  program; if not, write to the Free Software



  


  

  # Foundation, Inc.,
  59 Temple Place, Suite 330, Boston, MA 02111-1307 USA



  



Then push your new branch back to your fork, and create a pull
request from your fork of machinekit in github, to machinekit /
machinekit
and we will check it, test build and authorise.

If that is beyond your current experience curve, then reply direct
when you have your fork with the relevant files in and I will talk
you through it

regards


On 24/05/18 01:50, Karl Nilsson wrote:


  Hello All,
  A while back, I created a HAL component for interfacing
thermocouple amplifiers over the SPI bus (specifically the
MAX31855 and MAX6675). I was curious whether there was any
interest in including it in machinekit proper, and if so, what
do I need to do in order to get it included. Specifically, is
there any preferred copyright license for user-contributed
components?

Here's the code, feedback is appreciated!

https://github.com/karl-nilsson/MK_config/blob/master/spi_tc.py

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


  




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

Re: [Machinekit] Re: Help requested with Mesa custom 7i80HD-25 bit file compatibility

['schoone...@btinternet.com' via Machinekit]

  
  

On 18/05/18 22:14, fairbanks-john
  wrote:


  
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.
  


The last update was here
https://github.com/machinekit/machinekit/commit/df4b3b68aa1c9a64e62096350afdf9eb6d09e05c#diff-489f43a022a37a46dc11a435ee80955b
where the author updated to the same state as the then current
Linuxcnc version.

To get this 'up to date' would require someone who was interested in
using it and spending the time removing joints-axes stuff before
merging into machinekit.

I personally don't use it, as it adds nothing in terms of
functionality and visually reminds me of awful early KDE programs,
with their big clunky picture icon push buttons, 
where a simple word to denote its use would suffice.  But that is
just my taste.


  


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


Good, that all seems to be OK.  There should have been no reason why
a valid bitfile would have rendered the board unusable with
machinekit.

  


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.

 


  


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?


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


  




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

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

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

['schoone...@btinternet.com' via Machinekit]

  
  

On 16/05/18 16:39, 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! :)


I don't think you have ever said what image you have, so no idea
what kernel is in it

If it is the 3.8 Xenomai one, then no you can't update it.
Later kernels use Xenomai 3 and Machinekit does not support it

You will need to use a rt-preempt > 4.1.x based image to get
module support for that Texas Instruments chip.
The 4.4.113-ti-r149 kernel seems to be the favorite, but there are
other later kernels too.

There are several images marked 'all Beagle Bone variants' and 'BBB
and BBW', but you need advice as to which one to use.
Make sure you search the forum posts, several people have gone down
this route before.

Failing that, RCN is the expert, I don't have any BBx boards or
capes and s**t  :-P 


  


Where would I find Robert Nelson?

  


http://www.machinekit.io/docs/getting-started/machinekit-images/


  

  On Tuesday, May 15, 2018 at 10:43:13 AM UTC-4, Schooner wrote:
  
 
  On 14/05/18 19:10, Eric wrote:
  
  
 BeagleBone wireless, including the wifi
  chip: http://octavosystems.com/2016/09/27/the-beaglebone-black-wireless-and-beagleboard-compatibility/
  
  
  Getting wifi up and running on an image I didn't
create (and admittedly don't fully understand yet)
seemed like a pretty hard task. 
  

  
  
  Looks like you need the firmware-ti-connectivity
  package, which is backported all the way back to Jessie
  now
  https://packages.debian.org/jessie-backports/firmware-ti-connectivity
  
  Needs a 4.1 > kernel by the looks of it though, to get
  the kernel module, so if the image you tried uses the 3.8
  xenomai kernel or similar, that is part of the problem
  
  All the information is out there, but I would suggest you
  contact Robert Nelson who make the images, he will know
  which one you need.
  
  
  

  

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


  




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

['schoone...@btinternet.com' via Machinekit]

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.

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

['schoone...@btinternet.com' via Machinekit]

  
  

On 14/05/18 19:10, Eric wrote:


   BeagleBone wireless, including the wifi
chip: http://octavosystems.com/2016/09/27/the-beaglebone-black-wireless-and-beagleboard-compatibility/


Getting wifi up and running on an image I didn't create
  (and admittedly don't fully understand yet) seemed like a
  pretty hard task. 

  


Looks like you need the firmware-ti-connectivity package,
which is backported all the way back to Jessie now
https://packages.debian.org/jessie-backports/firmware-ti-connectivity

Needs a 4.1 > kernel by the looks of it though, to get the kernel
module, so if the image you tried uses the 3.8 xenomai kernel or
similar, that is part of the problem

All the information is out there, but I would suggest you contact
Robert Nelson who make the images, he will know which one you need.



  




-- 
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] Can't install machine kit on Beagle Bone stock image

['schoone...@btinternet.com' via Machinekit]

  
  

On 14/05/18 12:39, Eric wrote:


  Ahh, ok so that got me farther, but now I'm
getting a "no keyserver available" error... 
  


Unless you detail what you did and exactly what the error was,
no-one will be able to help

If you search for gpg 'no keyserver available' errors you will see
there can be a variety of reasons, from 
the dirmngr program having problems with the DNS server you use,  to
trying to do this behind a proxy.

I think you are going about this all wrong.

Instead of getting your wireless NIC recognised and module and
firmware installed for it in the Machinekit image,
(which incidently we don't produce and queries about it would best
addressed to RCN's site where you probably downloaded it from)
you are now trying to install Machinekit into an image which does
not have a RT kernel, so won't run Machinekit as is.

Wifi modules are not built in to kernels normally, they are loaded
as required.
Some of it is non-free and not in distributions for legal reasons,
but it is available all the same.

The first action, identify your wifi chipset
Internet search will 
find
https://www.cyberciti.biz/faq/linux-find-wireless-driver-chipset/ 
for example


  
On Monday, May 14, 2018 at 1:33:23 AM UTC-4, Bas de Bruijn
wrote:

  
  
  > On 14 May 2018, at 01:29, Eric 
  wrote:
  
  > 
  > Ok, so if you've seen my other posts you're probably
  figuring out that I'm new to pretty new to Linux. I've fooled
  around with Pis so I have some base knowledge, but that's
  about it.
  
  > 
  > I'm trying to use a stock BeagleBone wireless image that
  I'm running. The image I have on it is this: https://beagleboard.org/latest-images
  (Stretch LXQT)
  
  > 
  > I've been trying to use these commands to install
  MachineKit:
  
  > 
  > http://www.machinekit.io/docs/getting-started/APT-packages-stretch/
  
  > 
  > I keep getting "failed to start the dirmngr
  '/tmp/apt-key-gpdhome.ck58yIIcSL/S.dirmngr' failed: No
  such file or directory"
  
  > 
  > What's going on here?
  
  
  Use:
  
  Sudo apt update
  
  Sudo apt install dirmngr
  

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


  




-- 
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] Docker upgrade failing

['schoone...@btinternet.com' via Machinekit]

  
  
> Apr 27 11:13:30 D525MW dockerd[4167]: Error starting daemon:
Error initializing network controller: Error creating default…e
network
The print is truncated, there should be a more detailed error
explanation following a colon after the second ' Error'

eg.
Error starting daemon: Error
initializing network controller: could not delete the default
bridge network: network bridge has active endpoints

Have a look here, there are several people with similar issues and
some resolutions
https://github.com/moby/moby/issues/18283

Otherwise try searching with the full error string


On 27/04/18 22:13, mugginsac wrote:


  Schooner,

I uninstalled 18 and tried installing 17.0.3 and it failed too.
Must be something wierd with my setup.

Here is the screen from that effort. This was booted in to a
non-realtime kernel (4.9.0.6 AMD64).

acondit@D525MW:~$ sudo apt-get install
docker-ce=17.03.2~ce-0~debian-stretch
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no
longer required:
  pigz
Use 'sudo apt autoremove' to remove it.
The following NEW packages will be installed:
  docker-ce
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.3 MB of archives.
After this operation, 105 MB of additional disk space will be
used.
Get:1 https://download.docker.com/linux/debian stretch/stable
amd64 docker-ce amd64 17.03.2~ce-0~debian-stretch [21.3 MB]
Fetched 21.3 MB in 5s (4,250 kB/s)    
Selecting previously unselected package docker-ce.
(Reading database ... 325458 files and directories currently
installed.)
Preparing to unpack
.../docker-ce_17.03.2~ce-0~debian-stretch_amd64.deb ...
Unpacking docker-ce (17.03.2~ce-0~debian-stretch) ...
Setting up docker-ce (17.03.2~ce-0~debian-stretch) ...
Created symlink
/etc/systemd/system/multi-user.target.wants/docker.service →
/lib/systemd/system/docker.service.
Created symlink
/etc/systemd/system/sockets.target.wants/docker.socket →
/lib/systemd/system/docker.socket.
insserv: warning: script 'realtime' missing LSB tags and
overrides
Job for docker.service failed because the control process exited
with error code.
See "systemctl status docker.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
   Loaded: loaded (/lib/systemd/system/docker.service; enabled;
vendor preset: enabled)
  Drop-In: /etc/systemd/system/docker.service.d
   └─override.conf
   Active: failed (Result: exit-code) since Fri 2018-04-27
11:13:30 PDT; 37ms ago
 Docs: https://docs.docker.com
  Process: 4167 ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2375
(code=exited, status=1/FAILURE)
 Main PID: 4167 (code=exited, status=1/FAILURE)
  CPU: 515ms

Apr 27 11:13:30 D525MW dockerd[4167]:
time="2018-04-27T11:13:30.838786754-07:00" level=debug
msg="ReleaseAddress(LocalDefa….17.0.1)"
Apr 27 11:13:30 D525MW dockerd[4167]:
time="2018-04-27T11:13:30.838859527-07:00" level=debug
msg="ReleasePool(LocalDefault….0.0/16)"
Apr 27 11:13:30 D525MW dockerd[4167]:
time="2018-04-27T11:13:30.838944383-07:00" level=debug
msg="start clean shutdown of …meout..."
Apr 27 11:13:30 D525MW dockerd[4167]:
time="2018-04-27T11:13:30.878010057-07:00" level=debug
msg="Cleaning up old mountid : start."
Apr 27 11:13:30 D525MW dockerd[4167]:
time="2018-04-27T11:13:30.879990648-07:00" level=debug
msg="Cleaning up old mountid : done."
Apr 27 11:13:30 D525MW dockerd[4167]: Error starting daemon:
Error initializing network controller: Error creating default…e
network
Apr 27 11:13:30 D525MW systemd[1]: docker.service: Main process
exited, code=exited, status=1/FAILURE
Apr 27 11:13:30 D525MW systemd[1]: Failed to start Docker
Application Container Engine.
Apr 27 11:13:30 D525MW systemd[1]: docker.service: Unit entered
failed state.
Apr 27 11:13:30 D525MW systemd[1]: docker.service: Failed with
result 'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package docker-ce (--configure):
 subprocess installed post-installation script returned error
exit status 1
Processing triggers for 

Re: [Machinekit] Docker upgrade failing

['schoone...@btinternet.com' via Machinekit]

I am running v18.03 on an amd64 Buster desktop and v17.03 on my amd64 
Stretch server without problems.


As Charles says, it will not run on other than a POSIX kernel, had 
problems in the past when I booted into the RT

kernel without thinking about it.

There may be something else in the wind though, this thread is recent 
and unresolved

https://github.com/moby/moby/issues/36804

Worth checking the changelogs to see if they have updated without 
changing major version number recently?


The obvious first advice is remove it and install your previous version 
again via dpkg

Don't think there is anything magic about v18

On 26/04/18 23:02, Charles Steinkuehler wrote:

There's not really enough to tell exactly what went wrong, but IIRC I
ran into similar problems trying to get Docker running on one of my
machines I was also using for CNC tests.

It turns out my problem was with the kernel version or configuration.
The real-time kernel I was using wouldn't work with Docker and the
daemon would just refuse to start.  Switching back to a stock Debian
kernel got everything working as expected.

On 4/26/2018 4:50 PM, mugginsac wrote:

I have spent a couple days trying to get docker to run. I keep getting a
failure on the installation. Can anybody help?

acondit@D525MW:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up docker-ce (18.03.0~ce-0~debian) ...
insserv: warning: script 'realtime' missing LSB tags and overrides
Job for docker.service failed because the control process exited with error
code.
See "systemctl status docker.service" and "journalctl -xe" for details.
invoke-rc.d: initscript docker, action "start" failed.
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor
preset: enabled)
   Drop-In: /etc/systemd/system/docker.service.d
└─override.conf
Active: activating (auto-restart) (Result: exit-code) since Thu
2018-04-26 14:40:38 PDT; 66ms ago
  Docs: https://docs.docker.com
   Process: 9301 ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2375
(code=exited, status=1/FAILURE)
  Main PID: 9301 (code=exited, status=1/FAILURE)
   CPU: 340ms

Apr 26 14:40:38 D525MW systemd[1]: Failed to start Docker Application
Container Engine.
Apr 26 14:40:38 D525MW systemd[1]: docker.service: Unit entered failed
state.
Apr 26 14:40:38 D525MW systemd[1]: docker.service: Failed with result
'exit-code'.
dpkg: error processing package docker-ce (--configure):
  subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
  docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
acondit@D525MW:~$ sudo systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor
preset: enabled)
   Drop-In: /etc/systemd/system/docker.service.d
└─override.conf
Active: failed (Result: exit-code) since Thu 2018-04-26 14:40:40 PDT;
42s ago
  Docs: https://docs.docker.com
   Process: 9394 ExecStart=/usr/bin/dockerd -H tcp://0.0.0.0:2375
(code=exited, status=1/FAILURE)
  Main PID: 9394 (code=exited, status=1/FAILURE)
   CPU: 338ms






--
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] switching between kinematics modes in G code

['schoone...@btinternet.com' via Machinekit]

  
  
Have a look at rs274ngc_interp.hh:L233

The functions starting comp_get_current(...) appear
to get and set the values in the initial settings struct.
Initialised in rs274ngc_pre:L113 and struct detail in
interp_setup.cc / interp_internal.hh

I haven't looked much at it, but assuming this struct is updated
throughout, to hold the current values for all the settings, it may
be of use.

If you have a sim which can switch kinematic modes using your
components, I may be able to assist more.

I don't have any machines that use anything other than trivkins.

On 24/04/18 14:12,
  j...@allwinedesigns.com wrote:


  I believe I found the culprit. While everything
seems to be in order in the motion controller, I believe the
GCode interpreter still believes it's at the previous position
after a kinematics mode change. Manually executing a g0 to the
currently displayed coordinates after a change and then
executing another command seems to work perfectly. Now to find
where to change that...
  -- 
  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.


  




-- 
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 hm2_eth unable to read static internal configuration

['schoone...@btinternet.com' via Machinekit]

  
  

On 21/04/18 09:29, fairbanks-john
  wrote:


  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. 
  


There are major differences between the hm2_eth files in Linuxcnc
and those in Machinekit

At the most trivial basic level, it uses rtapi_xxx types which are
just redefinitions of standard types, but sufficient to prevent
compilation.
Getting past those, there are major incompatibilities.

Just a glance at hm2_eth.h, shows that there is a big hm2_eth_t
struct that did not exist before.
The hm2_eth.c file is 70% larger, partly as a consequence.

Errors indicate that hm2_lowlevel_io_t has changed markedly
too and within this and elsewhere, there are other functions used
which only exist in Linuxcnc,
such as need_soft_reboot(), rtapi_spawn_as_root().

If your 7i80 with its custom config works with Linuxcnc, I would use
use that.

Other people may be using 7i80s and be able to see why the existing
driver does not like your bitfile, I don't own one, so cannot test
anything.


  




-- 
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] Machinekit as a general purpose motor controller?

['schoone...@btinternet.com' via Machinekit]

Please see also https://github.com/machinekit/machinekit-hal

This is a standalone Machinekit HAL stack without interpreter, motion, 
NML etc etc.


At present the python vcp stuff is in the corresponding CNC stack at
https://github.com/machinekit/machinekit-cnc

If you need virtual panels etc for your project they could be moved 
across to machinekit-hal.
Their current location is simply because the primary mainstream use is 
within the Axis GUI,

but they can be wherever is most useful.

On 20/04/18 14:29, Charles Steinkuehler wrote:

On 4/19/2018 10:02 PM, dschr...@eng.ucsd.edu wrote:

Hi! I was curious about people using machinekit as a general purpose motor
controller? I have been developing my own 8 axis motor driver on the
DEO-NANO-SOC, but this seems to have many advanced features.

You could easily use the Machinekit HAL framework and the hostmot2 VHDL
to control whatever mix of hardware you need.  Assuming you don't want
to use the existing CNC stack, you should be able to fairly easily
connect your high-level planning software up to HAL using the C or
Python bindings.  Note that the ring-buffers available in Machinekit
make interfacing to non-real-time user-mode code a *LOT* easier than it
used to be in LinuxCNC.

Depending on exactly what you need to do, you may not even need anything
outside of HAL and a few limit2/limit3 blocks.  I'm controlling a couple
custom (not CNC, not 3D printer) machines using just Machinekit HAL and
a couple small HAL components I wrote for specific tasks.



--
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] switching between kinematics modes in G code

['schoone...@btinternet.com' via Machinekit]

  
  

On 12/04/18 16:00,
  j...@allwinedesigns.com wrote:


  I definitely have to stick with Machinekit as I'm
running the machine with a Beaglebone. What is the nature of the
changes made to LinuxCNC that allowed this to work? Do you think
I could get this going on Machinekit?
  


It is completely non-trivial and I am far from sure if it exists as
a series of commits which are easily accessible.
Linuxcnc did not have a Github repo until recently and I don't know
how they converted across.

These are just the commits that actually specify 'JA' in the title
(238 of them)
https://github.com/LinuxCNC/linuxcnc/search?q=JA=Commits

If the commit was relevant but did not have that tag in the commit
text, the search would not find it.
It may also have picked up 'jam' and the likes, Github
searches are not very good.

You are welcome to try cherry-picking the commits and resolving all
the major conflicts occurring because machinekit has completely
diverged from linuxcnc in many respects.  I would not recommend it.

If I were you I would get an old computer with a parport, install
Linuxcnc from a rtai kernel distro.
Then you can find out if it actually works as you want.

If it does, why do you need to use a BBB?

I don't have an axe to grind either way, whatever works best IS
best.


  
On Thursday, April 12, 2018 at 8:28:29 AM UTC-6, Schooner wrote:

   
On 12/04/18 14:59, jo...@allwinedesigns.com
  wrote:


  Thanks for the advice!


I started implementing this the other day and am
  running into follow errors when switching between
  modes using a hal pin. 
  


Yes I did predict that it would likely cause problems

  "The actual instant of changeover could reek havoc if it
  occurred midway through setting the joints say, so that
  would need to be catered for with a function
 that acted upon the changeover pin changing state,
  clearing old data and establishing new defaults or
  whatever."
  
You might be able to get around it by forcing
the position_fb to whatever the actual position changes to,
perhaps by unlinking position_fb at the right point
then re-linking,
with it set to the same as the actual position after the
move.


  
I found this thread on the LinuxCNC forums which
  discusses the same desired behavior and the same
  errors I'm encountering. It seems like they were able
  to resolve the issues, so I'll give what they tried a
  shot: https://forum.linuxcnc.org/10-advanced-configuration/31813-tcp-5-axis-kinematics?limitstart=0

  


We don't have the joints / axes work backported into
Machinekit, it caused a lot of problems in Linuxcnc
initially, so interesting that it seems to help this
succeed.

Hopefully it will work for you too.


  

  On Thursday, April 12, 2018 at 2:48:29 AM UTC-6,
  Schooner wrote:
  
 
  On 12/04/18 09:29, 'schoo...@btinternet.com'
via Machinekit wrote:
  
   

This code snippet from my lathe pulley speed
setting script shows the process to convert and
use case / esac to switch the input to the
correct call


  
  
  Just re-read and that gives the impression you
  need to use a case / esac switch
  
  All you need of course is a single call in place
  of the switch, as P contains the value to pass
  
  eg.    halcmd setp combokins.state $int
  
   



On 11/04/18 21:30, jo...@allwinedesigns.com
  wrote:


  Is there a way to switch
between kinematics modules using G code in
   

Re: [Machinekit] switching between kinematics modes in G code

['schoone...@btinternet.com' via Machinekit]

  
  

On 12/04/18 09:29,
  'schoone...@btinternet.com' via Machinekit wrote:


  
  
  
  This code snippet from my lathe pulley speed setting script shows
  the process to convert and use case / esac to switch the input to
  the correct call
  
  


Just re-read and that gives the impression you need to use a case /
esac switch

All you need of course is a single call in place of the switch, as P
contains the value to pass

eg.    halcmd setp combokins.state $int


  
  
  
  
  On 11/04/18 21:30, j...@allwinedesigns.com
wrote:
  
  
Is there a way to switch between kinematics
  modules using G code in Machinekit? The desired effect is to
  be able to switch between trivkins and a 5 axis inverse
  kinematics module that allows for TCPC (Haas uses G234 to
  enable TCPC, see https://www.youtube.com/watch?v=HxPjH4v5iEg).
  I've implemented the 5 axis kinematics module for my machine.
  I was thinking I could incorporate the trivial kinematics into
  the same module and add a hal pin that would switch between
  the two. Then I could write a python script that flips the hal
  pin, and bind that to a custom G code. Would that work? Is
  there another way to do it?
-- 
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.
  
  
  -- 
  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.


  




-- 
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] switching between kinematics modes in G code

['schoone...@btinternet.com' via Machinekit]

  
  
Interesting concept.

In theory there should be nothing to prevent the combination of two
kinematics types
and a conditional test based upon whether a pin is set, to decide
which is used.

Implementation might be a little more complicated.  
The data structures would need combining so that any data storage
required was available irrespective of which mode it started in.
The actual instant of changeover could reek havoc if it occurred
midway through setting the joints say, so that would need to be
catered for with a function
that acted upon the changeover pin changing state, clearing old data
and establishing new defaults or whatever.

Regards activating, that is the simple bit.
Create a bit pin, called say combokins.state
Then just create a user M code which is a bash script which calls
`setp combokins.state 1` or 0 as required
The 1 or 0 can be passed in the first arg (P) to the M code, just
remember it will be passed as fp and needs conversion to an integer.

This code snippet from my lathe pulley speed setting script shows
the process to convert and use case / esac to switch the input to
the correct call

Like to hear how it goes.

~

#!/bin/bash

## sets scale gain to make output speed accurate
## for each of 4 pulley settings

if [ ! $# -ge 1 ]; then
  echo "Usage: M101 n - where n is speed range 1 - 4"
  exit 1
fi

echo "param 2 is $2"
## emc takes the M101 P3 for example and passes 
## $1 as 3.00 and $2 as -1.00 (because Q was not set)
## to this script!!!
## need to convert to int first

float=$1
int=${float/\.*}
# DEBUG    echo "$float converted to $int"


case $int in

    1 ) halcmd setp scale.0.gain 0.595;;
#   accurate at 1200 in M4 for turning

    2 ) halcmd setp scale.0.gain 1.16;;
#   accurate at 600 in M4 for turning

    3 ) halcmd setp scale.0.gain 2.175;;
#   accurate at 300 in M3 for threading

    4 ) halcmd setp scale.0.gain 4.3;;
#   accurate at 150 in M3 for threading
esac

exit 0




On 11/04/18 21:30,
  j...@allwinedesigns.com wrote:


  Is there a way to switch between kinematics modules
using G code in Machinekit? The desired effect is to be able to
switch between trivkins and a 5 axis inverse kinematics module
that allows for TCPC (Haas uses G234 to enable TCPC,
see https://www.youtube.com/watch?v=HxPjH4v5iEg). I've
implemented the 5 axis kinematics module for my machine. I was
thinking I could incorporate the trivial kinematics into the
same module and add a hal pin that would switch between the two.
Then I could write a python script that flips the hal pin, and
bind that to a custom G code. Would that work? Is there another
way to do it?
  -- 
  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.


  




-- 
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: DE10-DE0-Nano - Invitation to collaborate

['schoone...@btinternet.com' via Machinekit]

  
  
Well done Michael,

Just tested it and works fine on a DE0-NANO too.

If you have no objections I will add them to the images at
http://deb.machinekit.io/uploads/de0-nano/

Notes for anyone looking to test.

Instructions are in the file readme-console-image.md
DO use bmaptool to write to SD card.  dd does not seem to cope too
well, but bmap works fine.

I used the console image and once the ethaddr etc was set etc. just
needed to log in;
$ sudo apt update
$ sudo apt install machinekit-rt-preempt machinekit socfpga-rbf
and I was up and running the socfpga-stepper sim, easy as that!



On 07/04/18 00:56, Michael Brown wrote:


  Just a FYI that I have released 2 new stretch based
images that are much more stable than the previous Jessie ones.


U-boot 2018.01,  4.9.76-ltsi-rt kernel


Also one is a desktop image running LXQT with kwin and even
  though there is some latency in loading, I find the windows to
  be much more responsive
with instantainios drag around etc.
And axis seems to run quite well with preview (see video
  demo).


   
https://github.com/the-snowwhite/soc-image-buildscripts/releases/tag/Release_2.0



  On Tuesday, 29 August 2017 15:05:32 UTC+2, Michael Brown
  wrote:
  

  

  

  Michael Brown has invited you to contribute
  to the following shared folder:
  


  DE10-DE0-Nano
  
  DE10-SoC
  Machinekit demo image with framebuffer
  This image also works with the Atlas
  (DE0-Nano-Soc) board(tested)
  Open

  
  

  

  

  






  
  






  
  






  

  




  

  






  
  






  
  






  

  

  

  
  

  
Google
  Drive: Have all your files within reach from
  any device. 
  Google Inc. 1600 Amphitheatre Parkway,
  Mountain View, CA 94043, USA

  

  

  

  

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

Re: [Machinekit] LinuxCNC and BeagleBone Black - a road well travelled?

['schoone...@btinternet.com' via Machinekit]

  
  

On 05/04/18 10:07, 'fishy' via
  Machinekit wrote:


  

On Wednesday, 4 April 2018 16:41:46 UTC+1, Schooner wrote:

  
  
  It is a community project, but thus far everyone (with minimal
  
  exceptions) who has stood where you are and bemoaned the lack
  of 
  detailed personalised instructions for their
  
  hardware combination of choice, has subsequently failed to
  contribute 
  anything to make it easier for the next person to tread that
  path.
  
  
  If you were to break that trend, I would be delighted.
  
  



I am not sure if that is what was described by "tragedy of
  the commons" ?
  


I think it is, certainly it is a common trend.


  


I guess most open source projects get less than 1% of users
  actually contributing something back to the project?


I wonder if some autodoc system could be made to force
  people to contribute in order to get support from a real
  person? :lol


Unfortunately 99% of people are here to get free cnc
  software installed for zero cost, they are not interested in
  playing with software development as a hobby.
  


Yes and as someone who would not touch Microsoft or Apple with a
bargepole, it does gall somewhat.


  


As a start does machinekit have a easy access wiki system?
  (http://www.machinekit.io/community/contributing/)
  


Wiki's unfortunately are for people who commit a mind dump to a page
and then move on, leaving it orphaned and unmaintained.

Linuxcnc's documentation is full of wikis which refer to Ubuntu
Hardy and other long since deceased distros and you pretty
much need to know enough not to need the wiki in the first place, to
sort the wheat from the chaff.

  


Of course this forum may not be the best place to find
  linuxcnc help, as it is actually  here for discussion of
  machinekit, so maybe the original poster should start by
  updating the wiki
  (http://wiki.linuxcnc.org/cgi-bin/wiki.pl?BeagleBone) with all
  the information they have used and the steps they took to
  install machinekit on the beaglebone.  Then maybe some of the
  experts here could take time away from their most important
  work to review and analyse the problem?
  


If you read the wiki, it was originally largely written by Michael
Haberler, before he left Linuxcnc to found Machinekit.
It is well out of date.

It was the refusal of Linuxcnc to incorporate changes that would
allow ARM boards to run Xenomai and rt-preempt kernels so as to make
the use of an ARM board
possible, amongst many other changes, that led to the split and fork
to Machinekit.
They have since seamlessly incorporated some of the changes, as if
they had come up with them ;-) 

If someone has something to contribute and refuses to use the tools
provided because some perceived difficulty or other bias, I don't
care.

If they create a wiki and provide a link to it, we can cut and paste
the text into a proper asciidoc and incorporate it into the website.
When they move to other things, the wiki will wither and die from
lack of relevance and maintenance, but we will have a document that
could be updated as required.

There's the challenge, Word document, wiki, compilation cut and
paste from a number of forum posts (all of which can be searched
from the website anyway),
or any other format.

If it is of use we will use it.



  


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


  




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

Re: [Machinekit] LinuxCNC and BeagleBone Black - a road well travelled?

['schoone...@btinternet.com' via Machinekit]

On 28 Mar 2018, at 22:02, Rick Mann  wrote:

I'm just starting on building a CNC router using MachineKit and a BBB. You'll 
still need a board of some kind, if for no other reason than to isolate the BBB 
from the rest of your system. I bought an OPTOCAPE ($165) to experiment with, 
but I will be designing and building my own board at the same time (mostly 
because I want all the right connectors on it).


The big problem to get across is that Machinekit is nothing to do with BBB.

The fact that you can get a BBB to work with Machinekit and 'X' 
hardware, does not mean it is the desirable or optimum choice.


For the money you spent on a cape and BBB, you could buy an ex-corporate 
dual core pentium computer and a Mesa card and have a setup which is 50 
times more capable

and far easier to configure and work with.


- Stepper Configuration Wizard: Better introductory information than anything else so 
far, but says it's for "standard parallel port." Does that mean I can't use it 
on BBB?

Yes, the BBB does not have a parallel port. Machinekit is not a beaglebone 
project. So there will always be options not applicable to your hardware



The documentation is legacy Linuxcnc, which was rtai kernel and parport 
or rt-preempt kernel and hardware FPGA cards only.
Where the docs diverge to include machinekit only areas, depends wholly 
upon people writing them and submitting them for general usage.


It is a community project, but thus far everyone (with minimal 
exceptions) who has stood where you are and bemoaned the lack of 
detailed personalised instructions for their
hardware combination of choice, has subsequently failed to contribute 
anything to make it easier for the next person to tread that path.


If you were to break that trend, I would be delighted.


--
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] Happy Birthday Machinekit!

['schoone...@btinternet.com' via Machinekit]

Yes, Happy Birthday to us

What is your inbox like if you have 3 years of these saved to reply to 
John !!!



On 04/04/18 00:37, John Morris wrote:

Happy Birthday #4 Machinekit!

While I've probably *contributed to* Machinekit *less* in the last 
year than ever before, it turns out I've *used* Machinekit *more*, 
whether for the EMC app on my 3D printer, or whether for straight HAL 
and QtQuickVCP for Golibox, autoclave and robot controls. Thanks to 
all the devs and maintainers for the great work.


John


On 04/03/2017 12:19 AM, John Morris wrote:

It's been three years.  Happy Birthday, Machinekit!

 John


On 04/03/2016 04:48 PM, John Morris wrote:

Happy two-year birthday, Machinekit! Another great year and more great
leaps forward.  Keep it up!

John


On 04/03/2015 03:59 AM, John Morris wrote:

A year ago today on April 3, Michael posted the [Machinekit
announcement] on the Emc-developers list.  IMO, that marks the 
official

birthday of Machinekit, so,

Happy Birthday!

I'm incredibly pleased (and surprised!) by the huge leaps the project
has made in such a short time, and by the explosive growth of the
project's community.  In the [ZeroMQ Guide Chap. 6], Pieter Hintjens
writes that the two go hand-in-hand, and says "It's hard to
overemphasize the power and persistence of a working open source
community."  That's exactly what I see here, an amazing bunch of folks
continually attracting new amazing folks, and the result is 
brilliance.

  Congratulations to everybody, both those participating in the
Machinekit project today, and also those who contributed to the 15+ 
year

legacy of the code base.  I can't wait to see what the next year will
bring.

[Machinekit announcement]:
http://sourceforge.net/p/emc/mailman/message/32182244/

[ZeroMQ Guide Chap. 6]: http://zguide.zeromq.org/php:chapter6

 John





--
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: DE0-Nano-SoC install guide

['schoone...@btinternet.com' via Machinekit]

On 04/04/18 13:05, Richard Thornton wrote:

Thanks, much appreciated!

So I just do a "sudo apt-get update" and then a sudo apt-get upgrade"
to upgrade socfpga-rbf?


Just 'apt install socfpga-rbf' will update the package you are 
interested in.


Doing an dist-upgrade on a SD card image should not be done routinely, 
if it works, leave it alone!




The thing is I might never use the DE0-Nano_DB25 (I might not have the
ability to solder it, I might never get round to it) and I want to get
it working well before then, I'm only talking about connecting two
pins between the G540 and the DE0, I have all I need as the G540 can
accept 3.3v.


You will need to look at the schematics Charles sent you for the 40 pin 
header that the DB25 board connects to
20 pins will be the P3 connector and 20 pins the P2 (17 pins plus a 
couple of ground/5v+)


Then preferably take them from the header to a buffered BOB and connect 
to that.


You don't want to be connecting directly to a £90 board if you can help 
it, too easy to fry something.


On 4 April 2018 at 18:51, 'schoone...@btinternet.com' via Machinekit
<machinekit@googlegroups.com> wrote:

On 04/04/18 08:48, Richard Thornton wrote:

Hi,

Apologies, I'm a real newbie and would really appreciate some help,
where I'm up to...

Got the latest image from here:


http://deb.machinekit.io/uploads/de0-nano/debian-9.2-console-armhf-2017-10-29/debian-9.2-console-armhf-2017-10-29-5.0gb.img.xz

I used an 8GB sandisk ultra

In linux:

sudo bmaptool copy ./debian-9.2-console-armhf-2017-10-29-5.0gb.img.xz
/dev/mmcblk0

Connected up using SerialTools on the Mac, select usbserial-X
and baud rate 115200 and hit connect.

Press any key while booting:

=> env default -a
## Resetting to default environment
=> setenv ethaddr ba:d0:4a:9c:4e:ce
=> saveenv
Saving Environment to MMC...
Writing to MMC(0)... done
=> reset

l:p is machinekit:machinekit

uname -a shows:

Linux mksocfpga 4.1.22-ltsi-rt23-ge3c1da3 #1 SMP PREEMPT RT Tue Aug 23
09:56:10 UTC 2016 armv7l GNU/Linux

cat /etc/issue
"Debian GNU/Linux 8 \n \l

Machinekit SoC/FPGA Debian Image, Altera CycloneV 2016-11-21"

ifconfig should show the MAC you set and your IP address should be
stable with DHCP

I can ssh in from my Mac Pro (install XQuartz) using "ssh -X
machinekit@x.x.x.x"

I change directory into machinekit and run machinekit

I'm presented with the Machinekit Configuration Selector, woohoo!

Is 4.1.22-ltsi-rt23-ge3c1da3 correct for debian-9.2, isn't it supposed
to be 4.9, also /etc/issue shows 8 and the dates are all in 2016,
seems weird?

It is an upgraded Jessie image.

There is no Debian kernel for the DE0 so the kernel is one that works


What to do now with machinekit, no idea where to start, Charles made
me a G540 config:


https://github.com/machinekit/mksocfpga/commit/7e81953c7a7971daaa08c533ef1cc828dbd9fcdd

How do I get that on to this DE0?


Upgrade the socfpga-rbf package

Then check /lib/firmware/socfpga/dtbo for the config you need

Specify this one in your .ini file


So I have my G540 and a stepper, all I want to do is cable up the X
axis to verify everything works (I'm using jumper wires) so can
somebody please give me a newbie guide to what I do next, my thoughts:

DE0 to G540 DB25, on the G540 it seem I only need to connect pins 2
(X-AXIS STEP) & 3 (X-AXIS DIRECTION), which pins will I connect that
to on the DE0 once I import the Charles G540 config, direct DE0 pin to
G540 pin connections as I don't have an assembled DE0-Nano_DB25 (I got
three from osh park but I'm waiting for the parts to come from
digi-key and I will have to do a bunch of practice before I even
attempt to solder 0603)?

DB9 for X AXIS I need to connect the four wires from the stepper to
pins 6, 7, 8 & 9, 6 & 7 are the A coil, 8 & 9 the B coil, how to work
out the order as the stepper wires (black/green are one coil and
red/blue are another according to a piece of paper that came with the
stepper)?


Plenty of sources on the net for this


Once I have the G540 config and have wired the above simple test what
do I do from the "Machinekit Configuration Selector" page to just test
one stepper, is that possible, if so, how?


I would suggest that you modify the configs/hm2-soc-stepper/5i25-socfpga.ini
and hal sim for now
Don't worry about attaching steppers until you have a DB25, because the
pinout on the headers is different and you will get in a right mess quite
easily


Sorry to be a pain but this would really be a lot of help.

Thanks.

Richard


On 2 March 2018 at 18:37, Richard Thornton <richie.thorn...@gmail.com>
wrote:

Update

Image installed and successfully booted

I lost some time figuring out that I had written to an SD card partition
instead of the raw device...

On 28 February 2018 at 23:11, Richard Thornton
<richie.thorn...@gmail.com> wrote:

Hi,

Thanks for all the help.

So I have the DE0-Nano-SoC, G540 and steppers are

Re: [Machinekit] Re: Rotary Axis on BBB and Xylotex BBB_DB25/26

['schoone...@btinternet.com' via Machinekit]

  
  
It is floating point, otherwise it could only ever be accurate to
the nearest whole unit

On 30/03/18 08:59, John Dammeyer wrote:


  

  
I'll answer my own question. I was searching through
  the HAL docs rather than the ini docs.
  

 
http://www.machinekit.io/docs/config/ini_config/#sub:AXIS-section
In that document I found ANGULAR_UNITS = degrees and has
  nothing to do with NC code.  
"'ANGULAR_UNITS =
  ' - Specifies the 'machine units' for
  rotational axes. Possible choices are 'deg', 'degree' (360
  per circle), 'rad', 'radian' (2pi per circle), 'grad', or
  'gon' (400 per circle). This does not affect the angular
  units of NC code. In RS274NGC, A-, B- and C- words are
  always expressed in degrees."
It doesn't state if the SCALE
is a floating point number like 75,000 pulses per 360
degrees = 208.3 per 1 degree or if it has to be 208.


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


  




-- 
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: rtapi_loadrt 'hal_pru_generic'... failed: Operation after apt update upgrade (4.14.20-ti-rt-r36)

['schoone...@btinternet.com' via Machinekit]

  
  
The linuxcnc log only shows after the error, need to see what it was
that produced 'operation not permitted' from insmod

We don't know what you upgraded from exactly, but for quite some
time now the /usr/lib/linuxcnc/prubin/*.bin have been symlinked
through to 
/usr/lib/linuxcnc//*.bin
Check both locations exist and no extra locations lingering from old
installs are there, but it does not sound like it is missing.
insmod errors can be pretty vague, but normally it is clear if the
module to be loaded does not exist.

It would not matter if the pru_generic.bin came from a xenomai
package, the binary format is the same across flavours.

Before I changed the packaging to build the pru binaries for all
armhf packages, people used to just manually copy them 
across from a xenomai package, if they wanted to use rt-preempt.


On 29/03/18 09:00, Karl Jacobs wrote:


  Are you sure that you prucode=prubin points to
rt-preempt/pru_generic.bin and not xenomai/pru_generic.bin ? The
Stretch Machinekit image runs on rt-preempt.

Am Mittwoch, 28. März 2018 22:24:08 UTC+2 schrieb Seb hl:

  Hi,
I've recently downloaded the Stretch Machinekit image
  for the Beaglebone (weekly build
  05.03.2018, 4.14.20-ti-rt-r36). Now I did an apt
  udate + upgrade and my hal-standalone config using the
  python hal modul no longer starts.



  $ export Debug=5
  $ python hal_test.py




  
  
Traceback (most recent call last):
  File "printjob_hal.py", line 305, in
  
    init_hardware()
  File "printjob_hal.py", line 211, in
  init_hardware
    rt.loadrt('hal_pru_generic', pru=1,
  disabled=0, num_stepgens=3, num_pwmgens=6,
  prucode=prubin, halname='hpg1', pru_period=1000)
  File "hal/cython/machinekit/rtapi.pyx",
  line 219, in machinekit.rtapi.RTAPIcommand.loadrt
  (hal/cython/machinekit/rtapi.c:5233)
RuntimeError: rtapi_loadrt '('hal_pru_generic',
  'disabled=0', 'pru_period=1000', 'num_stepgens=3',
  'pru=1', 'halname=hpg1',
  'prucode=/usr/lib/linuxcnc/prubin/pru_generic.bin',
  'num_pwmgens=6')' failed: Operation not permitted


  

  
  

linuxcnc.log shows



  
  
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5746:user halg_exit:293 HAL: removing
  component 76 'halcmd5746'
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5746:user ulapi_hal_lib_cleanup:235 HAL:
  lib_module_id=74
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5746:user halg_exit:293 HAL: removing
  component 74 'hal_lib5746'
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5746:user halg_exit:315 HAL:
  hal_errorcount()=0
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5746:user halg_exit:316 HAL: _halerrno=0
Mar 28 16:27:26 beaglebone rtapi:0:
  4:rtapi_app:5740:user pid=5740 flavor=rt-preempt
  gcc=6.3.0 20170516 git=v0.1~-~e37c70e
Mar 28 16:27:26 beaglebone msgd:0:
  ulapi:5750:user _ulapi_init(): ulapi rt-preempt
  v0.1~-~e37c70e loaded
Mar 28 16:27:26 beaglebone msgd:0:
  ulapi:5750:user halg_xinitfv:271 HAL: singleton
  component 'hal_lib5750' id=78 initialized
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5750:user --halcmd stop
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5750:user hal_stop_threads:357 HAL:
  threads stopped
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5750:user halg_exit:293 HAL: removing
  component 80 'halcmd5750'
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5750:user ulapi_hal_lib_cleanup:235 HAL:
  lib_module_id=78
Mar 28 16:27:26 beaglebone msgd:0:
  hal_lib:5750:user 

Re: [Machinekit] Pico-Systems ppmc setup

['schoone...@btinternet.com' via Machinekit]

  
  

On 12/03/18 14:48, Maxime Lemonnier
  wrote:


  Hi MachineKit,


It's been almost 8 years since I used my pico systems
  univpwm system (5 axis brushless servos). At the time I was in
  the process of rewriting Axis, that I found too monolithic to
  maintain or extend. I had a PyQt4 gui working, jogging,
  mdi-ing with a rather raw openGL display. I recently
  resurrected all this code and made it work with the latest
  linuxcnc version. Then I learned about the machinekit project,
  which I find fascinating. Especially the multicore effort and
  the more recent backend(hal)/frontend(not-hal) separation.
  Which leads to my questions:


What is the state of the ppmc driver in all this? anyone
  used it?
  


I am pretty sure no-one uses it, because it is not built.
https://github.com/machinekit/machinekit/blob/master/src/Makefile#L1440

The actual code is just the same as linuxcnc, it has not been
updated to run as instantiable or use any of the new HAL stuff.


  
Is there an effort/interest in modernizing the front-end
  API?
  


Alex has done quite a lot with the python API.

Or do you mean the front end GUI, as you mentioned rewriting Axis?

Alex has written Machineface, a remote capable Axis clone plus
QtQuick and Qml based VCP stuff.

I have a C++ Qt5 Axis replacement (which is not released because I
don't want to have to support it),
plus other C++ VCP stuff.


  
Any interest in ROS, expecially ROS2?
  


There is definitely some interest in ROS, I expect those concerned
will chime in.


  


At the present I use my machine as a robot to precisely
  move a sensor. I have years of experience in modern
  Python/C++/Qt/QML and lots of experience in real-time,
  math-heavy programming. I *may* find some time to contribute a
  bit to your project.
  


You will be most welcome.

Look forward to seeing what direction interests you.


  




Thanks!
  
  -- 
  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.


  




-- 
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: how to add toolchanger funtion to BBB with Xylotex cape

['schoone...@btinternet.com' via Machinekit]

On 03/03/18 16:17, Aurelien wrote:

Many thanks for reply

yes this is your code but modified by Mike Ross for 6 tool turret

For the Axis i have set as you says LINEAR and with trial and error 
have found the good SCALE for turn 360° exactly



i don't understand "You simply home axis A" because with this this 
component this is impossible without following error from classic setting,


You just set the homing values to 0, then A will show as homed with no 
movement.

(read www.machinekit.io/docs/config/ini_homing/)

If you have connected up properly, when homed the relevant pin will be 
true and allow the M6TN command without movement to initialise.


also impossible to move the motor by GUI. (hijack stepgen) (i think 
you know that lol)


It is not impossible, just load a config without the toolchanger 
component and A connected as normal to work out moves required



There is so much commented out in your component, including the tool 
number setting on homing provision, I am not going to get into
trouble shooting something that seriously diverges from the component I 
wrote.


I would get the original component working by reducing the tool numbers 
to 6 and changing the angles / steps between stations accordingly.


Even if you managed to get the ATC seeking the home switch, you have to 
update machinekit with the current tool number.


The method my component uses is simple, because it sets the number via 
M6, whilst not attempting to process the command.


It could be adapted to rotate the ATC until the home switch is triggered 
when A is homed, then trigger a halui MDI command to set the tool number.


What you need to be wary of is un-commanded movement and whether it will 
always be safe or if it is possible to foul a workpiece
or injure the operator when the ATC suddenly starts rotating during a 
homing procedure.



--
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: how to add toolchanger funtion to BBB with Xylotex cape

['schoone...@btinternet.com' via Machinekit]

  
  
It would be very helpful if you actually said what you had found and
provided a link to it.

From the comments in the code, I can tell that it is one I wrote
some time ago and posted here
http://www.machinekit.io/docs/developing/toolchangers/
amongst other places, including on the Linuxcnc contributed
components wiki.

There are several problems with this type of ATC, that need to be
overcome. 

First is that it is extremely unlikely that your tool tips will be a
perfect '360 / number_of_tools' apart.
I found I had to move different amounts depending upon whether it
was a conventional cutting tool
or a VDI 20 mounted tool or drill.

Next there is how rotary axes are dealt with.
Unless care is taken, and incremental moves only are programmed, the
interpreter will try to take the shortest path to the required
position, which may entail running in reverse.
eg. if you are at 30 deg and program in 330 deg, it will attempt to
move 60 deg in reverse. You need to program for instance G90 A300 
to avoid ramming back against the pawl and stalling.

The only sure way to determine the movement amounts is to experiment
using MDI commands until you have consistent results.
Every ATC will be different, the one this was written for had 8
tools, not 6. (4 cutting 4 boring)

On my current lathe I abandoned degrees altogether and calculated
the number of steps required to move the distance, programmed A as a
linear axis 
and just moved by outputting incremental position_cmd.  Far simpler
to account for any differences in move between tool numbers.

To answer your second email

There is no provision for a ATC home switch, because the one it was
originally written for did not have one.

The code tells you how to home

                    // axis does not remember the current tool
number, so prompt for it when A axis homed.
    if(ishomed && !currenttoolnumber
&& !bWarn)
    {
    bWarn = true;  // just warn once, its not an
error as such but INFO won't display unless debugging is set 3+
    rtapi_print_msg(RTAPI_MSG_ERR, "No tool
selected. Use M6Tx to set current tool");
    break;..
    }

You simply home axis A, and if no tool number is set, you are
prompted to do a M6TN to set the tool number.

If you want an automatic rotation until the home switch is found
etc, you need to use elements of the carousel toolchanger in the
same page.

I think that one uses an amended iocontrol component however, which
I have no intention of publishing or supporting, so I would just use
the method outlined above
unless your programming is up to doing similar.

regards

On 02/03/18 22:39, Aurelien wrote:


  Hi


Now i have found good config for moving the turret but i
  like to report 2 issue.


First :
When you move from tool 1 to 6 with actual setting the past
  to pawl move too less compared to real amount moved 5x63° =
  .315     fudge factor is 14 so 315-14 = 301° !!!


If i'm not wrong :



  pin io float odd_move = 64      "distance from odd tool
station to even one";
  pin io float even_move = 64     "distance from even tool
station to odd one";
  pin io float divisor = 2        "used in calculating
reverse move to lock";
  pin io float fudge_factor = 24      "additional move to
ensure locking";  
  // fudge factor need to be selected higher than
"additional angle" x( nTool-1)
  // so 4°x(6-1) = 20  i have add +4 for make really sure.



In this way 5x64° = 320° - 24 = 296° so i'm sure the final
  position is 300° on the pawl with 4° more for locking


Please are you agree with this ?




Second :
Is not a real issue but need to be potnted for noob like
  me 


 if(!fjog  && (delay_index < (delay * 30)) )  
if your stepper is too slow the past to pawl not append so
  you need to increase this delay.




Br






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

Re: [Machinekit] DE0-Nano-SoC install guide

['schoone...@btinternet.com' via Machinekit]

  
  

On 28/02/18 15:31,
  'schoone...@btinternet.com' via Machinekit wrote:


  
  
  On 28/02/18 12:11, Richard Thornton
wrote:
  
  
Hi,
  
  
  Thanks for all the help.


So I have the DE0-Nano-SoC, G540 and
  steppers are there instructions on how to install
  machinekit on the SoC and mesa on the FPGA?
  

  
  
  Use the existing image and change the firmware config in the .ini
  file to the firmware Charles has provided for the 540
  
  I put a snippet of my ini file here which shows that line.


Here even, that link somehow didn't make it

http://blog.machinekit.io/2016/11/you-will-recall-that-while-back-charles.html

 
  Easiest to adapt the 5i25-socfpga.ini etc to start with, get a sim
  working to show the module and the firmware is loading is loaded
  OK and then progress to a real config
  
  If you are not familiar with Mesa 5i25 pin outs, it will take a
  while, and as Charles alluded to, the pin designations from GPIO
  out to DB25 pins take a bit of getting your head around
  
  I made the attached image when I used  one without a 7i76, to
  connect to a stepper powered small mill using normal stepper
  drivers
  Just the P3 output pinout, but when you match it to the diagrams
  Charles linked to you will begin to see the light.
  (It is already in the forum posts if you search DE0-NANO, as with
  lots of other info, some out of date however - beware)
  
  

  


I should be able to wire it all up OK, I'm
  basically going to start by getting one stepper moving as
  instructed, I'm calling this phase 1.


So it will be DE0-Nano-SoC connected to G540
  connected to a stepper.


I will just install Cetus on Android.


Am I taking the path of least resistance?
  

  
  
  If you are a masochist.  :-P 
  
  Just connect it via a cat5 cable to your router and `ssh -X` into
  it to start with, you can struggle with remote apps as a second
  issue once you have it running.
  
  

  


Any documents, tips or tricks that will help
  me?
  

  
  
  There are several blogs on the DE0 starting here
  http://blog.machinekit.io/2016/04/altera-soc-running-machinekit-with.html
  
  

  


My computer skills are great so as long as I
  have instructions I will be fine with that.


I know very little about CAD/CAM or
  emc2/linuxcnc/machinekit.


Thanks again.


Richard






  

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


  




-- 
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] DE0-Nano-SoC install guide

['schoone...@btinternet.com' via Machinekit]

  
  

On 28/02/18 12:11, Richard Thornton
  wrote:


  Hi,


Thanks for all the help.
  
  
  So I have the DE0-Nano-SoC, G540 and steppers
are there instructions on how to install machinekit on the
SoC and mesa on the FPGA?

  


Use the existing image and change the firmware config in the .ini
file to the firmware Charles has provided for the 540

I put a snippet of my ini file here which shows that line.

Easiest to adapt the 5i25-socfpga.ini etc to start with, get a sim
working to show the module and the firmware is loading is loaded OK
and then progress to a real config

If you are not familiar with Mesa 5i25 pin outs, it will take a
while, and as Charles alluded to, the pin designations from GPIO
out to DB25 pins take a bit of getting your head around

I made the attached image when I used  one without a 7i76, to
connect to a stepper powered small mill using normal stepper drivers
Just the P3 output pinout, but when you match it to the diagrams
Charles linked to you will begin to see the light.
(It is already in the forum posts if you search DE0-NANO, as with
lots of other info, some out of date however - beware)


  

  
  
  I should be able to wire it all up OK, I'm
basically going to start by getting one stepper moving as
instructed, I'm calling this phase 1.
  
  
  So it will be DE0-Nano-SoC connected to G540
connected to a stepper.
  
  
  I will just install Cetus on Android.
  
  
  Am I taking the path of least resistance?

  


If you are a masochist.  :-P 

Just connect it via a cat5 cable to your router and `ssh -X` into it
to start with, you can struggle with remote apps as a second issue
once you have it running.


  

  
  
  Any documents, tips or tricks that will help
me?

  


There are several blogs on the DE0 starting here
http://blog.machinekit.io/2016/04/altera-soc-running-machinekit-with.html


  

  
  
  My computer skills are great so as long as I
have instructions I will be fine with that.
  
  
  I know very little about CAD/CAM or
emc2/linuxcnc/machinekit.
  
  
  Thanks again.
  
  
  Richard
  
  
  
  
  
  

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


  




-- 
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] Machinekit XHC-WHB04B-6

['schoone...@btinternet.com' via Machinekit]

  
  

On 23/02/18 07:26,
  'schoone...@btinternet.com' via Machinekit wrote:


  
  
  
  
  On 23/02/2018 01:12, Aurelien wrote:
  
  
this message is sended by the driver i have found
  the output text error in source code
  
  
  
 xhc.hal =
  (xhc_hal_t *)hal_malloc(sizeof(xhc_hal_t));
 if (xhc.hal ==
  NULL) {
 fprintf(stderr,
  "%s: ERROR: unable to allocate HAL shared memory\n",
  modname);
 exit(1);
  

  
  The most common mistake that gives this error, is calling
  hal_malloc() when realtime is not started.
  Does not look to be the case.
  
  I have no familiarity with this code and only have a standard xhc
  pendant, but will look later.


I don't know what you are doing, but when I build it and run, it
works (as far as it can with no pendant attached)

You will get the error you had when realtime is not started.

The memory allocation will work in sim mode because that uses
calloc() not hal_malloc()


user@INTEL-i7:/usr/src/sandbox/machinekit# DEBUG=5 realtime restart
user@INTEL-i7:/usr/src/sandbox/machinekit# halcmd loadusr
xhc-whb04b-6 -Hup
:0: Program 'xhc-whb04b-6' started
user@INTEL-i7:/usr/src/sandbox/machinekit# hal   initialize HAL
component in HAL mode xhc-whb04b-6 ... ok
hal   initialize shared HAL memory for component id  80 ... ok
hal   bit   out whb.button.reset
hal   bit   out whb.button.macro-11
hal   bit   out whb.button.stop
hal   bit   out whb.button.macro-12
hal   bit   out whb.button.start-pause
hal   bit   out whb.button.macro-13
hal   bit   out whb.button.feed-plus
hal   bit   out whb.button.macro-1
hal   bit   out whb.button.feed-minus
hal   bit   out whb.button.macro-2
hal   bit   out whb.button.spindle-plus
hal   bit   out whb.button.macro-3
hal   bit   out whb.button.spindle-minus
hal   bit   out whb.button.macro-4
hal   bit   out whb.button.m-home
hal   bit   out whb.button.macro-5
hal   bit   out whb.button.safe-z
hal   bit   out whb.button.macro-6
hal   bit   out whb.button.w-home
hal   bit   out whb.button.macro-7
hal   bit   out whb.button.s-on-off
hal   bit   out whb.button.macro-8
hal   bit   out whb.button.fn
hal   bit   out whb.button.probe-z
hal   bit   out whb.button.macro-9
hal   bit   out whb.button.macro-10
hal   bit   out whb.button.macro-14
hal   bit   out whb.button.mode-continuous
hal   bit   out whb.button.macro-15
hal   bit   out whb.button.mode-step
hal   bit   out whb.button.macro-16
hal   s32   out whb.axis.0.jog-counts
hal   bit   out whb.axis.0.jog-enable
hal   float out whb.axis.0.jog-scale
hal   bit   out whb.axis.0.jog-vel-mode
hal   s32   out whb.axis.1.jog-counts
hal   bit   out whb.axis.1.jog-enable
hal   float out whb.axis.1.jog-scale
hal   bit   out whb.axis.1.jog-vel-mode
hal   s32   out whb.axis.2.jog-counts
hal   bit   out whb.axis.2.jog-enable
hal   float out whb.axis.2.jog-scale
hal   bit   out whb.axis.2.jog-vel-mode
hal   s32   out whb.axis.3.jog-counts
hal   bit   out whb.axis.3.jog-enable
hal   float out whb.axis.3.jog-scale
hal   bit   out whb.axis.3.jog-vel-mode
hal   s32   out whb.axis.4.jog-counts
hal   bit   out whb.axis.4.jog-enable
hal   float out whb.axis.4.jog-scale
hal   bit   out whb.axis.4.jog-vel-mode
hal   s32   out whb.axis.5.jog-counts
hal   bit   out whb.axis.5.jog-enable
hal   float out whb.axis.5.jog-scale
hal   bit   out whb.axis.5.jog-vel-mode
hal   bit   out whb.pendant.is-sleeping
hal   bit   out whb.pendant.is-connected
hal   float in  whb.halui.axis.0.pos-feedback
hal   float in  whb.halui.axis.1.pos-feedback
hal   float in  whb.halui.axis.2.pos-feedback
hal   float in  whb.halui.axis.3.pos-feedback
hal   float in  whb.halui.axis.4.pos-feedback
hal   float in  whb.halui.axis.5.pos-feedback
hal   float in  whb.halui.axis.0.pos-relative
hal   float in  whb.halui.axis.1.pos-relative
hal   float in  whb.halui.axis.2.pos-relative
hal   float in  whb.halui.axis.3.pos-relative
hal   float in  whb.halui.axis.4.pos-relative
hal   float in  whb.halui.axis.5.pos-relative
hal   float in  whb.stepgen.00.maxvel
hal   float in  whb.stepgen.00.position-scale
hal   float in  whb.stepgen.01.maxvel
hal   float in  whb.stepgen.01.position-scale
hal   float in  whb.stepgen.02.maxvel
hal   float in  whb.stepgen.02.position-scale
hal   float in  whb.stepgen.03.maxvel
hal   float in  whb.stepgen.03.position-scale
hal   float in  whb.stepgen.04.maxvel
hal   float in  whb.stepgen.04.position-scale
h

Re: [Machinekit] Machinekit XHC-WHB04B-6

['schoone...@btinternet.com' via Machinekit]

On 23/02/2018 01:12, Aurelien wrote:
this message is sended by the driver i have found the output text 
error in source code


xhc.hal = (xhc_hal_t *)hal_malloc(sizeof(xhc_hal_t));
if (xhc.hal == NULL) {
fprintf(stderr, "%s: ERROR: unable to allocate HAL shared memory\n", 
modname);

exit(1);
The most common mistake that gives this error, is calling hal_malloc() 
when realtime is not started.

Does not look to be the case.

I have no familiarity with this code and only have a standard xhc 
pendant, but will look later.





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


--
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: BiggleBone Red from element 14 and Machinekit with furaday cape

['schoone...@btinternet.com' via Machinekit]

  
  
Hopefully with this info, someone who knows about the BBB will be
able to see what is likely happening

A SWAG from me would be that the correct device tree file is not
being used, but what do I know 
;-) 

On 18/02/18 12:25, Marius Alksnys
  wrote:


    
  machinekit@beaglebone:~/CRAMPS$ DEBUG=5 realtime status
  
  /bin/bash: warning: setlocale: LC_ALL: cannot change locale
  (en_GB.utf8)
  
  msgd:0 stopped
  
  rtapi:0 stopped
  
  machinekit@beaglebone:~/CRAMPS$ DEBUG=5 realtime restart

  /bin/bash: warning: setlocale: LC_ALL: cannot change locale
  (en_GB.utf8)
  
  machinekit@beaglebone:~/CRAMPS$ halcmd loadrt hal_bb_gpio
output_pins=816 input_pins=807
  
  E: 18-02-18 12:20:36 dangling 'ROUTER' socket created at
  rtapi/rt-preempt/rtapi_app.cc:1301
  
  :0: insmod failed, returned -1:
  
  rtapi_rpc(): reply timeout
  
  See /var/log/linuxcnc.log for more information.
  
  machinekit@beaglebone:~/CRAMPS$ cat /var/log/linuxcnc.log
   
  Feb 18 12:20:06 beaglebone msgd:0: msgd:0: got signal 15 -
  sending SIGTERM to rtapi (pid 17329)
  
  Feb 18 12:20:06 beaglebone msgd:0: msgd:0: Terminated -
  shutting down
  
  Feb 18 12:20:06 beaglebone msgd:0: zeroconf: unregistering
  'Log service on beaglebone.local pid 17324'
  
  Feb 18 12:20:06 beaglebone msgd:0: log buffer hwm: 0% (8 msgs,
  665 bytes out of 524288)
  
  Feb 18 12:20:06 beaglebone msgd:0: sent SIGTERM to rtapi (pid
  17329)
  
  Feb 18 12:20:06 beaglebone msgd:0: normal shutdown - global
  segment detached
  
  Feb 18 12:20:24 beaglebone msgd:0: startup pid=17433
  flavor=rt-preempt rtlevel=5 usrlevel=5 halsize=524288
  shm=Posix cc=gcc 6.3.0 201
  70516  version=v0.1~-~57844e1
  
  Feb 18 12:20:24 beaglebone msgd:0: ØMQ=4.2.1 czmq=4.0.2
  protobuf=3.0.0 atomics=gcc intrinsics    libwebsockets=2.0.3
  
  Feb 18 12:20:24 beaglebone msgd:0: configured: sha=57844e1
  
  Feb 18 12:20:24 beaglebone msgd:0: built:  Dec  2 2017
  11:50:00 sha=57844e1
  
  Feb 18 12:20:24 beaglebone msgd:0: register_stuff: actual
  hostname as announced by avahi='beaglebone.local'
  
  Feb 18 12:20:24 beaglebone msgd:0: zeroconf: registering: 'Log
  service on beaglebone.local pid 17433'
  
  Feb 18 12:20:24 beaglebone rtapi:0: 2:rtapi_app:17438:user
  rtapi:0: cannot create core dumps - /proc/sys/fs/suid_dumpable
  contains 0
  
  Feb 18 12:20:24 beaglebone rtapi:0: 2:rtapi_app:17438:user you
  might have to run 'echo 1 > /proc/sys/fs/suid_dumpable' as
  root to ena
  ble rtapi_app core dumps
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  rtapi.so default iparms: ''
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  RTAPI:0  rt-preempt v0.1~-~57844e1 init
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  rtapi: loaded from rtapi.so
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  hal_lib.so default iparms: ''
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  rtapi_app_main:195 HAL: initializing RT hal_lib support
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  halg_xinitfv:90 HAL: initializing component 'hal_lib' type=4
  arg1=0 arg2=0
  /0x0
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  hal_heap_addmem:58 HAL: extending arena by 262144 bytes
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  halg_export_xfunctfv:85 HAL: exporting function 'newinst' type
  2 fp=0 owne
  r=66
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  halg_export_xfunctfv:85 HAL: exporting function 'delinst' type
  2 fp=0 owne
  r=66
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  halg_xinitfv:271 HAL: singleton component 'hal_lib' id=66
  initialized
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  rtapi_app_main:199 HAL: RT hal_lib support initialized rc=66
  
  Feb 18 12:20:24 beaglebone rtapi:0: 4:rtapi_app:17438:user
  hal_lib: loaded from 

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

['schoone...@btinternet.com' via Machinekit]

  
  

On 18/02/18 12:01, Marius Alksnys
  wrote:


  Line 28:
loadrt hal_bb_gpio
  output_pins=816,822,823,824,825,826,914,923,925
  input_pins=807,808,809,810,817,911,913

  


I know nothing about BBB specifically

To debug it, use 

$ DEBUG=5 realtime restart
$ halcmd loadrt hal_bb_gpio
output_pins=816,822,823,824,825,826,914,923,925
input_pins=807,808,809,810,817,911,913

 to launch and look at /var/log/linuxcnc.log at the point of failure
It will contain the rtapi error message prints

If you cannot do this because the whole thing relies upon previously
loaded hardware drivers etc, then run
$ DEBUG=5 machinekit .ini
and look at the log after that fails

Also check dmesg in case of a GP fault or similar, albeit I see no
hint of that.


  

  2018 m. vasaris 18 d., sekmadienis 13:56:18 UTC+2, Schooner
  rašė:
  

On 18/02/18 11:37, Marius Alksnys wrote:

>

> CRAMPS.hal:28: insmod failed, returned -1:


Whatever you are trying to load at line 28 of your hal file
is what is 
producing the error


>

>

> That dangling 'DEALER' socket error sometimes shows up
even in BB Black.


Don't worry about that.

Since we switched to the new zmq API, that comes up when
machinekit does 
not shut down cleanly.


Something that used to be deleted automatically is not now.

  

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


  




-- 
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: BiggleBone Red from element 14 and Machinekit with furaday cape

['schoone...@btinternet.com' via Machinekit]

On 18/02/18 11:37, Marius Alksnys wrote:


CRAMPS.hal:28: insmod failed, returned -1:


Whatever you are trying to load at line 28 of your hal file is what is 
producing the error





That dangling 'DEALER' socket error sometimes shows up even in BB Black.


Don't worry about that.
Since we switched to the new zmq API, that comes up when machinekit does 
not shut down cleanly.


Something that used to be deleted automatically is not now.

--
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] 5-axis simultaneous, G-codes?

['schoone...@btinternet.com' via Machinekit]

Not a subject I know much about, this seems to give the best overview of 
the kinematics.


http://linuxcnc.org/docs/ja/html/motion/5-axis-kinematics.html

I think the XYZAC example at the very end is nearest what you are 
proposing, with A and C rotating in relation to Z


The G codes remain the same, but the plane in which the axis operates 
may limit them.


Regards post processors, usually one for Mach is a good starting point, 
being generally compatible.


Quite a few CAM packages have linuxcnc posts, either in the package or 
as something available either from their forum or the linuxcnc forum. So 
check either before you choose a CAM or before you write your own.




On 17/02/2018 23:51, Damien D wrote:

Hi,

I'm planning on building a 5axis plasma cutter similar to this one 
 but 
with one more axis to tilt the torch head.
I'm thinking of starting from the existing maxkins kinematics (XYZBC) 
and then modify it to my needs.


Sorry if some questions seem 'stupid' but I'm quite new in CAM.. I'm 
googling around and try to understand how the 5axis interface works 
between CAM softwares and CNC controller (Machinekit).


What I'm struggling to understand is what will be the G-codes 
supported by Machinekit if I use the "maxkins" configuration?


Does Machinekit support RTCP (Rotating Tool Center Point) like in this 
video . If yes, what are 
the G-codes commands Machinekit can understand to handle RTCP?


I would need to know that to chose/configure the post-processor.
Or Maybe I should rather ask what post-processor (configuration) 
should I use to produce G-code that can be understood by Machinekit?


Thanks for your help,

/Damien
--
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.


--
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: Machinekit and closed loop

['schoone...@btinternet.com' via Machinekit]

Ha, very good!


On 17/02/18 11:41, fritz wrote:
I first read that it had a name on the webcomic XKCD, but it appears 
that this phenomena now has its own website:


http://xyproblem.info/

On 02/16/2018 11:21 AM, 'schoone...@btinternet.com' via Machinekit wrote:

Now we know what you are doing, it is easier to assist.

You really need to ask a question about your problem, not how to 
effect the solution you have thought of.




--
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: Machinekit and closed loop

['schoone...@btinternet.com' via Machinekit]

  
  
Now we know what you are doing, it is easier to assist.

You really need to ask a question about your problem, not how to
effect the solution you have thought of.

The usual way to test backlash with a mill / lathe is to use a dial
gauge and move the bed a distance within the gauges range.
No need for a closed loop stepper.
May take several bites, but backlash should be taken up by the
initial movement in either direction and be pretty constant.

If you are getting a loss of position at a particular point in the
bed travel aside from the initial backlash, that could be caused by
binding, flexing or similar.
Insufficiently robust, loose or out of square / out of parallel,
rails, screws or many other mechanical components could be to blame.

A very common one is where the bed runs on 2 rails that are not
perfectly parallel and there is a pinch point at one or even both
ends.
Another is with Chinese castings and gib strips that have not been
scraped and mated properly
( I bought one once where the gib strips had obviously been
'finished' with an angle grinder!)

The ini file has facility to read a compensation file for backlash
on a per axis basis.
http://www.machinekit.io/docs/config/ini_config/#axis_-num-section-a-id-sub-axis-section-a

That should take care of backlash, which can differ in opposing
directions, especially on the Z axis where head mass comes into play
and may pre-load some moves and play catch-up on others.

Have a good search on their forum first, you won't be the first or
last person with a particular problem, it is defining what the
problem is that is key.

Good luck.


On 16/02/18 15:23, pasteur wrote:


  
Ok thank you guys, it was very useful all the data that you
  provided to me. 
Maybe I'm gonna to search or post in LinuxCNC forums... 
I read very interested the PID algorithm , but I'm using
  steppers motors and it isnt too eficient I guess, for my
  problem. My problem is simple I need to create a close loop
  because the backlash on my machine it isn't equal in all
  points and I need to measure and correct the errors...


I'm gonna to search in LinuxCNC forums and  post a question
  if it is necessary 


Thank you a lot.
  
  -- 
  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.


  




-- 
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] Machinekit and closed loop

['schoone...@btinternet.com' via Machinekit]

I suggest you read the posts on the linuxcnc forum.

More words have been written on this than most other subjects.

For the most part, the people who ask, want to exceed the limits of 
their stepper motors but escape the consequences.


https://www.forum.linuxcnc.org/forum/27-driver-boards/29357-real-closed-loop-steppers

Above is a starter



On 15/02/2018 19:45, pasteur wrote:
Hello everybody. I wanna make a simple question. How I can use a ruler 
or anything (anything that have sense) to create a closed loop for 
Machinekit?
I mean , I read many post  that explain that  it is possible but I 
didn't find a post that explain how do it (sorry about that :( ). I 
mean , I don´t know even where I must begin...
After read some Machinekit´s documentation  I guess that I need to 
program a HAL component , but also I dont know if that component 
already exists and I gonna to re invent the wheel.


Can someone give me a clue about this?

Thanks!
--
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.


--
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] Build MK for non-debian distribution

['schoone...@btinternet.com' via Machinekit]

  
  

On 15/02/18 07:37, Filip Kotouček
  wrote:


  Hello everyone,


I would like to ask if there is possibility to build
  Machinekit to other Linux distribution than Debian. To be
  specific we have platform based on (am335x) Beaglebone. I'm
  currently using official TI kernel 4.9.59 Arago. There is no
  packaging system and because of Buildroot I don't have native
  toolchain in the target.


The ideal scenario will be to build the Machine kit by
  cross-compilation and just paste some files into filesystem.
  


This may or may not be of use, I don't / won't use any boards that
are not capable of building their own software.

If you use Debian multistrap on your desktop, not only will you have
a chroot system you can compile in, it downloads a base Debian root
filesystem tarball for the version/arch

You could also use this for the basis of the filesystem on your
board, with just enough libs etc to be able to run the binaries, but
with the build tools and any superfluous stuff stripped out.
Then you do have a packaging system, so building Machinekit
becomes optional

I have chroot builders for amd64/i386/armhf in
Wheezy/Jessie/Stretch/Buster set up on my desktop which work very
well.
The multistrap filesystems are also at the core of the sysroot
docker builders used to produce the Machinekit packages.

regards

  


Does anybody have some advice how to accomplish this? Or
  should I switch to Debian? My main reason to use Arago and
  buildroot is that I need to keep the system as small and fast
  as possible. Stock Debian for BBB boots about 40 seconds and
  it is not acceptable for our application. 


Many thanks  
  
  -- 
  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.


  




-- 
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: Will DE0-Nano image work on a DE10-Nano board?

['schoone...@btinternet.com' via Machinekit]

First thing to check is probably that your dip switches are correctly set.

Seem to recall my DE0 board arrived with them in FPGA programming mode 
positions



On 08/02/2018 05:09, mugginsac wrote:

Thanks Schooner and Michael,

I followed the instructions through the setenv default -a; setenv 
ethaddr ba:d0:4a:9c:4e:ce; saveenv; reset.


Now I get a little farther. Do I need to remove the 'quiet' in 
extlinux.conf following the 'rootwait' so that I can see what is going 
on in the starting kernel?
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.02.07 20:16:46 
=~=~=~=~=~=~=~=~=~=~=~=


U-Boot SPL 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14)
drivers/ddr/altera/sequencer.c: Preparing to start memory calibration
drivers/ddr/altera/sequencer.c: CALIBRATION PASSED
drivers/ddr/altera/sequencer.c: Calibration complete
Trying to boot from MMC1

U-Boot 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14 -0800)

CPU:   Altera SoCFPGA Platform
FPGA:  Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0
BOOT:  SD/MMC Internal Transceiver (3.0V)
   Watchdog enabled
I2C:   ready
DRAM:  1 GiB
MMC:   dwmmc0@ff704000: 0
In:    serial
Out:   serial
Err:   serial
Model: Terasic DE10-Nano
Net:   eth0: ethernet@ff702000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
179 bytes read in 21 ms (7.8 KiB/s)
1:    Linux 4.9.68-socfpga-r3
Retrieving file: /boot/vmlinuz-4.9.68-socfpga-r3
5455176 bytes read in 380 ms (13.7 MiB/s)
append: root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait quiet
Retrieving file: 
/boot/dtbs/4.9.68-socfpga-r3/socfpga_cyclone5_de10_nano.dtb

14997 bytes read in 45 ms (325.2 KiB/s)
## Flattened Device Tree blob at 0200
   Booting using the fdt blob at 0x200
   reserving fdt memory region: addr=0 size=1000
   Loading Device Tree to 03ff9000, end 03fffa94 ... OK

Starting kernel ...

**

U-Boot SPL 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14)
drivers/ddr/altera/sequencer.c: Preparing to start memory calibration
drivers/ddr/altera/sequencer.c: CALIBRATION PASSED
drivers/ddr/altera/sequencer.c: Calibration complete
Trying to boot from MMC1


U-Boot 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14 -0800)

CPU:   Altera SoCFPGA Platform
FPGA:  Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0
BOOT:  SD/MMC Internal Transceiver (3.0V)
   Watchdog enabled
I2C:   ready
DRAM:  1 GiB
MMC:   dwmmc0@ff704000: 0
In:    serial
Out:   serial
Err:   serial
Model: Terasic DE10-Nano
Net:   eth0: ethernet@ff702000
Hit any key to stop autoboot:  2 1 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.


--
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: Will DE0-Nano image work on a DE10-Nano board?

['schoone...@btinternet.com' via Machinekit]

  
  

On 07/02/18 07:03,
  'schoone...@btinternet.com' via Machinekit wrote:


  
  Read the gist that Michael did for the DE0

Specifically here
https://gist.github.com/mhaberler/89a813dc70688e35d8848e8e467a1337

where you will see exactly the same error message you report,
because the MAC address is not set.

  There is a link to it in the blogs.
  You have to set the NIC MAC address etc and then restart
  
  
  On 06/02/2018 23:54, mugginsac wrote:
  
  
I finally got the USB console working under
  stretch. 
  I didn't have the dtb file that it was looking
  (socfpga_cyclone5_de10_nano.dtb) for in the
  boot/dtbs/4.9.68-socfpga-r3/ directory.
  After I fixed that it is either loading the kernel or trying
  to load the kernel. It is getting a crc error and then
  starting over to try and load the kernel.
  
  Any help interpreting what it is telling me would be greatly
  appreciated. The log is below:
  
  =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.02.06 15:47:15
  =~=~=~=~=~=~=~=~=~=~=~=
  
  U-Boot SPL 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14)
  drivers/ddr/altera/sequencer.c: Preparing to start memory
  calibration
  drivers/ddr/altera/sequencer.c: CALIBRATION PASSED
  drivers/ddr/altera/sequencer.c: Calibration complete
  Trying to boot from MMC1
  
  
  U-Boot 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14 -0800)
  
  CPU:   Altera SoCFPGA Platform
  FPGA:  Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0
  BOOT:  SD/MMC Internal Transceiver (3.0V)
     Watchdog enabled
  I2C:   ready
  DRAM:  1 GiB
  MMC:   dwmmc0@ff704000: 0
  *** Warning - bad CRC, using default environment
  
  In:    serial
  Out:   serial
  Err:   serial
  Model: Terasic DE10-Nano
  Net:   
  Error: ethernet@ff702000 address not set.
  No ethernet found.
  Hit any key to stop autoboot:  2 1 0 
  switch to partitions #0, OK
  mmc0 is current device
  Scanning mmc 0:2...
  Found /boot/extlinux/extlinux.conf
  Retrieving file: /boot/extlinux/extlinux.conf
  179 bytes read in 21 ms (7.8 KiB/s)
  1:    Linux 4.9.68-socfpga-r3
  Retrieving file: /boot/vmlinuz-4.9.68-socfpga-r3
  5455176 bytes read in 380 ms (13.7 MiB/s)
  append: root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait quiet
  Retrieving file:
  /boot/dtbs/4.9.68-socfpga-r3/socfpga_cyclone5_de10_nano.dtb
  14997 bytes read in 45 ms (325.2 KiB/s)
  ## Flattened Device Tree blob at 0200
     Booting using the fdt blob at 0x200
     reserving fdt memory region: addr=0 size=1000
     Loading Device Tree to 03ff9000, end 03fffa94 ... OK
  
  Starting kernel ...
  
  
  U-Boot SPL 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14)
  drivers/ddr/altera/sequencer.c: Preparing to start memory
  calibration
  drivers/ddr/altera/sequencer.c: CALIBRATION PASSED
  drivers/ddr/altera/sequencer.c: Calibration complete
  Trying to boot from MMC1
  
  
  U-Boot 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14 -0800)
  
  CPU:   Altera SoCFPGA Platform
  FPGA:  Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0
  BOOT:  SD/MMC Internal Transceiver (3.0V)
     Watchdog enabled
  I2C:   ready
  DRAM:  1 GiB
  MMC:   dwmmc0@ff704000: 0
  *** Warning - bad CRC, using default environment
  
  In:    serial
  Out:   serial
  Err:   serial
  Model: Terasic DE10-Nano
  Net:   
  Error: ethernet@ff702000 address not set.
  No ethernet found.
  Hit any key to stop autoboot:  2 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.
  
  
  -- 
  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.
 

Re: [Machinekit] Re: Will DE0-Nano image work on a DE10-Nano board?

['schoone...@btinternet.com' via Machinekit]

Read the gist that Michael did for the DE0

There is a link to it in the blogs.

You have to set the NIC MAC address etc and then restart


On 06/02/2018 23:54, mugginsac wrote:

I finally got the USB console working under stretch.
I didn't have the dtb file that it was looking 
(socfpga_cyclone5_de10_nano.dtb) for in the 
boot/dtbs/4.9.68-socfpga-r3/ directory.
After I fixed that it is either loading the kernel or trying to load 
the kernel. It is getting a crc error and then starting over to try 
and load the kernel.


Any help interpreting what it is telling me would be greatly 
appreciated. The log is below:


=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2018.02.06 15:47:15 
=~=~=~=~=~=~=~=~=~=~=~=


U-Boot SPL 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14)
drivers/ddr/altera/sequencer.c: Preparing to start memory calibration
drivers/ddr/altera/sequencer.c: CALIBRATION PASSED
drivers/ddr/altera/sequencer.c: Calibration complete
Trying to boot from MMC1


U-Boot 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14 -0800)

CPU:   Altera SoCFPGA Platform
FPGA:  Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0
BOOT:  SD/MMC Internal Transceiver (3.0V)
   Watchdog enabled
I2C:   ready
DRAM:  1 GiB
MMC:   dwmmc0@ff704000: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Terasic DE10-Nano
Net:
Error: ethernet@ff702000 address not set.
No ethernet found.
Hit any key to stop autoboot:  2 1 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
179 bytes read in 21 ms (7.8 KiB/s)
1:    Linux 4.9.68-socfpga-r3
Retrieving file: /boot/vmlinuz-4.9.68-socfpga-r3
5455176 bytes read in 380 ms (13.7 MiB/s)
append: root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait quiet
Retrieving file: 
/boot/dtbs/4.9.68-socfpga-r3/socfpga_cyclone5_de10_nano.dtb

14997 bytes read in 45 ms (325.2 KiB/s)
## Flattened Device Tree blob at 0200
   Booting using the fdt blob at 0x200
   reserving fdt memory region: addr=0 size=1000
   Loading Device Tree to 03ff9000, end 03fffa94 ... OK

Starting kernel ...


U-Boot SPL 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14)
drivers/ddr/altera/sequencer.c: Preparing to start memory calibration
drivers/ddr/altera/sequencer.c: CALIBRATION PASSED
drivers/ddr/altera/sequencer.c: Calibration complete
Trying to boot from MMC1


U-Boot 2018.01-rc1-dirty (Jan 25 2018 - 15:56:14 -0800)

CPU:   Altera SoCFPGA Platform
FPGA:  Altera Cyclone V, SE/A6 or SX/C6 or ST/D6, version 0x0
BOOT:  SD/MMC Internal Transceiver (3.0V)
   Watchdog enabled
I2C:   ready
DRAM:  1 GiB
MMC:   dwmmc0@ff704000: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Model: Terasic DE10-Nano
Net:
Error: ethernet@ff702000 address not set.
No ethernet found.
Hit any key to stop autoboot:  2 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.


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