SS2, STAB HH90 + 60cm Sky Dish/LNB

nikione

Hi all,

Because of how nice the people in this forum are .. somehow I got more interested in Satellite stuff.

I've bought off Ebay a STAB HH 90 which looks like a nice quality rotor with DiseqC 1.2 anf USALS support.

I have done the following:
PC w/ SkyStar2 PCI v2.6c
Latest original drivers installed (4.5.0 ??)
"Semaphore" working

I connected the rotor and tried to get it moving or do anything at all with the following sw:
- ProgDVB DiseqC "plugin"
- SS2 DiseqC 1.10 => I haven't done the "patching" of the drivers .. is that really necessary ?!?! why the hell doesn't it come as std ?
- FastSat Finder

NOTHING ... no movement at all.

I have read the manual which is not really helpful when it comes to troubleshooting. I have also made sure that I respected all indications.

Questions:
- Is DiseqC "bidirectional" .. is it possible to run diagnostics on the motor (or does the protocol include Error codes reporting)
- Is there some other software I can try ?
- Is the setup of the drivers and cards OK by default to move a Diseqc motor ?
- Is there any "typical" task that I can do for physical checks on the motor ?

Thank you very much as usual !!

Nick

nikione

Sorry to reply myself ..

I checked and the 1.10 ver doesn't require any patching of the drivers (from 4.4.0 they are "fine").

Anyone else know of any typical problem .. or possible resolutions (see my orig post) ?

Topper

I think more information is required by folks here, e.g. what cable run do you have, as in the type of cable, what length of cable, are the connections made correctly, i.e. no shorts.

A PCI card only has a low power output, is the card sufficiently rated to drive the requirements of the motor?

As you posted in the correct section I assume you have read all the threads
relating to this common PCI card problem

http://www.satellites.co.uk/satellit...net-satellite/

War does not determine who is right, it determines who is left!

Formerly toppervte33h
whose six pack has turned into a keg

Help support this web site by making a donation
Or use other options to help support Sats UK
Show Your Support
by clicking the button

Thank you.
Freddie Flintoff is back

Huevos

Diseqc 1.x sends messages from the receiver (or v-box) to the device (switch, motor, etc) without any feedback. With Diseqc 2.x the device acknowledges the commands it is sent.

nikione

Thanks.

I have checked the power specs of the card and of the motor and they are "compatible".

Unfortunately I do not have a received I can test it with.

The cable run I don't think would matter, it's about 10/15m top (RG58 ?) and there is no disturbances in regards to the LNB transmission (which obviusly is on a very different frequency than diseqc).
I also tested it initally with a "patch" 1.5m cable directly to the pc and it didn't move.

One thing that I noticed is that the SkyStar 2 PCI page on the mfg website states that it's Diseqc 1.0 - However I don't think that would matter as the diff between 1.0 and 1.2 is purely command set I suppose (I.e. newer sw and drivers can make use of it).

rolfw

If it's RG58 then you will have real problems, it isn't suitable for satellite installations and will lose 1db/metre, plus it is 50Ohm, not 75Ohm as required.

To drive your motor you need enough power and although the specs of the SS2 would suggest it is OK, many people have had problems.

You need the DiSEqC 1.2 plugin to make it work.

Rolf If you enjoy our site, you can help support it by wearing our unique branded merchandise, you can do this by clicking on my baseball cap, making a direct donation with Paypal by clicking on the Donation button below, or using our site supporting advertisers, to do this, click on the central image below. Follow us on Twitter, click on the twitter image.

Huevos

Just to expand on this: The power to drive the motor is always present on the co-axial line, but the motor only moves when it receives a diseqc command down that same co-axial line from the receiver. This means you can test if there is sufficient power to drive the motor by pressing the manual override button on the motor (assuming your motor has one). If the motor does move when you press this there must be sufficient power and your problem would be software related.

nikione

Tnx Huevos, the main problem is that this motor doesn't have ANY manual commands.
At this moment the only practical way to test it is to either buy a diseqc 1.2 capable receiver box or to buy a diseqc 1.2 motor controller