Re: [Machinekit] Home Built Delta Printer With Machinekit Interface, Makerfaire NYC 2016 Exhibit #58459

[Michael Haberler]

Hi John,

> Am 01.09.2016 um 05:15 schrieb John Pickens :
> 
> Now I've gone and done it.  I was accepted as an exhibitor at New York 
> Makerfaire October 1st and 2nd, 2016.
> I have built a Ramps 1.3 Arduino Mega 2560 controlled delta printer based 
> upon the original Johann Rostock build with my own modifications.
> It works rather well, but I bought the makings for a second printer when I 
> got the original stuff, because it was much cheaper for the second
> printer's parts.  I would have spent about $400 for one printer, and the 
> extra parts for the second one cost less than $200 due to savings 
> on quantity and shipping.
> 
> Anyway, I have planned  to build the second printer to improve upon the 
> first, and over the course of the last year or so, the Machinekit
> project for FDM printers caught my eye.  I went and purchased a CRAMPS board 
> and BBB, and now it is time to build.
> 
> I entered as a Makerfaire Exhibitor with the express intention of forcing a 
> deadline on myself to make some serious progress on this project.
> I will be bringing my completed Ramps/Arduino printer to the show, along with 
> the Machinekit/CRAMPS unit in whatever state it is in on 
> September 30.
> 
> SO
> 
> I was hoping that the members of this group could assist me in choosing the 
> path for a Newbie to implement Machinekit on this custom
> Delta printer.
> 
> As I understand it, the current SD card image for the BBB/Cramps 
> Machinkit/Debian is here:
> 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit
> 
> And I should be loading the prebuild SD card image, which at this point is:
> 
> 2016-08-28
> 
> BBW/BBB (All Revs) Machinekit
> 
> microSD/Standalone: (machinekit) Classic
> 
> Get prebuilt image:
> 
> wget: etc..
> 
> My first point of confusion is a thread in this group which says to go here:
> 
> https://github.com/ilaro-org/machinekit/wiki
> 
> Which is a Machinekit fork described as:
> 
> Repository to work with machinekit in a BeagleBone Black with CRAMPS board. 
> It is a fork fromhttps://github.com/machinekit/machinekit and includes 
> additions to work with a linear delta printer and a delta printer with a 
> rotating nozzle plataform for multiple extruders.
> 
> Now this sounds exactly like what I want to do, but I am wary of going to a 
> fork repository rather than the mainline Machinekit project.

first time I hear of this fork

I had a look - the repo is at a state of late May and contains no changes to 
the code base proper but really configs and G-code fragments

> 
> My questions are twofold:
> 
> 1. Which Beaglebone Black/Cramps image should I start with?

I think you will need to get the author involved (hi!) but gut feeling - this 
looks like a stock image plus minor local changes which do not affect the 
actual code base so no rebuild needed 

> 2. If it is best to start with the main Machinekit version, can I combine the 
> ilaro fork's add-ons for Cura Gcode conversion, etc. to the main fork version?

At first glance I'd say there is nothing from keeping you from doing that; 
again I'd suggest to involve the author 

- Michael

> 
> Any guidance would be appreciated.  I only have four weeks to get this puppy 
> up and running for all to see.
> 
> Thanks in advance.
> 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.

-- 
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] Rfid, Mtconnect and Machinkit.

[Tom M]

I think I may have found it... This link looks like it has possibilities.  
Hopefully I can find a little time to look at it this weekend.
https://github.com/mtconnect/cppagent/issues/31

