I have a brand new Zgemma H5.2TC and i installed Openatv 6.0 and at first Autobouqestsmaker worked perfectly however it now fails with error: tuning failed fatal so to check that the box is working ie Tuner i did a manual scan and it picks up all the channels and i can't understand what's changed to cause this. I have another box the Zgemma H2 and that's working perfectly. I 've tried re flashing with 3 different images and still get the same result.
Autobouqetsmaker error: tuning failed fatal
-
- AutoBouquetsMaker
- be6_2
- Thread is marked as Resolved.
There are 61 replies in this Thread which was already clicked 15,828 times. The last Post () by abu baniaz.
-
-
I have the exact same problem, I'm running openatv 6.1. A friend of mine is running Whooshbuild v6 and has the same problem.
I can also pick up channels after a manual scan but they arent in order.
-
Check the provider xml file for the frequency your area uses. In signal finder, check that you get a lock on all tuners for that frequency.
-
I just tried and signal is locking on for both tuners.
configuration i used, <configuration key="hd_00013_dvbc_uk" netid="00013" bouquettype="hd" frequency="643000" symbol_rate="6887000"
-
Someone else in Reading has posted similar problem.
Backup your lamedb to your PC. Found in /etc/enigma2/
Stop enigma2 with "init 4" command
Delete lamedb
Restart
Scan cable only
Restart
Attach this new lamedb and lamedb5 file here. It will be used to update the provider file with a different frequency.
-
I deleted lamedb, rebooted and scanned dvbc only. I unchecked network scan just before. The scan found only 180 channels so I'm not sure why
I rebooted again and have attached both files.
If it's wrong I'll try again tomorrow.
-
Will give that a look in the afternoon, thanks
-
I think there is a signal issue in your area. Best to check on official receiver/website. You have only found channels on 15 frequencies. You can edit the provider file in ABM, and ABM will work, but you will still have issues on the other frequencies.
CodeeDVB services /5/ # Transponders: t:dvb_namespace:transport_stream_id:original_network_id,FEPARMS # DVBC FEPARMS: c:frequency:symbol_rate:inversion:modulation:fec_inner:flags:system
t:ffff0000:0006:f020,c:699000:6952000:2:5:3:0:0t:ffff0000:0007:f020,c:707000:6952000:2:5:3:0:0
t:ffff0000:0008:f020,c:715000:6952000:2:5:3:0:0
t:ffff0000:0009:f020,c:723000:6952000:2:5:3:0:0
t:ffff0000:001a:f020,c:747000:6952000:2:5:3:0:0
t:ffff0000:001b:f020,c:755000:6952000:2:5:3:0:0
t:ffff0000:0022:f020,c:667000:6952000:2:5:3:0:0
t:ffff0000:0023:f020,c:675000:6952000:2:5:3:0:0
t:ffff0000:0024:f020,c:683000:6952000:2:5:3:0:0
t:ffff0000:0025:f020,c:691000:6952000:2:5:3:0:0
t:ffff0000:0026:f020,c:651000:6952000:2:5:3:0:0
t:ffff0000:0027:f020,c:659000:6952000:2:5:3:0:0
t:ffff0000:0065:f020,c:603000:6952000:2:5:3:0:0
t:ffff0000:0066:f020,c:611000:6952000:2:5:3:0:0
t:ffff0000:3ad7:0001,c:339000:6952000:2:5:3:0:0
-
I'm in Reading and my H2H is working but not the H5.2TC
Update it's stopped working to.
-
Display More
I think there is a signal issue in your area. Best to check on official receiver/website. You have only found channels on 15 frequencies. You can edit the provider file in ABM, and ABM will work, but you will still have issues on the other frequencies.
CodeeDVB services /5/ # Transponders: t:dvb_namespace:transport_stream_id:original_network_id,FEPARMS # DVBC FEPARMS: c:frequency:symbol_rate:inversion:modulation:fec_inner:flags:system
t:ffff0000:0006:f020,c:699000:6952000:2:5:3:0:0t:ffff0000:0007:f020,c:707000:6952000:2:5:3:0:0
t:ffff0000:0008:f020,c:715000:6952000:2:5:3:0:0
t:ffff0000:0009:f020,c:723000:6952000:2:5:3:0:0
t:ffff0000:001a:f020,c:747000:6952000:2:5:3:0:0
t:ffff0000:001b:f020,c:755000:6952000:2:5:3:0:0
t:ffff0000:0022:f020,c:667000:6952000:2:5:3:0:0
t:ffff0000:0023:f020,c:675000:6952000:2:5:3:0:0
t:ffff0000:0024:f020,c:683000:6952000:2:5:3:0:0
t:ffff0000:0025:f020,c:691000:6952000:2:5:3:0:0
t:ffff0000:0026:f020,c:651000:6952000:2:5:3:0:0
t:ffff0000:0027:f020,c:659000:6952000:2:5:3:0:0
t:ffff0000:0065:f020,c:603000:6952000:2:5:3:0:0
t:ffff0000:0066:f020,c:611000:6952000:2:5:3:0:0
t:ffff0000:3ad7:0001,c:339000:6952000:2:5:3:0:0
I ran the scan again and it's picked up the usual 600 or so channels.
New lamedb files attached.
-
Display More
Someone else in Reading has posted similar problem.
Backup your lamedb to your PC. Found in /etc/enigma2/
Stop enigma2 with "init 4" command
Delete lamedb
Restart
Scan cable only
Restart
Attach this new lamedb and lamedb5 file here. It will be used to update the provider file with a different frequency.
Ok, sorry for being so late following your instructions please find attached my files. The scan found 596 Channels, I'm in Reading and my H2H is working but not the H5.2TC
-
If one works and the other does not, there is going to be a signal issue. The tuners have different sensitivities. Check cabling, splitters etc.
Another simple check is to swap the receivers over.
-
If one works and the other does not, there is going to be a signal issue. The tuners have different sensitivities. Check cabling, splitters etc.
Another simple check is to swap the receivers over.
I've swapped the boxes and in both rooms i get the tuning failed fatal error on the H5.2TC, as i mention in my first post when i first set it up Autobouqestsmaker worked then all of sudden it stopped working and gave the tuning failed fatal error. I'll keep plugging away at it
-
a friend of mine has the same box and has the same problem also. Started for both of us on Friday or saturday
-
Post a screenshot of signal finder locking onto 643000 MHz on all tuners please.
-
Post a screenshot of signal finder locking onto 643000 MHz on all tuners please.
Are you asking me to do this?
-
I am getting a lock on all but 6 frequencies with 643000 being one of them.
I can however watch all channels after doing an automatic tune. They are just mixed up with loads of other channels that don't normally get picked up by autobouquetmaker.
-
Just ran Autobouqetsmaker on three boxes and now getting tuning failed fatal on all of them now, an edison os mini combo, Zgemma H5.2TC and H2 really don't understand what's going on as it was working yesterday on all the boxes except the H5.2TC before today.
update on Net ID 13 Reading it would appear that it's not just me having this problem a mate with Zgemma H2H is having the same issues
I am getting a lock on all but 6 frequencies with 643000 being one of them.
I can however watch all channels after doing an automatic tune. They are just mixed up with loads of other channels that don't normally get picked up by autobouquetmaker.
What Net Id are you on mate?
-
Is it because the frequency the bouquets are transmitted on is not locking on?
-
Is it because the frequency the bouquets are transmitted on is not locking on?
Whats your NET id mate
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!
