ATSC For Enigma2 (TEST)

[el bandido]

Looks like there is some interest in getting ATSC to work natively in enigma2. Testers in ATSC areas will be needed to make this project a success! If you would like to participate in the ATSC testing, you will need the following items.

(1) Enigma2 receiver capable of supporting usb tuners, and currently supported in OpenPLi

(2) ATSC usb device, or be willing to purchase an ATSC usb device.

(3) Basic knowledge of fta receiver operations including back-up and restoring images.

(4) Ability to use FileZilla or other file transfer programs.

(5) Ability to use Telnet or to connect to the receiver using RS232 (serial port).


I think the first three items would be about mandatory. Items 4 and 5 would make testing easier. EB

[eastof111]

What usb atsc tuners are currently supported with openpli?

Have you read anywhere when or if openpli will allow multiboot to work? Would prefer this method to test rather than loading it to flash. The same applies to Satdreamgr.

[el bandido]

12997

[eastof111]

Nice!

[eastof111]

I am guessing you're using the Sundtek tuner? Did you have to load a new driver and delete the Sundtek plugin?

[el bandido]

Which ATSC tuner do you have besides Sundtek? Make/Model Number

[el bandido]

12998

[eastof111]

Only have the Sundtek.

[mountaineer]

I have wintv 850 like yours....what packages do I need to load or are they only available for VU?

Thanks!!!!!

[el bandido]

Vu+ receiver is not really required in order to test.
(1) Enigma2 receiver capable of supporting usb tuners, and currently supported in OpenPLi

[el bandido]

I expect ATSC for enigma2 will be released to the community soon. It will be up to individual groups as to whether this enigma2 option is installed or not. I now have the capability to assign two atsc tuners to separate antennas pointed in different directions. This is possible because you may scan the ATSC tuner under cable or terrestrial types.

There is a lot we can do with enigma2 in North America. It would be nice if more people would get involved in improving this system.

[eastof111]

Looks like ATV has TBS drivers available since my last a while back.

[el bandido]

I do not see the ATSC driver, and their TBS driver is version 1.0 which is old. Current version is 1.4 I think. Also, you can install TBS driver all day but it will not work unless the kernel is patched for it. There is a separate thread for TBS if you need more info on it.

[eastof111]

That TBS driver wasn't there last week. I guess they're still playing catch up.

[el bandido]

Two ATSC tuners using two separate antennas is easy to do now. This feature works extremely well since you do not have loss trying to combine the two antennas.

13009

[el bandido]

Linux drivers will need to be available for any ATSC device that will be used in enigma2. ATSC drivers for WinTV850 (Hauppauge) is the only ATSC device that has been tested. Sundtek has said that an ATSC driver for their usb device will be available as time permits. I would also expect the WinTV 955Q to work now because it is very similar to the WinTV850.

13010

[el bandido]

I purchased another WinTv 850 USB stick in used condition for $18.00 on Ebay. Also purchased the WinTv 955Q to test. Images will be posted on this site soon that will have ATSC capability. Anyone interested in using these images will need to get a compatible ATSC usb stick.

[eastof111]

Nice.... a comparison of sensitivity and lock thresholds between WinTV and the Sundtek would be appreciated. Would like to see which is better for fringe area reception.

[el bandido]

So far, There will be little if any difference in reception of weak signals when using the Sundtek ATSC or the WinTv 850.

[eastof111]

Why is that? Are they both using the same chip, parts and circuitry?

[el bandido]

Why should it not be that?
The most noticeable gains (or losses) in any OTA or Terrestrial system will be in the antenna and feed line. OTA tuners will pretty much perform the same, and it may be possible to find a tuner that works a small amount better than most other tuners. But for the most part, tuners should perform about the same if they are correctly designed, and contain decent parts.

[eastof111]

I agree when one lives fairly close to strong signals and without obstructions. When one lives in a fringe area or a compromised location (valley with hills for example) every difference in quality build helps. I've been using the same antenna setup for many years and have had different tv models during that period. Many differed in reception quality on distant stations, whereas the local stations usually did not vary much between models. When I lived in a major suburban area, tuner quality wasn't really a concern.

While living in the boonies, I found tuner quality played a major difference in reception. Example, basically the same antenna setup I am using now, I used in northern California and was able to receive all SFO and San Jose stations from a location 110-130 miles away. The tv (lower quality) in the guest bedroom when hooked up to the same antenna system was not as sensitive and capable of receiving said stations. The main tv in the family room always performed well.

I agree, "tuners should perform about the same if they are correctly designed, and contain decent parts".

Just an observation.

[el bandido]

Any terrestrial signal over 80 miles in air distance will be a crap shoot due to the Earth being round. You can take ten identical terrestrial tuners and get different results from them. Tuner A may perform better at 503 MHz than tuner B, but tuner A may not perform as well at 677 MHz as tuner B. So if I tell you one tuner works better than another, you may not get the same results. At any rate, I will see if I can find a noticeable performance difference in the three tuner models I will have.

[el bandido]

