Hi, Prog, when you check the Diseqc 1.2 problems, please look this small bugs i observed:
Will breake this message in two, as it some long.
Regarding the Device options as picture bellow
I found that "how many repeat..." is not ok.
Puting 1, will be sent only the mandatory message:
E0 XX XX XX.
Puting 2, will be sent the mandatory + one repeat
E0 XX XX XX + E1 XX XX XX
Puting 3, will be sent the mandatory + two repeat
E0 XX XX XX + E1 XX XX XX + E1 XX XX XX XX
and so on.
The problem here is that i observed it's not hard loose the mandatory part, and so i think it is better
allways send the mandatory, and "how many repeats" someone likes, beeing 1 the minimal.
So best when choosing 1 repeat, send:
E0 XX XX XX + E1 XX XX XX, and so on.

A second problem is with the "Delay between commands".
Testing with 10ms, i found my controller/analyser looses most of the individual commands in message;
Testing with 50ms it looses a few commands;
Testing with 100ms, it seldom looses a command (it happens with the mandatory command, never see with the repeated).
So I would ask fixing a minimun delay of 100ms for reliability.

Continuing the message above.
These issues are concerning the positioner tab:
The first thing is the program dont send a GOTO 0(zero) command, only 1 to 100.
but i commonly use position 0 to park antenna and check if it lost position, with a mark in the pole
So I ask to enable the GOTO 0, and perhaps put a warning "its forbid store the O position"

The second is that when opening the tab, it by default uses the 0 position. For the day-by-day use
i open that tab to realign satellites with bad signal.
So the best is to open it with the number of the satellite in use.

The third is a more generic problem, that is present here. Most of the receivers send a diseqc message every time user changes a channel; instead, Progdvb sends the message only once when changing satellites. The problem here is that if a message is lost by the controller or switch, you will have to go to another satellite, then return to the satellite desired to try connecting correct.
As sending diseqc messages is time consuming, I may suggest Progdvb send messages when changing frequencies, or every two or three channel changes.

Prog, thanks your pacience, but i think this wil make Progdvb better.

1.Delay very depended from hardware part. I hope 200 is good for all devices. Or?

2. Hm. May be one more button for position 0?

3. May some option for send diseq command every time? Users very like speed of channel changes...

ps: Thanks for your help. Do you log diseq commands over ProgDVB or some addition software?

Thanks, Prog. What i think:

1.Delay very depended from hardware part. I hope 200 is good for all devices. Or?
- With my Prof 7301, 100ms only sometimes looses the first E0 command after opening the program,
after that, dont loose anything. So I guess minimal 100ms is ok, but needs allways one repeat.

2. Hm. May be one more button for position 0?
- No. Only allow GOTO 0, but dont allow Store 0.


3. May some option for send diseq command every time? Users very like speed of channel changes...
- To my taste, sending diseqc message when changin to another frequency is best option...

ps: Thanks for your help. Do you log diseq commands over ProgDVB or some addition software?
- I log messages with a monitor on the coaxial cable, assembly i did. It can be used with any receiver.
This it:

Cool! Where you buy this device?

I projected and did it myself some year ago. Its a diseqc 1.2 controler with control to a servomotor,
as nowadays receivers dont have that output. But as i need it to change circular/linear and C/Ku,
i use a combination of diseqc 1.0 and 1.2 to full automate the antenna (one dish only with everything).
The board in picture has a RS 232 serial output to monitor the diseqc messages in a terminal program.
Using a Pansat receiver this controller works pretty well.
With Progdvb i have problems when i try adjust antena (the matter of this topic).

Hi, Prog.
I found one more serious bug in the tab "Diseqc 1.2 Positioner" .
When I give a Step East or a Step West, program can repeat this message,
lets say for a step east: EO 31 68 FF + E1 31 68 FF.
The intention was to motor do one step, but as command is repeated,
motor does step 2 times. If i configure N repeats in device options, motor will step N times before stoping.
So you can not repeat a step command.
I think better not repeat any of the commands in the motor adjusts tab.

It looks like bug of hardware. Device not can repeat commend E1 after E0. E1 is copy of command but not new command.

ps: Changed logic for position 0 in last release.

No. If a controller looses a E0 step command, it will need a time-out to understanda new E1 now is a new command, not a repetition.
But how much long is this time-out to be?
See:
E0 E1 E1 ?? E1 E1
?? is something lost. One or two or five steps? More, if E1 is not a valid command why send it?

More easy not repeat, let the operator do that.

Hi, Prog, I fast tested the new 6.70.6, and found a problem:
the voltage change in the Ku band is ok now, but now the voltage is stucked in C band lnbs

Well, I did a list of wishes to follow the fix saga of the Diseqc 1.2 section.

In version 6.70.6 we have:

