Trouble linking fanlinc

[Tunaman]

I just got a new fanlinc, and can't get it to link. When I enter its address and tell the isy to autodiscover, it searches for a very long time, then starts to discover the topology.

 

I'm running 3.2.6

 

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

[LeeG]

Which option is in effect, erase existing links or keep existing links?

 

Check Help | About to be sure both Firmware and UI lines indicate 3.2.6.

[Tunaman]

Erase existing. Both ui and server are 3.2.6

 

Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

[LeeG]

Run Tools | Diagnostics | Event Viewer with Level 3 selected. Run New INSTEON Device with Auto Discover and post the event trace.

[Tunaman]

Level 3 log is attached. It will stay in this state forever (or at least overnight). It will occasionally add another entry like the last one.

 

I seem to recall seeing somewhere on this forum that earlier versions of the fanlinc caused some problems for the isy. This is rev 1.05

 

Sat 05/26/2012 11:40:12 AM : ---- Initializing the linked devices ----

Sat 05/26/2012 11:40:12 AM : ---- All Linked Devices are now initialized ----

Sat 05/26/2012 11:40:12 AM : ---- Add remaining devices ----

Sat 05/26/2012 11:40:12 AM : [iNST-TX-I1  ] 02 62 14 9F 79 0F 0D 00

Sat 05/26/2012 11:40:12 AM : [iNST-ACK    ] 02 62 14.9F.79 0F 0D 00 06                 (00)

Sat 05/26/2012 11:40:12 AM : [iNST-SRX    ] 02 50 14.9F.79 19.72.42 AB 0D FF           (FF)