Support for Hauppauge WinTv 955Q has been added. This ensures ATSC will be available in enigma2 for several more years.

[el bandido]

HD Video Clip. Use the 720p setting in the YouTube Player.




[Only registered and activated users can see links]

[el bandido]

Nice.... a comparison of sensitivity and lock thresholds between WinTV and the Sundtek would be appreciated. Would like to see which is better for fringe area reception.

I have had time to test these two tuners for you using the same antenna, and altering coax feeds to enure there is no cable issues in the tests.
The Sundtek tuner is down a little bit at 569 MHz compared to the WinTV 850, and the Sundtek tuner will glitch at random on some channels while the WinTv 850 is stable. The 569 MHz signal was weak and marginal for this test. Glitches on Sundtek can be noted by activating PIP and observing both tuners. Testing included changing which tuner was in PIP, and changing coak feed cables. The resuts were the same with all changes: The Sundtek device would glitch while the WinTv 850 did not. The Sundtek tuner runs cooler, but causes the spinner to activate when no signal is present. I do not know if that issue is related to enigma2 or not, but the WinTv 850 does not activate the spinner when no signal is present. Overall stability is in favor of the WinTv 850. Would be nice to make a comparison with the Sundtek device in native ATSC mode.

I have posted Experimental versions of the SatDeamGr image. These images are 100% stable for me. They are also 100% ready for ATSC. Simply load the divers from feeds, and scan the ATSC frequencies. Then watch TV.

[eastof111]

Thanks for the tests. You describe the glitching and spinner exactly as I have experienced. Will pickup a Wintv and see if it performs in my neck of the woods.

[el bandido]

Here is a short HD video that shows the Sundtek device glitching. Will be interesting to see if this issue disappears when a native ATSC driver is installed.


[Only registered and activated users can see links]

[ViP3R]

EB your video is set to private.

[el bandido]

Fixed...Just for you.

[el bandido]

Here is a short video showing two ATSC tuners installed in one receiver. This setup works very well with two separate terrestrial antenna systems.



[Only registered and activated users can see links]

[eastof111]

Picked up a new Wintv850 and installed the atsc-usbhauppauge (1.0-r0) driver on Satdreamgr, cold reboot of receiver and no usb shows up under tuner configuration. Tried different usb ports and the usb stick does display the green led getting power.

Did I miss a step somewhere?

[el bandido]

Which image did you use? Did you use the one I posted?

Post the output of lsusb in telnet.

[eastof111]

I downloaded the image from the Satdreamgr site, Satdreamgr-4.0-gst1-vuduo2-20160509.

[el bandido]

2040 Is the device number as seen below.



satdreamgr-openpli-gst1 4 vuduo2


vuduo2 login: root
[Only registered and activated users can see links]
Bus 001 Device 006: ID 2659:1211 Sundtek MediaTV Pro III (US)
Bus 001 Device 005: ID 734c:5925 TBS Technologies China
Bus 001 Device 004: ID 2040:7240 Hauppauge WinTV HVR-850
Bus 001 Device 003: ID 2040:7240 Hauppauge WinTV HVR-850
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 148f:5372 Ralink Technology, Corp. RT5372 Wireless Adapter
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Only registered and activated users can see links]


We could try fixing what you have, but it will be easier to install this image because it contains everything that is needed without using telnet.
[Only registered and activated users can see links]

[eastof111]

Will try Satdreamgr-4.0-gst1-vuduo2-20160505 and see what happens. Thanks.

[eastof111]

Well, installed Satdreamgr-4.0-gst1-vuduo2-20160505 and still no Hauppauge in tuner configuration or lsusb. Beginning to wonder if I got a bad stick. It does power on and it does get warm to the touch.

[el bandido]

[Only registered and activated users can see links]

The image the above link works because I tested it before uploading it. I am not using multi-boot due to kernel and other issues. So it has not been tested in a multi-boot environment. These usb devices will not work unless the kernel with the correct modifications is loaded.

You may try to verify these packages being installed in telnet.
opkg update
opkg install kernel-module-xc5000
opkg install kernel-module-tveeprom
opkg install kernel-module-au0828
opkg install kernel-module-cx231xx
opkg install kernel-module-em28xx
opkg install kernel-module-tda18271
opkg install kernel-module-si2157

Verify the firmware file is installed:
cd /lib/firmware
ls
FW File =
dvb-fe-xc5000-1.6.114.fw (Should be in the list.)

Still not working?
Post a complete log file using:
init 4
ENIGMA_DEBUG_LVL=4 enigma2

I suspect the usb stick is good from what you have posted. Just need to find the problem or issue as to why it is not loading.

[eastof111]

Thanks, I know about Satdream and Pli not working with multiboot, that's why I installed it in flash. I'll do the opkg's tomorrow since I am recording currently using ATV.

[eastof111]

Still using Satdreamgr-4.0-gst1-vuduo2-20160505 in flash.

Prior to doing any opkg's checked to see if the dvb-fe-xc5000-1.6.114.fw was in the lib/firmware directory and it was.

