oronomus Posted August 22, 2013 Posted August 22, 2013 I have 4 Venstar T1800 (Rev 2.30) thermostats. One is causing an occasional "cannot communicate with" issue. I have tried a couple of the usual fixes - remove and re-add, move access points around. Am using 94i and v4.05. Any suggestions from the following "Error - Out of Memory for Blocksize" messages: Thu 08/22/2013 06:35:09 AM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 08/22/2013 06:35:09 AM : MEM: :BATREQ :Alloc: *ERROR Out of Memory for blocksize= 38 (ask= 38) : Task[6] ProtocolReader PR-PROCESS pty=14 Thu 08/22/2013 06:35:09 AM : [iNST-SRX ] 02 50 14.91.96 23.98.2B 03 70 03 (03) Thu 08/22/2013 06:35:09 AM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Thu 08/22/2013 06:35:09 AM : MEM: :BATREQ :Alloc: *ERROR Out of Memory for blocksize= 38 (ask= 38) : Task[6] ProtocolReader PR-PROCESS pty=14 Thu 08/22/2013 06:35:10 AM : [iNST-SRX ] 02 50 14.91.96 23.98.2B 07 70 03 (03) Thu 08/22/2013 06:35:10 AM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 08/22/2013 06:35:10 AM : MEM: :BATREQ :Alloc: *ERROR Out of Memory for blocksize= 38 (ask= 38) : Task[6] ProtocolReader PR-PROCESS pty=14 Thu 08/22/2013 06:35:11 AM : [iNST-SRX ] 02 50 14.91.96 23.98.2B 03 70 03 (03) Thu 08/22/2013 06:35:11 AM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
LeeG Posted August 22, 2013 Posted August 22, 2013 I don't know about the memory message. ISY error messages usually have a number associated with them. Perhaps you are running the special alpha with extra debug capability or some other application that is having memory issues. The communication errors are the result of generally poor communication with the thermostat. The Hops Left=x count is changing on each communication and Hops Left=0 is as bad as it gets before a failure. Thu 08/22/2013 06:35:09 AM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 08/22/2013 06:35:09 AM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Thu 08/22/2013 06:35:10 AM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Thu 08/22/2013 06:35:11 AM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Michel Kohanim Posted August 23, 2013 Posted August 23, 2013 Hello oronomus, Those errors are not normal. Can you tell me: 1. Your model number 2. Your firmware version 3. What modules do you have installed 4. How many programs you have (approximately) With kind regards, Michel
oronomus Posted August 23, 2013 Author Posted August 23, 2013 Hello oronomus, Those errors are not normal. Can you tell me: 1. Your model number ISY994i 2. Your firmware version 4.05 3. What modules do you have installed Only ELK, although Open ADR also shows under product listing 4. How many programs you have (approximately) 47, of which 5 are disabled most of the time, and 5 run only when on vacation With kind regards, Michel See above. Also see below for status if helpful. Thank you for your help...
Michel Kohanim Posted August 23, 2013 Posted August 23, 2013 Thank you. Do you have Z-Wave and/or any other modules? With kind regards, Michel
LeeG Posted August 23, 2013 Posted August 23, 2013 It appears from the questions from Michel (see his last post this morning about ZWave) the memory message is from the ISY. That is something UDI will investigate. However, since the memory message appears after receiving a message from the thermostat I looked at those messages in more detail. The thermostat is sending a message to the ISY that Auto mode has been entered. If communication with the thermostat location was okay the message sequence would look something like below where the mode change message has a Max Hops=1 Hops Left=0 which is good communication (always use one hop). The messages from your trace show a Max Hops=3 Hops Left=0 (sometimes Hops Left=1) which indicates the thermostat is not getting the expected ACK which the PLM generates automatically so the thermostat is repeating the message with Max Hops bumped by 1 and retried. With Max Hops=3 it means the ACK from the PLM is not reaching the thermostat so the thermostat is repeating the mode change message. It would appear from the trace the thermostat is flooding the PLM/ISY with the mode change message because it is not getting ACKs back from the PLM. This may be causing the memory message. Independent of the memory message itself the communication between the PLM and the thermostat is very bad. Rather than moving existing devices around trying to find a combination that works without losing phase coupling I suggest adding an Access Point on the wall opposite to the thermostat location. SH has indicated the RF signal from the thermostat has some directional aspect to it with the best reception in front of the thermostat. If an Access Point in front of the thermostat improves/corrects the communication problem that is the solution. If it does not resolve the problem then look for something on the circuit powering the Dual Band device that is communicating with the thermostat. Fri 08/23/2013 09:52:11 AM : [iNST-SRX ] 02 50 1D.6C.D6 22.80.0B 01 70 03 (03) Fri 08/23/2013 09:52:11 AM : [std-Direct ] 1D.6C.D6-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 08/23/2013 09:52:11 AM : [ 1D 6C D6 1] CLIMD 3 If you still have the trace file from which the original snippet was obtained how many of the mode change messages appear in the trace (approx). Fri 08/23/2013 09:52:11 AM : [iNST-SRX ] 02 50 1D.6C.D6 22.80.0B 01 70 03 (03)
oronomus Posted August 23, 2013 Author Posted August 23, 2013 Thank you. Do you have Z-Wave and/or any other modules? With kind regards, Michel No Z-Wave. Only ELK Security Module.
oronomus Posted August 23, 2013 Author Posted August 23, 2013 Here is a current log with an Access Point (11.0D.4E) opposite the T-Stat (14.91.96) Fri 08/23/2013 01:45:19 PM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Fri 08/23/2013 01:45:19 PM : [iNST-TX-I1 ] 02 62 14 91 96 0F 6A 20 Fri 08/23/2013 01:45:19 PM : [iNST-ACK ] 02 62 14.91.96 0F 6A 20 06 (20) Fri 08/23/2013 01:45:21 PM : [iNST-SRX ] 02 50 14.52.5E 23.98.2B 47 11 01 LTONRR (01) Fri 08/23/2013 01:45:21 PM : [std-Cleanup ] 14.52.5E-->ISY/PLM Group=1, Max Hops=3, Hops Left=1 Fri 08/23/2013 01:45:21 PM : [iNST-DUP ] Previous message ignored. Fri 08/23/2013 01:45:26 PM : [iNST-SRX ] 02 50 14.91.96 23.98.2B 03 70 03 (03) Fri 08/23/2013 01:45:26 PM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 08/23/2013 01:45:30 PM : [iNST-SRX ] 02 50 14.91.96 23.98.2B 07 70 03 (03) Fri 08/23/2013 01:45:30 PM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 08/23/2013 01:45:30 PM : MEM: :BATREQ :Alloc: *ERROR Out of Memory for blocksize= 38 (ask= 38) : Task[6] ProtocolReader PR-PROCESS pty=14
oronomus Posted August 23, 2013 Author Posted August 23, 2013 If you still have the trace file from which the original snippet was obtained how many of the mode change messages appear in the trace (approx). Fri 08/23/2013 09:52:11 AM : [iNST-SRX ] 02 50 1D.6C.D6 22.80.0B 01 70 03 (03) Watching the Event Viewer, it is in a constant loop of spitting out the following three events (interrupted only by other commands or a change in other devices), so the 70 03 mode change event is occurring in an endless loop: Fri 08/23/2013 01:45:43 PM : [iNST-SRX ] 02 50 14.91.96 23.98.2B 07 70 03 (03) Fri 08/23/2013 01:45:43 PM : [std-Direct ] 14.91.96-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 08/23/2013 01:45:43 PM : MEM: :BATREQ :Alloc: *ERROR Out of Memory for blocksize= 38 (ask= 38) : Task[6] ProtocolReader PR-PROCESS pty=14
LeeG Posted August 23, 2013 Posted August 23, 2013 Thanks for the data, that is what it looked like was happening from the initial snippet. The flood of mode change messages must be causing the ISY to consume memory. From the date stamp on the last messages the situation must still be happening. I would try changing the mode at the thermostat to Off. If that does not stop the flood of messages then reset the thermostat. Insteon devices normally retry a failing message three times and stop. It looks like the thermostat is either in a loop retrying the mode message or it is designed not to stop until the message is ACKed. Either way the flood of messages has to be stopped. Once stopped it may be necessary to reboot the ISY to clear the memory issue caused by the message flood.
Michel Kohanim Posted August 23, 2013 Posted August 23, 2013 Thanks so very much to both. We have enough information to proceed with debugging. With kind regards, Michel
Recommended Posts
Archived
This topic is now archived and is closed to further replies.