Duo2 Dead - White LED / Blank VFD and no Boot

[Catface]

I bought the Duo2 last October from world-of-satellite.co.uk running VIX 3.xx with the CFE V2 Bootloader and it's been flawless until now, about an hour ago, the screen went blank and now the box appears to be dead.

When the Duo2 is powered up from the switch at the rear, the white LED lights up, the HDD spins but there's nothing on the VFD screen and the system won't boot.
It doesn't appear to be possible to load anything from the front USB since the prompt on the VFD screen doesn't show.

Is there a tool similar to the ones used for boxes like the DM500 to reflash the box if it's a software corruption issue? I really hope it's something not too difficult to rectify.
I did a search to see if anyone else had a fix for this but all I found were some people with the same problem with no solutions.

I'm grateful for any replies :)

[zoro25]

Have you tried to use a usb with an image on it to see if it will flash a clean image?

It also might be an idea to remove the HDD so you rule that out.

[Stanman]

When using the front usb make sure you don't have another usb stick attached.

Is there anything on the video

Sent from my SM-N9005 using Tapatalk

[Catface]

Thanks for your responses.

Here's what I've tried so far.
Starting with no USB devices attached.
Disconnecting the HDD,
Attempting to load an image from the front USB. (no other USB devices are attached)
Starting without the twin DVB-S2 and DVB-T tuner cards.


What makes it difficult is the box doesn't get to the stage where the prompt to update from the front USB appears. It used to boot with the VFD displaying CFE V2 and then "double your expectation" would appear followed by a message asking to press the power button for an update. There's no video on the screen and nothing appears on the VFD or LCD at all, possibly indicating that the basic functions of the receiver aren't starting. It behaves as if it's stuck in deep standby mode, the HDD spins up when it's connected but the fan doesn't spin.

The inside of the unit is immaculate with next to no dust. The white LED flickers when the front button is pressed, no response from the remote.

[marty]

Possible power supply failure?

[Catface]

It's possible it's the power supply but it's unlikely since when the rocker switch on the rear is switched to the on position the HDD will spin up, the white light on the front will light up and the tuner will get warm after a while so power must be reaching the rest of the unit.

There doesn't appear to be any tools where if the memory containing the bootloader is corrupt it can be read and corrected. I doubt it is as I wasn't flashing an image or making any alterations, the box was playing a recording from the HDD when the picture went off for the last time.

It could turn out to be a hardware fault and the box will have to be sent back. It's disappointing because it's been superb so far.

[nickj]

I had the same problem. I press the black button on the top of the front USB slot and the box start for me.

[DaMacFunkin]

It's possible it's the power supply but it's unlikely since when the rocker switch on the rear is switched to the on position the HDD will spin up, the white light on the front will light up and the tuner will get warm after a while so power must be reaching the rest of the unit.

There doesn't appear to be any tools where if the memory containing the bootloader is corrupt it can be read and corrected. I doubt it is as I wasn't flashing an image or making any alterations, the box was playing a recording from the HDD when the picture went off for the last time.

It could turn out to be a hardware fault and the box will have to be sent back. It's disappointing because it's been superb so far.Thats exactly how mine ended up although it didn't go quietly it was a downward spiral from the off, you will need to send it back to Vu, I got pissed off with s**tems*t messing me about so I contacted Vu+ myself and sent it back, after having it in their possession for 2 weeks they said they couldn't repair it and sent me a new one (thanks Julian).

[Rob van der Does]

Only a bootlog (rs232) can shed some light on what's going on.

[Catface]

I had another look it it over the weekend, trying to see if I could get any information from the RS232 connection using PuTTY and HyperTerminal, selecting the correct COM port and 115200 baud. Most of the time there was no response at all apart from a couple of odd occasions where very few garbled characters were displayed. The DM500 worked perfectly with the boot sequence displayed so I've come to the conclusion that it's a hardware fault