Did the opkg's and:

opkg update
opkg install kernel-module-xc5000 is up to date
opkg install kernel-module-tveeprom is up to date
opkg install kernel-module-au0828 is up to date
opkg install kernel-module-cx231xx is up to date
opkg install kernel-module-em28xx is up to date
opkg install kernel-module-tda18271 is up to date
opkg install kernel-module-si2157 installed and configured

Cold reboot and still nothing in the tuner configuration display. Currently running the level 4 debug and will post as soon as it completes.

[eastof111]

Before I went out today, I left the debug running, but forgot to assign a log file to it. When I got back it was still running so I had to stop the debug (need to use the receiver tonight). Will probably try again tomorrow.

[el bandido]

No need to leave debug running. All you need to do is:
set putty to record
open putty
init 4
ENIGMA_DEBUG_LVL=4 enigma2

The receiver will restart when you do this. Once the receiver is finished restarting Completly, Preess Ctrl C . This will break the putty recording, Then init 3 to restart the receiver. Zip and post the recorded putty file. The whole process takes less than 5 minutes. An example file is attached.

[eastof111]

Back to Satdreamgr-4.0-gst1-vuduo2-20160505 and disconnected a usb hub with fan which was using rear bottom port just to see if there were any conflicts. Cold reboot and still nothing in the tuner config display. Shut down receiver, reattached usb hub to rear port and re-connected 850 to front usb port. Cold reboot and did the debug routine which is attached.

[el bandido]

It is possible that the Sundtek device is causing problems. When did you install it?

Try loading the attached image in flash. Connect the WinTv device before installing this image.

[eastof111]

Will give it a shot tomorrow; currently recording some shows.

[eastof111]

Just to be sure.... I installed Wintv and drivers to Windows 10. Had to reinstall drivers a few times before 10 recognized them. Did a scan and it found and played the channels.

13069


13070

At least the 850 stick is confirmed as working ok.

Next, flashed Vuplus and uninstalled the Sundtek extension. Cold reboot and installed 850 driver. Cold reboot and nothing displays in tuner config. Checked fw in /lib/firmware and it was there. Applied all opkg's and they all confirmed as up to date.

Attached is the putty log for Vuplus image.

What version of 850 are you using? Mine is HVR-50 model 1230 SL-1230-V3.4-US.

[el bandido]

What is the output of lsusb in putty using the Vuplus image?

[eastof111]

Will check tomorrow and post.

[el bandido]

lsusb in Putty Should give a detailed description of all connected usb devices when using that particular image.

If you see the WinTv device listed correctly in lsusb but not being loaded:

Disconnect the internal hard drive.
Disconnect All external devices.
Insert WinTv usb stick into receiver.
Reinstall the VuPlus image using front usb port.

AFAIK, They made only one 850 ATSC model. Yours should have the same id as mine listed below.


satdreamgr-openpli-gst1 4 vuduo2


vuduo2 login: root
[Only registered and activated users can see links]
Bus 001 Device 006: ID 2659:1211 Sundtek MediaTV Pro III (US)
Bus 001 Device 007: ID 734c:5925 TBS Technologies China
Bus 001 Device 004: ID 2040:7240 Hauppauge WinTV HVR-850
Bus 001 Device 003: ID 2040:7240 Hauppauge WinTV HVR-850
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 148f:5372 Ralink Technology, Corp. RT5372 Wireless Adapter
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[Only registered and activated users can see links]

[eastof111]

Attached is the lsusb for me. It displays the Hauppauge only once not twice as yours. I've basically disconnected everything other than the HD, but I will give that a try and see what happens.

There's a newer image today, that I will also try later.

[eastof111]

Disconnected HD and re-flashed with vuplus. Cold reboot uninstalled sundtek extension. Cold re-boot. Installed 850 driver. Cold re-boot. Checked fw, opkg's, all current. Checked lsusb still displays one Hauppauge. Still nothing in tuner config.

[el bandido]

I have two WinTV 850 connected. This is the reason it is displayed twice.

Your device id is different and I suspect that is the reason it is not being loaded.

You have: 2040:b140 Hauppauge

Mine is: 2040:7240 Hauppauge WinTv HVR-850

The 955Q is: 2040:b123 Hauppauge WinTV HVR-955Q

Your best bet is to seek assistance at the SatDreamGr forum.

[eastof111]

Thanks I'll post there.

[el bandido]

Try this:

opkg update
opkg install kernel-module-cx231xx-dvb
opkg install kernel-module-cx231xx-alsa
opkg install kernel-module-cx2341x
opkg install kernel-module-cx231xx
opkg install kernel-module-lgdt3305
opkg install kernel-module-tda18271
opkg install kernel-module-tda18271c2dd
reboot

[eastof111]

Will give it a try tomorrow.

[eastof111]

Thanks EB, the following additions got the 850 to be recognized.

