TNAP-5 Image Discussion

Don't use the Magic skin. Looks like this skin needs to be deleted from the TNAP5 feeds!

Delete this line in /etc/enigma2/settings
config.skin.primary_skin=Magic/skin.xml

In telnet:
Init 4
Delete line shown above in the settings file
init 3
 
I only tried the Magic skin because on my older Sony TV, the edges are cut off. (No way to adjust it as far as I know.) That means I don't see the last digit or letter of the menu screens and can't see the descriptions of the color buttons. I'm currently using Pd1loi-HD-night skin on TNAP 4.2 since I can at least see a partial digit or letter on the menus and partial word on the color buttons. It looks like the text size is larger on Magic too, which I liked. I'll get rid of it if it's going to be a problem. Vacation starts for me so I'll be away for a couple weeks and won't try TNAP 5 until I'm back. Thank you E.B.
 
excuse me for this question which is not directly linked to TNAP 5
My MIO4k is completely blocked (after a flash that didn't work properly) on one of the four images of the multiboot (it remains at 99% and is blocked) so I can't take another image.
because I no longer have access to the menu
I knew that you can directly call up the list of the four images of the multiboot when you plug in the socket
and pressing one or more buttons on the remote control and then being able to choose an image that works, I've unfortunately forgotten how.
If someone could explain it to me, that would be great, because at the moment my edision is unusable.
 
Online updates (10-10-2023) for TNAP 5 are available in the Software update menu of the receiver. You may also update using telnet commands opkg update && opkg upgrade

More items have been removed from the enigma2 scan files which opens up the scan. Opening up the scan will allow more channels and services to be found, but at the same time, can also allow duplicate services. This needs to be tested on different satellite dish systems. Please report any duplicate channels or other problems that are seen in scanning after this update. Thanks.
 
117w C band is a very interesting satellite to blindscan. Seems there is a little bit of everything on this satellite. I made a blindscan video of 117w after the latest TNAP updates were installed. I don't see any duplicate channels or problems with the MIO 4K after installing these updates. A scan log is also attached.


 

Attachments

The Octagon SF8008 performs similar, but also slightly different than the current line of Edision 4K receivers.

As a comparison, Both the Mio 4K and the SF8008 will at times miss transponders with channels. The Mio4K(s) and the SF8008 will also find transponders that do not seem to exist.

The SF8008 blindscans noticeably slower than the Mio 4K receivers, but the SF8008 seems to be more consistent and logs more transponders both real and imagined.

So there are pluses and minuses to the Edision 4K receivers and the Octagon SF8008. Currently though, these are the best enigma2 blindscan receivers that I know about.

Attached are the blindscan results for 117w using the latest TNAP updates. Occasionally the SF8008 will duplicate a transponder with channels, but it is not enough to be aggravating. I haven't caught the Edision 4K receivers making duplicates yet.

The enigma2 debug has been altered as to what the scan shows in enigma2 debug log (terminal init 4 5 second pause, then enigma2 [/B). Transponder results are shown at the end of the scan in the log as shown blue below:
No Transponders left: 63 Transponders Scanned, 2 Transponders Unavailable, 61 Transponders in /etc/lamedb.
What that means is the SF8008 found 65 transponders, 2 transponders could not be scanned for unknown reasons, and 61 transponders had channels. IMO, That is not bad!

Attached is the scan log and enigma2 debug log for the SF8008 blindscan of 117w.
 

Attachments

The blind scan does seem better. Before, I was having trouble detecting all the transponders on 99W Ku-band. I even tried setting the position to 99.0 instead of 99.2 because some people say that the listings that have 99.2 are actually referring to the DirecTV satellite, but still couldn't get everything to show up every time on one scan.
 
Just downloaded TNAP5 to a spare slot. I have been using TNAP4.1. TNAP5 seems to be running fine.

I heard a rumour that if using a Hauppauge OTA USB receiver that TNAP5 will now display the SNR just like for satellites. But I find TNAP5 is the same as TNAP4.1 in this regard and only displays AGC value and BER. Anybody know if SNR readout is supported for OTA?
 
I downloaded the image 2023-07-17 to my PC from the TNAP5 folder. I transferred it to USB stick and loaded it from the Mio+ menus.

ADDED: I see now I can update the software via the Mio+ menus. I will do that now.

ADDED2: What do you know? SNR is working! Cool. Did I mention I was pleasantly surprised by the new TNAP5 graphic at startup? Every nerd gets to look at his anime dream each time he reboots.

I manually configured my satellites since I like to review them periodically anyway. I imported from my TNAP4.1 image my old bouquets so I didn't need to reconfigure all of them which was good. I now have TNAP5 up and running as my main image.

I like the Pluto TV feature. Lots of favourite channels are now in a bouquet which makes them easy to find and use. SNR readout on ATSC allowed me to grab 4 new UHF OTA channels. I see an improvement in the Positioner Setup function. Blind scanning is working better. Overall, I recommend anybody to update to this image.
 
Last edited:
el bandido said:
No Transponders left: 63 Transponders Scanned, 2 Transponders Unavailable, 61 Transponders in /etc/lamedb.
What that means is the SF8008 found 65 transponders, 2 transponders could not be scanned for unknown reasons, and 61 transponders had channels. IMO, That is not bad!
Click to expand...
Code: 
[eDVBFrontend0] prepare_sat System 1 Freq 3999000 Pol 1 SR 1167000 INV 0 FEC 3 orbpos 2429 system 1 modulation 1 pilot 0, rolloff 2, is_id -1, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
[eDVBFrontend0] tuning to 1751 mhz
[eDVBChannel] OURSTATE: tuning
[eDVBFrontend0] set static current limiting
[eDVBFrontend0] set sequence pos 3
[eDVBFrontend0] setVoltage 1
[eDVBFrontend0] setVoltage FE_ENABLE_HIGH_LNB_VOLTAGE 0 FE_SET_VOLTAGE 0
[eDVBFrontend0] sleep 75ms
[eDVBFrontend0] set sequence pos 3
[eDVBFrontend0] invalidate current switch params
[eDVBFrontend0] sendDiseqc: e01038f0(?)
[eDVBFrontend0] sleep 100ms
[eDVBFrontend0] sleep 70ms
[eDVBFrontend0] sendDiseqc: e01038f0(?)
[eDVBFrontend0] sleep 100ms
[eDVBFrontend0] set sequence pos 3
[eDVBFrontend0] set sequence pos 3
[eDVBFrontend0] update current switch params
[eDVBFrontend0] startTuneTimeout 20000
[eDVBFrontend0] setFrontend 1
[eDVBFrontend0] setting frontend
[eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
[eDVBFrontend0] fe event: status 8, inversion off, m_tuning 2
[eDVBFrontend0] sleep 500ms
[eDVBFrontend0] set dynamic current limiting
[eDVBFrontend0] fe event: status 10, inversion off, m_tuning 3
[eDVBChannel] OURSTATE: ok
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=17
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=0
[scan.cpp-#388] got sdt -1
[scan.cpp-#415] got pat, err -1
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=17
[scan.cpp-#388] got sdt -1
[scan.cpp-#886] Transponder Search Complete!
[scan.cpp-#1025] the current channel's ID was not corrected - not adding channel
 
Doing What through usb? What are you trying to do?

In general, there is no reason to format usb drives --unless they are not seen or recognized in the receiver.
 
EnoSat said:
Code: 
[eDVBFrontend0] prepare_sat System 1 Freq 3999000 Pol 1 SR 1167000 INV 0 FEC 3 orbpos 2429 system 1 modulation 1 pilot 0, rolloff 2, is_id -1, pls_mode 1, pls_code 0, t2mi_plp_id -1 t2mi_pid 4096
[eDVBFrontend0] tuning to 1751 mhz
[eDVBChannel] OURSTATE: tuning
[eDVBFrontend0] set static current limiting
[eDVBFrontend0] set sequence pos 3
[eDVBFrontend0] setVoltage 1
[eDVBFrontend0] setVoltage FE_ENABLE_HIGH_LNB_VOLTAGE 0 FE_SET_VOLTAGE 0
[eDVBFrontend0] sleep 75ms
[eDVBFrontend0] set sequence pos 3
[eDVBFrontend0] invalidate current switch params
[eDVBFrontend0] sendDiseqc: e01038f0(?)
[eDVBFrontend0] sleep 100ms
[eDVBFrontend0] sleep 70ms
[eDVBFrontend0] sendDiseqc: e01038f0(?)
[eDVBFrontend0] sleep 100ms
[eDVBFrontend0] set sequence pos 3
[eDVBFrontend0] set sequence pos 3
[eDVBFrontend0] update current switch params
[eDVBFrontend0] startTuneTimeout 20000
[eDVBFrontend0] setFrontend 1
[eDVBFrontend0] setting frontend
[eDVBFrontend0] fe event: status 0, inversion off, m_tuning 1
[eDVBFrontend0] fe event: status 8, inversion off, m_tuning 2
[eDVBFrontend0] sleep 500ms
[eDVBFrontend0] set dynamic current limiting
[eDVBFrontend0] fe event: status 10, inversion off, m_tuning 3
[eDVBChannel] OURSTATE: ok
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=17
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=0
[scan.cpp-#388] got sdt -1
[scan.cpp-#415] got pat, err -1
[eDVBDemux] open demux /dev/dvb/adapter0/demux0
[eDVBSectionReader] DMX_SET_FILTER pid=17
[scan.cpp-#388] got sdt -1
[scan.cpp-#886] Transponder Search Complete!
[scan.cpp-#1025] the current channel's ID was not corrected - not adding channel
Click to expand...

What are you trying to show here? A good channel not being recognized or something else? I have no clue what satellite this belongs to....

(Maybe I should look....orbpos 2429 (117.1w)
 
Last edited:
I installed TNAP5 and found (so far) that the timers don't work properly. Two days in a row I had the timer set to record a 30 minute program but only about 3-5 minutes got recorded. I rebooted to TNAP4.2 and got a good 30 minute recording on another program.
 
eelstrebor said:
I installed TNAP5 and found (so far) that the timers don't work properly. Two days in a row I had the timer set to record a 30 minute program but only about 3-5 minutes got recorded. I rebooted to TNAP4.2 and got a good 30 minute recording on another program.
Click to expand...

Should not be any changes or difference in the timer area from 4.2 to 5.0 but I guess anything is possible.

Post the timer files that you are using and we will see if your problem can be duplicated.
 
Back
Top