diseqc problems (emp 9/1 V1)

OldSkulRide · 8. März 2010, 14:24

Ok, today i got brand new EMP 9/1 V1 switch.
Now i have same problems...
Iam using this setup:

1. AA on uncommitted switch 1
2. AB on 1
3. BA on 1
4. BB on 1

the next 4 would be

5. AA on uncommitted switch 2
6. AB on 2
7. BA on 2
8. BB on 2

I also turned on "repeat sequence"

First four sats work superb, two sats that are on port 5 and 7, dont work too good. Sometimes diseqc will switch to that sat, sometimes not. Usually not.

I have a feeling that vu+ has some diseqc problems...

RealMagic911 · 8. März 2010, 14:25

We alreade hat different posts here, Diseq 1.1 not properbly working. I think we will add it to the known bugs list and report it to the developers.

OldSkulRide · 8. März 2010, 14:30

yep, vuplus developers need to look at this

Thanks for info

kaneguru · 8. März 2010, 15:20

Originally posted by OldSkulRide
Ok, today i got brand new EMP 9/1 V1 switch.
Now i have same problems...
Iam using this setup:

1. AA on uncommitted switch 1
2. AB on 1
3. BA on 1
4. BB on 1

the next 4 would be

5. AA on uncommitted switch 2
6. AB on 2
7. BA on 2
8. BB on 2

I also turned on "repeat sequence"

First four sats work superb, two sats that are on port 5 and 7, dont work too good. Sometimes diseqc will switch to that sat, sometimes not. Usually not.

I have a feeling that vu+ has some diseqc problems...

hi ,i have also this problem.
try this one,scan LNB5 ,you should found any transponders.
LNB6 to 8 scan also on LNB5,if the frequency are the same.

OldSkulRide · 8. März 2010, 18:07

Iam not scanning channels, iam using already built lists.

Also anyone noticed that receiver becomes slow when there is no signal on channel?
I noticed this several times.

Diseqc function isnt well implemented, especially 1.1 version.

OldSkulRide · 9. März 2010, 13:41

just to inform you guys. 1.2 diseqc on emp 9/1 works great.

Apperantly EMP 9/1 isnt 100% compatible with vu+ duo. 1.1 diseqc should be revised.

tonskidutch · 9. März 2010, 13:47

probably similar as this setting which I pinched from satmann
LNB1
****
Satelliet : 13E
LNB : LNB1
Prioriteit : Auto
LOF : universele usb
Spanningsmodus : Polarisatie
Verhoogd Voltage = nee
Tone modus : Band
Diseqc-modus : 1.1
Toneburst : Geen
Committed Diseqc commando : geen
Snelle Diseqc : nee
herhaal sequence : nee
Commando volgorde : uncommitted, committed,toneburst
Unicommited Diseqc commando : Input1
Diseqc herhaling : Geen

en dan voor lnb2:
LNB1
****
Satelliet : 19E
LNB : LNB2
Prioriteit : Auto
LOF : universele usb
Spanningsmodus : Polarisatie
Verhoogd Voltage = nee
Tone modus : Band
Diseqc-modus : 1.1
Toneburst : Geen
Committed Diseqc commando : geen
Snelle Diseqc : nee
herhaal sequence : nee
Commando volgorde : uncommitted, committed,toneburst
Unicommited Diseqc commando : Input2
Diseqc herhaling : Geen

and so on

ciao

malakudi · 9. März 2010, 14:49

I don't have diseqc 1.1 but a friend of mine has VU+ HD Duo with one Spaun diseqc 1.1 switch which drives four Spaun diseqc 2.0 switches, for a total of 16 LNBs, and he has no problems with this setup.

So it is more of a problem with EMP Centauri than diseqc 1.1 in general.

tonskidutch · 9. März 2010, 15:04

the emp centauri has an update procedure
regarding the correct diseqc protocol used
see the manufacturors website.
ciao

OldSkulRide · 9. März 2010, 15:26

Originally posted by malakudi
I don't have diseqc 1.1 but a friend of mine has VU+ HD Duo with one Spaun diseqc 1.1 switch which drives four Spaun diseqc 2.0 switches, for a total of 16 LNBs, and he has no problems with this setup.

So it is more of a problem with EMP Centauri than diseqc 1.1 in general.

Forget Spaun. do you know how expensive is this?
I have one 4x1 Spaun and thats enough.

