ABM 19.2 scan

[Wild Bill]

Hi, this is my first posting so I hope it is okay. I've already tried to search for a solution but so far haven't found anything completely similar.

I have just upgraded my Vu+ Ultimo from ViX 3.0 build 808 to Apollo build 023. As I could not restore a settings backup file, I first grabbed screen shots of the old menu settings and the major ones I have now set as they had been, either with the Setup Wizard or by going into the menus afterwards. My three tuners are now setup exactly as they were before and all are the same: DiSEqC A/B for 28.2E and 19.2E. I have attached two current screenshots:

36435 36434

In the past, I could select from the 19.2E providers as well as FreeSat and Sky for 28.2E, and I used AustriaSat Astra 1 for 19.2E. After the upgrade however, I only can see the 28.2E providers. I can tune to 19.2E channels with no problem. I have put some BBC and German channels in my Favourites bouquet to prove the DiSEqC switch is working properly and can smoothly switch between these using the CH +/- button on the remote.

36436

I've also seen that this problem can be a result of poor signal quality/misaligned dish, but the signal strength on all the 19.2E channels I have tried are all between 95%-100%. I cannot find any other settings to instruct ABM look for any particular providers or providers for a particular satellite. I see in the v1.1 manual that "ABM will only present you with setup options that are compatible with the tuner configuration of your STB."

Could someone please explain where I am going wrong? Thanks very much.

[abu baniaz]

You are not doing anything wrong.

Apprently those providers have shared chanenls over a few satellites. You need to have 23.5 also to be able to use one containing 19.2. Despite teher being over a 1000 chanenls on 19.2, we have not made progress on ABM and 19.2 yet.

[Wild Bill]

That's very odd. I have only ever had my tuners set to 28.2E and 19.2E, nothing else as I have two fixed dishes, but yet before upgrading all the 19.2E providers were visible and the AustriaSat Astra 1 provider was functioning without any problem. I attach some OLD screenshots taken at the end of June while still on ViX 3.0 build 808:

36447 36446 36445 36444

The only difference that I can see is that in the tuner settings 19.2E used to be described as 19.2E Astra 1KR/1L/1M/2C whereas it is currently described as 19.2E Astra 1KR/1L/1M/1N, i.e. 1N has been added and 2C removed from the description. Could this explain anything?

[abu baniaz]

There are the differences in the xml, one highlighted

New


<provider>
<name>AustriaSat</name>
<streamtype>dvbs</streamtype>
<protocol>fastscan</protocol>
<!-- namespace could change even on the same sat...
in case of use the service hacks to fix it -->
<namespace>c00000</namespace>
<transponder frequency="12070000" symbol_rate="27500000" polarization="0"
fec_inner="3" orbital_position="235" inversion="2" system="0"
modulation="1" roll_off="0" pilot="2"
nit_pid="0x3b6" nit_current_table_id="0xbc" nit_other_table_id="0x00"
fastscan_pid="0x3b6" fastscan_table_id="0xbd" />
<sections>
<section number="1">AustriaSat</section>
</sections>
<servicehacks>
<=!=[=C=D=A=T=A=[
if service["number"] > 999 or service["number"] < 1:
skip = True
]=]=>
</servicehacks>
</provider>


old


<provider>
<name>AustriaSat</name>
<protocol>fastscan</protocol>
<!-- namespace could change even on the same sat...
in case of use the service hacks to fix it -->
<namespace>c00000</namespace>
<transponder frequency="12515000" symbol_rate="22000000" polarization="0"
fec_inner="4" orbital_position="192" inversion="2" system="0"
modulation="1" roll_off="0" pilot="2"
nit_pid="0x3b6" nit_current_table_id="0xbc" nit_other_table_id="0x00"
fastscan_pid="0x3b6" fastscan_table_id="0xbd" />
<sections>
<section number="1">AustriaSat</section>
</sections>
<servicehacks>
<=!=[=C=D=A=T=A=[
if service["number"] > 999 or service["number"] < 1:
skip = True
]=]=>
</servicehacks>
</provider>

[Wild Bill]

Is there not anyway to put it back on 19.2E or perhaps duplicate the service on 19.2E? Otherwise, is my only option to download an available static bouquet that can be uploaded to my Ultimo or build a bouquet myself?

[abu baniaz]

Thanks for raising the issue.

I flashed build 808 and used the old version of ABM. Was able to read 19.2. Transplanted it no Apollo 23, was also able to read 19.2. I'll post in the dev section. Sorry can't provide timescales.

I have retitled thread.

[Wild Bill]

Thanks very much for your help.

[Rob van der Does]

The reason is that there is no 19.2 provider (for ABM).
Whatever you do with old versions is only a spurious solution: just look at the contents of the created bouquets.
Why do you think we made those changes?

[abu baniaz]

Please test this file
Extract xml and transfer to following location on receiver.
/usr/lib/enigma2/python/Plugins/SystemPlugins/AutoBouquetsMaker/providers/