13.0 just stopped working

[Cohibastevie]

Hi.

I unplugged my vu solo 2 and all cabling to do a spring clean.

Now i have lost 13.0E as a result

I have a multisat setup with 28.2 on tuner a

Then 19.0e and 13.0e on tuner b via a twin lnb and diseq switch

28.2e and 19.0e are working find but 13.0 is getting no signal at all.

Thoughts anybody?

Much appreciated as always

Thanks in advance

[malcolmp]

Hi.

I unplugged my vu solo 2 and all cabling to do a spring clean.

Now i have lost 13.0E as a result

I have a multisat setup with 28.2 on tuner a

Then 19.0e and 13.0e on tuner b via a twin lnb and diseq switch

28.2e and 19.0e are working find but 13.0 is getting no signal at all.

Thoughts anybody?

Much appreciated as always

Thanks in advance

Hello,

I have "not quite the same problem here".When I try to run ABM NC+ I get "Tuning failed fatal", other bouquets (Sly IT FTA, and Bis FTA are OK) Full manual tune for 13E is OK and all channels load.

[Cohibastevie]

I get the exact same error when running a scan "tuning failed fatal"

[malcolmp]

I get the exact same error when running a scan "tuning failed fatal"

Do you mean you get the error when you're running a scan with NC+?
PS: according to thread German Autoboquets? (Today (sat), 21:26 murphyb007 ) reply from abu baniaz "To recap Update image tomorrow"
Maybe this will rectify problems?

m

[abu baniaz]

13.e stopped working or ABM does not work on a 13.e provider.

If an ABM issue, please post as per this thread:
http://www.world-of-satellite.com/sh...port-questions

With regards to quote about updating image, that was made to take in a new provider for ABM.

[malcolmp]

Enigma2_debug_2017-04-05_12-52-29.logEnigma2_debug_2017-04-04_16-47-54.log

[malcolmp]

Here is a file

[abu baniaz]

There was some changes to the 10719 frequency.

A signal finder test of that frequency will therefore not lock > This probably led to the statement that 13e no longer works. OP could have checked other frequncies

The tuning details for NC+use 10719 on 13e. ABM cannot lock as shown by the debug log. We will update the files on Github soon.

[Cohibastevie]

I have checked through the various transponders on 13.0e as suggested above and get full signal with lock.

So i can assume this is due to a frequency change?

Thanks for everybodies input

[Huevos]

System and modulation change, not frequency. Just pull the latest config files.

[Cohibastevie]

How do I pull the latest config files?

[abu baniaz]

Select "update config files" in the AutoBouquetsMenu and then press OK.

[Cohibastevie]

Great. Thanks very much

[Cohibastevie]

Hi

I have updated the config files and still get no signal on transponder 10719 v 27500

Is this normal after updating the config files?

Thanks

[abu baniaz]

You are expecting people to read your mind. You are checking signal finder and it is still not finding a signal. Why don't you say that?

The config file inferred in post 11/mentioned in post 12 is for AutoBouquetsMaker. It will work on NC+ if you have updated the file successfully

When you check signal finder, it uses details in the satellites.xml file. Firstly looks in /etc/enigma2 for a user version, then /etc/tuxbox for the system one

You can replace the satellites.xml file manually or wait for the next image update. There is no way of doing it on the receiver. The request for this function was rejected.

Download from here

http://satellites-xml.org/