DISH 722k, 3rd unit, connected to Samsung LN32A550 via HDMI (second cable).
HDMI works fine all day with TV turned on and off multiple times.
However, immediately after the DISH program download, the DISH receiver malfunctions.
The receiver yellow 'mode' light comes on and no subsequent programs are recorded.
When the TV is turned on, at first there is no program info. After about 30 seconds the program info is recognized an the DISH and TV work normally until the next program download.
About 1/3rd of the time, when the TV is first turned on in the morning, the DISH also has to reacquire the satellites.
DISH phone tech support sent a replacement 722k No change.
When I asked them to again address the problem, they sent a technician out. He checked all the cables, installed new DISH antenna pickups, and a replacement 722k (new, not refurbished). No change. The tech has given up.
Called Samsung tech support. They gave up.
So, back to the basics. I disconnected all connections to the 722K except the satellite feed. 722k did downloads correctly.
I tried connecting the LCD and 722k by composite RCA (not component). Downloads worked and system started correctly.
I tried a new HDMI cable, and in all three Samsung HDMI jacks. 722k failed after TV turned on post-downloads.
So, apparently there is a handshake problem between the 722k and Samsung HDMI that affects the 722K 'wakeup' after program downloads. After the 722k is 'kickstarted' post downloads, the HDMI video and audio are first rate.
Has anyone else had this problem? It appears I can bypass the problem by using component video, but, I'd really like to connect the TV and 722K by HDMI if at all possible.
I find it troubling that none of the contacted tech support folks suggested that the HDMI could be the problem the DISH failing to work after downloads. DISH telephone support (level II) never suggested testing the units without the HDMI. Nor did the onsite technician. All they could suggest is continuing to replace the 722ks, and gave up when that did not solve the problem. The answer from all forms of DISH support was that they 'never' saw such an issue before.
HDMI works fine all day with TV turned on and off multiple times.
However, immediately after the DISH program download, the DISH receiver malfunctions.
The receiver yellow 'mode' light comes on and no subsequent programs are recorded.
When the TV is turned on, at first there is no program info. After about 30 seconds the program info is recognized an the DISH and TV work normally until the next program download.
About 1/3rd of the time, when the TV is first turned on in the morning, the DISH also has to reacquire the satellites.
DISH phone tech support sent a replacement 722k No change.
When I asked them to again address the problem, they sent a technician out. He checked all the cables, installed new DISH antenna pickups, and a replacement 722k (new, not refurbished). No change. The tech has given up.
Called Samsung tech support. They gave up.
So, back to the basics. I disconnected all connections to the 722K except the satellite feed. 722k did downloads correctly.
I tried connecting the LCD and 722k by composite RCA (not component). Downloads worked and system started correctly.
I tried a new HDMI cable, and in all three Samsung HDMI jacks. 722k failed after TV turned on post-downloads.
So, apparently there is a handshake problem between the 722k and Samsung HDMI that affects the 722K 'wakeup' after program downloads. After the 722k is 'kickstarted' post downloads, the HDMI video and audio are first rate.
Has anyone else had this problem? It appears I can bypass the problem by using component video, but, I'd really like to connect the TV and 722K by HDMI if at all possible.
I find it troubling that none of the contacted tech support folks suggested that the HDMI could be the problem the DISH failing to work after downloads. DISH telephone support (level II) never suggested testing the units without the HDMI. Nor did the onsite technician. All they could suggest is continuing to replace the 722ks, and gave up when that did not solve the problem. The answer from all forms of DISH support was that they 'never' saw such an issue before.