So, you're going to be at NAMES this year? Carol and I will most likely
drive up for at least a day. Perhaps we'll see you there!

-- Carol & Jerry Jankura
    Strongsville, Ohio
    So many toys, so little time....

Another question - when you compile, are you doing anything special? When I
compile the program, it works, but my EXE file is somewhat smaller than
yours (mine's around 122 Kbytes)


|  However, I'll consult Borland's legal dept just to be sure about
|that, as one project on the table is a CD version of TurboCNC that I
|can peddle at NAMES coming up this April.

Alan, (& list)

   I've uploaded instructions to the Files section on getting the
French TP7 compiler from Borland and compiling our favorite CNC
program.

   Since it's been "free download" for about 3 years now, I don't
think there'd be much problem with a freeware CD distribution for the
French compiler so long as no charge was made for the disk and the
usual disclaimers, including not asking them for support, were
prominently attached.

   However, I'll consult Borland's legal dept just to be sure about
that, as one project on the table is a CD version of TurboCNC that I
can peddle at NAMES coming up this April.

   Including the compiler, source code, numerous "canned" programs and
so on would be pretty neat, I would think.

Dave Kowalczyk
Everett WA
PS:  Thanks for the ini upgrade Jerry.  My hat's off to the
professional programmers in our group.

--- In turbocnc@y..., Alan Marconett KM6VV <KM6VV@a...> wrote:
{snip}
>
> I had an Idea, what if the "freeware" Pascal compiler needed to
build
> TurboCNC was put on a CD?   ;>)
>
> Alan  KM6VV
>
{snip}

Hi, Alan:

I don't know what Borland would think of this idea. Although they have it
available in their "French" museum, I don't think that they gave up rights
to it!

|I had an Idea, what if the "freeware" Pascal compiler needed to build
|TurboCNC was put on a CD?   ;>)
|
|Alan  KM6VV

Hi Jed,

Boston!  OK.  Nice seafood!  I'd recommend that you check out Vector
CAD/CAM, instead of Bobcad!

Thanks for the uploaded file.

The PCB's seem to be working for you, I've been wanting to make a board
for a while.  I'll soon have a small project to test it on!

MaxNC DOES have a different executable for the step/dir.  Looks EXACTLY
the same, but probably does a conditional compile to use a different
motor driver, IMO (like I do).  I'll be trying it shortly after I get
the driver/PS boxes finished up, and the motors swapped out.  I was
hopping to get a new Sherline mill to complement/replace my old
Sears/Sherline mill for Christmas, but it didn't happen.  I am playing
with the MaxNC digitizer, and hope to get MY code working for it.  I
have been running the "motion control kit" up to now, which is similar
to the MaxNC 10, I'm told.

Tool comp is a nice idea, but difficult to implement, IMO.  But then, I
haven't got the backlash figured out yet.  Using Vector CAD/CAM, I just
do the offset toolpaths, and run the controller straight (never even
tried it in MaxNC).  I'm told that tool LENGTH 'tho, is simple to do.
(just read about the G53 or something doing that...).

I had an Idea, what if the "freeware" Pascal compiler needed to build
TurboCNC was put on a CD?   ;>)

Alan  KM6VV

