how they did that ?

https://www.youtube.com/watch?v=D8BLyMryzQ8&t=175s

https://www.youtube.com/watch?v=wOarxQRKW9o

small cube is my.

On Sun, Mar 11, 2018 at 7:42 PM, Gene Heskett <ghesk...@shentel.net> wrote:

> On Sunday 11 March 2018 15:57:59 Chris Albertson wrote:
>
> > On Sun, Mar 11, 2018 at 12:28 PM, a k <pccncmach...@gmail.com> wrote:
> > > I already talk about why I can not use slicing program .
> >
> > I missed.  Maybe you can re-post.
> >
> > > If one can do change to existing slicing software then I am
> > > interesting to talk.
> >
> > Of course software can be changed.   It is just a text file you can
> > edit.   The key is having EXACT testable requirements.  Software
> > projects typically fail when the goal can't be clearly stated.
> >
> >
> > One way to state the problem and a proposed solution is to make a most
> > simple part possible.    If the machine is a 3D printer this simplest
> > part might be to draw one line of plastic one nozzle width wide and 1
> > mm long directly on the base place.  It would be a tiny part 1mm long
> > by 0.4mm wide and 0.2mm tall.  The code file would have about 3 or 4
> > lines after a standard "boiler plate".
> >
> > Don't do exactly that, but if you do start with a very trivial example
> > the entire g-code fits in a short email.
> >
> > The other problem is a procedural.   Each email lacks the context of
> > there discussion few people will remember details for days able if
> > they read 100 emails a day.  For example I'm reading/wrinting about
> > design of a human-like hand and the cost of linear actuators, about
> > ball bearing design and a software project.  and a few other things.
> > I suspect everyone has multiple projects that move slow.
> >
> > Maybe the best thing you can do is explain the machine you have and
> > the problem to be solved and a method for determining of a proposed
> > solution solves the problem.    Perhaps place this on a web page so
> > you don't have to re-write this 100 times.
>
> Along about now also seems to be a good place to explain how free
> software works.
>
> Suppose programer A has an itch, so he writes a piece of code that
> scratches his itch, and is currently makeing 4000 of this itch scratcher
> a day.  His itch has been scratched, but your itch isn't in the same
> place, so while his solution is similar, he'll have to modify that code
> in order to scratch your itch. But he is a working man, and to rewrite
> his code to scratch your itch, he'll have to stop whatever he is doing,
> which is buying his groceries and making the house payments. Generally
> he is going to expect that this missed income will be replaced by
> charging you for the time it takes to do this modification. You are not
> paying for the code, but the coders time. This makes all the difference
> in the GPL world. This modified code is also subject to the GPL in that
> if you pass it on to your brother-in-law, the complete src file kit must
> be made available to anyone who has a copy of the executable that came
> from you.
>
> There are probably 20+ people on this list who could handle this, (and
> I'm not one of them by any means,) but they would want a per diem, all
> expenses paid and in person access to the machine at X dollars, Dinar,
> Sheckles, whatever the local monetary unit is called, per hour while
> they are doing this work if as you claim you aren't able to do it.
>
> Thats rather harshly stated. But its as often as not, how free (GPL)
> software works.
>
> Too often I have observed that there are folks with plenty of smarts, but
> because the code "forest" is not familiar, cannot look and see what its
> doing, and without that, haven't the comprehension to look at the
> existing code and follow what its doing. And reaching that understanding
> will get you to easily seeing a variable that needs changed to get it
> closer to scratching "your" itch.
>
> Often referred to as the TANSTAAFL principle. :)
>
> --
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page <http://geneslinuxbox.net:6309/gene>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Emc-users mailing list
> Emc-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-users
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to