opkg install kernel-module-cx231xx-dvb installed and configured
opkg install kernel-module-cx231xx-alsa installed and configured
opkg install kernel-module-cx2341x is up to date
opkg install kernel-module-cx231xx is up to date
opkg install kernel-module-lgdt3305 installed and configured
opkg install kernel-module-tda18271 is up to date
opkg install kernel-module-tda18271c2dd installed and configured

The only problem is if I shut off the receiver or use the restart, upon boot up the 850 is not listed. Upon boot up, I have to do a restart enigma two or three times in order for the 850 to be recognized. But, even in this state I am happy that I will be able to use the 850 to make glitch free recordings.

[el bandido]

Athoik at SatDreamGr is supplying us with these fixes. So all Thanks goes to Athoik!

Does the WinTv device have the glitching that Sundtek does? You may add more tuners for more recording capability if needed. I usually have three ATSC tuners installed on two different antennas.

More than likely, the reason you are having to restart several times to see the device is the Sundtek device. Remove the Sundtek device, then delete the S99tuner.sh file located at: " /etc/rc3.d ". You do not need to delete the Sundtek plugin, just remove the device AND that file. You may need to use the Dream Explorer plugin to remove that file correctly.

Scanned channels/channel names may be transferred to the WinTv device by altering the transponder frequencies in lamedb.

[eastof111]

No glitching at all. Will try the above tomorrow.

[eastof111]

Did not remove Sundtek device yet and did a scan with Sundtek and assigned all channels to Sundtek bouquet. Plus, made manual corrections to the names in the bouquet. Shut off receiver and connected Wintv with a splitter. After getting Wintv to display, I did a scan and assigned the channels to Wintv bouquet. The scan changed all my manually corrected channels in the Sundtek bouquet. Plus, if I select a channel to watch in Sundtek bouquet, it will display from the Wintv tuner since it was the last scanned tuner.

I haven't found anything in the system menu to keep the two tuners separate. I did two instant recordings, using channel 3 on Sundtek and channel 5 on Wintv. Both recorded correctly from two tuners within the date/time frame.

Using the timers menu, I assign a recording of channel 3 on the Sundtek tuner and channel 5 with in the same date/time frame selecting the Wintv tuner. It will not accept these parameters. Keep getting timer conflict. Basically, because it is selecting the Wintv tuner instead of the separate tuners for the recordings.

[el bandido]

A dmesg(rs232) and lsmod(telnet) posting from your receiver at reboot would be nice. This information will help to get these features embedded in future images.

The tuners can be separated but you will need to make changes in lamedb if you want channel names displayed for the WinTv device. The receiver "sees" the Sundtek device as DVB-T, and the WinTv device as ATSC. The output of both devices is stored in the terrestrial folder. There is a manual scan option for the WinTV to scan under Cable. Anything scanned under the Cable setting cannot be accessed by the Sundtek device. I have found it much easier to edit the lamedb file one time and be done with it. Terrestrial channels do not change much, so the information does not have to be scanned and edited often. You may upload a lamedb that contains all the terrestrial channel information. I would prefer this lamedb to only have the Sundtek device scanned in it. Do not scan anything else including satellites and the WinTv device.

[eastof111]

Will reflash again tomorrow and add Sundtek only for the lamedb file. Played with Dreamboxedit and ticked off the box for "do not overwrite" for all the Sundtek scanned channels and reloaded to receiver. Disabled Sundtek in tuner config and loaded Wintv, rebooted a few times and scanned for channels.

Downloaded to Dreamboxedit and the Wintv scan did not change any of the channels in the Sundtek bouquet. Copied last scanned channels to Wintv bouquet. Then sorted and reloaded to receiver. Rebooted and tried to watch a channel with Wintv. No video or audio displayed nor any error message to indicate a tuning problem. Just displays the info bar on any channel selected.

Will pursue again tomorrow.

[el bandido]

Easier for me to edit the lamedb file with notepad++. The transponder id has to be altered slightly or your channel names will go back to channel numbers using the WinTv. The device automatically updates, and altering the tp id slightly disables the auto update feature.

[eastof111]

Re-flashed Satdreamgr-4.0-gst1-vuduo2-20160517 after boot up the lamedb displays Sundtek and sats from prior flashes. I could load to Dreamboxedit and delete all sats if necessary.

[el bandido]

A dmesg(rs232) and lsmod(telnet) posting from your receiver at reboot would be nice. This information will help to get these features embedded in future images.

Modified lamedb attached.

Init 4
Replace lamedb
Init 3

[eastof111]

Thanks, I'll try the lamedb and see how it works.

Do you want a dmesg(rs232) and lsmod from the image I was using when I had the timer conflict ( I can re-flash from a backup), or while using the new lamedb?

[el bandido]

Should not really matter. I think the idea is to correctly id the device so it can be included in the driver plugin. Also try in a multi-boot when you have time. Sundtek may release an ATSC driver which will make life easier for you. I do not see any real need to separate the ATSC devices in the receiver unless you have two separate antennas. The receiver will automatically manage the devices if they are the same such as ATSC or DVB-C/T. This is the only ATSC system I have seen that will allow the use of two separate antennas and have automatic switching between them. This is something I have wanted for a long time.