1 - Allow Goto 0 - OK!
2 - Not allow Store 0 - OK!
3 - Stucked voltage in Ku lnb of Diseqc 1.2 tab - OK!
4 - Stucked voltage in C lnb of Diseqc 1.2 tab - not ok
5 - Default position nn to the in use satellite when open Diseqc 1.2 tab - not ok
6 - Send full diseqc message according to diseqc tree when open and when change satellite in Diseqc 1.2 tab- not ok
7 - Send only E0 messages by buttons of Diseqc 1.2 tab, no repetitions - not ok
8 - Do correct number of repetion as set in Device Options - not ok
9 - Default 100ms minimun to Delay Between Diseqc Messages - not ok
10 - Remove the "Positions" button or lock its list, to show ALL numbered sattelites, in Diseqc 1.2 tab - not ok
11 - Send full diseqc commands when change frequency or channels - forgot to see this, guess not ok
12 - Test the 22K tone in Ku band lnbs of Diseqc 1.2 tab - not checked yet

Cant remember what more. Hope people else help in suggestion to perfect that part of Progdvb.

"E0 E1 E1" and "?? E1 E1" still one command. And my positioner (Strong v50) do only one step (I check with 4 repeats).
About 200ms, I am not sure about 100 for all diseq devices in world

Can you give me more information about "Stucked voltage in C lnb of Diseqc 1.2 tab" ? Of course you must select position in dialog with C Lnb. It is very important. ProgDVB must found this position in tree for detect correct settings.

Ok, Prog. Only to be 100 % sure, could you test step repetition with a large delay between commands?
I have a chinese unbranded controller that is very slow in response compared with my home-made controller.
When i put 100ms delay, it seems loosing or understanding the E1 are only useless repetitions.
But when I put 999ms delay, it executes the N steps i told you.
If you have an enemy, tell me I can send that controller to him...

Prog wrote:"Can you give me more information about "Stucked voltage in C lnb of Diseqc 1.2 tab" ? Of course you must select position in dialog with C Lnb. It is very important. ProgDVB must found this position in tree for detect correct settings.

In the old version 6.70.5, when in the "Diseqc 1.2 Positioner" tab, if you select a Ku lnb antenna to move,
you'll see that the voltage is fixed, dont change when change polarizations. C band lnbs are ok there.
In version 6.70.6, the problem moved: now the Ku lnbs change voltage right, but sadly the C band lnbs
got the ill.

Prog wrote:"About 200ms, I am not sure about 100 for all diseq devices in world

I suggest allow minimum (at least, more than) 100ms, as Options allow even 0ms delay. Thats because that would require a very fast controller to decode message and take actions required. And putting big delays may slow down channel change.

I did a better look in version 6.70.6, this the satisfaction state:

1 - Allow Goto 0 - it's OK!
2 - Not allow Store 0 - it OK!
3 - Stucked voltage in Ku band lnb of Diseqc 1.2 tab - it's OK!
4 - Stucked voltage in C band lnb of Diseqc 1.2 tab - not ok
5 - Set position NN to the in use satellite when open Diseqc 1.2 tab - not ok
6 - Send full diseqc message according to diseqc tree when open and when change satellites in Diseqc 1.2 tab- not ok
7 - Send only E0 messages by buttons of Diseqc 1.2 tab, no repetitions - not ok
8 - Do correct number of repetion as understand in Device Options - not ok
9 - Allow 100ms minimun to Delay Between Diseqc Messages - not ok
10 - Remove the "Positions" button or lock its list, to show ALL numbered sattelites, in Diseqc 1.2 tab - not ok
11 - Send full diseqc commands when change frequency or channels - not ok
12 - Test the 22K tone in Ku band lnbs of Diseqc 1.2 tab - it's OK!
13 - Change name of button "More than one satellite" to "Set Diseqc 1.2 Number" - Not ok

As me and Prog are not English speakers, sometimes hard undertand well, I ask testers to help, and confirm problems (some problems can be issues in my hardware, of course...)

Hi, Prog. Today (sunday) when i turned computer and Progdvb on, doing some tests, I noted the voltage change problem with Lnbs of "Diseqc 1.2 Positioner" tab returned to the Ku ones.
Today the C band lnbs are working perfect. In the Ku, voltage is stucked. Seems there´s a more generic bug envolving voltage selection in this tab. Checked config, all seems ok.
Need someone else doing tests, as this may be a problem with my card. But channel and scanning keep working well here .

Hi, all. Did some testing with version 6.70.7 of pre-release and didn't note important diferences to previous versions. Wrong diseqc messages, stuck voltage, etc....
I would say to Prog, that i observed there are many loose of messages in the first command sent (first E0 XX...). The next elements always go well. So maybe try give a small delay before sending the message, to stabilize things.