craigf Posted March 8, 2012 Share Posted March 8, 2012 I just purchased a new 2420M motion sensor. It is Rev 2.1. I also updated the ISY to version 3.1.17 before adding the MS. I have put on jumper 5 but I am unable to change the settings from the ISY. I am putting the MS in linking mode and I am not getting any errors but when I change the time or try and change to send on signals only, it writes to the device but the changes don't stick. After it writes the changes, I push the set button, the led double flashes repeatedly. If I push the set button again it goes back to normal mode. The problem is that the settings didn't change. If I put it back in link mode and choose "Set Options", the settings are back to the original settings. Any ideas why they are not sticking? Thanks, Craig Link to comment
LeeG Posted March 8, 2012 Share Posted March 8, 2012 Run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Put the MS into linking mode and click Set Options. Change the timeout value and click Ok. Click Set Options again. Post the event file and the new timeout value. Link to comment
craigf Posted March 9, 2012 Author Share Posted March 9, 2012 Lee, Here is the Log info: Thu 03/08/2012 06:20:26 PM : [14 98 59 2 ] Using engine version i2 for 'Garage Motion Sensor-Dusk/Daw' Thu 03/08/2012 06:20:26 PM : [iNST-ACK ] 02 62 14.98.59 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06 (00) Thu 03/08/2012 06:20:27 PM : [iNST-SRX ] 02 50 14.98.59 14.83.54 2B 2F 00 (00) Thu 03/08/2012 06:20:27 PM : [standard-Direct Ack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:27 PM : [iNST-ERX ] 02 51 14 98 59 14 83 54 11 2F 00 00 01 00 07 01 50 10 01 41 0E 64 01 80 33 Thu 03/08/2012 06:20:27 PM : [Extended-Direct][14.98.59-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 03/08/2012 06:20:27 PM : [All ] Writing 0 bytes to devices Thu 03/08/2012 06:20:33 PM : [14 98 59 2 ] Using engine version i2 for 'Garage Motion Sensor-Dusk/Daw' Thu 03/08/2012 06:20:33 PM : [iNST-ACK ] 02 62 14.98.59 1F 2F 00 00 02 00 07 08 50 10 01 41 0E 64 03 80 00 06 (00) Thu 03/08/2012 06:20:33 PM : [iNST-SRX ] 02 50 14.98.59 14.83.54 AB 2F FD (FD) Thu 03/08/2012 06:20:33 PM : [standard-Direct Nack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:34 PM : [All ] Writing 0 bytes to devices Thu 03/08/2012 06:20:42 PM : [14 98 59 2 ] Using engine version i2 for 'Garage Motion Sensor-Dusk/Daw' Thu 03/08/2012 06:20:42 PM : [iNST-ACK ] 02 62 14.98.59 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06 (00) Thu 03/08/2012 06:20:42 PM : [iNST-SRX ] 02 50 14.98.59 14.83.54 2B 2F 00 (00) Thu 03/08/2012 06:20:42 PM : [standard-Direct Ack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:42 PM : [iNST-ERX ] 02 51 14 98 59 14 83 54 11 2F 00 00 01 00 07 01 50 10 01 41 0E 64 01 80 33 Thu 03/08/2012 06:20:42 PM : [Extended-Direct][14.98.59-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Thu 03/08/2012 06:20:42 PM : [All ] Writing 0 bytes to devices Thu 03/08/2012 06:20:47 PM : [14 98 59 2 ] Using engine version i2 for 'Garage Motion Sensor-Dusk/Daw' Thu 03/08/2012 06:20:47 PM : [iNST-ACK ] 02 62 14.98.59 1F 2F 00 00 02 00 07 08 50 10 01 41 0E 64 01 80 00 06 (00) Thu 03/08/2012 06:20:47 PM : [iNST-SRX ] 02 50 14.98.59 14.83.54 AB 2F FD (FD) Thu 03/08/2012 06:20:47 PM : [standard-Direct Nack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:47 PM : [All ] Writing 0 bytes to devices The timeout was originally set to 1 s. I changed it to 3 s. When I went back in the second time, it was still set to 1s. The only jumper installed is jumper 5. Also, it might be noteworthy that the Sensor status is ON, the Bat Low is OFF, and the Dusk/Dawn status is blank. Thanks, Craig Link to comment
LeeG Posted March 9, 2012 Share Posted March 9, 2012 The Motion Sensor is rejecting the updates to the configuration data. Note the Nack being received each time the configuration is updated. Double check Jumper 5. Thu 03/08/2012 06:20:33 PM : [standard-Direct Nack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Thu 03/08/2012 06:20:47 PM : [standard-Direct Nack][14.98.59-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Link to comment
craigf Posted March 10, 2012 Author Share Posted March 10, 2012 Lee, I double checked the jumper. I returned the MS and got a new one and I am having the same identical behavior. Craig Link to comment
LeeG Posted March 10, 2012 Share Posted March 10, 2012 craigf There are a couple of possibilities. The v2.1 Motion Sensors may require a different method for updating the configuration data or they may be an I2CS device which UDI is currently adding support for. I ordered a new Motion Sensor so I can test the various possibilities. Michel Any thoughts about the new v2.1 hardware Motion Sensors? Link to comment
craigf Posted March 10, 2012 Author Share Posted March 10, 2012 I rolled back the firmware to 2.8.16 and tried the same thing with the same results so it does not appear to be a firmware issue. I also tried both of the configuration's for 2420M and 2420M-SP. I'm not sure what the difference is, but both behaved that same. Thanks for looking into this. Craig Link to comment
Brian H Posted March 10, 2012 Share Posted March 10, 2012 The developers Group was told. Before I2CS was in shipping products. An announcement would be made. That said. A NAK of FD looks like a I2CS reply. Link to comment
LeeG Posted March 10, 2012 Share Posted March 10, 2012 Brian Thanks for that information. There is a post under one of the FanLinc topics that one of the latest FanLincs is displaying FF FF --- FF FF for the current link record in the FanLinc. This is classic response from the MorningLinc if PLM access authorization is lost. I suspect the latest FanLinc is also an I2CS. Have ordered another FanLinc (my two FanLincs are older) to confirm as well as another Motion Sensor to confirm the cause of the Nack. Link to comment
Michel Kohanim Posted March 11, 2012 Share Posted March 11, 2012 Hi LeeG, I think you are right: the new MS is probably an I2CS device (we are working on it right now). I was told that there would be an announcement but I guess not. With kind regards, Michel Link to comment
Brian H Posted March 11, 2012 Share Posted March 11, 2012 I also was under the impression there was going to be an announcement. Here is what my Beta I2CS 2420M gives when I click on Options. FD NAK is the big clue. At least I could add it to My Lighting as you know other models you can't even add. PLM:19.70.1A Motion Sensor: 14.96.56 I2CS Firmware Clicking Set Options Tab in Administration Console. Event Viewer #3 Communications Events. Sat 03/10/2012 06:53:15 AM : [14 96 56 1 ] Using engine version i2 for 'MS1-Sensor' Sat 03/10/2012 06:53:15 AM : [iNST-ACK ] 02 62 14.96.56 1F 2F 00 00 00 00 07 01 00 00 00 00 00 00 00 00 00 06 (00) Sat 03/10/2012 06:53:15 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A 2B 2F 00 (00) Sat 03/10/2012 06:53:15 AM : [standard-Direct Ack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:15 AM : [iNST-ERX ] 02 51 14 96 56 19 70 1A 11 2F 00 00 01 00 07 01 50 10 01 8F 0E 64 01 80 E5 Sat 03/10/2012 06:53:15 AM : [Extended-Direct][14.96.56-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 Sat 03/10/2012 06:53:15 AM : [All ] Writing 0 bytes to devices Sat 03/10/2012 06:53:32 AM : [14 96 56 1 ] Using engine version i2 for 'MS1-Sensor' Sat 03/10/2012 06:53:32 AM : [iNST-ACK ] 02 62 14.96.56 1F 2F 00 00 02 00 07 08 50 10 01 8F 0E 64 03 80 00 06 (00) Sat 03/10/2012 06:53:33 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:33 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:33 AM : [All ] Writing 0 bytes to devices Sat 03/10/2012 06:53:34 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:34 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:34 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:34 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:34 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD): Process Message: Ignored Sat 03/10/2012 06:53:34 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:35 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:35 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:36 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD) Sat 03/10/2012 06:53:36 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sat 03/10/2012 06:53:36 AM : [iNST-SRX ] 02 50 14.96.56 19.70.1A AB 2F FD (FD): Process Message: Ignored Sat 03/10/2012 06:53:36 AM : [standard-Direct Nack][14.96.56-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Link to comment
LeeG Posted March 11, 2012 Share Posted March 11, 2012 Brian Thanks for that trace. It confirms what the OP is seeing. The fact that the motion sensor accepted link records in the conventional manor suggests another possibility. The MS options are being set using a 2F ALDB command to alter memory where the options are stored. That is outside the bounds of the link database and could be rejected for being out of range by this new MS. Are the link records actually functional? That is, does the MS Sensor node reflect motion On/Off messages? I’m wondering if they were rejected with a Nack making them not functional. Link to comment
LeeG Posted March 12, 2012 Share Posted March 12, 2012 I can confirm I2CS devices are in the retail stream. The Motion Sensor that arrived today along with not being able to Set Options, all the commands to write link records were rejected with Nacks. Even though New INSTEON Device added the Motion Sensor it is not functional without link records. Link to comment
Michel Kohanim Posted March 13, 2012 Share Posted March 13, 2012 Hi LeeG, Thanks so very much. We are very close in finishing up support for i2cs devices. With kind regards, Michel Link to comment
Brian H Posted March 13, 2012 Share Posted March 13, 2012 Thanks LeeG for the findings. Like when I2 was released and implemented all or part of the protocol. Not all I2CS features are in all model I2CS devices. A different model may not even add to My Lighting. Link to comment
LeeG Posted March 13, 2012 Share Posted March 13, 2012 Brian Would expect that will be true. I have a new FanLinc that also arrived yesterday I expect to be I2CS but have not had a chance to test it yet. Some differences could be whether extended ALDB is used as must be used with the Motion Sensor or Peek/Poke as I think will be used with the FanLinc. Link to comment
Michel Kohanim Posted March 14, 2012 Share Posted March 14, 2012 Hi LeeG, I can confirm that FanLinc is I2CS. We should have a build very soon. With kind regards, Michel Link to comment
SetMonkey13 Posted March 16, 2012 Share Posted March 16, 2012 I just got a 2420M too. Does this mean I can't program with it until the update? Link to comment
LeeG Posted March 16, 2012 Share Posted March 16, 2012 Yes. The 3.2.0 beta has a tentative availability of 3/16/2012. Once the Beta is installed the Motion Senosr must be Deleted and added back to the ISY under the Beta. Link to comment
craigf Posted March 21, 2012 Author Share Posted March 21, 2012 Thanks for the update everyone. The new firmware works great, no problems and everything seems to be working! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.