55E (Yamal 402)

[Channel Hopper]

The VIX image suggests the satellite is at 54.9 degrees East but I find it is about half a degree off.

 

[Channel Hopper]

Ah, looks to be correct.

Technical details for satellite YAMAL 402

YAMAL 402 was supposed to maneuver itself into a circular geosynchronous orbit 22,300 miles (35,888 km) up and lowering inclination where it can match Earth's rotation and appear parked over the equator at 55 degrees East longitude to begin a 15-year service life. However the upper stage of the...

www.n2yo.com

 

[moonbase]

The VIX image suggests the satellite is at 54.9 degrees East but I find it is about half a degree off.

OpenViX reads whatever is stored in the satellites.xml file that is loaded into the receiver.
The normal locations of the file are /etx/tuxbox/satellites.xml or /etc/enigma2/satellites.xml

I simply loaded into the SF8008 a recent xml file in UTF8 format that I downloaded from the xml creator site of forum member "Huevos".
I suppose you could edit the xml file if preferred before loading it into the E2 receiver.

 

[Channel Hopper]

It might assist those on the border of reception if they have the correct orbital slot before searching.

 

[moonbase]

It might assist those on the border of reception if they have the correct orbital slot before searching.

It is up to others how they wish to configure their E2 receivers, if they wish to edit the satellites.xml file that is up to them.
For my personal use, I select which satellites and frequency bands I wish to be represented in the satellites.xml file and accept the contents.

I think that the satellites.xml creator tool of "Huevos" takes a regular online feed from Lyngsat or Flysat as the basis of its database.
In which case, the orbital numerical values in the satellites.xml file would be aligned with the data source unless there was any post download adjustments via a script.
"Huevos" would be the person to confirm these points.

 

[Channel Hopper]

I'm not suggesting anyone should reconfigure a receiver database when forum members update historic error.

Autotune should tweak a system anyway.

 

[moonbase]

I'm not suggesting anyone should reconfigure a receiver database when forum members update historic error.

Autotune should tweak a system anyway.

I am not sure what historic error you are referring to. The "Jens T Saetre" satellite calculations website lists Yamal 402 as located at 54.91 East, based on a TLE dated today
The OpenViX screenshots I uploaded list the satellite at 54.9 East.

Perhaps you can illustrate with some screenshots from your E2 receiver(s)?

 

[moonbase]

After a few more scans and dish adjustments to Az/El/Skew I was not able to better the signals I reported previously a few days ago.

To summarise, I have attached below the final table from my recent scans of 54.9E.
Also attached are a few of the channel pictures from the one Russian beam frequency that I locked (12265V, SR30000).

Location: Surrey, UK.

.


.

 

[Satfaca]

After a few more scans and dish adjustments to Az/El/Skew I was not able to better the signals I reported previously a few days ago.

To summarise, I have attached below the final table from my recent scans of 54.9E.
Also attached are a few of the channel pictures from the one Russian beam frequency that I locked (12265V, SR30000).

Location: Surrey, UK.


.
View attachment 142393 View attachment 142394 View attachment 142395 View attachment 142396

That would be 11.265 V. Y

 

[satesco]

A new service(promo) has appeared at this position, Abaantu, with a pretty strong signal, at least in my area.
I get it with neumoDVB.
The credit goes to Bol@nov.

 

[dreamsat]

my signal

12506 V 1000 QPSK 7/8 "Rossia 24"

 

[zorbua]

I could get the 12506 V but not the 11055H. Using 1.5 Dish.
It's Ok now I got the Freq....I had the T2MI enabled which shouldn't be.

 

[EnoSat]

test OTT UBANTU on 55E/11056H

