1943 replies to this topic

[jpuigs]

No.

FEC is still 9/10, a really bad one, it can't be worse.

Edited by jpuigs, 25 October 2018 - 18:27.

[WanWizard]

Ok, so it was already very squeezed then.

[twol]

On 28.2E marginal reception, this has been often discussed with no result!
Summer can be really bad, and normally between September -> March ..OK
This year, not so.... the signal can dive in 60 minutes with the new FEC settings (3/4) from 10.4 dB to nothing (and I know dB is relative but I know my receivers pretty well, and this is unusual)

[WanWizard]

Looks like an attempt to narrow the UK spot beam...

[twol]

Looks like an attempt to narrow the UK spot beam...

I am sure thats true for 28.2E ... its funny how many traditional Brit holiday places receive OK.... BBC staff on holiday (at least until Brexit!!)??
.... but 27.5W ? So often when signal is marginal it has nothing to do with the satellite (although spot beaming doesn‘t help) but other factors.

[WanWizard]

Don't mention the B-word!

 

27.5W is afaik not intended for end-user reception but for downlinks, and I assume these downlink stations have no issue with the reception, they use large dishes and better equipment.

[Huevos]

 

 

Everything seems fine by me as of now, but since Huevos is a well reliable member I have nonetheless some shivering down my spine.
 
In any case, I am receiving BBC with usual strength.
 
Sleepy

The thing is I just set up the Ultimo 4K so I don't know if it is a tuner issue. Or maybe the dish just isn't big enough.

Huevos what size dish are you using on 27.5W??

 

Fibo 90, and my 1.8m Famaval, with a slightly offset LNB.

[lacierva]

i have not noticed any change far down southern europe 57% on a 90cm motorized dish

[jpuigs]

 

 

Huevos what size dish are you using on 27.5W??

 

Fibo 90, and my 1.8m Famaval, with a slightly offset LNB.

 

 

 

And don't you have any signal with both dishes ????

 

I use a 80 cm. dish. and I receive it.

Edited by jpuigs, 26 October 2018 - 09:38.

[Huevos]

Which is why I think the problem is the FBC tuner in the Ultimo 4K.

[jpuigs]

@Huevos, did you solve it ??

 

 

Does anybody know what are these unknown Green PIDs ?

They have enough bitrate to be something interesting….

 

Attached Files

•  BBC_SB_HIDDEN.jpg   205.43KB   12 downloads

[escoces1968]

Hello,

 

I use the channel list of Vhannibal (Motor) with the plugin for autoupdate the list. My problem is that this list don´t have the lamedb modified, so I need to change it each update. 

 

It is possible to have a double lamedb?  or  

Are they a plugin to change the lamedb automaticaly?

 

Thanks in advance.

Edited by escoces1968, 12 December 2018 - 23:59.

[lacierva]

Hello,

 

I use the channel list of Vhannibal (Motor) with the plugin for autoupdate the list. My problem is that this list don´t have the lamedb modified, so I need to change it each update. 

 

It is possible to have a double lamedb?  or  

Are they a plugin to change the lamedb automaticaly?

 

Thanks in advance.

i have a vusolo2 with motor list also, i have to manually edit the lamedb each time i update list, and up to now have found no other way im afraid.

[jpuigs]

I don't use lists, I read daily flysat and kingofsat and I update what I need, but I understand it's a common problem updating those user_lamedb channels.

A plugin to solve this would be very easy, but I really don't know how to do it.

 

Lamedb is as follows:

eDVB services /4/
transponders
eeee0000:0416:0001
t 177500000:1:5:5:3:2:4:4:2:0:0:0
/
…
…
end
services
051e:00820000:3d54:013e:1:0:0
i24News HD English
p:Harmonic,c:000727,c:010728,c:030727,c:050001
.
.
.
.
end
Have a lot of bugs!

So, you need to have the user_lamedb part in a separate file, let's call it user_lamedb.

1100:0cfdace7:1000:0001:1:0:0
BBC NEWS
p:BBC,c:0001f5,c:0101f6,c:0301f5,f:4
...... 

then, a plugin would have to do:

(After updating lists.)

 

Read current lamedb

copy all data until the "end Have a lot of bugs" in another file, ===> lamedb_temp

add (append)  your user_lamedb , to lamedb_temp

add  "end Have  a lot..…" to lamedb_temp.

Delete lamedb

Rename lamedb_temp to lamedb

 

The "problem" I see is that in order to read lamedb correctly, as far as I know, enigma has to be off, so if enigma is off, how do the plugin continue working ??

Edited by jpuigs, 13 December 2018 - 20:14.

[Pr2]

Hi,

 

lamedb is read at startup and can be change later on with OpenPLi running.

 

Then you can make a call to OpenWebif to tell OpenPLi to reload lamedb and userbouquet file with a simple wget in a script or from a http request in python.

 

https://dream.reichh...or_Userbouquets

 

So there is no problem and I guess that a python expert will provide the internal function to call to perform this lamebd reload.

 

Pr2

[jpuigs]

But how do we read correct lamedb while enigma is running ?

When we want to modify it, we have to "init 4" first, otherwise some changes won't be saved then.

[Pr2]

The problem is in fact different, the lamedb and userbouquet are saved when OpenPli is turned "off" properly (init 4).

 

So if you edit your lamedb and/or userbouquet and then reboot your box, during reboot an init 4 is iniated to properly stop it, so the lamedb and userbouquet in memory are saved. That's why you lose your changes when you edit manually those files and then issue a reboot from the menu.

 

So if you write a plugin in python that modify those files if you initiated from it a reload of the lamedb and userbouquet the changed one will be in memory and you won't get any problem.

 

Now an OpenPLi expert should confirm that after a satellite scan when saving the changes (green button), they are also immediately written into the lamedb otherwise indeed if you perform a scan then run the plugin that will modify directly the lamedb your latest scan might be lost.

 

From my side I have a shell script (written in bash) associated to a Hotkey button that modify automatically my userbouquet files and I call the openwebif with a wget from the script to perform a reload and I can told you that it is working really fine (I didn't change the lamedb because I don't need to but I am sure that it will work as fine). I should try to port my script to python but I am lazy since my shell script is already doing the job very well.

Edited by Pr2, 13 December 2018 - 23:11.

[jpuigs]

Now an OpenPLi expert should confirm that after a satellite scan when saving the changes (green button), they are also immediately written into the lamedb otherwise indeed if you perform a scan then run the plugin that will modify directly the lamedb your latest scan might be lost.

 

I think that sometimes they aren't.

I've noticed sometimes that when STB has been running with no changes (no zap, no webif changes…..) lamedb is f.i. 720316 bytes.

You do an init 4, and lamedb size changes to 720390 bytes.

So, as you say, we should be 100% sure that the read lamedb is the "latest", and won't be changed.

 

I said in a previous post that we had to have personal lamedb in a separate file.

In case of BBC lamedb channels, we can get them from lamedb by doing:

 

root@ET1000:/# cat /etc/enigma2/lamedb | grep "0cfdace7" -A 2 > /etc/enigma2/user_lamedb

Edited by jpuigs, 13 December 2018 - 23:34.

[Pr2]

Indeed there is also the automatic background scan of the TP you are on that can change the lamedb, and I guess that this one is not saved until a "init 4" or a stand-by is initiated.

[Stickan]

I have problem with 27,5w and my new Vu+Ultimo 4K. Channels running fine on my DM900 with CCcam 2.3.2. Bu not on Ultimo 4K. I have tried with both CCcam and oscam, but not working. I use same channel list on both recievers. Is there anything to do?