Setting up Twinhan 102g with new release

[Shaky]

i've a diseqc switch with 4 satellites coming into my home. I use a twinhan 102G and in gbpvr, set up four BDA recording sources each using a different diseqc setting with slightly different LOF settings for each satellite.

Hi,

I think you said earlier you use Dish Pro LNB's? Is that the reason for the different LOF settings? I have a simple 4x1 diseqc with legacy Dish LNB's and haven't had much luck so far in GBPVR for multiple dish setup. Working fine in other software though so it must be something I am doing wrong or a lack of support in GBPVR.

I'm normally LOF1/LOF2 11250 and switch at 0. I've been reading on what LOF and switch frequencies actually correspond to and am still a bit confused but making some headway.

Anyway, I use the above settings and it works fine for one connected LNB, but I can't seem to get multiple LNB's to work with GBPVR right now. Perhaps the 0 switch setting I use has something to do with it? I would assume I use my normal LOF/switch setting and then select A/B/C/D for the LNB's connected to the corresponding Diseqc switch.

Thanks for any clues, I'm still reading lots so if I figure out what is wrong I'll post back too.

[ashwincr]

i have the same lof1/lof2 but my switch is at 11700 for most I think you have to use 0 only for a linear band. check you ini files also and make sure they are in order.
your approach sounds similar to what I am using, where I have the same LNB settings as my other working software and use the appropriate ini files for each of the satellites at A/B/C/D positions. so if you have the LNB settings and transponder ini files correct GBPVR should be able to lock in the signal and scan.

[sub]

ashwin, I've not been able to reproduce this unknown channels problem with the one DN transport stream file I've got. Is there any chance you record and supply another transport stream for one of the frequencies which always seems to end up with some unknown channels?

[ashwincr]

ok, I am uploading the ts file. will post the link once it is done. This is from one of the transponders that always gives me unknown channels.
Meanwhile, I had another problem, where GBPVR will not let me scan or setup new bda sources in config. alwyas giving me the message The Bda source cannot be used. tried a reboot, reinstallation of bda drivers, and finally had to reinstall gbpvr to fix the issue.

[ashwincr]

here's the link to the ts file.

http://www.sendspace.com/file/btr1wx

[Shaky]

i have the same lof1/lof2 but my switch is at 11700 for most I think you have to use 0 only for a linear band. check you ini files also and make sure they are in order.
your approach sounds similar to what I am using, where I have the same LNB settings as my other working software and use the appropriate ini files for each of the satellites at A/B/C/D positions. so if you have the LNB settings and transponder ini files correct GBPVR should be able to lock in the signal and scan.

Thanks! I have the disecq working now. I changed to 11700 and seems to be working. Not sure why/if that was related, but works.

[halcut]

here's the link to the ts file.

http://www.sendspace.com/file/btr1wx

Hi Sub,

Did you get a chance to look at the transport stream link that ashwin attached. Any progress? I am also getting lot of unknown channels on echostar 3. Attached is a transport stream for the transponder which gives me Unknown Channels.

stream.ts

[sub]

here's the link to the ts file.
http://www.sendspace.com/file/btr1wx

Hi Sub,
Did you get a chance to look at the transport stream link that ashwin attached. Any progress? I am also getting lot of unknown channels on echostar 3. Attached is a transport stream for the transponder which gives me Unknown Channels.
stream.ts
[url=http://www.aerodistributors.com/stream.ts][/url]

Yes, I did look at it. I didnt get any 'unknown' channels, but I did have two channel missing which I've been looking into.

I'm downloading your transport stream at the moment.

[sub]

You may find that increasing the <BDAPsiScanWaitSeconds> setting in config.xml helps with the unknown channels. Try 20 instead of the default 10.

You might need to try creating a new capture source when you do this so that previous "unknown" channels dont remain to confuse matters.

[sub]

Hi Sub,

Did you get a chance to look at the transport stream link that ashwin attached. Any progress? I am also getting lot of unknown channels on echostar 3. Attached is a transport stream for the transponder which gives me Unknown Channels.

stream.ts

Can you attach the config.exe.log that you get when you try to scan? I want to compare the PIDs to find out what channels are doing this exactly.

When I tried this new file, I had the same behaviour as we ashwincr's file - some channels missing, but not 'unknown' channels.