nf1z wrote:
> <SNIP>
>
> Well, this is a lot more about the MAXNC than TurboCNC, I'm afraid I
> got carried away.  What I should have simply said was that I have
> built  a set of step+direction drivers for more powerful steppers that
> I got on eBay, that I am going to put on the MAXNC and use TurboCNC to
> drive them.  It's a relatively cheap fix, if you do the 'lectronics
> yourself, but it chews up a lot of time.  The issue now is that the
> original MAXNC driver program does not output step/direction, and I
> don't want to pay $125 for the step/direction version they sell, given
> the problems it has (see above).  I also wanted to get away from the
> direct winding driving of the MAXNC.  I guess there may be a way to
> configure it to do step/direction (I doubt MAXNC has two different
> executables), but I have not been able to crack the config file
> format.  That is why I was trying out all the CNC driver software, and
> landed on TurboCNC.  Even without the cost considerations, I think I
> would have picked it for its stability.  Dave has done a great job.
>
> <SNIP>
>
> The only qualm I had about TurboCNC was that the G-codes were quite
> different from the MAXNC (they are now much closer in the latest
> version).  That's not really a problem until you want to generate code
> from CAD files.  I already had MAXNC tools, so it would have been
> easier to keep on using them.  I guess I could have written a filter
> program easily enough, but I came to the conclusion that it would be
> for the best to ditch the MAXNC tools anyway, and get something a
> little better now I knew more about what I needed.  As I said earlier,
> I'm thinking about BOBCAD (the $200 version), since the demo and the
> docs are pretty impressive.  I haven't yet used it for real, so I'd
> appreciate any comments from users, particularly on the ease of
> generating G-code for TurboCNC.  I understand from the sales guy that
> it will do it, but it would be nice to get other views.
>
> <SNIP>
>
> I do like the new TurboCNC version 3.00g+.  A lot of the missing
> features have been provided, saving me the trouble of dusting off my
> Pascal books. Incidentally, how is Turbo 7 with regard to adding in
> object modules from other languages?  I haven't used it since 2.0, I
> think. Personally, I'd rather use C (not C++) these days, but it
> wouldn't be a good idea if all the rest is in Pascal.  The main use
> might be to steal stuff from EMC without having to translate it to
> Pascal first.  Incidentally, I saw something on another group about
> TurboPascal 7 and TurboCNC, but I missed the start of the thread.  Is
> TP7 a current supported product, or what?
>
> With any luck, this group might accelerate the adding of more
> features.  If anyone is looking for something to do, the feature I'd
> like to see is tool diameter offset compensation.  The MAXNC has it.
> Actually, tool RADIUS compensation, which has caused me more than one
> mistake.  I found it very useful, even indispensible. I may not
> completely understand all sides of the issue, but it would seem to me
> that without compensation, you have to go all the way back to the CAD
> drawing to change tool sizes - a strange thing indeed. Maybe I am
> wrong about that.
>
> --Jed Weare, NF1Z
>
> PS: Alan, KM6VV, my QTH is 20 miles W of Boston (responding to your
> question of about 6 months ago - sorry for the delay ;-)

--- In turbocnc@y..., turbocnc@y... wrote:
>
<snip>
>
>   File        : /G code summary, ver 300G.doc
>   Uploaded by : nf1z <gweare@m...>
>   Description : TurboCNC Codes quick ref
>
<snip>

Hi guys. Great idea, this group.  I saw someone request a command
reference, and it just so happens I threw the uploaded file together a
few days ago to help me transition to TurboCNC, so maybe it will help.
  I see Dave has already uploaded a section from his text document that
describes the codes.  Dave's docs are very good, at least as good as
any I've seen so far, but I thought I needed a small, handy, easy to
read, quick ref chart that I could pin to the wall to remind me of
what codes did what, etc..

A few remarks.  It is in Word 2000 format, but I can respond to
suggestions for different formats for those without Word.  Secondly,
there are a few of the "comments" that apply only to my setup, mainly
in regard to what M codes control what devices.  Feel free to edit as
you like.  Thirdly, I would not bet $1M on the completeness or
accuracy of the table, given I am new to the program and that I threw
it together in a hurry, so please feed back any errors (or suggestions
for improvements) and I can fix it.  Fourthly, my parameter notation
is possibly opaque to many people, but *I* understand it, and I
couldn't think of anything better...

While I am doing this, let me just tell you where I am coming from.  I
am a newcomer to CNC, though a (mostly home but some professional)
machinist since 1963 or so - though often equipmentless.  A year or so
ago, I bought a MAXNC 10 after much research based on little
knowledge.  As you can probably guess from the lack of knowledge,
price was about the greatest factor.  I wanted it to do some fairly
simple stuff, such as parts for steam engines, PCB routing and so on.
  It does a lot of what I need to do, but some of what I need it cannot
seem to do, so I cannot say I'm 100% pleased with the MAXNC - or
rather with my decision to buy it.

To be more specific:  I am completely happy with the amount it has
taught me about CNC, and I love it for PCB routing.  I can design a
PCB in a CAD program, so I don't need to mess with ferric chloride,
tape or photographic stuff, and it is entirely repeatable.  With a
carbide endmill of .020, which is not that small, I can make traces of
.030 with no effort, or danger of eliminating the trace altogether.  I
bet I could even, if I try, get traces between IC pins.  I can also
register front and back of a double-side board within .001 easily,
which is a royal pain with the etch-and-pray method; I have
hand-etched DS boards before now, but they were low grade.  CNC is the
way to go for the home enthusiast.  Not forgetting the ability to see
both sides of the board at once that you get with the CAD program.

