Re: [Machinekit] Re: Gcode from remote source

2018-04-09 Thread Marius
On Fri, 06 Apr 2018 22:28:37 +0200, Daren Schwenke  
 wrote:


Someone has already done this, but it's kinda old and not the best way.  
OpenPNP doesn't work by transferring files btw... it's a streams  
interface similar to spoon feeding a dumb 3D printer...as the next  
command depends on >the output of previous ones.


Alexander and I have previously discussed a better integration strategy  
but I have not gotten around to implementing any of it.
I had also planned to use Machinekit for this:  
https://hackaday.io/project/45404-arcus-3d-p1-pnp-for-3d-printers

So you are a little early to the party, but it will get going soon.


Thanks Daren, I will keep watching for it



On Friday, April 6, 2018 at 5:02:41 AM UTC-4, Marius Liebenberg wrote:
I would like to use MK on PocketBeagle to drive n solder paste  
applicator. The commands are sent to the controller from OpenPnp via  
Gcode or >>custom messages. I might have to write a custom component to  
connect to OpenPnp


On Thursday, April 5, 2018 at 9:38:13 PM UTC+2, Daren Schwenke wrote:
Depends on what you are running for your USB.  Ethernet, then you are  
good.
There is the old way using halcmd stuff, and the new way using the  
mkwrapper protocol.
The latter is what is used for Machineface and Cetus.  I use  
Machineface for running my machine from my tablet. File transfers are  
built in then.


On Thursday, April 5, 2018 at 10:09:53 AM UTC-4, Marius Liebenberg  
wrote:

Hi
I am planning on using a PocketBeagle for a project that will require  
some Gcode to be sent to the controller via USB. What mechanism is  
provided in MK to do this if any?



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




--
Using Opera's mail client: http://www.opera.com/mail/

--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups "Machinekit" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.


[Machinekit] Re: Compiling Machinekit on BBB

2018-04-09 Thread Jeff Pollard

Hi,

  From one of the previous posts:
=
add a swap file first:

 dd if=/dev/zero of=my_swap bs=1024 count=524288
 mkswap my_swap 
 sudo chown root my_swap 
 sudo chmod 600 my_swap 
 sudo swapon my_swap

  you can make the file permanent by adding a line to fstab

 /path-to-file/my_swap swap swap defaults 0 0
===
Jeff

On Sunday, April 8, 2018 at 11:06:51 AM UTC-7, mahdi@gmail.com wrote:
>
>
> could you please tell me how to  set the swap file properly
>
>
>>
>> On Friday, March 31, 2017 at 1:29:32 PM UTC-7, ceha...@gmail.com wrote:
>>>
>>> I just checked which image I have on my BBB, and it is the 1-30-2017 
>>> release.  My notes had the 3-15-17 release specified, but while that 
>>> compiled, it would not run.  I think the 2-12-17 release works though.  
>>> Sorry for any confusion.
>>>
>>> On Friday, March 31, 2017 at 4:21:42 PM UTC-4, ceha...@gmail.com wrote:


 I've compiled on beaglebone using these steps.  The process runs much 
 faster when running out of EMMC, so I recommend that you flash your SD 
 card 
 image onto the BBB, otherwise it will take hours.

 The swapfile is necessary as you've noted.  My first compile failed in 
 the same way but I had another window open running 'top' which showed all 
 of memory being consumed, and then the crash.  Running 'top' is an easy 
 way 
 to verify that a swap file is being used.

 From my notes:

 Build machinekit on the beaglebone

 Start with this image:

   bone-debian-8.7-machinekit-armhf-2017-03-12-4gb.img.xz
   
   install on an SD card and boot holding the boot button down at 
 power-on
   open a terminal up, and use the following instructions:

 add a swap file first:

  dd if=/dev/zero of=my_swap bs=1024 count=524288
  mkswap my_swap 
  sudo chown root my_swap 
  sudo chmod 600 my_swap 
  sudo swapon my_swap

   you can make the file permanent by adding a line to fstab

  /path-to-file/my_swap swap swap defaults 0 0

 then do this to build machinekit:

 sudo apt-get remove --purge machinekit
 rm -rf machinekit

 sudo apt-get install libczmq-dev python-zmq libjansson-dev pkg-config \
   libwebsockets-dev libxenomai-dev python-pyftpdlib cython bwidget 
 lsb-release

 sudo apt-get install git dpkg-dev
 sudo apt-get install --no-install-recommends devscripts equivs
 git clone https://github.com/machinekit/machinekit.git
 cd machinekit
 # to add RT-PREEMPT support, add a 'r'
 # to add Xenomai support, add an 'x'
 # this builds for Posix, RT-PREEMPT, Xenomai:
 debian/configure -prx
 sudo mk-build-deps -ir
 cd src
 ./autogen.sh
 # for the Beaglebone, add --with-platform-beaglebone to ./configure
 # for the Raspberry2, add --with-platform-raspberry to ./configure
 # for PC platforms, add --with-rt-preempt  --with-posix  --with-xenomai
 ./configure --with-platform-beaglebone

 make   <-- this takes a LONG time

 sudo make setuid

 Hope this helps!


 On Thursday, March 30, 2017 at 7:51:50 PM UTC-4, Jeff Pollard wrote:
