LEGALFREETOAIR.COM
October 17, 2018, 12:59:35 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: Check out our HD Wildfeed/Backhauls Section >>> http://legalfreetoair.com/index.php?board=66.0
 
   Home   Help Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Receiver scans in wrong channel?  (Read 575 times)
0 Members and 1 Guest are viewing this topic.
jholt5638
Full Member
***
Offline Offline

Posts: 79


« on: October 23, 2017, 10:10:13 AM »

I have a Zgemma H5.AC that was donated to me. It has both a DVB-S2 and ATSC tuners. It works great except one minor glitch. I live in Toledo, OH ( here is the channel list for my area  
Code:
http://www.rabbitears.info/market.php?request=print_market&mktid=90

The Receiver does scan in all the channels with the right call letters/sign however the channels 48-1 to 48-4 (which is Justice, This, COZI, and Antenna TV all show channel 68-1 Daystar. I didn't even notice the problem I thought it was strange to have four channels of Daystar (If I want to watch Daystar I'll pull it down from G19 and not the over compressed video OTA ) I said something to my dad and he told me no the channels on 48 were the above. What would cause a tuner to scan the right channels but show a different channel when trying to tune it in? Something I should report to the manufacturer, or to the Enigma-II developers?
« Last Edit: October 23, 2017, 10:15:37 AM by jholt5638 » Logged
jholt5638
Full Member
***
Offline Offline

Posts: 79


« Reply #1 on: October 23, 2017, 10:50:08 AM »

after looking up the frequency for physical channel 48 and did a manual scan the right channels came in. Looks like a receiver/enigma-II problem. Now to dig in and see why the box is storing the wrong frequency for that channel. Anyone know where/how Enigma stores its auto scan results?
Logged
jholt5638
Full Member
***
Offline Offline

Posts: 79


« Reply #2 on: October 23, 2017, 11:06:37 AM »

Now 68-1 shows 48-1 not sure to make of it
Logged
elbandido
Visiting Mod
LFTA Legend
*****
Offline Offline

Posts: 1773



« Reply #3 on: October 23, 2017, 11:24:41 AM »

Manual scan is what I prefer for ATSC.

Looking at your list in the link, it looks like you may have a couple of low power stations in  your area. Low power tv stations are not required to transmit an unique SID like the high power stations are required to do. This causes problems in enigma2, but they have been solved in some images.

All of your channel information is stored in the etc/enigma2 folder. The main file to be concerned with for this issue would be the lamedb file located in the etc/enigma2 folder. Copy that file from the receiver, zip it and post it. We will see what can be done about fixing it.
Logged
Jeff S.
Honored Member
Hero Member
*****
Offline Offline

Posts: 145


« Reply #4 on: October 24, 2017, 03:00:28 PM »

Just my two cents. Does the box SW eliminate the old channels before it scans for the new ones?

I have seen SW that does not do this function.

Jeff S.
Logged
elbandido
Visiting Mod
LFTA Legend
*****
Offline Offline

Posts: 1773



« Reply #5 on: October 24, 2017, 10:49:27 PM »

Toledo, Ohio has some Low Power Television Stations (LPTV).

Enigma2 allows for old channels to be saved or erased. I attached a screencap showing the manual scan menu and the options it has. I think about every scan menu in enigma2 has the old channel save/delete option. I doubt it matters or helps for this particular problem.

There is an ATSC bug in enigma2. I will explain it briefly:
(1) The FCC requires all tv stations to send an unique Transport Stream Identification number. This is commonly known as a TSID.
(2) The FCC Does Not require Low Power Television Stations or LPTV to send or transmit a TSID.
(3) ATSC in enigma2 is designed to look for a TSID and assign it to the frequency for a channel or group of channels (Transponder Frequency)
(4) When two or more LPTV stations are scanned in the enigma2 receiver that have the exact same TSID, enigma2 logs the channels, but only logs the last transponder scanned.

When two LPTV stations are scanned, the user will see the channel or channels for both stations, but only the channels for the last station scanned will work! This has been a big problem in the past for me because there are several LPTV stations in my area that are transmitting identical TSID's. Hopefully this TSID problem will correct itself when the television stations repack.

I was shown a solution or work-around by manually adding unique TSID's to the ATSC transponders in my area that do not have one. Doing this works well for me, but it does require some patience and lamedb file modifying.

An image modification by SatDreamGr allows for a selection to Ignore DVB namespace sub network. When this setting is set to No, ALL LPTV and other terrestrial stations scan and work correctly for me. The problem is, this selection is not currently available in all images. A screencap is attached showing this selection.
Logged
jholt5638
Full Member
***
Offline Offline

Posts: 79


« Reply #6 on: October 28, 2017, 06:50:32 PM »

yeah that is exactly what is happening which ever channel I scan last is the channel both low power stations have on it. Attached is my lamedb and lamedb5 in a zip
Logged
elbandido
Visiting Mod
LFTA Legend
*****
Offline Offline

Posts: 1773



« Reply #7 on: October 28, 2017, 10:12:48 PM »

Frequencies are referred to as transponders.

You have 6 transponders in this list. Look and see if you get more than that. (Search all of the ATSC transponders using satfinder if needed.)
It looks like only one has been written over, so it would be 7 transponders total for this list. Make sure that is all you can get!


eDVB services /4/
transponders
eeee0000:0001:0000
   a 677000000:2:6:0:0
/
eeee0000:0903:0000
   a 201000000:2:6:0:0
/
eeee0000:0905:0000
   a 213000000:2:6:0:0
/
eeee0000:0907:0000
   a 683000000:2:6:0:0
/
eeee0000:0909:0000
   a 563000000:2:6:0:0
/
eeee0000:090b:0000
   a 665000000:2:6:0:0


The Transport Stream ID (TSID) is in the middle and it is in hexadecimal, so it needs to be converted to decimal for easier reading.

Here is WTVG from your list:
eeee0000:0905:0000
   a 213000000:2:6:0:0
/
Convert 905 Hex to decimal = TSID: 2309 (0x0905)

The first transponder of 677MHz in your list has a TSID of 1, and is probably low power.
eeee0000:0001:0000
   a 677000000:2:6:0:0
/
So you may change it like this:
eeee0000:0002:0000
   a 677000000:2:6:0:0
/
But then you will need to change the channel or channels that are associated with it to the same.

A search of eeee0000:0001 in notepad++ of your lamedb returns these:
0001:eeee0000:0001:0000:1:0:1
48-1 WMNT
p:,c:000065,c:030065,c:040066
0001:eeee0000:0001:0000:1:0:10
68-1 WDTJ-LD
p:,c:000065,c:030065,c:040066

0002:eeee0000:0001:0000:1:0:2
48-2 FOXMUND
p:,c:00006f,c:03006f,c:040070
0003:eeee0000:0001:0000:1:0:3
48-3 WMNT
p:,c:000079,c:030079,c:04007a
0004:eeee0000:0001:0000:1:0:4
48-4 WEATHER
p:,c:000083,c:030083,c:040084

If two transponders are all you have with the same TSID, then change the TSID of the transponder with the least amount of channels from 1 to 2. You will need to change the transponder, and all the channels associated with the transponder.

You will need to do this using manual scan. Scan the low power station you want to change first, then edit the lamedb and scan the second low power station. No need to edit the second low power station if there are only two.

After you have edited lamedb, Telnet to the box, and type init 4. FTP the modified lamedb to the box, then telnet init 3. The telnet commands are needed to keep the box from rejecting the modified lamedb file.

No changes need to be made to the lamedb5 file.
Logged
elbandido
Visiting Mod
LFTA Legend
*****
Offline Offline

Posts: 1773



« Reply #8 on: October 29, 2017, 10:11:56 AM »

The option to "Ignore DVB namespace sub network" is supposed to be added to OpenPLi 6.1. So the problem will be fixed correctly when that version is released.
Logged
jholt5638
Full Member
***
Offline Offline

Posts: 79


« Reply #9 on: October 29, 2017, 11:56:00 AM »

I have OpenPLi 6.1 used the flash online option and had a option to choose either 6.0 or 6.1. Thanks for all the help
Logged
elbandido
Visiting Mod
LFTA Legend
*****
Offline Offline

Posts: 1773



« Reply #10 on: October 29, 2017, 12:08:18 PM »

You do not have OpenPLi 6.1 because it has not been released yet - online flash or other.

Code:
https://openpli.org/download/zgemma/H5.AC/
Logged
jholt5638
Full Member
***
Offline Offline

Posts: 79


« Reply #11 on: October 29, 2017, 02:31:01 PM »

My mistake I have OpenATV 6.1 not OpenPLi. Are there any major differences to choose one over the other?
Logged
elbandido
Visiting Mod
LFTA Legend
*****
Offline Offline

Posts: 1773



« Reply #12 on: October 29, 2017, 03:01:26 PM »

You may run any image you like.  OpenATV is more for Germans, and the image will load satellites and channel bouquets that are useless for us. OpenATV is a Full image, meaning many options are loaded by default. Full images usually run slower due to needing more resources.

OpenPLi is light, and usually runs faster. But you are expected to add the options that you want or need. I enjoy both of these groups, and their images. OpenPLi and SatDreamGr are the main ones responsible for ATSC, and those are the two images I usually prefer.

Several other groups also make and support enigma2 images. Find one you like and use it. Some of the file structure of the images a bit different, but it is all pretty much the same once you learn it.
Logged
elbandido
Visiting Mod
LFTA Legend
*****
Offline Offline

Posts: 1773



« Reply #13 on: October 31, 2017, 12:41:28 AM »

Here is the technical information on how to fix this problem correctly.

Code:
https://github.com/OpenPLi/enigma2/commit/d29f7c401f02b0625fac72768bf316a68bf9da71

You may go to the OpenAtv forum and request this solution to be added in the image.
Logged
elbandido
Visiting Mod
LFTA Legend
*****
Offline Offline

Posts: 1773



« Reply #14 on: November 30, 2017, 12:27:04 AM »

The image modification described in post #5 is now available in OpenPli 6.1 RC images.
 Example = openpli-6.1-rc-h5-20171130_usb.zip

Code:
https://openpli.org/download/zgemma/H5.AC/

Release candidate could be described as a Test preview of the next PLi image platform.
Logged
LEGALFREETOAIR.COM
   

 Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!