[rafikW]

So far it running perfectly but I have one question: I see information on screen is presented only when in csv file there are more than 15 lines. If there is less - black screen without values is shown. Why is it that limit?

I honestly don't know. I didn't intentionally code anything to ignore a file with less than 15 lines, but it's possible that some of the logic to find the last line of the file (without having to read the whole thing in to memory) might have caused that. I'm guessing I never noticed because the SpeedFan log file very quickly gets longer than 15 lines, so the only time this would be an issue is for a few seconds right after the log file rolls each day. Since I'm not usually up and checking temps at midnight, I never noticed.

If you post a debug log (turn on debugging in both Kodi *and* in the SpeedFan settings) with a file of less than 15 lines, maybe something will jump out that I can fix.

In fact this not a big deal for me - I can append 15 'copy'paste' fake lines with the same values at the beginning of my input log file creation - I was just curious why such an odd logic in your app
OK, I will provide the log generated in situation when SID trying to (and failing) to display results with less then 15 rows in input file so you will see the reason.
Tell me SID's log file location because I was trying to find it and I just didn't found.

[EDIT] OK, I see why I did not found the SID's log - I need to turn on Kodi log and SID just will log to Kodi's log, not to separate log.

[rafikW]

Hi, here you are the log:

10:26:02 128490.687500 T:1344373824 NOTICE: [SpeedFan Info] script version 0.7.2 started
10:26:02 128490.687500 T:1344373824 NOTICE: [SpeedFan Info] debug logging set to true
10:26:02 128490.750000 T:1344373824 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.IndexError'>
Error Contents: string index out of range
Traceback (most recent call last):
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 55, in onInit
self._populate_from_all_logs()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 158, in _populate_from_all_logs
self._populate_from_log()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 168, in _populate_from_log
temps, speeds, voltages, percents = self._parse_log()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 109, in _parse_log
first, last = self._read_log_file()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 287, in _read_log_file
first = self._parse_line( f, 0 )
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 263, in _parse_line
if read_str[offset - 1] == '\n':
IndexError: string index out of range
-->End of Python script error report<--
10:26:05 128493.203125 T:1344373824 NOTICE: [SpeedFan Info] script stopped



I suspect it could be related to values in column "Seconds"
When I was performing my tests I simply generated some values for that column and probably I did not followed the order.
Do you know how those values are calculated?

[rafikW]

I did more tests and I'm really confused with the results.
File:
Seconds NAS.temp NAS.speed
115712 42.0 3000
115718 43.0 5000
115719 45.0 6000
115749 40.0 3000
115812 42.0 3000
115818 43.0 5000
115819 45.0 6000
115949 40.0 3000
116912 42.0 3000
116718 43.0 5000
116719 45.0 6000
116349 40.0 3000
117712 42.0 3000
117718 43.0 5000
117719 45.0 6000
is properly maintained - last row's values 45.0 and 6000 are presented.
But when I remove last two lines, so the file looks like:
Seconds NAS.temp NAS.speed
115712 42.0 3000
115718 43.0 5000
115719 45.0 6000
115749 40.0 3000
115812 42.0 3000
115818 43.0 5000
115819 45.0 6000
115949 40.0 3000
116912 42.0 3000
116718 43.0 5000
116719 45.0 6000
116349 40.0 3000
117712 42.0 3000

there is empty window.

[pkscout]

Hi, here you are the log:

10:26:02 128490.687500 T:1344373824 NOTICE: [SpeedFan Info] script version 0.7.2 started
10:26:02 128490.687500 T:1344373824 NOTICE: [SpeedFan Info] debug logging set to true
10:26:02 128490.750000 T:1344373824 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.IndexError'>
Error Contents: string index out of range
Traceback (most recent call last):
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 55, in onInit
self._populate_from_all_logs()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 158, in _populate_from_all_logs
self._populate_from_log()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 168, in _populate_from_log
temps, speeds, voltages, percents = self._parse_log()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 109, in _parse_log
first, last = self._read_log_file()
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 287, in _read_log_file
first = self._parse_line( f, 0 )
File "/storage/.kodi/addons/script.speedfaninfo/default.py", line 263, in _parse_line
if read_str[offset - 1] == '\n':
IndexError: string index out of range
-->End of Python script error report<--
10:26:05 128493.203125 T:1344373824 NOTICE: [SpeedFan Info] script stopped



I suspect it could be related to values in column "Seconds"
When I was performing my tests I simply generated some values for that column and probably I did not followed the order.
Do you know how those values are calculated?

