Dish TV T2200 error code "P200", "set top box unable to receive signal?

Forums › Freeview (DVB-T/DVB-S) › Dish TV T2200 error code "P200", "set top box unable to receive signal?

phoenixx

57 posts

Master Geek

#208979 7-Mar-2017 15:14

Hi,

As above this happened when I turned the unit on giving me P200 on the unit and "Your set top box is unable to receive a signal. Please check your cable/UHF aerial".

I've checked all cables etc, turned unit and tv on/off several times, unplugged unit etc and I'm still getting this same error. Can anyone help please, Josh are you there?

Have googled and checked manual and triple checked all plugs, aerial, power points etc.

Thank you

Morgenmuffel

631 posts

Ultimate Geek

Lifetime subscriber

#1732709 7-Mar-2017 19:23

Ok, the Two obvious questions,

1) if you take the dishtv out of the equation your tv can actually receive a signal when plugged directly into the aerial?

2) The Unit DishTV has been working fine up until this point?

'We love to buy books because we believe we’re buying the time to read them.' WARREN ZEVON

phoenixx

57 posts

Master Geek

#1732794 7-Mar-2017 23:10

Yes TV receiving signal ok and T2200 been working fine.

joshhill96

1512 posts

Uber Geek

ID Verified

Trusted

#1732900 8-Mar-2017 10:43

phoenixx:

Yes TV receiving signal ok and T2200 been working fine.

Are you able to swap the cable from your TV into your T2200? The aerial cable that is and will see if there is a problem with the cable or something else.

Formerly worked at iStore NZ (Rest in Peace), Sky Network Television, Freeview, Apple, Spark New Zealand Trading Limited, DISH TV Technologies.

Travel Geek: Brazil, Chile, New Caledonia, United States, Fiji, Vanuatu, Australia, Cook Islands

phoenixx

57 posts

Master Geek

#1732903 8-Mar-2017 10:48

Have called Dish TV this morning, they've talked me through a factory reset, all working now, thanks :)

phoenixx

57 posts

Master Geek

#1748964 27-Mar-2017 20:41

So now I've got a new issue. During playback, if I pause the recording for more than a few seconds, when I unpause it I get a notification, "playback aborted due to invalid/corrupt content". So I have to play it again from the beginning and ff to where I was, rinse and repeat if I pause playback again. This is happening on playback on different recordings.

ALSO when I press play again and am asked "resume playback, yes/no" and I click yes, it plays from the beginning of the recording and NOT from where it is supposed to.

Any help please?

Jase2985

13457 posts

Uber Geek

ID Verified

Lifetime subscriber

#1748987 27-Mar-2017 20:58

there is a new firmware out as of today, try installing that and see how you go?

phoenixx

57 posts

Master Geek

#1749004 27-Mar-2017 21:14

Thanks Jase but the box updated itself this morning and it's still happening.

Also when I stop the recording it carries on playing (sound only, no picture) even though the on screen menu shows it as stopped. It's now very difficult to watch anything!

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

Jase2985

13457 posts

Uber Geek

ID Verified

Lifetime subscriber

#1749007 27-Mar-2017 21:17

sounds like you have a dud box

joshhill96

1512 posts

Uber Geek

ID Verified

Trusted

#1749278 28-Mar-2017 10:59

Hi Guys,

I'm sending issues reported after the latest update to our team to look into, feel free to provide more information via private message

Cheers

Formerly worked at iStore NZ (Rest in Peace), Sky Network Television, Freeview, Apple, Spark New Zealand Trading Limited, DISH TV Technologies.

Travel Geek: Brazil, Chile, New Caledonia, United States, Fiji, Vanuatu, Australia, Cook Islands

phoenixx

57 posts

Master Geek

#1749424 28-Mar-2017 14:22

Hi Josh,

Thanks for your reply. If you read my post number 1748964, 27-Mar-2017 20:41, you will see that this problem started for me last week and is still happening after the update so I would assume that it is nothing to do with the update?
Thanks :)