View Full Version : Check switch error on 61.5 on VIP622
glee989302
05-14-06, 09:56 AM
Last night I recieved an error message that I might have a bad switch and all I get is a check switch error that I can't get out of. When I run the test I get 3 sats on input 2 110, 119, and 61.5 but I get a just 110, and 119 on input 1 (with an X where 61.6 would be).
Suggestions anyone?
I have one wire coming into a little splitter thing that goes to the 2 inputs on the VIP622.
I then disconnected the switch and ran the one wire into input 1 and I get 3 sats Then I ran the same one wire to input 2 and I get 3 sats on that input.
Bad 622? bad switch? bad LNB?
HELP!!!
marcuscthomas
05-14-06, 01:06 PM
The same thing happened to me yesterday. I called technical support and they told me my switch was probably broken and scheduled an appointment for tomorrow to repair it. But, I hooked up my old 522 today and it works perfectly. Check switch and everything works. All channels ok (obviously SD only). Just called technical support back and they said there might be a difference in how the 622 works with the splitter and that the technician would have to look at it. He insists that the 622 does work fine on a splitter. Anyone with any experience like this?
marcuscthomas
05-14-06, 01:17 PM
Well,
I hooked the 622 back up to the switch after having the 522 hooked up and working and.......everything works like a charm???
I don't really get it. I got the exact same error complete with the same x in the same slot. Hooking the 522 back up seems to have fixed the switch.
By-the-way, this started for me when I ran a check switch as I was troubleshooting a video drop out problem. Did you run the check switch first or get the error?
LtMunst
05-14-06, 08:01 PM
Well,
I hooked the 622 back up to the switch after having the 522 hooked up and working and.......everything works like a charm???
I don't really get it. I got the exact same error complete with the same x in the same slot. Hooking the 522 back up seems to have fixed the switch.
By-the-way, this started for me when I ran a check switch as I was troubleshooting a video drop out problem. Did you run the check switch first or get the error?
This happened to me today as well. I also re-tested the switch with my old 625 and everything was fine. I am still unable to get the 622 to work, though.
Are you saying that your 622 now can do a successful switch check?
LtMunst
05-14-06, 08:10 PM
The same thing happened to me yesterday. I called technical support and they told me my switch was probably broken and scheduled an appointment for tomorrow to repair it...... that the technician would have to look at it. He insists that the 622 does work fine on a splitter. Anyone with any experience like this?
Our switches are not broken. Bet they start getting a bunch of calls for this. Something must have changed with the 61.5 signal that the 622's software does not like.
marcuscthomas
05-15-06, 07:24 AM
This happened to me today as well. I also re-tested the switch with my old 625 and everything was fine. I am still unable to get the 622 to work, though.
Are you saying that your 622 now can do a successful switch check?
Exactly, my 622 came back up and has worked perfectly for the last 18 hours or so.
I suspect that the 622 does not work well with my DISH500 and signal splitter. What is your setup? Also, how did this start for you. As I said earlier, my problems started when I ran a "check switch" while troubleshooting another issue. I have a tech coming today, but everything is working, so I suspect he will do nothing. I am requesting a Dish1000 and two distinct cable runs down to the receiver.
Also, an odd thing that I noticed, the signal strength on my 622 for all satellites is about 20% weaker than that of the 522. This might have more to do with the scales that they use, or I might be looking at different transponders and spotbeams. I should hook the 522 back up and carefully compare, but I am pretty much refraining from playing with it while it is working.
While the splitter may work, I am suggesting wherever possible that 2 distinct cable runs from the switch should be used for the dual tuner receivers. It just seems like that would make for a more reliable installation.
LtMunst
05-15-06, 08:08 AM
Exactly, my 622 came back up and has worked perfectly for the last 18 hours or so.
I suspect that the 622 does not work well with my DISH500 and signal splitter. What is your setup? Also, how did this start for you. As I said earlier, my problems started when I ran a "check switch" while troubleshooting another issue.
I have a DPP Twin with 110/119 and 61.5. There is a single line to my 942 and to my 622 (split at the receiver with the separators). This has never been a problem for my 622 until yesterday. I came across it when checking my sysinfo screen. The 61.5 location showed x on tuner1. From that point on I have been stuck in bad checkswitch hell.
Something changed this weekend on 61.5 that is causing it to not play nice with the 622 and DPP Twin. Hopefully this is a temporary glitch.
marcuscthomas
05-15-06, 08:58 AM
I have a DPP Twin with 110/119 and 61.5. There is a single line to my 942 and to my 622 (split at the receiver with the separators). This has never been a problem for my 622 until yesterday. I came across it when checking my sysinfo screen. The 61.5 location showed x on tuner1. From that point on I have been stuck in bad checkswitch hell.
Something changed this weekend on 61.5 that is causing it to not play nice with the 622 and DPP Twin. Hopefully this is a temporary glitch.
I agree that something took place this weekend. The trouble for me started when I ran the "check switch."
After I hooked up the 522 and got it working, I reconnected the 622. But, before reconnecting the 622, I did do a 30 second power line reboot. This may have helped, I don't know.
You asked earlier, If the 622 would successfully run a "check switch." In response, I can only say that when I first rebooted it from the power cord reboot, it came up into the 502 error screen and ran a "check switch" to get to the "acquiring signal" stage. This initial "check switch" reported a good signal on all three satellites. I have not dared to run another one since then.
I too have the DPP Twin looking at the two satellites and another separate dish aimed at 61.5. These signals come down on one coaxial and hit a splitter behind my reciever.
boylehome
05-15-06, 10:05 AM
Our switches are not broken. Bet they start getting a bunch of calls for this. Something must have changed with the 61.5 signal that the 622's software does not like.BINGO. Same problem with my DPP44. Additional information here: http://www.dbstalk.com/showthread.php?p=581998&posted=1#post581998
I checked transponders first on 622 then on 921. They both are seen on the same satellite with the same switch. There seems to be a lock issue with the 622 on transponders 16 & 20.
Transponer #-662/921
01-83/91
02-85/87
03-90/92
04-0/0
05-88/88
06-90/102
07-90/91
08-82/93
09-95/97
10-78/88
11-92/95
12-100/113
13-93/106
14-93/105
15-90/91
16-*84/91
17-91/95
18-78/88
19-93/96
20-*83/95
21-89/91
22-78/90
23-0/0
24-0/0
25-85/95
26-0/0
27-84/96
28-0/0
29-82/93
30-77/92
31-84/95
32-81/91
* Name Not Acquired & Not Locked on Model 622
dfergie
05-15-06, 10:40 AM
Check this thread (http://www.satelliteguys.us/showthread.php?t=65875&page=2)for his solution (for now)
LtMunst
05-15-06, 11:27 AM
I checked transponders first on 622 then on 921. They both are seen on the same satellite with the same switch. There seems to be a lock issue with the 622 on transponders 16 & 20.
Transponer #-662/921
* Name Not Acquired & Not Locked on Model 622
Nice catch!
marcuscthomas
05-15-06, 01:38 PM
A local technician showed up at my house today. Since my 622 was working, he left without looking at it. I expected that. I told him that the same problem involving the 61.5 satellite has been seen by several people and reported on the web and speculated that there might be a problem in the interaction between 61.5 and the 622. He said (I am not lying now), "we always get problems when the weather is stormy."
I guess we will have to see this a few more dozen times and see how E* responds.
I've never had any trouble with using my separator with my 921. I wonder if there are some issues with having the cables reversed. IIRC, I have out1 of the separator connected to sat1 of the receiver.
My 508 has been having check switch errors, but only when I run a check switch. Another solution to the problem might be to stop running check switches.
LtMunst
05-15-06, 01:57 PM
Another solution to the problem might be to stop running check switches.
Wish it were that easy. When the receiver detects certain switch errors, you are forced to run a checkswitch. In my case, just pulling up the sysinfo screen triggered the whole switch error mess.
Allin4greeN
05-15-06, 07:37 PM
My parents had a 211 and 622 installed this weekend (upgrades from 811 and 942). The techs spent several hours troubleshooting this problem with different LNBF's, cable runs, etc.
Their set-up includes DPP Twin on 110, 119 (D500) and 61.5 (D300), with a single run to Diplexer (backfeeding) and Separator on the 622. Techs had trouble locking onto 61.5 on one and then both STB's. They finally got it up and running but, the signal was very intermittant from 61.5
I haven't had any problems with my set-up (consistent signal strength has been in the mid 90's) but, I'm located 60 miles southeast of their location, am not using a Diplexer, and have a D500 on 61.5
LtMunst
05-16-06, 06:51 AM
Looks like the problem has cleared up. :) My unit checkswitched fine last night and is now back in business.
vBulletin® v3.7.6, Copyright ©2000-2012, Jelsoft Enterprises Ltd.