Posts by abu baniaz

Every Image uses a lamedb file.

I was saying to upload your lamedb file from your receiver to this forum.

Okay, good to hear SNP work. If you change your mind and want SRP reference to be added , please supply lamedb.

I don't know whether tsimage supports SNPicons. Please upload your lamedb file and I will add the references if I can work them out. Ye those picon packages are large because they do many satellites/cable/terrestrial positions. They can be made smaller if you use a lamedb file when building them.

Install the plugin called "missing picons", run it, upload the output it creates in /tmp directory.

Also upload your lamedb file. It is in /etc/enigma2 You may need to zip it before you upload it

Plain oscam, (i.e without emu) has had the stream relay changes for German channels added from version 11735. 11743 had the UK fix added. You can therefore install plain oscam (newer than 11743) from the image's plugin server.

You will need to enable the stream relay option and list the caids in the oscam config webif page.

The control file&folder are not needed on GitHub. The build processes employed by images builds the files using the bitbake file. When the tag is defined in bb, it is also used.

Those are commits to plain oscam, not oscam-emu. I have therefore moved them from the oscam-emu thread into the plain oscam thread.

Quote from thecrazybandit

Please can you confirm what is the correct bin file for a ZGemma h9 twin . Thanks

Arm

Thread

OSCam For sf8008 and others [ boxes_Arch:arm ]

a full version with (libcrypto,libusb,pcsc,emu) ;
the version with pcsc support if not running then install libpcsclite1 on your stb before installing oscam ;
(Code, 4 lines)



List of STB's:
Octagon SF4008 4k
Octagon SF8008 4k
Octagon SF8008 Mini 4k
Octagon SX88 4k

###
Ax / Mutant HD 51 4k
Ax / Mutant HD 60 4k
Ax / Mutant HD 61 4k
Ax / Mutant HD 66 SE 4k

###
Edision OS mio 4k
Edision OS mio+ 4k
Edision Mini 4k

###
Gigablue Quad 4k
Gigablue UE 4k

###
Zgemma H7C 4k
Zgemma H7S 4k
Zgemma H9 combo 4k

###
Dreambox 900 4k
…

samur

Oct 20th 2020

Compatibility list for checking and links

Thread

OSCam-EMU Device Compatibility List and Links !!!

linuxsat-support.com/cms/attachment/204764/



As on the title we will make a compatibility list for a large number devices used.
This list will help determine which OSCam binary you need for your device or STB.


Clicking on the icon to the left of your receiver will take you to the correct oscam for your receiver.


###
We ask for everyone to get involved and help contribute in making a complete list that will help everyone find which version they need for their receivers.

…

samur

Sep 26th 2022

The FBC tuners always output a voltage on the Vu and Gigablues. You can setup a power timer to put receiver into deep standby if you want to switch off power.

No. It is not a 4K receiver.

It seems that car123 has done something better. He has attached the wires from the motorised dish to the new FBC tuner. This means that his tuner configuration does not have to be changed because the motorised dish is still connected to his tuner I.

When his installer connects the two wires from the 39e dish, tuners Q and R can be set as simple, single, 39e.

car123_ 3 dishes.png

All that you need to know is:

1. the tuner letters will change when you add the new tuner card. Set them again.

2. Make sure you do not set satellites that you cannot receive on the tuner connected to your motorised dish. I.e 39e. That way the receiver cannot use the motorised dish for it. If will use the fixed dish for 39e

Wiil be good to show this thread to your installer.

Quote from jenseneverest

Thanks that helps with those new to the boxes.

But IMO it is confusing as f*#k

VU should have kept it simple and labelled it slot 1, 2, 3.

IMO e2 also gets it wrong.....the single/double tuner slot (aka "Tuner C") should always be labelled as Q and/or R and not changeable to I and/or J if using the middle slot.

For example with my STB:

i have a twin FBC tuner in tuner slot A (but normally have disabled it within the tuner configs.)

I have nothing in tuner slot B

I have a twin tuner in tuner slot C which is in use, and those come up as tuner I and J - just as you have pictured.

Display More

Agreed about identifying the tuner slots. This is nothing new, it affected old/ original/ non-4K Ultimo and Duo 2, so you 'd think they would have learned.

Not so sure about the tuner letters. It is always incremental, just like the person who had the loose tuner card in his Zgemma. Also, what about someone using the MTSIF Terrestrial tuners? They are only two tuners. So starting slot B from "I" could confuse issues more. And even then what would happen to USB tuners? Always start at "S"?

BTW, there is no such thing as single FBC, it is always a block of 8 tuners for satellite and cable, two with physical connections. Also, It would be better to use the FBC tuner instead of the legacy satellite tuner.

I don't understand what you are asking car123

Have you received and installed the extra tuner and dish yet?

If the motorised dish cannot revive 39east, deconfigure 39e on the tuner connected to the motorised dish. That way it will only use the fixed dish, there is no need for priority setting changes. In any case, the default settings mean that the fixed dish will be used before the motorised one

When you add the second FBC tuner card, this will be the hardware.

You will then need to re-set your tuners. This can be easily done by editing the settings file, otherwise use the remote.

Please do NOT alter anything on the vbox positioner as you might mess up the saved positions.

ultimo 4k 3 sat modules.jpg

This is the current tuner hardware

ultimo 4k 2 cards fbc legacy.jpg

PLi don't make images for that receiver. Ask the image builder to rebuild the plugin and upload on their plugin server. Alternatively install ATV and get it off their server. However, ABM won't build on python 2 images now. Getting it off the newer image it won't run on older one.

Or just manually update the provider file. What are you trying to solve by newer provider file.

Which image are you on?

It is not latest. If you want latest, download the binary for your receiver and rename to match existing name. Then replace the existing 11718 one.

However, when we last tried it there were issues with it.