BTW, I currently use AutoDesk's QuickCAD, mainly for cost reasons.  I
also used Visio a bit (because I had it) but I didn't like it.
QuickCad is nice, especially the price.  I think I paid about $50-$60
for it.  It's only 2D, and doesn't have a lot of CAM capabilities, but
it does most of what I want.  I am looking into getting BOBCAD for
$200 or so - it had some really nice CAM features and it is relatively
cheap.  Incidentally, I can't believe what some of these guys think
they can charge for low-end software!  It's a bit bizzarre when the
CAD program costs more than the CNC machine, IMHO.  I'm also appalled
at the quality of some of this stuff.  I tried a dozen or so driver
and/or CAD-CAM packages, and most of them were unusable.  Some would
even lock up the PC, which is inexcusable for ANY product.  Of
course, it may not be the SW, but the OS...

To return to the MAXNC:  I did quite a few nice parts in brass, Al,
CRS and even 304 stainless, and the machine held up pretty well, even
in stainless.  I did manage to kill quite a few endmills, though.  At
least I now have a lifetime supply of 1/8" carbide boring bar bits.  I
also had some SW problems, such as having to manually add code to the
output of the drilling G-code generator, since it does not generate
runnable code.  It aborts at every tool change because it does not
turn off the previous tool height compensation.  Then again, it
doesn't put in the tool change M codes, either.  I suppose the SW test
procedure was to see if there were any compiler errors.  Another one
was putting on tool diameter offset in the wrong direction -
sometimes.  There is a manual fix for it, but why should we have to do
that?  Also, the documentation really is worse than useless, I won't
get into that now.

Things came to a halt when I tried to make some small parts from 1/8"
O-1 oil-hardening tool steel.  I haven't found O-1 especially hard to
deal with before, but the MAXNC wouldn't have anything to do with it.
My tool breakage rate was getting so high there was no way I could
afford the parts I was making. After a lot of analysis, my conclusion
was that the two major problems were self-loosening of the slide gibs
if there were any sign of vibration at all - which of course makes
itself worse exponentially.  That can be patched up a bit by putting
in locking screws on top of the slide setting screws; it's tricky to
adjust but can be done.  Methinks they should have put locking nuts on
the screws at the factory, or at least some loctite "stiffener".  But
the worst problem was that the steppers on the MAXNC 10 are not
powerful enough to move the Z slide up, if you tighten it enough to
prevent the slide moving under gravity and the downward pull of the
end mill after the motor has moved it down to cutting position.  If
you don't tighten the slide ( I hate tight slides), the slide will
move down below the set cut height by the Z backlash amount and grab
and probably break, if carbide.  At least the finish will be poor due
to the lack of rigidity.  This naturally shows up more with tougher
materials, since the cut will tend to pull the end mill down more
strongly.

To prevent this, you can eliminate the backlash, or you can tighten
the slide and put bigger motors in.  There is a split brass (!) nut in
the Z slide that can be squeezed - but it works slack again almost
immediately.  Putting in the zero backlash option is a factory job
(they say) and expensive.  You can upgrade to the MAXNC 10-2 with
larger motors, but that is a lot of money too, even if you trade in
the small motors, since you need a new drive electronic module also.
Of course it is nice they have an trade-in upgrade (fix?) path, but I
sure wouldn't have bought the '10 if I'd known more.  Whose fault?
Mine probably, though I could be tempted to argue the position that
they shouldn't be selling inadequate machines at all....

Well, this is a lot more about the MAXNC than TurboCNC, I'm afraid I
got carried away.  What I should have simply said was that I have
built  a set of step+direction drivers for more powerful steppers that
I got on eBay, that I am going to put on the MAXNC and use TurboCNC to
drive them.  It's a relatively cheap fix, if you do the 'lectronics
yourself, but it chews up a lot of time.  The issue now is that the
original MAXNC driver program does not output step/direction, and I
don't want to pay $125 for the step/direction version they sell, given
the problems it has (see above).  I also wanted to get away from the
direct winding driving of the MAXNC.  I guess there may be a way to
configure it to do step/direction (I doubt MAXNC has two different
executables), but I have not been able to crack the config file
format.  That is why I was trying out all the CNC driver software, and
landed on TurboCNC.  Even without the cost considerations, I think I
would have picked it for its stability.  Dave has done a great job.

