Copyright (C) 1986-2009 by Daniel H. Hudgins, All Rights Reserved.

No part of "This Web Site" (HTML document), including associated files, may be: distributed, sublicensed, transmitted, copied, archived, mirrored, modified, bundled, embedded, sold, given away, rented, loaned, or shared in any form without express written permission in a formal Vendor agreement contract dated and signed in ink obtained directly from Daniel H. Hudgins by registered postal mail. All agreements for permission to distribute expire after a period no greater than one year from the date of the signing of the agreement by Daniel H. Hudgins. See the current "EULA" for information regarding limited copying and storage for the purpose of "Beta Testing" "This Web Site."

To view or use the current version of this Web page you may need to reload or refresh the display of this page by your browser. Just clicking on the browser's [Reload] or [Refresh] icon may not be enough to insure that all of the page's most current contents have been cached and displayed. Some browsers may have additional commands to help display the page's most current contents such as: holding down the [Shift] key and clicking on the [Reload] icon, holding down the [Control] key and clicking on the [Refresh] icon, holding down the [Control] and [Shift] keys and clicking on the [Refresh] icon, pressing the [Control] and [F5] keys, pressing [Control] and the [R] key, or some other combination of keys or clicks. Check to see which commands your HTML browser uses to load the most current page contents into its cache and then to display them onto the screen.

This Web site is dedicated to the thousands of "users" of my programs, those who have helped test my programs over the last 23 or so years, and especially those who shared their experiences with me.

You must read this notice: This is a licensed Web site (HTML document and associated files). You must read and agree to be legally bound in contract by the Terms of Use and conditions given in the End User License Agreement ("EULA"), Legal Notices, Instructions, Warnings, Disclaimers, and all other text in "SECTION: 0" of "This Web Site" (HTML document and associated files) before reading or using any of the information, software programs, and or files, contained in, linked to, and or associated with, "This Web Site" (HTML document and associated files). Any use or "Beta Testing" of "This Web Site" constitutes your acknowledgment of your full agreement with the current End User License Agreement ("EULA") and your decision to have this current license supersede all prior and contemporaneous agreements and understandings. Information and files in "This Web Site" (HTML document and associated files) have been placed here so that long time users of "The Author's" programs DANCAD3D.COM (tm) , DANCAD87.EXE (tm), DANCINEL.EXE (tm), DANCINES.EXE (tm) , DANCAM.EXE (tm) , or DANPLOT.EXE (tm) could help proofread the text of the documentation files or screens displayed, and also help test data files, example files, and or any software programs that might be made available from time to time, to aid "The Author" in finding mistakes, bugs, and other errors, omissions, defects, mistakes, and faults. Everything in "This Web Site" (HTML document and associated files) is "Beta Test", "Beta Code", Experimental, Preliminary, requires proofreading, or is being evaluated for possible revision, and is NOT warranted to be free of defect. To help "The Author" report any bugs, foul-ups, defects, or mistakes that you find, see "SECTION: 8" for instructions. "This Web Site" (HTML document and associated files) and all other files and programs by Daniel H. Hudgins are made available "AS IS" without warranty of any kind express, expressed, or implied. All offers and specifications are subject to change or discontinuation without notice of any kind. Please look over "SECTION: 8" of "This Web Site" before contacting "The Author."

This documentation file has text mostly about revisions to some "Beta Test" utility programs for use with my CAD and CAM programs, and might be looked to for updated information relating to changes from v2.5 of some of these utilities. There may be changes made in versions subsequent to v2.7E that alter what is described in this section as it applies to that subsequent version. See also any other documentation files, and pages in this Web site (HTML document) for additional and or more recent information.

The HTML documentation in this SECTION: 3.75.0.0 was derived from the README.TXT file that is, or was at one time, included in the *.ZIP file DANUTLPK.ZIP (tm), that you may be able to download by going to SECTION: 9.75.51.0. The file DANUTLPK.ZIP (tm) may also have the utility programs described in this section and some other files for testing with them in it.