Sat 05/26/2012 11:40:12 AM : [standard-Direct Nack][14.9F.79-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 05/26/2012 11:40:12 AM : [iNST-TX-I2CS] 02 62 14 9F 79 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Sat 05/26/2012 11:40:13 AM : [iNST-ACK    ] 02 62 14.9F.79 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Sat 05/26/2012 11:40:13 AM : [iNST-SRX    ] 02 50 14.9F.79 19.72.42 2B 09 01    LNK-ON (01)

Sat 05/26/2012 11:40:13 AM : [standard-Direct Ack][14.9F.79-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 05/26/2012 11:40:14 AM : [LNK-BGN     ] 02 64 01 00 06 

Sat 05/26/2012 11:42:04 AM : [ELK 0   1  0]  (56/140/0)

[LeeG]

Try a factory reset of the FanLinc. It failed to send the expected response to the begin linking command. Note the 02 53 inbound message from my I2CS FanLinc add did not come back in your trace.

 

Fri 03/16/2012 06:55:48 PM : [iNST-TX-I2CS] 02 62 14 9E F5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

 

Fri 03/16/2012 06:55:49 PM : [iNST-ACK ] 02 62 14.9E.F5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

 

Fri 03/16/2012 06:55:49 PM : [iNST-SRX ] 02 50 14.9E.F5 19.70.06 2B 09 01 LNK-ON (01)

 

Fri 03/16/2012 06:55:49 PM : [standard-Direct Ack][14.9E.F5-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Fri 03/16/2012 06:55:49 PM : [LNK-BGN ] 02 64 01 00 06

 

Fri 03/16/2012 06:55:50 PM : [LNK-STAT ] 02 53 M(01) gid=00 14.9E.F5 012E 41

 

Also, what type of PLM is being used with the ISY and what PLM firmware?

[Tunaman]

The PLM is a 2413S, V1.5. The Diagnostics shows v98

 

I've done the factory reset

 

 

Other than the timestamps, the trace looks identical

 

Sat 05/26/2012 12:48:05 PM : ---- Initializing the linked devices ----

Sat 05/26/2012 12:48:05 PM : ---- All Linked Devices are now initialized ----

Sat 05/26/2012 12:48:05 PM : ---- Add remaining devices ----

Sat 05/26/2012 12:48:05 PM : [iNST-TX-I1  ] 02 62 14 9F 79 0F 0D 00

Sat 05/26/2012 12:48:05 PM : [iNST-ACK    ] 02 62 14.9F.79 0F 0D 00 06                 (00)

Sat 05/26/2012 12:48:06 PM : [iNST-SRX    ] 02 50 14.9F.79 19.72.42 AB 0D FF           (FF)

Sat 05/26/2012 12:48:06 PM : [standard-Direct Nack][14.9F.79-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 05/26/2012 12:48:06 PM : [iNST-TX-I2CS] 02 62 14 9F 79 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6

Sat 05/26/2012 12:48:06 PM : [iNST-ACK    ] 02 62 14.9F.79 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)

Sat 05/26/2012 12:48:07 PM : [iNST-SRX    ] 02 50 14.9F.79 19.72.42 2B 09 01    LNK-ON (01)

Sat 05/26/2012 12:48:07 PM : [standard-Direct Ack][14.9F.79-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sat 05/26/2012 12:48:07 PM : [LNK-BGN     ] 02 64 01 00 06 

Sat 05/26/2012 12:51:26 PM : [ELK 0   0  2]  (113/136/0)

Sat 05/26/2012 12:52:13 PM : [ELK 0   1  0]  (56/143/0)

[LeeG]

There were some issues with the v.98 level but nothing related to I2CS that I remember. The v.99 PLM I am running with came out before the influx of I2CS devices. I have done a Set button link between a v.92 PLM and an I2CS FanLinc with no problem. The I2CS devices have not been out long enough to develop a comprehensive symptom/cause list.

 

Some things to consider trying ....

 

Power cycle the PLM

Move the FanLinc to an appliance cord and plug it into the same circuit as the PLM

Reset the PLM and restore with Restore Modem (PLM)

 

Except that the message exchange between the PLM and the FanLinc did not produce the expected 02 53 response I see no difference between the trace on my system and the posted trace. I Deleted the FanLinc and added it back under 3.2.6 after a FanLinc Factory reset. My trace is identical except I get the expected 02 53 response and the FanLinc adds successfully.

[Tunaman]

I followed all of your suggestions -- same results.

 

I'm afraid it might be RMA time.

 

Thanks for your help -- comparing traces was extremely helpful!

[LeeG]

One more thing to try before the RMA. Use Link Management | Start Linking which will put the PLM into linking mode (PLM LED blinking), then press the Set button on the FanLinc Light for 3-5 seconds. If that does not work and the RMA replacement does the same thing consider moving to a later PLM.

 

Whatever does resolve this please post back the solution so others can benefit. Thanks

[Tunaman]

Well, this is interesting.

 

I did the Link Management, then Start, and same results.

 

I was about to give up, but then I decided to see what would happen if I put a load on the light side, and that seems to have done the trick!

 

Now for the real test -- put it in the ceiling and see what happens.

[LeeG]

That is a good result if not a strange way to achieve it. All my linking tests have been done without anything connected to the Light or Motor wires.

 

Were either LED on the FanLinc Green during the linking? I do all my linking with both LEDs Red.

[Tunaman]

the motor was red, the light was green, with the load on the light.

 

In previous attempts, I'm sure I had both in the red.

 

It's in the fan now, responding to all commands from the admin console.

Hopefully I'll be able to add it to scenes without an issue.

 

Hopefully, one more trip up the ladder to put the covers on

[steelman58]

tunaman,

 

Are you using a KeypadLinc to control the 120VAC to FanLinc/Fan?

 

Before being put on the right track by LeeG in a previous post, I had tried to setup my FanLinc / KeypadLinc with KPL red "load" wire as the line wire going to the FanLinc. As it turns out the KPL red "load" wire is to be terminated in the J-box and the black wire from the KPL is connected to the line (120VAC) wire at the FanLinc. Because of the way I was wireing the KPL, when the load button was "Off", no current was going to the FanLinc and therefore it was not recognized during the ISY linking process. Once I changed the wiring, I was able to correctly link with the ISY.

[Tunaman]

I am using the KPL, but the load from the KPL is capped.

 

The fanlinc is wired so that it is always hot.

 

It is a little troubling that havin a load on the light side of the fanlinc was necessary to get it to link -- I've never had to do that for any other insteon devices.

 

But, it seems to be working now, but I haven't programmed anything yet, that will be the real test.

 

Time to have an adult beverage by the pool.