Scanning for services finds nothing on TBS6984 + multiswitch

In the unlikely ;) event you encounter a bug, tell us here
Post Reply
igor.maly
Posts: 4
Joined: Thu Nov 29, 2012 12:29 am

Scanning for services finds nothing on TBS6984 + multiswitch

Post by igor.maly » Thu Nov 29, 2012 1:06 am

I have problem scanning services on this setup:
4 LNBs on multifeed pointed to 13.0E, 19.2E, 23.5E, 28.2E; connected to 17x16 DISeqC 2.0 multiswitch EMP Centauri P170.
5 outputs go to HTPC with 1x TBS 6984 and 1x Asus ES3-110.
2 outputs go to Dreambox 7025+, and one to another PC with Technisat Skystar HD2.
Both PCs are Win7 64bit, latest drivers and updates.

The problem: scanning services in Argus 2.0.1 Recorder Console gives "No signal" on almost every frequency on every LNB when using either one from 4 TBS tuners. When scanning (in Argus) through Asus tuner, I can receive pretty much everything.
Using another application works fine even with TBS tuners (DVBViewer, DVBLink).
On the other PC and on Dreambox everything works fine as well.

It seems like there is some incompatibility between Argus, TBS tuners, and the multiswitch.
However, there is support advertised in 2.0.1 for TBS and DISeqC; it might be that I'm doing something wrong, only I cannot figure out what.

Any suggestion/help would be appreciated.

User avatar
Hominidae
Posts: 361
Joined: Wed Feb 01, 2012 10:45 pm

Re: Scanning for services finds nothing on TBS6984 + multisw

Post by Hominidae » Fri Nov 30, 2012 1:25 am

When I started with 4TR around 8-10 months ago, I had the same problem with the TBS Quad card.
No Diseqc working (with a Technisat Gigaset 17x16 multiswitch) in 4TR.

Standard SAT equipment (tuners, TVs etc) worked fine.
In 4tr and other PC programs (win and linux), I could only tune to the first
sat position in my setup.
I blamed the drivers, returned the card and went for another brand.

igor.maly
Posts: 4
Joined: Thu Nov 29, 2012 12:29 am

Re: Scanning for services finds nothing on TBS6984 + multisw

Post by igor.maly » Fri Nov 30, 2012 8:10 am

Well, the drivers could not be *that* bad, since I can succesfully tune in DVBViewer and DVBLink...
I am using driver v1.0.2.3 dated Feb 2012.

Post Reply

Who is online

Users browsing this forum: No registered users and 13 guests