15 replies to this topic

[chk8210]

Dear PLi Team!

 

Many of users using Ustym 4K pro & Octagon SF8008 receiver for 25.5E QO100 (Es'hailsat 2) DATV  reception, because these boxes has low SR capability. DATV mainly use SR 333, 250, 125, 66.

For these low SR rates very important the exact frequency input with at least 2 decimal, but 3 is better. For example 10496.250 MHz instead of 10496.

Is it possible to implement this feature for nightly image or development image for testing?

It would be very helpful for DATV users.

Thank you!

 

[littlesat]

Many of users using Ustym 4K pro & Octagon SF8008 receiver for 25.5E QO100 (Es'hailsat 2) DATV  reception, because these boxes has low SR capability. DATV mainly use SR 333, 250, 125, 66.

 

Nice to here that these boxes can be used for the QO100. I'm afraid this will not be an easy change.I suggest for the special need trying it via a plugin or make changes to a tuner plugin is the best we can do. The user interface itself works with a frequency in MHz for DVB-S. I have no idea (for now) if indeed numbers at the digits could be 'send' to the tuner/drivers. But I see in the code that satellite frequencies are multiplied by 1000 in the code.

 

I suggest for a first try to look at the satfinder plugin:

 

https://github.com/O...inder/plugin.py

 

And try to make little changes to it and try if you can add the digits?

Edited by littlesat, 17 June 2023 - 13:55.

[littlesat]

Ik zie daar in oa regel 476 iets engs gebeuren wat het helaas op 'driver' nivo waarschijnlijk niet mogelijk maakt

[chk8210]

Thanks fot the answers. It means the tuner using kHz?

E.g: 10496*1000= 10496000kHz

Decimal case that is no issue I think, because 10496.250MHz will be 10496250 kHz. Should be work.

But unfortunately I'm not programmer. 

[littlesat]

But as you show later it is devided by 1000 as integer

[el bandido]

What make/model of lnb are you using to tune a frequency such as 10496250 KHz? Most fta  lnbs are at least +- 1 MHz, so you will have a drift problem even if you are able to lock a signal such as 10496.250 MHz.

You will probably have at least the same drift of +- 1 MHz with the Octagon SF8008 tuner, but I have managed to lock a symbol rate of around 300 with the SF8008.  There are some places in the code where the frequency is shown in KHz which is I think seven digits for c band and 8 digits for ku band. But it won't be a lot of help to change the frequency accuracy if the tuner and lnb are not capable of that accuracy (10496.250 MHz).
 

The link below shows an example of a ku lnb that is fairly accurate in the KHz range. You can expect to pay $1500-$2000 Euro for the proper lnb, which gives only one polarity. Then you need to purchase the feed.  You need the proper equipment to lock symbol rates below 300. Changing the Octagon SF8008 to tune in KHz probably won't help much as I doubt the S!2166D is capable of being accurate in the KHz range.

https://www.digisat....ercial-vsat-lnb

Best of Luck with this Project!
 

[littlesat]

Sounds I need to add an lnb on this position to my t90 trying to receive this
And create a patch antenne or so on 2.4 GHz for the upload

Edited by littlesat, 17 June 2023 - 15:40.

[el bandido]

LOL.

As a test, I find the satellites.xml file may be edited to add a frequency such as 10496250 kHz with a low symbol rate. Editing the satellites.xml works for me on other low symbol rate frequencies, but I doubt it helps much with overall accuracy.

[chk8210]

LOL.

As a test, I find the satellites.xml file may be edited to add a frequency such as 10496250 kHz with a low symbol rate. Editing the satellites.xml works for me on other low symbol rate frequencies, but I doubt it helps much with overall accuracy.

 

 

I will try it. Thanks!

[el bandido]

Here is my example of satellites.xml edit in the SF8008:
Band = C
Frequency = 4022.583
Polarization = Vertical (1, 0 = Horizontal)
Symbol rate = 373

 

<transponder frequency="4022583" symbol_rate="373000" polarization="1" fec_inner="4" system="1" modulation="4" />

Ku band will have another digit in the frequency. The frequency is usually listed  like this in the code I have seen and is converted to MHz at some point. So editing the satellites.xml should be the same as listing the frequency on the receiver in three decimal places.

Edited by el bandido, 17 June 2023 - 16:27.

[littlesat]

When manipulating the satellite.xml file does work then we can also adapt something in the userinterface

[Dimitrij]

When manipulating the satellite.xml file does work then we can also adapt something in the userinterface

Everything is already there enigma2-plugin-extensions-ts-sateditor

[littlesat]

Then I suggest 'parts of it' might be 'exported' to satfinder.... or another plugin so you can also directlty scan?

Edited by littlesat, 18 June 2023 - 10:06.

[Dimitrij]

Then I suggest 'parts of it' might be 'exported' to satfinder.... or another plugin so you can also directlty scan?

I don't think anyone will do it.

Simple use plugin enigma2-plugin-extensions-ts-sateditor.

[chk8210]

I modified satellites.xml. Several cases I tried.

But it seems really no effect.

Yesterday was really high power with SR35 and no lock. Even beacon more less, but stable lock. You can see below.

So I think really hardware capability is the neckpoint.

Anyway thank you for the help guys!

 

 

Attached Files

•  IMG_20230618_191327.jpg   56.09KB   0 downloads

[EnoSat]

It is similar with radios that broadcast with low SR (e.g 16 East)

 16e_rad.png   74.13KB   0 downloads