Scan broken?

[Satsearching]

I have built a Neutrino image for DM500

It fails to scan astra 28' and usals not working.

There seems to be differences between satellites.xml and scan.conf, shouldn't the satellite names in these files be exactly the same?

For example, satellites.xml

Code: Alles auswählen

Astra 1N/2A/2B/2D/Eutelsat 28A (28.2E)

And scan.conf

Code: Alles auswählen

Astra 1N/2A/2B/2D/Eutelsat 28

Also SatName11, 18, 29 etc

[Satsearching]

It looks like certain satellite names in satellites.xml in tuxbox are too long (longer than 29 characters) so are not correctly made in scan.conf on first boot?

[Satsearching]

I believe this is the issue.

I have built again with a satellites.xml with smaller satellite name as below.

Astra 28.2E

And the tuxbox satellites.xml name for astra at 28' is below.

Astra 1N/2A/2B/2D/Eutelsat 28A (28.2E)

The tuxbox one is 38 characters long, hence in the scan.conf, it is truncated to "Astra 1N/2A/2B/2D/Eutelsat 28" causing the mismatch and failing scan!

My new build with an edited satellites.xml with shorter names now can scan astra at 28'

There are other issues with Usals, but will post about this later.....

Either longer satellite names needs allowing, or satellites.xml needs editing with shorter satellite names?

[Satsearching]

Any chance someone can fix the satellites.xml (shorter) names and commit?

[dbt]

Any chance someone can fix the satellites.xml (shorter) names and commit?

Of course. Please, can you send a complete patch?

[Satsearching]

Enclosed