Discussion in 'VuPlus Duo Hardware troubles and Repair support.' started by DS-1, Sep 28, 2018.
Ok, I'm gonna try it on the front and after with the obh.
Here there is few points,
- PSU of the USB Port (Using an external powered USB Hub would be good to see if it comes form that)
- Image driver, it's VERY important to install from the feeds of the image the driver, and not pick it up from another image, otherwise you will have exactly such problems... so use only the driver of the image, installing them from the Feeds of the installed image.
About my OpenBlackHole, if I remember well all the drivers were on the DM versions, I don't think on the VU+ versions (but you can try, http://www.openblackhole.com).
Let us know,
openblackhole with af9035 drivers makes the box hangs at the boot. It happens also with my other working duo, so I believe it's a kernel drivers not relating to any issue from the box.
Before flashing obh, I was using OpenPli 4 with af9035 drivers from vu+ openpli feeds. I'm also using this image and these drivers on my other working vu without issues.
Now I'll try with blackhole to see what happens.
@toysoft: I know I should use a psu on the hub, but unfortunately I haven't the right jack to use a psu. BTW, I'm gonna try with the hub I usually use on the other working vu, that I always use without psu.
EDIT: ok, I've found a psu for the hub, but it's olny 0.5A. Do you think it could be good to try?
A 500 MAmps is possibly to weak but can not harm to try.
But better is to use a 5vdc 1 or 2 Amps psu.
Ok, now I'm on BlackHole 3.0.5, doing some tests.
BTW, now I remember why I tried (with success) a hub on the other working VU WITHOUT psu: when I used PUS on the hub, the hub obviously was always on. This caused the box sometimes hangs on "starting..." (so it booted but i couldn't access to GUI), sometimes it showed strange characters on the display and also can't read from front usb without remove the hub usb cable. Removing the psu from hub, it started to work like a charm!
I'll update you later what's happening on this vu with hub and 0.5a psu on it.
The issue is still there. Now I'm trying to use the front usb port.
EDIT: nevermind, the issue is here even using the front usb port. Next try: a higher Ampere PSU for the hub?
It seems to me wise to try it with a higher amps psu, however it could also be related to the storage.
The nand flash chip may not be sufficient for using the dtt tuner, a hdd may needed.
But still, since you say that the other receiver has no issues with it, then it could still be related to a hardware issue.
I've found other users in the Net thas has a similar if not equal problem, but no one has solved it. I should try with a completely different dtt usb, but, again, as you told: I have another vu duo with OpenPli 4 on the nand, hub without psu, dtt usb, cf, internal hard drive and I have no issues.
Yeah well I only know that the duo motherboards could be not 100% the same, for example, suppose that the working one has been build in 2014, and the one that failed is from 2012, then it is possible that the 2012 version has no support for a dtt tuner.
These things may be programmed into the cpu.
If the board are from the same year, then it is ofcourse another story.
I believe the working one is older... tomorrow I'll check. This one is the 2.3 revision from 2010.12.28.
Strangely, now I'm trying the usb stick straight to the usb back port of the duo and it's working...bah
If so, then the only logic thing to think of is that it must be related to the 5v amps delivery.
Dunno how to replace the "bug" quickly, because sometimes it happens after 5-10 minutes, sometimes after almost an hour. By the way, the problem came also using only the usb dtt straight in the back usb panel.
Reading some posts on other boards, I've found a user that had a similar problem using newer images. So I came back to the old 2.1.4 Blackhole image, that has older kernel and dvb-t usb driver.
Tomorrow I'll post the results.
Nothing. The issue is still there. I believe it's time to check for another kind of issue.
Yes, the problem is clear, but the reason why it happens is not.
I think that I have already indicated all possibilities, as well as ideas, but sorry at this moment I have no new ideas about this problem.
I'm gonna try it with a completely different tuner, a ITE9135 chipset one.
In the meanwhile, can you please explain me if there's a way to check the voltage on usb ports? I believe it's possible that, after a while, something happens to usb ports...
I think for monitoring the usb port a usb oled display tester could be a good tool for it.
But this is only for the voltages and amps consumption overview.
Basically, by using a external usb hub, one with his own power adapter should be the best way to know if it's related to the 5v delivery from the box.
If both fails, then it seem to me unlikely that it's caused to it.
What happens now is a bit strange to me: testing the duo with ITE 9135 tuner (I had the usual issue using it with the hub), the image freezed and I can do nothing with the remote. I just had to shut it off from the back panel button.
I'm thinking about swapping all the main caps on the board. Over the c807, what other caps should I swap?
Because it is not known why the problem arises, it is also unclear which caps can be responsible for it.
So also whether it is a cap problem.
For the same case, it is a bad soldering on the motherboard of a component, which interrupts when the motherboard becomes warm.
I recommend to randomly cool some areas with a small fan, to find out whether it is related to a cap, or motherboard solder problem.
Of course this takes time, and some luck to try to find it this way.
Another option is to replace all caps, but that too, does not guarantee success.
I've disassembled the main board of the VU and I have done a better solder to C807, then swapped C848 and C819 (used 1000uF 35V for both).
Ok, I've swapped all the those three caps, but the issue is still there.
It is curious that I just need an Enigma2 to fix it. It doesn't need a full reboot. So could it be a NAND issue?
I think I'll try to install an image on USB to try.