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.
Page 3 of 4 FirstFirst 1234 LastLast
Results 31 to 45 of 55

Thread: ABM 2.8 Failed to tune NET ID 00016

  1. #31

    Title
    Member
    Join Date
    Apr 2011
    Posts
    96
    Thanks
    19
    Thanked 7 Times in 6 Posts
    ABM still not working, scanned in 606 channels and quickly looking at BBC HD and ITV HD they now work, frequency has changed from before when it didn't work from 635hz to 387hz.

  2. #32
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,338
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    Why would you expect ABM to work? Nothing had changed in ABM.

    I have just updated the file on GitHub. Update config file and then try ABM again.

  3. #33
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,338
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    Note to self

    Code:
    t:ffff0000:002a:f020,c:371000:6887000:2:3:3:0:0
    t:ffff0000:002d:f020,c:379000:6887000:2:3:3:0:0
    t:ffff0000:0068:f020,c:387000:6887000:2:3:3:0:0
    t:ffff0000:0001:f020,c:395000:6887000:2:3:3:0:0

  4. #34

    Title
    Member
    Join Date
    Apr 2011
    Posts
    96
    Thanks
    19
    Thanked 7 Times in 6 Posts
    Thanks for that, updated the cfg and its scanning 399 channels which is great, but call me a bit thick for the life of me I can't seem to arrange the bouquet other than alphabetical, I had it in sections before ie movies, sports etc, I haven't adjusted any other settings and the hide sections in ABM has nothing checked, any ideas?

  5. #35

    Title
    Member
    Join Date
    Apr 2011
    Posts
    96
    Thanks
    19
    Thanked 7 Times in 6 Posts
    Think I've got it sorted now, deleted the bouquet and rescanned and seems ok. Much appreciated.

  6. #36
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,338
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    Can someone in a pure area that has not yet been affected check if they get signal on the freqencies listed in post 33 please? Use signal finder.

  7. #37
    khan888's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Dec 2011
    Location
    Nottingham
    Posts
    562
    Thanks
    755
    Thanked 214 Times in 102 Posts
    Quote Originally Posted by abu baniaz View Post
    Can someone in a pure area that has not yet been affected check if they get signal on the freqencies listed in post 33 please? Use signal finder.
    I’m getting a signal on all those frequencies and I’m in a pure area


    Sent from my iPhone using Tapatalk
    Octagon SF4008 (1tb hdd - Openvix 5.1) Edision Combo (8gb USB - Openvix 5.1)

  8. #38

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    676
    Thanks
    56
    Thanked 234 Times in 161 Posts
    Quote Originally Posted by abu baniaz View Post
    Can someone in a pure area that has not yet been affected check if they get signal on the freqencies listed in post 33 please? Use signal finder.
    Getting a signal in 00008, all using 6887/256QAM. I believe previously all 6887 were 64 QAM, 643 Mhz does remain at 64 QAM

  9. #39

    Title
    Forum Supporter
    Donated Member
    Join Date
    Sep 2010
    Posts
    793
    Thanks
    360
    Thanked 216 Times in 134 Posts
    lamedb.ziplamedb5.zip

    Abu lamedb files attached as requested hope this is what you are after
    VU+Duo2 5.2.025

  10. The Following User Says Thank You to Alanp For This Useful Post:

    abu baniaz (04-11-17)

  11. #40
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,338
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    We have pre-emptively moved the pure areas that were on 643000 to 387000. If updating the config file doe snot resolve the locking error, please perform a conventional scan (don't use ABM) and attach the lamedb files.

    The commit has been reversed.
    Last edited by abu baniaz; 05-11-17 at 15:32. Reason: Commit reversed

  12. #41

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    676
    Thanks
    56
    Thanked 234 Times in 161 Posts
    You have moved the frequency but not changed the QAM M8, ABM scans now fail in 00008 unless the modulation is changed to 5

    EDIT: Added newly scanned lamedb
    Attached Files Attached Files
    Last edited by lincsat; 05-11-17 at 13:47.

  13. The Following User Says Thank You to lincsat For This Useful Post:

    samsid (05-11-17)

  14. #42
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,338
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts
    I have reverted the last commit.

    We use QAM 64 (modulation 3) for ABM cable. Your current frequencies with QAM64 are

    Code:
            <transponder frequency="619000" symbol_rate="6887000" fec_inner="3" modulation="3"/>
            <transponder frequency="627000" symbol_rate="6887000" fec_inner="3" modulation="3"/>
            <transponder frequency="635000" symbol_rate="6887000" fec_inner="3" modulation="3"/>
            <transponder frequency="643000" symbol_rate="6887000" fec_inner="3" modulation="3"/>

    People in areas that change will have to provide lamedb files after perform a non-ABM scan.

  15. #43

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    676
    Thanks
    56
    Thanked 234 Times in 161 Posts
    I suspect that eventually all transponders will use QAM256 M8, ABM runs fine on a QAM256 transponder, you may want to consider using that.

  16. #44
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,338
    Thanks
    6,422
    Thanked 9,146 Times in 6,224 Posts

    ABM 2.8 Failed to tune NET ID 00016

    All areas have both, they always have.

    If they were going to get rid of them, they would have done so in the changes. The recent changes seem to be more of a symbol rate change.

    The data transmissions are on 64Qam. If you inspect the lamedb5, this will be more apparent as you can see the device updates.

    We will not be changing it.

  17. #45

    Title
    ViX Beta Tester
    Join Date
    May 2011
    Posts
    676
    Thanks
    56
    Thanked 234 Times in 161 Posts
    Quote Originally Posted by abu baniaz View Post
    All areas have both, they always have.

    If they were going to get rid of them, they would have done so in the changes. The recent changes seem to be more of a symbol rate change.

    The data transmissions are on 64Qam. If you inspect the lamedb5, this will be more apparent as you can see the device updates.

    We will not be changing it.
    They always have had both - so far!

    I suspect they will change eventually to cram in more data per transponder. I can confirm that ABM works fine on a 256QAM transponder and data is present on the 256QAM transponders.

    I'm not telling you to use a 256QAM transponder, just suggesting as they are less likely to change again. I have updated the custom file I use

  18. The Following User Says Thank You to lincsat For This Useful Post:

    samsid (06-11-17)

Page 3 of 4 FirstFirst 1234 LastLast

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.