Why Crosstalk / Spillover from other Sats while Blindscanning on SBS6?

Status
Please reply by conversation.

jsattv

SatelliteGuys Pro
Original poster
Jul 4, 2006
1,061
8
This weekend I did a number of Blindscans on SBS 6 74.0W. A few times instead of scanning for feeds on SBS6, my receiver somehow scanned in all the 195 video channels and 130 radio channels from IntelSat 5.0 97W. It also did the same thing on the approx 50 channels on Galaxy 3C 95.0W. The only way I could get around this problem (at times) was to go into Antenna Setup and switch Off LNB Power for 97.0W and 95.0W. Does anyone know why this Channel Scan or Crosstalk from other Strong Satellites occurred? Do other Satellite receivers have this problem as well, or is this a quirk of the ViewSat Receiver?
 
I occasionally get some TP from AMC 6 showing up when I scan SBS6, but they are only 2 degrees apart. I have never gotten anything from sats you are reporting.

Is the viewsat driving your motor correctly?
 
it dounds like the dish isnt moving. If properly aimed, the only "spillover" I have seen on SBS6 is the GBN Network (really strong) on AMC6
 
You will not get signals from satellites located more than a few degrees off access. Check to make sure that you have not selected multiple satellites for scanning. In order for your system to scan in these other satellites, the dish will need to be aimed reasonably close to these birds. Are you sure that the dish is not moving to these other positions? Are you using USALS or DiSEqC 1.2?
 
You will not get signals from satellites located more than a few degrees off access. Check to make sure that you have not selected multiple satellites for scanning. In order for your system to scan in these other satellites, the dish will need to be aimed reasonably close to these birds. Are you sure that the dish is not moving to these other positions? Are you using USALS or DiSEqC 1.2?

Thanks SatelliteAv, you raise a good point, I do remember a couple of times accidentally hitting the " scan multiple satellites button" I don't think I selected it, but I'll have to check for this. Hope I know how to clear it on the ViewSat!
 
Thanks SatelliteAv, you raise a good point, I do remember a couple of times accidentally hitting the " scan multiple satellites button" I don't think I selected it, but I'll have to check for this. Hope I know how to clear it on the ViewSat!

I'm not sure about the Viewsat Ultra but I played with an extreme on a motor and after about 30 minutes of it not moving the dish, or moving to where it wasn't supposed to, or whatever, we finally gave up on the Viewsat controlling a motor and put it in a back bedroom for stationary G10R use only.
 
Agree with Iceberg. My current dish is non-motorized and locked at SBS6. I get GBN strong with clear skies and occasional strong feeds from AMC6. 2 deg is one thing, 23 is another :)
 
Thanks Scottc98, Digiblur, and IceBerg, I'm beginning to think that my Fortec Dish and HH120 Stab Motor are NOT Tracking properly in the Westerly Direction. Satellites East of IntelSat 5 97.0W seem to be tracking okay but those East of 97.0W are just barely ok there.

Is there an easy way to align the a Dish (once the snow is off the roof), for a poor tracking in one direction only? That is, do I just rotate the dish itself in an East or West direction when I'm on Satellite - SBS 6 74.0W?
 
Sorry Guys I made a typo error on my previous Post. It should have read: Satellites WEST of IntelSat 5.0 97.0W are tracking okay, but those Satellites EAST of 97.0W are just barely okay. Any replies would be appreciated.
 
Did the motor ever go east or did this just start? When you tell the receiver to return the dish to "reference" or back to your true south setting, does the motor go back to 0? I am not familiar with viewsat motor setup, but my pansat has a reference position that I save as my true south.
 
Last edited:
The incorrect tracking in one direction only may be due a bent LNBF arm or that the motor/dish installation is slightly off.

Was USALS or DiSEqC 1.2 used to install the dish?
 
I am using "USALS" and the problem appears to be with the Command to move the Dish with the ViewSat. When going into "USALS" my Long and Lat are already in re the Stab Motor. (But Stab Web Site says to use 97.1W Longitude for Winnipeg, Manitoba while SatCalculator FreeHostia says it should be 97.2W, wonder if this will make a difference?) But the choices for moving the Dish are: Go to Reference, & Move, seems like you have to hit Go to Ref first, wait a while, then hit Move and press Exit then the Receiver says "Antenna is Moving Please Wait.....