For second tuner iam using emp 9/1 V1 which apperantly isnt compatible with vu+ duo when using 1.1
When using 1.2 everything works ok. For Spaun switches is known they they are resistent to poor disecq 1.1 implementations.

@tonskidutch:
This settings are for EMP 9/1 V2 version, not for V1 version

malakudi · 9. März 2010, 15:43

Originally posted by OldSkulRide
Forget Spaun. do you know how expensive is this?
I have one 4x1 Spaun and thats enough.

For second tuner iam using emp 9/1 V1 which apperantly isnt compatible with vu+ duo when using 1.1
When using 1.2 everything works ok. For Spaun switches is known they they are resistent to poor disecq 1.1 implementations.

This is just a different point of view. You say that Spaun switches are resistent to poor diseqc 1.1 implementations. This can also be interpreted as "EMP Centauri 9/1 is not fully compatible with diseqc 1.1 standard", since VU+ HD Duo works great with Spaun, which is a diseqc 1.1 switch.

VU+ driver developers should check this incompatibility, but it's not an incompatibility with diseqc 1.1 in general. It is an incompatibility with a specific diseqc 1.1 switch from a specific manufacturer.

I had a similar issue with my IPBOX 9000HD. It was incompatible with Superjack V-BOX diseqc 1.2 positioner. All other receivers were working fine with Superjack, IPBOX was not. IPBOX manufacturer kept blaming Superjack for this, since their implementation was working fine with other diseqc 1.2 positioners. Issue was never fixed by IPBOX manufacturer.

tonskidutch · 9. März 2010, 15:44

OOPS,

V2 version, not for V1 version

just missed it reading was oké but didn't snap.
sorry

spearkie · 9. März 2010, 17:06

B/ Setting according to DiSEqC 1.1 protocol
If your receiver supports DiSEqC 1.1 protocol, set appropriate data in the fields for “uncommitted switch” and “committed switch” for each
of the connected LNB in the configuration menu.

Setting differs for switch V1 and V2:
V1

SAT 1 IN: com 1 (A) uncom 1 (A)
SAT 2 IN: com 2 (B) uncom 1 (A)
SAT 3 IN: com 3 (C) uncom 1 (A)
SAT 4 IN: com 4 (D) uncom 1 (A)
SAT 5 IN: com 1 (A) uncom 2 (B)
SAT 6 IN: com 2 (B) uncom 2 (B)
SAT 7 IN: com 3 (C) uncom 2 (B)
SAT 8 IN: com 4 (D) uncom 2 (B)

Please check your settings.

I think it is too simple to make VU+ responsible for a bad Disecq configuration.

OldSkulRide · 9. März 2010, 17:40

Check my first post. Settings that i used are correct settings for emp v1 switch. I also checked several forums.

LNB 1 - Diseqc Committed AA - Uncommitted input 1
LNB 2 - Diseqc Committed AB - Uncommitted input 1
LNB 3 - Diseqc Committed BA - Uncommitted input 1
LNB 4 - Diseqc Committed BB - Uncommitted input 1
LNB 5 - Diseqc Committed AA - Uncommitted input 2
LNB 6 - Diseqc Committed AB - Uncommitted input 2
LNB 7 - Diseqc Committed BA - Uncommitted input 2
LNB 8 - Diseqc Committed BB - Uncommitted input 2

Maybe there is also some different config possible i dont know.

Too bad no one has EMP V1...

OldSkulRide · 19. März 2010, 12:20

any improvement with new drivers?

RealMagic911 · 19. März 2010, 12:25

Yes Diseq Timing is improved with new drivers.

-> 2. Adjust DiseqC message timing

OldSkulRide · 25. März 2010, 11:00

I changed from 1.2 back to diseqc 1.1 and now it works

RealMagic911 · 25. März 2010, 12:08

Thanks for Acknowledge!

OldSkulRide · 26. März 2010, 11:06

i was too quick. 1.1 still causing troubles...
Back to 1.2

RealMagic911 · 26. März 2010, 11:07

Ca you describe the current problems and the difference to the old image. Maybe it would be usefull to report the changes to Vu+

diseqc problems (emp 9/1 V1)

diseqc problems (emp 9/1 V1)

RE: diseqc problems (emp 9/1 V1)

RE: diseqc problems (emp 9/1 V1)