It's a shame there aren't at least some basic recovery tools that use the RS232 port for the Duo2. The image support is fantastic but it's shocking that there appears to be nothing available for restoring fundamental features of the system like the bootloader, especially considering it's been out for nearly a year now. I'd expect poor support for clones, but not from genuine boxes that cost £400+. I know in my case it appears to be a hardware fault but I wish there were programs that could be used to rule out software issues sooner.

It looks like sending the receiver back for replacement or repair is the only option now. Just my luck when the World Cup is about to start :mad:

Hopefully I'll get it back and up and running soon. Thanks to everyone that responded :)

[mimi73]

hi to all

the same problem with the famous white light

after installing the latest bootloader Duo2_CFE_V2 and the last image of BH

he does not want to start it stops on the white light only no boot detect.
the fan does not work
it does not detect any USB device so that I can flash
(I tried 4 different types of USB .. with different version of images .. and also different Original Version .. nothing is happening with duo2 .. just the white light present)


http://www.youtube.com/watch?feature=player_embedded&v=L2Pfy0oRf5w

Now I'm sure this is a hardware fault

unfortunately it has no support solution with rs232
shame vu +

according to my research on this subject, this is the case of many people.
what breaks me is the cost we pay for a failed technology.

vu + do not believe it too just false advertising, I should choose the last competitor reliable and stable .. :mad:

the video is not mine (another victim)
but this is my scenario too.

[Rob van der Does]

I had another look it it over the weekend, trying to see if I could get any information from the RS232 connection using PuTTY and HyperTerminal, selecting the correct COM port and 115200 baud. Most of the time there was no response at all apart from a couple of odd occasions where very few garbled characters were displayed.
'Garbled characters' probably mean wrong settings.
Can you check please? 36426



It looks like sending the receiver back for replacement or repair is the only option now.
Surely the box must still be within warranty?

[mimi73]

Now it works with the original image

he started himself; after almost 3 hours waiting

may be the problem is in:

the new bootloader
or the various new images
or a default constructor

:smiley_yup:

[mimi73]

I hope it works for you

[DaMacFunkin]

I had all the same problems you if it is working now it will randomly lock up and eventually give up the ghost, the garbled characters seems to be when it can't read the flash, I suspected dodgy soldering although it could be capacitors not discharging properly which would explain how it can suddenly reflash and work again after a few hours, I bet any money it only had version 1 boot loader on it when you recieved it, even though they have been shipping with v2 fir nearly a year.
After having mine replaced because Vu couldn't repair it I havnt had one lock up or crash whatsoever.

[Rob van der Does]

.... the garbled characters seems to be when it can't read the flash,
Very unlikely; what is being read is the talkback from Linux, not from flash.

[marcus1975]

Hi all

This has also happened to me lately :confused:

my box is just coming up to 2 years old and out of warranty (very sad)

since this last post has any one found a fix or now of a repair ?

thanks

[bellejt]

I had the same with my duo2 as mimi73.Is in repair now already 8 weeks.Bad service from VU+.

[marcus1975]

Hi

will they repair boxes out of warranty ?

thanks

[:-)]

Bellejt - what happened to your Duo2 in the end? Your sign off mentions latest openVIX - did you have 3.2 on there? Is flashing 3.2 what killed it?

Sounds like poor quality capacitors fitted by the manufacturer.

Opened my (currently working) Duo2 today to be greeted by mainly "Samyoung" brand electrolytic capacitors - Samyoungs are known troublemakers in other Korean made set top boxes - worse still they are only 85c temperature rated because Vu+ wanted to save money plus it seems to be a good business model to build in obsolescence using cheap capacitors - even the garbage capacitors Sky fitted to their infamous Thomson power supply boards were at least rated to 105celcius - funny how Sky fitted quality capacitor brands to the Thomson motherboards but deliberately fitted rubbish to the adjacent PSU board in the same receiver.

