you need to update your whooshbuold to v6 as that uses autobouquetmaker 2.8. Details on how to do this can be found on the tech kings forums.
Posts by tsjarlie
-
-
I have changed frequency that ABM uses for tuning to 299000 as it was common between your lamedb and. Please update the provider/config file and run ABM again
If on OpenViX, you must be on 5.0 028 otherwise you will get the 2.8 version error.
If on OpenATV, it must be newer than 14th September
Hi Abu, I am having the same issue as previously mentioned. Based in Reading 13 area and all channels scanning fine on auto scan but ABM returning "Tuning failed fatal" message. How exactly can I resolve this issue? I am using the ZGEMMA H1 btw
Are you running openatv? You need to run software update to make sure you are on the latest version of autobouquetmaker (2.8) Then just run update config from within abm and you then should be able to do a scan.
-
I have changed frequency that ABM uses for tuning to 299000 as it was common between your lamedb and. Please update the provider/config file and run ABM again
If on OpenViX, you must be on 5.0 028 otherwise you will get the 2.8 version error.
If on OpenATV, it must be newer than 14th September
Config file updated and channel bouquets downloaded. All looks good. I will monitor it over the weekend and see how it goes.
Thank you for all your help.
-
not sure which files should be copied. I thought it was a .tv file but that's just a guess
-
please that would be a great.
-
Reading 00013 as is a friend of mine and both using the h5.2tc
-
Is it because the frequency the bouquets are transmitted on is not locking on?
-
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.
-
a friend of mine has the same box and has the same problem also. Started for both of us on Friday or saturday
-
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.
-
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.
-
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"
-
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.