system info values for VIP612

[piranesi]

I'm now on my third 612. The first two had constant rebooting problems. The third was installed yesterday and already randomly rebooted once today. I'd like to try and figure out if these are all bad receivers or if there is a problem with wiring, the dish itself, etc.

But, I'm pretty new to this and I haven't been able to find a simple rundown of what the system info values should be for a new receiver. I know they were all really high on the one taken out. Here's what I have for the new one right now.

Value 0:0
Value 1: 0
Value 2: 0
Value 3: 9
Value 4: 9
Value 5: 0
Value 6: 0
Value 7: -2
Value 8: 1
Value 9: 0

I'm pretty sure 0-2, and 5-7 are what they are supposed to be. But I'm not sure about 3, 4, or 8. Do these actually mean anything that a newbie like me can understand and relate to tech. support if I have to?

Is there a list somewhere of what each of these means?

 

[Smith P.]

I recall same question and someone posted what CSR told him about the values ...

 

[aklarvanto]

Vip612 is my first HD receiver and yes, mine too crashes almost daily. I also had problem with cooling fan and ended up replacing it with generic computer fan. It fitted perfectly and box is cooler now and no hummmmmmmmming sound anymore. I think I will not purchase another 612 ever again. I should had read this forum before I purchased mine year ago.

 

[piranesi]

A quick followup.

I contacted a chat CSR to ask about this and was told that the rebooting issue was due to a "software issue". This is the first time I've hear of this and I'm wondering if it was B.S. Here is what she wrote specifically:

"I apologize for any inconvenience, this is a software issue we are aware of, and we are working on correcting. It is very likely that if we replace the unit once more, the new unit will have the same issue."

and when I pressed her for more information about it:

"Okay. Is there anything else you can tell me about the software problem? Is it a new issue?"

(24DrDpx) Alma G. RYS: "No it is not, we are still working on the issue, and it is still listed as a known issue, when it started I could not remember."

I let it go at that. has anyone heard of a known software issue related to reboots?