Need Help with DVB-S, Card ADS Tech

[Pepse]

Uh, do I copy & paste or?????

Sorry, but I am pretty green with FTA, and hopefully you can keep helping me. I am going to Ebay and get a Diseqc switch and a couple splitters so I can try some C-Band sats. Maybe they will be a little easier to get than the KU sats.

Later. Pepse.

 

[gillham]

Uh, do I copy & paste or?????

Paste the following into a file called "Galaxy19":
# Galaxy 19 @ 97W
# freq pol sr fec

S 11789000 V 28125000 AUTO
S 11836000 V 20770000 AUTO
S 11867000 V 22000000 AUTO
S 11874000 H 22000000 AUTO
S 11898000 V 22000000 AUTO
S 11936000 H 20000000 AUTO
S 11966000 H 22000000 AUTO
S 11991000 V 22000000 AUTO
S 11999000 H 20000000 AUTO
S 12053000 V 22000000 AUTO
S 12084000 V 22000000 AUTO
S 12090000 H 20000000 AUTO
S 12115000 V 22425000 AUTO
S 12146000 V 22000000 AUTO
S 12152000 H 20000000 AUTO
S 12177000 V 23000000 AUTO

Now use the scan command, but with the new file, presumably in your home directory:

$ scan -o zap -l 10750 Galaxy19

As long as your dish is pointed to 97°W, this should find something. After the command completes the scan it should dump a list of services on the screen. That will verify your setup is working.

 

[Pepse]

Well, that didn't work. I created a File called Galaxy 19 and with the use of Kate I pasted your command into the File. Here is the answer:

scan -o zap -l 10750 Galaxy19
scanning Galaxy19
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
ERROR: cannot open 'Galaxy19': 2 No such file or directory
ERROR: initial tuning failed
dumping lists (0 services)
Done.


Later. Pepse.

 

[gillham]

Well, that didn't work. I created a File called Galaxy 19 and with the use of Kate I pasted your command into the File. Here is the answer:

scan -o zap -l 10750 Galaxy19
scanning Galaxy19
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
ERROR: cannot open 'Galaxy19': 2 No such file or directory

Well you didn't run the command in the same directory as the file it looks like. If you created "Galaxy19" on your Desktop (for example), then in the terminal you need to do:
$ cd ~/Desktop/
$ scan -o zap -l 10750 Galaxy19

Or just explicitly list the file's path:
$ scan -o zap -l 10750 /home/pepse/Desktop/Galaxy19 (or where ever the file is saved)

The scan command has to be able to open that file to find the transponders to scan.

 

[Pepse]

Okay, I "think" I have it figured out. If I understand what happened when I did some scans of Galaxy 19 and Galaxy 10R my Satellite needs tweaking/tuning. Here is the result from Galaxy 10R:


jim@jim-desktop:~$ S 11720000 V 27692000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 11732000 H 13240000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 11800000 V 26657000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 11805000 H 04580000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 11966000 V 13021000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 12104000 V 02222000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 12114000 V 04444000 AUTO
bash: S: command not found
jim@jim-desktop:~$ # Galaxy 10R @ 123W
jim@jim-desktop:~$ # freq pol sr fec
jim@jim-desktop:~$
jim@jim-desktop:~$ S 11720000 V 27692000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 11732000 H 13240000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 11800000 V 26657000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 11805000 H 04580000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 11966000 V 13021000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 12104000 V 02222000 AUTO
bash: S: command not found
jim@jim-desktop:~$ S 12114000 V 04444000 AUTO
bash: S: command not found

So, if I did this right, like I said I'll need to tune the Satellite. And I'll need to try one of those Dish Pro things for now.

Later. Pepse.

 

[gillham]

Don't try to paste the text straight into a terminal window.
You need to create a file with that in it.
So something like:
$ cat > Galaxy19
<you paste the "S 11720000 V 27692000 AUTO" lines it into the terminal window>
<you press control + z>
$ scan ...... commands from above.

 

[Pepse]

Sorry it's been a while.

What I did was I tried to make a folder and put that text into it but that wouldn't work. But I found that text in Kate (Klipboard) and it created a text file (folder?) on my desktop so I went to a Konsole and I changed directory to "Desktop" and had it scan? that way. So, on my Desktop is a file called "Galaxy10R", which when I put my mouse over it it is listed as a "plain text document"

Later. Pepse.

 

[Pepse]

This ADS Tech card seems to be a POC as Progdvb doesn't recognioze the PCI card. It's there as Linux sees it. So, I decided to order me a Twinhan 102g DVB card in hopes that it works. But in the meantime I will try to find some other sites similar to Progdvb and see if any of them will see my ADS Tech card.

Pepse.

 

[oncewaslost]

I picked up one of the ADS Tech PTV-341 last summer. I never tried it on linux but since you are trying it on windows now,I will chime in with my experience with it.

Other than the ADS Tech software, I never got any windows DVB software to work with the card. I was using the last version of the BDA driver/software available from their web site. ProgDVB would not see the card at all. DvbViewer, and DvbDream both would see the card, but would not tune anything. I tried Windows ME, 2000, XP SP2 & SP3. I tried it in three different computers.

The closest I came was this: I found that if I used the ADS Tech software to tune a channel, then close that software and open DvbViewer or DvbDream I could tune that same channel, but nothing else. I even tried drivers from Kworld since they had a card with the same conexant chipset.

The card works fine with the ADS Tech software.

After countless hours(weeks actually) I gave up and ordered a twinhan 1020 for the project.

 

[Pepse]

Thanks, at least I know I am not alone on this card. I will try your ideas whilst I am awaiting my Twinhan 102g.

As usual My being cheap does tend to show.

Later. Pepse.

 

[Pepse]

Well, I got the Twinhan 102g Thursday. It has issues in windows XP. After intalling the drivers and software I get an error of: CANNOT SUPPORT THE CARD OR DRIVER, PLEASE CHECK THE HARDWARE INSTALLATION. Well I tried the card in the other 2 PCI slots and got the same error. I e-mailed the problem to Twinhan. What I didn't tell them is I tried the card in DVB Dream and it almost works. I was able to get a channel on Galaxy 10R/Galaxy 18. Couldn't get the satellite aimed good enough for a strong signal but it was close. Also tried it with PROGFINDER and I couldn't tune it in to a strong enough frequency. Windows does not recognize this card in my hardware configuration.

But, even though I can get something with DVB Dream This card totally locks up any Linux I have tried, on boot up. It gets to " udev " and stops. UDEV is the hardware detector. I will go to a Linux forum and see if there is a work-around for that issue.

Later. Pepse.

 

[Pepse]

Well as for the Twinhan 102g I still have it. I realized that when I got a channel on Galaxy !0R it is an HD channel and my Twinhan is only a DVB-S card. So, I just gotta get back out there and try some other Sats. But I think my splitters might be causing some of my problem so I am going to get a couple new ones and see if that helps. Actually I will feel better NOT using the Dishpro splitters. They were free anyway.

As for the Linux side, no luck yet.. I am still having issues with getting changes to modprobe.

Later. Pepse.

 

[voomvoom]

The 102g card will get an HD channel in DVB-S, but it won't get an S2 channel, or a Digicipher2 channel.

 

[Pepse]

I thought that DVB-S2 is for HD and DVB-S for SD?

Pepse.

 

[voomvoom]

DVB-S = modulation type
DVB-S2 = modulation type
Digicipher2 = modulation type
SD = Video
HD = Better Video

you can have SD or HD in any of the modulation types