TwinhanDTV Locks up - Please help

[jclausen]

I have a Fortec 31" FS80P dish with a Digipower SG2100 motor and a KUL1 LNB. My receiver is a Twinhan Starbox USB VP7021.

This was all purchased as a kit.

When I tried the software that came with the kit, I could not find where to put in Long. and Lat.. I downloaded the latest software from Twinhan.

In the software when I select "Channel Scan" and then "Satellite Setup", the little blue light on my VP7021 blinks out for a split second and then the software locks up.

If I unplug the power to the VP7021, the software will respond again.

The dish, motor, and lnb all work fine, I have tested them with a stand alone receiver.

If I start the software with the RG6 cable unplugged, It does not lock up.

I have already tried to shorten my cable and that did not work.

Any help would be greatly appreciated.

Thanks,

John

[jclausen]

Ok, I figured out what the locking up problem was.
The power supply that was supplied with the receiver was too weak. I installed a slightly bigger one and everything is moving ok.

I could not get a lock on any transponders so, I hooked up my Coolsat to the lnb and left the Twinhan on the motor.

The dish was slightly off center so I corrected it and USALS was working great.

Still no signals.

I then used the Coolsat to blind scan the satellite and paid attention to the transponder frequency and SR, it was off.

A trransponder that was supposed to be at 11720 with a SR of 20000 was showing up at 10719 with a SR of 20001.

I hooked everything back up to the Twinhan and changed all my transponders. I can not scan transponders and get channels.

Whew.....

Anyway, I guess my LNB is bad for it to be so far off.

John

[wejones]

Originally Posted by jclausen

Ok, I figured out what the locking up problem was.
The power supply that was supplied with the receiver was too weak. I installed a slightly bigger one and everything is moving ok.

I could not get a lock on any transponders so, I hooked up my Coolsat to the lnb and left the Twinhan on the motor.

The dish was slightly off center so I corrected it and USALS was working great.

Still no signals.

I then used the Coolsat to blind scan the satellite and paid attention to the transponder frequency and SR, it was off.

A trransponder that was supposed to be at 11720 with a SR of 20000 was showing up at 10719 with a SR of 20001.

I hooked everything back up to the Twinhan and changed all my transponders. I can not scan transponders and get channels.

Whew.....

Anyway, I guess my LNB is bad for it to be so far off.

John

Glad you figured out the power supply thing. I was thinking about that, but not sure enough to suggest it.

Re the LNB being "bad", first of all, the LNB doesn't have any effect on the SR value. And a difference of 1 in 20,000 SR won't have any effect on your being able to tune a transponder. Most receivers can still tune if off by MUCH more, although my Twinhan is quite tight in this respect. My Twinhan PCI card needs to be off by at least 8 before it can't tune a 20,000 SR signal. The frequency, however, is another matter. Although I'm surprised that you could tune 11719, but not 11720, my Twinhan generally needs to be within 2 or 3 MHz or it will start to have trouble tuning. I ran into a similar situation with the LNBF I got for my 90CM dish, I was having trouble tuning transponders, but I hooked up the the system to another PCI receiver which has a control APP that will tell how far off frequency you are, so I looked at several transponders, and found that my LNBF was off by 2 MHz, ie mine would lock an 11720 transponder at 11718. On most transponders, I could still lock, when 2 MHz off, but many would not lock. So what I did, was change the LO freq UP 2 MHz, ie I changed it from 10750 to 10752. Doing this allowed me to enter the correct frequencies when manually entering transponder data.
If I were you, I'd experiment a bit to verify just how far off your LNBF is, and then make the appropriate change to your LO frequency.

[jclausen]

The difference is not between 11719 and 11720, it is 10719.

The transponder is at 11720 and I have to look for it at 10719.

I will try what you said and use the lof to correct...sounds a lot better than editing ini files!!

Thanks,

John

[wejones]

Originally Posted by jclausen

The difference is not between 11719 and 11720, it is 10719.

The transponder is at 11720 and I have to look for it at 10719.

I will try what you said and use the lof to correct...sounds a lot better than editing ini files!!

Thanks,

John

Sorry, re the 10719. I mis-read that. Wow, that is off a lot. I've never seen an LNB off that much. I'd have to suspect that you have your LO freq off for that sat, like if you were using a 9750 LO freq (universal) when your LNBF is really 10750 (standard). Ie if you did a blind search and used a 9750 LO freq, then 11720 would show up as being 10720. Just a guess. Your LNBF should be set on Standard with a LO freq of 10750.