PDA

View Full Version : [ABM-MISC] BoxNation SD new frequency


maxben
20-04-17, 11:20
11344 h 27500 5/6 qpsk
abu baniaz
20-04-17, 11:26
Is ABM not finding it? If so, attach debug log. Found it yesterday for me, albeit used the number until I zapped to it.
maxben
20-04-17, 13:01
Hmm, It finds it with a fresh setup but not when mixed with my own non ABM bouquests.

I'll have to investigate further.
abu baniaz
20-04-17, 13:11
It finds it with an old setup too. There is a bug with ABM/Enigma2 where a channel in test mode keeps its name (number) when ABM adds it to a bouquet.

Do you know why people are reluctant to add debug logs for ABM issues?
maxben
20-04-17, 13:23
Dunno if your last comment is a dig at me for not adding debug log but I assumed as I'm not using a pure ABM setup no one would be interested.

After performing a normal full scan on 28.2 BoxNation then shows in ABM bouquets.
dsayers
20-04-17, 14:49
Your log is empty
maxben
20-04-17, 15:02
Your log is empty

How odd, not empty when I d/l it

....anyway try again
dsayers
20-04-17, 15:15
So are you overwriting the channel? you say your own mix is that via a custommix? if so a can you upload it
maxben
20-04-17, 15:33
No custommix on that scan.

I'm pretty sure I know what the the problem is now - I use vhanibals ready made motorised list customised to my own liking and with my own additions and ABM scan on top.

In this vhanibals list is his scan of 28.2 which quite old now and is conflicting with the ABM scan, I'm pretty sure now that if I remove the 28.2 from the the original list then the ABM scan will be fine.
abu baniaz
20-04-17, 16:22
The problem from what I have discovered is that a channel enters the dvb system as test channel, i.e not assigned to the bouquets. It normally is just named the service number.

When the channel becomes a proper channel and the tables change, ABM uses the new channel. E2 seems to maintain the old name. When you zap to a channel, that should sort it out. A reboot also seems to iron out this quirk. Failing that, select channel, manual scan of the transponder with clear before scan enabled also makes the new name take effect. The issue manifest itself with the seasonal renames more often.

For example

Lamedb has this


08ff:ffff0000:0017:f020:25:0
Sky Hits HD
p:Unknown,C:0000


Bouquet file has this


#SERVICE 1:0:19:8ff:17:f020:ffff0000:0:0:0:


Manual scan with clear causes a delete and N/A appears instead of fast and furious. Run ABM again and voila we have Sky Hits HD