Startup errors

[MalcolmS]

When I restarted HS 2 today I get the following mcsTeemperature errors:


10/05/2007 15:12:06 ~!~mcsTemperature~!~Sensor 02 C600080037F7F010 DS1820 OK reported by Temp05 has not yet been recorded by mcsTemperature
10/05/2007 15:12:06 ~!~mcsTemperature~!~Sensor C600080037F7F010 is reported as Temperature sensor DS1820 but known by mcsTemperature as type 0
10/05/2007 15:12:06 ~!~mcsTemperature~!~Sensor 03 7E00080013514210 DS1820 OK reported by Temp05 has not yet been recorded by mcsTemperature
10/05/2007 15:12:06 ~!~mcsTemperature~!~Sensor 7E00080013514210 is reported as Temperature sensor DS1820 but known by mcsTemperature as type 0

If I go to setup both of these sensors (02 & 03) are already defined. What does the errror mean and what should I do to eliminate this? I'm on v5.2.0

Malcolm

[MalcolmS]

Not sure if it's related at all but I've now noticed that I'm getting these two errors also:

10/05/2007 15:18:44 ~!~mcsTemperature~!~ EvaluateTemperatureTrigger: on line 50 Subscript out of range
10/05/2007 15:19:07 ~!~mcsTemperature~!~ Log_Temperature: on line 540 Subscript out of range

every 60 seconds. Not sure why as I only collect temp data every 15 minutes...

How can I track these down?

[MalcolmS]

my sensor errors have disappeared but I'm still getting the "Subscript out of range" errors and no temperature readings. Can anyone help me track this down please??

[Michael McSharry]

The sync with Temp05 and mcsTemperature occurs at HS startup. That is where the first set of messages come from. The subscript range error is due to no sensors being recognized.

The mcsTemperature.ini file contains the info about what sensors the plugin knows about from the Temp05. It could be that this file is not valid and you may want to go to a backup or at least compare with a backup.

If you enable the debut and raw data to log options and then restart HS there will be info in the log that you can post that may help understand.

[MalcolmS]

Before I'd read this post I found an old Word document that I'd created some time ago with screenshots of each of the mcsTemperature setup pages (the old style not the web ones).

So I thought the simplest way was to delete my mcsTemperature.ini file and start from scratch. I did all that and mcsTemperature was working perfectly again! Heaven.

Even though I've still a list as long as my arm of other HS1 to HS2 upgrade problems to fix I took some time to setup weatherxml for forecasts whcih I haven't done before - very impressive.

However!

This morning HS2 crashed (not sure yet why still investigating) this morning. When I restart my mscTemperature errors are back again!

12/05/2007 09:35:29 ~!~Info~!~Initializing Plug-in: mcsTemperature
12/05/2007 09:35:29 ~!~mcsTemperature~!~Version 5.2.0 Registered with Homeseer
12/05/2007 09:35:30 ~!~COM Plugin~!~Calling InitIO
12/05/2007 09:35:30 ~!~mcsTemperature~!~InitINIVariables sensorType=0, index=61 on line 5240 Subscript out of range
12/05/2007 09:35:31 ~!~mcsTemperature~!~Last temperature sample recorded at 12/05/2007 09:21:49
12/05/2007 09:35:31 ~!~mcsTemperature~!~Last forecast sample recorded at 12/05/2007 09:27:01
12/05/2007 09:35:31 ~!~Info~!~Finished initializing plug-in mcsTemperature


