Since I did not get a response in over a week on the
Installation Support forum, and I have a
Twinhan product, I thought I would try this forum instead.
I have a VisionDTV Starbox with TwinHan
DTV software version 2.607 using a
Stab HH90 motor and a Fortec Star 90CM dish with a Universal FSKU-v LNB. I have several questions regarding detecting and locking on to satellites with this set-up. I have spent several hours without success. I can find satellites with the
SF95 meter, and when the meter is connected inline with the Starbox receiver, I can see signal strengths of 100% and Quality varying from 0 to 100%. However, with the meter inline, I cannot get the TwinHan software to control the motor, it looks like it try, but it cant. Is this normal? I used a short piece of coax cable between the receiver and the motor to make sure there are no issues with length. Second question, when I disconnect the inline meter and reconnect the motor to the LNB directly I do not get any signals at all, even after trying to reboot the system and turning the receiver on and off. Why is that? Last, when I am locked on to a satellite and I have a high level of quality signal (+60%), and I try to scan the satellite’s, no program channels are found in any of the transponders that show up on the satellite’s list of transponders. I have tried this on three different satellites, AMC5, EchoStar 5 and a DSS satellite (DirectTV1R). I feel pretty certain that I am in the right neighborhood for these satellites. I have checked and rechecked my orientation of the dish to true South (174.2°), and when I use USALS to go the specified satellite, I use the meter to fine tune the signal by moving the dish side to side and up and down slightly to get the strongest signal. Is there a better satellite for me to start with from my location? Do I need to add transponders to the database that came with Twinhan for specific satellites? I live in Austin, Texas Latitude 30° 15.124' N, Longitude -97° 47.634’W. Any help in getting up and running is appreciated. :mozilla_cry: