cables.xml is not used by our e2
Explains why the errormessage remains the same.
Posted 30 April 2015 - 14:39
cables.xml is not used by our e2
Explains why the errormessage remains the same.
Vu+ Ultimo 4K (4 TB HD, DVBS FSB, DVBC FBC & OpenPli 9),
Xtrend ET10000 (1 DVBS works via ethernet & OpenPli 9),
Xtrend ET10000 (DVBT2 & OpenPli 9, located in Thailand). Only latest stable releases.
Xtrend ET10000 (works via ethernet & OpenPli 9) and
Xtrend ET8000 (1 TB HD, 1 DVBT2 & works via ethernet & OpenPli 9)
Posted 30 April 2015 - 15:48
cables.xml is not used by our e2
You didn't provide a cables.xml but if people install a cables.xml into /etc/tuxbox/ then we can define our DVB-C with an operator and the operator is pick up from the cables.xml.
So next question is why don't you include any cables.xml file in OpenPLi image?
NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.
Wanna help with OpenPLi Translation? Please read our Wiki Information for translators
Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)
AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
Posted 30 April 2015 - 16:21
No problem, just hallerThank you very much.I ask you to carry out new tests, when the package will be upgradedExplains why the errormessage remains the same.cables.xml is not used by our e2
meta-dream: update blindscan utils to 1.9
Vu+ Ultimo 4K (4 TB HD, DVBS FSB, DVBC FBC & OpenPli 9),
Xtrend ET10000 (1 DVBS works via ethernet & OpenPli 9),
Xtrend ET10000 (DVBT2 & OpenPli 9, located in Thailand). Only latest stable releases.
Xtrend ET10000 (works via ethernet & OpenPli 9) and
Xtrend ET8000 (1 TB HD, 1 DVBT2 & works via ethernet & OpenPli 9)
Posted 30 April 2015 - 19:17
NimManager.py:cables.xml is not used by our e2
if self.hasNimType("DVB-C") or self.hasNimType("DVB-T"): print "Reading cables.xml" db.readCables(self.cablesList, self.transponderscable)It's not used by the cablescan plugin though, probably. But if you're going to scan on provider name, you need it.
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 30 April 2015 - 20:17
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Posted 1 May 2015 - 08:07
The "old" version is what you get if you use the url that's in bb recipe. It's a generic url construction, iirc there is no "1.7" or "1.9" in the url. We can change it to use 1.9 explicitly, but the recipe is shared and I am not sure if it's still works then. Maybe blzr can have a look?
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
Posted 1 May 2015 - 09:22
@Erik
athoik already provided patch for this
http://forums.openpl...ndpost&p=489330
Edited by blzr, 1 May 2015 - 09:22.
Posted 1 May 2015 - 14:22
Posted 3 May 2015 - 12:17
Vu+ Ultimo 4K (4 TB HD, DVBS FSB, DVBC FBC & OpenPli 9),
Xtrend ET10000 (1 DVBS works via ethernet & OpenPli 9),
Xtrend ET10000 (DVBT2 & OpenPli 9, located in Thailand). Only latest stable releases.
Xtrend ET10000 (works via ethernet & OpenPli 9) and
Xtrend ET8000 (1 TB HD, 1 DVBT2 & works via ethernet & OpenPli 9)
Posted 3 May 2015 - 14:22
New Pli image 2015-05-03 on dm7020hd.
Tuner configured first for frequency bands, then frequency steps, then provider (Kabel Deutschland).
Automatic scan and manual scan (complete) : all ok
Then I tested Cable Scan with Network id 61441. Result: Scanning failed!
This doesn't work and it never worked.
Best and fastest method is Manual scan -> User defined transponder 466 MHz -> Network scan = yes.
Edited by hein holz, 3 May 2015 - 14:25.
Posted 3 May 2015 - 15:22
Now I tested Cable Scan with Network id 61448. Result: It's searching a bit longer, but scanning failed!
Here is a part of my NIT. May be cable scan only works if Network_ID = Original_network_ID?
dvbsnoop V1.4.51 -- http://dvbsnoop.sourceforge.net/ ------------------------------------------------------------ SECT-Packet: 00000001 PID: 16 (0x0010), Length: 250 (0x00fa) Time received: Sun 2015-05-03 15:47:18.639 ------------------------------------------------------------ PID: 16 (0x0010) [= assigned for: DVB Network Information Table (NIT), Stuffing Table (ST)] Guess table from table id... NIT-decoding.... Table_ID: 64 (0x40) [= Network Information Table (NIT) - actual network] section_syntax_indicator: 1 (0x01) Network_ID: 61448 (0xf008) [= Kabel Deutschland | 276 | Cable | Kabel Deutschland] Version_number: 13 (0x0d) current_next_indicator: 1 (0x01) [= valid now] Section_number: 3 (0x03) Last_Section_number: 3 (0x03) Transport_stream_ID: 10016 (0x2720) Original_network_ID: 61441 (0xf001) [= Deutsche Telekom | Deutsche Telekom AG] DVB-DescriptorTag: 68 (0x44) [= cable_delivery_system_descriptor] descriptor_length: 11 (0x0b) Frequency: 55836672 (= 354.0000 MHz) FEC_outer: 2 (0x02) [= RS(204/188)] Modulation (Cable): 5 (0x05) [= 256 QAM] Symbol_rate: 430080 (= 6.9000) FEC_inner: 15 (0x0f) [= No conv. coding] DVB-DescriptorTag: 65 (0x41) [= service_list_descriptor] descriptor_length: 18 (0x12) service_ID: 50033 (0xc371)[ --> refers to PMT program_number] service_type: 25 (0x19) [= advanced codec HD digital television service] service_ID: 50035 (0xc373)[ --> refers to PMT program_number] service_type: 25 (0x19) [= advanced codec HD digital television service] service_ID: 50031 (0xc36f)[ --> refers to PMT program_number] service_type: 25 (0x19) [= advanced codec HD digital television service] service_ID: 50032 (0xc370)[ --> refers to PMT program_number] service_type: 25 (0x19) [= advanced codec HD digital television service] service_ID: 50034 (0xc372)[ --> refers to PMT program_number] service_type: 25 (0x19) [= advanced codec HD digital television service] service_ID: 50030 (0xc36e)[ --> refers to PMT program_number] service_type: 25 (0x19) [= advanced codec HD digital television service]
Edited by hein holz, 3 May 2015 - 15:25.
Posted 3 May 2015 - 19:06
Now I tested Cable Scan with Network id 61448. Result: It's searching a bit longer, but scanning failed!
Here is a part of my NIT. May be cable scan only works if Network_ID = Original_network_ID?
Posted 3 May 2015 - 19:41
http://git.opendream...cd2b707b6127e53
+ if cmd.startswith("cxd1978") or cmd.startswith("tda1002x"): + cmd += " --scan-flags DVB-C"
What does it mean("--scan-flags DVB-C")?
On openPli used " --scan-bands ".
Edited by Dimitrij, 3 May 2015 - 20:53.
GigaBlue UHD Quad 4K /Lunix3-4K/Duo 4K
Posted 4 May 2015 - 17:26
"--scan-bands" and "--scan-flags DVB-C" do exactly the same, only the syntax is different . No need to change anything
These options reduce the amount of frequencies scanned by cxd1978. The frequencies are hard coded.
root@dm7020hd:/# cxd1978 --init --scan --verbose --wakeup --inv 2 --bus 2 --scan-flags DVB-C:VHF II failed reading revision from driver, default to 1 waiting for 1 seconds FAILED 105000 8000000 FAILED 113000 8000000 FAILED 121000 8000000 FAILED 129000 8000000 FAILED 137000 8000000 FAILED 145000 8000000 FAILED 153000 8000000 FAILED 161000 8000000 FAILED 169000 8000000
root@dm7020hd:/# cxd1978 --init --scan --verbose --wakeup --inv 2 --bus 2 --scan-bands 2 failed reading revision from driver, default to 1 waiting for 1 seconds FAILED 105000 8000000 FAILED 113000 8000000 FAILED 121000 8000000 FAILED 129000 8000000 FAILED 137000 8000000 FAILED 145000 8000000 FAILED 153000 8000000 FAILED 161000 8000000 FAILED 169000 8000000
0 members, 3 guests, 0 anonymous users