OK, that's a bug of some sort. I'll see if I can take a look at it this weekend.

[bearhntr]

OK... I admit defeat.

I have followed all of these steps. Installed the latest version of SPEEDFAN, enabled the logging option, and then go through the tabs to turn on the LOGGED setting.

I can see the .CSV file getting created with the name that the HELP FILE says it will use. I open it in NOTEPAD and I see the columns of information with values.

I do not understand how you get the files to name with .TEMP, .CPU, that you mention.

I have scoured the computer for this README file that you mention for your add-on, and I am not finding that.

Please assist....as you can see - I am getting these .CSV files - but when I use your add-on I get a blank display.

Seconds Temp1 Temp2 Temp3 HD2 HD0 HD1 Temp1 Temp2 Core 0 Core 1 Fan1 Fan2 Fan3
73412 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 41.0 1342 752 2150
73414 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 41.0 1342 752 2150
73417 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 41.0 1339 752 2157
73420 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 41.0 1339 752 2157
73423 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 41.0 1339 751 2163
73426 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 40.0 42.0 1339 751 2163
73429 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 42.0 1347 751 2163
73433 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 40.0 42.0 1347 751 2163
73436 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 42.0 1342 750 2170
73439 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 41.0 1342 750 2170
73442 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 38.0 41.0 1342 752 2150
73445 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 41.0 1342 752 2150
73448 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 40.0 42.0 1342 751 2150
73451 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 41.0 1342 751 2150
73454 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 42.0 1345 750 2150
73457 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 41.0 1345 750 2150
73460 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 42.0 1339 751 2157
73463 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 42.0 1339 751 2157
73466 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 43.0 1342 751 2157
73469 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 42.0 1342 751 2157
73472 42.0 -128.0 34.0 43.0 35.0 42.0 27.8 29.8 39.0 42.0 1337 751 2163
73476 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 40.0 42.0 1337 751 2163
73478 42.0 -128.0 33.0 43.0 35.0 43.0 27.8 29.8 39.0 42.0 1342 751 2163
73482 42.0 -128.0 33.0 43.0 35.0 43.0 27.8 29.8 39.0 41.0 1342 751 2163
73485 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 40.0 46.0 1342 752 2157
73488 42.0 -128.0 33.0 43.0 35.0 43.0 27.8 29.8 39.0 41.0 1342 752 2157
73491 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 40.0 41.0 1342 751 2157
73494 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 39.0 41.0 1342 751 2157
73497 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 39.0 41.0 1345 751 2150
73500 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 39.0 41.0 1345 751 2150
73503 42.0 -128.0 33.0 43.0 35.0 43.0 27.8 29.8 39.0 42.0 1342 751 2163
73506 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 39.0 43.0 1342 751 2163
73509 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 40.0 42.0 1345 751 2170
73512 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 41.0 43.0 1345 751 2170
73515 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 39.0 43.0 1345 751 2163
73518 42.0 -128.0 34.0 43.0 35.0 43.0 27.8 29.8 40.0 43.0 1345 751 2163


I have tried everything, but I see no way to change the names of the files that SpeedFan is saving.

Bearhntr

[pkscout]

You have to change the name of the sensors from within Speedfan. I've found the GUI kind of erratic, but if I double click on the name of the sensor it usually gives me a way to change the name. If not that, try right clicking. I also found this thread about changing names:

http://forums.overclockers.co.uk/showthr...?p=7517541

It mentions selecting the sensor and hitting F2.

Hope that helps.

[bearhntr]

PK.

You are the best. I would never have figured that out. It was HIGHLIGHT A SENSOR >> PRESS [F2] and change the name to include the extensions.

Now I just gotta figure out how to put that as a sub-menu on the home screen - so that I do not have to go to SYSTEM >> ADD-ONS >> yadda yadda yadda to get to it.


Thanks again,
*BH*

[rafikW]

Hi,
Using Keymap Editor you can assign any of TV remote's button to launch speedfan window.
I did that so when I press "red" button on my TV remote it popup Compact Display window of speedfan.
One question only: would it be possible that pressing again assigned button Compact Display window will be closed? In current speedfan version in order to close that Compact Display window it is required to press "Back" button on TV remote.

[pkscout]

Hi,
Using Keymap Editor you can assign any of TV remote's button to launch speedfan window.
I did that so when I press "red" button on my TV remote it popup Compact Display window of speedfan.
One question only: would it be possible that pressing again assigned button Compact Display window will be closed? In current speedfan version in order to close that Compact Display window it is required to press "Back" button on TV remote.

