Post a screenshot please.This bug only it's showing info, not scanning. The frecuencies from 11701 to 12700 show 14xxx.
Vu+Uno. I update OBH 0.1 via net, the problem continue.
I use a motsat3 diseqc motor.Universal should be correct, depending on your LNB. You could try the User Defined option, and manually enter the details.
I am using a 36V motor, so I have to use the Diseqc 1.2 option, without Usals, can you please explain your satellite set up and why you're using the Tuner Advanced option, and still using Usals?
I haven't heard of anyone else, running Open Black Hole 0.1, having this problem. Can you try your receiver on another dish/LNB setup?
If I have not problems scanning, tuning and viewing channels with the high ku band it mean that LNB and his setting it's ok. The problem it's showing info, In Low band show the true frecuency of the channel. In High band show channels the frecuency + 2863 MHz , why? I think it's a calc error in a script. 2863 MHz like the C bad?I haven't heard of anyone else, running Open Black Hole 0.1, having this problem. Can you try your receiver on another dish/LNB setup?
Re-flash and same problem. I have not another LNB but the unic one that I have work fine, tested with Black Hoole 2.1.7. I tested a lot of options in the LNB setting and always there is that problem with Open Black Hole. I forgot to mention that the false frecuency i's showed only when the tuner have signal. If I move the dish until lost the signal the showed frecuency it' OK.If it's a calculation error, in the software, I would have thought other users would have reported it, this seems to be unique, to you.
Perhaps a re-flash, or a new image, might be worth testing, but I think I'd still check it on another LNB, just to rule out that the problem is with the LNB.
Thanks you very much for to confirm it. Now I'm quiet, BH guys solve it.I can confirm the same problem on my duo2. It's an image problem as pli has the same error.