Changed & upgraded the capacitors myself in my SKY Thomson SD & HD boxes (same PSU's) - they both worked perfectly after that - or rather I initially fitted a ready made kit (that everybody raved about online at the time) BUT the kit failed after only just under a year - SO de-soldered the lousy kit capacitors & mailed it all back (to the suppliers horror!) got a refund - THEN made up my own kits and finally had some peace as the SKY HD & SD boxes then kept working for years!

Catface - sorry to disagree with you but power supplies generally seldom go totally dead - unless the primary [mains voltage] side develops a fault - then they generally go KA-BOOM & then totally dead while cryptically managing to only blow the 3 or 5 Amp fuse in the plug while leaving the generally 1Amp fuse on the PSU PCB intact.

PSU's generally manage to fail by gradually fading away for instance the output filtering caps. on the secondary [low voltage] side can fail meaning that the relevant voltage is still there (but it needs to also be accurate so a +5volt rail reading that is slowly moving around or solidly reading +4.89 [or even +5.15] is enough to be faulty - it has to be practically dead on spec while under its normal operating load) but with enough mains borne AC noise (as DC output filtering caps are past it) superimposed over what is meant to be a smooth & clean DC supply that the Duo2 CPU cannot function correctly as it needs clean & smooth DC power - you would need an oscilloscope to spot that a multi-meter generally couldn't see it (if it was really bad try seeing if you can read any AC voltage on a DC PSU voltage output line - again depends on the quality of the multi-meter - if you find AC where there is only meant to be DC you have a problem).

If it were me I would start by changing all the caps. on the PSU and seeing what happens - then I would re-cap the motherboard electrolytics - take apart the front panel & re-cap any electrolytics that might be lurking in there - likewise do the tuner modules in the same way - after that I would look at the polymer and SMD type caps on the motherboard and replace those - upgrading as I go of course!

The only good thing about Sky boxes is the ability to force download of fresh non-corrupt firmware by holding down backup button and applying mains - although theoretically flashing new firmware by USB should achieve the same thing on a Duo2 - lack of adequate power would prevent replacement (non-corrupt) firmware being written to the flash memory chips as writing to the flash memory generally needs higher voltage than the normal memory read function voltage so that could be why people cannot get the same USB pen drive to work to flash update firmware (vix version) as before because there is now inadequate power to complete the programming process.

Anyway could keep writing endlessly on the topic but am off to bed - you might have guessed by now I am keen on replacing cheap capacitors (changed 65 caps on one of my computer motherboards - it solved a BIOS problem it was having last year) let me know how you all get on.

You know I thought I was detecting a slight hesitancy creeping in to my Duo2's otherwise smooth operation (not like when it was brand new at all!)- faulty caps become temperature sensitive - maybe my Duo2 is looking to give me an excuse to pounce on it with a soldering iron - I thought it was Hades that was the problem so was planning to go to 3.2 when I had the patience to do so but maybe it is the capacitors and they had it coming all along!

[Rob van der Does]

.....Is flashing 3.2 what killed it?......
What kind of suggestion is that? Did you ever hear of any image killing any box at all :confused:

[:-)]

What kind of suggestion is that? Did you ever hear of any image killing any box at all :confused:

If you read the third paragraph from the bottom of my post that you quote the beginning of you will find that the act of FLASHING itself (meaning any image) could kill a box with a power supply that is failing.

In simpler terms reading a non-volatile memory chip happens at one voltage (it used to be 5.0volts on every non-volatile memory chip but newer more power efficient memory chips take less voltage to read so it could be as little as 2.5volts to read - it depends on the actual chip being used but it will still be a higher voltage to write to the chip and possibly a third different voltage to erase the chip - it depends on the exact chip and its design architecture) and writing new data or changing some data on the chip will require a higher voltage for a 5.0volt read memory chip you used to need at least 6.75volts to write and around 9.0volts to fully erase the non-volatile memory chip (not to be confused with computer Memory [RAM] which is volatile memory so all data is lost the moment power is disconnected).