Unfortunately, no. At least I'm pretty sure the answer is no. You have to define in the addon what key commands will do what, and there's no way to know what command someone might have chosen. I used to use a remote keymap program that had some logic to it, so it would know if SpeedFan was running and quit it if I hit the same key again. But the key mapper got kind of temperamental, so I went with something else that doesn't have the logic pieces. Now I do the same thing you do. I hit a key to launch speed fan and BACK to quit it.

[rafikW]

Hi,
Using Keymap Editor you can assign any of TV remote's button to launch speedfan window.
I did that so when I press "red" button on my TV remote it popup Compact Display window of speedfan.
One question only: would it be possible that pressing again assigned button Compact Display window will be closed? In current speedfan version in order to close that Compact Display window it is required to press "Back" button on TV remote.

Unfortunately, no. At least I'm pretty sure the answer is no. You have to define in the addon what key commands will do what, and there's no way to know what command someone might have chosen. I used to use a remote keymap program that had some logic to it, so it would know if SpeedFan was running and quit it if I hit the same key again. But the key mapper got kind of temperamental, so I went with something else that doesn't have the logic pieces. Now I do the same thing you do. I hit a key to launch speed fan and BACK to quit it.

OK, thanks for explanation, so we have to live with it as it is, not a big deal

[johntaaffe]

I'm not sure if this is an issue with the latest version of Speedfan or if this will help anyone else, but I could only get Celsius temps to display in Kodi. Might be an issue with the latest release of Speedfan, but it will only log in Celsius. Switching between Celsius and Fahrenheit in Kodi only changes whether "F" or "C" is used.

I played around with _parse_log in default.py and added a Fahrenheit conversion when Fahrenheit is selected in Kodi. Here is the github fork I made if anyone else has run into this issue:

https://github.com/johnftaaffe/script.speedfaninfo

This will be unnecessary for anyone only using Celsius and should be avoided by anyone somehow already logging in Fahrenheit.

[johntaaffe]

Here it is in action: http://i.imgur.com/gilZwyi.jpg

edit: under load: http://i.imgur.com/30Ir3WF.jpg

[pkscout]

I'm not sure if this is an issue with the latest version of Speedfan or if this will help anyone else, but I could only get Celsius temps to display in Kodi. Might be an issue with the latest release of Speedfan, but it will only log in Celsius. Switching between Celsius and Fahrenheit in Kodi only changes whether "F" or "C" is used.

I played around with _parse_log in default.py and added a Fahrenheit conversion when Fahrenheit is selected in Kodi. Here is the github fork I made if anyone else has run into this issue:

https://github.com/johnftaaffe/script.speedfaninfo

This will be unnecessary for anyone only using Celsius and should be avoided by anyone somehow already logging in Fahrenheit.

I haven't updated SpeedFan in forever, so I haven't seen this yet. I'm out of town right now, but when I get back I'll look into this and see if I can duplicate it.

[johntaaffe]

I'm not sure if this is an issue with the latest version of Speedfan or if this will help anyone else, but I could only get Celsius temps to display in Kodi. Might be an issue with the latest release of Speedfan, but it will only log in Celsius. Switching between Celsius and Fahrenheit in Kodi only changes whether "F" or "C" is used.

I played around with _parse_log in default.py and added a Fahrenheit conversion when Fahrenheit is selected in Kodi. Here is the github fork I made if anyone else has run into this issue:

https://github.com/johnftaaffe/script.speedfaninfo

This will be unnecessary for anyone only using Celsius and should be avoided by anyone somehow already logging in Fahrenheit.

I haven't updated SpeedFan in forever, so I haven't seen this yet. I'm out of town right now, but when I get back I'll look into this and see if I can duplicate it.

I just installed SpeedFan/SpeedFanInfo a few days ago, I'm assuming that there used to be an option for logging in Fahrenheit in SpeedFan? In the latest version even with the display temp set as Fahrenheit it still logs in Celsius.

Thanks for the great add-on by the way. It was exactly what I was looking for.

[pkscout]

SpeedFan Information Display 0.7.3~beta1 Released

v.0.7.3~beta1
- convert Celcius in Speedfan log to Fahrenheit when Fahrenheit is selected in settings

I'm thinking this has been a long standing issue with SpeedFan Information Display, but I suspect basically everyone (including myself) views the logs in Celsius. Anyway, thanks to johntaffe for reporting this.

This update is currently available in my beta repo. If you want to install the update, you can download my repo from:

https://github.com/pkscout/repository.sk...-1.1.0.zip

I'll test here for a few days and then put in a pull request to get this in the main Kodi repo.