Anaconda Blind Scan Problems

Jim S. said:
My bad, I was assuming something based on what costac said in another thread. He said that if you select manual, it comes up with the right numbers automatically, but he was talking C-band. On Ku-band, it doesn't.

BTW, I'm getting the impression that the scan on the Gekko is really buggy. I'm trying to scan AMC-6 Ku, and not only did it blow through the vertical side in no time at all with finding no transponders (whereas we know that most of them on that bird are in fact vertical), it's been hung for quite a while at 81.2% on the horizontal side. (The Openbox did that once upon a time when they were playing with the blind scan parameters. The part about hanging on AMC-6 Ku horizontal, not the part about blowing through the vertical. It did the vertical just fine. I wonder if skipping the vertical is another manifestation of whatever bug makes it sometimes skip the scan altogether. I really have this gut feeling that there's some bogus data in the satellite list somewhere that's making it do that. It would be SO nice if we could delete satellites and rebuild from ground zero rather than having to edit the satellites that are already there, then we'd know if that was the source of the problem.
Click to expand...


This is exactly the same thing I experienced. I'm using the latest firmware version 2.10.29.
 
So what are we calling invalid? I've been using 11700 - 12200, and sometimes it works and sometimes it doesn't.

I've noticed that I have slightly better success leaving it on universal and limiting the range than trying 10600 with 22k on, but only slightly. Either way sometimes ends up blowing through the scan!
 
If you make a mistake and enter 117000 instead of 11700 then your blind scan will complete in a couple of seconds without finding anything. Try it and see.
You cannot check and see if you made a mistake after a blind scan because the manual values that you entered are not stored.
 
For every second blind scan yesterday, I had to reboot my anaconda so it wouldn't blow through the scan- 11700-12200 every scan.
 
From advise from EB, I saved all channel and sat info. Factory defaulted my anaconda and retransferred all my info back- been great ever since. I also decided to delete some unwanted encrypted channels- that menu is quite impressive.
 
Costactc said:
From advise from EB, I saved all channel and sat info. Factory defaulted my anaconda and retransferred all my info back- been great ever since. I also decided to delete some unwanted encrypted channels- that menu is quite impressive.
Click to expand...


But my blind scan problems occurred right out of the box before any satellites were setup. My very first scan took roughly 40 minutes and then I constantly had to repower the unit. However, I'll try the factory default.
 
A factory default will not fix a 40 minute blind scan but it may fix the scan running from 0 to 100 in a few seconds. I think this 0 to 100 scan problem is corruption or an incorrect setting.

New firmware has been released for some of the other Fortis receivers, and I imagine it will not be long before Optibox has some new firmware too. Whether the new firmware will blind scan any better remains to be seen. EB
 
Last night I removed the Ecoda 22KHz switch from my system and performed 7-9 blind scans and the "L-Band of Universal LNB with Horizontal Polarity" message didn't appear once. I'm going to continue testing without the Ecoda 22KHz switch until I'm convinced the problem no longer occurs.
 
You never know it could well be the switches..I run a single LNB from my C-Band dish and have not had one lockup apart from when I installed webzeal, I did need a hard boot in this case.
I have yet to see scanning stopping or freezing at 81% either or blowing through transponders the Anaconda always completes the scan on all polarity's.

My blindscan times average 25-30 minutes. I didn't really want to say I am not experiencing any of the problems before, as you know I sell them at LegitFTA-Shop and some would think because of this I would there is not a problem.

Not the case though, I fully believe you guy's are having these issues. So even if it is a switch issue, this needs to be fixed as well as speeding up the blindscan..I like to feed hunt as well and if we could get it down to 10-15 minutes, I think most would be pretty happy. I would not expect it to be much faster than that or we may lose the accuracy.

We have sent the requests for changes to be made..I was told it would take a few weeks for the needed changes...Just don't carve that in stone...lol
They were pretty quick to make an NTCS file for us because of the simplicity of changes on that, but my understanding is this requires a good deal more work.

So all we can do is hang in there and keep testing for any other issues.

Myself If I see any switch issues if thats the case fixed and the blindscan speed-ed up, I think this Anaconda is good to go.
 
No switches on my end either. Turns out to be about 1 reboot per 5 blind scans and hopefully blind scan speed can be addressed as well.
 
Costactc said:
No switches on my end either. Turns out to be about 1 reboot per 5 blind scans and hopefully blind scan speed can be addressed as well.
Click to expand...

This is very odd to me.. when I set up the Anaconda, I scanned my C-Band arc from 55W to 123W through the whole day non stop.. not one single reboot needed and all scans completed... Go figure!
 
I can't see it only occurring when scanning on ku band. I initially set my anaconda up on c band and scanned all sats- don't recall having this issue. My receiver is set up on my ku feed and it happens on a daily basis. My ku blind scans are always 11700-12200 unless scanning a sat with lower frequencies and c band was 3600 or 3700-4200 depending on the sat.
 
SatelliteGuy said:
Perhaps it only occurs when scanning KU band.
Click to expand...

Am I the only one using the Anaconda on C-Band ? Costa said he did not see this when on C-Band and he does now on KU, I will hook up the Anaconda tomorrow on my KU and see if I get the same.. Thanks all for your input.
 
I am scanning Amc6 at the moment on c band with my anaconda. I had forgotten that default when you go manual in the blind scan menu was 3700-4200, just wondering if its an issue because you actually have to change the numbers for ku band.
 
3700 and 4200 are not default scan parameters. They are only numbers that appear when you select manual mode.

In automatic mode, the entire range is scanned from about 950 MHz to 2150 Mhz.
To find out what is being scanned in automatic mode, subtract 950 from 5150 for your high limit and 2150 from 5150 for your low limit. EB
 
Did it again EB. I meant default when you choose the manual option. So far I haven't encountered any issues on c band at all and I have changed the frequency several times. I'm thinking that when you input 11700-12200 for ku and the scan starts at 27.9% that it just jumps but I can't explain it.
 
Back
Top