Committed/ non committed?

sceh99

Member
My Satellite Setup
Humax 5000HD, two dishes, four LNBs
My Location
france
Can someone explain in words of one syllable what these terms mean and why the word is 'committed'? Committed to what?
I can't find an explanation anywhere which does not assume you already know the subject inside out.

thanks
 
Can someone explain in words of one syllable what these terms mean and why the word is 'committed'? Committed to what?
I can't find an explanation anywhere which does not assume you already know the subject inside out.

thanks
committed relationship = being faithful to partner.
 
committed relationship = being faithful to partner.
I think he meant in terms of a DiSEqC switch. :-rofl2

It's a question I've wondered about too, but never really looked into as I've not used multiple layers of switches.
 
I suspect it means that if you assign a number to the Diseqc switch port then you can fix this port to a certain satellite. If it is this easy, why don't they say so?
 
 
When used in combination, you can have up to 16x4 (64) LNBs under control of a single receiver/cable. That is, using a single DiSEqC 1.0 switch with 4 inputs and 4 DiSEqC 1.1 switches connected to each of those, containing 16 inputs.
 
When used in combination, you can have up to 16x4 (64) LNBs under control of a single receiver/cable. That is, using a single DiSEqC 1.0 switch with 4 inputs and 4 DiSEqC 1.1 switches connected to each of those, containing 16 inputs.
Unless things have moved on in the past few years, the maximum number of inputs that could be worked on a DiSEqC only switched network was 32. (8 x 4)
 
Officially, in the DiSEqC protocol, uncommitted commands take precedence over committed commands... although some software offers the option to reverse this.

So, you can use a 16x1 DiSEqC 1.1 switch and place a 4x1 DiSEqC 1.0/2.0 switch between each input, resulting in 16x4 = 64 inputs.
 
Officially, in the DiSEqC protocol, uncommitted commands take precedence over committed commands... although some software offers the option to reverse this.

So, you can use a 16x1 DiSEqC 1.1 switch and place a 4x1 DiSEqC 1.0/2.0 switch between each input, resulting in 16x4 = 64 inputs.
Thanks.

So, somewhere there is a functional switch (or installation) with more than 32 inputs using unofficial DiSEqC protocol.
 
Officially, in the DiSEqC protocol, uncommitted commands take precedence over committed commands...

Well, it is not so rigid, I believe. Many things are "recommended" for implementation, in their documents.

In total, you can indeed service 4x16 = 64 universal LNBs with diseqc 1.0 and diseqc 1.1.

Add 16/1 diseqc 1.2 switches (readily available for the consumer market, e.g. the EMP Centauri), and you can service 16x64 = 1024 individual universal LNBs with regular diseqc commands/equipment.
All using official Diseqc protocol, as far as I am concerned.

Greetz,
A33
 
Last edited:
Well, it is not so rigid, I believe. Many things are "recommended" for implementation, in their documents.

In total, you can indeed service 4x16 = 64 universal LNBs with diseqc 1.0 and diseqc 1.1.

Add 16/1 diseqc 1.2 switches (readily available for the consumer market, e.g. the EMP Centauri), and you can service 16x64 = 1024 individual universal LNBs with regular diseqc commands/equipment.
All using official Diseqc protocol, as far as I am concerned.

Greetz,
A33
It is certainly not a matter of "taking preference". committed and uncommitted simply address different switch types, which is essential in
order to "cascade" switches. Two of the same type can never be cascaded.
 
It is certainly not a matter of "taking preference". committed and uncommitted simply address different switch types, ...

That is absolutely right.
But, the word used by @Marcus_21 was "take precedence over", which I interpreted as "comes before", as in the order of commands.

The order of commands should basically follow the order of the actual physical setup.
Though it would be very logical to use the order first uncommitted switch - then committed switch - then LNBs,
the order first committed switch - then uncommitted switch - then LNBs would indeed work just as well.

Two of the same type can never be cascaded.
Well, they can, but that would normally be rather useless.
Except in some cases, for instance when using a monoblock LNB after a 4/1 diseqc 1.0 switch; leaving the other two ports of the 4/1 switch available for two other LNBs (or another monoblock).

Or for example with a 2/1 diseqc 1.0 POSITION switch, to two dish locations that are rather apart, and then at each remote dish using the OPTION part of a 4/1 diseqc 1.0 switch for two LNBs. That is usually a cheaper solution than buying a 2/1 diseqc 1.0 OPTION switch.


I always like setups with parallel use of diseqc signals. It's not often that you see those, though...


Diseqc, a very versatile world of possibilities......


Greetz,
A33
 
That is absolutely right.
But, the word used by @Marcus_21 was "take precedence over", which I interpreted as "comes before", as in the order of commands.

The order of commands should basically follow the order of the actual physical setup.
Though it would be very logical to use the order first uncommitted switch - then committed switch - then LNBs,
the order first committed switch - then uncommitted switch - then LNBs would indeed work just as well.


Well, they can, but that would normally be rather useless.
Except in some cases, for instance when using a monoblock LNB after a 4/1 diseqc 1.0 switch; leaving the other two ports of the 4/1 switch available for two other LNBs (or another monoblock).

Or for example with a 2/1 diseqc 1.0 POSITION switch, to two dish locations that are rather apart, and then at each remote dish using the OPTION part of a 4/1 diseqc 1.0 switch for two LNBs. That is usually a cheaper solution than buying a 2/1 diseqc 1.0 OPTION switch.


I always like setups with parallel use of diseqc signals. It's not often that you see those, though...


Diseqc, a very versatile world of possibilities......


Greetz,
A33

The rule is simple: as long as each command is either not received or ignored by all switches, except one, then all will be fine in theory.

About "precendence", the main point is that either order should work if the commands are sent in the correct order.
 
I am still a bit perplexed as to why, in practice in Europe, you would need more than, say, five satellites so why does DiseqC allow so many?
 
I am still a bit perplexed as to why, in practice in Europe, you would need more than, say, five satellites so why does DiseqC allow so many?
Dxers try to receive as many satellites as possible, it's a passion, it has nothing to do with logic.
 
Thanks - I suspected as much but you are the first to say so! :cool:
 
I have two dishes, four LNBs and point to three satellites (Eutelsat, Hotbird and Astra) and diseqC with four channels does the job
 
I use EMP-Centauri 8 way DiSEqC switches but I think the most I've used at one time is 7 ports with one spare for plugging in a temporary dish.
 
I have T90 dish with a 16 way DiSEqC switch. Reason is... immediate switching between satellites.
 
Back
Top