266 replies to this topic

[Pietjebel10]

Oscam ==> Oscam camd35

[robbedoeske]

En nog steeds stabiel?

[ronh]

Ik heb nu al even gedraaid met Blackhole zonder problemen... Met één adapter. Met 2 adapters wil het niet lukken. Ik had de afgelopen geen tijd om iets te doen (en ja, het werkte toch). Maar nu heb ik tijd, en wil ik toch beide Sundtek adapters gaan gebruiken. Begrijp ik nu uit dit draadje dat je dan beter geen OpenPli kunt gebruiken, maar beter de VTi image? Ik heb geen ervaring met VTi.
PS: Ik gebruik de schotel helemaal niet meer, ik kijk alleen nog via de kabel.

[ronh]

Hmm, ik heb nu de laatste update van OpenPli erop staan, met de laatste drivers van Sundtek, en hij hangt om de haverklap. Ik wordt er niet goed van.
Heeft iemand een goede config (OpenPli versie, en versie drivers) om met OpenPli op een VU+Duo icm 2 Sundtek adapters te werken?

[robbedoeske]

Vergeet Openpli i.s.m. met Sundtek. Is niet stabiel te krijgen,het lijkt wel of het met oscam iets beter gaat,maar ben toch steeds weer terug naar VTI. Is welliswaar ook niet 100% stabiel maar werkt meestal wel.

[sundtek]

Hmm, ik heb nu de laatste update van OpenPli erop staan, met de laatste drivers van Sundtek, en hij hangt om de haverklap. Ik wordt er niet goed van.
Heeft iemand een goede config (OpenPli versie, en versie drivers) om met OpenPli op een VU+Duo icm 2 Sundtek adapters te werken?

your problem is related to the Powersupply. It seems like the VU+ Settopbox shares 500mA on both ports which is not USB 2.0 conform. You might try to use an active USB hub.
We saw in the logfile that the USB Controller cuts off the second tuner, Enigma does not support tuner hotplugging so it crashes.
Alternatively you can use the tuners via Network, in order to "outsource" the power issue.

Vergeet Openpli i.s.m. met Sundtek. Is niet stabiel te krijgen,het lijkt wel of het met oscam iets beter gaat,maar ben toch steeds weer terug naar VTI. Is welliswaar ook niet 100% stabiel maar werkt meestal wel.

if you experience a problem report it and we can check it. The driver is proven to be stable, the only issue that might arise comes from the local vu+ modules. Just like the previous issue where the USB 2.0 power for 2 DVB-C/T Sticks is not enough. I even think someone already reported that in the past, that a second USB tuner only might work on the front USB port(?). Alternatively as mentioned an active USB hub or moving the tuner to an external system might be a workaround.

Edited by sundtek, 30 September 2012 - 18:34.

[robbedoeske]

@SundTek Probleem van het schakelen tussen cable en sat zit er nog steeds in,het resulteerd steevast in een zwart scherm met de melding "sid not found in pat"
en alleen een reboot helpt. Ik heb dus een VU duo met CCcam ,het lijkt met Oscam iets langer te gaan maar ook niet stabiel.

Edited by robbedoeske, 30 September 2012 - 19:06.

[sundtek]

@SundTek Probleem van het schakelen tussen cable en sat zit er nog steeds in,het resulteerd steevast in een zwart scherm met de melding "sid not found in pat"
en alleen een reboot helpt. Ik heb dus een VU duo met CCcam ,het lijkt met Oscam iets langer te gaan maar ook niet stabiel.

Can you contact us via Skype? "sundtek"
At least we can check and see what's going on to nail down where the problem is.

Edited by sundtek, 30 September 2012 - 19:24.

[robbedoeske]

Heb geen Skype op het moment,maar zal es zien of ik dat kan installeren.

[ronh]

your problem is related to the Powersupply. It seems like the VU+ Settopbox shares 500mA on both ports which is not USB 2.0 conform. You might try to use an active USB hub.
We saw in the logfile that the USB Controller cuts off the second tuner, Enigma does not support tuner hotplugging so it crashes.
Alternatively you can use the tuners via Network, in order to "outsource" the power issue.