So if a PSU is failing it generally loses output capacity measured in Amps - to create the higher NVM WRITE voltage the motherboard will draw more amps from PROBABLY the 5.0volt PSU rail and step it up to whatever voltage is required to WRITE to the NVM chip which will not reliably happen so corrupting the NVM.

Grundig SKY boxes used to have a known PSU fault (about 10 years ago) so when Sky updated the firmware OTA the box would download then erase NVM fail to successfully write the new firmware to the NVM and leave you with a bricked Grundig Sky box - to fix it you had to repair the PSU & then extract a known good firmware from another Grundig Sky box and flash that using a chip programmer into the repaired Sky Grundig box & finally the box would come back to life.

So I think when the Duo2 does an update it fails to correctly re-flash the NVM (due to a lack of voltage from a lack of PSU current) and that is why the boxes get stuck in a boot loop.

I thought I read on the forum that clone boxes get deliberately bricked by original images - but that is not what is being discussed here - The hunt for the elusive clone box - nothing like a bit of clone hysteria to maintain price support i.e. that box is cheap, so must be a clone - better spend an extra hundred pounds to get a genuine one with the genuinely cheapo capacitors!!!!!!

Best Regards

[bellejt]

the box worked fine after flashing.Is now 11 weeks away in repair.Vendor says that 12 weeks seems to be a normal repair time for VU+.Talking off service from VU+ I'll be waiting until the box is back. If it takes to long I will start a law suite to the vendor en VU+ for a full refund because off lack off service under warranty.
Seems that ther is also a strange warranty problem : my belgium vendor gives 2 years and the other gives 3 years. I have 2 boxes here.

[:-)]

bellejt - Hopefully your other box will behave itself!

Sure you all already know but there is always the "eu directive 24 month warranty" (Google it) which is meant to give everything sold in the EU an automatic 2 year warranty - which could prove useful if somebody is stuck with a potential £400 (ish) loss from a dead Duo2 box on their hands.

In general do you all keep your Duo2's on a shelf by themselves to keep them cool or are they in a stack of hot equipment?

There is a distinct constant hot spot on my Duo2 on the top of the plastic above the Infra Red receiver - do they all do this?

Does the number of tuners internally plugged in plus the two possible external USB Cable tuners as well (potential total of SIX Tuners - which is why I got a Duo2 in the first place) increase the current load on the Duo2 and cause them to fail?

What about motorised dishes? Don't yet have one but intend to get one.

Always wondered if you use one of these http://www.world-of-satellite.co.uk/DiSEqC-Motors-Positioners and all the power comes direct from the receiver as well along the Coaxial satellite cable isn't the total applied current load going to start getting pretty high for the receiver to handle all by itself?

My intention was to get a 1.2m motorized dish using a gadget like this "satellite positioner" (Google.Com it) to take the Diseq command off the co-ax and separately provide power from the gadget directly to a SuperJack (Jager) linear Ram type dish mover - then I spotted this on http://www.amazon.com/ASC1-Satellite-Actuator-Positioner-Controller/dp/B00HUJA6NA looks like a beast of a gadget compared to the rest - bit too pricey - but of greater interest is the current ratings on the back panel (you can see in the amazon rear photo) 38Volts DC at 5Amps dedicated just to operating the SuperJack & not drawn from the satellite box itself - voltage is too high for a Diseq positioner powered down the coax obviously but it raises the question about total possible applied load to the Duo2 sat box vs. what can the sat box comfortably supply to drive everything without failing?

I am not recommending any of this stuff http://www.superjack-solar.com/ (shows more) not sure what to buy for my self but apart from its cost I like the look of http://www.titaniumsatellite.com/asc1 like a sledgehammer to crack a nut.

I just want to motorize a big dish WITHOUT making my Duo2 fail - to this end I think it would be safer to have an external Dish moving PSU.

