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.
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.
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.
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
Last edited by abu baniaz; 02-11-17 at 22:16.
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?
Think I've got it sorted now, deleted the bouquet and rescanned and seems ok. Much appreciated.
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.
lamedb.ziplamedb5.zip
Abu lamedb files attached as requested hope this is what you are after
VU+Duo2 5.2.025
abu baniaz (04-11-17)
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
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
Last edited by lincsat; 05-11-17 at 13:47.
samsid (05-11-17)
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.
I suspect that eventually all transponders will use QAM256 M8, ABM runs fine on a QAM256 transponder, you may want to consider using that.
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
samsid (06-11-17)