The satellites.xml file is used to:
1. Provide a list of satellites that can be used by Enigma2. This includes the names and orbital positions.
2. Provide a list of transponders on each satellite that are scanned/probed.
On Manual scan and signal finder, the list of pre-defined transponders is also obtained from the xml files.
There is no need to trim the xml files, Enigma2 will filter selection based on your Tuner configuration.
Plugins like Blindscan, AutoBoquetsMaker, AutoBouquets 28.2, SatScanLCN, Terrestrail scan do NOT use these files.
There are two locations for the xml files
- /etc/tuxbox/ This is the location for official/system version and will be updated during software updates.
- /etc/enigma2/ This is for user version where you can make your own edits. If you have an xml file in here, it will have priority over the system version. It will not be updated on software updates*
NB:
Some channel list providers include an outdated version of the xml file or one from a source that uses different criteria.
They have been asked to stop attaching xml files,, but they refuse to co-operate.
The XML files are not using for tuning/activating the channels. That data is held in lamedb.
If you dont believe this, remove all the transponders for your satellite in the xml file, the name must exist then reboot. If you corrupt the satellite name, it will not be available to Enigma2. You will find all the existing channels will still work, thereby removing your misconception.
The same applies to Cables and Terrestrial xml files.
On OE-A images, the satellites, terrestrial and cable XML files are part of the Tuxbox plugin.
The data in satellites.xml file on OE-A and PLI images is from Lyngsat. OE-A images until recently used to update it every Saturday.
The repository is here: https://github.com/oe-alliance/oe-alliance-tuxbox-common
The Tuxbox plugin is rebuilt when the image line is built. It is dependent on an image build being run before it becomes available in a software update.
Vix does not have nightly builds like OpenATV. Even for ATV, some users do not update images for a long time. That means whe they scan (not using a plugin), the data is old and not all transponders are scanned/probed.
To deal with this, for many years, OpenViX has had an option for users to update the xml files from the receiver. The plugin is called XML update and is located within the scanning menu. It is pre-installed on Vix and maybe OBH.
Attached is plugin created by Huevos to install on images that do not have it, it is for Python 3 images. It has been adapted to install on all receivers by KiddaC.
Please note: There is an issue with un-installation of the ipk.
Source code is here: https://github.com/oe-alliance/oe-alliance-plugins/tree/master/xmlUpdate
Install by your usual method:
1.
Place the ipk on a USB stick.
Ensure no menus are showing on TV
Insert USB stick into receiver
You will get a prompt to install the plugin.
2.
Transfer the ipk to the /tmp/ directory using an FTP program such as Filezilla/WinSCP
Issue the following command using Telnet protocol in Putty or Terminal in OWIF
opkg install /tmp/*.ipk
Once it installs, best to restart the GUI/Enigma2.
To use the plugin, access the scanning menu.
Menu > Setup > Tuners, scanning & Reception
(May be named something slightly different depending on your image)
The plugin is called "XML update"
Select the type of file you want (satellite, cable, terrestrial)
The default and recommended location is /etc/tuxbox/
Press Green to fetch/download the file.
Enigma2 will restart as soon as it completes the download.
