Reply to thread

Message

<blockquote data-quote="Huevos" data-source="post: 800488" data-attributes="member: 301161">There is no such limitation. The 32 is the number of physical LNBs that can be configured. This has nothing to do with the number of orbital slots that can be accessed. Here is an example to show you what I mean. The tuner &quot;C&quot; of my Ultimo is connected to 4 LNBs (C-band circular, C-band linear, Ku-band linear, all motorised, plus 28E, static). That counts as 4 LNBs in the tuner config menu, but from 57E to 58W (my accessible arc) there are 81 orbital slots in my satellites.xml file and that tuner can access them all.Well obviously that is up to the image developers, but yes they are updated because most developers want to keep their image fresh and up-to-date.In OpenPli based images (OpenPli, OpenVIX, BlackPole, etc) there is a location for a user satellites.xml file (/ect/enigma2). When the receiver boots it checks if there is a satellites.xml in that location and if not uses the one that comes with the image. This allows the developers to keep their file up-to-date but not overwrite a user's custom file (which always takes priority if it exists).</blockquote>

[QUOTE="Huevos, post: 800488, member: 301161"] There is no such limitation. The 32 is the number of physical LNBs that can be configured. This has nothing to do with the number of orbital slots that can be accessed. Here is an example to show you what I mean. The tuner "C" of my Ultimo is connected to 4 LNBs (C-band circular, C-band linear, Ku-band linear, all motorised, plus 28E, static). That counts as 4 LNBs in the tuner config menu, but from 57E to 58W (my accessible arc) there are 81 orbital slots in my satellites.xml file and that tuner can access them all. Well obviously that is up to the image developers, but yes they are updated because most developers want to keep their image fresh and up-to-date. In OpenPli based images (OpenPli, OpenVIX, BlackPole, etc) there is a location for a user satellites.xml file (/ect/enigma2). When the receiver boots it checks if there is a satellites.xml in that location and if not uses the one that comes with the image. This allows the developers to keep their file up-to-date but not overwrite a user's custom file (which always takes priority if it exists). [/QUOTE]

Verification