ATSC For Enigma2 (TEST)

[Megatron817]

You are right
It is channel 18-1 on rf ch. 18 at 497 mhz.
Went thrugh scanning freqencies one at a time doing a reboot after each scan and that was the one causing the problem.
Thanks!

[Megatron817]

Got everything working good again and backed up. No problems with reboots/restarts.
I modified the atsc .xml file in etc/tuxbox. Changed atlanta, Ga. to Tampa,FL. and added the 11 frequencies that I wanted and deleted the rest. Now I scan with signal finder plugin easy.

[el bandido]

Which image are you using?

[Megatron817]

openpli 6.2 release
build date 2018-05-23
last upgrade 2018-06-04

[el bandido]

Other cities besides Atlanta could have been added to the ATSC file when it was first introduced, but no one except me submitted cities or areas. ATSC does not require a scan very often, so scanning all possible frequencies works and takes less than ten minutes.

The namespace problem can be fixed by setting Ignore namespace sub network to No as shown below. This menu will be at different places, depending on the image, but all of the major images have these settings available. Delete all ATSC channels and re-scan after setting DVB-C and DVB-T to No.

[Only registered and activated users can see links. ]

[Megatron817]

I found the setting at setup/system/customize it was set to green so I changed it to grey.
Thanks.

[Megatron817]

Those settings still didn't help with that ch.18 at 497MHz. It is Daystar so I can live without it.
What I did was made some more changes to the astc .xml. Deleted 497MHz from the terrestrial list.
problem solved and a full manual scan took about 5 minutes. The Tampa, FL scan takes about 30 seconds scanning 11 frequencies only.

[Megatron817]

Namespace data incorrct for channel 18-1 at 497MHZ
I probably could add the service with dreamset but i don't need it.

[Megatron817]

Ok I am a tinkerer just had to figure this ch.18 problem out so using dreamset it wasn't acually the name space. That just caused a mis alignment of the channel name. The Real problem is a four digit transponder ID that is 5065 so by changing it to a three digit ID 565 that fixed it. a one or two digit ID will also work fine.

[el bandido]

Very Good!
This is a known problem, and a solution has been provided to fix it. I tested OpenAtv 6.1 this evening, and find it works correctly for ATSC channels, providing the correct settings for ATSC are entered. There are about 4 frequencies that have the same TSID in my area, so it is real easy for me to see if the solution works or not. Check and make sure you are using the correct settings that are shown. You should not have to worry about a work-around as this problem has been, Or should be fixed. Enter the correct settings, delete ATSC channels and re-scan.

[Only registered and activated users can see links. ]

[Only registered and activated users can see links. ]