On Wednesday, August 31, 2016 at 12:17:53 PM UTC-5, Tom M wrote:
>
> Not so much an question of if but more of when.   My free time is 
> constrained at the moment and I want to get the mpcnc project done before I 
> hit that.. (if you have the link to the agent implantation handy could you 
> post it.. or I can google it and post it at some point
>
> On Aug 31, 2016 11:37 AM, "John Morris"  wrote:
>
>>
>>
>> On 08/30/2016 10:07 PM, Tom M wrote:
>>
>>>
>>> I plan to use machinekit for our cnc mill at the space.  I was thinking
>>> it would be a fun learning experience to get a MTconnect client going to
>>> get usage metrics
>>>
>>
>> If you get serious about MTConnect, I believe there's an agent 
>> implementation for EMC around somewhere that should be easily dusted off.
>>
>> 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.

[Machinekit] Home Built Delta Printer With Machinekit Interface, Makerfaire NYC 2016 Exhibit #58459

[John Pickens]

Now I've gone and done it.  I was accepted as an exhibitor at New York 
Makerfaire October 1st and 2nd, 2016.
I have built a Ramps 1.3 Arduino Mega 2560 controlled delta printer based 
upon the original Johann Rostock build with my own modifications.
It works rather well, but I bought the makings for a second printer when I 
got the original stuff, because it was much cheaper for the second
printer's parts.  I would have spent about $400 for one printer, and the 
extra parts for the second one cost less than $200 due to savings 
on quantity and shipping.

Anyway, I have planned  to build the second printer to improve upon the 
first, and over the course of the last year or so, the Machinekit
project for FDM printers caught my eye.  I went and purchased a CRAMPS 
board and BBB, and now it is time to build.

I entered as a Makerfaire Exhibitor with the express intention of forcing a 
deadline on myself to make some serious progress on this project.
I will be bringing my completed Ramps/Arduino printer to the show, along 
with the Machinekit/CRAMPS unit in whatever state it is in on 
September 30.

SO

I was hoping that the members of this group could assist me in choosing the 
path for a Newbie to implement Machinekit on this custom
Delta printer.

As I understand it, the current SD card image for the BBB/Cramps 
Machinkit/Debian is here:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit

And I should be loading the prebuild SD card image, which at this point is:

2016-08-28BBW/BBB (All Revs) MachinekitmicroSD/Standalone: (machinekit) 
> Classic
>
> Get prebuilt image:
>
> wget: etc..
>
>
My first point of confusion is a thread in this group which says to go here:

https://github.com/ilaro-org/machinekit/wiki

Which is a Machinekit fork described as:

Repository to work with machinekit in a BeagleBone Black with CRAMPS board. 
> It is a fork fromhttps://github.com/machinekit/machinekit and includes 
> additions to work with a linear delta printer and a delta printer with a 
> rotating nozzle plataform for multiple extruders.


Now this sounds exactly like what I want to do, but I am wary of going to a 
fork repository rather than the mainline Machinekit project.

My questions are twofold:

1. Which Beaglebone Black/Cramps image should I start with?

2. If it is best to start with the main Machinekit version, can I combine 
the ilaro fork's add-ons for Cura Gcode conversion, etc. to the main fork 
version?

Any guidance would be appreciated.  I only have four weeks to get this 
puppy up and running for all to see.

Thanks in advance.
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] How to cross compile machinekit to run on the zedboard?

[Michael Haberler]

> Am 31.08.2016 um 11:46 schrieb yfyf...@gmail.com:
> 
> 
> Dear Michael,
> I am sorry to trouble you. Now I want to run MachineKit on the Zedboard. And 
> the operation system running on the Zedboard is Linux patched the 
> Xenomai2.6.3 or Xenomai3.x.

please state which one as it matters. Please paste the output of dmesg to 
pastebin.com so we can end the guesswork.

> And I have two questions.
> 1, The MachineKit is only an linux's application who will only to call the 
> API from Linux. So why do I need to consider which FPGA or which hardware 
> below the Linux operation system?

you do not have to. You can use the zed gpio driver for a (slow) stepper config.

Again it would help if you explained what you are trying to achieve. If this 
Xenomai kernel thing comes from the EtherCAT master as a requirement: are you 
planning to have the EtherCAT master talk to machinekit? Why do you need any 
local I/O at all then? And how is that going to work? I have never seen any 
interworking with that product.

If EtherCAT is separate from running machinekit, why bother about the kernel at 
all?

>I think that is because  you want to compile a common SD kernel, which can 
> run either on CycloneV or Zynq platforms.

no. These are separate kernels based on separate vendor trees as many of the 
required changes are not Linux mainline yet. Maybe downstream, but certainly 
not under a year from now.

> So you need to use the hostmot2 driver and need to care the hardware.

These kernels (+FPGA manager) enable hostmot2. However you can run machinekit 
like on other platforms with GPIO as well - slow but works. It is an option, 
not a requirement.

> But If I don't use the SD kernel image from you. And I only want to build the 
> MachineKit witch need run on Zedboard with xenomai by myself. 

Why? apt install machinekit and either machinekit-xenomai or 
machinekit-rtpreempt and be done. Likely the zedboard driver works ok for both 
Xenomai2 or RT-PREEMPT.

> What should I do？ Do I should to build the hostmot2 driver?

I am out of my depth to answer that given what I know about your plans. 

> Can you kindly share me some document about how to build the MachineKit in 
> order to run on the Zedboard with xenomai?

it is all on http://www.machinekit.io . 