Any thoughts anyone???

[bellejt]

both my VU duo2's have a temp from under 39 degrees in full working condition.I also have a dish with motor SG 2100 and working fine.The rotor can have dishes to up 1.20 m.Usals are used for positioning.The main box has also a 1 TB HDD.In the main box also 2 dual twin tuners.

[:-)]

bellejt - have you set the fan to keep running in the Duo2 when it goes in to standby? Flashed my Duo2 with four different VIX images over time and so far each one turns the fan completely off for standby - personally I think that is asking for trouble and it is an easy setting to miss.

By "SG 1200" I think you mean this http://www.galaxy-marketing.com/sg2100.htm which looks like a good motor and I am sure it can drive 1.2m dishes BUT my personal worry is that on the link the spec says it draws a load of between 200mA to 350mA on to the Duo2 (50mA in Standby Mode - I presume that means not when watching a channel?).

My personal opinion is that the kind of motor (that is very popular) that you have been sold (the SG1200) that takes its power only from the Duo2 (via the Co-Ax ONLY) turns the Duo2 into a very expensive power supply that will have its life shortened by driving the motor at what looks like (from my initial reading) a constant 200mA which is a lot of current (relatively speaking) for any satellite receiver to supply.

The difficult question to answer is how much spare capacity in Amps does a Duo2 have after running its motherboard, the two display boards, the hard disk and all the connected tuners?

It must by design have at lest enough spare current capacity to run all the items listed in the above paragraph (current draw of the Hard disk is the only real variable in the list) or legally it would have a design fault built in to it (Design Fault = Refund time as fault existed from the outset) BUT is there any current (Amperage) left over to also power a dish motor directly & is it enough?

Again it is possible load vs. actual applied load and how much load does the voltage drop of the cable run to the dish where the motor is add plus the voltage drop of the connections which steadily corrode especially outdoors so the voltage drop goes even higher taking the applied load higher with it - I use solder on F - Connectors to stop corrosion.

The Duo2 designers must (or at least they should - but it costs money to build in spare capacity) have allowed for all that - but cooling is a variable - BUT can the Duo2 also supply the added load of the SG 1200 (or any of that type or motor) on top of everything else - or do Satellite Equipment Dealers make a healthy living out of the Co-Ax only powered dish positioners rapidly blowing the satellite receiver?

bellejt - No matter what you are entitled to a full repair or replacement of your Duo2.

But personally I would never use a relatively expensive Duo2 to directly power any positioner (like the SG1200) via the Co-Ax - But I am not disputing that it all works just that it could be overloading the Duo2 and causing it to fail early.

I personally would go to the extra trouble and expense of laying the 5/6core motor power and sensor cable use a superjack type linear ram actuator (trying to figure out exactly which one myself) and control the superjack probably using that overpriced monster of a positioner I have my eye on (the Titanium Satellite ASC1 - look at its current output 5Amps that is 5,000mA!) that way the Duo2 passes its Diseq commands to the ASC1 (or whatever similar gadget you prefer instead) it interprets the command and moves the dish using power from the ASC1 NOT the more precious Duo2 so the dish motor cannot put any load on the Duo2 so the Duo2 cannot be harmed by that cause.

There is also an argument if you go for superjack type ram positioner over whether you should get the superjack with reed switch position sensors or optical type position sensors - the controller will have to be able to understand the sensor type you go for.

Opinions?

[Rob van der Does]

I always use FanControl2 to be able to monitor the temperature of the DUO2 (and other boxes). Temp is always around 45 degrees, which is really low.

[:-)]

I was looking at the temperature of my Duo2 last night - the highest the temperature ever got was 26C after a couple of hours while recording two HD channels and watching a third HD recording – now that is what I call a low operating temperature.

I do not use any fan control program other than the one built into the standard VIX image – but I do set the fan to run slowly & constantly in standby mode.