You may not distribute, sell, rent, share, or give away these HTML documentation files or printed copies of them. You may not extract text from these HTML documentation files for distribution, sale, rent, sharing, or giving away. You can use the [Print] option in your browser to make one copy for yourself to mark up in order to help me proofread the text for mistakes.

Documents may be available to download from time to time, you can check SECTION: 9 to see what the current situation with regard to downloadable files is. The names of these documentation files may change, and they may be edited, combined, or eliminated in the future, without notice.

You may need to adjust your browser for best viewing of the pre- formatted text by changing the "font" size using the commands in your browser (see the help in your browser, or use the pull-down menus in your HTML browser.) If some letters in words on the screen appear to be missing or scrambled try changing the font size in your browser as this sometimes happens even though the words are spelled correctly in the HTML code.

Use the "Edit, Find in page Ctrl+F" or "Edit, Find (in this page)... Ctrl+F" command in your browser to search for keywords within the documentation text in this HTML page. You will need to search over again in the other pages in this HTML document for the same keyword since your browser may not search for a keyword beyond the current page that is loaded.

DANUTLPK.ZIP (tm) is a *.ZIP file that holds some "Beta Test" utility programs and associated files for "Beta Testing" along with "Beta Testing" of the programs DANCAD3D.COM (tm), DANCAM.EXE (tm), and DANPLOT.EXE (tm) that were also authored by Daniel H. Hudgins.

The use and copying of these utility programs are governed by my current End User License Agreement ("EULA") which is located in SECTION: 0 of this "Beta Test" Web site. You must read and fully agree to be legally bound by the current End User License Agreement ("EULA") before you use or "Beta Test" any of the files in DANUTLPK.ZIP (tm). If you are unable to read and agree to the current End User License Agreement ("EULA") do not use or "Beta Test" any of the files in the DANUTLPK.ZIP (tm) file.

Be sure that you scan the programs and files in DANUTLPK.ZIP (tm) for virus or other contamination since you are responsible for checking them before you use them. These programs and this information are made available "AS-IS" and are without warranty of any kind express, expressed, or implied. Since these programs are "Beta Test" you must agree to become a "Beta Tester" before you make any use of them, see the End User License Agreement ("EULA") in this "Beta Test" Web site for more information. Be sure to read the current instructions in this "Beta Test" Web site regarding procedures for reporting program bugs and other such problems.

On some systems the *.ASC data files may be able to be renamed *.TXT to avoid certain kinds of file type misinterpretation by text editor type programs and such. Thank you for helping test these "Beta Test" utility programs.

A *.TXT version similar to this S0375000.HTM file may be included in the DANUTLPK.ZIP (tm) file (see the "downloads" SECTION: 9 of this "Beta Test" Web site) probably as in file README.TXT stored in DANUTLPK.ZIP (tm), so you should check for that document because the README.TXT file may be more up-to-date than this *.HTM file, or this HTML file could be more up to date, depending on which one got worked on last.

FILES THAT MAY BE IN THE DANUTLPK.ZIP (tm) FILE:

CHAIN.EXE   v2.7E (tm) Program to concatenate my ASCII data type files.
OFFSET.EXE  v2.7E (tm) Program to translate data points in ASCII data.
JOBDONE.EXE v2.7E (tm) Program to signal when a batch job is done.
COUNTER.EXE v2.7E (tm) Program to keep a count of parts made and such.
CHA1TEST.BAT           Demo & test Batch file for CHAIN.EXE v2.7E (tm).
OFF1TEST.BAT           Demo & test Batch file for OFFSET.EXE v2.7E (tm).
JOB1TEST.BAT           Demo & test Batch file for JOBDONE.EXE v2.7E (tm).
COU1TEST.BAT           Demo & test Batch file for COUNTER.EXE v2.7E (tm).
SQU1.ASC               Sample Square *.ASC drawing file for batch files.
CIR1.ASC               Sample Circle *.ASC drawing file for batch files.
TRI1.ASC               Sample Triangle *.ASC drawing file for batch files.
README.EXE             Text version of some information about the utilities.

