Abu Baniaz

It looks like I mixed up the terminology. The point I was trying to make is below

 

https://github.com/O...icon.py#L78:L80

@Wanwizard, I didn't realise there was a daily build by PLI. Thanks for the correction/information. Anyone else who read my previous post, please disregard it.

 

SRP has prioroity over SNP. The SNP sets have SRP references where there are clashes.

 

If the channel has different names depending on satellite, we can add them too. For clarification purposes,

Markiza HD will use picons in this order: reference > markizahd > markiza
Markiza (HD) will use picons in this order: reference > markizahd > markiza

The "(" and ")" are not allowed and skipped

 

If links need adding, just submit a pull request/raise an issue. There are several contributors to the Ocram project who are active on this forum.

The plugin's name was changed to hrtunerproxy. It has been this for a while now.

There seems to be a problem with scanning on a motor. If the transponder is dead, out of footprint area or dish is slightly out, the scanning does not progress to the next TP. It stalls trying to scan the first listed Transponder forever. I waited 20 minutes in one test.

I tested this with:
Mutant HD51 on 6.2 RC 2018/04/24
1.1 Triax dish
TM 0.1 Gold single LNB
Tuner is set as simple, positioner(selecting satellites)
No other options were changed

The same issue is present on latest Developer OpenViX image using a Solo 4K using the FBC tuner.

We suspect that this commit partly responsible
https://github.com/O...c96ca95eadf3ac9

Is it possible we can have a look at the issue please?
Thanks in advance

I'll add other devices when we have a successful build (On Ubuntu 16.04.4 LTS) and bootable image for wetek or odroid

I have built the image for hardkernel-odroid c2. I don't know how to flash/transfer this image as the software I have only does .img file.

openpli-enigma2-homebuild-hardkernel-odroidc2.rootfs.tar.bz2

https://mega.nz/#!cqAlEbRI!beAywGHYAoAakRoCiqscasJpuqaqazI5nNgPj8LT1O0 

People get confused on lots of forums. I share your desire to avoid this.

If a person also had a receiver/device that was not able to use unicable. Is that not relevant? For example, a TV with built-in satellite tuner or provider's official reciever.

As this thread and numerous others have shown, people get confused about number of tuners versus number of tuner cards. That is before we even involve FBC tuners. Anyway, If establishing number of tuners, then if all devices/tuners will be compliant with technology is the way you want things done, than I will do that while here.

How many receivers will be making use of this dish and LNBs?

That's the wrong question. The question is whether how many TUNERS will be used. A VU+ Ultimo4k can have 18 tuners...

I beg to differ. It is the right question and comes up higher up in the logic process.
The number of tuners question/answer comes after establishing the number and also the capability of receivers.
I agree with the asking about the number of tuners to be used.

We have established that he is only using one receiver, so the question/debate is pointless. However the considerations would have been:
If several receivers will be connected, the multi-switch route would be better.
If one or more of the receivers cannot use unicable, we would have to dismiss the unicable route or use a multi-switch with a legacy output.

As you have mentioned/hinted, it is possible to lock the two "actual" tuners on the FBC tuner card. (You have referred to it as a "complex").

So, the four cables is a more robust install. It is cheaper to install cables in one go even not used than add afterwards.

Another option is:
Install two FBC cards (and a maybe a twin card card).
Do not use the diseqc switches.
Use unicable LNBS instead of universal ones and connect all direct to the receiver.

This is where the FBC tuner + unicable LNB combination will pay dividends.

I hope this picture explains things graphically. One FBC satellite tuner card installed.
 
Tuner A set to Diseqc ABCD
Tuner B set to Diseqc ABCD
Tuner C left as FBC Automatic
Tuner D left as FBC Automatic
Tuner E left as FBC Automatic
Tuner F left as FBC Automatic
Tuner G left as FBC Automatic
Tuner H left as FBC Automatic

One FBC tuner card will be fine for most occasions. The one card is more than one tuner. This has been said several times in this thread. Please understand this first before you go any further. If you still do not understand it, the rest will just stay confused. Best you deal with understanding this first.

 

