Huevos

I don't think you have understood. You can either:

 

1) configure the LNB as Unicable II

2) or preconfigure it.

 

1) means up to 32 tuners. and I think 4 positions (4 LNBs but the LNBs have to be configured with the controller so they understand positions)

2) means up to 32 transponders from as many LNBs as you like to any number of STBs.

 

The above is related to the Inverto LNB and controller tool.

Example is the Inverto 32 output Unicable II. Using the controller you can map each SCR to a transponder. 32 transponders total. Once save these will be remembered across power cycles. Then you can connect an unlimited number to STBs to it. They don't even need to be Unicable capable.

 

I guess you could attach 32 transmodulators to it but wouldn't it be easier to have a television set with built in DVB-S tuner or DVB-S STBs?

Maybe Lyngsat was "requested" to remove the PLS values (for the reason in the post above). In that case we should grab it otherwise or we could adjust the grabber script to insert them explicitly.

 

Regarding making bouquets, LCN, etc. I don't like them inside enigma, that would mean a pile of code for every provider, no thanks. So a plugin makes perfectly sense.

After exchanging a couple of emails the values have now returned... so no need to do anything.

It is very basic. It just reads the LCNs from the SI tables and creates a bouquet file. Enigma does the service scan.

 

Source is available on oe-alliance-plugins. I put it there today so no feedback yet. Will be in the feeds of any image that builds that git.

I made a scanner to make some sort of order out of the MIS chaos.

 

 

 

 

 

 

No, it is simply said a multiplexing mechanism to put multiple channels in a single datastream. I can only assume it has to do with transponder bandwidth saving.

Main use is to package several terrestrial multiplexes onto one satellite transponder. That way they can be unpacked and broadcast without SI tables being inserted locally. NIT table is for terrestrial. Also LCNs are present on 5W transpondrs so it would be possible to create an automatic bouquet.

 

Wouldn't it be useful if somehow the blindscan plug-in code read the frontent capabilities and auto configure the range values from that?
Granted SRs below 1000 are not plenty but in the other hand newer tuners can handle these quite easily if their driver and firmware support them, so why wouldn't blindscan reflect these capabilities too? For instance Availink reports a minimum SR of 0 (although it seems there's a firmware restriction that cuts all SRs below 1000) and now a new test driver for Silabs extends the range to 80000.
And besides blindscan is supposed to find everything, so why argue if that has to be audio and video? In that logic it shouldn't find data transponders either!


Στάλθηκε από το Redmi Note 5 Pro μου χρησιμοποιώντας Tapatalk

Sounds like a good idea, but in practice it is not. For example the sf8008 reports the tuner as 800-46000, but it was the supplier of this STB that requested the blindscan plugin range be extended to 60000.

And now we know that STB will receive as low as 285 (well below its 800 bottom limit). The tuner range is what is considered reliable operation, not what the DX guys can squeeze out of it on some transponders if they are lucky.

 

Also some receivers output SRs outside the range of the blindscan search parameters. Attached image is with the search set to 1 (1000) but it has reached below that to 874. This is what we have to contend with because the executable is closed source, and one of the reasons the Python filters are present. Others don't respect the SR limits at all so 100% rely on the Python filters.

I think the reasoning was that hardware depends on drivers.

Yes but every enigma receiver can do this without any changes to the drivers just by using astra-sm.

 

Also, for some reason this commit links T2MI to multistream capability. That is wrong. This commit should not need to touch the multistream code.

 

And the user still needs to know pid details just to be able to scan. What other scan ever requires the user to enter pid details? And even if those pid details are known by the user they are not saved in lamedb so how is it supposed to work across reboots?

 

It looks like there is something wrong with entries for 21.6E satelite.

Some of the SR's are too short.

 

The short SR's are OK, It are low symbol rates (radio stations)
symbol_rate="255000" = SR 255
symbol_rate="376000" = SR 376
symbol_rate="512000" = SR 512

 

