Decrease temp/fan logging

[JakeNL]

How can I disable/decrease the temperature logging?
the file "stats-633-262015267.txt" is updated every second, while I never ever look into this file. Which .ini file can I edit to reach my goal?

Crystalfontz LCD Blog

Looking for additional LCD resources? Check out our LCD blog for the latest developments in LCD technology.

 

[jc634]

From my lcd_631.ini file:

[module00]
id=2554230504
id_keypad=707705882
key_repeat_rate=250
port="\\\\?\\ftdibus#vid_0403+pid_fc0c+cf007255a#0000#\12386e0d1e0-8089-11d0-9ce4-08003e301f73\125"
speed=115200
log_stats="stats-631-2554230504.txt"
log_history="history-631-2554230504.csv"
history_period=60
history_length=1500

Change the history_period=60 to something larger. How much? Don't know. Perhaps CCadmin can enlighten us further.

JC

 

[JakeNL]

Yep, my lcd_633.ini is looking similar to this and I also was looking at the history_period, but I'm not sure what it means. 60 = 60/minute?

It would be nice when these INI files were documented somehow.

I just checked the value and changed it from 60->1 and also from 60 -> 180, but it doesn't change anything in the update speed.

 

[JakeNL]

Today I downloaded the program "process monitor" which does a good job at (for instance) looking at all write/read actions on the Hard disk. There I found out that 'cc2-service.exe is writing every 2 seconds to the logfile. I was expecting it to do it every second, but OK...

This is what my lcd_633.ini says (partly):

log_stats="stats-633-262015267.txt"
log_history="history-633-262015267.csv"
history_period=180
history_length=1500

It's this file that get's written to all the time: "stats-633-262015267.txt". I don't do anything with this data and when it's up to me, this should be stopped somehow.

Please let me know how to change this, changing the values of history period or length don't help.

 

[CF Mark]

The history settings only effect the history log file.

The stats file is updated every 2.5sec, and cant be turned off at the moment.

Why is this an issue for you?
The file never grows in size.

 

[JakeNL]

The history settings only effect the history log file.

The stats file is updated every 2.5sec, and cant be turned off at the moment.

Why is this an issue for you?
The file never grows in size.

Since I see my HD-led blinking every 2 seconds, I was wondering what was going on. I don't need the stats and therefore would like to turn it off. It's of course not a major issue, but if this can be fixed in a future release...

With the history log file, you mean "history-633-262015267.csv"? I looked into this file and I guess that 'history_period' is the interval in seconds and 'history_length' the amount of records in this file. I stretched the time interval and shortened the amount of records. This works!

Since I was using 'Process monitor' anyhow, I was also wondering why cc2service.exe tries to find the 'fraps.dll' file in several locations?

47027	19:46:50,9464313	cc2_service.exe	968	QueryOpen	C:\Program Files\CrystalControl2\FRAPS.DLL	NAME NOT FOUND	
47028	19:46:50,9466494	cc2_service.exe	968	QueryOpen	C:\WINDOWS\system32\FRAPS.DLL	NAME NOT FOUND	
47029	19:46:50,9469752	cc2_service.exe	968	QueryOpen	C:\WINDOWS\system\FRAPS.DLL	NAME NOT FOUND	
47030	19:46:50,9471260	cc2_service.exe	968	QueryOpen	C:\WINDOWS\FRAPS.DLL	NAME NOT FOUND	
47031	19:46:50,9472431	cc2_service.exe	968	QueryOpen	C:\Program Files\CrystalControl2\FRAPS.DLL	NAME NOT FOUND	
47032	19:46:50,9474227	cc2_service.exe	968	QueryOpen	C:\WINDOWS\system32\FRAPS.DLL	NAME NOT FOUND	
47033	19:46:50,9475627	cc2_service.exe	968	QueryOpen	C:\WINDOWS\FRAPS.DLL	NAME NOT FOUND	
47034	19:46:50,9477915	cc2_service.exe	968	QueryOpen	C:\WINDOWS\system32\wbem\FRAPS.DLL	NAME NOT FOUND	
47035	19:46:50,9481750	cc2_service.exe	968	QueryOpen	C:\Program Files\Microsoft SQL Server\80\Tools\Binn\FRAPS.DLL	NAME NOT FOUND	
47036	19:46:50,9483941	cc2_service.exe	968	QueryOpen	C:\Program Files\Common\Autodesk Shared\FRAPS.DLL	NAME NOT FOUND	
47037	19:46:50,9486424	cc2_service.exe	968	QueryOpen	C:\WINDOWS\system32\windowspowershell\v1.0\FRAPS.DLL	NAME NOT FOUND	
47038	19:46:50,9488592	cc2_service.exe	968	QueryOpen	C:\Program Files\Autodesk\DWG TrueView\FRAPS.DLL	NAME NOT FOUND

 

