What is the correct LO setting for a SuperDish?

Pepper

DVR Addict~Mad Scientist
Original poster
Supporting Founder
Mar 16, 2004
8,191
1,060
Satsuma, AL
OK, I've got a couple of SuperDish with the stacked FSS LNB. Closest LO setting I've found is 10750/13850. It finds nothing on the transponders I previously was using on a standard (primestar) LNBF. Blindscan finds some of them but the polarity is reversed. I only get the vertical TPs which it thinks are horizontal. I am sure it's something I am doing wrong, or I have two bad FSS LNBFs?

10750 finds only vertical transponders.
10750/13850 finds the same ones but labels them horizontal.
13850 finds nothing.

FSS is on 103 and 125. motorized standard linear for everything else.
 
Last edited:
Yeah, I found that one too, sounds like the exact same thing I'm experiencing. I don't think I have enough spare parts to swap out these LNBFs so I hope it can be made to work.
 
By the way I tried the trick in that thread about extending the range 11700 to whatever the upper limit is, somewhere at or above 13500 I think. Didn't make a bit of difference.
 
Yeah, thanks for the reference, that is it. But it doesn't seem to work on either of the FSS LNBs I am using. Lucky everything I want on 125 is vertical, but 103 is another story (already took skew into account, btw); I guess I could try rotate the thing 90 degrees?
 
Yes, just ran another detailed scan with LO 10750, range 12200-13500. Nothing there.

I am going to try to cobble something together with that dish and feedhorn and the guts of an old primestar LNB with separate V and H, and a multiswitch. Maybe that will work better.
 
fss on 125 scan in as (regular scan)
11983-30000 h
12063-30000 h
12108-2397 h this one is hottest
12115-8703 h
12142-30000 h
12183-30000 h
12149-4443 h
12425 4443 h
12431-4443 h
12444-14028 h
12559-3725 h
 
fss on 125 scan in as (regular scan)
11983-30000 h
12063-30000 h
12108-2397 h this one is hottest
12115-8703 h
12142-30000 h
12183-30000 h

12149-4443 h
12425 4443 h
12431-4443 h
12444-14028 h
12559-3725 h
looks right. Bolded would be the normally vertical ones
I assume you mean 12419 (instead of 12149) H 4444
 
Well I guess I have some bad LNBs, a FSS with a busted high oscillator, and a standard that doesn't switch polarity on voltage change.

I swapped the superdish on 103 for my 39" channelmaster with standard LNBF. It found the same transponders both V and H which makes me think that LNB is stuck on vertical polarity. I switched its LNB with a THIRD spare Superdish LNB on the same feedhorn. It still only found V when the LO was stacked 10750/13850, so I think the stacked option in the microHD might not work right. But, it found everything with LO 10750, H only and the scan range extended up to 13500. Over on 125, I rescanned with LO 10750, H only, 11700-13500 and it found everything listed above. So I am in good shape now.

These FSS seem notorious for drift. All the frequencies seem shifted up around 15MHz. Example 11940 showed up at 11955. The horizontals, being in reverse order, show 15MHz lower. On the old coolsat, i could specify a custom LO of 10765 which would have corrected this.
 
Last edited:
As detailed in another thread, the FSS option are working, but currently logging all transponders as Horizontal. Without remapping this is how bandstacking LNBFs work. All TPs are sent down the coax on a single polarity and a certain range are remapped by the receiver as the opposite polarity for ease of use by us mere mortals.... lol!

The receiver should be logging the IF range 1650 - 2150 using the second LO and remapping to be a vertical transponder. We have corrected for next firmware release.
 
That sounds backwards. 10750 is vertical and 13850 is horizontal, if I'm not mistaken.
 
As detailed in another thread, the FSS option are working, but currently logging all transponders as Horizontal. Without remapping this is how bandstacking LNBFs work. All TPs are sent down the coax on a single polarity and a certain range are remapped by the receiver as the opposite polarity for ease of use by us mere mortals.... lol!

The receiver should be logging the IF range 1650 - 2150 using the second LO and remapping to be a vertical transponder. We have corrected for next firmware release.

so, just curious of course, when will the next firmware be out? :)
 
Planning on next week.

I took a one week break and went on a week road trip to the beautiful NW. Saw my daughter off to volunteer for a year at an orphanage in Honduras, toured St. Helens, put down the convertible and drove the Oregon coast, zipped inland to Crater Lake and came back refreshed. Once again, staying up all night programming and testing.... :D

99.9% of the firmware hit list is complete. We want to address as many as possible requests and bugs before this major release. Quite often when one item is modified it has seemingly unrelated operational changes in other processes. Painstaking testing of every function each time a process is modified....
 
Well I guess I have some bad LNBs, ...
...
These FSS seem notorious for drift. .
Which feed horns are you using?
There have been numerous threads on (making) better horns.
I believe most any were better than stock.

As for drift, in original service, all LNBs were powered 24/7.
That probably helps a lot.
If you want to consider that option, search for old discussion threads (in FTA) using the DP34 switch.

Edit: search for old discussion relating to batch or revision numbers on the FSS LNBs.
Probably a thread by Iceberg (or maybe me).
Something about stability...


sent from iPhone 4
 
Last edited:
Kodaz or other bandstacked users.....

I have attached a pre-release of new firmware. I am unable to test the bandstacked LOs. Would you give me some feedback on if bandstack LNBs scan properly?

There are a few issues still being worked on in this release, but nothing that is damaging ... more cosmetic. Please note that this is not an official release and do not post it as such on the forum. This is only a pre-release for testing Bandstacked LNBs.
 

Attachments

  • GSP_MHD_20120809.zip
    1.8 MB · Views: 272

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)