Author |
|
nerdboytodd Newbie
Joined: January 19 2011 Location: United States
Online Status: Offline Posts: 11
|
Posted: July 14 2012 at 18:35 | IP Logged
|
|
|
I've got my PH2 installation running for a couple of years now. About 50+ Insteon devices and all working well. I just purchased a couple of new 2466D ToggleLinc Dimmer modules to add on some additional controlled lights. However, when I go to link those two new modules (both running v5.9) PH2 is unable to program them. I keep getting a NAK in the Insteon Raw Log. Is this something new due to the folks at SmartHome upgrading the code. This is the first time I've seen that version of code on modules I've ordered. Any help would be appreciated.
Nerdboy Todd
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: July 15 2012 at 04:47 | IP Logged
|
|
|
This would be the first Dimmer reported to have I2CS firmware but that is what it sounds like. Up to now the majority of I2CS devices have been Relay based. If you can post the Insteon Raw Log section that has the ToggleLinc communication I can verify for sure.
I2CS devices require special linking procedures along with a Checksum calculation that PH2 does not yet support. If it is I2CS firmware, linking can only be done with the Set button for now.
__________________ Lee G
|
Back to Top |
|
|
nerdboytodd Newbie
Joined: January 19 2011 Location: United States
Online Status: Offline Posts: 11
|
Posted: July 15 2012 at 22:43 | IP Logged
|
|
|
Take a look at the screen shot I got (see URL below). I couldn't get all the data due to the window not being wide enough. If you need more data from the raw log let me know how best to capture it.
Thanks for your help with this. I would never have gone Insteon if not for PowerHome. Insteon and my Elk M1 Gold do so much more with PH2.
http://public.accessprotocol.com/PH2ScreenShot.png
NerdboyTodd
Edited by nerdboytodd - July 15 2012 at 22:48
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: July 15 2012 at 23:40 | IP Logged
|
|
|
Under Powerhome Explorer, Setup, Controllers, Settings, the Echo Log File field contains the fully qualified file name for the Insteon Raw Log file. You can use anything you want here, I use
c:\temp\phlog.txt
After defining the path it is necessary to reinit PH2 for the definition to take effect. Under Insteon Explorer when you want to get a trace file check the “Echo Raw Log to File” check box. From then on what is displayed is also written to the file until the checkbox is unchecked.
The NAK is the lack of a valid link record between the ToggleLinc and the Powerhome PLM. Even if the Set button is used to create that link the ALDB command will not work because there is no Checksum in the Extended command. Cannot go back to using the old I1 Peek/Poke method because those commands have been removed from I2CS devices.
If you create the Set button link between the ToggleLinc and the PH2 PLM it should be possible to turn the ToggleLinc On and Off with PH2 but link records cannot be created with PH2 until Dave releases the next update with I2CS support. Dave is working on this but no target date has been published.
__________________ Lee G
|
Back to Top |
|
|
nerdboytodd Newbie
Joined: January 19 2011 Location: United States
Online Status: Offline Posts: 11
|
Posted: July 16 2012 at 15:26 | IP Logged
|
|
|
Thanks for the directions and the background on this. Glad to hear I'm not going crazy. Here's the rawlog.txt file I was able to create. I'll try manual linking to get me working for now. Look forward to finding out when the new version which incorporates the I2CS fix will be out. Hopefully Dave's going full steam on it.
http://public.accessprotocol.com/rawlog.txt
NerdboyTodd
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: July 16 2012 at 15:44 | IP Logged
|
|
|
The FF in the NAK response has been the indicator of the missing link record on other I2CS devices. If you do a Set button link and try linking again I would expect the FF to become a FD which indicates the Checksum value is invalid.
2012-07-16 13:18:10.063 TX &nbs p; 02 62 1D 03 7E 1F 2F 00 00 02 0F FF 08 A2 07 1D 99 37 FF 1F 00
2012-07-16 13:18:10.797 RX &nbs p; SENTINSTEONEXT=18 CF 23 1D 03 7E 1F 2F 00 00 02 0F FF 08 A2 07 1D 99 37 FF 1F 00 00 06
2012-07-16 13:18:10.813 RX &nbs p; RECEIVEINSTEONRAW=1D 03 7E 18 CF 23 A7 2F FF
2012-07-16 13:18:10.844 RX &nbs p; INSTEON NAK=1D 03 7E
Lots are looking forward to the next PH2 upgrade.
Edited by grif091 - July 16 2012 at 15:46
__________________ Lee G
|
Back to Top |
|
|
Ken524 Newbie
Joined: February 23 2007 Location: United States
Online Status: Offline Posts: 14
|
Posted: August 16 2012 at 08:02 | IP Logged
|
|
|
I'm glad I found this thread.
I recently purchased a replacement 2466 relay and two
2466 dimmers and nearly convinced myself that all three
were defective. They are all v5.9.
For several years I used a 2414U PLC timer/controller
until I read last week on SmartHome that it no longer
worked with the new firmware.
I just received my new 2413U PLM and was surprised when
the new switches still refused to be programmed using
PH2.1b.
I can manually program the switches with the old "running
around the house" method, but what fun is that?
Edited by Ken524 - August 16 2012 at 08:04
|
Back to Top |
|
|
grif091 Super User
Joined: March 26 2008 Location: United States
Online Status: Offline Posts: 1357
|
Posted: August 21 2012 at 11:28 | IP Logged
|
|
|
See link for I2CS support
I2CS support for 2.1.4
__________________ Lee G
|
Back to Top |
|
|