I recently had some setup changes, which made my problem reoccur. It never really went away, but now frequency is up again to approx once per day. So 2 years after, my issue still hasn't been solved. Regarding earlier comments in this thread;
Tieske wrote:I have now rerouted my emitter cable (which were lying around the amplifiers) in another way. Only for 4 days now, but so far so good, I'm hoping this will solve my issue but need some more time to be convinced its been resolved.
That didn't work, problem stayed.
mrceolla wrote:Either way though, the UIRT's receiver light still blinks when it receives IR. So it may be still receiving...it just stops sending.
Never noticed this before, but indeed mine shows the same. Girder throws error messages, and no led blinks when sending commands. But the led still blinks when it receives IR.
zackcorn wrote:Use Ferrite beads on your emitter wires (It helps sometimes reduce EMI, and in weaker cases should solve the problem)
I tried this as well, also to no avail.
Recalling my issue: the USBUIRT fails when I send a power-on/off command to my 5.1 amplifier (randomly offcourse, but always on one of these commands).
I went to a local electronics shop to try and find something that I could use to shield the emitter wires (as suggested in some post, using alu foil). But they didn't have anything I could use for it, but the guy at the counter told me that he didn't think the EMI was the issue, he figured that it had to be noise on the power circuitry.
Anyway; The amplifier always makes a big 'boiinng' sound when switched on, so I insisted on the EMI and he sold me a resistor that only lets power come-up slowly (when its cold, it is highly resistive, and it reduces while it gets warmer. Effect; when power is switched on the power is only slowly comming up to the full power). It worked on the amplifier as it now no longer makes the big "boing" noise when it power up. So EMI now has to be a lot less. But USBUIRT still dies. So another option down.
But it brought me to the point of considering the noise on the powerline to be the cause. After my setup changes I also have a lot of X10 failures. X10 was unreliable already, but now nearly stopped functioning at all. That was another reason to suspect the power supply. In the past I also had trouble with the server being unstable, this was resolved by properly grounding the power supply. Since the server has been stable.
The solutions by yaccri also lead me this way
yaccri wrote:I found the following:
- Replacing the computer may help. Some computers are better at handling USB.
- Reducing the number of devices that are connected by USB may help.
- Increasing the delay between commands helps
- As a last resort, I use 'devcon' to automatically restart the device
The first 2 items indicate a power related cause. A longer delay didn't change anything for me.
I never used devcon. I tried disabeling and reenabeling the device from devicemanager, but that doesn't work to get it back alive.
For now I've added ferrite beads on the USB cable, and no longer on the emitter cables. I added 2, near the USB connector and the other as close as possible to the USBUIRT.
Other options I'm considering;
- using a powered USB hub inbetween
- adding a noise filter to the power supply