This topic about general diseqc issues.
First, I will ask Prog to look at an old bug of diseqc.
Its about cascade devices.
The problem in short is: the diseqc tree sequence is not regard when sending the diseqc messages. It seems that the more distant devices (from the receiver) are beeing called first. Thats an absurd.

Let´s do an example tree:

Dvbcard -> diseqc 1.0 switch -> diseqc 1.1 switch -> LNB.

The logic messages should be:
E0 10 38 Fx -> E0 10 39 Fx.

But Progdvb sents the message to more distant switch first:
E0 10 39 Fx -> E0 10 38 Fx.

The absurd of this is: if the more distant switch is not yet powered, how it will respond to the message sent to it?
Only the near device will respond correct in this way, the more distant ones will stuck in their default position (port1 of each, normally).

So, obey the diseqc tree design (chain of devices from near to distant) when sending messages to get correct operation of them.

Thanks! This is very important bug. Fixed.

Hallelujah! Hallelujah! This a happy day!

I tested pre-release version 6.86.6.a, and finally the diseqc tree sequence bug is fixed. After years waiting, now we can cascade diseqc devices in Progdvb!

But as nothing is perfect, we will have to delete all the channel lists and re-scan satellites again...

Anyway, thanks Prog. Will keep testings and report what I find, later.

Hi, Prog,

I tested pre-release version 6.85.6b, and I see you added a "multiswitch" option to the diseqc devices.
Frankly, I cant find a reason that it may help something.

1- Are you sure "multiswitches" are limited to 4 inputs? I dont know... ;

2- There's a increase of complexity to configurations, and in fact Progdvb is already too complex ;

3- The multiswitch seems it is only a copy of the diseqc 1.0 device .

So, I still suggest simplify things, and do only this:

A - remove that inoccuous "multiswitch" option;

B - do as standard, not optional, sending diseqc messages every tuner lock. It has very litttle impact on channel change time and permit the use both simple version switches as multistandard switches.

C - Keep a "Lock tuner in every channel change" as the option to bypass problematic response of diseqc devices.

Well, thats only my personal vision of this issue, forgive me if I say too much.

diseq Multiswitch is not diseq switch. It is special mode of ProgDVB logic.

Ok, I see what I see.
Again, cant Progdvb make "send diseqc message every transponder change" as standard? Anyway I will not insist more on that.

Next issue.
Some versions ago, Progdvb stopped doing the n-repeat of the diseqc messages.
Now, only the first message sent (E0...), no repeats (E1...).
Is that intentionally or a bug?
If repeat returns, I will do comments about it.

What you mean "as standard"? Do you like enable it by default (after installer?). I hope that is not need in most configurations. But what too slow.

I am not have idea about repeats. Module send command 2 times, but... Some conflict with driver. I try ask TBS. What device you use?

All evidence is the no-repeat of diseqc messages is a recent bug of Progdvb.
1- It was working (ok) some versions ago, same hardware;
2- the same problem in a TBS6925 (pci-e) and a Prof 7500 (usb).

But that is not my real concern. Personally I dont use repeats anytime.

The problem I see is that the repeats should be limited to 1 (send an E0...) or 2 (send E0... + E1...) No more than 2, never.

When using switchs, number of repeats normally is not a matter. But when using diseqc 1.2 (motors), then repeats may become a problem.
The Step (W/E) command will make antenna crazy with a 10 repeats, for instance. The Store NN will spend the lifetime of the EEproms,...
I may need a motor do only one step, but it may move 10 steps this way.
And there´s no logic way to diseqc 1.2 controller understand the meanning of those several E1... repeats. I programed my own diseqc soft, and could not find a way to fight that issue; I had to make controller just not accept any E1 30 68/69 nn command. But most people cant program their controllers...

So the real matter is: dont allow more than two repetitions of the commands, in a diseqc message.

Thats enough for today.

I am test on my PC 6925 with hardware diseq logger and not found problem. In log both copes of commands. E0 ... and E1 ....

Well... I use diseqc hardware logger too.

Can somebody with diseqc devices confirm for us if his instalation is sending repeated diseqc messages with a TBS6925 or a Prof 7500?

Just make N-repeats (2 or more) in Settings>Device Settings.
After some changes of channels, open ProgdvbEngine.log and look for some diseqc messages like this
first message > E0 10 31 Fn (can vary with devices)
repeated messages > E1 10 31 Fn (can vary )

Any help please?

Not many users have hardware logger for test that...

The logs of Progdvb are very detailed, and I think we can trust them, isnt it?

No need for hardware logs, just look in ProgDVBengine.log (with logs enabled in Settings>Options>Debug. The log itself is in the Logs folder of Progdvb directory.

I tested version 6.85.7, and still no repeated diseqc messages, only E0... (first message), no E1...(repeated message).

Then I full unistalled Progdvb, instaled my old Prof7301, and again no repeated diseqc messages.

So, I can get repeats anyway. Everything else seems ok. Very intriguing this...

PS. Hey, Prog, in this version, my logs are full of this warning:
"Table 0x10 not released inDvbtoUnicode".Please give a look in it.

Impossible check over ProgDVB log. ProgDVB write only diseq commands - NO copes!!! Also driver can send only one copy.

Ok, I installed a Prof7301 and a TBS6925 on same computer, installed the diseqc hardware logger in coax cable, with last version 6.85.7. The results?

1- Prof7301 is repeating ok: E0..., E1,... as expected;

2- TBS6925 sends only the first message E0...

So, do I have a defective dvb card? Most things seems working well.

But there´s something I feel it is not ok with the (mine) TBS6925: on PC power-up, this card powers the LNB, and keep that until a program turns the power off. Not the best, as you can burn devices by connecting / disconecting then with power applied...

With the Prof7301, theres no power to LNB until a program runs and requires the LNB. When that program shuts off, power goes off, too.

Hey, Prog, I observed the repeats are limited to 10 (1 x E0 + 9 x E1).
Still think its a good idea decrease that number. If 2 repeats dont work, why will 10 repeats do?. And there´s the step n command issue I explained before...

It most depended from driver. May be I am use other version? I am not have problems on same TBS with command copes.