The only qualm I had about TurboCNC was that the G-codes were quite
different from the MAXNC (they are now much closer in the latest
version).  That's not really a problem until you want to generate code
from CAD files.  I already had MAXNC tools, so it would have been
easier to keep on using them.  I guess I could have written a filter
program easily enough, but I came to the conclusion that it would be
for the best to ditch the MAXNC tools anyway, and get something a
little better now I knew more about what I needed.  As I said earlier,
I'm thinking about BOBCAD (the $200 version), since the demo and the
docs are pretty impressive.  I haven't yet used it for real, so I'd
appreciate any comments from users, particularly on the ease of
generating G-code for TurboCNC.  I understand from the sales guy that
it will do it, but it would be nice to get other views.

For the future, I expect to get the MAXNC finished pretty soon, and
will be making some O-1 chips for a while (with any luck).  The only
largish task left is a motor speed controller that can be controlled
from TurboCNC, and has a speed regulator.  I've convinced myself these
are essential.  I may even add the hardware for software control of
speed (given there is now a hook in TurboCNC), but it isn't currently
planned.  Mainly because the current design is a single chip HW
solution, and I would probably go to an MPU if I added speed control.
  Further down the road, I have a Millrite that needs to be CNC'd.  I
originally planned to use the same driver HW (and SW) as for the
MAXNC, so I designed them with dual L298s for 3.5 - 4.0A per phase for
the bigger steppers that I will need.  However, I got the proverbial
good deal on some commercial drives on eBay, so I will probably use
those instead.  That will be interesting because the drives have
built-in indexers, encoder interfaces, and a serial command/config
interface, so some new code for TurboCNC may result.

I do like the new TurboCNC version 3.00g+.  A lot of the missing
features have been provided, saving me the trouble of dusting off my
Pascal books. Incidentally, how is Turbo 7 with regard to adding in
object modules from other languages?  I haven't used it since 2.0, I
think. Personally, I'd rather use C (not C++) these days, but it
wouldn't be a good idea if all the rest is in Pascal.  The main use
might be to steal stuff from EMC without having to translate it to
Pascal first.  Incidentally, I saw something on another group about
TurboPascal 7 and TurboCNC, but I missed the start of the thread.  Is
TP7 a current supported product, or what?

With any luck, this group might accelerate the adding of more
features.  If anyone is looking for something to do, the feature I'd
like to see is tool diameter offset compensation.  The MAXNC has it.
Actually, tool RADIUS compensation, which has caused me more than one
mistake.  I found it very useful, even indispensible. I may not
completely understand all sides of the issue, but it would seem to me
that without compensation, you have to go all the way back to the CAD
drawing to change tool sizes - a strange thing indeed. Maybe I am
wrong about that.

Anyway, apologies for the "Gone with the Wind" length of this.
Hopefully, since the group is new I can be excused on the grounds of
everyone getting introduced.  In any case, TurboCNC is a great job by
Dave, this group is a great idea, and I hope it prospers.

--Jed Weare, NF1Z

PS: Alan, KM6VV, my QTH is 20 miles W of Boston (responding to your
question of about 6 months ago - sorry for the delay ;-)

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the turbocnc
group.

   File        : /G code summary, ver 300G.doc
   Uploaded by : nf1z <gweare@...>
   Description : TurboCNC Codes quick ref

You can access this file at the URL

http://groups.yahoo.com/group/turbocnc/files/G%20code%20summary%2C%20ver%20300G.\
doc

To learn more about file sharing for your group, please visit

http://help.yahoo.com/help/us/groups/files

Regards,

nf1z <gweare@...>

I downloaded the source for TurboCNC G+ and modified the INI.PAS file to
search the directory in which the TurboCNC application is located.

1. Change the variable declaration of IFile : String[14]; to IFile : String;
to provide a string large enough to hole a complete file name.

2. Add variables

AppPath : DirStr;
AppName : NameStr;
AppExt : ExtStr;

These variables hold the parsed filename portions.

3. In the initialization code at the bottom of the unit, you'll find three
comment lines

{Check for command line parameter for ini file}
{Generalize this for language and menu mode switches later}
{If multiple ini files are called out, last will be used}

Beneath these lines, add the line that splits Paramstr(0) into its component
parts. Paramstr(0) holds the fully qualified name of the executable.

FSplit(Paramstr(0), AppPath, AppName, AppExt);

Next, replace the line "Ifile := 'turbocnc.ini';" with

IFile := AppPath + AppName + '.INI';

Then, go a few lines lower and find the statement

