FILE SCREEN


FILE SCREEN

A file is a unit in which the system stores information. Files can be stored on a variety of storage media.

You perform file manipulations using the FILE screen.

From the FILE screen you can:

  • Generate a directory of files

  • Load or restore files from the default device onto controller memory

  • Back up program and system files

  • Update software automatically

  • Display text (ASCII) files

  • Copy files to and from various devices

  • Delete files from the default device

  • Save files to the default device

  • Create error log files

To manipulate a file you must know the type of file you are manipulating. Table 1, "Types of Files" lists several types of files available. During your work on the controller, you might only use a few types of files. You can determine the file type by looking at the file name as it is displayed on the FILE menu. The file name consists of up to 36 characters for file name, followed by a period, followed by a two- or three-letter file type:

file.XX

where file is the file name and XX is the file type.

Note

File types with three characters might be displayed on the FILE screen. These types are for various kinds of compressed files. The display of these file types is controlled by the system variable $FILE_MASK. Refer to the System Software Reference Manual for more information.

Table 1. Types of Files

File Type

Description

Bit map file (.BMP)

This file type contains bit map images used in robot vision systems.

Command file (.CF)

This file type contains text (ASCII) files that contain a sequence of KCL commands for a command procedure.

Condition handler file (.CH)

This file type contains files that are used as part of the condition monitor feature.

Default file (.DF)

This file type contains binary files that contain the default motion instructions for teach pendant programming.

Diagnostic file (.DG)

This file type is an ASCII file that provides you with a snapshot of the special diagnostic files on the memory device. The names of the diagnostic files are stored in the system variable $FILE_DGBCK.

Data file (.DT)

This file type contains text (ASCII) or binary files that contain any data that is needed by the user.

I/O file (.IO)

This file type contains binary files that store configuration data.

KAREL file (.KL)

This file type contains text (ASCII) files that contain the KAREL language statements for a KAREL program.

Listing file (.LS)

This file type contains text (ASCII) files that contain the listing of a TP language program, and line numbers for each TP statement. Listing files are also generated when a teach pendant screen is saved.

Listing files also include error log files and other special diagnostic files.

Part model file (.ML)

This file type contains part model information used in robot vision systems.

Mnemonic(.MN)

Files of this type are supported in previous versions of the application software.

Macro (.MR)

This file type contains programs with a macro sub type.

P-Code file (.PC)

This file type contains binary files that contain the translated version of a .KL KAREL program file. This is the file that is actually loaded into controller memory and executed.

PMC (.PMC)

This file type contains Programmable Machine Controller (PMC) information.

Process (.PR)

This file type contains programs with a process sub type.

System file (.SV)

This file type contains binary files that store default values for system variable, servo parameter data, and mastering data.

Teach pendant program file (.MN)

This file type contains binary files that contain teach pendant instructions for teach pendant programs.

Text file (.TX)

This file type contains text (ASCII) files that contain system-defined or user-defined text.

Variable listing file (.VA)

This file type contains text (ASCII) files that contain the listing of KAREL variables or system variables.

Variable file (.VR)

This file type contains binary files that contain variable data for a KAREL program.

Vision Data file (.VD)

This file type contains binary files that contain Vision Data for Vision.

Vision Data ASCII file (.VDA)

This file type contains text (ASCII) files that contain Vision Data parameters for Vision.

Zip file (.ZIP)

This file type contains multiple types of files in one container file.


Table 2, "Robot Data File Groups" describes how file types are grouped based on their function, and lists example file names for each group. This information can be used to determine files to load or download depending on a functional area of the controller.

Table 2. Robot Data File Groups

Robot Data File Group Description Example Files
Operating System Files These files are related to the robot operating system's configuration.
  • DIOCFGSV.IO— I/O information

  • NUMREG.VR— data register information

  • POSREG.VR— position register information

  • FRAMEVAR.VR—Frame setup information

  • SYSFRAME.SV—Tool frames and user frames

  • SYSVARS.SV— system variable information

  • SYSSERVO.SV— servo parameter data

  • SYSMAST.SV— robot mastering data

  • SYSPASS.SV— password information (if applicable)

  • SYSFSAC.SV— remote access control information (if applicable)

  • SYSHOST.SV— Ethernet host table (if applicable)

  • SYSMACRO.SV— macro table definitions

Supplier Application Files These files are application files that are pertinent to the manufacturing process. They are provided by the supplier and are common to a number of robots.
  • SWCUSTO.VR— Customized variables

  • SYSSPOT.SV— Spot welding-specific variables

  • SYSSEAL.SV— Dispense application-specific variables

  • MAIN_TCP.VR— Torch Mate data (if applicable)

  • SET_ATCP.VR— Torch Mate data (if applicable)

  • OFFSETDT.VR— Torch Mate data (if applicable)

  • TMMOVETO.VR— Torch Mate data (if applicable)

  • User-specified variables listed in $FILE_APPBCK

User Application Files These files are application files that are pertinent to the manufacturing process. However, they are customized by the user and are common to a number of robots.
  • User-specified files listed in $FILE_AP2BCK

Robot Path Files These are files that are related to specific robot functions such as robot path and variable data customizable by the robot plant floor operator.
  • All teach pendant programs (*.tp)

Robot Specific Data Files These are robot specific files containing calibration and configuration data, and I/O mapping information.
  • SWCUSTO.VR— Customized variables

  • SYSSPOT.SV— spot welding specific variables

  • User-specified files listed in $FILE_AP2BCK (Calibration and configuration data and I/O mapping can be specified.

Error Log These are robot system error log files.
  • ERRALL.LS— Alarm history

  • ERRACT.LS— Active alarms

Vision Data Files These are vision process specific data files.
  • All vision data files (*.VD)


Table 3. Auto Update Operations Items

ITEM

DESCRIPTION

Start Auto Update

This function will start the complete Auto Update operation.

Display Backups

This function is used to display the Auto Update backups so that one can be selected for the other operations.

Get Image Backup

This function is used to quickly get the right Image Backup files to the top-level directory. This will allow the user to quickly select and copy a specific Image Backup made by Auto Update.

Clear Backup

This function is used to make room on the Auto Update media. This will allow you to select and clear out a specific Backup made by Auto Update. This deletes the content of the directory and all sub-directories and removes the directory itself.