16 replies to this topic

[Huevos]

Cable scan seems to be knackered.

 

"Provider" works. List built from cables.xml.

"Frequency Bands" and "Frequency Steps" does not.

 

The only way to scan is user defined (single) transponder.

 

When selecting "Complete" the tlist is empty, so the result is the warning message "Nothing to scan! Please setup your tuner settings before starting a service scan.".

 

Tested on Duo2, Solo2, Solo SE, ET 6500... with internal and USB tuners.

[Huevos]

Frequency steps works on some boxes, but frequency bands doesn't appear to work on any.

Edited by Huevos, 30 June 2015 - 23:52.

[Dimitrij]

Please run tool manual(in telnet) for test.

[Huevos]

Please run tool manual(in telnet) for test.

Sorry, I don't understand.

 

What command exactly.

Edited by Huevos, 1 July 2015 - 14:46.

[Dimitrij]

see ScanSetup.py(def startCableTransponderSearch)

cmd = "%(BIN_NAME)s --init --scan --verbose --wakeup --inv 2 --bus %(BUS)d" % {'BIN_NAME':bin_name, 'BUS':bus}

for example et6500

BIN_NAME = tda1002x

[Huevos]

Ok, testing Xtrend 6500 in "Frequency bands" gives this:

tda1002x --init --scan --verbose --wakeup --inv 2 --bus 2 --scan-bands 127 --mod 64 --mod 256 --sr 6900000 --sr 6875000

Not sure what you mean about running that in telnet. It returns "Not found".

root@et6x00:~# tda1002x --init --scan --verbose --wakeup --inv 2 --bus 2 --scan-bands 127 --mod 64 --mod 256 --sr 6900000 --sr 6875000
-sh: tda1002x: not found
root@et6x00:~#

[Dimitrij]

Sorry,for et6500 not blindscan tool(tda1002x).

Is for et8000/8500/10000/7x00

[Huevos]

Manual scan, frequency bands, complete.

 

"Nothing to scan!\nPlease setup your tuner settings before you start a service scan."

 

Means tlist is not being built. What is the reason?

[Erik Slagter]

I think frequency bands and frequency steps only work on dmm receivers. They call an external binary with certain options that apparently only dmm implemented. It's just like blindscanning on DVB-S ridiculously bad implemented.

 

The best way to scan cable, indeed, is to scan the frequency that sends the NIT and have enigma use that info.

[peterjo]

I think frequency bands and frequency steps only work on dmm receivers. 

Both my Solo SE and DUO2 can do a cable automatic band scan and a manual full scan.

The Solo SE is using a Sundtek usb DVB-C tuner, the DUO2 an internal DVB-C tuner.

I think it is more tuner type related.

[Dimitrij]

Both my Solo SE and DUO2 can do a cable automatic band scan and a manual full scan.

 

In what image?

[Huevos]

 

Both my Solo SE and DUO2 can do a cable automatic band scan and a manual full scan.

 

In what image?

 

Used to work in OpenPLi and OpenViX in both "frequency steps" and "frequency bands" but there have been some changes in the last 12 months. It was working when I did the pre-defined cable transponder mod last year.

 

Now it just works in "frequency steps" on a few select receivers, and doesn't work in "frequency bands" on any receivers.

 

Anyway if it is not available why can users select it? This really needs sorting out. The ability to scan services should be a top priority of and set-top-box... and having an error message telling the user their tuner needs setting up properly when this is impossible in the software is very misleading for a typical user.

Edited by Huevos, 3 July 2015 - 18:47.

[peterjo]

 

Both my Solo SE and DUO2 can do a cable automatic band scan and a manual full scan.

 

In what image?

 

I tested my Solo SE with both PLI and ViX last week.

Duo2 with ViX .

[Erik Slagter]

Anyway if it is not available why can users select it? This really needs sorting out.

Because it's implemented in a ridiculous bad way, where enigma calls an external closed source binary from the manufacturer. So a.o. this means that enigma can't even know what scanning capabilities are supported for a certain tuner/manufacturer.

[peterjo]

 

Anyway if it is not available why can users select it? This really needs sorting out.

Because it's implemented in a ridiculous bad way, where enigma calls an external closed source binary from the manufacturer. So a.o. this means that enigma can't even know what scanning capabilities are supported for a certain tuner/manufacturer.

 

You are absolutely right. (geknutsel). Also the manual user transponder scan is done completely different than automatic and manual full scan. That's why the first is working on the ET6500 and the last 2 isn't.

It would be nice if someone rewrites it completely , suitable for all brands.

[Erik Slagter]

It would be nice if someone rewrites it completely , suitable for all brands.

If that only would be possible. But you're dependend on the manufacturer's closed source binaries, as long as the tuners' specs are closed.

[sundtek]

Blindscan should just work with the Sundtek devices (because you mentioned them before).

 

If there's still an image out there which does not just let us know.

 

So far we tested:

OpenPLI

OpenVIX

VTI

Dream Multimedia's Dreambox Images

BlackHole

Edited by sundtek, 19 July 2015 - 00:36.