Jump to content


Photo

Cannot determine Insteon Engine - 2474DWH


  • Please log in to reply
10 replies to this topic

#1 Bill Morrow

Bill Morrow

    Member

  • Members
  • PipPip
  • 16 posts

Posted 26 January 2013 - 04:33 PM

I installed 3 2-Wire SwitchLinc dimmers today, but one of them is giving me 'Cannot determine Insteon Engine'. This switch is within 10' of a WAP. Manual switch operation is OK.

Any ideas?

#2 LeeG

LeeG

    Advanced

  • Members
  • 10,523 posts

Posted 26 January 2013 - 04:48 PM

You can run Tools | Diagnostics | Event Viewer at LEVEL 3. Trace a New INSTEON Device and post the results. Every time I have seen that message it means the device is not responding to commands. Could be an RF range problem or the load is not incandescent of sufficient size to provide power to the 2-wire switch.

#3 arw01

arw01

    Advanced

  • Members
  • 912 posts

Posted 26 January 2013 - 04:55 PM

Set your log level to 3 and post the results please.

#4 Bill Morrow

Bill Morrow

    Member

  • Members
  • PipPip
  • 16 posts

Posted 26 January 2013 - 05:05 PM

Sat 01/26/2013 08:04:13 PM : Start Insteon Device Linking Mode

Sat 01/26/2013 08:04:14 PM : [LNK-BGN ] 02 64 01 00 06

Sat 01/26/2013 08:05:36 PM : [LNK-STAT ] 02 53 M(01) gid=00 1F.C9.AD 0124 41

Sat 01/26/2013 08:05:36 PM : [1F.C9.AD 00] Linked device type=01.24 fw=41

Sat 01/26/2013 08:05:36 PM : [1F C9 AD 0 ] Added to list of devices to link to ISY

Sat 01/26/2013 08:05:36 PM : [LNK-BGN ] 02 64 01 00 06

Sat 01/26/2013 08:05:57 PM : Stop Insteon Device Linking Mode, Final processing to follow

Sat 01/26/2013 08:05:57 PM : [INST-TX-I1 ] 02 62 1F C9 AD 0F 0D 00

Sat 01/26/2013 08:05:57 PM : [LNK-END ] 02 65 06

Sat 01/26/2013 08:05:57 PM : [Std MH ] Unexpected Ack imCmd=65 cmd1= 0xAD

Sat 01/26/2013 08:05:57 PM : [INST-ACK ] 02 62 1F.C9.AD 0F 0D 00 06 (00)

Sat 01/26/2013 08:06:02 PM : [INST-TX-I1 ] 02 62 1F C9 AD 0F 0D 00

Sat 01/26/2013 08:06:11 PM : [INST-TX-I1 ] 02 62 1F C9 AD 0F 0D 00

Sat 01/26/2013 08:06:15 PM : [1F C9 AD 0 ] Failed to add device

Sat 01/26/2013 08:06:15 PM : ---- Start: Generate Scenes from links ----

Sat 01/26/2013 08:06:15 PM : ---- End: Generate Scenes from links ----

Sat 01/26/2013 08:06:20 PM : [INST-SRX ] 02 50 1F.C9.AD 1F.24.6B 27 0D 02 (02)

Sat 01/26/2013 08:06:20 PM : [Std-Direct Ack] 1F.C9.AD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sat 01/26/2013 08:06:20 PM : [INST-DUP ] Previous message ignored.

#5 LeeG

LeeG

    Advanced

  • Members
  • 10,523 posts

Posted 26 January 2013 - 05:26 PM

Several unexpected results. First the device did identify itself when the Set button was pressed at Sat 01/26/2013 08:05:36 PM.

Sat 01/26/2013 08:04:13 PM : Start Insteon Device Linking Mode

Sat 01/26/2013 08:04:14 PM : [LNK-BGN ] 02 64 01 00 06

Sat 01/26/2013 08:05:36 PM : [LNK-STAT ] 02 53 M(01) gid=00 1F.C9.AD 0124 41

