motor/ swings

[littlelor]

I just started having this problem here with the HH90 motor, I'm in the arc as I can get all sats, but when I store them, and try to flip from one sat to the other, it goes to the farthest one in the east, I started over at my 0 postion, and then renetered all info, it stores the info, but the dish swings all the way west and goes back all the way to the east, and sits on that one sat.I do not use any switches ,Fortec star 33" dish, and hh90 motor.Would a lnb cause this problem ?

[wejones]

Originally Posted by littlelor

I just started having this problem here with the HH90 motor, I'm in the arc as I can get all sats, but when I store them, and try to flip from one sat to the other, it goes to the farthest one in the east, I started over at my 0 postion, and then renetered all info, it stores the info, but the dish swings all the way west and goes back all the way to the east, and sits on that one sat.I do not use any switches ,Fortec star 33" dish, and hh90 motor.Would a lnb cause this problem ?

You don't say what receiver you're using, plus you don't say whether you're using DiseqC-1.2 or USALS (both of which are DiseqC formats).
I kind of assume that you're using 1.2 since you say that you're storing the positions, since USALS doesn't store any motor position.
The receiver is an issue, because if you are using a Fortec Ultra, the memory in the Ultra has been known to get scrambled, and when it does that STRANGE things happen, including it sending bogus info to the motor.
Also, if you have a Mercury II, the mercury has been shown to have some serious bugs with respect to DiseqC-1.2. In particular, if you program your sats, then delete a satellite, it mixes up which position goes with which sat. Basically the Mercury has only a partially implimented DiseqC-1.2 even when it works, but it doesn't work.
Anyway, I'd expect that there is a good chance that you have a receiver issue.

[MrBillM]

The DisEqc 1.2 mode seems to work fine with my Mercury II. No confusion, so far.

[littlelor]

the receiver is a viewsat extreme, I hired someone to install it for me, from a satelite center,as I had no idea how to set up the motor(female, not into technical stuff) he set it up as installer then user, I did a factory upgrade, and this is when the swing on the sats started, and will not go auto only manually, I had the installer come back and he then tried usuals (i don't use any switches)and he never seen anything like it, and had no answer, he then tried the first way he hooked it up, but still does the same thing. Could it be the memory in the receiver, or lnb line?

[wejones]

Originally Posted by littlelor

the receiver is a viewsat extreme, I hired someone to install it for me, from a satelite center,as I had no idea how to set up the motor(female, not into technical stuff) he set it up as installer then user, I did a factory upgrade, and this is when the swing on the sats started, and will not go auto only manually, I had the installer come back and he then tried usuals (i don't use any switches)and he never seen anything like it, and had no answer, he then tried the first way he hooked it up, but still does the same thing. Could it be the memory in the receiver, or lnb line?

I don't know anything about the Viewsat receiver, maybe someone else does. Since the problem started when you did the factory upgrade, I wouldn't think the coax would be a problem. Also, the only related things kept in memory in the receiver is your longitude/latitude and the sat's latitude (if you're using USALS), and the DiseqC1.2 sat number, if you're using DiseqC1.2. When using DiseqC1.2, the positions are stored in the motor, not the receiver, and when using USALS, the positions aren't stored, they are calculated each time you go to a sat.

Typical things that might be entered wrong though, are:
In general,
try to disable the limits, and reset them manually.
Make sure that the motor's "ZERO" is correct. Ie issue a goto zero command, and see where the motor goes. If it doesn't go to zero, see if there is a hard-reset procedure. I have a different motor, but on my motor, you can manually move the motor to zero, then do the hard reset, and it will calibrate where the zero is.
Make sure that the firmware you upgraded to was indeed for your receiver. Perhaps revert to the old firmware you had before the upgrade.

If using USALS... Make sure your lat/lon and sat lon are entered with proper hemisphere (E,W,N,S).

If using DiseqC1.2... After insuring that the zero is at zero, do one sat at a time, starting near your due south sat. Manually bump the motor until you find a known transponder, using a meter in the transponder scan section, and when you have found the transponder, then save the sat position.

What I think most likely happened, is that somehow your receiver sent a reset command, or resync or something that changed the motor's zero position, so it is calculating all the sat positions vs a zero position that is way off to one horizon.

[littlelor]

I have a question here about the posts in the motor that hold the lnb line and rec. line if those posts become really loose will the signal and quality become poor? If so is there any way of tighten them?

[wejones]

Originally Posted by littlelor

I have a question here about the posts in the motor that hold the lnb line and rec. line if those posts become really loose will the signal and quality become poor? If so is there any way of tighten them?

That doesn't sound good. If those things get loose, it seems like you're running the chance of breaking a connection inside, depending upon how it's attached (ie via wires or directly to a circuit board. I would sure try to see if you can tighten it up, but I don't know anything about that particular motor, and haven't even looked closely at the motor I have.
I seem to remember a post either here or over at satforums, that mentioned the f connector getting loose, and causing problems because it didn't have a flat side or tab of some sort to keep it from turning, but I can't remember what was done to fix the problem. Those connectors usually have a nut either on the inside or outside, that tightens them, but it isn't always easy to accomplish, particularly if it isn't prevented from turning.
Anyway, not sure how to tighten it, but I'd sure recommend trying.

[littlelor]

thanks for replying back, I phoned a store that supplies these motors, and asked and they tell me there is no way of tightening them as they are attached to the motherboard, and if a wrench was used on them thats what loosen it in the first place( my old nieghbor thought he was helping me out) the wires get snapped off from the board, cause a malfuntion, I ordered a new motherboard for 25.00 .I f anybody else comes across this, you can mention this. Thanks again