12/05/2007 09:36:32 ~!~mcsTemperature~!~Temp05/08 Comm Port 2 Opened
12/05/2007 09:36:32 ~!~mcsTemperature~!~ EvaluateTemperatureTrigger: on line 50 Subscript out of range
12/05/2007 09:36:48 ~!~mcsTemperature~!~Sensor 04 B9000800382FF710 DS1820 OK reported by Temp05 has not yet been recorded by mcsTemperature
12/05/2007 09:36:48 ~!~mcsTemperature~!~Sensor B9000800382FF710 is reported as Temperature sensor DS1820 but known by mcsTemperature as type 0
12/05/2007 09:36:52 ~!~mcsTemperature~!~ TemperatureReceiveVersion5 on line 750 Subscript out of range
12/05/2007 09:36:52 ~!~mcsTemperature~!~ TemperatureReceiveVersion5 on line 750 Subscript out of range
12/05/2007 09:37:33 ~!~mcsTemperature~!~ EvaluateTemperatureTrigger: on line 50 Subscript out of range
12/05/2007 09:37:48 ~!~mcsTemperature~!~ Log_Temperature: on line 540 Subscript out of range
12/05/2007 09:38:33 ~!~mcsTemperature~!~ EvaluateTemperatureTrigger: on line 50 Subscript out of range
12/05/2007 09:38:48 ~!~mcsTemperature~!~ Log_Temperature: on line 540 Subscript out of range
12/05/2007 09:39:33 ~!~mcsTemperature~!~ EvaluateTemperatureTrigger: on line 50 Subscript out of range
12/05/2007 09:39:48 ~!~mcsTemperature~!~ Log_Temperature: on line 540 Subscript out of range


And guess what, I never got around to creating a copy of the .ini file.

I'm guessing that during the crash the .ini file was corrupted in some way? I've had a look at the file and I'm afraid I can't see anything wrong with it. Can anyone?

[Michael McSharry]

Two of your devices are recorded as being from index #61 and #62 from Temp05. The Temp05 maintains a set of indexes for discretes and another index for other devices. These indexes are constructed based upon the DIS command response. Where the 61 and 62 are coming from is the item of interest. The debug during startup should provide a clue. The ini file can be edited in the [DEVICES] group as shown below to change 61 and 62 to 03 and 04 so it will initialize properly. You should also get the version of mcsTemperature from the message board which should be in the 5.5 sequence vs. the 5.2 that you are running so my source matches what you are running and eliminate the change that we are chasing after something that has already been fixed.

[Database]
R1="R1,0,1"
R2="R2,0,1"
R3="R3,0,1"
R4="R4,0,1"
_65="R5,0,1"
_67="R8,0,1"
_68="R9,0,1"

[Devices]
B0000800135B3710="R1,01:01,,0,0"
C600080037F7F010="R2,02:02,,0,0"
7E00080013514210="R3,03:61,,0,0"
B9000800382FF710="R4,04:62,,0,0"

[MalcolmS]

[Michael McSharry]

What I posted was your ini setting to provide context. You should change the values so the values in the 60's are replaced. The debug information needs to include the handshake between HS and the Temp05 and include the first pass of data source by the Temp05. This may be 5 or so minutes depending upon your settings for the Temp05 to deliver data.

[MalcolmS]

Thanks Michael. I'm afraid I'm still playing catch up a bit in understanding this, but I think I'm getting close! Right at this minute my mcsTemperature.ini file looks like this.

[Database]
R3="R3,0,1"
R4="R4,0,1"
_65="R5,0,1"
_67="R8,0,1"
_68="R9,0,1"
R1="R1,0,1"
R2="R2,0,1"
[Devices]
7E00080013514210="R3,03:61, 0,0,0"
B9000800382FF710="R4,04:62, 0; 0,, 0"

So now it's lost sensors R1 and R2. Correct? Right now the I/O stream direct from the Temp05 is showing:

14:30:59 | Reading Sensors...
14:31:02 | Temp #01[B0000800135B3710]=28.68C
14:31:04 | Temp #02[C600080037F7F010]=10.93C
14:31:06 | Temp #03[7E00080013514210]=09.81C
14:31:08 | Temp #04[B9000800382FF710]=15.18C

Which means R1 and R2 are the Temp #01 and Temp #02 sensors. Correct? So if I add the following to the [Devices] section of mcsTemperature.ini I should be ok?

B0000800135B3710="R1,01:01, 0,0,0"
C600080037F7F010="R2,02:02, 0; 0,, 0"