root@sf8008:~# dvbsnoop -s pidscan | grep datagram
PID found:  201 (0x00c9)  [SECTION: DSM-CC - private data section  // DVB datagram]

root@sf8008:~# astra --analyze pipe://"dvbsnoop 201 -b"
Jul 09 17:22:47: INFO: Starting Astra SM 0.2
Jul 09 17:22:47: INFO: [pipe_input analyze] process started (pid = 7488)
Jul 09 17:22:48: INFO: PAT: tsid: 1
Jul 09 17:22:48: INFO: PAT: pid: 256 PMT pnr: 1
Jul 09 17:22:48: INFO: PAT: crc32: 0xE8F95E7D
Jul 09 17:22:48: ERROR: PMT checksum error
Jul 09 17:22:48: ERROR: PMT checksum error
Jul 09 17:22:48: INFO: Bitrate: 3781 Kbit/s
Jul 09 17:22:49: ERROR: PMT checksum error
Jul 09 17:22:49: ERROR: PMT checksum error
Jul 09 17:22:49: INFO: Bitrate: 4196 Kbit/s
Jul 09 17:22:49: ERROR: CC: PID:0=2 PID:256=2
Jul 09 17:22:50: ERROR: PMT checksum error
Jul 09 17:22:50: INFO: Bitrate: 3367 Kbit/s
Jul 09 17:22:50: ERROR: CC: PID:0=1 PID:256=1
Jul 09 17:22:51: ERROR: PMT checksum error
Jul 09 17:22:51: ERROR: PMT checksum error
Jul 09 17:22:51: INFO: Bitrate: 2887 Kbit/s
Jul 09 17:22:51: ERROR: CC: PID:0=2 PID:256=2
Jul 09 17:22:52: ERROR: PMT checksum error
Jul 09 17:22:52: INFO: Bitrate: 2763 Kbit/s
Jul 09 17:22:52: ERROR: CC: PID:0=1 PID:256=1
Jul 09 17:22:53: INFO: Bitrate: 1905 Kbit/s
^CJul 09 17:22:54: INFO: [main] shutting down

root@sf8008:~# dvbsnoop -n 1 201
dvbsnoop V1.4.56 -- [url]https://github.com/OpenVisionE2/dvbsnoop[/url]
------------------------------------------------------------
SECT-Packet: 00000001   PID: 201 (0x00c9), Length: 1360 (0x0550)
Time received: Sat 2022-07-09  17:28:26.337
------------------------------------------------------------

PID:  201 (0x00c9)

Guess table from table id...
DSM-CC DATAGRAM-decoding....
Table_ID: 62 (0x3e)  [= DSM-CC - private data section  // DVB datagram]
section_syntax_indicator: 1 (0x01)
private_indicator: 0 (0x00)
reserved_1: 3 (0x03)
Section_length: 1357 (0x054d)
MACaddrbyte/DevicdID 6: 0 (0x00)
MACaddrbyte/DeviceID 5: 0 (0x00)
reserved_2: 3 (0x03)
payload_scrambling_control: 0 (0x00)  [= unscrambled]
address_scrambling_control: 0 (0x00)  [= unscrambled]
LLC_SNAP_flag: 0 (0x00)
current_next_indicator: 1 (0x01)  [= valid now]
Section_number: 0 (0x00)
Last_Section_number: 0 (0x00)
MACaddrbyte/DeviceID 4: 0 (0x00)
MACaddrbyte/DeviceID 3: 0 (0x00)
MACaddrbyte/DeviceID 2: 0 (0x00)
MACaddrbyte/DeviceID 1: 0 (0x00) => MAC-Address/DeviceID: 00:00:00:00:00:00

IP_datagram_bytes:
    Version: 4 (0x04)
    IP header length: 5 (0x05)
    Type of service: 0 (0x00)
    Total length: 1344 (0x0540)
    Identification: 0 (0x0000)
    Reserved: 0 (0x00)
    DF: 0 (0x00)
    MF: 0 (0x00)
    Fragment offset: 0 (0x0000)
    Time to live: 128 (0x80)
    Protocol: 17 (0x11)  [= UDP]
    Header checksum: 14251 (0x37ab)
    Source address: 7f000001 [= 127.0.0.1]
    Destination address: 7f000001 [= 127.0.0.1]

    UDP_datagram:
        Source port: 9933 (0x26cd)
        Destination port: 9933 (0x26cd)
        Length: 1324 (0x052c)
        Checksum: 0 (0x0000)
        Data
              0000:  47 01 01 11 f1 12 eb 49  8e a8 19 9b 52 81 e2 3e   G......I....R..>
              0010:  83 1f 3e 9f 23 b7 9a c7  db 71 b6 2c dc 0c d0 72   ..>.#....q.,...r
              0020:  4f f0 d2 1e cf cb ae 3f  b8 90 56 81 54 35 98 7e   O......?..V.T5.~
              0030:  ae 2b cf 29 76 f3 02 46  e1 59 2b 7c 81 e0 7f 47   .+.)v..F.Y+|...G
              0040:  3a 2d d2 49 eb 2b ab 62  7d c9 e8 c7 37 ee d7 cf   :-.I.+.b}...7...
              0050:  09 00 4b f8 74 b6 7f 8a  2d c6 a2 f9 b5 e7 a2 d5   ..K.t...-.......
              0060:  06 32 3a 9c cf f5 db e3  5a 61 f6 ed 0a c8 dd 38   .2:.....Za.....8
              0070:  85 f1 2d 2e c9 28 ec 87  0f eb 8e 8c fd 0a ff 79   ..-..(.........y
              0080:  65 ea fa ed da 76 28 fe  3f 58 aa f2 76 68 b1 b3   e....v(.?X..vh..
              0090:  dc 84 be ed bf 63 ad e7  16 3a 65 0d 00 f5 bd 93   .....c...:e.....
              00a0:  11 d2 19 f9 79 7a 32 d1  cf d9 e9 5d 0c 3e 7b a0   ....yz2....].>{.
              00b0:  93 43 46 57 30 cb 45 c1  f0 62 87 b7 47 01 01 12   .CFW0.E..b..G...
              00c0:  a4 1d 13 f4 d6 47 8e 8f  a9 ab a1 5c b8 d4 6a 6c   .....G.....\..jl
              00d0:  b1 82 44 95 48 00 99 27  9f 52 df b3 3b f1 14 0f   ..D.H..'.R..;...
              00e0:  1d 6a e5 79 ac ac 98 1e  06 a4 fe d5 e9 2a 74 97   .j.y.........*t.
              00f0:  fb b7 46 25 19 a1 02 4c  e5 ef a9 5f f6 4b 3d df   ..F%...L..._.K=.
              ...
              0500:  da cd 5f e4 e4 78 d7 97  1d 62 ca e8 e0 16 f6 e3   .._..x...b......
              0510:  cd 1e 44 4e 6d 7d 6b 75  13 82 bb 4d e2 44 2d 60   ..DNm}ku...M.D-`
              0520:  11 80 fd d9                                        ....

CRC: 4282079733 (0xff3b59f5)
==========================================================

 

[Satfaca]

Feed from Kievskiy Station.

12.593 V, SR 4133, FTA, ID: RUS-026

 

[Analoguesat]

The European beam is reported back on - anyone getting it? Last time it was active 55E was an easy catch on my kit, but I'll need to rig another lnb to get it.

11105H
30000
3/4

 

[anto@]

Il raggio europeo viene segnalato - qualcuno lo riceve? L'ultima volta che è stato attivo 55E è stata una presa facile per il mio kit, ma dovrò attrezzare un altro lnb per ottenerlo.

11105H
30000
3/4

nord Italia laminas 180

 

[2night]

The European beam is reported back on - anyone getting it? Last time it was active 55E was an easy catch on my kit, but I'll need to rig another lnb to get it.

11105H
30000
3/4

11105 H 30000 3/4 DVB-S2 and
Gazprom-Media tests on 11180 H 10000 DVB -S2

both via europe beam , both transponders come in fine here in friesland (northern netherlands) with 120 cm dish
available in Central Europe with smaller dishes (approx. 60 to 80 cm).

 

[ViaHussun]

Yamal-402 @ 55.0E
TP: 12564 V 5000 8PSK 4:2:0
ID: RUS-064 M

Russian Premier League feed

Biss

 

[Satfaca]

10.976 H, SR 3320, FEC 2/3, 8PSK, FTA