60.0°E Intelsat 33e

11463 V,20082,77/90,16APSK,RollOff:0.20,CCM-Data,-new mode,symbol rate,fec.
11463 V,20082,2/3,S2X/16APSK,RollOff:0.20,CCM-Data

11739 H,14455,7/9,(S2X)/16APSK,RollOff:0.10,CCM-Data

Zitat

Original von satesco
11463 V,20082,77/90,16APSK,RollOff:0.20,CCM-Data,-new mode,symbol rate,fec.
11463 V,20082,2/3,S2X/16APSK,RollOff:0.20,CCM-Data

11463 V,21910,77/90-new symbol rate

Zitat

Original von satesco

11463 V,21910,77/90-new symbol rate

Zitat

Original von satesco
11739 H,14455,7/9,(S2X)/16APSK,RollOff:0.10,CCM-Data

Both S2X transponders have left.

Zitat von satesco

11463 V,21910,77/90-new symbol rate

11464 V,25000,13/45,(S2X)QPSK,0.15,ACM-new mode & symbol rate,

11630 V,26954,13/45,(S2X)QPSK,ACM-Packetized,new.Locked both with tbs6590.

11135 H,36855,13/45,(S2X)/S2,0.05,ACM-Packetized.It's not new, KooLy on FlySat, now it's also in S2X.

11793 H,3549,9/20-Data,new

I found several modulations with the tbs6902se card for 11793 H. But for sure 11793 H is in S2X even if the signal is problematic, because I think it comes from a cell/beam far from my area.Precisely because of this, to which I add that the 6902se card is still to be explored by the developers to be sure that the parameters found, especially the 256 APSK modulation can be correct.

With all the doubts I have about this 256APK, I'm still posting this finding, because it's the first time I've ever had such a signal locked in this this post. Maybe we'll get a confirmation another time and with another card. Could it be an app bug?

Zitat von satesco

...

11793 H,3549,9/20-Data,new

...

I found it again on 11793 H,3549,7/9,(S2x)/16APSK,0.15, and this time I locked it with the tbs6902s card. I can confirm that it is active.