View Full Version : vu+ blind scan how to blinscan C band
i using the black hlod IMG ,can blind sacn the KU band ,But can not to blind sacn the C band
how to blind sacn the C band
as far as i am aware you can only blindscan the KU band there are no other options for C band etc.
as far as i am aware you can only blindscan the KU band there are no other options for C band etc.I'm sure you must be wrong, but I don't have the Uno so I can't say for certain. You need to have a tuner, aerial system, and satellites.xml file set up so that you are able to carry out a manual scan in C-band. If you have trouble with this I'll share my settings for C-band from my Duo.
Then to do a blind scan; just select the correct tuner and satellite.
Start frequency: 0950000000
Stop frequency: 1550000000
That should scan 3600-4200MHz.
Give it a try.
Good luck, and happy C-banding...
hi
i just set it on the box
it is still not to SACN the C band
hi
i just set it on the box
it is still not to SACN the C bandIf you want a helpful answer you'll need to tell us something about your setup.
Do you have an appropriate aerial and LNB for C-band? What are they?
What satellite are you trying to receive.
Is the aerial correctly aligned for that satellite.
Is your tuner correctly set up for that satellite? Post a screenshot of your tuner configuration.
Have you managed to receive any signals from that satellite with a manual scan.
Is your satellites.xml correct? Zip it up and post it.
the lnb C band set is ok,and i can manual scan the satelite.
only the Cband blind sacn can not to sacn any signals
the KU band IS so esay
There is no difference between a Ku-band and a C-band scan. If Ku blind scan works C-band will also.
Are you receiving channels from that satellite in C-band?
Please answer all the questions above in post number #5, and post the screenshot of your tuner setup (for this satellite), and post a copy of the satellites.xml file, otherwise I can't help you further.
There is no difference between a Ku-band and a C-band scan. If Ku blind scan works C-band will also.
Are you receiving channels from that satellite in C-band?
Please answer all the questions above in post number #5, and post the screenshot of your tuner setup (for this satellite), and post a copy of the satellites.xml file, otherwise I can't help you further.
the satellites.xml file has no impact on a blindscan as the blindscan searches the satellite in question for all available transponders then carries it's scan out on those it finds.
the satellites.xml file has no impact on a blindscan as the blindscan searches the satellite in question for all available transponders then carries it's scan out on those it finds.I know that, but I want to establish he has everything properly setup for C-band first. If there are no errors and it still doesn't work then it is obviously a fault with E2 blind scan... but this is still not a problem because C-band and Ku-band operate on the same IF so the receiver will quite happily blind scan a C-band satellite using fudged Ku-band settings.
Right now though the problem is the O.P. has only said he can't scan C-band but he hasn't provided any detailed description of why not. The reason I am asking for all this other data is because whether or not a satellite is C-band or Ku-band is established in the tuner config, not in the blind scan page. This says to me you should be able to blind scan any satellite, irrespective of what band the LNB is designed for, once it has been setup in tuner config.
The main reason I was asking about satellites.xml is because with the Vu+ the C-band and Ku-band transponders must be in different blocks and also with different orbital positions. So, for example at 1ºW you need to setup the C-band block as 0.9ºW and the Ku-band block as 1.0ºW. If they are not done like that some of the satellites become inaccessible (due to some sort of bug in the firmware).
MY C band dish is the motor dish ,1155611557
the satellites.xml
</sat>
<sat name="Chinasat 6B (115.5E)" flags="1" position="1155">
<transponder frequency="3600000" symbol_rate="27500000" polarization="1" fec_inner="5" system="0" modulation="0"/>
<transponder frequency="3640000" symbol_rate="27500000" polarization="1" fec_inner="5" system="0" modulation="0"/>
<transponder frequency="3680000" symbol_rate="27500000" polarization="1" fec_inner="5" system="0" modulation="0"/>
<transponder frequency="3706000" symbol_rate="4420000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3730000" symbol_rate="10720000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3740000" symbol_rate="27500000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3750000" symbol_rate="10490000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3769000" symbol_rate="13400000" polarization="0" fec_inner="5" system="0" modulation="0"/>
<transponder frequency="3780000" symbol_rate="27500000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3786000" symbol_rate="5440000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3796000" symbol_rate="6930000" polarization="0" fec_inner="1" system="0" modulation="0"/>
<transponder frequency="3807000" symbol_rate="6000000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3808000" symbol_rate="8800000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3825000" symbol_rate="6780000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3834000" symbol_rate="5400000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3840000" symbol_rate="27500000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3846000" symbol_rate="5950000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3854000" symbol_rate="4420000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3861000" symbol_rate="4800000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3871000" symbol_rate="9080000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3880000" symbol_rate="27500000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3885000" symbol_rate="4340000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3892000" symbol_rate="4420000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3900000" symbol_rate="6670000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3910000" symbol_rate="6400000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3920000" symbol_rate="27500000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3929000" symbol_rate="8840000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3940000" symbol_rate="5948000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3950000" symbol_rate="11406000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3951000" symbol_rate="9520000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3960000" symbol_rate="3570000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="3980000" symbol_rate="27500000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4000000" symbol_rate="27500000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4020000" symbol_rate="27500000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4040000" symbol_rate="27500000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4060000" symbol_rate="27500000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4080000" symbol_rate="27500000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4100000" symbol_rate="27500000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4116000" symbol_rate="21374000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4140000" symbol_rate="27500000" polarization="1" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4147000" symbol_rate="6150000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4158000" symbol_rate="8680000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4171000" symbol_rate="9200000" polarization="0" fec_inner="3" system="0" modulation="0"/>
<transponder frequency="4175000" symbol_rate="18000000" polarization="1" fec_inner="1" system="0" modulation="0"/>
<transponder frequency="4192000" symbol_rate="6000000" polarization="1" fec_inner="3" system="0" modulation="0"/>
the 115 sat ,i did not have set the 115 sat ku band ,the satellites XML did not KU xml yet
In the blind scan page change the scan band to low.
Also, there is something else weird although I could be completely wrong. The zeros in start frequency and stop frequency are a different size to the rest of the numbers, almost as if they are the letter "o" rather than the number "0". This is even more noticeable because the leading zero of start frequency is the correct size. Like this -> 095ooooooo. How are you entering these? With some sort of keyboard, or using the remote?
Another thing, I would lower the scan stop symbol rate to a more practical value (like 30000000).
What happens when you press OK to do the scan? And why do the zeros look like that?
HUEVOS ,did you have to try to BLINDsacn the C band?
and how to set?
HUEVOS ,did you have to try to BLINDsacn the C band?
and how to set?As stated above I don't own that receiver.
is it have the anyone to use the UNO blindscan the Cband?
i using the black hlod IMG ,can blind sacn the KU band ,But can not to blind sacn the C band
how to blind sacn the C band
I had the same problem with my DM 8000 HD (almost same images) and with the helpof the Dream Multimedia team I found a workaround for the problem (I have a triple C/Ku LNB system on 180 cm dish). Here the workaround...
As I explained before blind scan function does not work for the C band due to a silly bug that does not consider the use of a C band LNB and does not allow to change the scan limits, but ...........
Thanks also to tha Dream Multimedia team help ...
.... I have found a good workaroud to the problem simply modifing the two lines in the file:
/usr/lib/engima2/python/Screens/ScanSetup.py
in the following way:
the following lines ...
# blindscan sat
self.scan_sat.bs_freq_start = ConfigInteger(default = 10700, limits = (10700, 12750))
self.scan_sat.bs_freq_stop = ConfigInteger(default = 12750, limits = (10700, 12750))
have to be modified in the following way ...
# blindscan sat
self.scan_sat.bs_freq_start = ConfigInteger(default = 10700, limits = (3400, 12750))
self.scan_sat.bs_freq_stop = ConfigInteger(default = 12750, limits = (3400, 12750))
When you perform blind scan in the Ku band there is substantially no difference. You have just to remember, if you want to select a different range, to select it within the 10700-12750 range.
To scan in the C band you can now change the limits, since the firmware now allows the modification, by inserting values within the range 3400-4200.
I still do not know what can happen if I wrongly select value outside the LNBs range.
While I am still waiting for a new firmware this workaround is working well for mixed C/Ku band users.
Obviously remember to perform a Enigma system reboot after you have edited the file.
Paolik65
Looking in the Vu+ all the files end with .pyo and the file is just full of gibberish. I guess that means they are compiled files. Where did you find the .py file?
Rob van der Does
22-12-11, 16:54
*.pyo files are indeed compiled *.py's
If you really want the py's go to telnet and give the command
opkg install enigma2-src
*.pyo files are indeed compiled *.py's
If you really want the py's go to telnet and give the command
opkg install enigma2-srcThanks Rob, what will that do exactly? Where will it put the file? Can I just get that file? Or is that going to modify the whole of Enigma 2? Sorry if these are stupid questions. I've written quite a bit of code but I'm a complete virgin when it comes to Python. And how do you change it back to .pyo once modified?
Rob van der Does
22-12-11, 18:27
Installing that plugin will add all the .PY's to the same locations as where the .py's are.
Normally they are left out, as that makes the whole package much lighter. And also, when the PY's are there, they will compile pyo's on every Enigma start (so that takes more time).
So: install the plugin, make any changes to the py's you want, restart E2 and check the result; once you are happy with that, make a backup of the .pyo and delete the src-plugin again.
So what is the command to delete the pluggin?
opkg delete enigma2-src
Rob van der Does
22-12-11, 19:27
opkg remove enigma2-src
I have found a good workaroud to the problem simply modifing the two lines in the file:
/usr/lib/engima2/python/Screens/ScanSetup.py
in the following way:
the following lines ...
# blindscan sat
self.scan_sat.bs_freq_start = ConfigInteger(default = 10700, limits = (10700, 12750))
self.scan_sat.bs_freq_stop = ConfigInteger(default = 12750, limits = (10700, 12750))
have to be modified in the following way ...
# blindscan sat
self.scan_sat.bs_freq_start = ConfigInteger(default = 10700, limits = (3400, 12750))
self.scan_sat.bs_freq_stop = ConfigInteger(default = 12750, limits = (3400, 12750))Those lines are not in that file in the VIX image. Where else could they be?
I had the same problem with my DM 8000 HD (almost same images) and with the helpof the Dream Multimedia team I found a workaround for the problem (I have a triple C/Ku LNB system on 180 cm dish). Here the workaround...
As I explained before blind scan function does not work for the C band due to a silly bug that does not consider the use of a C band LNB and does not allow to change the scan limits, but ...........
Thanks also to tha Dream Multimedia team help ...
.... I have found a good workaroud to the problem simply modifing the two lines in the file:
/usr/lib/engima2/python/Screens/ScanSetup.py
in the following way:
the following lines ...
# blindscan sat
self.scan_sat.bs_freq_start = ConfigInteger(default = 10700, limits = (10700, 12750))
self.scan_sat.bs_freq_stop = ConfigInteger(default = 12750, limits = (10700, 12750))
have to be modified in the following way ...
# blindscan sat
self.scan_sat.bs_freq_start = ConfigInteger(default = 10700, limits = (3400, 12750))
self.scan_sat.bs_freq_stop = ConfigInteger(default = 12750, limits = (3400, 12750))
When you perform blind scan in the Ku band there is substantially no difference. You have just to remember, if you want to select a different range, to select it within the 10700-12750 range.
To scan in the C band you can now change the limits, since the firmware now allows the modification, by inserting values within the range 3400-4200.
I still do not know what can happen if I wrongly select value outside the LNBs range.
While I am still waiting for a new firmware this workaround is working well for mixed C/Ku band users.
Obviously remember to perform a Enigma system reboot after you have edited the file.
Paolik65
I have not those lines on my DM 820HD
some help to use blind scan on C band,please?
Thanks!
(5 year old thread)
Yes I know but I have the same problem... I can´t to do blind scan on my DM 820 on C-band
Could you help me?
Thanks!
Sorry your receiver is not supported by OpenViX. This thread is about Vu+.
genius5000
04-03-17, 20:30
5 and half year old thread !
I have the same prob ...
I am using VTI img on VU+Duo².
VTI blokes dont really care about C-Band, so they dont answer my inquiry there.
So, what do I have to do in order to BLINDSCAN my C-Band satellites?
I have updated the satellite.xml (etc/tuxbox) from http://satellites-xml.eu (all)
I'd really appreciate your help. I am waiting for this for a long time now.
There must be some way to do it !
Thanks a lot.
el bandido
05-03-17, 04:56
5 and half year old thread !
I have the same prob ...
I am using VTI img on VU+Duo².
VTI blokes dont really care about C-Band, so they dont answer my inquiry there.
So, what do I have to do in order to BLINDSCAN my C-Band satellites?
I have updated the satellite.xml (etc/tuxbox) from http://satellites-xml.eu (all)
I'd really appreciate your help. I am waiting for this for a long time now.
There must be some way to do it !
Thanks a lot.
The answer to your problem about blind scanning C band is simple:Use an image like VIX that supports C band blindscan. Or modify the blindscan plugin yourself and make it work in ViTi.
genius5000
08-03-17, 09:49
The answer to your problem about blind scanning C band is simple:Use an image like VIX that supports C band blindscan. Or modify the blindscan plugin yourself and make it work in ViTi.
Hey, thank you for your reply.
I wouldn't like to move to ViX yet as I really like one of VTI skins a lot :D
I would really appreciate it though if you explain as to how could I modify the VTI-Blindscan app in order to scan the C-Band satellites?
Greetings.
el bandido
08-03-17, 13:44
It has been about 3 years or more since I put a c/ku blindscan plugin in Viti or BlackHole.
The big question is: Can you transfer files to the box using FileZilla or similar file transfer program ?
genius5000
08-03-17, 17:50
It has been about 3 years or more since I put a c/ku blindscan plugin in Viti or BlackHole.
The big question is: Can you transfer files to the box using FileZilla or similar file transfer program ?
Yes, I do use FileZilla for my Duo².
I wouldn't like to move to ViX yet as I really like one of VTI skins a lot :DThat is like saying you are going to stick with a dodgy girlfriend because you like her coat.
I would really appreciate it though if you explain as to how could I modify the VTI-Blindscan app in order to scan the C-Band satellites?Why would you want to modify that crap plugin when there is a brilliant blindscan plugin that works properly in C and Ku bands. And doesn't have those stupid number fields and all the other problems.
el bandido
09-03-17, 05:10
It used to be fairly easy to make OE blindscan plugin work in Vti. Not anymore, or Not Today.
53082
As you can see, I got the plugin to install, but it would not find any transponders for C band. There is too many issues for me to mess with on this one.
Your only other Good option would be to import a channel list that has C band channels in it. IMO, your Best option will be to not use VTi because it does not support c band blindscan. Their loss, your gain.
genius5000
09-03-17, 10:25
That is like saying you are going to stick with a dodgy girlfriend because you like her coat.
It's not that really ... y'see, I worked really hard to modify that infobar skin I'm using,
Could I still use it with ViX? If yes, then I could give it a try :)
genius5000
09-03-17, 10:29
It used to be fairly easy to make OE blindscan plugin work in Vti. Not anymore, or Not Today.
53082
As you can see, I got the plugin to install, but it would not find any transponders for C band. There is too many issues for me to mess with on this one.
Oh, this screenshot looks good ... freq rage is perfect ... I could never come this far with the blindscan app on VTI. :confused:
genius5000
09-03-17, 11:15
Hey ...
I've just installed ViX and tried out Blindscan for C-Band, but it doesnt find any transpoder, it says !
Manually, it finds though.
el bandido
09-03-17, 13:07
Post some screenshots of what happens in OpenVix c band blindscan.
genius5000
09-03-17, 13:24
it says: No transponders were found ...
how do I screenshot here ... by HELP button ?
it says: No transponders were found ...
how do I screenshot here ... by HELP button ?OpenWebif has a screenshot facility.
genius5000
09-03-17, 13:34
well it basically the same config as your screenshot (3600-4200 Mhz, etc) ... result = No transponders were found.
I have tried out now OpenPli, OpenSpa, OpenATA ... all of them have the same result.
I wonder BLINDSCAN really works for C-band on Enigma2 at all !
el bandido
09-03-17, 14:37
C band blindscan works unless the image has issues.
What tuner in the duo2 are you trying to scan?Only internal tuners A and C support blindscan
Do you have any External usb tuners connected or other usb devices connected to the receiver(DVB-T...etc)? Try removing them, hard boot the box and try again.
genius5000
09-03-17, 14:59
Only internal tuners A and C support blindscan
aha ... that mustve been it. my C-band sat is set on D tuner. I can move it to C.
but, i've moved back to VTI. nothing against you guys. I think I prefer VTI. :)
I have tried all the other images in the last hour or so, it would be like moving Windows to Mac.
if it is still possible for you to help me out with this, provided I move my C-band to C tuner, I'd be very grateful :)
thanks a lot.
genius5000
09-03-17, 16:25
C band blindscan works unless the image has issues.
What tuner in the duo2 are you trying to scan? Only internal tuners A and C support blindscan
Well. I've just tried out blindscanning the tuners A B C for Ku-band on VTI. They all scan. So, it's not only A & C tuner that does it.
My D tuner is not blindscanning because it is C-band. I'm not sure if there's any use moving the C-band sat on to the C tuner if I'm still on VTI !?
well it basically the same config as your screenshot (3600-4200 Mhz, etc) ... result = No transponders were found.
I have tried out now OpenPli, OpenSpa, OpenATA ... all of them have the same result.
I wonder BLINDSCAN really works for C-band on Enigma2 at all !C-band works fine in Blindscan. It was me that wrote that part of the plugin.
What tuners do you have installed? What receiver? What dish size? What LNB? What is the L.O.F. of the LNB? What satellite are you trying to scan.
Well. I've just tried out blindscanning the tuners A B C for Ku-band on VTI. They all scan. So, it's not only A & C tuner that does it.
My D tuner is not blindscanning because it is C-band. I'm not sure if there's any use moving the C-band sat on to the C tuner if I'm still on VTI !?Second tuner of AVL6222 does not blindscan properly due to either a faulty binary or hardware problem. This is nothing to do with the plugin. Please save the plugin from VTi and zip it and post it here.
Andy_Hazza
09-03-17, 19:57
I have tried all the other images in the last hour or so, it would be like moving Windows to Mac.
Yeah Mac is better. [emoji4]
Sent from my iPhone using Tapatalk
el bandido
09-03-17, 20:10
Second tuner of AVL6222 does not blindscan properly due to either a faulty binary or hardware problem. This is nothing to do with the plugin. Please save the plugin from VTi and zip it and post it here.
(Plugin Attached)
Yeah Mac is better. [emoji4]
Sent from my iPhone using Tapatalk
Linux (Ubuntu) for me.
genius5000
09-03-17, 20:48
C-band works fine in Blindscan. It was me that wrote that part of the plugin.
What tuners do you have installed? What receiver? What dish size? What LNB? What is the L.O.F. of the LNB? What satellite are you trying to scan.
Hey, thank you for your reply. The details as follows:
VU+ Duo²
Tuner : D (for C-Band / 76.5E)
Dish Size : 240cm Mesh
LNB : C-Band
LOF : C-Band
more info in the attached screenshots ...
genius5000
09-03-17, 20:50
Second tuner of AVL6222 does not blindscan properly due to either a faulty binary or hardware problem. This is nothing to do with the plugin. Please save the plugin from VTi and zip it and post it here.
OK.
Where is the plugin folder in enigma2/VTI anyway ? ...
Alright, I got it :-)
Attached: VTI Blinscan plugin
Hey, thank you for your reply. The details as follows:
VU+ Duo²
Tuner : D (for C-Band / 76.5E)
Dish Size : 240cm Mesh
LNB : C-Band
LOF : C-BandAs already explained second tuner of AVL6222 does not work properly for blindscan. Returns empty scans.
You will not get VTi plugin working in C-band without a major rewrite.
TBH the plugin is crap. And not user friendly. Just look at the frequency entry. Completely meaningless to a human being. Who writes this rubbish?
genius5000
09-03-17, 22:10
As already explained second tuner of AVL6222 does not work properly for blindscan. Returns empty scans.
You will not get VTi plugin working in C-band without a major rewrite.
TBH the plugin is crap. And not user friendly. Just look at the frequency entry. Completely meaningless to a human being.
yeah, completely agree with you !
So, even if I set my C-Band sat to the tuner C, it still won't work ?
btw, when I blindscan tuner A B C for Ku-Band sats, it does work normally on VTI.
when I blindscan tuner A B C for Ku-Band sats, it does work normally on VTI.Can you get me a debug log of tuner B working "normally" during a blindscan.
el bandido
10-03-17, 00:31
I have 4 internal DVB-S tuners in my Duo2. Tuners A and C have always blindscanned for me, while tuners B and D do not blindscan in my Duo2 receiver.
C Band blindscan Today on tuner C:
53100
53101
I've got an AVL6222 tuner. I've tried it in Ultimo and Solo4K. Only ever works when searching on input 1. Input 2 always returns an empty search.
genius5000
10-03-17, 08:39
Can you get me a debug log of tuner B working "normally" during a blindscan.
Excuse my ignorance ... how do I do that ?
please help :(
Excuse my ignorance ... how do I do that ?Don't ask me; you're the VTi expert round here.
genius5000
10-03-17, 17:13
Don't ask me; you're the VTi expert round here.
Okay, I've done all kinds of blindscan tests with all 4 tuners on VTI @ VU+ Duo2, and the results are as follows:
Tuner A & C = Do blindscan normally for Ku-Band.
Tuner A & C = Do blindscan abnormally for C-Band.
It works for C-Band only if you set the LNB as Universal LNB, but then, all kinds of random Ku-band ferq & SR for the C-band channels !
Tuner B & D = Cannot do any blindscan.
@Huevos, since you wrote this plugin, perhaps you could rewrite/tweak it in order to make it USEFUL on VTI ?
At least, if you let few of us to use it properly for C-Band ? :D
Thanks
@Huevos, since you wrote this plugin, perhaps you could rewrite/tweak it in order to make it USEFUL on VTI ?
At least, if you let few of us to use it properly for C-Band ? :DI didn't write the plugin. I rewrote it. I've got no interest in modifying it for VTi. Life's too short to waste time on that. If VTi had any interest in providing a decent product for their users they could have included my changes 5 years ago.
genius5000
10-03-17, 18:29
Yes, VTI thinks people are only watching 19E & 13E :D
So for that matter, they also taken off all other picons from their feed :D:D
Let me tell ya ... VTI have at least 13 to 19 reasons for not making Blindscan a C-Band friendly app :D:D:D
eldereli84
10-04-17, 11:58
hello all
ı want buy new receiver and use blindscan for c band ,which receiver using in c band blind scan ?
can u help me
el bandido
11-04-17, 04:10
Any enigma2 receiver that blindscans the ku band should also blindscan the c band. But not all enigma2 images support a c band blindscan.
eldereli84
11-04-17, 06:49
which images use c band blindscan
eldereli84
11-04-17, 19:19
help me frs
eldereli84
12-04-17, 16:18
ı dont know this ''All OE-A images.''
open pli blindscan is ku band work c band not work
which images you suggest
el bandido
12-04-17, 18:56
C band blindscan works in OpenPLi.
A couple of the Vu+ images such as Blackhole and VTi do not have C band blindscan.
It might be better or easier to tell us what receiver you are getting instead of asking which images do not blindscan c band.
eldereli84
13-04-17, 18:35
http://i67.tinypic.com/2eqb86p.jpg
please help me
receiver : dm500 hd
image: openpli 4 04-04-2017 image
tuner: bcm4505
ku band blindscan working but c band blindscan not work
how is work c band blindscan helping myfr
This box does not have hardware blind scan on C-Band.
eldereli84
13-04-17, 23:00
This box does not have hardware blind scan on C-Band.
which model receiver use blindscan for cband
eldereli84
09-10-17, 18:55
myfriends please help me
which models have a c band blindscan tuner
ı want to buy new receiver but ı want to use cband blind scan
It has nothing to do with the tuner. The frequency conversion is done at the LNB. So any reciever that has blindscan for Ku will work for blindscanning C band as well. Just make certain it is blindscan capable in Ku.
eldereli84
20-10-17, 20:23
please add the fotos friends which receiver use blindscan cband
ı want to buy new receiver but ı dont know which receiver and images have c band blindscan ?
I guess you didn't read my post above.
My preferred is Vu+ Solo2 and OpenViX image.
But not current enigma2 receiver is perfect for blindscan, especially weak signals or low symbol rates.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.