SATPI
SATPI copied to clipboard
Barracuda09
Gigablue: Signal strength is sometimes wrong (2 instead of 240)
I am not sure what you need to understand my problem. But my signal strength is sometimes not read correctly. instead of 240 a 2 is transmitted. then again the 240. this leads in the TVheadend to jumping signal strengths from 1% to 100%. I have a Gigablue UE4K in conjunction with a Gigablue SCR LNB
Hello @SaulGoodman1337
Does it jump more then 1 time (only in the begin) or just all the time? is it regular intervals?
Hi, All the time and there is no Intervall. I think its a parsing issue. Sometimes the Signal strenght ist 240 then 2, then 4 and then 240.
4.3 But I think that is irrelevant. The values already come out wrong from SATPI. But I can not exclude whether the values already come wrong from the tuner ?
Is the value jumping in the also in the SatPI web interface?
Yes, exactly. However, I don't know if this already happens on Enigma level. Wait, I just look for the remote control, configure a tuner and go into the satfinder.
But the streams seem OK..
The stream is perfect... I think something strange is happening here when parsing. but I must confess that I don't quite understand your code here. can you possibly tell me at which point you do this exactly?
I use an android phone, it has SAT>IP Alignment app. if you use an android phone you could try that?
https://github.com/Barracuda09/SATPI/blob/6b90b138ec2903254be982793a485dd43d7aa05e/src/input/dvb/Frontend.cpp#L292-L300
https://github.com/Barracuda09/SATPI/blob/6b90b138ec2903254be982793a485dd43d7aa05e/src/input/dvb/FrontendData.cpp#L334-L350
https://github.com/Barracuda09/SATPI/blob/6b90b138ec2903254be982793a485dd43d7aa05e/src/output/StreamThreadRtcpBase.cpp#L105-L130
Do you have some TCP data where it shows there is an parsing error?
No, that was a guess. But I think that I was on the wrong track. I have now played again with the signal finder in Enigma and then found that the error also occurs there. sometimes ACG is 0% ... However, if I activate the following in the tuner option: "force legacy signal stats" in the tuner option it works and the signal strength is constant at 99%..... The description says that the data is then calculated from a V3 API . maybe that tells you something? I can live with the error but it would be nice if it could be solved somehow. but now I'm not sure if this is a satpi problem at all.
Yes, In SatPI there is something similar. Only it will switch to old API when it can not read the new one.
https://github.com/Barracuda09/SATPI/blob/6b90b138ec2903254be982793a485dd43d7aa05e/src/input/dvb/Frontend.cpp#L307-L310
ah, we're getting closer. I think it would make sense to offer the following setting for the option in the web interface:
- Automatic
- V5? Api
- V3 API (deprecated)
how does that sound to you?
Yes perfect!!
Here is an test version: satpi_armv7ve_force_oldapi_V1.6.2-11-g6b90b13.tar.gz
it does not work,sorry. i have checked several times to make sure that i have really pushed the correct binary onto the box. edit: the same as before. wrong values
Strange.. So it is the same outcome??
yes exactly the same behavior as before too. i'll check the satfinder again...
Change stb image and problem will disappear. This is common problem.
I will try this out today and report back.
Change stb image and problem will disappear. This is common problem.
Any recomendation?
Ok, I did not know of this problem (or if this is a driver issue). But I do not use openatv on my Gigablue and Vu+ FBC receivers.
Do you use Enigma?
I use on Gigablue the TeamBlue image and Vu+ just stock image. But I do not use Enigma I use openatv on my Vu+ zero 4k and have Enigma runing. but do not see this problem there.
I use the box completely headless. Tomorrow I will try it with the teamblue image.