[eastof111]

OK, I've got recordings to do later tonight, so I'll switch back to ATV. Then tomorrow I'll pursue the new lamedb along with Satdreamgr-4.0-gst1-vuduo2-20160522.

[eastof111]

Flashed Satdreamgr-4.0-gst1-vuduo2-20160522 and loaded the edited lamedb. Reinstalled Sundtek and all channels listed in bouquet display.

Sundtek is tuner E.

Did the opkg's and Wintv shows installed after the reboots. WinTV is tuner F. Did a scan with Wintv and it changed all the channel mods originally made to the Sundtek bouquet.

Selecting a channel from the Sundtek bouquet will display it as originating from tuner F.
Selecting a channel from the Wintv bouquet will display as tuner F.

I am guessing I won't be able to use the two tuners together until some changes are made.

Attached is the lsmod and dmesg.

[el bandido]

Why did you do a scan with the WinTv device? Doing a scan using the WinTv will erase all the changes.

You should have two folders in the original lamedb that I modified for the terrestrial channels. One folder will be terrestrial, and the other folder will be cable. I tested these two folders, and they worked correctly. There should be no need to re-scan any terrestrial channels.

[eastof111]

No problem, will redo tomorrow without the scan. By the way, the atsc.xml file was missing 195000000 for my area.

[el bandido]

Make the needed changes to the main atsc.xml and post it. You may also want to make a sub-section in the atsc.xml that contains the transponders for your area.

[eastof111]

Re-flashed Satdreamgr-4.0-gst1-vuduo2-20160522 and loaded the edited lamedb. Reinstalled Sundtek. All channels listed in bouquet display.

Sundtek is tuner E.

Did the opkg's and Wintv shows installed after the reboots. WinTV is tuner F. Did NOT scan with Wintv.
Attached is the lsmod and dmesg in putty log.

Later, created a bouquet for Wintv and copied some of the Sundtek channels to Wintv bouquet.

Selected a channel from the Sundtek bouquet and displays as originating from tuner E.
Selecting a channel from the Wintv bouquet will display as tuner E also.

Makes sense since there is no scan for Wintv and it's actually using the Sundtek parameters.

[el bandido]

The channel and transponder information for terrestrial channels has been changed in lamedb. You will change this information if you scan terrestrial channels. Try the attached lamedb and see if it works better. Two folders. 1 labeled terrestrial and 1 labeled Cable. The tuners should automatically switch now when you change from Terrestrial to Cable or Cable to Terrestrial.

[eastof111]

Will give it a try tomorrow.

[eastof111]

Installed and it changed the bouquets for tuner E and F to n/a.

[el bandido]

Of course it did. Those bouquets get their channel information from lamedb in etc/enigma2 which has been altered. You cannot expect those two bouquets to work and they would need to be rebuilt. In channel selection, you should see two folders listed as Terrestrial and Cable. The channels in those two folders should work correctly for you. I will try to post some screenshots or a short video sometime this evening.

[el bandido]

Here is a transponder listing in lamedb:
ffff0000:222b:0001
t 563309999:2:6:0:0

Here is a channel listing in lamedb:
0003:ffff0000:222b:0001:1:0
KGRQ-LD (29.1 Antenna 1)
p:Sundtek

You will lose any bouquets that have been made when you alter the above information because this is the same information that the bouquets are created with. It normally takes only a few minutes to create new bouquets.

The channels that are in the Terrestrial or in the Cable folders as seen below should work in your receiver. You would have to create new secondary bouquets from them because the channel and transponder information has bee altered.

The second picture shown below demonstrate how to scan a single ATSC frequency into the cable folder. The Sundtek device is listed as DVB-T in the receiver and has no rights to the Cable folder. Anything scanned into the cable folder can only be accessed using a native ATSC device such as WinTV. This is how the two devices may be separated. The WinTv device will be able to access both Terrestrial and Cable folders unless the transponder and channel information is altered in the folder you do not want WinTv to access.

13103


13104

[eastof111]

Yesterday I created a cable bouquet and scanned a couple of channels manually with Wintv and entered them to the cable bouquet. Played fine with Wintv, then went to the Sundeck (terrestrial bouquet) and selected the same channel and it still displayed as tuner F (Wintv). Actually all channels in terrestrial bouquet display as tuner F.

Will try again tomorrow.

[el bandido]

The lamedb file in post #73 should work correctly. Check it and see. Try using only the Terrestrial and Cable folders that the receiver creates. Screenshots of the automatic switching are shown below. Sundtek will actually play an Atlanta local channel using your channel information as seen in the screenshots.

13106


13107


13108


13109

[el bandido]

Yesterday I created a cable bouquet and scanned a couple of channels manually with Wintv and entered them to the cable bouquet. Played fine with Wintv, then went to the Sundeck (terrestrial bouquet) and selected the same channel and it still displayed as tuner F (Wintv). Actually all channels in terrestrial bouquet display as tuner F.

Will try again tomorrow.

