Update 5.0.023 all stations black - timeout PAT

[nekrub2]

When doing a couch Flash on my VU+ Solo2 to VIX 5.0.023 it all went through and restarted. However all station were black and showed a timeout error message on reading PAT.

So I did a USB flash and restored the old backup settings. > same result

Has the new version a differnt path to the PAT? How can this be fixed.

Meanwhile I went back to 5.0.020 and it all works as before. Has any other Solo2 user seen the same behaviour?

Thanks for looking into this and hopefully fixing it for the next release.

nekrub2

[spanner123]

I did a 'normal' software update (not usb or couch flash) to 5.0.023 today on my Solo2 and all working fine!

[Andy_Hazza]

Working fine on my Vu+ Solo2 here also.


Sent from my iPhone using Tapatalk

[ronand]

My solo2 is working fine on 5.0.023

[nekrub2]

Hi guys

Do you have a hard disk attached or installed to your box? Could it be that I have a memory issue? I did another try: USB installation, no restore of settings, search of channels. Afterwards I could open the stations for 10 minutes before the same PAT error came up again on all stations.

I wonder weather I have to stay on VIX 5.0.020 forever.

Best regards
nekrub2

[twol]

Buy a usb stick and format FAT32
Fresh flash, don't restore settings.
Wizard setup
Set debug logs to yes and set save to USB not flash
Reboot and then run until problem occurs.
Post debug log from the usb.

[nekrub2]

Another try with 5.0.025
Driver 2017-05-22
Kernel 3.13.5
Python 2.7.12
Skin Army-MoodBlue_mod 1280x720

Software update via menue

Found behaviour Startup Station SRF1 comes clear. Other stations such as Das Erste (Free) get Timeout error on reading PAT-
No log is written, even debug log is activated.
When changing the second station as startup station this station comes clear, but the other ones (except for SRF1) not.

Could it be that the PAT path has been moved to an other directory since 5.0.021?

Until somebody tells me what to do I will run my box with 5.0.020.

Please be aware when further developping openvix that not all users have HD, fast processors and a lot of memory.

Thanks for looking what has changed in respect of PAT.
nekrub2

[abu baniaz]

Maybe a diseqc switch issue.

[nekrub2]

New plain installation, no restore of backups. Here and now the error comes up again. I could create logs > 1503403883.33 and send them to vixlogs@oe-alliance.com, did not find timeout on PAT. Maybe you cracks find the root cause.

Thanks a lot
nekrub2

[nekrub2]

Dear all

Having investigated in the log files I fould a certain pattern
< 29.152> [Avahi] avahi_timeout_new
< 29.157> [Avahi] avahi_watch_new(3 0x1)
< 29.158> [Avahi] avahi_timeout_update

< 29.162> [Avahi] avahi_timeout_new
< 29.164> [Avahi] avahi_timeout_free

< 29.166> [Avahi] avahi_timeout_new
< 29.168> [Avahi] avahi_timeout_free

< 29.169> [Avahi] avahi_timeout_new
< 29.171> [Avahi] avahi_timeout_free

< 29.173> [Avahi] avahi_timeout_new
< 29.175> [Avahi] avahi_timeout_free

< 29.176> [Avahi] avahi_timeout_new
< 29.179> [Avahi] avahi_timeout_free

< 29.181> [Avahi] avahi_timeout_new
< 29.183> [Avahi] avahi_timeout_free

< 29.184> [Avahi] client state: 2
< 29.189> [Avahi] avahi_timeout_new
< 29.192> [Avahi] avahi_timeout_free

The first values represent the frequencies. [Avahi] must be the program that reads on the parameters for the selected channel.

Would be great if someone could provide me a fix.
Best regards
nekrub2

[nekrub2]

Log file after new USB flash 5.0.26 without restore of any settings. Still time-outs when switching channels. Looks like a memory leak. When restarting the channel previously having a time-out comes clear, after zapping to a new channel the same problem starts again.

[abu baniaz]

You issue is a hardware issue, most probably diseqc switch.

Avahi is a network item that had not been used for anything yet. Ignore any references to it in your logs.

[nekrub2]

Dear Abu
If it was a disequ issue: Why does it work with OpenVix 5.0.020? The tuner settings are the same. For me it cannot be a hardware faillure. Did you change the coding of the tuner settings?

These are the setting on my box under 5.0.020 and also manually under 5.0.026 done.

Tuner A: nothing configures (loop through to tuner B)
Tuner B:
Configuration mode simple
Mode DISEEqc A/B
Port A 13.0E Eutelsat HB
Port B 19.2E Astra
Send voltage 22Khz yes
Send Disecq only on sat change no


Please reconsider your conclusion.
Thanks a lot
nekrub2

[abu baniaz]

Dear Abu
If it was a disequ issue: Why does it work with OpenVix 5.0.020? The tuner settings are the same. For me it cannot be a hardware faillure. Did you change the coding of the tuner settings?

These are the setting on my box under 5.0.020 and also manually under 5.0.026 done.

Tuner A: nothing configures (loop through to tuner B)
Tuner B:
Configuration mode simple
Mode DISEEqc A/B
Port A 13.0E Eutelsat HB
Port B 19.2E Astra
Send voltage 22Khz yes
Send Disecq only on sat change no


Please reconsider your conclusion.
Thanks a lot
nekrub2

How can you have two tuner configs for one tuner? "Not configured/nothing connected" and also "loop through"?

Attach your settings file here. You will need to zip it before you can attach it.

[ronand]

Those channels work fine for me on my solo2 (Vix 5.0.025/026) on a motorised system so it is definitely something with your installation. The PAT is not part of the image or on the receiver - it is the Program Association Table containing the PIDs of the channels on a transponder (it comes from the satellite). The error you are getting means the receiver cannot read the data. Apart from the possibility of a switch issue it may be a faulty lnb or an alignment issue etc. The only part of the image that could affect it are the drivers but these are provided by VU not the openvix team. New drivers were released recently but they were not in .025 so this is not your problem.