Page 1 of 2
DISEqC settings problem
Posted: Sun Mar 15, 2009 7:20 pm
by Flanders Sat Freak
Hello,
I have used ProgDVB successfully in the past on my laptop.
I'm using USB Settopbox from TECHNOTREND TT CONNECT S2-3650 CI
and it used to work fine on the laptop.
Now I bought a new desktop PC and installed ProgDVB 6.05
and there's trouble?!
-->There seems to be a problem with my diseqc settings on startup :
For an unknown reason I cannot seem to
select "none" in this menu (and I think it has to be this one from when I used it on my laptop)
Only "custom" is an option and when I press OK it does nothing?!
--> I'm forced to press "CANCEL" to continue...
I selected the Eurobird 1 Astra 2a, 2b,2c, 2d satellite because my antenna is pointed to this sat.
ProgDVB detects my Technotrend settopbox,
but the problem remains...
--> Why can't I select "none" in this diseqc menu??????????????
PLEASE HELP, coz I wanna start using PROGDVB again on my new PC;
I think it's the best program so I wanna fix this problem...
THXXXX a lot!
Grtz from Flanders, Belgium
J.K.
.
Posted: Sun Mar 15, 2009 7:30 pm
by Prog
ProgDVB show this dialog if you not setup providers for all your devices.
I have the same Problem
Posted: Thu Mar 26, 2009 6:48 pm
by Dampfnudel
First of all: Thank you for this great program. But i have one problem too:
The Diseqc settings appear every time i start the program. and i cant add lnbs or something. Where do i have to set these providers u mean?
The following picture shows what i can do:
Im running technotrend in soft mode.
Thank you for any help.
Best regards
Andreas / Germany
.
Posted: Thu Mar 26, 2009 7:02 pm
by Prog
You must config IPTV device also.
Posted: Fri Apr 03, 2009 7:06 am
by KouDy
Hello,
i'll use this topic rather than creating new one.
I think i have problems with DiseqC settings aswell.
I have monoblock, one part is for 23.5" (Astra 3A) and the other one is 28.2" (Astra 2). This is connected to Technisat SkyStar HD2 with CAM reader for some TVs that i have card for on 23.5" satelite.
When i do search for channels, i think most of (if not all) on Astra 2 are found, however channels on Astra 3 are not found, but it keeps giving me channels from Astra 2 into channel list of Astra 3.
Moreover i cannot change channel to anything from Astra Astra 3. Only Astra 2 channels work.
DiseqC i have set as 22kHz switch (2 ports).
I tried all others but nothing works..
Thanks for looking at this issue.
.
Posted: Fri Apr 03, 2009 7:31 am
by Prog
Check settings->Device options. Must be Azurewave
Posted: Fri Apr 03, 2009 7:58 am
by KouDy
I have AzureWave (TwinHan) there.
Posted: Fri Apr 03, 2009 9:35 pm
by Juergen
You MUST NOT set up for a 22kHz switch, as that control is essential and exclusive for band switching, over here in Europe.
22kHz control has to be done by (in your case default) LOF settings only, to enable high band access for both positions.
Either a tone burst (~ simple DiSEqC) switch or a (2 port) DiSEqC 1.0 switch is what you need to set up for, depending on that monoblock LNB you've got. RTFM...
Anyway, did you ever try that monoblock with any other tuner?
Does that LNB really come as dedicated for an angular distance of around 4.7°???
Else you will never be able to head towards both positions half way properly.
Most monoblocks are made for a spacing of around 6°, mainly intended for Astra 19.2°E and Hotbird 13°E. One degree does really matter a lot on satellite. RTFM again...
BTW, on most monoblocks (and according to Eutelsat defined DiSEqC specifications), the less eastern position comes first. Means, 23.5°E in fact is position A, 28.2°E is B. Except for people who use dishes with a sub reflector or for those who install dish or LNB upside down.
Posted: Fri Apr 03, 2009 10:33 pm
by KouDy
First i apparently live in Europe if i have dish directed to 23.5"E (Astra 3A) and 28.2"E (Astra 2A). I'm not sure what you meant by that 22kHz is exclusive for Europe.
Anyway i set up DiseqC 1.0 as it's by default in ProgDVB (meaning there are 4 positions, but i used only 2 of them) and it seems to work now.
If by other tuner you mean also TV set top box then the answer is yes (it's dual monoblock with 2 cables out of it one to PC and the other one to normal table top set top box so it wasn't anything wrong with that anyway, yea i could post that before, sorry i didn't realize).
Yes i have 23.5"E as first position and 28.2"E as second but i fail to see A and B option in ProgDVB (logicaly i only set Astra 3A as first in DiseqC, i'm not sure if this is intended as A).
Posted: Sun Apr 05, 2009 7:48 pm
by Juergen
Don't just read fragmentsof sentences...
KouDy wrote: I'm not sure what you meant by that 22kHz is exclusive for Europe.
I wrote:
"that control is essential and exclusive for band switching"
and
"over here in Europe. 22kHz control has to be done by (in your case default) LOF settings only, to enable high band access for both positions."
Anything left unclear with this???
KouDy wrote:it seems to work now.
Congrats
KouDy wrote: i'm not sure if this is intended as A).
Yes, of course.
The DiSEqC ports may be numbered, but this can cause misunderstandings, as some people count from 1 to 4, others from 0 to 3. Letters are precise in any case. A for the first of the four DiSEqC 1.0 ports, B for the second one and so on.
Posted: Mon Jul 20, 2009 10:08 pm
by KouDy
Sorry to bring all this up again.
I've done some PC cleanup and ait included reinstall of ProgDVB.
So now my problem is again with DiseqC. It doesn't matter which switch i will set, it doesn't work.
I have most of the 23.5"E channels up and runing (only those i have subscribed ofc). Channel search on 28.2"E gives me channels. I can switch to them, but all i can see is info in bottom line what program is currently running. No picture, no sound.
DiseqC settings as following :
I have no idea what should i change to get programs working. Obviously they are there because i know running program. But i can't watch them. That eventually leads me to idea DiseqC might be set correctly.
Posted: Tue Jul 21, 2009 6:26 am
by Juergen
Do you get good level / quality readings?
Did you have them before?
Anything else changed since April, like ProgDVB version, dish alignment or whateverelseintheworld...?
Anyway, you should have made a backup of your formerly working settings.
Why do we have to start everything from the very beginning again...
Posted: Tue Jul 21, 2009 12:27 pm
by KouDy
Juergen wrote:Do you get good level / quality readings?
Did you have them before?
Anything else changed since April, like ProgDVB version, dish alignment or whateverelseintheworld...?
Anyway, you should have made a backup of your formerly working settings.
Why do we have to start everything from the very beginning again...
Yes level and quality is good. Same as before.
Programs work ok on regular TV set top box. So dish is in the same position as before.
ProgDVB version changed yes. I use latest one (force of habit to update software i use).
I saw in patch notes there were some changes done to DiseqC recently, could that cause this issue?
Posted: Tue Aug 18, 2009 7:09 am
by KouDy
Hi all,
a bit of bump for this issue as it remains still valid for me, but i wanted to ask :
Now that new official driver from Technisat is out, what device in ProgDVB should one choose given fact of having Technisat SkyStar 2 HD? It was AzureWave before, should we move to Technisat now?
PS. I've installed older version of ProgDVB (6.03.04 to be specific), would you have any hints how to move on now to newer versions without losing one whole sattelite?
Posted: Tue Sep 15, 2009 8:36 am
by KouDy
Good news everyone. I've tried latest version (6.20.3) this weekend and the issue with DiseqC has been partially fixed!
What works now is that from version 6.04.03 i had all channels searched and saved and i can switch back and forth between satelites including also channels from my primary satelite which are coded and require access to CAM module with card. Problem is with sound on secondary satelite where it sttuters periodically (it's like very small lag of sound every 5 seconds). It's listenable yet very annoying which made me switch back to 6.04.03. I'm looking forward to new version where this will be hopefully fixed.