alexwheel2001 Posted May 19, 2011 Share Posted May 19, 2011 I can't link my MS with my ISY. Everytime I try to link it shows: Node not added - failed reading Links. I thought the reason of this problem was the 2443, so I bought 3 more access point 2443 but I still have the same problem. I disconnected my Ventar adapter 2441v and it didn't do anything to improve the error. Can someone help me to fix this issue? Link to comment Share on other sites More sharing options...
LeeG Posted May 19, 2011 Share Posted May 19, 2011 alexwheel2001 Place the motion sensor near an Access Point. Put the motion sensor into linking mode by pressing the Set button on the motion sensor for 4-5 seconds. Use New INSTEON Device, specify Address, Name and select the Device Type for the motion sensor (important as this is the only way a motion sensor can be added to the ISY). If the above does not work, run Tools | Diagnostics | Event Viewer with Device communications events selected from pulldown (important). Repeat the above process and post the event trace. Lee Link to comment Share on other sites More sharing options...
alexwheel2001 Posted May 19, 2011 Author Share Posted May 19, 2011 Thanks Lee, Now I can link the 4 devices (2 triggerLinc & 2 Motion sensors) to my ISY. Link to comment Share on other sites More sharing options...
jackal Posted August 7, 2011 Share Posted August 7, 2011 Hi, I couldn't link despite trying all the ways that was advised. Could you take a look at my log? Sun 07/31/2011 06:41:05 PM : [14 5D B4 1 ] Failed getting engine version. Reverting to i1. Sun 07/31/2011 06:41:34 PM : [ 12 C2 49 4] DOF 0 Sun 07/31/2011 06:41:34 PM : [ 5 6A 80 1] ST 0 Sun 07/31/2011 06:41:34 PM : [ 12 C2 49 4] ST 0 Sun 07/31/2011 06:41:40 PM : [ 14 5D B4 1] ** Not added ** Remove Device Links failed Sun 07/31/2011 06:41:40 PM : ---- All Remaining Device Added ---- Sun 07/31/2011 06:41:40 PM : [All ] Writing 0 bytes to devices Sun 07/31/2011 06:42:52 PM : ---- Initializing the linked devices ---- Sun 07/31/2011 06:42:52 PM : ---- All Linked Devices are now initialized ---- Sun 07/31/2011 06:42:52 PM : ---- Add remaining devices ---- Sun 07/31/2011 06:42:52 PM : [ 14 5D B4 1] Removing all links Sun 07/31/2011 06:43:14 PM : [14 5D B4 1 ] Failed getting engine version. Reverting to i1. Sun 07/31/2011 06:43:44 PM : [ 14 5D B4 1] ** Not added ** Remove Device Links failed Sun 07/31/2011 06:43:44 PM : ---- All Remaining Device Added ---- Sun 07/31/2011 06:43:44 PM : [All ] Writing 0 bytes to devices Sun 07/31/2011 06:46:27 PM : ---- Initializing the linked devices ---- Sun 07/31/2011 06:46:27 PM : ---- All Linked Devices are now initialized ---- Sun 07/31/2011 06:46:27 PM : ---- Add remaining devices ---- Sun 07/31/2011 06:46:27 PM : [ 14 5D B4 1] Removing all links Sun 07/31/2011 06:46:27 PM : [14 5D B4 1 ] Querying engine version Sun 07/31/2011 06:46:27 PM : [iNST-ACK ] 02 62 14.5D.B4 0F 0D 00 06 (00) Sun 07/31/2011 06:46:36 PM : [iNST-ACK ] 02 62 14.5D.B4 0F 0D 00 06 (00) Sun 07/31/2011 06:46:45 PM : [iNST-ACK ] 02 62 14.5D.B4 0F 0D 00 06 (00) Sun 07/31/2011 06:46:49 PM : [14 5D B4 1 ] Failed getting engine version. Reverting to i1. Sun 07/31/2011 06:46:49 PM : [14 5D B4 1 ] Using engine version i2 Sun 07/31/2011 06:46:49 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/31/2011 06:46:53 PM : [iNST-ERX ] 02 51 14 5D B4 19 6F 06 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 00 Sun 07/31/2011 06:46:53 PM : [Extended-Direct][14.5D.B4-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sun 07/31/2011 06:46:53 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/31/2011 06:46:57 PM : [iNST-ERX ] 02 51 14 5D B4 19 6F 06 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 00 Sun 07/31/2011 06:46:57 PM : [Extended-Direct][14.5D.B4-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sun 07/31/2011 06:46:57 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 02 0F FF 08 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/31/2011 06:47:06 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 02 0F FF 08 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/31/2011 06:47:15 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 02 0F FF 08 00 00 00 00 00 00 00 00 00 06 (00) Sun 07/31/2011 06:47:19 PM : [ 14 5D B4 1] ** Not added ** Remove Device Links failed Sun 07/31/2011 06:47:19 PM : ---- All Remaining Device Added ---- Sun 07/31/2011 06:47:19 PM : [All ] Writing 0 bytes to devices Link to comment Share on other sites More sharing options...
LeeG Posted August 7, 2011 Share Posted August 7, 2011 jackal The motion sensor is taking 4 seconds to respond to commands. The command to write the link record which clears the existing link records failed to get a response. The motion sensor may have timeout out of linking mode as there was communication (albeit slow) between the motion sensor and the ISY up to that point Is this a V1 or V2 motion sensor? Are there Venstar tstat adaptors in use? If so unplug the dongle temporarily. Suggest trying it again with a fresh battery. Lee Link to comment Share on other sites More sharing options...
jackal Posted August 8, 2011 Share Posted August 8, 2011 The motion detector is version 2. I tried with a new battery ... still no luck. I dont have any venstar adapters. Any other suggestions? Link to comment Share on other sites More sharing options...
jackal Posted August 8, 2011 Share Posted August 8, 2011 The motion detector is version 2. I tried with a new battery ... still no luck. I dont have any venstar adapters. Any other suggestions? This is my new log: ===================================== Sun 08/07/2011 05:45:26 PM : ---- Initializing the linked devices ---- Sun 08/07/2011 05:45:26 PM : ---- All Linked Devices are now initialized ---- Sun 08/07/2011 05:45:26 PM : ---- Add remaining devices ---- Sun 08/07/2011 05:45:26 PM : [ 14 D5 B4 1] Removing all links Sun 08/07/2011 05:45:26 PM : [14 D5 B4 1 ] Querying engine version Sun 08/07/2011 05:45:26 PM : [iNST-ACK ] 02 62 14.D5.B4 0F 0D 00 06 (00) Sun 08/07/2011 05:45:35 PM : [iNST-ACK ] 02 62 14.D5.B4 0F 0D 00 06 (00) Sun 08/07/2011 05:45:44 PM : [iNST-ACK ] 02 62 14.D5.B4 0F 0D 00 06 (00) Sun 08/07/2011 05:45:48 PM : [14 D5 B4 1 ] Failed getting engine version. Reverting to i1. Sun 08/07/2011 05:45:48 PM : [14 D5 B4 1 ] Using engine version i2 Sun 08/07/2011 05:45:48 PM : [iNST-ACK ] 02 62 14.D5.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 08/07/2011 05:45:57 PM : [iNST-ACK ] 02 62 14.D5.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 08/07/2011 05:46:05 PM : [iNST-ACK ] 02 62 14.D5.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 08/07/2011 05:46:09 PM : [ 14 D5 B4 1] ** Not added ** Remove Device Links failed Sun 08/07/2011 05:46:09 PM : ---- All Remaining Device Added ---- Sun 08/07/2011 05:46:10 PM : [All ] Writing 0 bytes to devices Link to comment Share on other sites More sharing options...
LeeG Posted August 8, 2011 Share Posted August 8, 2011 The new trace shows NO communication with the motion sensor. Note the 9 seconds between command attempts. The ISY is now not receiving any response, as if the motion sensor is not in linking mode. I have seen it take several minutes for a motion sensor to be able to communicate after a battery change. Sun 08/07/2011 05:45:48 PM : [iNST-ACK ] 02 62 14.D5.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 08/07/2011 05:45:57 PM : [iNST-ACK ] 02 62 14.D5.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Sun 08/07/2011 05:46:05 PM : [iNST-ACK ] 02 62 14.D5.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Link to comment Share on other sites More sharing options...
LeeG Posted August 8, 2011 Share Posted August 8, 2011 The motion sensor address has been flipped. It was 14.5D.B4 in the first trace. The second trace shows 14.D5.B4. 5D versus D5. Link to comment Share on other sites More sharing options...
jackal Posted August 8, 2011 Share Posted August 8, 2011 The motion sensor address has been flipped. It was 14.5D.B4 in the first trace. The second trace shows 14.D5.B4. 5D versus D5. My bad. Keyed in so many times that I made a typo in the last log. But no luck. Still couldn't connect. I have tried the following: - reset the motion detector - change the battery (to new energizer) - reset ISY - let it rest overnight - change computer (in case its the java) What else can I do? Thanks for any suggestions. Link to comment Share on other sites More sharing options...
LeeG Posted August 8, 2011 Share Posted August 8, 2011 Post the Event Log so we can see what is happening now with a good address. Best to have multiple traces showing the same thing before deciding what to do next. If the motion sensor continues to take 4 seconds to generate a response and eventually stops responding altogether (as the first trace showed) my next suggestion would be a factory reset. Watch the motion sensor LED and see if it stops blinking before the device add completes. Link to comment Share on other sites More sharing options...
LeeG Posted August 8, 2011 Share Posted August 8, 2011 jackal I deleted a motion sensor and added it back to see if I missed something in that initial trace. First it took less than 30 seconds for the entire device add processing to complete on my system. From memory (cannot access forum) the initial trace covered more than 5 minutes. Mon 08/08/2011 03:42:28 PM : ---- Initializing the linked devices ---- Mon 08/08/2011 03:42:51 PM : [PLM ] Group 3 : Writing Responder Link matching [13 F2 57 1 ] Link 2 : 0FE8 [E203129FE4FF1F03] The next thing I noticed is that your trace is missing the Standard message response (02 50) from the motion sensor. It is the message in blue. There may be a communication problem between the motion sensor and the ISY PLM. If the Standard message was being retried by the motion sensor it could explain why it took so long for the Extended message (02 51) to be received. Mon 08/08/2011 03:42:29 PM : [13 F2 57 1 ] Using engine version i2 Mon 08/08/2011 03:42:29 PM : [iNST-ACK ] 02 62 13.F2.57 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Mon 08/08/2011 03:42:30 PM : [iNST-SRX ] 02 50 13.F2.57 12.9F.E4 27 2F 00 (00) Mon 08/08/2011 03:42:30 PM : [standard-Direct Ack][13.F2.57-->ISY/PLM Group=0] Max Hops=3, Hops Left=1 Mon 08/08/2011 03:42:30 PM : [iNST-ERX ] 02 51 13 F2 57 12 9F E4 11 2F 00 00 01 0F FF 01 62 00 00 00 00 00 00 00 00 Mon 08/08/2011 03:42:30 PM : [Extended-Direct][13.F2.57-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Try moving the motion sensor closer to a Dual Band device. A new trace will confirm but the message in the first trace that failed to get any response may well have been the motion sensor timing out of linking mode. Lee Link to comment Share on other sites More sharing options...
jackal Posted August 9, 2011 Share Posted August 9, 2011 Sorry for the delay as I was at work. Just got home. I moved the motion sensor to 1 feet away from ISY and no luck still. Here's my new trace: ======================================= Mon 08/08/2011 07:03:25 PM : ---- Initializing the linked devices ---- Mon 08/08/2011 07:03:25 PM : ---- All Linked Devices are now initialized ---- Mon 08/08/2011 07:03:25 PM : ---- Add remaining devices ---- Mon 08/08/2011 07:03:25 PM : [ 14 5D B4 1] Removing all links Mon 08/08/2011 07:03:25 PM : [14 5D B4 1 ] Querying engine version Mon 08/08/2011 07:03:25 PM : [iNST-ACK ] 02 62 14.5D.B4 0F 0D 00 06 (00) Mon 08/08/2011 07:03:34 PM : [iNST-ACK ] 02 62 14.5D.B4 0F 0D 00 06 (00) Mon 08/08/2011 07:03:43 PM : [iNST-ACK ] 02 62 14.5D.B4 0F 0D 00 06 (00) Mon 08/08/2011 07:03:47 PM : [14 5D B4 1 ] Failed getting engine version. Reverting to i1. Mon 08/08/2011 07:03:47 PM : [14 5D B4 1 ] Using engine version i2 Mon 08/08/2011 07:03:47 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Mon 08/08/2011 07:03:50 PM : [iNST-ERX ] 02 51 14 5D B4 19 6F 06 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 00 Mon 08/08/2011 07:03:50 PM : [Extended-Direct][14.5D.B4-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Mon 08/08/2011 07:03:50 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Mon 08/08/2011 07:03:54 PM : [iNST-ERX ] 02 51 14 5D B4 19 6F 06 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 00 Mon 08/08/2011 07:03:54 PM : [Extended-Direct][14.5D.B4-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Mon 08/08/2011 07:03:54 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 02 0F FF 08 00 00 00 00 00 00 00 00 00 06 (00) Mon 08/08/2011 07:04:03 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 02 0F FF 08 00 00 00 00 00 00 00 00 00 06 (00) Mon 08/08/2011 07:04:12 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 02 0F FF 08 00 00 00 00 00 00 00 00 00 06 (00) Mon 08/08/2011 07:04:16 PM : [ 14 5D B4 1] ** Not added ** Remove Device Links failed Mon 08/08/2011 07:04:16 PM : ---- All Remaining Device Added --- Mon 08/08/2011 07:04:16 PM : [All ] Writing 0 bytes to devices Link to comment Share on other sites More sharing options...
LeeG Posted August 9, 2011 Share Posted August 9, 2011 jackal I assume the ISY is using a Dual Band PLM. The Standard messages are still missing and the write of the End Of List link record did not get a response from the motion sensor. Only thing I can suggest is to factory reset the motion sensor. Lee Link to comment Share on other sites More sharing options...
jackal Posted August 9, 2011 Share Posted August 9, 2011 jackal I assume the ISY is using a Dual Band PLM. The Standard messages are still missing and the write of the End Of List link record did not get a response from the motion sensor. Only thing I can suggest is to factory reset the motion sensor. Lee Yes, it is. Just bought it. Actually, I already did a factory reset. Should I return the motion sensor? Link to comment Share on other sites More sharing options...
LeeG Posted August 9, 2011 Share Posted August 9, 2011 jackal Just to be sure there is no PLM question, all the other Insteon devices are working as expected. The Admin Console is showing device status changes as button/paddle is pressed. These events are conveyed by Standard messages so if status changes Standard messages are being handled by the PLM. I have no other suggestions regarding the motion sensor. It is not responding as my motion sensors respond. Enough other folks are using motion sensors that all points to that motion sensor. Lee Link to comment Share on other sites More sharing options...
jackal Posted August 9, 2011 Share Posted August 9, 2011 uh oh. The "My Lighting" controller shows all my devices as "off" even though some lights are definitely on. Is that correct? How do I get the diagnostics to make sure that the PLM is ok? Link to comment Share on other sites More sharing options...
LeeG Posted August 9, 2011 Share Posted August 9, 2011 jackal Was a Restore modem (PLM) function executed when the new Dual Band PLM was installed? If not that would explain the lack of status changes being received by the ISY. Perhaps some background, this was a functioning system with the ISY seeing device status changes before the new PLM was Installed. To see what the device is sending to the ISY when a button/paddle is pressed run Tools | Diagnostics | Event Viewer with Device communications events selected (important step). Press a button/paddle and see if events are being received/traced. Lee Link to comment Share on other sites More sharing options...
jackal Posted August 9, 2011 Share Posted August 9, 2011 Just some background. My system is powered by SmartLinc controller before I install the ISY 2 weekends ago. I didn't perform any Restore modem function and I don't remember the ISY ever displaying status changes. So I have to do a "Restore modem" is that it? Do I have to plug out the Smartlinc controller before doing the restore modem? And I just want to say thank you for helping me walk every step so far. I really appreciate and can't thank enough. Link to comment Share on other sites More sharing options...
LeeG Posted August 9, 2011 Share Posted August 9, 2011 Do not do a Restore Modem (PLM). The necessary link records will be established as the Insteon devices are added to the ISY. I misunderstood the comment about being a new PLM. I assumed it had replaced an existing PLM on the ISY. If status changes are not being displayed there could be a powerline communication issue where the ISY PLM is plugged. Be sure it is not plugged into a surge/noise suppression power strip. If near a UPS that is not on a FilterLinc try plugging the PLM into an extension cord and plug the extension cord as far away from the UPS as possible. What type of devices are being used to couple the 2 120V legs and do they indicate being on opposite 120V legs? How many devices are now defined to the ISY and what types? EDIT: note that devices turned On by the SmartLinc will not register in the ISY. Only devices that have been defined to the ISY and have their button/paddle pressed will show status changes in the ISY. Link to comment Share on other sites More sharing options...
jackal Posted August 9, 2011 Share Posted August 9, 2011 The forum seems to be up and down. I will try to get the log as soon as I get back home. I don't have a UPS. The devices defined are several light switches and 1 keypadlinc. Link to comment Share on other sites More sharing options...
LeeG Posted August 10, 2011 Share Posted August 10, 2011 A simple test of the ISY PLM would be to turn On/Off some of the devices using the Admin Console. Standard messages are expected in response to these commands so the ISY should indicate some comm error if the devices do not respond with (or the PLM does not accept) the Standard messages. Yes, the forum is having some problems. The number of logins is being restricted to try and control the issues so it will be unavailable at times. Link to comment Share on other sites More sharing options...
jackal Posted August 10, 2011 Share Posted August 10, 2011 ok, this is the log I get trying to turn on from the admin console. I've moved my PLM into a new wall plug location. ============================== Tue 08/09/2011 07:54:57 PM : [iNST-ACK ] 02 62 14.79.AD 0F 11 FF 06 LTONRR (FF) Tue 08/09/2011 07:54:57 PM : [iNST-SRX ] 02 50 14.79.AD 19.6F.06 2B 11 FF LTONRR (FF) Tue 08/09/2011 07:54:57 PM : [standard-Direct Ack][14.79.AD-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Tue 08/09/2011 07:54:57 PM : [ 14 79 AD 1] ST 255 =============================== Link to comment Share on other sites More sharing options...
jackal Posted August 10, 2011 Share Posted August 10, 2011 This is my new log for the motion sensor after I moved the PLM location. Still no luck. ============================= Tue 08/09/2011 08:04:32 PM : ---- Initializing the linked devices ---- Tue 08/09/2011 08:04:32 PM : ---- All Linked Devices are now initialized ---- Tue 08/09/2011 08:04:32 PM : ---- Add remaining devices ---- Tue 08/09/2011 08:04:32 PM : [ 14 5D B4 1] Removing all links Tue 08/09/2011 08:04:32 PM : [14 5D B4 1 ] Querying engine version Tue 08/09/2011 08:04:32 PM : [iNST-ACK ] 02 62 14.5D.B4 0F 0D 00 06 (00) Tue 08/09/2011 08:04:40 PM : [iNST-ACK ] 02 62 14.5D.B4 0F 0D 00 06 (00) Tue 08/09/2011 08:04:49 PM : [iNST-ACK ] 02 62 14.5D.B4 0F 0D 00 06 (00) Tue 08/09/2011 08:04:53 PM : [14 5D B4 1 ] Failed getting engine version. Reverting to i1. Tue 08/09/2011 08:04:53 PM : [14 5D B4 1 ] Using engine version i2 Tue 08/09/2011 08:04:53 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Tue 08/09/2011 08:04:57 PM : [iNST-ERX ] 02 51 14 5D B4 19 6F 06 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 00 Tue 08/09/2011 08:04:57 PM : [Extended-Direct][14.5D.B4-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Tue 08/09/2011 08:04:57 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 00 0F FF 01 00 00 00 00 00 00 00 00 00 06 (00) Tue 08/09/2011 08:05:01 PM : [iNST-ERX ] 02 51 14 5D B4 19 6F 06 11 2F 00 00 01 0F FF 01 00 00 00 00 00 00 00 00 00 Tue 08/09/2011 08:05:01 PM : [Extended-Direct][14.5D.B4-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Tue 08/09/2011 08:05:01 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 02 0F FF 08 00 00 00 00 00 00 00 00 00 06 (00) Tue 08/09/2011 08:05:10 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 02 0F FF 08 00 00 00 00 00 00 00 00 00 06 (00) Tue 08/09/2011 08:05:19 PM : [iNST-ACK ] 02 62 14.5D.B4 1F 2F 00 00 02 0F FF 08 00 00 00 00 00 00 00 00 00 06 (00) Tue 08/09/2011 08:05:23 PM : [ 14 5D B4 1] ** Not added ** Remove Device Links failed Tue 08/09/2011 08:05:23 PM : ---- All Remaining Device Added ---- Tue 08/09/2011 08:05:23 PM : [All ] Writing 0 bytes to devices Link to comment Share on other sites More sharing options...
LeeG Posted August 10, 2011 Share Posted August 10, 2011 All points to a motion sensor problem. The last log is the same as the others. There is no Standard response messages being received. The command to write the link record to clear the link database is acknowledged with a Standard message only. The lack of any response is correctly considered a failure so the device add is terminated. The shorter log of the device On to 14.79.AD looks correct which I think rules out a PLM issue. I know of nothing else to try. Time for a new motion sensor. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.