Check preferred Tuner Setting. Try changing the preferred tuner to E.

Check Alternative services tuner priority. Set to "No priority."

13110

[eastof111]

"The lamedb file in post #73 should work correctly. Check it and see. Try using only the Terrestrial and Cable folders that the receiver creates."

That's the one I am using. Maybe I missed something, but the receiver never created terrestrial or cable folders at my end. I've had to create the bouquets manually. Will play with the tuner settings tomorrow.

[el bandido]

Post the enigma2 folder located in etc (etc/enigma2). Remove the settings file from enigma2 before posting IF you have made any logins with the receiver to facebook or any other site that requires a password.

[eastof111]

Looks like I will resume using ATV with Sundtek for a while longer. Timer recordings of fta and atsc have always worked flawlessly, except of course for the Sundtek glitching.

Satdreamgr still has a timer recording problem. It has disabled timer recordings, both fta and atsc on four occasions prior to completion of the recordings. Plus, on occasion, the time has to be corrected and updated for no reason. Usually takes a few cold boots to correct this problem. Even with the NTP time set to correct itself every five minutes, it's usually of by 45+ seconds. With ATV the time is always right on (+ or - 2 seconds). I will wait until they correct this time/timer problem along with having not to install the opkg's for Wintv.

I do like the fact that re-flashing Satdreamgr will automatically update prior settings, thus. saving time.

[el bandido]

Something is not loading correctly from what you have written. System Time seems to works correctly for me and is accurate. Your ATSC problems or issues cannot be fixed easily without providing information or files needed to replicate them. Other images such as OpenATV should have ATSC at some point in the future. We will wait and see what happens. EB

[eastof111]

Here's a new one I have not experienced before with over night recordings of atsc channels. I would guess this error to be a sat uplink or downlink problem rather than the tv station or atsc tuner.

[el bandido]

What skin is that, and which device are you using for ATSC?

[eastof111]

PD1LOI-Full-HD with Sundtek. We had very heavy thunderstorms and lightning the night of the recording. Some places received two to three inches of rain within an hour, so that may have been a contributing factor.

[eastof111]

Glad to see OpenATV added the Hauppauge driver.

[el bandido]

ATSC support now avalable in Open PLi.

13266


13267

Channels scan and play without any issues!

[eastof111]

Nice! Does OpenPli differentiate when using the Sundtek and WinTV and allow using them independently without modifying the lamedb?

[el bandido]

I have already tried to explain that, but do not mind trying again.

Sundtek tricks enigna2 into thinking the ATSC signal is DVB-T. DVB-T is terrestrial according to enigma2. Consider this to be tuner 1 or antenna 1.

ATSC in enigma2 may be scanned as terrestrial or as cable. What is scanned as cable cannot be seen or shared with Sundtek because cable and terrestrial cannot be shared unless it is an ATSC device. Consider the ATSC cable scans to be tuner 2 or antenna 2.

[eastof111]

Understand, but why can't the coding include a scan menu to test for Sundtek or Hauppauge using their xml files, once found, do a scan for each tuner and assign the found stations to the lamedb file by tuner type?

[el bandido]

The scan menus are already there in manual scan. Sundtek DVB-T will scan as terrestrial. You do not have any other option. A single ATSC Transponder may be scanned as terrestrial or cable. Lamedb sorts the terrestrial and cable channels, keeping them separate.

[mountaineer]

Is there a way to scan in Ch4 analog? I have two atsc channels and one ch 4 from my Dish Network receiver being combined and sent over a coacx throughout the house. It works great but didn't know if the 950Q could scan in the ch4 analog in E2 on osmini.
Thanks guys!!!!

[el bandido]

Does the OS Mini recognize the 950Q?

'[Only registered and activated users can see links]

Analog is supported for the device, according to the information in the link.

[el bandido]

Forgot to mention that most fta receivers do not support analog.

[mountaineer]

Yes both of my os minis have a 950Q on them and work very well. I just have channel 4 output from DN receiver like from an old VCR but no way to scan it in. Thanks for the info!!!!

[chewie]

Hello Guys
I Purchased a 955Q Hauppauge tuner, it works good on my computer, but I can not get it going on my Octagon, I downloaded the drivers for this tuner and they are installed, I am not sure if this tuner is like the Sundtek tuner, but I check the tuner config. and I only see A and B tuners, on my computer I see a an Icon for this tuner where I can launch the tuner and scan for channels, on the receiver I don't see anything like the sundtek that has a Control center. I looked for something similar under the plugins section but was not able to see something for this tuner.
Just wondering how you launch this tuner on a satellite receiver.
If anybody Has any ideas please let me know.
Regards.
Chewie

[el bandido]

Hauppauge 850 and 950 are the only two supported usb devices for ATSC that work. The Hauppauge ATSC devices do not require a special plugin. The ATSC .xml file loads by default in almost all enigma2 images.

Try this:
Load the drivers for the device in downloadable plugins.
Remove power to the receiver, inert the usb device, power on the receiver.
A light should appear on the side of the 955 once the receiver is booted. Please verify this.
[Only registered and activated users can see links]