[Heffo]

By the look of some of the folders CC2 is trying to find the fraps.dll file in, I am assuming that it's not CC2 itself that is trying all these folders, but Windows inside a call to the LoadLibrary/LoadLibraryEx functions. When you try to open a DLL file, if windows can't find the file, it attempts to find it in several locations. The application's folder, the windows system folders, and the folders in the path environment string.

It's your environment string that I am assuming has directions to your Autodesk directory.

 

[JakeNL]

By the look of some of the folders CC2 is trying to find the fraps.dll file in, I am assuming that it's not CC2 itself that is trying all these folders, but Windows inside a call to the LoadLibrary/LoadLibraryEx functions. When you try to open a DLL file, if windows can't find the file, it attempts to find it in several locations. The application's folder, the windows system folders, and the folders in the path environment string.

It's your environment string that I am assuming has directions to your Autodesk directory.

Thanks for the explanation, but why would cc2 look for this dll file in the first place? Some plugin trying to use it? I haven't selected a plugin that would have anything to do with fraps.dll. (the file itself look like it's used for a fps game )

 

[jc634]

If you don't use fraps, just delete (or move) the file cc2_fraps.dll out of the CrystalControl2 directory. Won't harm anything to do this.

 

[moeburn]

I would also like to disable the stats and history logging. If I go into Task Manager and sort by CPU time, cc2_tray.exe always has the highest value, even higher than system (3 times higher, in fact). I can only assume this is because of the constant logging. Not only is it hard on the CPU, its hard on the HD, which has a limited number of read/write cycles. Would deleting the "log_stats="stats-633-4076742841.txt"" line stop the logging?

 

[CF Support2]

If you do not use the fan or temperature features of your CFA631 - or the CFA533 / CFA633 / CFA635 for that matter - you can disable the reporting in the module itself as part of it's boot state.

The easiest way would be to use 631WinTest:

http://www.crystalfontz.com/software/631WinTest

1 - Stop CC2 (to free up the VCP for WinTest)
2 - Start 631_WinTest
3 - WinTest should find your module, if not, select the appropriate COM port from the drop down
4 - Click on Packet Debugger
5 - Select Command 19 = Set Temperature Reporting
6 - In the data field, enter \000\000\000\000
7 - Click on Send Packet
8 - Select Command 16 = Set Fan Reporting
9 - In the data field, enter \000
10 - Click on Send Packet
11 - Verify your boot screen at this point, make any changes to the text, custom characters, contrast / backlight
12 - In the packet debugger, select Command 4 = Save current state as boot state
13 - Clear out any text in the data field
14 - Click on Send Packet

That will set your module to have fan and temperature reporting OFF by default when it powers up.

 

[CF Mark]

I would also like to disable the stats and history logging. If I go into Task Manager and sort by CPU time, cc2_tray.exe always has the highest value, even higher than system (3 times higher, in fact). I can only assume this is because of the constant logging. Not only is it hard on the CPU, its hard on the HD, which has a limited number of read/write cycles. Would deleting the "log_stats="stats-633-4076742841.txt"" line stop the logging?

CC2 logs to those files once every 2.5 seconds. Windows also has HDD write caching. The effect of this logging on your HDD's lifespan will be negligible.
How high is the CPU usage?