IFile := ParamStr(n);

And replace it with

Ifile := AppPath + ParamStr(n);

Note that, if you make this modification, the program will look for an INI
file having the same name as the primary name of the executable. So, if you
rename the executable from TurboCNC.EXE to CNC.EXE, it will then look for
CNC.INI and not TurboCNC.ini unless you specify TurboCNC.INI on the command
line.

Hope this helps out.

-- Carol & Jerry Jankura
    Strongsville, Ohio
    So many toys, so little time....

|For point 2 - The DOS's that I tested 3g+ with (6.22, 7) correctly
|found the default ini file if it was in the same directory as the
|executable.  If I understand your comment, you are saying that this
|is not the case with yours?

I'm running Novell DOS-7 (DR-DOS) and it didn't find it unless I was in the
same directory as TurboCNC. Unless you've got code in the program to look
for the directory, there's no way for TurboCNC to know which directory it is
executing from. I'll look again since the new code is now available.

|Source code for 3g+ should be in the, er, "usual spot" as of this
|writing.

Jerry,

   Thank you for the suggestions.  Just some quick comments since you
addressed this to me:

For point 2 - The DOS's that I tested 3g+ with (6.22, 7) correctly
found the default ini file if it was in the same directory as the
executable.  If I understand your comment, you are saying that this
is not the case with yours?

For point 4 - One user I'm aware of gets this accomplished by
programming cuts as G00 rapids and adjusting the max speed to the
cutting parameters.  Your suggestion is still a good one of course.

Source code for 3g+ should be in the, er, "usual spot" as of this
writing.

Dave Kowalczyk
Everett WA

--- In turbocnc@y..., "Carol & Jerry Jankura" <jerry.jankura@s...>
wrote:
> Hi, Dave:
>
> Great idea to set up this list.
>
> I started playing with RelG+ and have some comments regarding the
additional
> INI files:
>
> 1. The string used to hold the ini file name should be larger than
12 chars
> to allow a drive and directory chain to be specified.
> 2. At least for the "default" TurboCNC.INI file, you ought to use
> Paramstr[0] to find the directory from which TurboCNC is executing
and look
> to that subdirectory for the INI file.
> 3. It would be nice to provide a separate subdidrectory for CNC
files. These
> really ought to be kept out of the TurboCNC directory. Use the
INIFile to
> specify the CNC directory.
> 4. It would be nice if default feed rates, etc. were stored within
the INI
> file instead of hard code. This would allow better customization of
the
> program by using several different INItialization files. For
example, you
> might have a "wood.ini" that provided a default feed rate of 60ipm
and a
> "steel.ini" that provided a default feed rate of 5 ipm.
>
> Any idea when you'll have the source code to the G+ release
available?
>
> -- Carol & Jerry Jankura
>    Strongsville, Ohio
>    So many toys, so little time....

----- Original Message -----

From: Alan Matheson

To: turbocnc@yahoogroups.com

Sent: Thursday, January 10, 2002 11:26 PM

Subject: [turbocnc] Bug in Backlash routine

Dave there is a bug in the backlash routine in 3g and 3g+.

My machine is set to metric mode and traverses the correct distances in response to entered commands.

If however I setup the X axis with 0.1 mm of backlash the actual correction is, as close as I can get 2.54 mm.

Mmmm!

 

Regards

Alan Matheson

 

Snip<>

Folks,

   Glad you're all excited about the new list.  I am too...

   I've taken your excellent suggestions about list administration and
stocked up the Files and Photos sections a bit.  Among other things,
a prioritized feature list for v4 and a short to-do list for the next
regular blockpoint update are there.

   All of you should be able to post pictures, files, and bookmarks
now as well.

   For now, I'll try to stand back as much as I can and let you (the
users) hammer out the new directions for the product and share
advice/projects/code; and step in to address specific issues as they
come up.

Dave Kowalczyk
Everett WA
(who's already lost most of his hair anyway, thus making further
aggravation moot, Ballendo... )

Garry,

   Sure thing.  Your step increment works out to 0.0005 inches/step.
(0.200 / 400) or 2000 steps per inch.

   Start and Max speed are the frequencies in Hz (cycles/second) that
define the motion envelope for your machine.

   Start speed is the step rate below which TurboCNC decides that it's
safe to stop a motor completely, and also the step rate that it uses
to start from a dead stop.  Values on the order of 100 thru 500 are
usually appropriate here.

   Max speed is the highest physically possible step rate for your
