View Full Version : [ABM-DVB-C] Not configured on Edision OS Mega
Hi i have an edision os mega, just switched on the box now and it says Tune Failed
So i deleted the bouquets and done an automatic scan. Found all the channels both sly and virmin
Check my netid and area on tuner config and abm - all ok
When i start scan it says my tuner has not been configured
I updated the config files using the menu and it say sly needed updating but not vm
I dont think vm have changed the frequency because i can see it on the "last scanned" bouquet
It sounds more like an ABM issue
Anyone else experiencing similar problems since the morning
Thanks
Minesh
abu baniaz
16-12-17, 14:39
please attach your log
please attach your log
thanks for the reply, please see abm.log
55542
Andy_Hazza
16-12-17, 15:13
Tuner not configured is not update config files, it means your tuner(s) haven’t been configured so go into your Tuner Configuration menu & setup your tuners correctly.
Sent from my iPhone using Tapatalk
abu baniaz
16-12-17, 15:17
[ABM-config] providers: cable_uk_virgin:hd_40979_dvbc_uk:45:|sat_282_sky_u k:sdcustom_london:37:
Your log shows doing Sky on its own works.
A. Please attach your lamedb and lamedb5 files. They are in /etc/enigma2/ You will need to zip them before you can attach them.
B. Please post a screenshot of your Device information page. (Menu > Information > About) A guide to screenshots is in my signature if you need it.
C. Please check with the failed tuner that you get a lock on the frequency specified for 40979. Use manual scan or signal finder. The onscreen failure message should tell you which tuner it is failing on.
frequency="411000"
symbol_rate="6952000"
modulation="3" (Qam64)
A screenshot showing the lock would be better.
D. Which image version are you using?
[ABM-config] providers: cable_uk_virgin:hd_40979_dvbc_uk:45:|sat_282_sky_u k:sdcustom_london:37:
Your log shows doing Sky on its own works.
A. Please attach your lamedb and lamedb5 files. They are in /etc/enigma2/ You will need to zip them before you can attach them.
B. Please post a screenshot of your Device information page. (Menu > Information > About) A guide to screenshots is in my signature if you need it.
C. Please check with the failed tuner that you get a lock on the frequency specified for 40979. Use manual scan or signal finder. The onscreen failure message should tell you which tuner it is failing on.
frequency="411000"
symbol_rate="6952000"
modulation="3" (Qam64)
A screenshot showing the lock would be better.
D. Which image version are you using?
555435554455545
Thats correct I have turned of vm from the providers option because it doesn't work. If you like i can turn it back on and post a new log
Thanks for your continued support
Minesh
abu baniaz
16-12-17, 16:07
You have not answered the question about getting a lock.
My nephew is using the PC, I'll have a look at the lamedb files later. All your frequencies that the scan found sre in there. We can then amend the one used for ABM if required.
55546
Apologies mate, I missed that bit
Does that screenshot help?
abu baniaz
16-12-17, 16:36
You have not checked the specified frequency. 411 MHz
You are doing it correctly. just scroll until you get to 411, qam 64
You have not checked the specified frequency. 411 MHz
You are doing it correctly. just scroll until you get to 411, qam 64
Thanks very much for your help mate
I done a manual scan and then ran ABM, worked perfectly got my bouquets back for vm now
Minesh
abu baniaz
16-12-17, 17:22
Can you attach your current lamedb files again please. The one after a successful ABM scan.
Posting the section below for reference purposes only.
<?xml version="1.0" encoding="UTF-8"?>
<cables>
<cable name="PROVIDER NAME HERE" satfeed="true" flags="9">
<transponder frequency="115000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="123000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="131000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="347000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="355000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="363000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="371000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="443000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="451000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="459000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="467000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="475000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="523000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="531000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="571000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="579000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="587000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="627000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="667000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="675000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
<transponder frequency="683000" symbol_rate="6952000" fec_inner="3" modulation="5"/>
</cable>
</cables>
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.