>
>
> Hi,
>
>   I'm trying to build machinekit from the 2017-02-12 version.  I've 
> gone through the steps below, and at step 24 I encounter an error while 
> compiling emctask.cc.  I read somewhere that adding a swap space might 
> help, so I tried to add one, and it either didn't help, or I did it 
> wrong.  
> In any case, can anyone tell me if the steps I've taken below are either 
> wrong, or if I'm missing any?
>
> Thanks,
>
> Jeff
> (PS.  I tried to download the most recent Jessie version and when 
> booting the three blue LEDs would light up, and the BBB would freeze, 
> thus 
> I'm using the 02-12 version)
> == 
> on ubuntu
> [1] wget 
> https://rcn-ee.com/rootfs/bb.org/testing/2017-02-12/machinekit/bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz
>
> [2] sha256sum bone-debian-8.7-machinekit-armhf-2017-02-12-4gb*
> 18361e0426715974b5a0e7f014ff1bf26db2421cbf8d61622efd2856cd8c6214  
> bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz
>
> [3] xzcat bone-debian-8.7-machinekit-armhf-2017-02-12-4gb.img.xz | 
> sudo dd of=/dev/sdc
> 
> [4] install uSD in to BBB and boot
> 
> resize 4GB to full 16 GB
> [5] cd /opt/scripts/tools/
> [6] git pull
> [7] sudo ./grow_partition.sh
> [8] sudo reboot
> -
> [9] sudo apt-get remove --purge machinekit
> [10] sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 
> --recv 43DDF224

Re: [Machinekit] Re: DE10-DE0-Nano - Invitation to collaborate

2018-04-09 Thread Michael Brown
Yes you can boot the images without setting the ethernet and hostname 
variables(in u boot),
however things can get a bit messy on your network as the dhcp server will 
issue a new ip address for each reboot/boot.

---

Sure for the console image (this is tested to work on both de0-nano-soc and 
DE10 nano)

I just updated the readme for The Desktop 
image(readme_hdmi-desktop_image.md)

I'm wondering if there is a way to circumvent having to add bash -c to the 
linuxcnc.desktop file (does this work on a pc ?)

I am looking into adding the fpga-load u boot variables in an easier 
fashion, so that the desktop image is just as easy to startup as the 
console one. 

On Monday, 9 April 2018 12:39:55 UTC+2, Schooner wrote:
>
> 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 
>> 
>> [image: Sender's profile photo]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 [image: 
>> Logo for Google Drive]  
>>
> -- 
> 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+...@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

2018-04-09 Thread '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