Eutelsat 9b italia beam

stephan94

stephan94

Member
Messages
411
Likes
571
My Satellite Setup
1.20 Channel master ( Paris)and 1200 Laminas ( Bavaria) KU and C Band
Openbox SX6 and S3 Mini, Dr HD 15, Octagon SF 4008 and Octagon SX88and SX8 HD One, TBS 6983
My Location
Bavaria and Paris
#1
I have not read it anywhere yet.
Now at 12341V at the Italia Beam there is a second MIS
the second in QPSK
with already known transmitter.

With my 1200 laminas it is from my location
pretty close to getting a lock.
Thanks to the Mio4K, it has found everything by itself and it worked out well

Eutelsat 9b italia beam_1067014 Eutelsat 9b italia beam_1067014 Eutelsat 9b italia beam_1067014
 
MCelliotG

MCelliotG

Specialist Contributor
Messages
668
Likes
856
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
#2
Don't get it confused, it's the same frequency. A new IS ID 2 was added to this MIS, Mio shows different modulation because the one is synced with the xml that has the correct parameters and the other was auto found.
Look at the result from OpenATV which does not have 12341 in the xml
Eutelsat 9b italia beam_1067016
 
stephan94

stephan94

Member
Messages
411
Likes
571
My Satellite Setup
1.20 Channel master ( Paris)and 1200 Laminas ( Bavaria) KU and C Band
Openbox SX6 and S3 Mini, Dr HD 15, Octagon SF 4008 and Octagon SX88and SX8 HD One, TBS 6983
My Location
Bavaria and Paris
#3
Yes . I mentioned frequency 12341, but I know it's the same.
I did not stop the filter "synchronize with known frequency"
That's why there is this result.
 
MCelliotG

MCelliotG

Specialist Contributor
Messages
668
Likes
856
My Satellite Setup
TBS 5925, Mut@nt HD51, EDISION OSMINI, MABO 130X144, DRAGONSAT DS3000 LED MOTOR, INVERTO BLACK ULTRA TWIN LNB
My Location
Thessaloniki, Greece
#4
Blindscan does not find the correct parameters when blindscanning MIS frequencies that are not synced. It returns auto values but these are corrected once the services are tuned and Tuner is selected as source for values in the settings. So, the muxes are not QPSK in reality, this is the auto value result. Possibly that could be fixed with having blindscan looking at the SDT tables, but that would slow down the searhing significantly.
 
Top