Almost seems like the reason I think I had Crosstalk which I thought was from other Sats, is because the Motor still hasn't moved the Dish yet to the new Satellite chosen. As Iceberg has already posted, - the ViewSat is indeed very Quirky with this.

Think I need to look into a better Receiver and am also considering doing a complete Receiver Factory Reset and rescanning in all sats again. Any comments would be appreciated.
 
When going into "USALS" my Long and Lat are already in re the Stab Motor. (But Stab Web Site says to use 97.1W Longitude for Winnipeg, Manitoba while SatCalculator FreeHostia says it should be 97.2W, wonder if this will make a difference?)

the .1 difference will only mean the dish might be a little off. I'm at 93.5W but for the longest time my USALS say 93.0 yet its fine
 
Viewsats are not known for quality motor control, but I am not sure on the newer models if anything improved.

Is there anyway you can have someone work the receiver and you watch the dish to see what is going on? We know it is not moving properly, but maybe just watch and listen to make sure nothing is mechanically wrong when it tries to move east.

Also, I have had a couple times when my setup got out of whack and besides doing the reset on the receiver, I had to Zero the motor again. I used the manual move buttons on the motor and of course, I didn't zero it back to the exact same spot (it was nighttime), but a little adjusting of the reference point (longitude) on the receiver took care of that issue.
 
IceBerg, thanks for the reply, I can change the Longitude settings in USALS on ViewSat for the Stab Motor to 97.1W as Stab recommends, or to 97.243 as Sat Calculator FreeHostia recommends. I just wondered who was correct for Winnipeg?? But since there is only 0.1 difference in the 2 calculations, then I guess it doesn't really matter?

And SatinKzo, thanks for the suggestions. Unfortunately the Stab HH120 Motor has no Manual Buttons like the SG 2100 motor does. Also right now there is no access to my roof with about 20 inches of snow up there, and more snow scheduled for today. BUT, I can hear and see the motor move when I select a far EAST or far WEST Satellite Channel. As mentioned to IceBerg the USALS settings on the ViewSat does allow me to change or key in the Longitude and Latitude Settings but I'm not sure what I would set them to other than the published 97.1W or 97.2W for my location? Or do I play with this trying several different settings?
 
I guess I don't know enough about the Viewsat USAL setup, but the two receivers I have used USALS on (Pansat 3500 and fortec Merc II) I put in my Lat and long and like I said, I had to tweak them a bit after zeroing my motor once. Just a slight .4 adjustment on long, but it helped nudge the dish enough to get a stronger signal.

I got your equip list confused with 'bergs, I thought you had the SG2100, but it sounds like the motor is fucntional, I would have to guess maybe viewsat still has motor control issues that many have reported
 
Thanks SatinKzo, I'm not sure what you mean by Zeroing the Motor? Do you mean physically going up to the Motor & Dish when its on my South Satellite (97.0W) and making sure the degrees settings on the motor with reference to the Stab Motor Pointer are at Zero?
 
The Viewsat is most likely the cause of the problem of the incorrect satellite movement during the scans. Make sure that you are parked on the satellite that you want to scan before staring the process and only scan one satellite and not multiple satellites.

The Viewsat incorrect motor control is not just alleged...... it is reality! We have tested the Platinum and the Extreme and both could only reliably control USALS on up to three satellites before they began erratic motor calculations. We found that if USALS and DiSEqC 1.2 commands were used (USALS for set-up and reference and DiSEqC 1.2 for all additional satellite motor control) that the motor could be more reliably controlled.

An incorrect Longitude and Latitude entry will cause calculation errors. Use a GPS or an application mapping to determine your exact location.
 
Thanks for the info. Well I have about 8 Sats Scanned in, but as mentioned I've had the most problems with SBS6 74.0W. I cannot get Ohio News Network (ONN)any more. But haven't really checked out the other Sats that much except for IntelSat 5.0 97.0W and it is working okay.

What do you mean by an Application Mapping to determine my exact location? Also when giving the ViewSat - USALS Commands, do you press: "Go To Reference", then Press "OK Move", or do you just Press "OK Move"? This seems to make a big difference in the setup, and I sure wish someone was expert or could supply the correct information on this?
 
If he had the longitude off in the USALS setup, wouldn't that throw all sats off and not just east or west?

I have an HH120 also, it is a great motor, but moves slowly. Perhaps the scan started before the motor actually got to the right location.
 
Status
Please reply by conversation.

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)

Top