machine.  For example, a 5000 here means 5000 Hz - which works out to
150 ipm on your equipment.

Dave Kowalczyk
Everett WA

--- In turbocnc@y..., "gah2007" <gah@p...> wrote:
> Hi,
>
> I am trying to setup Turbocnc and need some HELP!!
>
> Spacificly with the Step increment, and the the start speed.
>
> I am using nema23 steppers, 1.8 drgree running in the 1/2 step mode
> with 5TPI lead screws I think then if my math is correct then I am
> looking at 2000 SPI but the Start speed CPS has me totaly dumb
> founded.
>
> Thanks
> Garry

Hi Jerry,

Yes, I'd like to have a "windows" controller, less hassle to run, then
switch back to other apps.  But if all that is on the NC's machine is
the controller program (unless one is WRITING the controller), then it
doesn't matter much, IMO.

My recently set up system for MY NC's machine is 400 mhz AMD; mostly for
EMC.  And it has Windoz 98 so I can try Art's program, DeskNC for
windowz, and so forth.  CNCpro is also a possibility (untested), as
later versions wouldn't run on my main CAD, software development,
internet, etc. machine.

There is a GUI called Menuet/CPP (I used about 8 years ago), which
provides a real nice windows looking interface, and runs on DOS.  I
think that would be a better choice, rather then run on 3.1.  (but then
I even think my "text" menu interface is suitable for a controller!).

TurboVision?  Is that the OLD Borland "text" menu interface I see
occasionally on OLD programs (OOPS!  That sounds like mine too)?

Alan  KM6VV

Carol & Jerry Jankura wrote:
>
> Hi, Alan:
>
> |Or are you talking about what Dennis Of SuperCAM is talking about?
> |Apparently, he's found a way to "shut down" the other tasks, or pre-empt
> |ALL the process time while running gcode?  I'd like to know what he's
> |doing!
>
> This is more to what I was thinking about.
>
> |You mentioned 3.1 before.  You're thinking it would run with less
> |interference?  I'd hate to go back THAT far!  What other apps could you
> |run in Windoz?
>
> Well, Delphi-I runs under windoze 3.1, but this machine would just run the
> CNC program, nothing else, really. It's just that using something like
> Delphi to do the human interface code, and then rework some of the TurboCNC
> code could make a much nicer looking package than TurboVision.
>
> |Let's figure out how to get 98 to "cool it's threads".  ;>)
>
> I'll drink to that!
>
> -- Jerry

Hi, Dave:

Great idea to set up this list.

I started playing with RelG+ and have some comments regarding the additional
INI files:

1. The string used to hold the ini file name should be larger than 12 chars
to allow a drive and directory chain to be specified.
2. At least for the "default" TurboCNC.INI file, you ought to use
Paramstr[0] to find the directory from which TurboCNC is executing and look
to that subdirectory for the INI file.
3. It would be nice to provide a separate subdidrectory for CNC files. These
really ought to be kept out of the TurboCNC directory. Use the INIFile to
specify the CNC directory.
4. It would be nice if default feed rates, etc. were stored within the INI
file instead of hard code. This would allow better customization of the
program by using several different INItialization files. For example, you
might have a "wood.ini" that provided a default feed rate of 60ipm and a
"steel.ini" that provided a default feed rate of 5 ipm.

Any idea when you'll have the source code to the G+ release available?

-- Carol & Jerry Jankura
    Strongsville, Ohio
    So many toys, so little time....

Hi, Alan:

I agree that one attraction to TurboCNC is the source code availability. My
"druthers" would have a windows based system simply because it's what most
other software runs on. It'd be Win 3.1 simply because the CNC computer is a
486-DX250 based notebook with only 8 Mbytes of memory in it. Not nearly
enough to run Win 98 in. But, like you, I'd prefer to spend my money on
something other than another PC just to run the CNC stuff.

-- Jerry
-----Original Message-----
From: Alan Matheson [mailto:hokianga@...]
Sent: Thursday, January 10, 2002 6:04 PM
To: turbocnc@yahoogroups.com
Subject: [turbocnc] Why use windows?


Don't know how others feel but  Turbocnc's attraction to me  is that it runs
in DOS and that the code is published.
Means I can use a junk PC in the workshop and spend the difference between
that and a Windows PC on tooling.

Alan Matheson

Hi, Alan:

