PDA

View Full Version : [ABM-DVB-C] Oxford NetID 20



ossie5
11-06-16, 23:51
I've been banging my head against a wall trying to get ABM to work for DVB-C Oxford (20). Now it finally works.
The frequency should be 642250 not 643000 as it currently is in the xml. Will my modification get overwritten?

YM

abu baniaz
12-06-16, 00:28
Can you attach your lamedb file? It will be in /etc/enigma2/ You will have to zip it before you can attach it. Can you also upload your debug log.

The data is on all frequencies. You need a lock for it to work. These are the frequencies with customer channels. Pure areas only have whole number frequencies although it will lock on nearest frequency to one specified. Cue the arguments about correct/wrong frequency...



<transponder frequency="131000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="147000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="155000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="163000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="339000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="347000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="355000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="363000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="371000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="379000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="387000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="395000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="411000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="419000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="427000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="435000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="443000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="451000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="459000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="467000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="507000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="515000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="555000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="563000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="571000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="579000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="587000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="595000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="603000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="611000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="619000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="627000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="635000000" symbol_rate="6887000" fec_inner="3" modulation="3"/>
<transponder frequency="643000000" symbol_rate="6887000" fec_inner="3" modulation="3"/>
<transponder frequency="651000000" symbol_rate="6887000" fec_inner="3" modulation="3"/>
<transponder frequency="659000000" symbol_rate="6887000" fec_inner="3" modulation="3"/>
<transponder frequency="667000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="675000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="683000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="691000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="699000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="707000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="715000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="723000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="731000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="739000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="747000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="755000000" symbol_rate="6952000" fec_inner="3" modulation="5"/>


Your change will be undone on updates. If we were to change it for everyone, I'd be inclined to use the PVR EPG channel frequency. Your lamedb file will assist in this.

ossie5
12-06-16, 09:51
Hi,

In the zip i've put the lamedb and the 3 files from the python script (where I got the frequency from). Having looked around the forum, there are two other people that appear to have had the same problem as me in network ID 20. I don't know where the debug log file is.

YM

abu baniaz
12-06-16, 12:58
OK. I have changed it and will be in next image. https://github.com/oe-alliance/AutoBouquetsMaker/commit/490f906b80723c932486ac50ccc5ceb27a17ee1a

You can also update the provider file using the update config file feature

We used old data for the Pure Net ID values. Seems that there was rounding up, not rounding to nearest MHz. Well done for using the script. Glad Peter's work did not go to waste.

blackhawkcrow
14-06-16, 14:46
I also have struggled for months off and on with trying to get ABM for Oxford to work!!!! Keep on getting time out for tuner lock error, hoping this is the fix, well done ossie5


Sent from my SM-G900F using Tapatalk

lincsat
14-06-16, 18:21
Somebody had told me of a similar problem in Glasgow but I believe their problem is a weak signal on the default transponder. Would be interesting to know if anyone in Glasgow 00002 can confirm the frequency of 643.000 MHz

blackhawkcrow
15-06-16, 08:25
Updated the provider file last night, ran ABM and now happy to say working a charm !!!! I now have a perfect miraclebox
thanks again ossie5 & abu baniaz :thumbsup::thumbsup::thumbsup::thumbsup:

Yellow Ostrich
26-06-16, 11:36
Oh wow! This is why ABM has just started working for me in Oxford. Thanks Gents :)

Joyceman
11-11-16, 21:48
Hi please can someone help not sure where these files go I'm in Oxford and stuck

Joyceman
11-11-16, 21:50
Hi how did you get this to work where do you find provider file thanks

Andy_Hazza
11-11-16, 22:00
If you are on the latest ViX (latest being 4.2.013) you would setup in ABM (AutoBouquetsMaker) and select your Net ID in your Providers menu.


Sent from my iPhone using Tapatalk

Joyceman
12-11-16, 02:01
Thanks for the reply can't update box as it will wipe my skin and my set up . Can I just edit cable_uk_virgin .XML and restart and rescan as I just get tuner lock

abu baniaz
12-11-16, 02:27
It might not be the xml file. It could also be cabling, splitters, or signal level.

The xml file is in /usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers

Andy_Hazza
12-11-16, 08:11
Thanks for the reply can't update box as it will wipe my skin and my set up . Can I just edit cable_uk_virgin .XML and restart and rescan as I just get tuner lock

That is a poor excuse for not updating. Learn Learn Learn. lol


Sent from my iPhone using Tapatalk

Joyceman
12-11-16, 10:12
That is a poor excuse for not updating. Learn Learn Learn. lol


Sent from my iPhone using Tapatalk

Sorry I told a little white lie it wasn't my box . That was the issue it was a customers . And I didn't want to go through the whole process of updates . But thanks for all the help and quick respones

Joyceman
12-11-16, 11:08
It might not be the xml file. It could also be cabling, splitters, or signal level.

The xml file is in /usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers

Hi not the splitter or signal as auto scan work . When I looked at the net ID there is two for Oxford 20 But only 1 for 20 in abm files

abu baniaz
12-11-16, 11:53
I understand the following from your post:
Conventional scan works, ABM does not.

I don't know what you mean about two Net IDs. There is only one. Upload the lamedb file created by your normal scan, run the script that other have used, upload your ABM debug log.

Joyceman
14-11-16, 10:14
Hi is there a ipk that I could install like an updated abm plugin . Thanks

Joyceman
14-11-16, 10:43
Hi was referring to this in net id just thought that this maybe the conflict but maybe itt seem frequency was just incorrect . Can't upload files as don't have tge box customer has it but have trouble editing file as customer has a Mac and never used idreamx only know dcc . That why I wondered if there was an update ipk then I could correct it with a USB thanks for all your hard work and help
Oxford 1 NTL 00020 578.250 6.887
Oxford 2 NTL 00020 818.250 6.887

abu baniaz
14-11-16, 18:19
Can't upload files as don't have tge box customer has it
What business do you have?

Joyceman
14-11-16, 21:18
What business do you have?

fancy dress bussiness