Results 1 to 19 of 19

Thread: VIX 2.3 problem with Sundtek

  1. #1
    Senior Member
    Join Date
    Feb 2008
    Posts
    501
    Thanks
    3
    Thanked 133 Times in 81 Posts
    Rep Power
    22

    Default VIX 2.3 problem with Sundtek

    I can't get my Sundtek DVD-T to scan Channel 7 (177.5 MHz) in vix 2.3 on the vu duo. No problems if I go back to vix 2.2.



    Tried a fresh 2.3 install from scratch, but still no go. Doesn't matter if I do a full scan, or just a single freq. There's stacks of signal so that's not the problem. I mucked around a bit with terrestrial.xml (adding dummy entries at the start) & did see chan 7 once, but chan 9 was missing, so I aborted the scan. Since then, I haven't been able to get it again.

  2. #2
    Senior Member Vic's Avatar
    Join Date
    Jan 2008
    Posts
    913
    Thanks
    68
    Thanked 267 Times in 154 Posts
    Rep Power
    37

    Default

    Quote Originally Posted by jgm View Post
    I can't get my Sundtek DVD-T to scan Channel 7 (177.5 MHz) in vix 2.3 on the vu duo. No problems if I go back to vix 2.2.

    Tried a fresh 2.3 install from scratch, but still no go. Doesn't matter if I do a full scan, or just a single freq. There's stacks of signal so that's not the problem. I mucked around a bit with terrestrial.xml (adding dummy entries at the start) & did see chan 7 once, but chan 9 was missing, so I aborted the scan. Since then, I haven't been able to get it again.
    Try Pli it works for me
    DM800 DM800se Vu+Duo ET9000

  3. #3
    Premium Member warbo's Avatar
    Join Date
    Jan 2008
    Location
    Armidale
    Posts
    1,659
    Thanks
    283
    Thanked 632 Times in 289 Posts
    Rep Power
    72

    Default

    Quote Originally Posted by jgm View Post
    I can't get my Sundtek DVD-T to scan Channel 7 (177.5 MHz) in vix 2.3 on the vu duo. No problems if I go back to vix 2.2.

    Tried a fresh 2.3 install from scratch, but still no go. Doesn't matter if I do a full scan, or just a single freq. There's stacks of signal so that's not the problem. I mucked around a bit with terrestrial.xml (adding dummy entries at the start) & did see chan 7 once, but chan 9 was missing, so I aborted the scan. Since then, I haven't been able to get it again.
    I did a quick install today and had the same problem with ch10 and sbs. Another rescan sucked in sbs but still no ch10. I haven't had any time to look at it any further. I'll ask the sundtek guy to take a look at what the problem might be.

  4. #4
    Premium Member weirdo's Avatar
    Join Date
    Jan 2008
    Posts
    3,927
    Thanks
    2,933
    Thanked 1,831 Times in 938 Posts
    Rep Power
    184

    Default

    maybe try your terrestrial services file from the 2.2 version in your new one

  5. #5
    Premium Member warbo's Avatar
    Join Date
    Jan 2008
    Location
    Armidale
    Posts
    1,659
    Thanks
    283
    Thanked 632 Times in 289 Posts
    Rep Power
    72

    Default

    Tried that weirdo. The files are identical.

    There are reports that the hauppage stick is doing something similar in 2.3 so it sounds like an image issue.

  6. #6
    Senior Member
    Join Date
    Feb 2008
    Posts
    501
    Thanks
    3
    Thanked 133 Times in 81 Posts
    Rep Power
    22

    Default

    Another report of the same problem in VIX forum.

  7. #7
    Senior Member
    Join Date
    Aug 2009
    Posts
    261
    Thanks
    43
    Thanked 185 Times in 95 Posts
    Rep Power
    18

    Default

    all those with problems please make a post here and we will look into it.
    Code:
    http://www.world-of-satellite.com/showthread.php?13396-Hauppauge-WinTV-dvb-not-all-channels-help-please&p=97153#post97153

  8. #8
    Premium Member warbo's Avatar
    Join Date
    Jan 2008
    Location
    Armidale
    Posts
    1,659
    Thanks
    283
    Thanked 632 Times in 289 Posts
    Rep Power
    72

    Default

    With the following code, I can now get the abc's to scan in but not 10,11 or one hd. Somethings a bit screwy.

    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- useable flags are
    	1: Network Scan
    	2: use BAT
    	4: use ONIT
    	8: skip NITs of known networks
    	and combinations of this.
    -->
    <!-- transponder parameters:
    	bandwidth: 0 = 8 MHz, 1 = 7 MHz, 2 = 6 MHz, 3 = Auto (unsupported, default)
    	constellation: 0 = QPSK, 1 = 16-QAM (default), 2 = 64-QAM, 3 = Auto
    	code_rate_{lp,hp}: 0 = 1/2, 1 = 2/3, 2 = 3/4, 3 = 5/6, 4 = 7/8, 5 = Auto (default), 6 = None
    	guard_interval: 0 = 1/32, 1 = 1/16, 2 = 1/8, 3 = 1/4, 4 = Auto (default)
    	transmission_mode: 0 = 2K, 1 = 8K, 2 = Auto (default)
    	hierarchy_information: 0 = None, 1 = 1, 2 = 2, 3 = 4, 4 = Auto (default)
    	inversion: 0 = Off, 1 = On, 2 = Auto (default)
    -->
    <!--
    	Please report missing frequencies and pointers to regional
    	standards to http://www.dream-multimedia-tv.de/board/
    -->
    
    <locations>
    	<terrestrial name="Australia: DVB-T Frequencies" flags="5">
    		<transponder centre_frequency="177500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="184500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="191500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="198500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="205500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="212500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="219500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="226500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="529500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="536500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="543500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="550500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="557500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="564500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="571500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="578500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="585500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="592500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="599500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="606500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="613500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="620500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="627500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="634500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="641500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="648500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="655500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="662500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="669500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="676500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="683500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="690500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="697500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="704500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="711500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="718500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="725500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="732500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="739500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="746500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="753500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="760500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="767500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="774500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="781500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="788500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="795500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="802500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="809500000" bandwidth="1" constellation="3"/>
    		<transponder centre_frequency="816500000" bandwidth="1" constellation="3"/>
    	</terrestrial>
    </locations>
    Last edited by warbo; 29-11-11 at 02:25 PM.

  9. #9
    Premium Member warbo's Avatar
    Join Date
    Jan 2008
    Location
    Armidale
    Posts
    1,659
    Thanks
    283
    Thanked 632 Times in 289 Posts
    Rep Power
    72

    Default

    The sundtek engineer has been working on my stb for the last couple of hours. In the end the conclusion was "weird" lol.

    The sundtek works fine in windows.

    DUDE.......FYI he says he sent the VIX team some dongles. Not sure who to or when but they must be on the way if you don't have them yet.

  10. #10
    Senior Member
    Join Date
    Feb 2008
    Posts
    501
    Thanks
    3
    Thanked 133 Times in 81 Posts
    Rep Power
    22

    Default

    Just managed to get 177500 to scan by manually setting parameters. I did a Single transponder, manual scan with the following settings:
    Inversion - off
    Bandwidth - 7MHz
    Code rate HP - 2/3
    Code rate LP - 2/3
    Modulation - QAM16
    Transmission mode - 8K
    Guard interval - 1/32
    Hierarchy info - None
    Network scan - no
    Clear before scan -no
    Only Free scan - no

  11. The Following User Says Thank You to jgm For This Useful Post:


  12. #11
    Senior Member
    Join Date
    Aug 2009
    Posts
    261
    Thanks
    43
    Thanked 185 Times in 95 Posts
    Rep Power
    18

    Default

    Quote Originally Posted by warbo View Post
    The sundtek engineer has been working on my stb for the last couple of hours. In the end the conclusion was "weird" lol.

    The sundtek works fine in windows.

    DUDE.......FYI he says he sent the VIX team some dongles. Not sure who to or when but they must be on the way if you don't have them yet.
    yeah i think silverfox and andy may have those. although there seems to be no problems with the uk terrestrial frequencies, just the Australian ones.

  13. #12
    Administrator admin's Avatar
    Join Date
    Jan 2008
    Posts
    20,137
    Thanks
    97
    Thanked 5,766 Times in 2,578 Posts
    Rep Power
    25

    Default

    I have had a bot of a nightmare time since upgrading from a 12 month old PLI image to VIX. I only upgraded because I could not get the Sundtek to work properly.

    On the Vix image, I managed to scan in all terrestrial channels except for the 7 network which would not scan in at all. I also "lost" all satellite HD channels...they were there but when selected the signal level dropped to nothing.

    After almost giving up , I did a full satellite and terrestrial rescan and what do you know...the 7's turned up and the sat HD problem fixed itself

  14. #13
    Premium Member warbo's Avatar
    Join Date
    Jan 2008
    Location
    Armidale
    Posts
    1,659
    Thanks
    283
    Thanked 632 Times in 289 Posts
    Rep Power
    72

    Default

    You should try the magichdnite skin under the vix menu plugin. It looks really nice on a large screen, you'll be amazed at how much more fits on the screen and how crisp it looks compared to the older magichd skins.

  15. #14
    Senior Member
    Join Date
    Aug 2009
    Posts
    261
    Thanks
    43
    Thanked 185 Times in 95 Posts
    Rep Power
    18

    Default

    just to let you guys know as BH have released a series of beta images with the linux 3.1.1 kernel, we in ViX are also currently testing the 3.1.1 linux kernel with the Vu receivers and will let you know as soon as it's ready to release.


    this should bring a lot more compatibility for the likes of USB tuners etc direct to the box.

  16. The Following User Says Thank You to DUDE For This Useful Post:

    weirdo (14-12-11)

  17. #15
    Senior Member omega99's Avatar
    Join Date
    Feb 2008
    Posts
    596
    Thanks
    53
    Thanked 48 Times in 34 Posts
    Rep Power
    19

    Default

    nebody tried the Vix 2.3 240 updated image to see if the sundtek issue remains
    woteva

  18. #16
    Senior Member AJM's Avatar
    Join Date
    Jan 2008
    Posts
    170
    Thanks
    83
    Thanked 33 Times in 23 Posts
    Rep Power
    11

    Default

    Quote Originally Posted by omega99 View Post
    nebody tried the Vix 2.3 240 updated image to see if the sundtek issue remains
    I don't have a sundtek, but I can report that the 204 build (Vix 2.3) has fixed my dtt (Avermedia Twinstar a825 based on af9035 chipset). Prior to this build, ViX dtt was unstable and would run out of memory after being left on a terrestrial channel for several hours. Also, the signal strength and SNR are now reported (previously not).

    YMMV, but this build has been a massive improvement for dtt support for me
    Last edited by AJM; 31-01-12 at 01:55 AM.

  19. #17
    Premium Member
    Join Date
    May 2009
    Posts
    54
    Thanks
    9
    Thanked 40 Times in 17 Posts
    Rep Power
    8

    Default

    Just thought I would post in my results.

    I have a Sundtek tuner that worked fantastic on Vix 2.2.

    Upgraded to 2.3 Build 153, and my experiances were pretty much the same as everyone else.

    While it worked most of the time it was glitchy, sometimes would error with a "could not tune" message when I selected a terresterial channel, and caused the box to crash every now and then while watching terresterial channels.

    I upgraded to Build 204 the other day through online update and so far the terresterial TV experiance has improved greatly.

    Has not glitched, or crashed so far while tuning or watching a terresterial channel.

    I will keep experementing though and see how it goes longer term.

  20. #18
    Senior Member AJM's Avatar
    Join Date
    Jan 2008
    Posts
    170
    Thanks
    83
    Thanked 33 Times in 23 Posts
    Rep Power
    11

    Default

    Quote Originally Posted by AJM View Post
    I don't have a sundtek, but I can report that the 204 build (Vix 2.3) has fixed my dtt (Avermedia Twinstar a825 based on af9035 chipset). Prior to this build, ViX dtt was unstable and would run out of memory after being left on a terrestrial channel for several hours. Also, the signal strength and SNR are now reported (previously not).

    YMMV, but this build has been a massive improvement for dtt support for me
    I've now upgraded the drivers to 26/01/2012.

    These drivers seem to make the DTT usb tuners hang in there. So far rock solid.

    cheers

  21. #19
    Senior Member omega99's Avatar
    Join Date
    Feb 2008
    Posts
    596
    Thanks
    53
    Thanked 48 Times in 34 Posts
    Rep Power
    19

    Default

    I wonder if they have solved the issue with the sundtek, might have to ditch vti4 & go back to vix
    woteva

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •