|
Page 1 of 2
|
[ 19 posts ] |
Go to page: 1, 2 Next |
| Author |
Message |
|
dolpht2
Joined: Jan 28, 2012 Posts: 1
|
 Cannot connect to 2413U
I have been using Indigo 4 with a PowerLinc 2413U for quite a while with no issues. One day my front lights didn't turn on at sunset as programmed and had previously done with no issues. I researched on the forum and have tried all the suggested remedies. I tried other power outlets, different USB cables, different USB ports (all direct to the Mac), and removed/reinstalled the drivers. I thought maybe the unit had died and ordered a new 2413U. Same issues. I tried a trial version of Indigo 5 and still nothing. Now that I have 2 2413U's I can connect one and select the unit in the preferences and I get the popup that says it's a new unit and needs to be synced. so obviously the program is recognizing something, however, after that it fails. Here's the error log after selecting one of the units for re-sync:
2012-01-28 17:51:50 Application Indigo Cocoa client connected 2012-01-28 17:53:43 Application Connected to PowerLinc 2413U interface on port usbserial-A60089Wu 2012-01-28 17:53:43 Application PowerLinc address 13.AD.2A, firmware version 9.2 2012-01-28 17:53:50 PowerLinc Linking - batch syncing all links for "Living Room Lamp" 2012-01-28 17:53:50 PowerLinc Linking - batch syncing all links for "Front Porch Lights" 2012-01-28 17:53:50 PowerLinc Linking - batch syncing all links for "TMD Garage Door" 2012-01-28 17:53:50 PowerLinc Linking - batch syncing all links for "Kitchen Table" 2012-01-28 17:53:50 PowerLinc Linking - batch syncing all links for "KAA Garage Door" 2012-01-28 17:53:50 PowerLinc Linking - batch syncing all links for "Upstairs Thermostat" 2012-01-28 17:53:50 PowerLinc Linking - batch sync started 2012-01-28 17:53:50 PowerLinc Linking - syncing PowerLinc links (address 13.AD.2A) 2012-01-28 17:53:50 PowerLinc Linking - comparing local and powerlinc links 2012-01-28 17:53:50 PowerLinc Linking - . missing: remote link not found for persistent link 14.28.2E group 01 (adding remote link) 2012-01-28 17:53:50 PowerLinc Linking - . missing: remote link not found for persistent link 13.46.FC group 01 (adding remote link) 2012-01-28 17:53:50 PowerLinc Linking - . missing: remote link not found for persistent link 11.D5.9B group 01 (adding remote link) 2012-01-28 17:53:50 PowerLinc Linking - . missing: remote link not found for persistent link 13.42.91 group 01 (adding remote link) 2012-01-28 17:53:50 PowerLinc Linking - . missing: remote link not found for persistent link 17.75.37 group 01 (adding remote link) 2012-01-28 17:53:50 PowerLinc Linking - . missing: remote link not found for persistent link 14.65.20 group 01 (adding remote link) 2012-01-28 17:53:50 PowerLinc Linking - compare complete 2012-01-28 17:53:50 PowerLinc Linking - . . adding: INSTEON plc link to controller 14.28.2E, flags 03, group 01, data 00 00 FF 2012-01-28 17:53:50 PowerLinc Linking - . . adding: INSTEON plc link to controller 13.46.FC, flags 03, group 01, data 00 00 FF 2012-01-28 17:53:51 PowerLinc Linking - . . adding: INSTEON plc link to controller 11.D5.9B, flags 03, group 01, data 00 00 FF 2012-01-28 17:53:51 PowerLinc Linking - . . adding: INSTEON plc link to controller 13.42.91, flags 03, group 01, data 00 00 FF 2012-01-28 17:53:51 PowerLinc Linking - . . adding: INSTEON plc link to controller 17.75.37, flags 03, group 01, data 00 00 FF 2012-01-28 17:53:51 PowerLinc Linking - . . adding: INSTEON plc link to controller 14.65.20, flags 03, group 01, data 00 00 FF 2012-01-28 17:53:51 PowerLinc Linking - sync complete 2012-01-28 17:53:51 PowerLinc Linking - PowerLinc links updated 2012-01-28 17:53:51 PowerLinc Linking 2012-01-28 17:53:51 PowerLinc Linking - initializing remote device "Living Room Lamp" (address 14.28.2E, firmware version 3A) 2012-01-28 17:54:04 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:04 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:04 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:05 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:05 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:05 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:06 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:06 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:07 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:07 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:07 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:08 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:08 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:08 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:09 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:09 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:09 Error SendInsteonMessage failed 2012-01-28 17:54:16 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:17 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:17 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:17 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:18 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:18 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:18 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:19 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:19 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:20 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:20 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:20 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:21 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:21 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:21 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:22 Error SendInsteonMessage failed 2012-01-28 17:54:28 Error Linking - initializing failed 2012-01-28 17:54:29 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:29 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:29 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:30 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:30 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:30 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:31 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:31 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:31 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:32 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:32 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:33 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:33 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:33 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:34 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:34 Error PowerLinc not responding -- attempting reset 2012-01-28 17:54:34 Power Failure possible power failure 2012-01-28 17:54:38 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:38 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:38 Interface Failure lost connection with interface 2012-01-28 17:54:38 Error resending previous command (busy or unexpected command) 2012-01-28 17:54:39 Error resending previous command (busy or unexpected command)
Any advice is greatly appreciated as I'm stuck.
|
| Sat Jan 28, 2012 5:41 pm |
|
 |
