Funny Diseqc issue

[markbone100]

This is an issue I have been having for a while now.

I have a 4 port Diseqc switch for the satworks 3618 (that could be it there). Ever since I have hooked up the 4th dish to it, I have major errors when blind scanning.

I have it setup this way

Port 1 - C band movable
Port 2 - Ku band movable (same dish as 1)
Port 3 - .75m channel master at 91W with universal LNB at 10750 LO
Port 4 - Fixed C band at 58W

When using port 2 to blind scan, I get a whole mess of C band transponders when scanning and it misses about 90% of the Ku stuff. Tried this on IA5 or whatever its called now and wouldnt even scan one Ku TP into it, it was all C band. Now if I unhook Port 3, everything is normal.

Say I swap port 3 and 4 around. Problem still exists. Swap 2 and 4, same issue. I just bought a new switch the other day and its doing the exact same problem as the old switch.

Port 1 gets its power from an analog receiver and power passed through a splitter to the LNB and the other leg goes into the switch. 2, 3 and 4 get power from the FTA. Could this be from a low voltage issue or the FTA is junk? Note both the old and new switch do the exact same thing and I do NOT have another FTA to test it with.

If it is a power issue, how can I add external power to make up for the loss

 

[Larry1]

Some receiver Diseqc combinations work better than others. I have one receiver that acts simular. The simple way around it for me was to only connect the one dish that I was scanning at the time of the scan. then disconnect it and connect the next dish to scan, etc. When all were scanned, connected all dishes to the diseqc and it switched properly when using the receiver. It only had a problem when scanning. Now in my case it was just a scan for setup and not to be used for daily scanning. When I want to update the channels from one of the dishes, I have to do the same proceedure when I re-scan.

 

[pedrogarcia]

I did not think any FTA receiver would allow you to select a Universal LNB and set the LO to 10750, I am not sure why you would do this.
Port 1 is a default on most switches, I would put the C Bands on 3&4 and keep the universal LNB with its 2 LOs and turn the 22hz on, if it is not auto for that bird.
Also check your port3 cable connections.

 

[guacharaca]

This is your most important clue. Try taking off what is on port 3 and put it on a Ecoda 22hz switch either before or after the Diseqc to see if it solves the problem. Try 11.250 for your LO on the universal.

 

[crackt]

what happens if you set the universal lnb to 10600 22khz on. these are the proper settings when using a universal lnb for north american frequencies.

crackt out,.

 

[markbone100]

Whoops made a mistake. It isnt a universal but a Standard Linear LNBF with a LO of 10.750. Was gone this afternoon but narrowed it down. Completely eliminated everything except LNB 1 and 2, its definately bleeding in from port 1. Ill switch 1 to a Ku band LNB and see what happens

EDIT - after swapping LNB's, cables, and direct hookups I have came to the conclusion the receiver has lost its mind. This was found out by hooking a single KU band LNB to the receiver and doing a scan. During the scan it will lock onto 2 transponders that I confirmed are there with lyngsat. But on the next screen where it actually looks for channels, the valid frequency and transponder has been replaced with numbers totally different and out of kilter. IE show a LO of 10.750 but showing 4000 mhz (not SR) and complete random numbers it decided to put into itself when trying to scan channels. It does this with every LNB when it is hooked direct to the receiver whether it is a C or a Ku.

Was a nice receiver before but its utter crap now. Doing a reset to factory defaults works until about 50 channels or so then it starts to get all crazy again

 

[turbosat]

What receiver is it? Might need to reload the firmware, possibly got corrupted somehow.

 

[markbone100]

Its a Satworks St-3618. There is firmware for the 3688 out there but very old. the satworks brand itself has completely dissapeared

 

[markbone100]

Forgot.......... There was a thread about the satworks firmware. Last night reflashed it to 6.0, cant remember what was there to begin with. Last night re-scanned 3 sats and as of right now it works excellent. That might of been the problem all along