Does that mean that the relatively high temperatures you both report are caused by a worsening electrical fault developing in your Duo2’s meaning impending failure OR electrical overload OR being in a stack of hot equipment with inadequate ventilation?

I have an internal 1TB 3.5 inch HDD and a dual input single satellite tuner card in my Duo2.

The fan arrangement in the Duo2 has always struck me as totally daft – it is an odd size at 50MM by only 10MM thin! And there is a huge amount of adjacent internal empty space to accommodate a much thicker fan – if only it was a 60MM fan instead of the 50MM you could easily get a 25MM thick fan in and then really shift some air with the deeper fan blades – you can even get very deep 35MM fans in 60MM Diameter which I would mount on rubber pins instead of steel screws & probably cut out the back panel metal grille for maximum airflow & silence.

Strangely the Duo2 fan is nosily mounted using metal screws – even SKY Satellite boxes (when they finally started fitting fans to them) fans were mounted not with metal screws but soft rubber pins instead to decouple the fan from the metal chassis and stop fan noise – Vu+ instead rubber mount the internal Hard disk – so why not the fan as well?

Considered using a duct (like this http://www.frozencpu.com/products/6075/duc-43/40mm_to_60mm_Aerodynamic_Fan_Adaptor_-_UV_Green.html?tl=g47c121s442&id=Se8gxccu ) externally mounted to change the fan size but no 50MM ducts existed when I last looked – then decided not to bother modifying that duct or do anything as according to the reading it runs cool at 26C anyway.

Where does the Duo2 get an idea of the Fan RPM from? After all it is only a 2 wire connection so the box has no idea from a third RPM feedback wire if the fan is even running or if it has failed – measuring fan current draw would be daft as if the fan locked up or the bearings went stiff from dirt the current draw would go up not down & the box would not have a clue – till overheating shuts it down!

Do your fans actually run? Have you looked & checked? Can you see them spinning?

Then again a lousy 50MM skinny fan that is an odd & difficult to change size that is also hard mounted with screws to make yet more noise which would overall discourage fan use – that combined with four different VIX images that do not run the fan at all in standby (under default settings) is a recipe to sell a lot more Duo2’s!

Rob & bellejt you both have motorized dishes is that what is causing the heat issue?

Rob describe how you turn your dish?

bellejt I think you and I were both complaining on another thread that Hades ruined the PiP function that was previously working on our Duo2’s Rob I think you were commenting in the same thread.
http://www.world-of-satellite.com/showthread.php?45452-Hades-Bug-PiP-Sound-amp-Front-Panel-Colour-LCD-no-longer-shows-current-progarmme-name&highlight=Pip+Hades

bellejt – by any chance is the box that you have in for repair the one that PiP on Hades stopped properly working on? If it is that means my Duo2 will conk out too!

If you have got that same Duo2 with the PiP fault now running on VIX 3.2 is PiP now fixed? Does PiP failure imply looming box failure?

Or has your box come back from repair and PiP function is now working again?

My Duo2 was bought in May 2014 how old are your Duo2’s?

Best Regards

[Joe_90]

Get a grip, man - no processor runs at 26C! That's only marginally above room temperature in the UK or Ireland. It's below room temperature if you live in southern Europe:eek: A fanless CPU or GPU will run 80C+ easily and a fan will reduce it to 45C or thereabouts. If you are seeing temps of 26C, then there is either an error in the driver software or it is a case temperature rather than an actual CPU or GPU temp.

[:-)]

Get a grip, man - no processor runs at 26C! That's only marginally above room temperature in the UK or Ireland. It's below room temperature if you live in southern Europe:eek: A fanless CPU or GPU will run 80C+ easily and a fan will reduce it to 45C or thereabouts. If you are seeing temps of 26C, then there is either an error in the driver software or it is a case temperature rather than an actual CPU or GPU temp.

Exactly how high do you have the heating turned up if your ambient room temperature is around 26C - that must be almost unbearable - we are not in Siberia!

