jeallen01
Specialist Contributor
- Joined
- Oct 12, 2003
- Messages
- 6,674
- Reaction score
- 2,630
- Points
- 113
- My Satellite Setup
- See Signature
- My Location
- Somewhere in England (possibly?)!
Swapping the C band to position four cured that problem, I assume the signal was getting across inside the switch somehow.
Just the odd problem now with the dish not driving to a KU band position.
Drive it to a different sat, then it will go to the errant one.
Good evening thank you for your interest : )Just to understand what is happening:
- On what diseqc input is/was the KU-dish, input 1 or 2?
- Do I understand correctly, that EVERY time you switch from C to KU-dish, that the KU-motor doesn't move; it moves only after your second KU-dish moving command?
- And on what input did you have C-dish, before changing it to input 4?
- Does the motor move everytime you switch from Ku to C-dish?
Good thinking to switch to port 4, to minimise crosstalk in the switch! (Inputs 1+2 and inputs 3+4 in diseqc switches usually share a PIN-diode....)
Edit: But if it was on port 1, crosstalk probably wasn't the cause! "Port 1" was...
Might be that you need the two-step switching procedure that I described earlier, for switching to KU. That another switch wouldn't help for that.
But first I want to understand what is happening, to explore the causes of the problem, and other possible solutions.
@jeallen01 : signal loss of diseqc switches usually concerns only signal strength, not signal quality. So I wouldn't worry too much about that.
Greetz,
A33
... all appears to be working as it should,
Possibly true, and probably the easiest (and cheapest?) solutionHallo A33 : )
...I have now fitted a vintage manual switch which works fine, I may upgrade to a remote controlled one....
Thank you all for your advice : )
God Bless Spiff
Well it worked fine yesterday, but unfortunately today it played up badly, switching to C band also caused the KU band box to drive.
I did try using port 2 for KU and leaving C on port 4, but it made no difference.I'm thinking of two possible ways to try to overcome this.
First:
If it doesn't the other way round, switching from C-dish to Ku-dish, try changing port 1 to port 2 for Ku-dish (so port 1 as default port is not used anymore).
Does this help?
Second:
For the two step switching procedure I described earlier, add (in your receiver) a fictive C-band satellite and a fictive Ku-band satellite, both with a program attached to that satellite. Define these satellites with the proper diseqc 1.0-command for C and Ku, but without motor command!
Then for changing motor-dishes, always first choose the fictive program of the wanted dish, and only after that select the wanted program. So the motor command is always sent only after the proper dish is chosen by the diseqc 1.0 switch.
If this procedure is too troublesome for you, a manual A/B switch or 0/12V switch would indeed also be a good (less-automatic) solution.
Edit: but they have the same risk of moving the wrong dish, when you forgot to use the switch!
BTW I don't quite understand this "This upset some of the sat positions on KU band." How can the stored diseqc 1.2 positions be disturbed by move-commands? Otherwise restore by sending the command Goto-0 or Goto-Reference.
Greetz,
A33
I did try using port 2 for KU and leaving C on port 4, but it made no difference.
I tried turning off the motor command on one of the KU sats before setting up a fictive satellite, it turned the motor off on all the KU sats.
It did not appear possible to switch off just one, but perhaps I use the wrong place to do it ?
Good afternoon A33 Thank you for your interest.That is a pity. Though I don't really understand why switching to C causes movenment on Ku, but not the other way round.
Edit: still wondering if this is a problem of your specific switch? In this topic it is causing no problem: DiSEqC 1.1 16x1 Gecen GD-1601A - SatsUK
Can you post a picture of the menu options you have? LNB setup menu, and satellite setup menus?
I guess you have to define a third LNB.
As far as I know, a diseqc 1.2 position is stored in a positioner or diseqc motor as the number of pulses away from zero-point (reference). So if zero is unaltered, the command Goto(position)Nn is always carried out to the correct stored position, not dependant on previous position.
Now, a third possible solution (not having the risk of 'forgetting' to switch to the right dish beforehand):
Store all C-band satellite positions as GotoNn in odd numbers in one positioner, and all Ku-band positions as GotoNn in even numbers in the other positioner; leaving the unused numbers EMPTY (or a similar division of GotoNn-numbers). So a motor command will only affect the relevant dish.
(I just remembered having read this once, in a forum... )
I have at least one receiver that can specify the StoreNn-number (edited!). Your receiver also?
(Maybe this phenomenon is also the cause for the fact that the movement of the other dish is sometimes present in your case, sometimes not: depending on the presence/absence of a GotoNn position?)
Greetz,
A33
I used one of those STABDiseqc 1.0 -1.2 converters
That is a pity!With the TM5402 M3, you can choose either 1.2 or USALS (and, IIRC, can select a mixture of those) for every sat, but once you disable motor control for 1 sat then it is automatically disabled for all the rest of them!
One learns to work around as many of the issues as one can - as, like a few people, I've found that that TM is a nice reliable and simple tool which doesn't spring too many surprises, and has advantages like selectable frequency-band blindsearch and so on. Very useful for getting a system up and running, after which you can play with something more "sophisticated" to fine tune it.That is a pity!
(You posted while I was still writing!)
So the technomate algorythm takes control? And reduces possibilities and manual control, alas.
Just hope that the number-choice of GotoNn is left open, then...
Greetz,
A33