|Or are you talking about what Dennis Of SuperCAM is talking about?
|Apparently, he's found a way to "shut down" the other tasks, or pre-empt
|ALL the process time while running gcode?  I'd like to know what he's
|doing!

This is more to what I was thinking about.

|You mentioned 3.1 before.  You're thinking it would run with less
|interference?  I'd hate to go back THAT far!  What other apps could you
|run in Windoz?

Well, Delphi-I runs under windoze 3.1, but this machine would just run the
CNC program, nothing else, really. It's just that using something like
Delphi to do the human interface code, and then rework some of the TurboCNC
code could make a much nicer looking package than TurboVision.

|Let's figure out how to get 98 to "cool it's threads".  ;>)

I'll drink to that!

-- Jerry

Hi Jerry,

Oh sure!  ;>)

For the 3.1, From the Main group, select MS-DOS prompt.  OR, I just boot
to DOS, then call up WIN.  When I exit Windoz 3.1, I get back to DOS.

Or are you talking about what Dennis Of SuperCAM is talking about?
Apparently, he's found a way to "shut down" the other tasks, or pre-empt
ALL the process time while running gcode?  I'd like to know what he's
doing!

You mentioned 3.1 before.  You're thinking it would run with less
interference?  I'd hate to go back THAT far!  What other apps could you
run in Windoz?

Let's figure out how to get 98 to "cool it's threads".  ;>)

Alan  KM6VV


Carol & Jerry Jankura wrote:
>
> |Hi Dave, list,
> |
> |Great Idea!  Hope this list grows, and your programs continue to
> |improve.  I really enjoy digging through source code (my day job too),
> |so this is a welcome opportunity to study controller software.  Of
> |course, it should be written in 'C'!  Just kidding!  ;>)
>
> Alan, I think that Delphi, and building a driver for Win 3.1 and/or Win 98
> would be much better than C or C++! :)
>
> On a more serious note - Does anyone know if Windows 3.1 can be set up so
> that the program that is in-focus can take over the machine? If so, using
> Delphi might be a good way to build a Win 3.1 compatible program.
>

|Hi Dave, list,
|
|Great Idea!  Hope this list grows, and your programs continue to
|improve.  I really enjoy digging through source code (my day job too),
|so this is a welcome opportunity to study controller software.  Of
|course, it should be written in 'C'!  Just kidding!  ;>)

Alan, I think that Delphi, and building a driver for Win 3.1 and/or Win 98
would be much better than C or C++! :)

On a more serious note - Does anyone know if Windows 3.1 can be set up so
that the program that is in-focus can take over the machine? If so, using
Delphi might be a good way to build a Win 3.1 compatible program.

Hi Dave, list,

Great Idea!  Hope this list grows, and your programs continue to
improve.  I really enjoy digging through source code (my day job too),
so this is a welcome opportunity to study controller software.  Of
course, it should be written in 'C'!  Just kidding!  ;>)

I have been working on a controller of my own design for over a year.
It's running, but not ready for release.  Amazing how many basic
"algorithms", if you will, are done in a similar fashion!  (Somebody
please say: "Great minds think alike").

Alan  KM6VV
Central coast, CA

Great Idea Dave.

Just to introduce myself. I live and work from a tiny town called
Turakina a bit south of Wanganui in New Zealands North Island.

Im using TurboCnc to control a converted drill mill with 4 axes
currently available. The motors are 450 oz/in steppers driven with
stepper driver kits from Oatley Electronics in Australia. The mill is
used about half and half as a hobby machine and to make one off
laboratory equipment.   Have been working intermittently on a VB5
program to convert Autocad LT files to gcode specifically for
TurboCNC.

Regards
Alan Matheson

Hi,

I am trying to setup Turbocnc and need some HELP!!

Spacificly with the Step increment, and the the start speed.

I am using nema23 steppers, 1.8 drgree running in the 1/2 step mode
with 5TPI lead screws I think then if my math is correct then I am
looking at 2000 SPI but the Start speed CPS has me totaly dumb
founded.

Thanks
Garry

--- In turbocnc@y..., "dkowalcz2000" <dkowalcz@d...> wrote:
> I'm really looking forward to being able to get all the users and
> source-code tinkerers, starry-eyed dreamers, etc talking to each
> other in one place where we can collaborate on ideas.

Which brings up a question - Who of us (besides Dave, the master
tinkerer) is tinkering with the code.

