Availink is available on Github.
A ticket created:
https://github.com/a...ailink/issues/3Regarding the VU+, the enumerations used are here:
http://code.vuplus.c...e798eb94eb#l303
FEC_Auto=0
FEC_1_2=1
FEC_2_3=2
FEC_3_4=3
FEC_5_6=4
FEC_7_8=5
FEC_8_9=6
FEC_3_5=7
FEC_4_5=8
FEC_9_10=9
FEC_None=15
FEC_13_45=16
FEC_9_20=17
FEC_11_20=18
FEC_23_36=19
FEC_25_36=20
FEC_13_18=21
FEC_26_45=22
FEC_28_45=23
FEC_7_9=24
FEC_77_90=25
FEC_32_45=26
FEC_11_15=27
FEC_1_2_L=28
FEC_8_15_L=29
FEC_3_5_L=30
FEC_2_3_L=31
FEC_5_9_L=32
FEC_26_45_L=33
enum fe_code_rate {
FEC_NONE = 0,
FEC_1_2,
FEC_2_3,
FEC_3_4,
FEC_4_5,
FEC_5_6,
FEC_6_7,
FEC_7_8,
FEC_8_9,
FEC_AUTO,
FEC_3_5,
FEC_9_10,
FEC_2_5,
FEC_1_3,
FEC_1_4,
FEC_5_9,
FEC_7_9,
FEC_8_15,
FEC_11_15,
FEC_13_18,
FEC_9_20,
FEC_11_20,
FEC_23_36,
FEC_25_36,
FEC_13_45,
FEC_26_45,
FEC_28_45,
FEC_32_45,
FEC_77_90,
};
They don't match with official fec, (and problem is not the enumeration on e2, but what is send on drivers).
Because in order to support VU+ a new code IF VU THEN VU_FEC Else Linux_FEC will be required.
Anyway S2X, even most promo/demo available are causing problems to receivers. If this technology doesn't become mainstream, don't expect manufactures to really pay attention on this.
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916
.
)