|
matt (support)
Site Admin
Joined: Jan 27, 2003 Posts: 11689 Location: Texas
|
 Re: Cannot connect to 2413U
If you are seeing the same type of errors with both PowerLincs, then I'm inclined to think it is power line noise. Those particular errors means that the PowerLinc is busy or sending a ton of commands to Indigo, and thus Indigo cannot get outbound commands sent. That can occur if there is lots of power line noise.
How many different outlets did you try?
Were they on other circuits?
The easiest way to try a bunch is to just use an extension cord so you don't have to move the Mac. That will help prove/disprove the power line noise theory. The other possibility is 2 bad PowerLincs in a row. But the 2413Us have been very reliable thus far for most folks.
_________________
|
| Sun Jan 29, 2012 7:05 pm |
|
 |
|
finkej
Joined: Jan 28, 2012 Posts: 10 Location: Troy NY
|
 Re: Cannot connect to 2413U
Would power line noise wipe out a 2413, while a 2414 would be happy? I just attempted to replace my 2414 with a 2413, and was getting a similar error - Code: Select all
Connected to PowerLinc 2413U interface on port usbserial-A4016OJT PowerLinc address 1C.F3.A7, firmware version 9.9 Error resending previous command (timeout) Power Failure possible power failure Interface Failure failed to establish connection with serial interface PowerLinc 2413U on port usbserial-A4016OJT Error unknown command bytes received 03 15 (ignoring) Power Failure possible power failure Interface Failure failed to establish connection with serial interface PowerLinc 2413U on port usbserial-A4016OJT Power Failure possible power failure Interface Failure failed to establish connection with serial interface PowerLinc 2413U on port usbserial-A4016OJT Power Failure possible power failure Interface Failure failed to establish connection with serial interface PowerLinc 2413U on port usbserial-A4016OJT Error unknown command bytes received A7 03 (ignoring) Power Failure possible power failure Interface Failure failed to establish connection with serial interface PowerLinc 2413U on port usbserial-A4016OJT Power Failure possible power failure Interface Failure failed to establish connection with serial interface PowerLinc 2413U on port usbserial-A4016OJT Power Failure possible power failure Interface Failure failed to establish connection with serial interface PowerLinc 2413U on port usbserial-A4016OJT Power Failure possible power failure Interface Failure failed to establish connection with serial interface PowerLinc 2413U on port usbserial-A4016OJT Connected to PowerLinc 2413U interface on port usbserial-A4016OJT PowerLinc address 1C.F3.A7, firmware version 9.9 Power Failure possible power failure Interface Failure failed to establish connection with serial interface PowerLinc 2413U on port usbserial-A4016OJT
For now, I just put the 2414 back into place.
|
| Sun Apr 29, 2012 4:39 pm |
|
 |
