I find blindscan in the SF8008 Supreme to be a bit unstable. My log files show over 600 blindscans since I have owned the Supreme, which would be a few months. Sometimes the blindscan hangs for no apparent reason, and this is why I say it is a bit unstable.
The blindscan plugin is nothing more than an interface for the blindscan binary file in /usr/bin of receiver files. It is possible to blindscan using the terminal and the proper blindscan command. The receiver has to be tuned to the correct band and polarization for command line blindscan to work. The blindscan command in terminal for me might look like this:
start_freq, end_freq, start_symbol-rate, stop_symbol-rate, pol, hilow[band], feid, NimSocket, is_c_band_scan, orbit
Note the orbit command in the blindscan. For some reason, the blindscan binary wants to look at your transponder list in satellites.xml. I have disabled this and point to a fake orbit in my satellites.xml (2100).
In terminal, I would enter this:
cd /usr/bin
octagon-blindscan 950 2125 1 60 1 0 0 2 0 2100
Then after a while, I would get a return of found transponders in the terminal screen.
You can change the command to .8 in the Supreme for the symbol rate start value, and the blindscan will return transponders down to 500 symbol rate.
octagon-blindscan 950 2125 .8 60 1 0 0 2 0 2100
The test above is not stable, and sometimes the blindscan will hang when the .8 symbol rate start value is used. But it does work. A video of this has been made and sent to Octagon. We will see if anything is done with it. But this test does demonstrate the Supreme can indeed find and log transponders down to a 500 symbol rate under the right conditions.
I find almost any transponder below 1000 symbol rate to be unstable. There is a 675 symbol rate transponder on 117w c band that has radio channels. Most of the time, this transponder works. But sometimes it doesn't. The 675 symbol rate transponder Does Not work at all after a blindscan until the receiver is rebooted. Another reason why I say unstable...