<cut>

Just like the previous issue where the USB 2.0 power for 2 DVB-C/T Sticks is not enough. I even think someone already reported that in the past, that a second USB tuner only might work on the front USB port(?). Alternatively as mentioned an active USB hub or moving the tuner to an external system might be a workaround.

I've ran the latest update of OpenPli 3.0 on my VUDuo now for a week with one Sundtek adapter, and experienced no hangs. So now I've ordered an active USB hub to test it with 2 adapters.

Keep you posted.

[sundtek]

your problem is related to the Powersupply. It seems like the VU+ Settopbox shares 500mA on both ports which is not USB 2.0 conform. You might try to use an active USB hub.
We saw in the logfile that the USB Controller cuts off the second tuner, Enigma does not support tuner hotplugging so it crashes.
Alternatively you can use the tuners via Network, in order to "outsource" the power issue.

<cut>

Just like the previous issue where the USB 2.0 power for 2 DVB-C/T Sticks is not enough. I even think someone already reported that in the past, that a second USB tuner only might work on the front USB port(?). Alternatively as mentioned an active USB hub or moving the tuner to an external system might be a workaround.

I've ran the latest update of OpenPli 3.0 on my VUDuo now for a week with one Sundtek adapter, and experienced no hangs. So now I've ordered an active USB hub to test it with 2 adapters.

Keep you posted.

that's fixed, a special update which is required for the dreambox caused that on vu (and other) boxes, we hope that the middle way will keep all boxes stable now. Unfortunately it took at least 3 attempts to find a mechanism to work around the actual problem so we can serve the options dream needs and ignore it on other boxes.

[ronh]

that's fixed, a special update which is required for the dreambox caused that on vu (and other) boxes, we hope that the middle way will keep all boxes stable now. Unfortunately it took at least 3 attempts to find a mechanism to work around the actual problem so we can serve the options dream needs and ignore it on other boxes.