Or are you saying you heat your home from the exhaust vent heat of electronics equipment - in which case the more heat generated the better - more power to you!

26C is the temperature reported in the information panel of ViX Hades - are you really saying a standard ViX install is really that bad or inaccurate?

Do you have a Duo2 and if so what temperature does it report in the ViX info panel?

Upper operating temperature is a limit not a contest - the cooler it runs the longer it lasts!

Check out Intel Microprocessors datasheets for upper temperature limits - unless you are frying food on your microchips the only thing those temperatures will achieve is to make computer chip etc. manufacturers rich by rapidly burning out microchips (in those temperatures the capacitors will go first!) and paying more money for new equipment - details please.............

Has anyone checked if their exhaust / cooling fans are actually running - actually looking at the fan to see it rotating?????

[Rob van der Does]

26 degrees is when the box is in deep. Normal temperature readouts for STB's is 40 - 75 degrees. The actual SoC will be far hotter but we depend on where the sensor is located.

[:-)]

26 degrees is when the box is in deep. Normal temperature readouts for STB's is 40 - 75 degrees. The actual SoC will be far hotter but we depend on where the sensor is located.

Take a look at the picture I just took it shows 25C on the TV screen - the box has been running all evening non stop - Rob explain the temperature in the picture - the Duo2 has been in use for hours.

You have the same Duo2 as me - so you are saying the ViX Temperature readout on the information page is totally meaningless?

So Rob where are you getting your "meaningful" temperature readings from?

If what you are saying is true then ViX massively underreports the operating temperature of the box - how massively stimulating for sales of new boxes!!! What a money spinner.

Are you saying there is more than one temperature sensor in a Duo2? How many temperature sensors are you saying there are? Beyond the one in the HDD.

So according to you that is one temperature sensor integrated into the main Intergrated Circuit / CPU and another thermo-diode/resistor sticking out of the motherboard?

I have rested my finger on top of the 44922black heat-sink directly over the CPU in the past and it is pretty cool - nowhere near 75 degrees - but Rob do you mean C or F ?

So if there is a second temperature sensor other than the one producing the 25C reading then why does ViX give only the reading that is meaningless according to you - so how does one go about accessing the meaningful true reading to which you refer???? And why does ViX according to you ignore that reading?

Lets all get to the bottom of this for once and for all - thrash the temperature issues out or keep paying for replacement boxes & repairs - due only to unchecked heat & odd / different temperature readings.

Best Regards

PS Are your heat-sinks firmly attached to your CPU's - there is no visible fixing method so I presume it is glued on with what should be thermally conductive glue - Sky HD boxes CPU Heat-sinks were glued on to the Thomson MK4 Generation Sky HD box - and that one kept falling off when the glue regularly went bad - the HDD caddy above the CPU kind of stopped it coming completely adrift but it still meant zero effective CPU cooling - even worse if a DiYer superglued it back into place the glue either acted as a thermal insulator or depending on the solvent content of the glue the glue would occasionally smoulder - the MK6 Sky HD boxes by Amstrad (god help us all) use a spring steel "Z" clip and a thermal interface pad - a lot more reliable than the thermal glue - has an unscrupulous retail dealer been breaking the glue bond between Duo2 CPU and Heat-sink?? Or is it cack handed owners recklessly installing Hard disks??

[judge]

If what you are saying is true then ViX massively underreports the operating temperature of the box - how massively stimulating for sales of new boxes!!! What a money spinner.

The level of paranoia in this thread has reached peak.
If you have a well working box, enjoy it.
If any box has a hardware failure & is still covered under warranty, use it.

[Rob van der Does]

The level of paranoia in this thread has reached peak.
If you have a well working box, enjoy it.
If any box has a hardware failure & is still covered under warranty, use it.
Exactly, I couldn't have said it better.

[Sicilian]

Think this thread has run its course, closed.


Sent from my iPhone using Tapatalk