beautypg.com

20 automax file types – Rockwell Automation 57C650 AutoMax Programming Executive Version 3.8 User Manual

Page 48

background image

4Ć14

AutoMax Programming Executive Version 3.x

4.20

AutoMax File Types

In addition to the files described in section 4.18, the following file

types may be created when you use the Programming Executive.

The file type is determined by the file extension. AutoMax uses the file

extension to determine the particular editor (text editor or PC editor)

to be used. When you create a file, the Executive appends one of the

following file extensions to designate the file type:

.BAS

BASIC tasks

.BLK

Control Block tasks

.CNF

Configuration files

.PC

PC/Ladder Logic tasks

.INC

Include files (see BASIC statement INLCUDE)

.SDC

System documentation files

.CDC

Section documentation files

.RDC

Rack documentation files

.TDC

Task documentation files

.IDC

Include documentation files

.DBF

Database files

.NDX

Database index files

.XRF

CrossĆreference files

.LOG

Log files

.LST

Task list files

.OBJ

Object files (BASIC, Control Block, or

Configuration)

.POB

Drive parameter object files

.OS

System files

.EXE

"ąąą "

.BAT

"ąąą "

.INI

"ąąą "

.ERM

"ąąą "

.HLP

"ąąą "

.IMA

"ąąą "

.DAT

"ąąą "

After you edit and save an existing file using the text editor or the PC

editor, AutoMax renames the original file by adding the tilde character

(~) at the beginning of the file extension and dropping the third letter

in the file extension. This makes it possible to edit a file once without

losing the original. For example, editing and then saving the task

SPD.BLK would result in the edited version of the task being saved

as SPD.BLK and SPD.~BL as the backup.
Note that if you choose a different text editor in AutoMax Setup (see

section 5.5.2), the character used to designate backup files, if any,

may be different than described above. If your text editor creates

backup files by attaching a .BAK file extension, be sure that you give

all task files unique names to avoid writing over an existing backup

file. For example, if you create a BASIC task and an Include file with

the same name (TASK1.BAS and TASK1.INC), and then edit

TASK1.BAS, the backup file will be named TASK1.BAK. If you then

edit the Include file, its backup would write over, and you would lose,

the backup for the BASIC task.
The Executive software maintains a maximum of two versions of any

task file. Backup copies of the database files are not maintained. If

more than two versions of any file need to be maintained, the file

should be copied under another name using the COPY command

from the Windows File Manager.