View Full Version : [VU+ Solo2] Update 5.0.023 all stations black - timeout PAT
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
16-07-17, 16:28
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
16-07-17, 17:50
Working fine on my Vu+ Solo2 here also.
Sent from my iPhone using Tapatalk
My solo2 is working fine on 5.0.023
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
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.
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
13-08-17, 21:09
Maybe a diseqc switch issue.
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
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
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
09-09-17, 21:54
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.
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
10-09-17, 17:37
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.
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.
Tuner A settings are not relevant. There is noting attached to tuner a. So whether I set nothing or look-through to be should have no impact.
This is really strange. For the time being I will stick to OpenVix 5.0.020.
Thanks anyway
nekrub2
abu baniaz
11-09-17, 13:38
If the same hardware works in 5.0 020, it cannot be a hardware issue.
Are you not going to attach your settings file?
Hi Ronand
My problem started with version 5.0.021. When I go back to 5.0.020 all is fine and clear.
So I would assume that it is unlikely that the LNB, the adjustment of the dish or the switch are the root cause of the problem.
Maybe the new vu+ tuner driver sends the signal differently now. Strange enough is also that when I stay on a black station and I do a reboot I get it bright.
Do you know where I can read out the vu+ tuner driver version?
I can predict the answer of VU+ support when I would ask them. “use VU+ original firmware”. This would mean I would loose a lot of good stuff built into OpenVix.
Thanks 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.
Hi Abu Baniaz
I am rather a newbee.Can you please tell me how I get the settings for attachment. I have DCC and could copy them out if I knew where the relevant parts were. - Or would you like the whole backup file?
Thanks in advance for your advice.
nekrub2
Dear all
These are the setting files. a) 5.0.20 b) 5.0.026
Hope you can read out something.
Thanks a lot
nekrub2
I got a message after switching to Client mode on my Mutant HD1200 -- It read unable to read PAT then something about Data.
And that was on teh latest update as well. May not be connected at all to your issue but thought I would drop in.
Hi FlyiingPig,
Problems reading PAT in both cased. They could be related - even with different error messages.
Hope that one of the cracks find out what is fishy.
Thanks a lot
nekrub2
abu baniaz
19-09-17, 17:13
Posting for reference purposes only
5.0 020
config.Nims.0.configMode=loopthrough
config.Nims.1.diseqcA=130
config.Nims.1.diseqcB=192
config.Nims.1.diseqcMode=diseqc_a_b
5.0 025
config.Nims.0.configMode=nothing
config.Nims.1.diseqcA=130
config.Nims.1.diseqcB=192
config.Nims.1.diseqcMode=diseqc_a_b
Hi Abu Banjaz
I am confused, on tuner A I manually entered loopthrough. When I have time I will redo a plain installation, writing loopthrough again and check what is written in the settings. I never new that there is an option "nothing". Will report soon.
Thanks nekrub2
Hi Abu Banjaz
There is indeed a bug. When setting up the tuner configuration from scratch and you enter loop through the system stores "none". I tested this today. When you modify this at a later stage it keeps loopthrough. > Nevertheless the problem of time-out on reading PAT stays.
Best regards
nekrub2
new try with 5.0.031
Couch update from 5.020 - same behaviour as described before PAT timeout. Only the startup station is clear. When I change the startup station the new one is clear and all others have time-out. >> So I go back to 5.0.20 which works perfectly well for TV, Hbbtv, Youtube and most plugins.
new try with bulid 5.1.002
USB flashing with 5.1.002 - restore 5.020 settings
Result: Startup channel is clear, when switching to other free channels still PAT time-out.
Conclusion: The bug is obviously not yet fixed. So I go back to 5.0.020.
Manual installation of build 5.1.003 with USB. No settings restored, signal search done and all setup adaptions made.
Good news: no more PAT time-outs.
Small setback: Restore of setting from 5.0.020 was not possible. It toiok me a while until I had all settings and plugins in place.
Anyway - Thanks a lot to the builders of 5.1.003.
nekrub2
Small setback: Restore of setting from 5.0.020 was not possible. It toiok me a while until I had all settings and plugins in place.
That should have worked, what sort of problems did you encounter?
Hi ccs
It said something of a missing directory. Unfortunately I did not activate the log before. But I would not like to retry it now.
Anyway thanks a lot
nekrub2
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.