SkyStar 2 and Diseqc 1.2 problem

stan_drew

Hi,

I put my new Moteck H-H motor up yesterday, no problem with moving it manually with the little button on front, but my SkyStar 2 can't seem to control it.

I'm using ProgDVB as my viewer, and have tried a few different plugins, inc Dixie, SS2Diseqc (with new skynet.sys driver) and Diseqcu, but no joy. If I look at the output from the card with an oscilloscope, I can see that no Diseqc 1.2 control pulses are being generated (but if I use ProgDVB's built-in Diseqc 1.0, then I can see the switching signals being sent).

Anyone got any ideas? Can all SS2's be made to send Diseqc? (mine is over 18 months old). Which skynet.sys should I be using?

Thanks for any help,
s

BGonaSTICK

They should all work with the plugin listed at the bottom of this post (all the PCI cards, but not the USB versions).

As you say, you must replace the driver file, and restart the PC.

The software works fine, (I use it all the time), but maybe your motor is not working correctly? I know you've tested the SS2 output with a 'scope, but can you try another diseqc 1.2 receiver? It may be a power problem?

In the same way as you have driver versions, so you have corresponding versions of the patched driver, so make sure you have the correct one.

If you're using an older driver version, and don't want to upgrade, search out version 1.5 of the plugin as opposed to 1.7. It still works OK.

http://www.satellites.co.uk/php-bin/...26&postcount=1

stan_drew

Thanks for that- it was indeed a problem with different versions of the "official Technisat" and "patched" drivers for the card.

Once I rolled back my Technisat driver to 4.2.11, I found that the patched SkyNET.sys from SS2Diseqc 1.7 did the trick (i.e. my card is now sending out pulses). There's also a SS2Diseqc 1.8 that has a patched version of the Technisat 4.3.0 driver, but that combination wouldn't work for me.

Having said all that, my motor's still not shifting automatically, but I'll have to wait until the weekend for sufficient free time in daylight hours to investigate further!

s

BGonaSTICK

Check back here if you have any probs. If it's not busted... we can fix it!

stan_drew

Well, I finally got the motor under control yesterday. After much investigation with an oscilloscope, the Diseqc specification, a mate's STB etc, etc, I ended up getting the motor down and bringing it indoors to connect to the PC directly over a short cable.

Turns out it was a software problem- as I said in my earlier post, the only way to get my PC to send Diseqc 1.2 is to use the patched Technisat 4.2.11 driver, as supplied with SS2Diseqc 1.7. However, this version of the plugin doesn't seem to send commands that my Moteck will act upon- upgrading to SS2Diseqc 1.8 (just the plugin- not the driver) fixed it for me (just a theory- v1.7 sends commands beginning "00", whereas v1.8 commands begin "E0", the latter being correct according to the spec.).

Hope this is useful for someone else- just make sure you don't use the patched 4.3.0 version of the driver as supplied with SS2Diseqc 1.8.
s