However I haven't made this change yet as I'm confused about the 61, 62 question. I did as you asked and set up the debug option and got the following...

[now attached as txt file as HS Board message was too long]

I can see from that mcsTemperature reporting that it doesn't know about sensors 01 and 02 but the 61 and 62 you mentioned don't seem to come until later? I'm confused. What can you tell me?

Also can you tell me why I'm getting the "Subscript out of range" messages every 1 minute as I've mcsTemperature and the Temp05 only to take readings every 15 minutes? Thanks again.

[MalcolmS]

Michael - any ideas how i can get my R1 and R2 sensors re-established??

[Michael McSharry]

The edit I mentioned is:

from

[Database]
R1="R1,0,1"
R2="R2,0,1"
R3="R3,0,1"
R4="R4,0,1"
_65="R5,0,1"
_67="R8,0,1"
_68="R9,0,1"

[Devices]
B0000800135B3710="R1,01:01,,0,0"
C600080037F7F010="R2,02:02,,0,0"
7E00080013514210="R3,03:61,,0,0"
B9000800382FF710="R4,04:62,,0,0"

to

[Database]
R1="R1,0,1"
R2="R2,0,1"
R3="R3,0,1"
R4="R4,0,1"
_65="R5,0,1"
_67="R8,0,1"
_68="R9,0,1"

[Devices]
B0000800135B3710="R1,01:01,,0,0"
C600080037F7F010="R2,02:02,,0,0"
7E00080013514210="R3,03:03,,0,0"
B9000800382FF710="R4,04:04,,0,0"

To understand why the 61 and 62 showed up the initial interaction with the Temp05 at the HS startup is needed ...

The debug information needs to include the handshake between HS and the Temp05 and include the first pass of data source by the Temp05. This may be 5 or so minutes depending upon your settings for the Temp05 to deliver data.

Each minute mcsTemperature evaluates trigger conditions so it looking for devices that are indexed with 61 and 62 and these indexes (subscripts) are out of range.

[MalcolmS]

To understand why the 61 and 62 showed up the initial interaction with the Temp05 at the HS startup is needed ...

That's twice you've asked for that. I'm guessing that's because I still haven't given you it then??

Sorry, but you'll need to be more to be more explicit because I thought I now had (admitedly not in the first post...)

[Michael McSharry]

My mistake, I see the attachment.

Note the line when it is reading the temperature from the Temp05 and the Temp05 provides a temperature sensor #61. The lines also have a \par which I do not recognize. These \par items are causing mcsTemperature to not recognize what the device types are. The #61 is causing the subscript problems.

13/05/2007 10:17:45 ~!~mcsTemperature~!~Temp05/08 Data: Temp #61=09.93C\par

In the response to the DIS command it returned the following sensors with indexes 01, 02, 03, and 04. No index 61 returned. The 03 sensor was not processed due to the \par text after the 03 and before the serial number.

13/05/2007 10:17:42 ~!~mcsTemperature~!~Sensor 01 B0000800135B3710 DS1820 OK reported by Temp05 has not yet been recorded by mcsTemperature\par
13/05/2007 10:17:42 ~!~mcsTemperature~!~Sensor 02 C600080037F7F010 DS1820 OK reported by Temp05 has not yet been recorded by mcsTemperature\par

13/05/2007 10:17:42 ~!~mcsTemperature~!~Sensor 04 B9000800382FF710 DS1820 OK reported by Temp05 has not yet been recorded by mcsTemperature\par

Could it be that you have some form of debug mode of the Temp05 turned on? It is just not returning the stream of data that is normal

[MalcolmS]

Thanks Michael, Not aware of any debug setting on the Temp05. However I did a soft reset and set the mcsTemp debug options again and the readings now seem to be 'clean'.

[MalcolmS]

quick update

everything had been running fine until last night when these errors reappeared. Don't know what's causing it but I did another quick soft reset of the temp05 and edited the mcstemperature.ini to remove the "61" and "62" settings again and everything seems to be fine again.

Will keep an eye on it to see if I can track down why this is happening...