Venton unibox ABM tune failed

[reeves1985]

I'm not a noob so have had this working perfect before.
I've updated my image on my receiver in this instance using open atv 6.1 latest build 18/11/17

But for some reason abm just keeps giving tune failed
Failed to tune virgin on tuner.
It gives it for both tuners if one or the other is disabled.
I have my net id 40963 in correct but it just won't work.

I know I can receive the channels fine for example a normal scan pulls the channels in on both tuners and I can view channel 4 for example.

But yet abm just keeps giving me this time failed error.

Any help?

[abu baniaz]

Attach your lamdedb files

[abu baniaz]

Please also attach logs as per this thread

http://www.world-of-satellite.com/showthread.php?44783-Please-read-before-raising-ABM-support-questions

[reeves1985]

Please also attach logs as per this thread

http://www.world-of-satellite.com/showthread.php?44783-Please-read-before-raising-ABM-support-questions

Thanks for the quick reply
I'll add the logs and lamedb later as I've just gone out now
3 hours of head scratching
Been trying all net ids thinking I'm going mad!

I'm in Doncaster if that helps which doesn't have a dedicated net id but a few years back the net id in a official receiver was 40963 which has worked fine ever since.

The old box image running on another receiver I have works fine on that net id as well as I haven't got around to updating that one yet

[abu baniaz]

Get logs from both please.

[reeves1985]

Get logs from both please.


Will do I'll grab them this afternoon

[reeves1985]

Get logs from both please.

Here's the lamedb file

Other logs to follow
55340

[reeves1985]

debug log attached also now
55341

[reeves1985]

I'm not quite sure what to try next as like I say it was working fine until I upgraded the image today.

[abu baniaz]

You said one receiver works, the other does not. I asked you for both logs.

Are you removing one and plugging the same wire into the other one? Or are you using a splitter and different cabling?

Your log shows this


'FE_READ_STATUS', potential driver issue, 145ms

[reeves1985]

sorry the other image is an old openvix image I didn't realise you wanted the logs from that as the abm version is still prior to these pid hacks and works fine.
I'm using the same cable whilst updating the receiver yes. I also know that this receiver is clearing the channels fine and I can scan the channels in fine and actually watch them. so I know there is no issue with the tuners.

it just wont run abm

[reeves1985]

55342

heres the lamdb file from the other receiver.
ill have to grab the log later as its not enabled for debug logs and the mrs is watching something

[reeves1985]

Here's the debug log from the old vix image on the other receiver
Running the old abm which works fine

55343

[reeves1985]

I'm going to try to transfer the older abm from the working receiver to the one that won't work and see if it will run a scan.

At least if it does then we know the problem isn't the image or receiver
Although the receiver was working fine this morning with the older abm so I wouldn't have thought it could be that

[reeves1985]

Well that didn't work either
Still gives the same similar error although the older abm shows
Tune failed fatal

Grrrr

[abu baniaz]

The tuning frequency for your area in ABM has not changed. ABM on UK cable will work on any active frequnecy.

You are not answering questions, and I don't believe you are doing things in a methodical manner. When you are finished doing your tests, and want to get to a solution/diagnosis, please say so. I have better things to do.

[reeves1985]

The tuning frequency for your area in ABM has not changed. ABM on UK cable will work on any active frequnecy.

You are not answering questions, and I don't believe you are doing things in a methodical manner. When you are finished doing your tests, and want to get to a solution/diagnosis, please say so. I have better things to do.

sorry my man.

I'm ready for help. appreciate your busy I'm just trying to get up and running again.

[abu baniaz]

<496459.173> [eDVBFrontend] tuning to 595000 khz, sr 6952000, fec 3, modulation 3, inversion 2
<496459.678> [ABM-main][checkTunerLock] TUNING
<496459.783> [ABM-main][checkTunerLock] ACQUIRING TSID/ONID
<496459.972> [ABM-Manager][read] Reading cable_uk_virgin (hd_40963_dvbc_uk)...

Your problem is going to be signal related

[abu baniaz]

Are both receivers connected?

This troublesome receiver, how many tuners does it have?
Is signal wire connected to all cable tuners?

[reeves1985]

Right thanks for that.

Now I have to work out what's changed in relation to the signal from this morning. As nothing else has changed other than the image.

That's what's causing me concern because I can scan in the channels fine. But as you say if it's signal related the res an issue somewhere

[reeves1985]

Are both receivers connected?

This troublesome receiver, how many tuners does it have?
Is signal wire connected to all cable tuners?

