Sundtek Support Forum
Deutsch => {Single, Dual, Quad} Sundtek SkyTV Ultimate => Thema gestartet von: therock am April 23, 2011, 07:58:21 Nachmittag
-
Hey
i just installed my new Sundtek SkyTV Ultimate onto my xbmc linux box
with kernel Linux XBMCLive 2.6.32-26-generic #48-Ubuntu SMP Wed Nov 24 09:00:03 UTC 2010 i686 GNU/Linux
and the tone and all that is fine on normal SD channels
but when i want to watch a HD channel it gives a pixel picture and this is what i got from the log file
2011-04-23 19:52:38 [851] Packetsize < 188 bytes is invalid, throwing it away and increasing corruption
2011-04-23 19:52:38 [851] THERE MUST BE A BUG WITH YOUR HARDWARE, PLEASE CHECK ISO/BULK TRANSFER MODE
2011-04-23 19:52:38 [851] Packetsize < 188 bytes is invalid, throwing it away and increasing corruption
2011-04-23 19:52:38 [851] TS Sync byte not aligned, realigning stream (752)
2011-04-23 19:52:38 [851] skipped everything ...
2011-04-23 19:52:38 [851] TS Sync byte not aligned, realigning stream (376)
2011-04-23 19:52:38 [851] TS Sync byte not aligned, realigning stream (568)
2011-04-23 19:52:38 [851] TS Sync byte not aligned, realigning stream (564)
2011-04-23 19:52:38 [851] TS Sync byte not aligned, realigning stream (756)
2011-04-23 19:52:38 [851] skipped everything ...
2011-04-23 19:52:38 [851] TS Sync byte not aligned, realigning stream (564)
2011-04-23 19:52:38 [851] TS Sync byte not aligned, realigning stream (756)
2011-04-23 19:52:38 [851] skipped everything ...
2011-04-23 19:52:38 [851] THERE MUST BE A BUG WITH YOUR HARDWARE, PLEASE CHECK ISO/BULK TRANSFER MODE
2011-04-23 19:52:38 [851] Packetsize < 188 bytes is invalid, throwing it away and increasing corruption
2011-04-23 19:52:38 [851] THERE MUST BE A BUG WITH YOUR HARDWARE, PLEASE CHECK ISO/BULK TRANSFER MODE
2011-04-23 19:52:38 [851] Packetsize < 188 bytes is invalid, throwing it away and increasing corruption
2011-04-23 19:52:38 [851] THERE MUST BE A BUG WITH YOUR HARDWARE, PLEASE CHECK ISO/BULK TRANSFER MODE
2011-04-23 19:52:38 [851] Packetsize < 188 bytes is invalid, throwing it away and increasing corruption
2011-04-23 19:52:38 [851] TS Sync byte not aligned, realigning stream (188)
is there anything i can do?
-
What System do you use?
Are you using any graphic acceleration for HDTV?
Please provide some information about the CPU load (eg. screenshot of top on the console).
please note that decoding HDTV with the CPU can take a massive amount of CPU and steal it from the driver finally corrupting the datatransfer.
So far we advice to use NVidia Graphiccards for HDTV since they have mature support so far.
-
im on a zotac zbox id11 with a Intel Atom 1.6Ghz with nvidia ION2 with VDPAU
top - 21:14:22 up 2:49, 1 user, load average: 0.79, 0.86, 0.72
Tasks: 132 total, 1 running, 131 sleeping, 0 stopped, 0 zombie
Cpu(s): 8.9%us, 2.7%sy, 0.0%ni, 87.5%id, 0.1%wa, 0.2%hi, 0.6%si, 0.0%st
Mem: 1024868k total, 620136k used, 404732k free, 76828k buffers
Swap: 3108260k total, 0k used, 3108260k free, 327616k cached
2639 xbmc 20 0 138m 12m 5436 S 23 1.3 6:34.59 tvheadend
2943 xbmc 20 0 409m 128m 41m S 20 12.8 8:05.00 xbmc.bin
851 root 18 -2 106m 9.9m 6460 S 6 1.0 11:09.19 mediasrv
931 root 20 0 0 0 0 S 2 0.0 2:40.16 hd-audio1
2895 root 20 0 43172 32m 9752 S 1 3.2 0:25.65 Xorg
but yeah it looks like it can't manage the load but if i play a mkv HD movie it plays nicely
so its not that bad on cpu
-
We're still missing the BER (Bit error rate) reporting in the driver it should be available early next week, that should help to go further with that problem.
HDTV in general is no issue normally.
-
okay looking forward to that...
anyway if i mount it in a very powerfull pc with the same kernel it should work with HD channels right?
-
Let's check the statistics first.
-
okay but if i put the same cable in my sat i get a fine signal so i dont think it has anything todo with BER...?
-
is the BER reporting enabled or when will it be enabled in a new driver?
-
We are currently working on getting the Signal Strength into the driver, the problem is that specific part is missing from the information which we received from our chip dealer.
BER is basically no problem, we'll check it quickly tomorrow morning. Our main interest is the signal quality indicator.
-
We received all the necessary information this morning so it will be available very soon, also we've been told that the driver for the S2 chip component is outdated. We're going to update it completely asap.
-
Just to update this, we updated the BER but are still testing how usable those values are and finding some reference values by comparing it with different devices on the market.
Good for us the BER value is always low but question is how correct this is so more testing is needed, we only tested those values for one day so far so more work is needed.
One thing we noticed is that the F-Connector of the LNB cable is a major point of failure we have several different cables for testing - the cable itself does not matter but the connector. Cables with a high quality F-Connector never caused any change of the signal quality when moving or touching this part. Whereas cheap connectors which did not connect both items rock solid could cause a drop of signal quality of up to 30%.
-
hi therock, did you manage to get HD working? I seem to have the exact same issue:
http://support.sundtek.com/index.php/topic,651.0.html
-
we're looking at it (but please expect the answer in 1-2 days), we can't answer before we finish some testing with new devices.
The device overall should be fine but sensitivity might need to be improved of your stickversion, testresults will be available soon.
-
Ok, it has now been more than 1-2 days, whats the status?
-
We did some tests, basically if your LNB delivers a strong enough signal it should work without any problem.
However, we were working together with the tuner company within the last week and found a way to improve the sensitivity of our USB Stick. The sensitivity of the latest DVB-S/S2 stick is at least as good as with regular settopboxes (if not better). We also compared some other PCTV DVB-S/S2 devices (eg. TT S2-3650) and figured out that the latest revision (v3.5) has a much more sensitive tuner implementation now.
If you have purchased your tuner after 20. May we will replace the USB Stick for free with a new version, if not we will charge a small handling fee (basically shipping + 2 EUR handling) for upgrading the USB Stick, plus we need the old stick in return (only the USB Stick).
This upgrading option will only be available as long as devices are available at the beginning. Once the mass production has been finished in August it will be available until the end of 2011.
Rev 3.5:
* improved sensitivity
Rev 3.0:
* short circuit protection
* works without AC adapter with many active multiswitches
* faster inductor discharging (eg. when disconnecting AC adapter while stick is connected to an active multiswitch).
* stick shows up red light if something's wrong
-
I have 76% signal quality, should that be enough?
I ordered my stick 03.05.2011 19:53:59, order no 1946, however, it was not shipped untill mid-june..
-
Signal quality should be enough but we better replace the unit with a new one this month.
-
Ok i will email you!
-
Can you please send an email with your ordernumber to kontakt at sundtek de
-
done deal!
-
Hi i have received the new stick - and swapped it, too bad the same results (see attached logfile) i also tried to upgrade to the latest driver, same error (see logfile)
Anything else you want me to try?
with latest driver:
Logfile @ http://dl.dropbox.com/u/8760671/mediasrv.log
Br
Tobias
-
hi i just tryed the new 3.5 i got with the mail aswell and i have the same problems
2011-08-03 16:59:51 [902] found lock
2011-08-03 16:59:52 [902] voltage is low/0
2011-08-03 16:59:52 [902] Starting diseqc timing
2011-08-03 16:59:52 [902] diseqc len: 4/0
2011-08-03 16:59:53 [902] Diseqc execution time: 267 ms
2011-08-03 16:59:53 [902] diseqc send burst Modulated (SEC_MINI_B)
2011-08-03 16:59:53 [902] Starting tuning timing
2011-08-03 16:59:53 [902] Tuning DVB-S2 (QPSK) Transponder
2011-08-03 16:59:53 [902] USING FEC_3_4
2011-08-03 16:59:53 [902] roll off 035
2011-08-03 16:59:53 [902] LNB tone off
2011-08-03 16:59:53 [902] voltage is low
2011-08-03 16:59:53 [902] setting frequency: 1028000
2011-08-03 16:59:53 [902] setting symbolrate: 25000
2011-08-03 16:59:53 [902] using auto mode for this transponder
2011-08-03 16:59:53 [902] roll off 035
2011-08-03 16:59:53 [902] LNB tone off
2011-08-03 16:59:53 [902] voltage is low
2011-08-03 16:59:53 [902] setting frequency: 1028000
2011-08-03 16:59:53 [902] setting symbolrate: 25000
2011-08-03 16:59:54 [902] Tuning delay: 694 ms
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (463)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:54 [902] TS Sync byte not aligned, realigning stream (555)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (523)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (441)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (639)
2011-08-03 16:59:55 [902] skipped everything ...
2011-08-03 16:59:55 [902] found lock
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (429)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (677)
2011-08-03 16:59:55 [902] skipped everything ...
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (489)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (399)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (691)
2011-08-03 16:59:55 [902] skipped everything ...
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (0)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (192)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (385)
2011-08-03 16:59:55 [902] TS Sync byte not aligned, realigning stream (633)
-
We already figured out this issue and are testing some different components for it this week.
We mainly use Astra 19.2 / Hotbird for testing, those satellites have different requirements compared with eg. Thor5. Anyway more about this issue will be posted within the next 1-2 days. That issue mainly affects northern Europe (scandinavian Area as far as we could figure this out) so our current plan is to provide different S2 sticks for that region.
-
okay looking forward to getting this problem fixed
-
hi any news???
-
Working on adding the features of the central European stick to the stick which is compatible with Thor5/Scandinavia.
We'll send you the current engineering sample which already works with it as soon as we have the next cut (1-2 weeks) so you have something to play around with.
-
Small Update:
3 handmade samples are ready for the Scandinavian market which solve those issues, the devices will be shipped out at around mid next week.