Page 1 of 1

Communication failure in Lion

PostPosted: Wed 21. Dec 2011, 15:02
by smfrank
iRed 2.0/iTrans USB working fine in Lion.
Plugged directly into USB - no hub.
All of a sudden, I get:
2011-12-21 09:57:38.782 Info: Connected to 1 IRTrans module(s)
2011-12-21 09:57:41.633 Error: Connection failed, now trying to restart communication to IRTrans ….
2011-12-21 09:57:41.646 Error: Command 1 to IRTrans module failed with error 105
2011-12-21 09:57:44.696 Info: Connected to 1 IRTrans module(s)
I have reinstalled everything.

Have contacted Robert Fischer (iRed) and he is puzzled.

Here's my driver info:

FTDIUSBSerialDriver:

Version: 2.2.16
Last Modified: 2/28/11 10:49 AM
Kind: Intel
Architectures: i386, x86_64
64-Bit (Intel): Yes
Location: /System/Library/Extensions/FTDIUSBSerialDriver.kext
Kext Version: 2.2.16
Load Address: 0xffffff7f811d4000
Valid: Yes
Authentic: Yes
Dependencies: Satisfied

Any suggestions?
BTW, works fine on another computer, so not a hardware problem.

Re: Communication failure in Lion

PostPosted: Wed 21. Dec 2011, 19:16
by IRTrans
Hi,
did you try a different USB Cable?

What does the Status LED of the IRTrans device do?

IRTrans

Re: Communication failure in Lion

PostPosted: Wed 21. Dec 2011, 21:22
by smfrank
Yes, I've tried another USB cable.
When I plug it in, I get green, then red, then none.
Any command selected in iRed2 results in the above error, and the status LED does nothing.

Other info: s/n 17217
Firmware: U5.03.24
On back of unit: USB 3.5

It was working fine until Friday morning. Just stopped responding.

Works on my MacBook Air running OS 10.7.2
Just tried 'removing' the IR module then adding it as new.
Same problem. Help!

Re: Communication failure in Lion

PostPosted: Thu 22. Dec 2011, 00:26
by IRTrans
Hi,
no idea what the problem might be here.

As it is working with other computers I do not think it is a hardware problem.

IRTrans

Re: Communication failure in Lion

PostPosted: Thu 22. Dec 2011, 13:08
by smfrank
IRTrans wrote:
As it is working with other computers I do not think it is a hardware problem.



I said that in my first post.

I was looking for some help regarding the software conflicts, drivers, etc..

Never mind.

I did a clean install of Lion and everything is fine now.