Re: [Machinekit] Happy Birthday Machinekit!

[John Morris]

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: Example Gantry Configs

[Tom M]

Hi Charles,
I'm getting ready to bite the bullet and give up on gantrykins and switch 
over to this method for my dual gantry MPCNC/Cramps setup.

One thing that I'm a little fuzzy on is syncing the limit switches. 
I understand the trick/feature you developed; that both switches need to 
close for the homing cycle to finish and a is the mechanism for  de-racking 
the gantry.

So I'm assuming that the implication to this is that the switches on the 
gantry need to be aligned perfectly.   Is this correct or is there some 
offset compensation built into code that will account for error in the 
switches(that I'm not seeing /understanding)

The reason I'm asking is need make the mounts for the endstops.  If I need 
to take out error using the stops only, I need to create some sort of fine 
alignment feature in end stop mount.

Tom

On Sunday, November 29, 2015 at 2:59:46 PM UTC-6, Bas de Bruijn wrote:
>
> Hi Neo,
>
> On 29 Nov 2015, at 21:31, Neo Phema  
> wrote:
>
> It's very well done. Is the gantry component you wrote beaglebone 
> dependant? 
>
>
> the components that are used in HAL are meant to be the link between 
> software and hardware. Some components are specifically for setting up 
> hardware, most are not. So _you_ can decide the hardware that gets attached 
> to this component. The beaglebone and pins etc are just the hardware part. 
> In the terminal type "man gantry” which should give you the manpage. Or 
> have a look here 
> https://github.com/machinekit/machinekit-docs/blob/master/machinekit-documentation/components/gantry.asciidoc
>
> You might also have a look here:
>
> https://github.com/machinekit/machinekit-docs/blob/master/src/hal/intro.asciidoc
>
> Cheers,
> Bas
>
>
> On Friday, November 27, 2015 at 9:35:55 PM UTC-6, Charles Steinkuehler 
> wrote:
>>
>> Mostly because of all the stuff in the legacy LinuxCNC stack that 
>> breaks when you aren't using trivialkins, and the associated extra 
>> hassle required when using the application.  Switching between 
>> world/joint modes, no coordinated MPG jogging with non-trivialkins, 
>> more complicated (IMHO) homing setup, etc. 
>>
>> A gantry system is basically just a Cartesian machine with duplicated 
>> drive and a modified homing scheme for the paired joints.  Both 
>> gantrykins and my gantry component are essentially hacks to make this 
>> work with LinuxCNC, but using gantrykins comes with a bunch of other 
>> UI fallout I didn't want to deal with.  So I wrote the gantry comp. 
>>
>> One example: 
>> Configure your gantry system to move to the center of the work 
>> envelope (let's say it's 100.0 for example) when finished homing, and 
>> the home switch is at 0.0.  So that means for your gantry joints you'd 
>> set: 
>>
>>   HOME = 0.000 
>>   HOMEOFFSET = 100.000 
>>
>> Now home your gantrykins machine in joint mode and watch as one side 
>> of the gantry rapids from the home switch to the midpoint, while the 
>> other side is still searching for the home latch position.  This is 
>> *NOT* a GoodThing!  The gantry component I wrote handles this case 
>> correctly.  :) 
>>
>> On 11/27/2015 3:52 PM, Neo Phema wrote: 
>> > Charles, just an orientation question. 
>> > 
>> > My study shows trivikins to be less specialized that gantrykins for 
>> this 
>> > type of control. That I might learn, I am interested in what led you to 
>> > choose trivikins.   
>> > 
>> > On Friday, August 15, 2014 at 10:32:46 AM UTC-5, Charles Steinkuehler 
>> wrote: 
>> >> 
>> >> I finally crafted some example configurations for the gantry HAL 
>> >> component I wrote some time ago.  These specific configs are for a 
>> Comet 
>> >> router from Probotix, but should work as a starting point for any 
>> gantry 
>> >> style system that has a homing switch available for each gantry joint 
>> >> (ie: Shapeoko or similar). 
>> >> 
>> >> Video on Youtube: 
>> >> https://www.youtube.com/watch?v=7XhIoDV8Hp8 
>> >> 
>> >> Configs are in a github PR (already merged while I was typing!): 
>> >> https://github.com/machinekit/machinekit/pull/276 
>> >> 
>> >> The relevant portions of the config in the HAL file: 
>> >> 
>> >> Splitting one commanded position into two with the gantry comp: 
>> >> 
>> >> 
>> https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/Probotix/Comet.hal#L54-L62
>>  
>> >> 
>> >> Home/limit switch setup: 
>> >> 
>> >> 
>> https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/Probotix/Comet.hal#L105-L111
>>  
>> >> 
>> >> Holler if there are any questions! 
>> >> 
>> >> -- 
>> >> Charles Steinkuehler 
>> >> 
>> >> 
>> >> 
>> > 
>>
>>
>> -- 
>> Charles Steinkuehler 
>> cha...@steinkuehler.net 
>>
>
> -- 
> 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] Looking for a good example of modern configuration files

[Bas de Bruijn]

Hi,

> On 02 Apr 2017, at 15:09, Brian Schousek wrote:
> 
> From which example should I start if I want to follow current best practices 
> for a new machine config?

there have been some threads on this in the past.
If you search the Google Group there's some more info there.
One of them : https://groups.google.com/forum/m/#!topic/machinekit/UDsLddETO20

Personality I make the configurations these days with python instead of .hal 
files. I use that with Machineface.

> I am putting together a coreXY 3D printer and am using a cheap RAMPS 1.4 for 
> support components/connectors which I eventually intend to wire up CRAMPS 
> style to a Beagle Board.

You could just take a CRAMPS configuration, and use the same pins.

> Initially I have a line on a good technique for pulse generation via DMA on 
> the Raspberry Pi and want to do what I can do to support the experiments in a 
> future-proof way.
> -- 
> 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.