These utility programs use DOS command line parameters for their commands rather than having menus. This mode of operation allows you to enter the command after the program name at the DOS prompt or to use the program in a DOS batch file along with other programs and DOS commands.

CHAIN.EXE v2.7E (tm) is used on the DOS command line by putting a list of filenames after the program name CHAIN, just like you would use some DOS type commands.

The first filename after CHAIN is the output file that you want the concatenated (joined) data to go to. Be sure that you do not use the name of an existent file for the output file unless you want to erase the existent file and overwrite it.

After the name of the output file come a list of up to eight (8) input files that will be concatenated in the order given reading from left to right. If you need to concatenate more than eight (8) files you can use the CHAIN program more than once.

EXAMPLE: C>CHAIN OUT.ASC IN1.ASC IN2.ASC IN3.ASC IN4.ASC

In this example the file OUT.ASC is made up of data from files IN1.ASC, IN2.ASC, IN3.ASC, and IN4.ASC.

If there is a error or problem while CHAIN.EXE v2.7E (tm) is used, you should disable and power-down your automated machine tool before you allow the batch file you have CHAIN.EXE v2.7E (tm) in to continue since the CAM program(s) may receive a tool path file that is not correct.

OFFSET.EXE v2.7E (tm) is used on the DOS command line by putting a pair of filenames, and three numbers, after the program name OFFSET, just like you would use some DOS type commands.

The first filename after OFFSET is the output file that you want the translated (shifted, offset) data to go to. Be sure that you do not use the name of an existent file for the output file unless you want to erase the existent file and overwrite it.

After the name of the output file comes the name of the input file that you want copied with the data points offset. Be sure that the input filename is the name of a data file that exists and you include the fill filename including the correct file path and drive letter.

After the input filename is a list of three (3) offset values that are used in the order given reading from left to right for the x, y, and z axis offset values. Whether positive offset values shift the tool in one direction or the other depends on how you have your automated machine set-up and configured.

EXAMPLE: C>OFFSET OUT.ASC IN1.ASC 0 0 0.005

In this example the file OUT.ASC is made up of data from file IN1.ASC offset by the x, y, and z axis offset values, which in this case are no x offset change, no y offset change, and 0.005 z axis offset change.

EXAMPLE: C>OFFSET OUT.ASC IN1.ASC -2.75125 3.0001 0

In this example the file OUT.ASC is made up of data from file IN1.ASC offset by the x, y, and z axis offset values, which in this case are -2.75125 x offset change, +3.0001 y offset change, and no z axis offset change.

If there is a error or problem while OFFSET.EXE v2.7E (tm) is used, you should disable and power-down your automated machine tool before you allow the batch file you have OFFSET.EXE v2.7E (tm) in to continue since the CAM program(s) may receive a tool path file that is not correct.

JOBDONE.EXE v2.7E (tm) is used on the DOS command line by putting a command after the program name JOBDONE, just like you would use some DOS type commands.

The command after JOBDONE is optional, and is used to control the audio signal. There currently three options: (1) no command makes the program produce an audio signal (beeps) until you quit the program, (2) the command ONCE that makes the program produce the audio signal just once when it starts, and (3) the command SILENT that disables the audio signal altogether.

EXAMPLE: C>JOBDONE

In this example the program beeps on and on.

EXAMPLE: C>JOBDONE ONCE

In this example the program beeps once then goes silent.

EXAMPLE: C>JOBDONE SILENT

In this example the program does not beep at all.

When JOBDONE is used in a loop in a Batch file you should put the DOS commands BREAK ON and PAUSE between JOBDONE and GOTO so that you will be able to use the [Ctrl] and [Break] keys on the computer's keyboard (or [Control] and [C] keys on some computers) to "break" the endless looping of the batch file.

EXAMPLE: :LABEL
          DANCAM PART.ASC
          JOBDONE
          BREAK ON
          PAUSE
          GOTO :LABEL