|
matt (support)
Site Admin
Joined: Jan 27, 2003 Posts: 11689 Location: Texas
|
 Re: Cannot connect to 2413U
I'd say that is unlikely, but before shipping it off for a replacement, I would try:
• Other USB ports. We recommend the ports on the Mac, but try others as well.
• A different USB cable. It is a pretty standard cable, so swap it out with a printer/scanner.
• Different outlets on different circuits. Use an extension cord so you don't have to move the Mac around.
• Factory resetting the PowerLinc: unplug it from the outlet, hold the SET button for 3 seconds or so, then plug it in and continue to hold the SET button for 10+ more seconds, then release.
If none of that helps, then I think you have a bad 2413U. So far they have been much more reliable than the 2414Us, but it is still possible to get a malfunctioning unit, of course.
_________________
|
| Mon Apr 30, 2012 3:20 pm |
|
 |
|
finkej
Joined: Jan 28, 2012 Posts: 10 Location: Troy NY
|
 Re: Cannot connect to 2413U
I think I have eliminated the hardware as a problem. I installed AHC under a Windows 7 VM running in Parallels on my mac, and it was able to use the 2413u (after installing the FTDI driver in windows. I was able to add a module, and then build the device list via Insteon queries.
So, I have a one year old iMac, running Lion, and the latest release of Indigo - Suggestions of what I should try - the iHealth program gives me a perfect score - 100% failure. I suspect some flakey USB cables in previous tests, but the Windows 7 test demonstrates that current USB cable is ok.
|
| Sun May 06, 2012 8:06 pm |
|
 |
|
matt (support)
Site Admin
Joined: Jan 27, 2003 Posts: 11689 Location: Texas
|
 Re: Cannot connect to 2413U
I'm at a loss on this one. I know we have quite a few users running Lion on Macs (including the iMac) with the 2413U. I presume you tried all of my suggestions above, including trying other USB ports? Also disconnect all USB devices except the 2413U and your keyboard/mouse.
The errors you are receiving show both unexpected bad/corrupt data from the 2413U and also FTDI driver level errors which is causing the communication channel to be reset (which causes the "possible power failure" message Indigo shows). The only thing I can think of is that you have a marginal 2413U, and the Mac version of the FTDI driver is less tolerant of its bad behavior than the Windows FTDI driver.
If you try a replacement 2413U then please let us know the results.
_________________
|
| Mon May 07, 2012 7:13 am |
|
 |
|
finkej
Joined: Jan 28, 2012 Posts: 10 Location: Troy NY
|
 Re: Cannot connect to 2413U
Argh....
When did I install Domoto? Once I stopped that server, things got MUCH better with the 2413U. I guess it didn't support the 2414, so I didn't have trouble with that interface.
Thanks for the help - things seem much better now.
And the iHealth App is cool!
|
| Mon May 07, 2012 2:02 pm |
|
 |
|
matt (support)
Site Admin
Joined: Jan 27, 2003 Posts: 11689 Location: Texas
|
 Re: Cannot connect to 2413U
Ahh, thanks for the feedback. I didn't realize their server would take over the PowerLinc communication like that and cause issues.
_________________
|
| Mon May 07, 2012 3:18 pm |
|
 |
|
morps
Joined: Nov 01, 2003 Posts: 117
|
 Re: Cannot connect to 2413U
I am having a similar issue as this thread reports, but I have *never* been able to get the 2413U to work. I can successfully remove it and replace with a 2414U and it works fine. Here is a snippet from my log. Do I have a bad 2413U? - Code: Select all
Connected to PowerLinc 2413U interface on port usbserial-A4016ST6 PowerLinc address 1C.F6.AC, firmware version 9.9 PowerLinc Linking Interface Failure lost connection with interface PowerLinc Linking - initializing remote device "Light: Outside Basement Stairs" (address 03.80.AE, firmware version 27) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error SendInsteonMessage failed Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error resending previous command (busy or unexpected command) Error SendInsteonMessage failed Error Linking - initializing failed
Note that this is the same behavior for every single one of my devices. Thoughts?
|
| Sun Jun 10, 2012 9:55 am |
|
 |
|
matt (support)
Site Admin
Joined: Jan 27, 2003 Posts: 11689 Location: Texas
|
 Re: Cannot connect to 2413U
If the 2414U works in the exact same outlet, and you cannot get the 2413U working in a different outlet (on a different circuit -- use an extension cord if needed), then I'd say the 2413U is not working correctly.
_________________
|
| Sun Jun 10, 2012 10:00 am |
|
 |
|
morps
Joined: Nov 01, 2003 Posts: 117
|
 Re: Cannot connect to 2413U
Yup, that's what I suspected. RMA time. Thanks, Matt.
|
| Sun Jun 10, 2012 10:09 am |
|
 |
|
asherms1
Joined: Apr 21, 2012 Posts: 7 Location: Ellicott City, MD
|
 Re: Cannot connect to 2413U
I had my 2413U up and running and controlling four devices for several weeks. Then I changed the USB arrangement to add a printer and nothing works. (None of the outlets were changed etc.) Is there a compatible Insteon USB interface for Indigo 5 that actually works -robustly-? In looking at the above threads it seems like a lot of users with more experience than me are having problems running this with a Mac. I refuse to install Parallels on my Mac, but i would consider getting a castoff desktop PC if that solved this problem. Any thoughts? I have spent about $1200 on Insteon products, and some of them are still in boxes, at this point I am contemplating returning them all and going back to local timers. MA Attachment:
IdigoMessage.tiff [ 70.94 KiB | Viewed 232 times ]
|
| Sun Jul 15, 2012 4:44 am |
|
 |
|
jay (support)
Site Admin
Joined: Mar 19, 2008 Posts: 6655 Location: Austin, Texas
|
 Re: Cannot connect to 2413U
If you're connecting your 2413 through a USB hub then that's likely the problem. Timing-sensitive devices often don't work through many USB hubs. It could also be another device on the USB bus causing an issue. This is less a problem with the PowerLinc and more an issue with USB devices that don't precisely follow USB protocol specs. And it has nothing to do with the Mac.
Looking at the image above, the FTDI driver isn't even seeing the 2413 any more since it says port not found so I'd undo what you did, make sure it works, then attempt to arrange the USB devices differently in terms of connections.
_________________ Jay (Indigo Support)
|
| Sun Jul 15, 2012 8:23 am |
|
 |
|
asherms1
Joined: Apr 21, 2012 Posts: 7 Location: Ellicott City, MD
|
 Re: Cannot connect to 2413U
No hub. USB connected directly to iMac port. Tried different cable. Same result.
|
| Sun Jul 15, 2012 3:41 pm |
|
 |
|
asherms1
Joined: Apr 21, 2012 Posts: 7 Location: Ellicott City, MD
|
 Re: Cannot connect to 2413U
And yes, computer has filtered power. 2413U is on extension cord to remote outlet. Going to try some more outlets now.
|
| Sun Jul 15, 2012 3:48 pm |
|
|
|
Page 1 of 2
|
[ 19 posts ] |
Go to page: 1, 2 Next |
Who is online |
Users browsing this forum: No registered users and 1 guest |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|