Blind Scanning with LNB L.O. of 10750 the Octagon SF8008 Twin tuner doesn't find any transponders. I have used the Circular LNB, User Defined of LOF/L= 10750, LOF/H=10750 Treshold=11700 or 12700, Tone Mode = On/OFF settings, and nothing works. But when I manually scan a transponder using L.O. = 10750, it scans in the channel. On the other hand, setting the "LNB Type" to Universal, I'm able to scan in transponders, but they're off by 150MHz. This is happening on OpenATV 6.3 with the latest Image.
Octagon SF8008 Twin Tuner KU Issues
- Thread starter Babadem
- Start date
I wonder if maybe using blind scan start frequency 11750 will help and Circular LNB. That's what I have to do with the mutant HD60 but it uses DMM blind scan.
Post a screenshot of the blindscsan menu. Thanks.
Blind scan may be broke with the latest openatv. I updated my os mio4k earlier today (satdreamgr-6) kernel 5.3.0 and my blind scan was doing the same no transponders found so I went back to a backup kernel 5.2.0 now it is back to normal.
45000 SR is probably the max on the octagon.
45000 SR is probably the max on the octagon.
Let's see the output from the VIX image in post#4 We can use this telnet command:
init 4 && enigma2 > /tmp/debug.log 2>&1
Enter the above command then do a blindscan.
Get the debug.log file from the /tmp folder after the blindscan is complete, then zip it and attach it here.
type Control c (Ctrl + c) to stop the debug log, then type init 3 to restart the box.
init 4 && enigma2 > /tmp/debug.log 2>&1
Enter the above command then do a blindscan.
Get the debug.log file from the /tmp folder after the blindscan is complete, then zip it and attach it here.
type Control c (Ctrl + c) to stop the debug log, then type init 3 to restart the box.
Change the Tone mode from Off to Band. This is for the 22KHz tone in the antenna setup. See if that makes a difference.
I get these errors when I run telnet and blind scan. I have checked and triple checked the commands. Can the system generate a debug file without those commands? Btw, I used putty for telnet.
Attachments
Some images can, but the results would probably be the same. I do not normally work in OE Alliance images, and some things are different from PLI.
Post the log that was made. Let's see if we can find the issue with what is in it.
Get the log from /tmp, then reboot the box. Then change the 22KHz tone from Off to band and try a blindscan.
Post the log that was made. Let's see if we can find the issue with what is in it.
Get the log from /tmp, then reboot the box. Then change the 22KHz tone from Off to band and try a blindscan.
Debug file
View attachment debug.zip
Even though the same error as as in the screen shots above are still present, I ran a blind scan without the command and this is debug log I found in the temp folder, I don't know if it's what you need. Thanks.
View attachment debug.zip
Even though the same error as as in the screen shots above are still present, I ran a blind scan without the command and this is debug log I found in the temp folder, I don't know if it's what you need. Thanks.
I tried that in OpenATV it didn't work. As noted earlier, the only one that works flawless with Circular/L.O of 10750 is that version of OpenVix, I posted above.
The log shows you have a single tuner for satellite or one DVB-S tuner, correct?
There are some time-shift remarks which may explain the tuner busy message.
It is great that you have an older OpenVix image that works, but it will not help us much. The blindscan plugin has been upgraded and altered since that old VIX image was released, so we will have to work with something new to fix it.
SatDreamGr is similar to PLI, and I am more used to working with it. That is the image we need to try and get working. Please reload it and check the following.
(1) Repeat the same test to make a debug log.
(2) Change the lnb to Universal, Then blindscan and report what that produces.
(3) Try a C band blindscan and report what it produces.
Maybe doing the above 3 things will get us somewhere or tell us something.
There are some time-shift remarks which may explain the tuner busy message.
It is great that you have an older OpenVix image that works, but it will not help us much. The blindscan plugin has been upgraded and altered since that old VIX image was released, so we will have to work with something new to fix it.
SatDreamGr is similar to PLI, and I am more used to working with it. That is the image we need to try and get working. Please reload it and check the following.
(1) Repeat the same test to make a debug log.
(2) Change the lnb to Universal, Then blindscan and report what that produces.
(3) Try a C band blindscan and report what it produces.
Maybe doing the above 3 things will get us somewhere or tell us something.
I just saw this as I was about to upload an updated image debug log from Openvix. Yes, I'm currently using only one turner for now. I will do the above steps as instructed later. Meanwhile, please take a look at this debug file.
Last edited:
It looks like a semi-successful blindscan that generated a ton of errors:
Move to an image type that I am used to working with and we will try to fix it. It should be "doable" from what I see in the second log.
Stick with 103 Ku as a test. That satellite should blindscan easy and I am used to seeing the transponders on it.
Move to an image type that I am used to working with and we will try to fix it. It should be "doable" from what I see in the second log.
Stick with 103 Ku as a test. That satellite should blindscan easy and I am used to seeing the transponders on it.
Using SatDreamGr didn't result in any success in either Universal, Circular for KU nor Cband Blindscan. See attachments.
Attachments
Debug File and Telnet command line screenshot attached.
Attachments
I gave you the wrong command line. PLI based images are different.
Repeat the blindscan with debug log using this terminal command.
init 4 && ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/debug.log 2>&1
Post the output after starting the log and doing a blindscan.
We can probably take a couple of files from the older image that works, and make the newer image work, but some idea of what is going on would be great. The failed blindscan log may give a clue! We will see...
Repeat the blindscan with debug log using this terminal command.
init 4 && ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/debug.log 2>&1
Post the output after starting the log and doing a blindscan.
We can probably take a couple of files from the older image that works, and make the newer image work, but some idea of what is going on would be great. The failed blindscan log may give a clue! We will see...
As requested see debug log attached.
What happens when you use the other tuner for blindscan? Try setting a satellite up on it and blindscan it.
I will try that as soon as I can. But what did you find out from the last debug log that I posted?