Here is a screenshot of 3 850 devices installed. in the Octagon SF4008.

14379

[chewie]

Thanks EB
I don't understand why the 955 is not supported if the drivers are there, I will try your suggestions when I get home, hope it works, I would hate to send it back to amazon.
Regards.
Chewie

[el bandido]

You can install drivers and all the stuff needed to support the device, but it will not work if the receiver does not know what the device is or what it is supposed to do! I suspect this may be the problem.

Here is one reason why the driver is listed in enigma2 feeds, but does not work:
There has not been any interest in ATSC enigma2. No one in North America has shown much of a desire to test anything or to make any improvements in enigma2. ATSC works well for me with the 850 and that is all that matters! Lol. I will see if we can get the help that is needed to make the 955 work if you are interested.

[chewie]

Hello EB
Yes I will Be interested if they can make it work, since the drivers are there already, yes ask your friends some questions and see if is going to be be a long process.
Let me know.
Chewie

[el bandido]

It will take as long as it takes. That is all I know to say. Buy an 850 if you are in a big hurry.

Please list the output of lsusb as mentioned earlier. Thanks.

[chewie]

Hello EB
I try the commend by telnet and there is no output, I try the tuner on the VU+, same thing, neither receiver is seeing the tuner.
Chewie

[el bandido]

The telnet command "lsusb" lists usb devices that are connected to the receiver. It may help to see how yours is listed in the receiver.

Remove power to the receiver.
Insert the 955 usb device into the receiver.
Power On the receiver.
Connect to the receiver using telnet.
Type "lsusb" in the telnet window.
Post the output.

Here is an example:

[Only registered and activated users can see links]
Bus 004 Device 002: ID 1a40:0101
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0003
Bus 003 Device 001: ID 1d6b:0002
Bus 004 Device 001: ID 1d6b:0002
Bus 005 Device 001: ID 1d6b:0001
Bus 006 Device 001: ID 1d6b:0001
Bus 004 Device 003: ID 2040:b123
Bus 004 Device 004: ID 2040:7240
Bus 004 Device 005: ID 05e3:0610
Bus 004 Device 006: ID 2040:7240
Bus 004 Device 007: ID 0bda:2838
Bus 004 Device 008: ID 2040:7240
[Only registered and activated users can see links]

[chewie]

Hello EB
Here is the output.
Regards.
Chewie

[el bandido]

The device ID is correct in your list. Let's see if we can get some help with this.

[chewie]

Thanks EB, I was talking to the VIX Guys, and they said is Best to install by command line, that will show any errors. what ever this means.
I think they are asking to install the drivers Manually and see if there is any errors.
Let me know what you find out.
Regards.
Chewie

[el bandido]

User driver installation is not the problem or issue.
VIX is a Great Good Group of people, but as far as I know, they do not know about or do any ATSC development work in the enigma2 system. Let's talk to the people that did the ATSC install work instead!

[chewie]

Right on EB, let me know what you find.
Regards.
Chewie

[el bandido]

The 955Q issue is being looked at. We will see soon...

[el bandido]

The 955Q usb device is recognized correctly in linux utils.
The problem will be vtuner and/or drivers because the 955Q is not being recognized.

A sample 955Q usb device may need to be sent to Octagon in order to fix the problem. This is something Rick Caylor should do since he is the Octagon vendor in North America. I am not interested in buying a 955Q or paying to send my 955Q to Germany so the problem can be fixed.

Special Thanks to Athoik & SatDreamGr for looking at this problem and suggesting a solution. EB

[chewie]

Thanks EB for looking into it, I am sending it back to amazon and ordering the 950q, I don't thinks they sell the 850 anymore.
Regards.
Chewie

[el bandido]

You give up too easy. They got it working to a degree after a few more tests. am watching TV with the Octagon and 955Q now.

You are welcome to test it also if you want.

[chewie]

Hello EB
Well I haven't send it back yet, what do I need to do to test it.
Let me know.
Chewie

[el bandido]

Insert 955Q into receiver.

Download and install Satdreamgr-5-sf4008-20170901.zip From here: [Only registered and activated users can see links]

After install of image, Open telnet and type or enter:
opkg update (wait for finish)

opkg upgrade (wait for finish)

reboot

After box completely reboots, Open telnet and type or enter:
sed -i 's#device/ep_84#device/ep_8f#g' /usr/bin/enigma2

reboot

The 955Q should be usable.

Also, Kodi is available in downloadable plugins under extensions.

Please post results.

[chewie]

Hello EB
it works now, it scan 131 Channels, I try 50 of them and was able to see about 47, I will try the the rest of them later, thanks to the people that made this possible One question, can these commends work with other images?
Thanks again EB.
Regards.
Chewie

[el bandido]

All I can say is try it and see. Please post any problems or issues you have with the 955Q here. This is a Test!

If you want to Thank someone, go over to the SatDreamGr forum and let them know you appreciate their efforts and work! A lot of our "toys" have came from them!

