Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.

View Entry Info: SID not in PAT Error

Category:
Possible Bug
What ViX Image build number are you using?
Please provide your ViX Team image build number. Menu > Information > About > Build number > ENTER THIS NUMBER e.g. 4.2.028
21
Have you tried a flash WITHOUT settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Have you tried a flash WITH settings restore?
Have you tried this? PLEASE SELECT YES OR NO.
No
Attachments
Page 2 of 2 FirstFirst 12
Results 16 to 17 of 17

Thread: SID not in PAT Error

  1. #16

    Title
    Senior Member
    Join Date
    Nov 2010
    Posts
    687
    Thanks
    35
    Thanked 89 Times in 76 Posts
    i think we can declare victory now. the "sid not in pat" tuning error hasn't shown up since i installed 4.0.
    thanks to all who contributed to the fix.

  2. #17
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,335
    Thanks
    6,421
    Thanked 9,146 Times in 6,224 Posts
    Just to update this thread:


    Response to a thread/issue where I was experiencing issues using a Jess/Unicable 2 LNB with conventional tuners.

    The Universal LNB is an analogue device. It starts sending signals down the cable as soon as it is powered.



    The Unicable LNB is a digital device. From a cold start it needs to boot before it can interpret any instructions sent to it by the STB. It has to do this every time power is removed. i.e. every time the tuner stops sending power up the co-ax.


    The Unicable LNB is a communal device. So normally it would have an injection power supply to keep it permanently awake. Even if it didn't have a dedicated power source it would always have some user or other connected, so it would always be powered. That means that any new user coming out of standby would be able to use it instantly.

    In your case you are the only user and you do not have a dedicated power source, so coming out of standby, or coming from a terrestrial channel the LNB has to cold boot. The cold boot is the reason for the brief tune failed message.


    If you had other active devices using the same LNB when you brought your STB out of standby the tune failed message would not display, and the service would be viewable immediately.

    The reason this doesn't happen with the Solo4K is because "ForceLNBPower" means the LNB is permanently powered from the STB even when the tuner is not in use.
    The solution is
    Install satellitequipmentcontrol plugin. It is under system plugins. Installs in service searching menu.

    Change "Delay after enable voltage before switch command".

    1000 ms looks like it should be good for that device.

    Other devices may need less time, so adjust to suit.
    Attached Images Attached Images

  3. The Following User Says Thank You to abu baniaz For This Useful Post:

    Bangord30 (09-01-17)

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.