Sat 01/26/2013 08:05:36 PM : [1F.C9.AD 00] Linked device type=01.24 fw=41

Sat 01/26/2013 08:05:36 PM : [1F C9 AD 0 ] Added to list of devices to link to ISY

Sat 01/26/2013 08:05:36 PM : [LNK-BGN ] 02 64 01 00 06

Sat 01/26/2013 08:05:57 PM : Stop Insteon Device Linking Mode, Final processing to follow


Next the ISY asked the device the type of Insteon Engine which is where the things went wrong. The device did not respond. The ISY issued the Query Insteon Engine again and the PLM did not respond. The ISY issued a third request for the Insteon Engine which the PLM did not respond. Some 23 seconds later after the ISY had stopped the device add process the device the device finally responded with the Insteon Engine type. This delay may have been the PLM rather than the device since the PLM did not respond to the two retries. By the time the ISY received the information about the Insteon Engine the device add process had already ended.

Sat 01/26/2013 08:05:57 PM : [INST-TX-I1 ] 02 62 1F C9 AD 0F 0D 00

Sat 01/26/2013 08:05:57 PM : [LNK-END ] 02 65 06

Sat 01/26/2013 08:05:57 PM : [Std MH ] Unexpected Ack imCmd=65 cmd1= 0xAD

Sat 01/26/2013 08:05:57 PM : [INST-ACK ] 02 62 1F.C9.AD 0F 0D 00 06 (00)

Sat 01/26/2013 08:06:02 PM : [INST-TX-I1 ] 02 62 1F C9 AD 0F 0D 00

Sat 01/26/2013 08:06:11 PM : [INST-TX-I1 ] 02 62 1F C9 AD 0F 0D 00

Sat 01/26/2013 08:06:15 PM : [1F C9 AD 0 ] Failed to add device

Sat 01/26/2013 08:06:15 PM : ---- Start: Generate Scenes from links ----

Sat 01/26/2013 08:06:15 PM : ---- End: Generate Scenes from links ----

Sat 01/26/2013 08:06:20 PM : [INST-SRX ] 02 50 1F.C9.AD 1F.24.6B 27 0D 02 (02)

Sat 01/26/2013 08:06:20 PM : [Std-Direct Ack] 1F.C9.AD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sat 01/26/2013 08:06:20 PM : [INST-DUP ] Previous message ignored.


Has the PLM been giving problems before this? What does Tools | Diagnostics | PLM Info/Status show for the PLM firmware?

What type of load and how much wattage is this 2-wire device connected to?

Might try a New INSTEON Device rather than Start Linking. Not sure it will make any difference. The Event Viewer should be running if New INSTEON Device is tried.

Not sure if this is a PLM issue or a device/load issue at this point.

#6 Bill Morrow

Bill Morrow

    Member

  • Members
  • PipPip
  • 16 posts

Posted 26 January 2013 - 05:47 PM

Thanks.

New Insteon Device worked.

Light is a 300w Halogen, so power snb the issue.

I have not noticed a PLM problem before, but the install is fairly new. I did notice that my ISY99 is complaining about one of my KeyPadLincs after installing the three new RF switches today. Might just be the power cycling causing an issue.

#7 LeeG

LeeG

    Advanced

  • Members
  • 10,523 posts

Posted 26 January 2013 - 06:06 PM

Is that a 120v or low voltage Halogen?

#8 Bill Morrow

Bill Morrow

    Member

  • Members
  • PipPip
  • 16 posts

Posted 26 January 2013 - 06:13 PM

Lamp takes two 150W T3 bulbs.

#9 paauto

paauto

    Advanced

  • Members
  • 140 posts

Posted 02 February 2013 - 05:04 AM

I had the same problem last weekend wiring up some 2-wire devices. 2 of the 3 I was installing gave me the same message you got. At first I thought it was a faulty device and swapped it with another. That worked. I then tried the "bad" device in another location and had the same error. I pulled the air gap button and reset the device locally and that seemed to fix things - the ISY was then able to communicate with it. Same with the third device. No problems after a week of use.

#10 smbaker

smbaker

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 19 April 2013 - 09:17 AM

