Nun, dass eine schließende Klammer fehlt, sagt ja schon die Error Message, nur bin ich mir nicht sicher, ob sie hinter ".svalue" gehört.
Schon klar. Aber auch wenn ich nicht so wirklich Ahnung von C habe, war ich mir sehr sicher die Logik hinter dem Patch verstanden zu haben, und wollte Dir einfach nur schnell helfen. 
Hat ja funktioniert.
Ich muss da Thema nochmal aufwärmen...
Bei DVB-T2 scheint die Berechnung wohl noch nicht so ganz zu stimmen?
dvb-fe-tool gibt auf dem SAT>IP Server folgendes aus:
server02 ~ # dvb-fe-tool -a2 -f0 -m -c5
Lock (0x1f) Signal= -16,38dBm C/N= 27,40dB UCB= 0 postBER= 80,9x10^3
Lock (0x1f) Signal= -16,32dBm C/N= 27,60dB UCB= 0 postBER= 79,9x10^3
Lock (0x1f) Signal= -16,38dBm C/N= 27,20dB UCB= 0 postBER= 80,9x10^3
Lock (0x1f) Signal= -16,32dBm C/N= 27,20dB UCB= 0 postBER= 81,3x10^3
Lock (0x1f) Signal= -16,26dBm C/N= 27,50dB UCB= 0 postBER= 81,4x10^3
server02 ~ #Der VDR, bzw. das femon Plugin zeigt aber das an:
[Blockierte Grafik: http://imagizer.imageshack.us/v2/280x200q90/923/Cz7Aog.jpg]
Die Werte vom dvb-fe-tool sind doch eigentlich ganz passabel, woher kommt dann die schlechte Signalbewertung, oder liegt das am femon Plugin, oder gar an satip?
There are two things. First, the femon doesn't support the new API and only signal strength and quality values, scaled between 0 and 100, are supported..
Secondly, SAT>IP protocol provides only signal level and quality measurements. The signal level is scaled between 0 and 255, but no information whether the adaptation is linear or something else:
ZitatNumerical value between 0 and 255 An incoming L-band satellite signal of -25dBm corresponds to 224 -65dBm corresponds to 32 No signal corresponds to 0
The signal quality is is scaled between 0 and 15:
ZitatNumerical value between 0 and 15 Lowest value corresponds to highest error rate The value 15 shall correspond to -a BER lower than 2x10-4 after Viterbi for DVB-S -a PER lower than 10-7 for DVB-S
So, for a certain specific satellite combo it's possible to calculate the actual signal level in dBm, but there's absolutely no info how to do it for DVB-T/T2/C/C2. If you'll find any information, please, send a pull request in Github.
I stumbled over the same description in this spec too. But, even if this spec is rather incomplete here (and on other points too..), one could guess..
Signal level in terms of power in dBm is valid for any other dvb system too, so no difference. It maps to DTV_STAT_SIGNAL_STRENGTH with FE_SCALE_DECIBEL.
No simple mapping from power <-> percent scale is given, because the wanted signal level depends on noise power level (nyquist noise, phase noise,..), selected modulation and goal bit error rate before FEC.
If BER after FEC is compared, the FEC setting goes in too.
For the second one the spec is not precise enough. But given, that for any values for signal quality above zero a video is still visible, on could assume a scale with max 2 or 3 magnitudes of Post-BER that ends at 1e-7.
And again, the goal number of error rate should be similar for other systems. It should map to (DTV_STAT_POST_ERROR_BIT_COUNT/DTV_STAT_POST_TOTAL_BIT_COUNT) and makes sense only,
if DTV_STAT_POST_TOTAL_BIT_COUNT has a reasonable high value.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!