Yes they are correct. The SR is low because there is no point wasting bandwidth having a higher SR for such a small amount of data. But such a low SR is beyond the scope of most satellites tuners as these are designed for TV transport streams so not able to filter such a narrow bandwidth.

Tell me where/how and I can add and test.

Just to avoid confusion...

<  1041.106> [eDVBResourceManager] allocate channel.. 0802:0002
<  1041.106> [eDVBResourceManager] available channel.. 080e:0002

0x0802 is the TSID to be recorded.

0x080e is the TSID of the currently playing service.

Robertooo, I have these but need to check this evening if they are still working:

 

4440:0cfdace7:1000:0001:25:0:0
BBC Two HD
p:BBC,c:0017d5,c:0317d5,c:050001,c:0917d90101,c:1217d6,c:1617d4,C:2600,f:4001

 

c00:0cfdace7:1000:0001:1:0:0
BBC RB 1
p:BBC,c:000385,c:0103b7,c:030385,c:093890101,c:160384,C:2600,f:400
 

I

 

How can that be valid?

c:0917d90101

Cached data. Field tag [lower case] c: followed by two decimal digits and four hexadecimal digits. For example c:010282 is composed of 01 decimal cache id, 0282 hexadecimal value to cache.

 

As far as I see in the DVB standard the PID number is a 16 bit integer, i.e. in the range of 0x0000-0xFFFF.

I am against offering code to individual users that will increase load on Lyngsat. My script does the download over several hours to try to avoid causing any load issues on that website. If for some reason a captcha is added to that site it will be a nightmare for everyone. People that want an individual customised xml can easily download it from satellite-xml.org. And anyway the file offered by OpenPLi and OE-Alliance is a pretty good file for the majority of uses.

 

I swap the position data before putting it in the database. That way the positions in the database will always be the same.

 

The basics of my code to pull the positions is as follows. Note there are no collisions in this list but the complete code has a workaround just in case a new satellite causes an unexpected one (unlikely due to allocations, e.g. 0.8ºW and 1.0ºW share the same page so will show as one satellite).

 

List of fixed sats:

$fixed_slots = array(
						'57.0E', '56.0E', '54.9E', '53.0E', '49.0E', '45.0E', '42.0E', '39.0E', '36.0E',  
						'31.5E', '30.5E', '28.2E', '26.0E', '25.5E', '23.5E', '21.6E', '20.0E', '19.2E', 
						'17.0E', '16.0E', '13.0E', '10.0E', '9.0E', '7.0E', '4.8E', '3.0E', '0.8W', '4.0W', 
						'5.0W', '7.0W', '8.0W', '11.0W', '12.5W', '15.0W', '18.0W', '20.0W', '22.0W', 
						'24.5W', '27.5W', '30.0W', '31.5W', '34.5W', '37.5W', '40.5W', '43.1W', '45.0W', 
						'50.0W', '53.0W', '55.5W', '58.0W'
					);

Convert the slots to positions:

function slot_2_orb_pos($slot)
{
	$orb_pos = intval(substr($slot, 0, strlen($slot)-1)*10);
	if(substr($slot, -1) === 'W')
	{
		$orb_pos *= -1;
	}
	return $orb_pos;
}

And then to check if the current position is in the fixed slots and migrate if necessary:

function check_against_fixed_orbitals($orb_pos, $orbitals)
{
	$tolerance = 3;
	foreach($orbitals as $pos)
	{
		if($orb_pos <= ($pos+$tolerance) and $orb_pos >= ($pos-$tolerance))
		{
			$orb_pos = $pos;
			break;
		}
	}
	return $orb_pos;
}

If you want the whole script I'm happy to send it but would like it kept private.

PR to "fix" currently broken version until grabber gets repaired if OpenPLi team cares to use it.

https://github.com/O...343c2ba2361018c

I think you are pretty close. -08 and -09 have a leading zero.

And your west slots are not quiet in natural order e.g. -9 should come before -8.

And by the way I convert all PLS codes and modes to gold as that is what enigma now uses internally.