System Hangs

Program Hung Ups

There are several files that can accumulate if yearly maintenance is not undertaken. In extreme cases this can cause program slow downs and hangs. Let’s look at details

1 - There is a daily backup file of all configuration and sensors data. The location of these files is by default in the root directory but can be targeted to other drives, both local and network by selection in screen #2. Each day at the time entered in “Start Shift” (default =7:00am) a backup copy of data is created e.g. C:/dcbuxxx and depending on the length of the season and number of drying unit this file can be large. Each day the Optek program will look at the last backup and add 1 to the numerical value to name the next file e.g. c:/dcbuxxx+1.  In a 45 days season the will create 45 significant files and if left unpurged will accumulate year after year eventually using up memory space and causing problems. We have seen cpu lockups at each start of day. This is outside of the Optek Program control since it is under the Microsoft domain.  

Generally the only file need to preserve data if required is the most recent backup. Our recommendation is, after the season,  rename the most recent file dcdatyear and erase the remaining files. This will preserve the configuration data in folder fildatxx and the season sensor data for the year. Prudence would copy this file and c:/optek5 to a usb and secure its location.

2 - Along with the backup history there are season long files created each year and possibility multiple times in a year if additional seasons are used. This also can result in very large data folders such as C:/DCDAT (English, Portuguese, Romanian versions) and C:/CSDAT for Spanish. Each Season and or Year a new set of sensor data will be generated and the files grow with days of drying. If the previous season/year are not deleted upon starting a new season/year then the data folder becomes very large and can impact memory availability. The data files are denoted by F(C)XXY.ABzz where 

F or C is temperature form, XX is Year, Y is Season. AB is site code, zz in selnet number (net#). Our recommendation is to delete (provided #1 above is followed) all files in e.g DCDAT. Also the Bin Ticket records in the subfolder C:/DCDAT/Ticketxx can be deleted since this also will accumulated year after year. This will leave  C:/DCDAT with subfolders Offset and fildatxx. The ticket folder will be recreated upon the next usage whenever a bin process has been completed and populated with the new bin ticket information