That said: as long as your plans are very unclear, I advise against "building" 
everything in sight in the hope this will yield great results. Everything you 
need to run Machinekit on a  Xenomai2 or RT-PREEMPT kernel can be had by a 
package install.

> 
> 2, As far as I know, you has build the MachineKit which can run on the 
> Zedboard. But the operation system is Linux patch RT-Preemt. And you have 
> packaged into a SD image.
> So I want to know, do you have the plans to build a SD image for MachineKit 
> on the Linux patch xenomai?

No, as I already explained this makes no sense and therefore will not happen. I 
see no hope for running the hostmot2 code with the on-chip FPGA on either the 
Zynq or Altera platforms with Xenomai2.

> No matter xenomai2.6.3 or xenomai3.x.

It DOES matter which is why I'm asking for the output of 'dmesg' .

> Because it is important for us, we only want to use the OS of  Linux patch 
> xenomai. We don't want to use the RT-Preemt.

Well fine, and there are consequences. In this case this means: no hostmot2 
with on-chip FPGA for Xenomai2.


- Michael

> 
> 在 2016年8月29日星期一 UTC+8下午3:44:51，Michael Haberler写道：
> 
> > Am 29.08.2016 um 09:19 schrieb lf : 
> > 
> > Hello Michael: 
> >   Recently,I am doing some summary and plan on how to start our project. 
> > 
> >   There are some question,i want to ask you to figure out. 
> > 
> >   1.Three words:hostmot2 driver, FPGA manager, mksocfpga.As far as i 
> > know,mksocfpga is a project about machinekit running on FPGA boards.This 
> > project's main module is hostmot2 driver which based on FPGA manager code 
> > makes machinekit running on different FPGA boards. It is means that we 
> > should choose kernels which support FPGA manager first.That is my 
> > understanging and that's correct? 
> 
> The https://github.com/machinekit/mksocfpga/ repository contains the Mesanet 
> hostmot2 VHDL code, and the supplementary IP and configurations to build 
> firmware bitfiles for the CycloneV and Zynq platforms - nothing else. 
> 
> The machinekit hm2_soc_ol HAL driver is the glue layer talking to the FPGA 
> manager to load a bitfile, and to map a portion of the FPGA region 
> (http://freeby.mesanet.com/regmap) into memory so the hostmot2 driver can 
> talk to it. 
> 
> Since the hm2_soc_ol driver expects and FPGA manager API, the latter is a 
> prerequisite, yes. 
> 
> > 
> >   2.As you said "well the KPA website says it runs with RT-PREEMPT kernels 
> > as well, and since Xenomai3 supports multiple flavors you might just as 
> > well check if your kernel isnt RT-PREEMPT under the hood anyway".Actually,I 
> > can't fully understand "since Xenomai3 supports multiple flavors you 

Re: [Machinekit] Rfid, Mtconnect and Machinkit.

[Tom M]

Not so much an question of if but more of when.   My free time is
constrained at the moment and I want to get the mpcnc project done before I
hit that.. (if you have the link to the agent implantation handy could you
post it.. or I can google it and post it at some point

On Aug 31, 2016 11:37 AM, "John Morris"  wrote:

>
>
> On 08/30/2016 10:07 PM, Tom M wrote:
>
>>
>> I plan to use machinekit for our cnc mill at the space.  I was thinking
>> it would be a fun learning experience to get a MTconnect client going to
>> get usage metrics
>>
>
> If you get serious about MTConnect, I believe there's an agent
> implementation for EMC around somewhere that should be easily dusted off.
>
> 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] How to cross compile machinekit to run on the zedboard?

[yfyfly1]

Dear Michael,
I am sorry to trouble you. Now I want to run MachineKit on the Zedboard. 
And the operation system running on the Zedboard is Linux patched the 
Xenomai2.6.3 or Xenomai3.x.
And I have two questions.
1, The MachineKit is only an linux's application who will only to call the 
API from Linux. So why do I need to consider which FPGA or which hardware 
below the Linux operation system?
   I think that is because  you want to compile a common SD kernel, which 
can run either on CycloneV or Zynq platforms. So you need to use the 
hostmot2 driver and need to care the hardware.
But If I don't use the SD kernel image from you. And I only want to build 
the MachineKit witch need run on Zedboard with xenomai by myself. 
What should I do？ Do I should to build the hostmot2 driver?
Can you kindly share me some document about how to build the MachineKit in 
order to run on the Zedboard with xenomai?

2, As far as I know, you has build the MachineKit which can run on the 
Zedboard. But the operation system is Linux patch RT-Preemt. And you have 
packaged into a SD image.
So I want to know, do you have the plans to build a SD image for MachineKit 
on the Linux patch xenomai?
No matter xenomai2.6.3 or xenomai3.x. Because it is important for us, we 
only want to use the OS of  Linux patch xenomai. We don't want to use the 
RT-Preemt.

在 2016年8月29日星期一 UTC+8下午3:44:51，Michael Haberler写道：
>
>
> > Am 29.08.2016 um 09:19 schrieb lf : 
> > 
> > Hello Michael: 
> >   Recently,I am doing some summary and plan on how to start our project. 
> > 
> >   There are some question,i want to ask you to figure out. 
> > 
> >   1.Three words:hostmot2 driver, FPGA manager, mksocfpga.As far as i 
> know,mksocfpga is a project about machinekit running on FPGA boards.This 
> project's main module is hostmot2 driver which based on FPGA manager code 
> makes machinekit running on different FPGA boards. It is means that we 
> should choose kernels which support FPGA manager first.That is my 
> understanging and that's correct? 
>
> The https://github.com/machinekit/mksocfpga/ repository contains the 
> Mesanet hostmot2 VHDL code, and the supplementary IP and configurations to 
> build firmware bitfiles for the CycloneV and Zynq platforms - nothing else. 
>
> The machinekit hm2_soc_ol HAL driver is the glue layer talking to the FPGA 
> manager to load a bitfile, and to map a portion of the FPGA region (
> http://freeby.mesanet.com/regmap) into memory so the hostmot2 driver can 
> talk to it. 
>
> Since the hm2_soc_ol driver expects and FPGA manager API, the latter is a 
> prerequisite, yes. 
>
> > 
> >   2.As you said "well the KPA website says it runs with RT-PREEMPT 
> kernels as well, and since Xenomai3 supports multiple flavors you might 
> just as well check if your kernel isnt RT-PREEMPT under the hood 
> anyway".Actually,I can't fully understand "since Xenomai3 supports multiple 
> flavors you might just as well check if your kernel isn't PT-PREEMPT under 
> the hood anyway".Could it be that Xenomai3 can be patch to RT-PREEMPT 
> kernels? 
>
> The Xenomai3 website explains the options pretty well: 
> https://xenomai.org/introducing-xenomai-3/ 
>
> Xenomai3 is mostly about a common API over two options - either RT-PREEMPT 
> or an ipipe-patched kernel in the style of Xenomai2. Since Machinekit has a 
> Xenomai2 as well as an RT-PREEMPT support layer there is no value a 
> Xenomai3 glue layer would add as there would be no added functionality. 
>
> If you are not sure what your kernel is, consider looking at the boot log: 
>
> Xenomai2 example: 
>
> mah@cancan:~$ dmesg |grep Xenomai 
> [0.701245] I-pipe: head domain Xenomai registered. 
> [0.701280] Xenomai: hal/arm started. 
> [0.702721] Xenomai: scheduling class idle registered. 
> [0.702745] Xenomai: scheduling class rt registered. 
> [0.707480] Xenomai: real-time nucleus v2.6.3 (Lies and Truths) loaded. 
> [0.707491] Xenomai: debug mode enabled. 
> [0.707944] Xenomai: starting native API services. 
> [0.707957] Xenomai: starting POSIX services. 
> [0.708160] Xenomai: starting RTDM services. 
>
> This is typical for a Xenomai-2 type kernel (I-pipe: line). 
>
> For determining if a kernel is RT-PREEMPT, look at the config: 
>
> root@mksocfpga:/boot# grep PREEMPT config-4.1.22-ltsi-rt23-ge3c1da3 
> CONFIG_PREEMPT_RCU=y 
> CONFIG_PREEMPT=y 
> CONFIG_PREEMPT_RT_BASE=y 
> CONFIG_HAVE_PREEMPT_LAZY=y 
> CONFIG_PREEMPT_LAZY=y 
> # CONFIG_PREEMPT_NONE is not set 
> # CONFIG_PREEMPT_VOLUNTARY is not set 
> # CONFIG_PREEMPT__LL is not set 
> # CONFIG_PREEMPT_RTB is not set 
> CONFIG_PREEMPT_RT_FULL=y   < this must be 
> present 
> CONFIG_PREEMPT_COUNT=y 
> CONFIG_DEBUG_PREEMPT=y 
> # CONFIG_PREEMPT_TRACER is not set 
>
> For a quick check, you can look at the contents of /sys/kernel/realtime - 
> if it exists and its content is '1', it is an RT-PREEMPT kernel. 
>
> The way machinekit detects a kernel at