If there is a error or problem while JOBDONE.EXE v2.7E (tm) is used, you should disable and power-down your automated machine tool before you allow the batch file you have JOBDONE.EXE v2.7E (tm) in to continue since the CAM program(s) may receive a tool path file that is not correct.

COUNTER.EXE v2.7E (tm) is used on the DOS command line by putting a filename to store the current count in, a command mode keyword, and in some cases a number value after the program name COUNTER, just like you would use some DOS type commands.

The number value after COUNTER is used with the ASSIGN and COUNT command modes, it is used to control the current count. The filename used to store the count in, and the command mode must always be stated. There currently three command modes: ASSIGN to set the counter starting value, COUNT to add to or subtract from the current value assigned, and DISPLAY to display the current value in the file used to keep the count in.

EXAMPLE: C>COUNTER MYCOUNT.TXT ASSIGN 0

In this example the program sets MYCOUNT.TXT to a count of 0.

EXAMPLE: C>COUNTER MYCOUNT.TXT ASSIGN 20010300

In this example the program sets MYCOUNT.TXT to a count of 20010300.

EXAMPLE: C>COUNTER MYCOUNT.TXT COUNT +1

In this example the program sets MYCOUNT.TXT to a count of one more than its last value.

EXAMPLE: C>COUNTER MYCOUNT.TXT COUNT -1

In this example the program sets MYCOUNT.TXT to a count of one less than its last value.

EXAMPLE: C>COUNTER MYCOUNT.TXT COUNT +15

In this example the program sets MYCOUNT.TXT to a count that is 15 more than its last value.

EXAMPLE: C>COUNTER MYCOUNT.TXT COUNT -54

In this example the program sets MYCOUNT.TXT to a count that is 54 less than its last value.

EXAMPLE: C>COUNTER MYCOUNT.TXT DISPLAY

In this example the program displays the current count stored in your file MYCOUNT.TXT that is used to hold the count value, and waits for you to press a key so that you can read the displayed value off of the computer screen.

When COUNTER is used in a loop in a Batch file you should put the DOS commands BREAK ON and PAUSE between COUNTER and GOTO so that you will be able to use the [Ctrl] and [Break] keys on the computer's keyboard (or [Control] and [C] keys on some computers) to "break" the endless looping of the batch file.

EXAMPLE: COUNTER MYCOUNT.TXT ASSIGN 0
         :LABEL
         DANCAM TOOLPATH.ASC
         COUNTER MYCOUNT.TXT COUNT +1
         COUNTER MYCOUNT.TXT DISPLAY
         BREAK ON
         PAUSE
         GOTO :LABEL

If there is a error or problem while COUNTER.EXE v2.7E (tm) is used, you should disable and power-down your automated machine tool before you allow the batch file you have COUNTER.EXE v2.7E (tm) in to continue since the CAM program(s) may receive a tool path file that is not correct.

Below is an example DOS batch file to give you some idea of how these utilities might be used in practice. It is possible to arrange the utilities in different ways to use them for various tasks within the scope of their use. You can obviously mix these utilities with the other DOS batch file commands such as COPY, XCOPY, DEL, ERASE, RENAME, MD, RD, and so on.

REM Start of example DOS batch file named EXAMPLE.BAT

COUNTER MYCOUNT.TXT ASSIGN 0

CHAIN OUT1.ASC IN1.ASC IN2.ASC

:LABEL

COUNTER MYCOUNT.TXT COUNT +1

OFFSET OUT2.ASC OUT1.ASC 0 0 0.005

DANCAM OUT2.ASC

OFFSET OUT2.ASC OUT1.ASC 0 0 0.010

DANCAM OUT2.ASC

OFFSET OUT2.ASC OUT1.ASC 0 0 0.015

DANCAM OUT2.ASC

JOBDONE ONCE

COUNTER MYCOUNT.TXT DISPLAY

BREAK ON

PAUSE

GOTO :LABEL

REM End of example DOS batch file named EXAMPLE.BAT