You can't get a pin point answer if you don't pin-point what you have/want to achieve Everyone's situation is different.

 

In my experience people assume and post assumptions and people respond to those assumptions. Once you have an assumption and do not let go, it just gets muddy. I appreciate the language issue.

 

IMO, it is best to set out what you want to achieve, and people will post options for you to consider. Once you have a set of options, you can explore the one that is most suitable for you.

Unless you use a unicable multiswitch, you will still need two signal wires to the receiver. In my opinion, it is far more economical  to use standard LNBs and two diseqc switches.

 

I'll keep you updated on developments, for the moment, I haven't seen any more transponders go black.

Can you please let me know which transponders with SD channels have now gone black?

Thanks.

 

    broken_TSIDS = [
        2007, #7d7 20170518
        2011, #7db 20170425
        2012, #7dc 20170518
        2019, #7e3 20170518
        2021, #7e5 20170516
        2023, #7e7 20170331
        2025, #7e9 20170518
        2026, #7ea 20170425
        2029, #7ed 20170516
    ]
 

Well done. Congratulations.

I am posting this for anyone wanting to obtain a raw Transport Stream recording using a Sundtek tuner. (Please do not confuse with normal video recording in .ts format.)
The transport stream recordings are useful for interrogating the data.

Issue the following command, this will give you the tuner frontend node (on set top boxes usually adapter1)

/opt/bin/mediaclient -e | grep adapter

Output will be similar to
 

     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0
     FRONTEND: /dev/dvb/adapter1/frontend0
     DVR: /dev/dvb/adapter1/dvr0
     DMX: /dev/dvb/adapter1/demux0

Tune to your desired frequency. In this example, adapter is 1 and frontend is 0.
You must ensure adapterN matches your tuner. (We got this using the mediaclient -e command)
Modify the values according to your need (those sample values).

For Terrestrial.

/opt/bin/mediaclient -m DVBT -f 490000000 -b 8 -d /dev/dvb/adapter1/frontend0

For Cable

/opt/bin/mediaclient -m DVBC -f 667000000 -S 6952000 -M Q64 -d /dev/dvb/adapter1/frontend0

-m device mode
-f frequency in Hz
-M modulation
-S Symbol rate

Ensure you get a LOCKED notification.

If you don't know any cable frequency you might try doing a blind scan to figure out some frequencies on the console

/opt/bin/mediaclient --blindscan /dev/dvb/adapter1/frontend0

Make sure enigma2 is not accessing the tuner. Simplest thing to do is to disable the tuner in the tuner configuragion menu.

/opt/bin/mediaclient --lc

Snippet below shows nothing is connected
 

root@tmnano3t:~# /opt/bin/mediaclient --lc
**** List of Media Clients ****
/dev/dvb/adapter1/frontend0:
  No client connected
/dev/dvb/adapter1/dvr0:
  No client connected
/dev/dvb/adapter1/demux0:
  No client connected
/dev/mediainput0:
  No client connected

This will list who is currently accessing the tuner this should show up "No client connected".

Once your tune command has locked to a channel and printed [LOCKED] and there's no other client connected, you can start to capture some raw data.

To be sure that the frequncy is useful, for you perform a channel scan
 

/opt/bin/mediaclient --tsscan /dev/dvb/adapter1/dvr0

(Again, take care about adapter number, it's usually adapter1 on set top boxes)

This should give you a list of TV channels on the transponder you are tuned to.

Ensure you have enough space on the storage device for the recording otherwise the box might crash if you run out of space).

In this example, we are saving to the hdd. Amend for your needs
 

/opt/bin/mediaclient --cat /dev/dvb/adapter1/dvr0 > /media/hdd/test.ts

You can abort/end the capturing by pressing CTRL and C together. Two minutes recording is usually enough.

It makes it easier to find channels, you can then move into the proper bouquet.

Sent from my HTC One M9PLUS using Forum Fiend v1.3.3.

The bitbake file for Lraizer's plugin, Autobouquets 28.2 is here

https://github.com/L...obouquets-e2.bb

 

It will build the binary for the receiver's architecture.

 

Please do not confuse with OE-Alliance AutoBouquetsMaker