[chewie]

Hello EB
I TRY ON atv 6.1 and it worked, openeight did not work, on EGAMI IT RECOGNIZE the tuner but was not able to scan, it rebooted.
Regards.
Chewie

[chewie]

Hello EB
Not real issues so far 2 or 3 channels get distorted and that is it on both images, I noticed tonight that the ATV image scan 142 channels and the SatDreamGr only 131 channels, picture is very good.
Do you think is ok to share this information on this tuner on another forum?
Regards.
Chewie

[el bandido]

You may share the information. It is Open Source. Thanks for asking first. Remember, Athoik and SatDreamGr supplied this solution!

The image should not have anything to do with channels scanned or not scanned because the 955Q tuner does the actual finding of channels.

Open Eight and Egami have issues with ATSC using any supported Hauppauge tuner.

I appreciate your comments and taking time to check the operation of the device!

[el bandido]

The 955Q project should now be complete in SatDreamGr experimental image. The information needed to fix the 955Q is available and will probably be added by most of the other image groups in time.

There should not be any need now for telnet commands.

Simply download and install Satdreamgr-5-sf4008-20170917.zip from:[Only registered and activated users can see links]

Do an online update after installing the image and the signal in db will work.
14394

[chewie]

Hello EB
I installed the Satdreamgr-5 on on the flash, updated the software and it recognizes all tuners, but there is no sound either on the USB tuners or the A and B tuners, are you having the same problems?
Let me know.
Regards.
Chewie

[el bandido]

Sound works for me.
Go into the standby/restart menu of the receiver and restart enigma. See if that works.

[chewie]

Try that already and same thing, I will down load a fresh image and reload it.
Regards.
Chewie

[el bandido]

There is an ATSC bug in enigma2. I will explain it briefly, but I am not interested in trying to fix it.

(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 problem will correct itself when the television stations repack and transition to ATSC 3.0. I have yet to see anyone else complain about this problem, and the symptom would be scanning in channels that do not work.

I have found a solution or work-around by manually adding unique TSID's to the ATSC transponders in my area that do not have one. This works well for me, and is probably the only solution at this point in time.

We have tested Hauppauge 850, 950, and 955 ATSC 1.0 usb devices. All three of these devices, or a combination of these three devices work in Vu+ Duo2, Vu+ Zero, Edision OS Mini, and Octagon SF4008. These three ATSC devices along with this list of receivers satisfies the needs of the members of this forum. I do not see any reason to change or add anything else to enigma2 ATSC at this time. Let's wait a year or two and see what ATSC 3.0 does.

[el bandido]

ATSC bug has apparently been fixed in latest SatDreamGr Experimental image!
More information on this shortly.

[el bandido]

Here is a technical description of the problem from Athoik:

scan: do not ingore namespace subnetwork

By default the namespace contains only part of the hash that is possible to store
because when we are having valid ONID we are ingoring the last 2 bytes (subnetwork).

That is happening when isValidONIDTSID is true and that exists since the initial
import of enigma2 in git.

In the subnetwork we are storing the frequency and polarization for sat
and frequency for other systems and that solves all the problematic cases where
same ONID is appeared twice, without hardcoding exceptions in isValidONIDTSID.

Although by not ingoring the subnetwork all the service references will change
making at least picons unusable.

The findPicon can be optimized to ingore the subnetwork and that will be fixed
by another.

Ideally the namespace should not ingore the subnetwork and isValidONIDTSID
check can go away, once there are no issues preventing to do so.
[Only registered and activated users can see links]

Extra selection has been added in SatDreamGr and OpenVix images.
(Ignore DVB namespace sub network = no)
14473

14474

[Megatron817]

Something to do with the hauppauge 950Q is causing my channels to change after a reboot. Alot of channels in tv favorites show N/A but when I change to that channel it will tune in and say dvb service and then change back to the original name but my radio favorites the ones I added Pid's manually say not found in pat and the pid's have been changed to all zeros. Luckily I Had it backed up and loading the backup fixes it.
has this happened to anyone else?

[el bandido]

No one has documented or even commented about the ATSC tuners causing problems with other channels before this. Some low power tv stations do not transmit a correct Id, and this will cause problems only with the ATSC channels, but there is a setting that fixes this.

Favorites could be thought of as an extension of the main channel list. It would be a good idea to check and see if the main list is correct, then figure out what you are doing to disrupt the Favorite channel bouquet.

[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.

14977

[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.

14980

14981

[Megatron817]

Talked to the RF Engineer from daystar in Texas, said the tsid is asigned by the FCC and can't be changed. So the work around will have to do.
He seemed very interested in this hobby with FTA and Atsc so I gave him this forum address.

[el bandido]

Good deal!
Yes and No on the TSID being assigned by the FCC for OTA.
TSID is assigned and is mandatory except for low power stations. Low power stations do not have an assigned TSID, so they can transmit what they want or transmit 0 for TSID. We would not have this problem if low power OTA stations were assigned TSID. It is what it is...