Re: [CAD_CAM_EDM_DRO] Re: Ref: PC to controller comunication protocols
Posted by
Brian Foley
on 2008-03-01 18:47:49 UTC
Hi, Mr clickit, here is what i would suggest, instead of trying to make
another controller, perhaps write plug-ins for say Mach3 to do some of the
textile /sewing machine work......adapting to g-code would bring more
systems to g-code....even g-code isnt universal.....but it is getting
better......i will use this example;
if i wrote microsoft ware, i would have used semi colon instead of colon for
hyper text protocall, and instead of names with underscore it would be a
dash, this would save a lot of shifted typing, same with files, semi colon
instead of colon............
not having a limit on ram size used by the softwear!
move the forward slash to a better position on the keyboard......
if i re-wrote g-code all the radius and circle stuff would have been a sub
routine style operation, the computer figguring out the math.....however it
isnt the way it happened. i think it was made so only specialists would be
profficient writing g-code..
guys like Art Fenerty and many others have broken this stuff down so the
average guy can write code, use the menu and make chips with machines they
built!!!!!!
And not be a programmer/machinist/electronics major to build and run a
machine......the music folks would prefer "Midi" style programming for code
and operation of a machine?
i could write all day, the idea here is make a particular piece of code do
more things, rather than start another code....it looks easy but even Art
will tell you "your playing with a can of worms" looks simple, ends up being
very complicated.....
IMHO, cul brian f.
www.genapro.com
another controller, perhaps write plug-ins for say Mach3 to do some of the
textile /sewing machine work......adapting to g-code would bring more
systems to g-code....even g-code isnt universal.....but it is getting
better......i will use this example;
if i wrote microsoft ware, i would have used semi colon instead of colon for
hyper text protocall, and instead of names with underscore it would be a
dash, this would save a lot of shifted typing, same with files, semi colon
instead of colon............
not having a limit on ram size used by the softwear!
move the forward slash to a better position on the keyboard......
if i re-wrote g-code all the radius and circle stuff would have been a sub
routine style operation, the computer figguring out the math.....however it
isnt the way it happened. i think it was made so only specialists would be
profficient writing g-code..
guys like Art Fenerty and many others have broken this stuff down so the
average guy can write code, use the menu and make chips with machines they
built!!!!!!
And not be a programmer/machinist/electronics major to build and run a
machine......the music folks would prefer "Midi" style programming for code
and operation of a machine?
i could write all day, the idea here is make a particular piece of code do
more things, rather than start another code....it looks easy but even Art
will tell you "your playing with a can of worms" looks simple, ends up being
very complicated.....
IMHO, cul brian f.
www.genapro.com
----- Original Message -----
From: "mrclicit" <chris@...>
To: <CAD_CAM_EDM_DRO@yahoogroups.com>
Sent: Saturday, March 01, 2008 11:51 AM
Subject: [CAD_CAM_EDM_DRO] Re: Ref: PC to controller comunication protocols
> > The number of folks putting together controller software is
> impressive.
>
> Well, here's another.
> I have built a windows app with a nice gui that allows loading dxf
> output directly, displaying the toolpath, allowing a few simple
> adjustments,such a mirroring and offsets, then launches it to a
> microcontroller on my stepper driven 2 1/2 axis machine.
>
> I started going further, such as bresenham and ellipses, but then i
> asked - "would anyone want such a system?" i have started working with
> Inventor 2008, and realized the import of a full 3rd axis and the
> ability to read whatever filetype it will export, and the whole project
> continued to grow in my mind.
>
> Now i see so many on this list are working on similar projects, that I
> am not sure if I'll continue. What i would appreciate knowing is if
> anyone thinks the idea of skipping the g-code altogether might have
> been a good idea.....It seems to me that textiles and garments are cut
> everyday on commercially produced machines that do not rely on any
> single standard - has anyone worked with OptiTex software, for example?
>
> As for microcontrollers, there's a number of pic 18's that will handle
> all the line and curve calculations. It really shouldn't matter how
> it's written - I've done much larger projects based on PIC 18's in
> assembly, C, and basic....yes, basic - there are many ways to not need
> to rely on floating point and to crunch a fair number of decimal places
> even in picbasic.
>
> So, should I continue with my project? What is the collective view?
>
>
>
>
>
> Addresses:
> FAQ: http://www.ktmarketing.com/faq.html
> FILES: http://groups.yahoo.com/group/CAD_CAM_EDM_DRO/files/
> Post Messages: CAD_CAM_EDM_DRO@yahoogroups.com
>
> Subscribe: CAD_CAM_EDM_DRO-subscribe@yahoogroups.com
> Unsubscribe: CAD_CAM_EDM_DRO-unsubscribe@yahoogroups.com
> List owner: CAD_CAM_EDM_DRO-owner@yahoogroups.com, wanliker@...,
timg@...
> Moderator: pentam@... indigo_red@... davemucha@...
[Moderators]
> URL to this group: http://groups.yahoo.com/group/CAD_CAM_EDM_DRO
>
> OFF Topic POSTS: General Machining
> If you wish to post on unlimited OT subjects goto:
aol://5863:126/rec.crafts.metalworking or go thru Google.com to reach it if
you have trouble.
> http://www.metalworking.com/news_servers.html
>
> http://groups.yahoo.com/group/jobshophomeshop I consider this to be a
sister site to the CCED group, as many of the same members are there, for OT
subjects, that are not allowed on the CCED list.
>
> NOTICE: ALL POSTINGS TO THIS GROUP BECOME PUBLIC DOMAIN BY POSTING THEM.
DON'T POST IF YOU CAN NOT ACCEPT THIS.....NO EXCEPTIONS........
> bill
> List Mom
> List Owner
>
>
> Yahoo! Groups Links
>
>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.516 / Virus Database: 269.21.2/1305 - Release Date: 2/29/2008
6:32 PM
>
>
Discussion Thread
dandumit
2008-02-26 04:43:43 UTC
Cutting helical gear - req for info
Michael Fagan
2008-02-26 06:44:58 UTC
Re: [CAD_CAM_EDM_DRO] Cutting helical gear - req for info
stan
2008-02-26 06:52:14 UTC
PC to controller comunication protocols
Philip Burman
2008-02-26 11:08:41 UTC
Re: Cutting helical gear - req for info
dgoadby
2008-02-27 05:54:43 UTC
Re: PC to controller comunication protocols
Yahoo
2008-02-27 07:51:43 UTC
Re: PC to controller comunication protocols
stan
2008-02-27 08:52:00 UTC
ref: PC to controller comunication protocols
Doug Chartier
2008-02-27 09:02:36 UTC
Re: Cutting helical gear - req for info
Alan KM6VV
2008-02-27 09:59:07 UTC
Re: [CAD_CAM_EDM_DRO] Re: PC to controller comunication protocols
jcc3inc
2008-02-28 09:34:31 UTC
Re: PC to controller comunication protocols
stan
2008-02-28 10:00:06 UTC
Ref: PC to controller comunication protocols
Yahoo
2008-02-28 12:43:04 UTC
Re: PC to controller comunication protocols
Yahoo
2008-02-28 12:45:10 UTC
Re: PC to controller comunication protocols
Alan KM6VV
2008-02-28 15:22:28 UTC
Re: [CAD_CAM_EDM_DRO] Re: PC to controller comunication protocols
stan
2008-02-28 17:38:05 UTC
Ref: PC to controller comunication protocols
mrclicit
2008-03-01 08:51:43 UTC
Re: Ref: PC to controller comunication protocols
Alan KM6VV
2008-03-01 09:19:50 UTC
Re: [CAD_CAM_EDM_DRO] Re: Ref: PC to controller comunication protocols
stan
2008-03-01 09:31:51 UTC
Ref: PC to controller comunication protocols
Mike Pogue
2008-03-01 13:25:46 UTC
Re: [CAD_CAM_EDM_DRO] Re: Ref: PC to controller comunication protocols
stan
2008-03-01 14:10:47 UTC
Ref: PC to controller comunication protocols
stan
2008-03-01 15:46:36 UTC
Ref: PC to controller comunication protocols
Brian Foley
2008-03-01 18:47:49 UTC
Re: [CAD_CAM_EDM_DRO] Re: Ref: PC to controller comunication protocols