@Sundtek: What is fixed? Can I run 2 adapters on a VUDuo without an active USB hub? (Just a little to late, I've allready ordered and paid the hub) Have you released new drivers for the adapters? Where can we find them (Link?).

[sundtek]

that's fixed, a special update which is required for the dreambox caused that on vu (and other) boxes, we hope that the middle way will keep all boxes stable now. Unfortunately it took at least 3 attempts to find a mechanism to work around the actual problem so we can serve the options dream needs and ignore it on other boxes.

@Sundtek: What is fixed? Can I run 2 adapters on a VUDuo without an active USB hub? (Just a little to late, I've allready ordered and paid the hub) Have you released new drivers for the adapters? Where can we find them (Link?).

In your case the second adapter disappeared from the system due a USB reset.
One DVB-C dongle requires around 300-350mA in DVB-C mode, 2 Sticks would require 600-700mA on your system, VU+ DUo shares 500mA on 2 ports (official USB 2.0 spec is 500mA on each port)
The USB Hub should be a try on your side,
Another way would be to outsource the tuners (eg use it with a linux NAS, Seagate Dockstar or other system) and use the adapter via network (the driver has full network support integrated, server and client), that way the tuner can be decoupled from USB on the VU+ (and also be used from other systems eg. windows in your network).

Edited by sundtek, 12 October 2012 - 02:00.

[jongbj]

Another way would be to outsource the tuners (eg use it with a linux NAS, Seagate Dockstar or other system) and use the adapter via network (the driver has full network support integrated, server and client), that way the tuner can be decoupled from USB on the VU+ (and also be used from other systems eg. windows in your network).

Am I reading this right when I think that would allow one tuner to be used on both a Vu+ and DM500hd without having to switch? Of course not simultaneously.

[robbedoeske]

your problem is related to the Powersupply. It seems like the VU+ Settopbox shares 500mA on both ports which is not USB 2.0 conform. You might try to use an active USB hub.
We saw in the logfile that the USB Controller cuts off the second tuner, Enigma does not support tuner hotplugging so it crashes.
Alternatively you can use the tuners via Network, in order to "outsource" the power issue.

<cut>

Just like the previous issue where the USB 2.0 power for 2 DVB-C/T Sticks is not enough. I even think someone already reported that in the past, that a second USB tuner only might work on the front USB port(?). Alternatively as mentioned an active USB hub or moving the tuner to an external system might be a workaround.

I've ran the latest update of OpenPli 3.0 on my VUDuo now for a week with one Sundtek adapter, and experienced no hangs. So now I've ordered an active USB hub to test it with 2 adapters.

Keep you posted.

that's fixed, a special update which is required for the dreambox caused that on vu (and other) boxes, we hope that the middle way will keep all boxes stable now. Unfortunately it took at least 3 attempts to find a mechanism to work around the actual problem so we can serve the options dream needs and ignore it on other boxes.

Toch maar weer een poging met openpli en de volgende drivers: sundtek_installer_121010.220349.sh
resultaat,1 keer zappen van kabel naar sat en weer naar kabel levert een zwart scherm met de melding: geen data op transponder "timeout reading pat"
Er is dus helemaal niks gefixed.

[littlesat]

Met welke versie op de VU???

[robbedoeske]

De laatse openpli op een VU DUO met de genoemde drivers van sundtek

[Frenske]

@ Robbedoeske.

Dan lijkt het mij een goed plan om dit in het Engelse deel van het PLi forum met Sundtek aan te kaarten.
Daarmee blijft dit deel schoon en kan je naar hartelust met hem daarover debatteren.

[robbedoeske]

Ik snap niet waarom dit in het engelse deel moet,het schijnt een groot probleem te zijn PLI en Sundtek.

[robbedoeske]

Oke ik heb enigma gestopt met init 4 en weer gestart met enigma2.
Zie bijlage misschien kunnen jullie hier iets mee.
Oke bijlage lukt niet dan maar zo:


DMX_SET_PES_FILTER(0x1839) - video - ok
DEMUX_START - video - ok
VIDEO_FREEZE - ok
VIDEO_PLAY - ok
VIDEO_SLOWMOTION(0) - ok
VIDEO_FAST_FORWARD(0) - ok
VIDEO_CONTINUE - ok
AUDIO_CONTINUE - ok
disable teletext subtitles
not pauseable.
[eDVBCAService] new service 1:0:19:EF:13:3E8:FFFF0000:0:0:0:
[eDVBCAService] add demux 0 to slot 0 service 1:0:19:EF:13:3E8:FFFF0000:0:0:0:
[eDVBCIInterfaces] gotPMT
[EPGC] start caching events(1350046785)
[eDVBLocalTimerHandler] diff is 1
[eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
[eDVBLocalTimerHandler] update RTC
[eDVBLocalTimerHandler] time update to 14:59:47
[eDVBLocalTimerHandler] m_time_difference is 1
[eDVBLocalTimerHandler] set Linux Time
[EPGC] abort non avail nownext reading
[EPGC] abort non avail schedule reading
[EPGC] abort non avail schedule other reading
[EPGC] abort non avail netmed schedule reading
[EPGC] abort non avail netmed schedule other reading
[EPGC] abort non avail FreeSat schedule_other reading
[EPGC] abort non avail viasat reading
action -> InfobarChannelSelection switchChannelDown
action -> OkCancelActions ok
playing 1:0:19:D2:19:3E8:FFFF0000:0:0:0:
[eDVBCAService] free slot 0 demux 0 for service 1:0:19:EF:13:3E8:FFFF0000:0:0:0:
[eDVBCAService] free service 1:0:19:EF:13:3E8:FFFF0000:0:0:0:
decoder state: play, vpid=-1, apid=-1
DEMUX_STOP - pcr - ok
DEMUX_STOP - video - ok
VIDEO_STOP - ok
AUDIO_STOP - ok
DEMUX_STOP - audio - ok
AUDIO_CONTINUE - ok
cleaning up
TuxTxt cache cleared
start release channel timer
not pauseable.
RemovePopup, id = ZapError
[eDVBLocalTimerHandler] remove channel 0x168c980
[eEPGCache] remove channel 0x168c980
allocate channel.. 0019:03e8
(2)tune
tuning to 578000 khz, sr 6875000, fec 0, modulation 3, inversion 2
OURSTATE: tuning
allocate Channel: res 0
[eDVBCIInterfaces] addPMTHandler 1:0:19:D2:19:3E8:FFFF0000:0:0:0:
allocate demux
[SEC] startTuneTimeout 5000
[SEC] setFrontend 1
setting frontend 2
(2)fe event: status 0, inversion on, m_tuning 1
[DVBCAHandler] no more services
(2)fe event: status 1f, inversion off, m_tuning 2
OURSTATE: ok
[eDVBLocalTimerHandler] channel 0x168c980 running
[eEPGCache] channel 0x168c980 running
stop release channel timer
ok ... now we start!!
eventNewProgramInfo 0 0
[EPGC] next update in 2 sec
have 1 video stream(s) (00a1), and 1 audio stream(s) (00a2), and the pcr pid is 00a1, and the text pid is 00ae
allocate demux
TuxTxt cache cleared
decoder state: play, vpid=161, apid=162
DMX_SET_PES_FILTER(0xa1) - pcr - ok
DEMUX_START - pcr - ok
DMX_SET_PES_FILTER(0xa2) - audio - ok
DEMUX_START - audio - ok
AUDIO_SET_BYPASS(1) - ok
AUDIO_PAUSE - ok
AUDIO_PLAY - ok
Video Device: /dev/dvb/adapter0/video0
demux device: /dev/dvb/adapter0/demux0
VIDEO_SET_STREAMTYPE 1 - ok
DMX_SET_PES_FILTER(0xa1) - video - ok
DEMUX_START - video - ok
VIDEO_FREEZE - ok
VIDEO_PLAY - ok
DMX_SET_PES_FILTER(0xae) - ttx - ok
DEMUX_START - ttx - ok
TuxTxt cache cleared
TuxTxt: initialized
TuxTxt service started ae
VIDEO_SLOWMOTION(0) - TuxTxt running thread...(0ae)
ok
VIDEO_FAST_FORWARD(0) - ok
VIDEO_CONTINUE - ok
AUDIO_CONTINUE - ok
disable teletext subtitles
not pauseable.
[eDVBCAService] new service 1:0:19:D2:19:3E8:FFFF0000:0:0:0:
[eDVBCAService] add demux 0 to slot 0 service 1:0:19:D2:19:3E8:FFFF0000:0:0:0:
[eDVBLocalTimerHandler] diff is -2
[eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
[eDVBLocalTimerHandler] update RTC
[eDVBLocalTimerHandler] time update to 14:59:59
[eDVBLocalTimerHandler] m_time_difference is -2
[eDVBLocalTimerHandler] set Linux Time
PATready
use pmtpid 0036 for service_id 00d2
eventNewProgramInfo 0 0
have 1 video stream(s) (00a1), and 2 audio stream(s) (00a2, 00a3), and the pcr pid is 00a1, and the text pid is 00ae
decoder state: play, vpid=161, apid=162
[eDVBCIInterfaces] gotPMT
[eDVBCAService] don't build/send the same CA PMT twice
[EPGC] start caching events(1350046800)
action -> InfobarChannelSelection switchChannelDown
action -> ChannelSelectBaseActions showFavourites
action -> OkCancelActions ok
[EPGC] abort non avail nownext reading
[EPGC] abort non avail schedule reading
[EPGC] abort non avail schedule other reading
[EPGC] abort non avail netmed schedule reading
[EPGC] abort non avail netmed schedule other reading
[EPGC] abort non avail FreeSat schedule_other reading
[EPGC] abort non avail viasat reading
action -> OkCancelActions ok
playing 1:0:19:1B7B:C88:3:EB0000:0:0:0:
[eDVBCAService] free slot 0 demux 0 for service 1:0:19:D2:19:3E8:FFFF0000:0:0:0:
[eDVBCAService] free service 1:0:19:D2:19:3E8:FFFF0000:0:0:0:
decoder state: play, vpid=-1, apid=-1
DEMUX_STOP - pcr - ok
DEMUX_STOP - video - ok
VIDEO_STOP - ok
AUDIO_STOP - ok
DEMUX_STOP - audio - ok
AUDIO_CONTINUE - ok
DEMUX_STOP - ttx - ok
TuxTxt stopped service ae
cleaning up
TuxTxt cache cleared
start release channel timer
not pauseable.
RemovePopup, id = ZapError
[eDVBLocalTimerHandler] remove channel 0x168c980
[eEPGCache] remove channel 0x168c980
allocate channel.. 0c88:0003
opening frontend 0
FE_ENABLE_HIGH_LNB_VOLTAGE: Operation not supported
(0)tune
Entry for 23,5? not in Rotor Table found... i try gotoXX?
siteLatitude = 53.109001, siteLongitude = 7.010000, 23.500000 degrees
PolarmountHourAngle=161.895586
RotorCmd = e122
RotorCmd e122, lastRotorCmd e122
prepare_sat System 1 Freq 11856000 Pol 1 SR 27500000 INV 2 FEC 4 orbpos 235 system 1 modulation 1 pilot 2, rolloff 1
tuning to 1256 mhz
OURSTATE: tuning
allocate Channel: res 0
[eDVBCIInterfaces] addPMTHandler 1:0:19:1B7B:C88:3:EB0000:0:0:0:
allocate demux
[SEC] set static current limiting
[SEC] setVoltage 1
FE_ENABLE_HIGH_LNB_VOLTAGE: Operation not supported
[SEC] sleep 10ms
[SEC] setTone 1
[SEC] sleep 10ms
[SEC] update current switch params
[SEC] startTuneTimeout 5000
[SEC] setFrontend 1
setting frontend 0
(0)fe event: status 0, inversion on, m_tuning 1
[SEC] sleep 500ms
(0)fe event: status 1f, inversion on, m_tuning 2
OURSTATE: ok
[eDVBLocalTimerHandler] channel 0x74dff4a8 running
[eEPGCache] channel 0x74dff4a8 running
[EPGC] next update in 2 sec
stop release channel timer
ok ... now we start!!
eventNewProgramInfo 0 0
have 1 video stream(s) (0205), and 1 audio stream(s) (005c), and the pcr pid is 0205, and the text pid is 0024
allocate demux
TuxTxt cache cleared
decoder state: play, vpid=517, apid=92
DMX_SET_PES_FILTER(0x205) - pcr - ok
DEMUX_START - pcr - ok
DMX_SET_PES_FILTER(0x5c) - audio - ok
DEMUX_START - audio - ok
AUDIO_SET_BYPASS(0) - ok
AUDIO_PAUSE - ok
AUDIO_PLAY - ok
Video Device: /dev/dvb/adapter0/video0
demux device: /dev/dvb/adapter0/demux0
VIDEO_SET_STREAMTYPE 1 - ok
DMX_SET_PES_FILTER(0x205) - video - ok
DEMUX_START - video - ok
VIDEO_FREEZE - ok
VIDEO_PLAY - ok
DMX_SET_PES_FILTER(0x24) - ttx - ok
DEMUX_START - ttx - ok
TuxTxt cache cleared
TuxTxt: initialized
TuxTxt service started 24
TuxTxt running thread...(024)
VIDEO_SLOWMOTION(0) - ok
VIDEO_FAST_FORWARD(0) - ok
VIDEO_CONTINUE - ok
AUDIO_CONTINUE - ok
disable teletext subtitles
not pauseable.
[eDVBCAService] new service 1:0:19:1B7B:C88:3:EB0000:0:0:0:
[eDVBCAService] add demux 0 to slot 0 service 1:0:19:1B7B:C88:3:EB0000:0:0:0:
[SEC] set dynamic current limiting
PATready
use pmtpid 09e7 for service_id 1b7b
eventNewProgramInfo 0 0
have 1 video stream(s) (0205), and 1 audio stream(s) (005c), and the pcr pid is 0205, and the text pid is 0024
decoder state: play, vpid=517, apid=92
[eDVBCIInterfaces] gotPMT
[EPGC] start caching events(1350046811)
main thread is non-idle! display spinner!

Edited by robbedoeske, 12 October 2012 - 14:07.