When an application directory is created in InTouch, a set of data files is created to be used by WindowMaker and WindowViewer. Each application created must be in a separate directory. Unless specifically instructed by Wonderware personnel, do not, under any circumstances, edit these files.
InTouch Data Files wonderware intouch
File | Description |
ALARM.CFG | This binary file contains information for alarm logging and printing. |
ALMGRP.INI | Text file containing the Alarm Group Lists specified in the Name |
Manager/Distributed Alarms configuration. | |
APP.VER | This binary file contains the application version. |
APPEDIT.LOK | Read-only file created by WindowMaker to prevent multiple nodes from |
editing an application. | |
APPCHNGD.FMS | File updated from WindowMaker when a Special/Notify Clients is |
performed. | |
APPLIST.INI | Text file containing information about the custom and transparent |
colors used by the WindowMaker Palette. | |
APPSTG.STG | Binary file containing information about the custom and transparent |
colors used by the WindowMaker palette. | |
APPLOGIC.LGC | This binary file containing the Application script (On Start, While |
Showing, On Shutdown). | |
COLORCH.INI | Text file containing the 32 colors used by the color selection boxes in |
WindowMaker. | |
DB.INI | This file contains the defaults for each dialog box in the Tagname |
Dictionary. | |
DDE*.AVL, DDE*.BIN, DDE.CFG | These files contain information for DDE Access names and nodes. |
DHISTCFG.INI | This file is used by the distributed history system. |
DS######.CFG | This file contains SPC dataset configuration information. |
DS######.DAT | This binary file contains data collected using SPC. |
DS.INF | This binary file contains Dataset information. |
GROUP.DEF | This file contains information for tagname alarm groups. |
HISTLOG.CFG | This file contains the configuration information used by this Historical |
logger. | |
HISTPRV.INI | Text file containing the distributed history provider information specified |
by the Name Manager/Distributed History configuration. | |
INTOUCH.INI | This file contains the configuration information used by InTouch for the |
application. | |
INTRACK.INI | Text file containing information about the InTrack configuration. |
INTRACK.ITL | Binary file containing the InTrack taglist information. |
ITOCX.CFG | Binary file containing cross-reference information about ActiveX |
controls used in the application. | |
LINKDEFS.INI | This file contains the defaults for each link dialog box in WindowMaker. |
OCX.INI | Text file containing the Globally Unique Identifier (GUID), and a |
description of each ActiveX control registered in InTouch from Install | |
Wizards/Active X. | |
PASSWORD.BIN | This binary file contains the User Names, Passwords and Access |
Levels used in the security section of the application. |
InTouch Data Files
RETENTIV.X, RETENTIV.A, | These binary files contain retentive values for this application. |
RETENTIV.D, RETENTIV.H, | |
RETENTIV.S, RETENTIV.T | |
SECCONFIG.XML | This file contains the security model definition for this application. |
SERIAL.TRN | This file contains the serial numbers for all the real time trends in the |
application. | |
SPC.CFG | Binary file containing information about the SPC configuration. |
SPC.INI | Text file containing information about the SPC Dataset and SPCPro |
data source name configuration. | |
SPCPASSWORD | Binary file containing the user/password configuration for event-based |
and automatic data collection to the SPCPro database. | |
SUPERTAG.DAT | Binary file containing the template definitions used by WindowMaker |
when creating SuperTags from the Tagname Dictionary. | |
SQL.DEF | Text file containing the bindlist and templates defined from the SQL |
Access Manager. | |
TAGBRW.DAT | Binary file containing the last configuration used by the Tag Browser. |
TAGNAME.AVL, | These files contain specific information about items in the Tagname |
TAGNAME.NDX, TAGNAME.X | Dictionary. |
TBOX.INI | This file contains the initial settings for the toolbox. It is updated each |
time WindowMaker is closed and will restart with the same settings for | |
the application. | |
*.TRN | This file represents trend information for a window. If a window has no |
trend information, there will be no corresponding .TRN file. | |
VERS_RES.INF | This file contains the InTouch version number and the screen resolution |
of the application. | |
VIEW.INI | This file contains the default window selections used by |
WindowViewer. | |
*.WIN | This WindowMaker file contains a detailed description of each window. |
File names are in the following format: win#####.win. | |
WIZ.INI | Text file containing information about the Wizards registered in InTouch |
from Install Wizards/ActiveX. | |
WM.INI | This file contains the default window selections used by WindowMaker |
on startup. | |
*.WVW | When a window is first loaded by WindowViewer it is “compiled” and |
save into a .WVW file. This substantially improves the window loading | |
time in WindowViewer. | |
WWREPORT.INI | Text file containing the tagname of the tag to increment when using the |
InTrack report function. | |
WW_WDWS.NDX | This file contains a cross-reference of the application window names. |
*.AEH | This is a text file created by the WWLOGGER.EXE program and contains |
the error log for all Wonderware products. | |
*.ALG | This is the ALARM file. It is a text file created by the InTouch alarm |
program and contains a listing of all logged alarms. | |
*.LGH | This binary file contains logged data from InTouch. |
*.IDX | This is the index file for the *.LGH file. |
*.CSC | This binary file contains a condition script. |
*.KSC | This binary file contains a Key script. |
*.CSV | Text file in Comma Separated Variable format. |
*.TXT | Text file |
InTouch Data Files
*.BMP, *.JPG. *.PCX, *.TGA | Graphics/image files containing a bitmap object of the bitmap has a |
String Value Display link. | |
*.PAL | Windows Palette file created by exporting a palette from the |
WindowMaker color palette or by a 3rd party utility. | |
*.WAV | Microsoft sound file. |
*.NEH | Text file created by the Wonderware NT Conversion Logger when a 16- |
bit InTouch application is converted to 32-bit. Contains a log of the | |
conversion process, including any errors that are encountered. | |
*.DCH | This binary file contains a Data Change script. |
*.NMD | A binary file containing a Quick Function script. |
*.OES | A binary file containing an ActiveX event script. |
*.?BK | All files ending with .?BK are backup files. InTouch creates backup files |
of all edited files. All backup files can be deleted when the application is | |
complete. This will free up disk space and make the application | |
directory smaller for making backups or transporting an application. |
- NB Designer OMRON HMI Youtube Tutorial Videos
- DOPSOFT DELTA HMI Youtube Tutorial Videos
- Wonderware Intouch Youtube Tutorial Videos
- GT Designer MITSUBISHI HMI Youtube Tutorial Videos
- WinCC Siemens HMI Youtube Tutorial Videos
- FACTORY TALK VIEW Youtube Tutorial Videos
Certain InTouch files may be deleted to conserve disk space. Typically, any files whose extensions end in BK (e.g., .cbk) may be deleted by specifying a delete of *.?BK in one of the file manipulation utilities (e.g., Winfile or Explorer). Because WindowViewer always compiles a fresh .wvw file for each new version of the .win files, all of the .wvw files can be deleted and new .wvw files will be compiled from the existing .win files when WindowViewer is launched. Depending on how the application was configured, historical log files and alarm log files can be stored in the application directory. If the log files are unnecessary, all files ending with .LGH and .IDX (historical log files) can be removed. Most of the files remaining are essential to an application and should be left alone. If further size reduction is desired, a compression utility can be used (e.g., PKZip or WinZip) or a backup utility can be used to condense and store the application. When using one of the zip programs, it is recommended to convert the zipped file into a self-extracting zip file by running zip2exe or the equivalent. This will insure that the recipient of the application has the correct unzip version
- Delta Tutorials
- HMI Demo examples
- PLC Tutorials
- Rockwell Tutorials
- WinCC Siemens Tutorials
- Wonderware Intouch Tutorials