TNAP-5-Test Thread

[lme]

Ok. that's all i can see:

[Only registered and activated users can see links. ]

[el bandido]

An online update should fix BackSuite in the MIO receivers. Please let me know if you find anything else wrong.

Thanks.

[Only registered and activated users can see links. ]

[sattech64]

Thanks for the info! And thanks for all the work do on this project!!

[el bandido]

Are there any more problems or issues?

Please do an online update, then check for errors. Thanks.

[Megatron817]

Are there any more problems or issues?

Please do an online update, then check for errors. Thanks.

Haven't found any. Thanks.

[lme]

Same here: none.

[maor77gt]

Greetings from El Salvador, at this moment I am going to install TNAP 5.0 in my Edision OS Mio 4k Plus, it is possible to install OSCAM 11719

[el bandido]

Greetings from El Salvador, at this moment I am going to install TNAP 5.0 in my Edision OS Mio 4k Plus, it is possible to install OSCAM 11719

Edit the /etc/issue file. Change it to openpli.

[el bandido]

Some small changes have been made in the enigma2 scan file(/lib/dvb/scan.cpp). The scanning hack for Dish/Bev has been removed. This hack was introduced some twenty years ago, and should no longer apply to us. Therefore it has been removed.

/* NA scanning hack */
switch (servicetype)
{
/* DISH/BEV servicetypes: */
case 128:
case 131: /*Sky UK OpenTV EPG channel */
case 133:
case 137:
case 144:
case 145:
case 150:
case 154:
case 163:
case 164:
case 166:
case 167:
case 168:
servicetype = 1;
break;
}

This code can be added back if needed, but I doubt anyone notices it missing. Removing it may/may not help in transponder scanning. But if we are not using it, then it shouldn't be there.

Some old blindscan code has also been removed. Years ago we had this:

* For DVB-S, you need to provide a list of 4 transponders for each orbital position:
* one for each polarity (H/V or L/R), one for each band (hi/lo).
* The frequency defines the starting frequency within the desired band.
* The symbolrate defines the frequency search range, in MHz (frequency / 1000).
* The polarity defines on which polarity the search should run.
* All remaining transponder parameters will be ignored.
* So for each orbital position, 4 blindscan iteration runs will be done, one for each polarity/band 'quadrant'.

I don't think that blindscan stuff has anything to do with us because all of our receivers today use blindscan binary located in /usr/bin.

An online update after today should include the changes. If the scan becomes problematic, then these items can be returned to the code.

The word "Test" has been removed form the code. this leaves us with TNAP 5. An extra copy of the tuner driver for osmio4k receivers is currently being put in /etc/enigma2. This issue and a couple more little things should be fixed.

[el bandido]

The previously mentioned changes to the scan file do not seem to be hurting anything so the changes will stay for now. A ku scan of 103w looked good and is shown below:

< File created on Sunday, July 16, 2023 at 14:05:56 >
< Satellite = 103.0W Ku-band T10/T12 & SES 3 >
< Receiver = edision osmio4kplus >
< Enigma2 Image = Tnap 5 >
< Kernel Version = 5.15.0 >
< DVB Driver Date = 2021-11-03 >
< Blindscan Frequency Range = 11550 to 12750 MHz >
< Blindscan Symbol Rate Range = 1 to 60 Msps >
< Blindscan Only Free Channels or Services? = False >
< Tuner = Tuner A: Availink AVL6261 (DVB-S2X) >

< 'DVB-S2 QPSK 11704V / 3650 / 3/4' > Tp# 1
< 'DVB-S 11708H / 1013 / AUTO' > Tp# 2
< 'DVB-S 11710V / 1107 / AUTO' > Tp# 3
< 'DVB-S2 8PSK 11911H / 4600 / 3/4' > Tp# 4
< 'DVB-S 11937V / 1013 / AUTO' > Tp# 5
< 'DVB-S2 8PSK 12069V / 17144 / 5/6' > Tp# 6
< 'DVB-S2 8PSK 12080H / 29971 / 5/6' > Tp# 7
< 'DVB-S2 8PSK 12120H / 29999 / 5/6' > Tp# 8
< 'DVB-S 12144V / 19999 / AUTO' > Tp# 9

A complete file of this scan is attached.

To a degree, TNAP 5 is a basic rewrite of the python files as compared to previous versions. This rewrite was needed if the image had any kind of chance for being updated in the future. A lot of plugins for skins and other items will be missing because they are not compatible with the python upgrade. New plugins and updates to the older plugins will happen over time. This includes skins. But for now, it is what it is.

Bugs or crashes may still exist in TNAP 5. The only way to fix them is for people to use the image and report the problems or issues. Right now, TNAP 5 as a whole should be a good, solid image because it has been tested as thorough as possible with the users that we have. All efforts in testing, comments and bug reports are appreciated!

This TNAP 5 thread is Closed. Any future problems or issues should be discussed or reported in the TNAP 5 release thread. Thanks to all who participated!