There isnt a setting in CC2 to disable temp/history logging.
There are two ways i can think of to get around this...
1. set an invalid file name for the log files in the INI
2. set the existing log files to be read-only

 

[moeburn]

CC2 logs to those files once every 2.5 seconds. Windows also has HDD write caching. The effect of this logging on your HDD's lifespan will be negligible.
How high is the CPU usage?

There isnt a setting in CC2 to disable temp/history logging.
There are two ways i can think of to get around this...
1. set an invalid file name for the log files in the INI
2. set the existing log files to be read-only

I actually thought of #2 originally, but all that did was make CC2 write to a file called "unknown.log" instead. That file is now over 2mb. I guess you're right, that wouldn't have very little effect on the HDD's lifespan in comparison to the 300GB per month read/write that goes on from downloading. But it might be whats causing the high CPU usage. I'll start a new thread about the CPU usage, since it is a little off-topic.

 

[moeburn]

If you do not use the fan or temperature features of your CFA631 - or the CFA533 / CFA633 / CFA635 for that matter - you can disable the reporting in the module itself as part of it's boot state.

The easiest way would be to use 631WinTest:

http://www.crystalfontz.com/software/631WinTest

1 - Stop CC2 (to free up the VCP for WinTest)
2 - Start 631_WinTest
3 - WinTest should find your module, if not, select the appropriate COM port from the drop down
4 - Click on Packet Debugger
5 - Select Command 19 = Set Temperature Reporting
6 - In the data field, enter \000\000\000\000
7 - Click on Send Packet
8 - Select Command 16 = Set Fan Reporting
9 - In the data field, enter \000
10 - Click on Send Packet
11 - Verify your boot screen at this point, make any changes to the text, custom characters, contrast / backlight
12 - In the packet debugger, select Command 4 = Save current state as boot state
13 - Clear out any text in the data field
14 - Click on Send Packet

That will set your module to have fan and temperature reporting OFF by default when it powers up.

Sorry to resurrect an old post, but I just wanted to tell you, that I followed those instructions exactly, and it does absolutely nothing to fan and temperature logging. All it does is prevent it from logging actual values, now instead it is logging null values every 2 seconds:

01/07/2013 13:07:17
CFA633 HW1.5 FW1.9

FANS:
sensor,name,power,power-min,power-max,auto-ctrl,auto-power,manual-power,avgtemp,avgtemp-min,avgtemp-max,rpm,rpm-min,rpm-max
fan01,Fan 01,100,100,100,0,100,100,NA,NA,NA,0,0,0
fan02,Fan 02,100,100,100,0,100,100,NA,NA,NA,NA,NA,NA
fan03,Fan 03,100,100,100,0,100,100,NA,NA,NA,NA,NA,NA
fan04,Fan 04,100,100,100,0,100,100,NA,NA,NA,NA,NA,NA

CONFIGURED TEMPS:
sensor,name,dow-uid,temp,temp-min,temp-max

HARDWARE TEMP SENSORS:
sensor,dow-uid,temp

CC2 logs to those files once every 2.5 seconds. Windows also has HDD write caching. The effect of this logging on your HDD's lifespan will be negligible.
How high is the CPU usage?

There isnt a setting in CC2 to disable temp/history logging.
There are two ways i can think of to get around this...
1. set an invalid file name for the log files in the INI
2. set the existing log files to be read-only

cc2_tray.exe has the highest cpu time of all applications, including high cpu system apps like dwm.exe, higher than cpu-using apps like utorrent.exe. Right now my system has been on for 3 days, cc2_tray.exe has cpu time of 5 hours. That's a lot of cpu time.

Tried #1, edited lcd_633.ini and changed log_stats to log_stats="**??**" (an invalid filename), but cc2 still tries to write to it every 2 seconds. Also tried deleting entry entirely, cc2 just writes to default filename. Tried #2, set existing file to read-only, cc2 just tries to write to it even MORE often, making the problem worse!
Can someone please find a way to turn off stats logging? Why on earth is cc2 configured to log null values, and why can't we turn it off? It makes cc2_tray.exe into a real cpu hog, not to mention it cripples my HDD's random access time!