July 6th, 2010

...now browsing by day

 

A software problem in the ViP722 receiver that Dish Network doesn’t want to fix

Tuesday, July 6th, 2010

Subtitle: A way to get $6 off your Dish bill every month

Erin and I have been having a hell of a time with Dish Network lately.  A couple of months ago, our Dish receiver started flaking out.  All sorts of shows would fail to record, old shows would start recording when only new ones should, shows would get caught in an endless loop as though skipping like a record.  We got the receiver replaced and found that the skipping problem improved, turns out that the hard-drive was going bad.  Unfortunately, some of the shows were still failing to record.

Whenever a show failed to record, it showed up in the schedule history as failed due to signal loss.  However, we found that while some shows would fail to record to tv2, we would simultaneously be able to watch tv1.  This got our interest piqued.  The technician came back to check the signal strength and replace various components several times.  We even had the receiver replaced again.  Over the next month or so, we added a cable directly from the satellite to the receiver through the back door…then a cable directly from the receiver to tv2 in an attempt to bypass any possible wiring problems in the house or electronic components.

Now, over time Erin and I had come to the conclusion that there was a specific sequence of events that could force the receiver to not record a show.  And based on this sequence, we’d come to the conclusion that it was most likely a software problem.  These are the arguments that Dish Network folks gave for the problem:

1) There are signal problems, need to replace something in the system – They replaced the LMBs, diplexers, mixers, etc…and eventually bypassed everything with cables through the house.  Not the problem

Me – It seems like a software issue

2) This must be a problem with the receiver – There was a problem with the original receiver which was fixed by replacing it.  The problem with the failed recordings was exhibited on replacement receivers 2 and 3.  The probability of this same exact problem being hardware and being present in 3 receivers is probably astronomical.  Keep in mind that both Dish Network customer service and the local satellite folks claimed that this problem is really weird and they haven’t heard of anything like it that isn’t fixed with component or receiver replacement.  (Yes, grounding can be a problem, but we fixed that last year when we went through Dish problems)

Me – I think it’s software…maybe a combination software/hardware issue

3) The power line driving the receiver must be dirty, or somehow non-standard – House power isn’t always pure and correct.  The only way I had to measure the power was with my multimeter.  Voltage and frequency were dead on.  I don’t know if there were some other strange harmonics or other noise, but given that we have a lot of other electronic equipment hooked into the electric grid that hasn’t fried, I don’t believe our power is that bad.  Additionally, we had our original receiver for about a year before it flaked out.  The 2 replacement receivers started with the problem immediately.

Me – I don’t see how it could be anything but software

4) It could be some weird signal reflection deal from the TV through the HDMI cable – We use component video.  Not the problem.

Ok, we’ve gone through a lot of troubleshooting here and have no way forward with Dish.  When we talk to customer service (level 1, lvl 1 supervisor, advanced tech support, account specialist, etc), they say that the only things they can do are to replace the receiver or request a tech visit.  I’ve been dealing with the local satellite company (Valley Satellite in Decatur AL) directly, they have been very competent and have worked well with us.  Greg, the owner, knows the VP of tech support at EchoStar (Dan) and says he’ll give him a call.  EchoStar develops receivers for Dish.  Dan gives me a call and tells me they are about to make a software update that probably fixes the problem and to hold tight…it should start rolling out that week.  That was a month ago.  The software version number (L627RJ2B-N) hasn’t changed since we first noticed this problem.  (note that I think L627 is the important part of the software version number).  So either Dan was blowing smoke up my ass, or he didn’t know what he was talking about.  Greg tells me that Valley Satellite will be supporting DirecTV soon…hmm…

The one thing that Dish has maintained is that no-one else is experiencing the problem that we have.  Here is the clincher, my in-laws have a Dish 722 receiver setup similar to ours.  We visited over the 4th of July, tested the system, and were able to recreate the same exact issue.  I am convinced that this problem is a software issue.  The problem started very abruptly a couple months ago and has been very repeatable on multiple systems.

So, if you want to get a discount on your Dish Network bill, or if you want to see if you have the same problem, try out the sequence below and see what happens.  If you get it to happen, you should be able to argue your way out of $6 or more from your monthly bill each month until it is fixed.  That is the monthly cost of the DVR service.  If you decide to call Dish Network, please reference a trouble ticket entered on July 4th by Jessica (Operator ID: LWZ) from Advanced Tech Support.  Supposedly if enough people call about the same problem, they might look into fixing it.

If you’ve made it this far, please post a comment if you are having the same problem.

Sequence for failed recording

1) We usually see the problem first thing in the morning.  The receiver usually does a software update check at 3 AM and resets, so you may want to do this before any recordings start…or reset the receiver before you begin if it doesn’t work otherwise.

2) Record 10+ minutes of a show.  We usually just use a half-hour show previously recorded.

3) Set up two 30 minute recordings back-to-back to TV 2.  The recordings don’t have to be on the same channel, just set to record on TV 2.  (e.g. 7:00 Curious George, 7:30 Sid the Science Kid)

4) Prior to the start of the first show, start watching the recorded show on TV 2 so that you are watching it through the start of the first recording. (e.g. start watching a 30 minute show at 6:50)

5) After the first recording has started, turn TV2 off. (including the dish transmission to TV 2.  Don’t just turn the TV off) (e.g. stop watching TV2 at 7:05)

6) Turn TV1 on to watch the previously recorded show prior to the ending of the first recording such that it will finish after recording 2 has begun. (i.e. start watching at 7:25)

If you follow the steps above, when TV 2 is supposed to be recording the second show, you can look in the DVR->Schedule menu, and you will see the recording is stopped for ‘Service Shutoff’.  When the recording “finishes” and you look back at the schedule, it will show that the recording was skipped due to signal loss.

After this point, nothing will record or play on TV 2 unless you go to the TV 2 DVR menu and start an old recording.  Once you start, then stop a recording, live TV will return and programs will record.  If you turn TV 2 back on and just leave it, nothing will be on the screen.  Eventually TV 1 claims to lose signal and it goes through the process of recapturing satellite signal and downloading guide data.  If you do fix TV 2 via the old recording, it will work fine for the rest of the day.

Please help me out here.  I just want to get the problem fixed.  My wife and I have been on the phone numerous times, hung up on, ignored, blown off, etc by Dish Network.  Their customer service representatives have scripts that do not cover any problem out of the ordinary.  I’m a freaking aerospace engineer who knows how to do troubleshooting and problem reporting.  If Dish would give me the system definition documents, schematics and software, I’d find the problem and fix it for them.  Unfortunately things do not work that way.  I’ve sent some of the tech support folks emails with the details, my wife and I have described the problem to a lot of tech support people many times.  Can anyone help?