going metric only?

45 views
Skip to first unread message

jet

unread,
Oct 19, 2012, 11:34:31 AM10/19/12
to lase...@googlegroups.com
I'm trying to debug some failures we're having over at CMU on large
cuts. I've added ifdefs for each sensor and have narrowed it down to
power issues possibly interfering with cuts.

While going through the code I'm also doing some performance cleanups,
like removing support for Z movement and noticed that there are some
unneeded checks for inches/metric. The browser code that NORTD is
pushing only generates metric and I've yet to work with a g-code
generation system that doesn't let you pick the output dimensions.

Any reason to keep the support for inches? If so, I can do more than
"take it out", I can change the processing so fewer "is is metric" tests
are done during processing.



--
J. Eric Townsend, IDSA
design <http://www.allartburns.org>
hacking <http://www.flatline.net>
fabrication <watch this space>

Stefan Hechenberger

unread,
Oct 19, 2012, 3:27:34 PM10/19/12
to lase...@googlegroups.com

hey jet, I agree that support for imperial units can be removed from the
firmware. Most people who interact on the g-code level will have no
problem using metric units. Unit conversion should be done in the
gcode-generating app.

On the other hand, I have no inclination to remove z-control. We want to
support mods with z-table and also leave the possibility open to have a
Plasmasaur running with the same controller/software stack. Also the
upcoming DriveBoard is z-axis-ready.

If the power issue debugging reveals anything that is pertinent to
others keep us posted.

Best,

--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

Paul Graham

unread,
Oct 19, 2012, 4:06:41 PM10/19/12
to lase...@googlegroups.com
I am very intrigued by the "Plasmasaur" - where is the devel on this?
--
Paul Graham

Chief Engineer & cable puller¦ Alpine Engineering ¦  248-274-0177 -  519-488-0362

Check out my Hacking Space Project! OpenLuna.org - "Because we've waited long enough!"
Your Moon, Your Mission, Get involved! http://www.openluna.org

Stefan Hechenberger

unread,
Oct 19, 2012, 4:40:40 PM10/19/12
to lase...@googlegroups.com

Plasmasaur devel stage: "we would like to have one"

The LasaurApp/DriveBoard stack could quite easily be used for plasma
cutting as well. The requirements are very similar. For this reason we
have this illusive machine in mind when we make design decisions.

If you are interested in pushing in that direction feel free to start a
discussion about a LasaurApp/DriveBoard-powered plasma cutter. This may
very well expedite things.


--
Stefan Hechenberger
studio: Nortd Labs - labs.nortd.com
resident: F.A.T. Lab - fffff.at
project: Lasersaur - labs.nortd.com/lasersaur

On 10/19/12 10:06 PM, Paul Graham wrote:
> I am very intrigued by the "Plasmasaur" - where is the devel on this?
>
> On Fri, Oct 19, 2012 at 3:27 PM, Stefan Hechenberger <ste...@nortd.com
> <mailto:ste...@nortd.com>> wrote:
>
>
> hey jet, I agree that support for imperial units can be removed from
> the firmware. Most people who interact on the g-code level will have
> no problem using metric units. Unit conversion should be done in the
> gcode-generating app.
>
> On the other hand, I have no inclination to remove z-control. We
> want to support mods with z-table and also leave the possibility
> open to have a Plasmasaur running with the same controller/software
> stack. Also the upcoming DriveBoard is z-axis-ready.
>
> If the power issue debugging reveals anything that is pertinent to
> others keep us posted.
>
> Best,
>
> --
> Stefan Hechenberger
> studio: Nortd Labs - labs.nortd.com <http://labs.nortd.com>
> resident: F.A.T. Lab - fffff.at <http://fffff.at>
> project: Lasersaur - labs.nortd.com/lasersaur
> <http://labs.nortd.com/lasersaur>
Reply all
Reply to author
Forward
0 new messages