pete_c
Guru
10th May, 2013 - 0900C
Started from scratch this morning.
1 - reset EEPROM
2 - reset RAM
Using PCA via serial link. Updated Firmware to 3.11C. Started with a new configuration.
1 - I changed IP to what I have been using and keys
2 - uploaded configuration.
3 - didn't work. No IP connectivity.
4 - I then went to a console (test Omnitouch 5.7)
5 - noticed that console didn't change IP nor keys.
6 - entered IP and keys on legacy Omnitouch (using a spare next to the touchscreen hub)
7 - I then downloaded configuration via PCA/Serial
8 - I can now ping and access via IP using PCA
9 - next I configured Omnistat
10 - stuck here - I can see the Omnistat via PCA serial and network connection.
11 - Keypad console, Omnitouch 5.7 and Omnitouch 5.7e's do not see the Omnistat (thermostat)
12 - reset ram - reset Omnistat (RC-80)
13 - Seeing the thermostat just fine with Snaplink and PCA (connected either via the network or serially). I do not see the thermostat though with the keypad, Omnitouch 5.7 and Omnitouch 5.7e's. I have unpowered them and reset the Omnitouch 5.7's
14 - I am currently using an Omnitouch 5.7 spare (connected to the Omnitouch serial hub) for testing.
15 - just noticed thermostat ambient temp went to zero and is staying there right now.
16 - unplugged power from thermostat. Still reading zero ambient temperature from PCA
17 - unplugged network cable - temperature readings from omnistat came right up on PCA.
18 - reset RAM with network cable off. PCA serially is still showing a thermostat temperature. No console though is showing any thermostat connected.
19 - reloaded old config via PCA - left unplugged rest of serial devices for time being (X10,UPB,Z-Wave, Russound).
During the write of the config - PCA appeared to stop. Cancelled write and did it again.
20 - Went to "test" Omnitouch and see my thermostat and temperature sensors just fine.
21 - left network cable off for time being.
I did notice that the status for the battery never went from 0 to a value during this testing. When I put my configuration back in noticed that the battery status went to a value of 229 (battery is good and that is where it was at before testing).
I am still not sure why my thermostat didn't show up other than some misconfiguration. That said though I did program my OPII in Florida with no issues (it is simplier though). I must have missed something; so will try again at another time. (reset eeprom and starting from scratch)
Stuck.
Its been a few hours running and consoles continue to show ambient thermostat temperature fine. Network connectivity appears fine. Time sync'd once so far. This is without the Russound, UPB, Z-Wave and X10 plugged in. I did leave PCA connected via one serial port. Left the IP Omnitouch screens on plus one Snaplink connection and coreserver.
10th May, 2013 - 1900C - 10 hours later - X10, UPB, Z-Wave and Russound serial devices unplugged. RC-80 connected instead of the Omnistat2. Time is still in sync, network connectivity is fine and ambient temperature is correct on OmniTouch (legacy and IP) screens, Snaplink screens, PCA (serially connected) and Coreserver. This doesn't make sense to me.
Will connect UPB PIM tomorrow and see what happens.
A few months ago switched the X-10 TW-523 for the XTB-IIR. Its been working fine and I do not think that would be an issue.
Time is fine.
11th May, 2013 - 0900C
Reconnected UPB, Z-Wave, Russound and X10.
11th May, 2013 - 1042C
Reconnected UPB, Z-Wave, Russound and X10 at around 0800c
Watching coreserver communications. The time could be in sync for hours then it goes off by 5 seconds to minutes at a time with a correction. Network connectivity either is really good while watching Snaplink or I see wierd disconnects. The Omnistat mostly is showing ambient temperature but occasionally does show zero degrees on the legacy serial consoles. I never see this on the IP connected Omnitouch consoles.
Then right now with the coreserver time corrections happening; it's kind of fixing the issue but it doesn't make sense to me that I need to do this. I also tested the network connection going to a switch but not connected to the main house network. Works this way never losing time. If I have it connected to the network then it starts with the time thing; then the disconnect from the network thing and then the Omnistat issue. If I disconnect the network then the time stays in sync looking at it with the keypad consoles and Omnitouch serial consoles.
I am here thinking its more of an issue with my configuration / firmware versus a hardware issue. That is only a guess.
I am though considering the purchase of another OPII board to swap this one out.
11th May, 2013 - 1427C
Time sync has been corrected one time for 5 seconds from 1207C earlier today.
TimeSyncTimer: Controller time 05/11/2013 12:07:55 out of sync by 5.0656419 seconds
This morning it was almost an every hour correction up to 30 seconds. Ambient Omnistat temperature on Omnitouch legacy is fine. No network issues.
11th May, 2013 - 1627C
No time syncs have occurred all day. This is getting very wierd. No changes, no unplugging any devices, nada...Its almost like before when the issue would go away by unplugging the network cable for a day or so. I have left the older RC80 Omnistat connected along with the HS serial plugin disabled.
11th May, 2013 ~ 2300C
Time sync off after 11 PM started every 10 minutes with an average of ~30 seconds off. Network connectivity is still OK and still seeing ambient Omnistat temps just fine. Going to disconnect Russound, Z-Wave, X10 and UPB serial connections again today. I will try adding one at a time to see maybe if one is an issues.
TimeSyncTimer: Controller time 05/12/2013 03:17:33 out of sync by 27.255793 seconds
TimeSyncTimer: Controller time 05/12/2013 03:28:34 out of sync by 26.113062 seconds
TimeSyncTimer: Controller time 05/12/2013 03:39:35 out of sync by 25.109735 seconds
TimeSyncTimer: Controller time 05/12/2013 03:50:34 out of sync by 26.26501 seconds
12th May, 2013 ~ 0400C
Just tried a Snaplink connection from laptop (wirelessly connected). It is very slow to connect versus testing on and off yesterday. Disconnected Russound, Z-Wave, X10 and UPB serial connections again. Also disconnected serial for PCA cable as I am currently not using PCA but rather just coreserver to look.
12th May, 2013 ~ 0757C
Unplugged board at PS and battery. Disconnected one AUX 12VDC out going to multiple devices which were not really related to the panel itself. Reconnected all serial devices that were earlier disconnected.
12th May, 2013 ~ 1122C
One time correction at 0835C and none afterwards.
TimeSyncTimer: Controller time 05/12/2013 08:35:54 out of sync by 6.3490704 seconds
12th May, 2013 ~ 1345C
No time corrections seen in coreserver. Network is fine. Serial comm to Omnitouch screens appears good. I might remove long patch network cable and reconnect network as originally configured in the next few hours. Next day or so if this continues will reconnect Omnistat2.
12th May, 2013 ~ 1621C
No time corrections seen in coreserver. Shut down coreserver. Removed long patch cable and reconnected to local switch. It did not connect as I could not ping IP. Reset RAM. It still wouldn't connect. I then unplugged it (power and battery). I also unplugged Omnitouch hub and Omnitouch video hub. Plugged the OPII back in and then Omnitouch hub. Network connectivity worked fine after this. I then restarted coreserver and watched it resync time. Will watch it for a bit now before reconnecting the Omnistat2.
12th May, 2013 ~ 1712C
Started again with the out of sync time. This time kept seeing a loss of connectivity. Streaming HD movie from NAS to another switch (never really paid attention before though).
TimeSyncTimer: Controller time 05/12/2013 17:12:55 out of sync by 5.2240474 seconds
CoreServer: CONNECTION STATUS: Retrying
CoreServer: CONNECTION STATUS: Retrying
TimeSyncTimer: Controller time 05/12/2013 20:40:52 out of sync by 10.2693693 seconds
TimeSyncTimer: Controller time 05/12/2013 20:51:34 out of sync by 26.1075619 seconds
CoreServer: CONNECTION STATUS: Retrying
CoreServer: CONNECTION STATUS: Retrying
TimeSyncTimer: Controller time 05/12/2013 21:02:32 out of sync by 28.404737 seconds
TimeSyncTimer: Controller time 05/12/2013 21:24:34 out of sync by 28.0853262 seconds
CoreServer: Starting up server (21:30)
Shut down Homeseer Plugin. Removed serial cable. Plugged in patch cable. Powered down and restarted OPII & Omnitouch hub.
TimeSyncTimer: Controller time 05/12/2013 21:45:36 out of sync by 24.151132 seconds
TimeSyncTimer: Controller time 05/12/2013 21:56:30 out of sync by 30.2364328 seconds
13th May, 2013 ~ 0800C
Time sync'd every 10 minutes up to 30 seconds off all night. Network was fine. Disconnected Russound, Homeseer, Z-wave UPB, and X10. Rest RAM, disconnected power.
13th May, 2013 ~ 1443C
No time syncs, network or comm issues. Reconnecting UPB PIM. Continue testing.
13th May, 2013 ~ 1854C
No time syncs, network or comm issues. Reconnected Omnistat2. Continue testing.
Started from scratch this morning.
1 - reset EEPROM
2 - reset RAM
Using PCA via serial link. Updated Firmware to 3.11C. Started with a new configuration.
1 - I changed IP to what I have been using and keys
2 - uploaded configuration.
3 - didn't work. No IP connectivity.
4 - I then went to a console (test Omnitouch 5.7)
5 - noticed that console didn't change IP nor keys.
6 - entered IP and keys on legacy Omnitouch (using a spare next to the touchscreen hub)
7 - I then downloaded configuration via PCA/Serial
8 - I can now ping and access via IP using PCA
9 - next I configured Omnistat
10 - stuck here - I can see the Omnistat via PCA serial and network connection.
11 - Keypad console, Omnitouch 5.7 and Omnitouch 5.7e's do not see the Omnistat (thermostat)
12 - reset ram - reset Omnistat (RC-80)
13 - Seeing the thermostat just fine with Snaplink and PCA (connected either via the network or serially). I do not see the thermostat though with the keypad, Omnitouch 5.7 and Omnitouch 5.7e's. I have unpowered them and reset the Omnitouch 5.7's
14 - I am currently using an Omnitouch 5.7 spare (connected to the Omnitouch serial hub) for testing.
15 - just noticed thermostat ambient temp went to zero and is staying there right now.
16 - unplugged power from thermostat. Still reading zero ambient temperature from PCA
17 - unplugged network cable - temperature readings from omnistat came right up on PCA.
18 - reset RAM with network cable off. PCA serially is still showing a thermostat temperature. No console though is showing any thermostat connected.
19 - reloaded old config via PCA - left unplugged rest of serial devices for time being (X10,UPB,Z-Wave, Russound).
During the write of the config - PCA appeared to stop. Cancelled write and did it again.
20 - Went to "test" Omnitouch and see my thermostat and temperature sensors just fine.
21 - left network cable off for time being.
I did notice that the status for the battery never went from 0 to a value during this testing. When I put my configuration back in noticed that the battery status went to a value of 229 (battery is good and that is where it was at before testing).
I am still not sure why my thermostat didn't show up other than some misconfiguration. That said though I did program my OPII in Florida with no issues (it is simplier though). I must have missed something; so will try again at another time. (reset eeprom and starting from scratch)
Stuck.
Its been a few hours running and consoles continue to show ambient thermostat temperature fine. Network connectivity appears fine. Time sync'd once so far. This is without the Russound, UPB, Z-Wave and X10 plugged in. I did leave PCA connected via one serial port. Left the IP Omnitouch screens on plus one Snaplink connection and coreserver.
10th May, 2013 - 1900C - 10 hours later - X10, UPB, Z-Wave and Russound serial devices unplugged. RC-80 connected instead of the Omnistat2. Time is still in sync, network connectivity is fine and ambient temperature is correct on OmniTouch (legacy and IP) screens, Snaplink screens, PCA (serially connected) and Coreserver. This doesn't make sense to me.
Will connect UPB PIM tomorrow and see what happens.
A few months ago switched the X-10 TW-523 for the XTB-IIR. Its been working fine and I do not think that would be an issue.
Time is fine.
11th May, 2013 - 0900C
Reconnected UPB, Z-Wave, Russound and X10.
11th May, 2013 - 1042C
Reconnected UPB, Z-Wave, Russound and X10 at around 0800c
Watching coreserver communications. The time could be in sync for hours then it goes off by 5 seconds to minutes at a time with a correction. Network connectivity either is really good while watching Snaplink or I see wierd disconnects. The Omnistat mostly is showing ambient temperature but occasionally does show zero degrees on the legacy serial consoles. I never see this on the IP connected Omnitouch consoles.
Then right now with the coreserver time corrections happening; it's kind of fixing the issue but it doesn't make sense to me that I need to do this. I also tested the network connection going to a switch but not connected to the main house network. Works this way never losing time. If I have it connected to the network then it starts with the time thing; then the disconnect from the network thing and then the Omnistat issue. If I disconnect the network then the time stays in sync looking at it with the keypad consoles and Omnitouch serial consoles.
I am here thinking its more of an issue with my configuration / firmware versus a hardware issue. That is only a guess.
I am though considering the purchase of another OPII board to swap this one out.
11th May, 2013 - 1427C
Time sync has been corrected one time for 5 seconds from 1207C earlier today.
TimeSyncTimer: Controller time 05/11/2013 12:07:55 out of sync by 5.0656419 seconds
This morning it was almost an every hour correction up to 30 seconds. Ambient Omnistat temperature on Omnitouch legacy is fine. No network issues.
11th May, 2013 - 1627C
No time syncs have occurred all day. This is getting very wierd. No changes, no unplugging any devices, nada...Its almost like before when the issue would go away by unplugging the network cable for a day or so. I have left the older RC80 Omnistat connected along with the HS serial plugin disabled.
11th May, 2013 ~ 2300C
Time sync off after 11 PM started every 10 minutes with an average of ~30 seconds off. Network connectivity is still OK and still seeing ambient Omnistat temps just fine. Going to disconnect Russound, Z-Wave, X10 and UPB serial connections again today. I will try adding one at a time to see maybe if one is an issues.
TimeSyncTimer: Controller time 05/12/2013 03:17:33 out of sync by 27.255793 seconds
TimeSyncTimer: Controller time 05/12/2013 03:28:34 out of sync by 26.113062 seconds
TimeSyncTimer: Controller time 05/12/2013 03:39:35 out of sync by 25.109735 seconds
TimeSyncTimer: Controller time 05/12/2013 03:50:34 out of sync by 26.26501 seconds
12th May, 2013 ~ 0400C
Just tried a Snaplink connection from laptop (wirelessly connected). It is very slow to connect versus testing on and off yesterday. Disconnected Russound, Z-Wave, X10 and UPB serial connections again. Also disconnected serial for PCA cable as I am currently not using PCA but rather just coreserver to look.
12th May, 2013 ~ 0757C
Unplugged board at PS and battery. Disconnected one AUX 12VDC out going to multiple devices which were not really related to the panel itself. Reconnected all serial devices that were earlier disconnected.
12th May, 2013 ~ 1122C
One time correction at 0835C and none afterwards.
TimeSyncTimer: Controller time 05/12/2013 08:35:54 out of sync by 6.3490704 seconds
12th May, 2013 ~ 1345C
No time corrections seen in coreserver. Network is fine. Serial comm to Omnitouch screens appears good. I might remove long patch network cable and reconnect network as originally configured in the next few hours. Next day or so if this continues will reconnect Omnistat2.
12th May, 2013 ~ 1621C
No time corrections seen in coreserver. Shut down coreserver. Removed long patch cable and reconnected to local switch. It did not connect as I could not ping IP. Reset RAM. It still wouldn't connect. I then unplugged it (power and battery). I also unplugged Omnitouch hub and Omnitouch video hub. Plugged the OPII back in and then Omnitouch hub. Network connectivity worked fine after this. I then restarted coreserver and watched it resync time. Will watch it for a bit now before reconnecting the Omnistat2.
12th May, 2013 ~ 1712C
Started again with the out of sync time. This time kept seeing a loss of connectivity. Streaming HD movie from NAS to another switch (never really paid attention before though).
TimeSyncTimer: Controller time 05/12/2013 17:12:55 out of sync by 5.2240474 seconds
CoreServer: CONNECTION STATUS: Retrying
CoreServer: CONNECTION STATUS: Retrying
TimeSyncTimer: Controller time 05/12/2013 20:40:52 out of sync by 10.2693693 seconds
TimeSyncTimer: Controller time 05/12/2013 20:51:34 out of sync by 26.1075619 seconds
CoreServer: CONNECTION STATUS: Retrying
CoreServer: CONNECTION STATUS: Retrying
TimeSyncTimer: Controller time 05/12/2013 21:02:32 out of sync by 28.404737 seconds
TimeSyncTimer: Controller time 05/12/2013 21:24:34 out of sync by 28.0853262 seconds
CoreServer: Starting up server (21:30)
Shut down Homeseer Plugin. Removed serial cable. Plugged in patch cable. Powered down and restarted OPII & Omnitouch hub.
TimeSyncTimer: Controller time 05/12/2013 21:45:36 out of sync by 24.151132 seconds
TimeSyncTimer: Controller time 05/12/2013 21:56:30 out of sync by 30.2364328 seconds
13th May, 2013 ~ 0800C
Time sync'd every 10 minutes up to 30 seconds off all night. Network was fine. Disconnected Russound, Homeseer, Z-wave UPB, and X10. Rest RAM, disconnected power.
13th May, 2013 ~ 1443C
No time syncs, network or comm issues. Reconnecting UPB PIM. Continue testing.
13th May, 2013 ~ 1854C
No time syncs, network or comm issues. Reconnected Omnistat2. Continue testing.