I ran into the same problem with a switchlinc I bought a few months ago that I'm just now adding to the ISY. The diagnostics are as follows:

Fri 04/19/2013 10:12:55 AM : Start Insteon Device Linking Mode
Fri 04/19/2013 10:12:55 AM : [LNK-BGN     ] 02 64 01 00 06 
Fri 04/19/2013 10:13:17 AM : [LNK-STAT    ] 02 53 M(01) gid=00 1F.72.AD 0120 41 
Fri 04/19/2013 10:13:17 AM : [1F.72.AD 00] Linked device type=01.20 fw=41
Fri 04/19/2013 10:13:17 AM : [1F 72 AD 0  ] Added to list of devices to link to ISY
Fri 04/19/2013 10:13:17 AM : [LNK-BGN     ] 02 64 01 00 06 
Fri 04/19/2013 10:13:27 AM : Setting Time From NTP
Fri 04/19/2013 10:13:32 AM : Stop Insteon Device Linking Mode, Final processing to follow
Fri 04/19/2013 10:13:32 AM : [LNK-END     ] 02 65 06 : : Unexpected, ignored (65)
Fri 04/19/2013 10:13:32 AM : [INST-TX-I1  ] 02 62 1F 72 AD 0F 0D 00
Fri 04/19/2013 10:13:33 AM : [INST-ACK    ] 02 62 1F.72.AD 0F 0D 00 06                 (00)
Fri 04/19/2013 10:13:33 AM : [INST-SRX    ] 02 50 1F.72.AD 22.82.2D A7 0D FF           (FF)
Fri 04/19/2013 10:13:33 AM : [Std-Direct Nack] 1F.72.AD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Fri 04/19/2013 10:13:33 AM : [INST-TX-I2CS] 02 62 1F 72 AD 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6
Fri 04/19/2013 10:13:33 AM : [INST-ACK    ] 02 62 1F.72.AD 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01)
Fri 04/19/2013 10:13:34 AM : [INST-SRX    ] 02 50 1F.72.AD 22.82.2D 27 09 01    LNK-ON (01)
Fri 04/19/2013 10:13:34 AM : [Std-Direct Ack] 1F.72.AD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Fri 04/19/2013 10:13:34 AM : [LNK-BGN     ] 02 64 01 00 06 
Fri 04/19/2013 10:13:35 AM : [LNK-STAT    ] 02 53 M(01) gid=00 1F.72.AD 0120 41 
Fri 04/19/2013 10:13:35 AM : [INST-TX-I1  ] 02 62 1F 72 AD 0F 0D 00
Fri 04/19/2013 10:13:35 AM : [LNK-END     ] 02 65 06 
Fri 04/19/2013 10:13:35 AM : [Std MH      ] Unexpected Ack imCmd=65 cmd1= 0xAD
Fri 04/19/2013 10:13:35 AM : [INST-ACK    ] 02 62 1F.72.AD 0F 0D 00 06                 (00)
Fri 04/19/2013 10:13:36 AM : [INST-SRX    ] 02 50 1F.72.AD 22.82.2D A3 0D FF           (FF)
Fri 04/19/2013 10:13:36 AM : [Std-Direct Nack] 1F.72.AD-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Fri 04/19/2013 10:13:40 AM : [INST-TX-I1  ] 02 62 1F 72 AD 0F 0D 00
Fri 04/19/2013 10:13:40 AM : [INST-ACK    ] 02 62 1F.72.AD 0F 0D 00 06                 (00)
Fri 04/19/2013 10:13:40 AM : [INST-SRX    ] 02 50 1F.72.AD 22.82.2D A7 0D FF           (FF)
Fri 04/19/2013 10:13:40 AM : [Std-Direct Nack] 1F.72.AD-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Fri 04/19/2013 10:13:40 AM : [1F 72 AD 0  ] Failed to add device


#11 smbaker

smbaker

    Newbie

  • Members
  • Pip
  • 6 posts

Posted 19 April 2013 - 09:29 AM

Followed paauto's suggestion of doing a full reset, and now the device can be linked.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users