E2 on a new Atemio Nemsis

[Pixl]

My other thread on the Atemio Nemsis was getting rather long. Thought I'd start a new one here since the issues seem to be more of the E2 beast rather than the receiver it's loaded on.

I've done well at getting my tuner lnb1 set up for C band. I wanted to add a second dish which is Ku, port #4 on my diseqc 1.1 switch, so I set up LNB2, but can't get it to work. Here is a screen shot of the setup. I question my selections for LOF/L, LOF/H, and threshold what ever that is.

 

[chewie]

Is it in the same tuner as your C-band is? if it is, try another tuner.
Chewie

 

[eastof111]

Also, looking at your signature, you show the ku as being a universal vs. your menu setup is showing a standard linear lnb.

 

[el bandido]

Why are you using LNB2 instead of LNB1?

 

[Pixl]

Is it in the same tuner as your C-band is? if it is, try another tuner.
Chewie

Yes, same tuner, has 8 port switch downline to feed 3 different dishes with one coax.

 

[Pixl]

Also, looking at your signature, you show the ku as being a universal vs. your menu setup is showing a standard linear lnb.

East, this is not the main Ku dish listed in my signature, but is a fixed 1.2m dish for 103w weird skew. Uses a standard lnbf with 10750 LO.

 

[eastof111]

Pixl, then the settings seem to be correct for that lnb. Again, back to the basics of running a straight cable until you get a scan then adding the switch and scanning again etc. Sometimes posting a hand drawn diagram, helps alleviate the guessing of how the system is connected.

On mine. I prefer to separate C and Ku on two tuners... makes life easier for me, especially for recording later on.

 

[Pixl]

Why are you using LNB2 instead of LNB1?

I just thought I should since it is physicaly different from the lnb for C band. I am trying another scan with it set to lnb1. It breaks the scan into 4 parts. Vert, horz, 10700 to 11700, and 11700 to 12750, even though I did not specify a two band universal. It locks one TP 11920 H 4599, but no channels found.
Again if you guys can look at these settings, what should be entered for LOF, LOF/L, LOF/H, threshold when using a single band standard Ku lnb?

 

[Pixl]

. Sometimes posting a hand drawn diagram, helps alleviate the guessing of how the system is connected. On mine. I prefer to separate C and Ku on two tuners... makes life easier for me, especially for recording later on.

Not too much to understand, my system has been simplified over time. Most all Ku is on a separate dish, no switches, to separate tuner. My C band is this setup shared by a couple stray Ku dishes.

Tuner> 8 port 1.1 switch> port 8> Cband lnb.
____________________>port 4> 103w Ku. lnb.
____________________> port 6> 15w Ku. lnb.

This setup was working with the Raptor I just pulled out of service.

 

[eastof111]

Your LNB is only single band, so no threshold switching is necessary with a standard lnb. I have always used 10750 or 11700 just to remind me that it's a ku setting when I quickly zoom through my settings in the tuner section.

The threshold setting is the frequency at which the receiver tells the LNB to switch from Low Band to High Band.

"It breaks the scan into 4 parts. Vert, horz, 10700 to 11700, and 11700 to 12750, even though I did not specify a two band universal."
Some of the images I used did do that with a standard ku lnb when the scan start frequency isn't changed. Change the scan start frequency to 11700 and the end frequency to 12200 and it should give you a two part scan process instead of four.

In regards to the threshold, if you were using a universal, the settings would be:
Lo 9750, Hi 10700, Threshold 11700 and have the 22khz switching on.

 

[Pixl]

I had to go back to configuring Ku on the LNB2 template. Setting up Ku on LNB1 template greys out all my C band sat channels. At this point I was able to get the Huntington beach cams and several NBC channels by doing a manual scan on those TPs. So this tells me the Ku dish and switch port 4 is working. Something not right with the LO settings that affect blind scan on Ku. Blind scan works great on C band. The lnb menu choices does not have a predefined setting for a standard single band Ku lnb. Anyone have blindscan working with Ku ??

 

[Pixl]

Change the scan start frequency to 11700 and the end frequency to 12200 and it should give you a two part scan process instead of four.

I have tried this and it does drop back to a 2 part scan, but finds nothing.

 

[eastof111]

This is my current setting for 103º ku using 8x1-> on input 2 -> 4x1 -> on input 2.

Here are some pixs.

 

[Pixl]

This is my current setting for 103º ku using 8x1-> on input 2 -> 4x1 -> on input 2.

Here are some pixs.

East,

I matched my settings to your screen shots ( only a minor change to the scan range) it stops on several TPs along the way, but finds no channels. Maybe something broken in the blindscan of my image?

 

[eastof111]

You might play with the voltage mode under the advanced setting and change it to 13 v then scan and see what happens. The same for 18v.

But prior to doing that go to the sat finder and select the appropriate tuner, then the sat, then user defined transponder then see if it scans Huntington.

 

[Pixl]

You might play with the voltage mode under the advanced setting and change it to 13 v then scan and see what happens. The same for 18v.

But prior to doing that go to the sat finder and select the appropriate tuner, then the sat, then user defined transponder then see if it scans Huntington.

Might be one of my posts got behind. See my post #11 above. I am able to get Huntington that way. So the dish, lnb, and switch setting is working. Just something with blind scan on Ku. C band is ok.

What image are you using?

 

[eastof111]

Yeah, I missed that one.

I remember last year when the Duo2 came out, we were having blind scan problems with some of the tuners and we had to wait till they issued new drivers and eventually new images. I wonder if this is the same case with your receiver and image.

Currently using NFR in flash and I have ATV in usb stick.

Another possibility is when you keep re-flashing an image it will reinstall the system satellite.xml file and if it differs in size and content from your original that you uploaded earlier with your settings, it will create havoc sometimes.

 

[eastof111]

Pixl, you caught my curiosity, so I loaded up ATV and I am getting the same blind scan results.

1 - Satfinder finds and scans 103º on my fixed dish, but no blind scan.
2 - I did a blind scan of 97º ku with the fixed dish and it produced about half of what should be there.
3 - Switched to the bud and Satfinder finds and scans 103º, but no blind scan.
4 - Moved the bud back and forth while watching Satfinder and the signal for 103º did decrease and return to normal when centered.

So, either my settings got corrupted or the image has switch bugs or both.

When I have time this week, I will start from scratch with ATV and load a new image, new sat file and set up my fixed ku dishes and see if they blind scan properly with the 8x1 switch. Then I'll check the bud which uses a 2x1 switch.

 

[Pixl]

Thanks for testing that. You getting the same results makes me look toward the software. The blindscan for C band has a single band template. But for Ku there is no single band template. Just user defined dual band. This may be the trouble, what values do you put in for the box to handle it as a single band scan? I've tried 10750 for lo and hi, also tried different combinations of 10750 and 00000, 11700, and 12200.

 

[eastof111]

I am still trying to figure out what has changed because I've never had a problem blind scanning with my bud before. Satfinder is working (my guess) because it is reading the info from the lamedb file. The current sat.xml (old) system file is what is being read by the blind scan option. Since the lamedb and sat.xml file don't match, I am guessing that's why the blind scan option is not working correctly.

I will try to update the file today using telnet to put the receiver to sleep and see what happens. This has always worked in the past for me.