I'll start the ball rolling by saying that I've been playing with
pieces of it. For starters, I tend to run any new release through the
DelForEx code formatter. This is a freebie available at
http://www.slm.wau.nl/wkao/delforexp.html. While Borland Delphi is
its intended target, it works well for code written in TurboPascal.

I'm interested in hearing how others have modified the code. I
simplified the parser (parseline function) into a case statement and
am toying with adding a TurboVision front end to it. I'm not sure how
TurboVision will affect the smoothness of the stepper pulse train, as
I'm sure that TurboVision plays with the interrupt structure in order
to achieve its event driven paradigm.

Has anyone gotten the DOS version of TurboCNC to plot out the tool
path?

-- Jerry Jankura
    Strongsville, Ohio
    So many toys, So little time....

Hi Dave,

This group is a great Idea !

I see the simple starting point for beginners in software has to be a
ultra low cost package that has some real functionality.

I can see that the CAD to G-code to TurboCNC will be a pretty
straight forward process and I really look forward to this group
dissecting and reassembling that sequence over and over.

My I recommend you put some of your pictures in the photo section ?

And if there is a free/shareware g-code interpreter, put that in the
files section.

Also, as this group matures, I'll be interested to see the path it
follows.

Dave Mucha

Hi all from sunny Australia.

Just thought I'd introduce myself.   My name is Andrew Erwood, and I
live in Cairns, Queensland Australia.
I am converting an old Mori-Seiki NC lathe, to a PC based system
using TurboCNC.  I am about halfway through writing a windoz front-
end for TurboCNC.  I am using two boxes, one dos running just
TurboCNC, the other running my front-end.  I am doing this mainly
because I know nothing (well, very little) about Pascal, and I am a
little bit better with VB6.  I have written a conversational editor
in VB, so I have incorperated this into the front-end. I am planning
to also put a teach mode into it as well.  I have the VB side just
about licked, I have toolchanger working(8 tools, two turrets),
spindle speeds are almost there also, with gearchanging for 8 gears
and a VFD fitted to vary the speeds for constant surface speed
(hopefully).
I am running Rutex drives and DC motors 90VDC 40 amp peak.


All the best

Andrew

Doug,

Excellent suggestions!

Ballendo

--- In turbocnc@y..., "cnckitsdotcom" <pentam@h...> wrote:
<snip> It would be great for you also to post here the specific
> GCodes (and their meaning) that TurboCNC implements
> currently (version 3.00g+).  That will give future readers
> a grounding in your current technology.
>
> Finally, you might want to post your 'to do' list.  Perhaps
> with some feedback, you will be able to assign priorities to
> their implementation.
>
>
> Doug Fortune
> http://www.cncKITS.com

Dave,

Let's get started! What are the features necessary and or desirable
for a cnc lathe control? How does a lathe control differ from a
milling control?

Good luck with this site.

Ballendo

P.S. Do you have any idea what you're getting yourself into? :-)

Good to see you make this move. Few suggestions:
Put a link to your website in the bookmarks folder at the group
homepage.
Post a coupla program screenshots in the photos area.
disallow attachments in posts. The spammers will eat you alive if not.
consider turning off the members directory at the group website for
the same reason.
Anyway, I'm looking forward to this groups' growth!

--- In turbocnc@y..., "dkowalcz2000" <dkowalcz@d...> wrote:
> To all,
>
>   Welcome to the new discussion group for the program.
> I'm figuring most folks will want to talk about TurboCNC

Hi Dave:
Yes this should be interesting, due to your modesty you
forgot to post your website!

http://www.dakeng.com/

and the TurboCNC specific page is at

http://www.dakeng.com/turbo.htm

It would be great for you also to post here the specific
GCodes (and their meaning) that TurboCNC implements
currently (version 3.00g+).  That will give future readers
a grounding in your current technology.

Finally, you might want to post your 'to do' list.  Perhaps
with some feedback, you will be able to assign priorities to
their implementation.


Doug Fortune
http://www.cncKITS.com

To all,

   Welcome to the new discussion group for the program.  I'm figuring
most folks will want to talk about TurboCNC - there really aren't
many people using my gear calculator on a regular basis...  So the
group has been named accordingly.

   I'm really looking forward to being able to get all the users and
source-code tinkerers, starry-eyed dreamers, etc talking to each
other in one place where we can collaborate on ideas.  Much better
than CC'ng emails to each other.

So, feel free to discuss anything that comes to mind!

Yours,
Dave Kowalczyk