It's a twin tuner venton inbox HD eco
The tuner is a twin 1 module with loop through on the back.

I have tried with just one receiver connected and also both

I've also tried by disabling one tuner and also by switching the cable inputs on the back so it uses the other tuner

[abu baniaz]

I don't follow. Do you have two single tuner cards or two twin tuner cards?

[reeves1985]

I don't follow. Do you have two single tuner cards or two twin tuner cards?

sorry the venton unibox hd eco is a twin tuner receiver.

[reeves1985]

The main signal feed goes into the input and then is looped from the output to the input on tuner B

[abu baniaz]

If you flash a different image, the drivers may be different.

Back to the questions, are both receivers connected at the same time? I m not interested in the past, only the present state.

[lincsat]

Have you tried doing a manual cable scan, not ABM, to check the tuner/signal. You can do the full scan or just select some of the frequencies from the lamedb off the working receiver

[reeves1985]

At the present time yes both are connected at the sane time.

[reeves1985]

Have you tried doing a manual cable scan, not ABM, to check the tuner/signal. You can do the full scan or just select some of the frequencies from the lamedb off the working receiver

Yes I've done a full manual scan and pulling all channels in fine.
Clearing the FTA fine also manual scan finds channels also.

[reeves1985]

Also it's showing full signal

On the atv image there is also a cable scan section
But that fails which is strange.

This is a separate menu to the standard auto and manual scan within the service searching menu on the atv image

[abu baniaz]

Set your tuner A as "UK, Virgin all areas"
Set your tuner B as "UK, Virgin all areas"

Go into signal finder and see if you get a lock on 595000, Qam 64 on tuner A. Post a screenshot.
Go into signal finder and see if you get a lock on 595000, Qam 64 on tuner B. Post a screenshot.

[reeves1985]

Set your tuner A as "UK, Virgin all areas"
Set your tuner B as "UK, Virgin all areas"

Go into signal finder and see if you get a lock on 595000, Qam 64 on tuner A. Post a screenshot.
Go into signal finder and see if you get a lock on 595000, Qam 64 on tuner B. Post a screenshot.

Bare with me I'll do that in a minute

[reeves1985]

I think this is what you were wanting

5534455345

[abu baniaz]

Sorry, I should have said, use "predefined" instead of user "defined". Should also be 6952, not 6900.

Please save my neck. There is a screenshot guide in my signature if you need it.

[reeves1985]

Lock on both tuners

hopefully ive attached the screenshot right this time

5534655347

[abu baniaz]

I hope you agree that looks better.

Issue this command (guide in signature if you need it)



init 4 && sleep 10 && rm -rf /etc/defaultsat.tar.gz && rm -rf /etc/enigma2/lamedb* && rm -rf /etc/enigma2/*.tv && rm -rf /etc/enigma2/*.radio && rm -rf /etc/enigma2/*.del && init 3


Then do following please
go back into satfinder,
select the same frequency as above,
green to scan,
restart,
then attach the lamedb file again.


Also, are you on last night's OpenATV image?

[reeves1985]

I hope you agree that looks better.

Issue this command (guide in signature if you need it)



init 4 && sleep 10 && rm -rf /etc/defaultsat.tar.gz && rm -rf /etc/enigma2/lamedb* && rm -rf /etc/enigma2/*.tv && rm -rf /etc/enigma2/*.radio && rm -rf /etc/enigma2/*.del && init 3


Then do following please
go back into satfinder,
select the same frequency as above,
green to scan,
restart,
then attach the lamedb file again.


Also, are you on last night's OpenATV image?

Yes I am on the last night's openatv image

I'll issue those commands now

Can you tell me what they will do as I want to learn as much as possible

[abu baniaz]

That is going to clear all your channel data, including the default bouquets OpenATV forcibly install.

Once you scan the frequency, I know your lamedb only has the values of that frequency.

[reeves1985]

I issued the command but I can't seem to find 595 now in the pre defined section

[reeves1985]

55348

I think this is the correct log

[reeves1985]

Ignore that yoi want the lamedb file
55349

[abu baniaz]

your lamedb contains more than one frequency

[abu baniaz]

It turned out to be the drivers in latest images. They have 20161207

We got the 20160128 drivers and replaced them, ABM worked fine. The linuxdvb.ko file must have 755 properties and goes in /lib/modules/3.14.21/extra

[reeves1985]

here's the files Abu.

I cannot thank you enough I would have been screwed without your help as its not a massively popular receiver

55350

[alanmek]

I will extend my thanks to Abu aswell, I had the same problem and changing these drivers fixed!