Those details are common knowledge, as AltxRo is strictly following the DiSEqC definitions by Eutelsat, as documented completely here:
http://www.eutelsat.org/satellites/4_5_5.html
But that's not the problem at all.
BDA does not provide an interface to send DiSEqC commands to.
So manufacturers use some proprietary tricks to talk directly to the hardware, bypassing the driver.
And that methods and codes are not public, as it seems, mainly due to NDA with M§, necessary to get their support for BDA development...
This means, there is NO common standard to talk DiSEqC to BDA devices.
Solutions may only work device specific, if someone finds out about it's dirty tricks.
That's more like hacking than programming...
My signature:
Please read here:
On Bug Reports And Other Complaints
and there:
BOARD RULES - READ THIS!
I don't give support by e-mail or PM.
And I will never assist on PayTV hacking.
PM ME FOR THIS AND YOUR ACCOUNT WILL BE DELETED IMMEDIATELY, WITHOUT ANY WARNING!!!
NEVER EVER DARE TO CONTACT ME FOR PRO VERSION ISSUES!
I am not responsible for that.
Check the 'Activation' section.
Please keep it in English here, or Russian in the Russian section, or German in the German section.
I don't read nor write Klingonian or any other language than English and German.
Addressing me personally in any exotic language will be treated as severe insulting! Be warned!!!
1.)AMD Phenom II x4 940, GA-MA770-UD3, 8 GB DDR2-6400. 7 Pro SP1 x64 + XP Pro SP3 x86
DVB-S2: Cynergy S2 USB HD
2.)P4 3200 i865G (F-S Scenic W600pwr) XP Pro SP3
DVB-S: hauppauge WinTV Nexus-S rev. 2.2, driver TT 2.19h, hardware mode
19.2°,13°,28.x°E,30°W, DiSEqC 1.0
Auf Deutsch:
DVB-Cube <<< Das deutsche DVB-Forum >>>