PDA

View Full Version : [ABM-DVB-T/T2] Heathfield ABM says Failed to tune FreeView



obtutus
24-07-18, 18:41
After problems on my MB Premium Twin+ I thought I'd try a Mutant HD51 but that's giving me different problems! :confused:

Basically the automatic scan works and picks up all the expected FreeView channels.
I've set up ABM for FreeView and my area 'Heathfield'.
I updated the config files via the menu too.
Then I run the ABM scan but it always says Failed to tune Freeview.
Don't understand that as the box is obviously picking up all the channels.
The log says TUNING FAILED FATAL.
I've not installed a hard drive yet but don't think that should be a problem?
I've updated to the latest version of OpenVix (5.0.31) as box was a couple of versions out of date.

Can anyone point at what I am doing wrong or what I can do to fix this please?

Thanks!

obtutus
24-07-18, 20:25
I meant Openvix 5.1.031 of course!

obtutus
24-07-18, 21:12
Attached a debug log 57135

abu baniaz
25-07-18, 00:21
Your debug log does not show you running ABM. Can you please check and re-upload. A copy of your lamedb file would be helpful too.

obtutus
25-07-18, 07:30
Your debug log does not show you running ABM. Can you please check and re-upload. A copy of your lamedb file would be helpful too.

Sorry I managed to select the wrong log file! I wasn't having a good night last night :o

I'll try again when I get home this afternoon :p

Huevos
25-07-18, 10:32
Ok, first things first.


Open signal finder (Menu > Setup > Tuner config > Signal finder).
Select a terrestrial tuner.
Check you have signal on 722 MHz (Channel 52).
Do the same check on all terrestrial tuners (if your box has more than one).
Post your results.



57139

obtutus
25-07-18, 18:24
Hopefully I've done it right today!

obtutus
25-07-18, 18:32
Ah, this may be the problem. I'm not getting anything on CH52. BBC1 seems to be on CH32 which doesn't seem to tie up with any transmitter data I can find at the moment. :confused:

Ok found this this which seems to be right http://www.digitaluk.co.uk/coveragechecker/main/trade/TN21+0UG/NA/0/NA.

Looks like the recent FreeView shuffle has mucked things up? I guess the XML file needs updating. I could try that myself :D

Huevos
25-07-18, 19:40
Update to build 032.
Download TerrestrialScan from the feeds (in SystemPlugins).
Run TerrestrialScan (it is in tuner config menu).
In the menu tell it to create a terrestrial bouquet.
Post the debug log.
Check the bouquet works properly.



Once we have the log it should be easy for us to fix ABM for all users.

obtutus
25-07-18, 19:40
I've update the XML and it seems to work OK for me. I've attached for your perusal.
Thanks for nudging me in the right direction Huevos! :thumbsup:

obtutus
25-07-18, 20:07
Update to build 032.
Download TerrestrialScan from the feeds (in SystemPlugins).
Run TerrestrialScan (it is in tuner config menu).
In the menu tell it to create a terrestrial bouquet.
Post the debug log.
Check the bouquet works properly.



Once we have the log it should be easy for us to fix ABM for all users.

Done and attached :thumbsup:

Huevos
25-07-18, 21:25
https://github.com/oe-alliance/AutoBouquetsMaker/commit/8adb55ad8ae4ddfe4e0648b1522bf08a214a3c95

Just pull the updated config file and check it works.

obtutus
26-07-18, 19:01
https://github.com/oe-alliance/AutoBouquetsMaker/commit/8adb55ad8ae4ddfe4e0648b1522bf08a214a3c95

Just pull the updated config file and check it works.

Sorry I can't get your version to fully work. Some channels won't tune in when selecting them.

I've updated mine again as I'd got some of the custom transponders wrong and everything seems to work OK for me.
I've attached the latest in case it helps anybody.
Thanks again.

Huevos
27-07-18, 01:15
Can you post the debug log of your ABM scan, with extra debug enabled.

obtutus
27-07-18, 14:58
Can you post the debug log of your ABM scan, with extra debug enabled.

I did this log using my xml, if you want it with yours let me know.

abu baniaz
27-07-18, 17:01
If you use Skype, can you please PM me your username

abu baniaz
27-07-18, 18:51
Sorry, had to pop out.

I have updated the file used by ABM to include the transponders from your lamedb. Please update provider and try again

Huevos
27-07-18, 23:50
Looking at your debug log the only custom transponders that are necessary for you are 634, 658, and 682. Please delete the redundant ones and confirm this works for you.

obtutus
28-07-18, 17:47
Looking at your debug log the only custom transponders that are necessary for you are 634, 658, and 682. Please delete the redundant ones and confirm this works for you.

Sorry, that didn't quite work. It thinks channels KMTV, Sony Movie, Sony Movie+1 and truTV are on CH21 474MHz, but they aren't.
I put 618 back in and then everything worked. I think that was because I had mucked that one up in the first place.

Huevos
28-07-18, 20:59
So needed is 618, 634, 658, and 682 right?

obtutus
29-07-18, 09:38
So needed is 618, 634, 658, and 682 right?

Yes, that's what I've got.

I've noticed that 618 CH39 gives me very poor reception and breaks up. I don't know whether that means I'm picking that up from another transmitter? Not sure how to tell.

ccs
29-07-18, 10:27
Tune to the channel and then press ok twice, it will show you the mux frequency.

Huevos
30-07-18, 11:45
618 is not documented as a Heathfield frequency. Could be Tunbridge Wells. Give it a few days and I'll post some code to try to work out the correct muxes for you.