TNAP-5 Image Discussion

el bandido said:
The multi-satellite scan function located under Manual scan should work. Do an online update again and recheck.

Today's online update also sends the correct bootlogo and corrects the drivers being listed twice in feeds.
Click to expand...
I updated. The multi-satellite scan is working.

I notice something interesting. This occurred with new TNAP 5.1 even before today's update. If I use Positioner Setup to fine tune the dish with diseqc commands, save and exit, then if I change channels while still on the same satellite, the box crashes every time. My workaround is to exit Positioner Setup then change to an adjacent satellite. If I then move back to original satellite, the box doesn't crash.
 
cyberham said:
This just happened so I grabbed the crash log.
View attachment 18127
Click to expand...

[eServiceMP3] Gstreamer error: Could not establish connection to server. (5) from source
[eServiceMP3] Gstreamer error: Internal data stream error. (1) from source
[eServiceMP3] Gstreamer error: Stream doesn't contain enough data. (4) from typefindelement2


Can you post your channel file named lamedb? This file is located in /etc/enigma2.
Thanks.
 
el bandido said:
...Can you post your channel file named lamedb? This file is located in /etc/enigma2....
Click to expand...

Recently when changing between images, I did ftp my backed-up lamedb and other user files to the Mio+. I just didn't want to lose all my C-band scans, etc. I bet you're going to say my lamedb is corrupted in some way. I always dislike doing this since it seems this causes trouble.

I just updated my Mio+ online, then I grabbed a copy of my current lamedb (attached). I renamed it .txt just so I could transfer it.
 

Attachments

Updates are online that should solve most of the signal finder errors. These errors or complaints did not seem to bother anything, so I doubt fixing them helped. The Gstreamer error is what I find interesting. Why is a "Could not establish connection to server" error in there unless some type of ip issue is present? Anyway, do an online update and see what happens.
 
el bandido said:
...Anyway, do an online update and see what happens.
Click to expand...
Same symptom even after I updated. After exiting Positioner Setup, the display shows as attached. Note how Tuners A and C letters are not green. The Mio+ has always done this. So I must press the Up key to change channels to make the Mio+ "see" the channel even when there is only one channel scanned in such as on 129W Ku. But when I do this, the box crashes. If I press the Right or Left key to change satellites, then go back to the satellite, the box doesn't crash. This simple workaround isn't so bad at least until TNAP5.1 comes along when I won't restore user files; just create them fresh at that time maybe with exception of user bouquets which are a lot of work to re-create.

Reuters.webp
 
el bandido said:
Do you select yes and press the ok button when exiting Positioner setup?...
Click to expand...
As a matter of fact, I see that I don't. I press EXIT EXIT. If I press EXIT YES, then Tuner A is green and issue doesn't occur. If I press EXIT NO, then Tuner A is not green and problem occurs. Operator error perhaps.
 
OK
Most likely, your problems are a combination of the way you exit Positioner setup along with a lamedb file that has some corruption in it.
 
Do we know when TNAP5.1 will be available in some form? My system is working well. So I'm looking for something to do that will mess it up. I may get out my old Openbox S9 and hook it up just to see how it handles the current FTA transponders.
 
After the last online update (2024-3-24), today I was fine tuning my signals acrros the arc.
After few of this fine tuning and position saved, the box becomes sluggish: takes time to respond to the commands, even
from the main menu when trying to restart:

restart1.webprestart2.webp

..and there is the spinner, like the box is confused.
 
Last edited:
Usually the spinner means that something or something(s) are running that are using enough resources to cause problems. This is why it is sluggish. This will be hard to fix without knowing what is running that caused this. What exactly were you using to do the tuning? Positioner setup?, Signal finder? Or ???. Does the box work normal now that it is rebooted?
 
el bandido said:
Usually the spinner means that something or something(s) are running that are using enough resources to cause problems. This is why it is sluggish. This will be hard to fix without knowing what is running that caused this. What exactly were you using to do the tuning? Positioner setup?, Signal finder? Or ???. Does the box work normal now that it is rebooted?
Click to expand...

The only menu to do a fine tuning is positioner setup. After the reboot is working at normal speed, but after few tunings it's sluggish again. Do not remember having this issue before. And is not happening on other images (vix, openbh, etc) !
 
You may also fine tune a c band actuator using Signal finder. The files for Signal finder recently changed. The files for Positioner setup have not been changed for months in TNAP 5.

I just fine - tuned back to back 89w, 91w, and 105w using Autofocus in Positioner setup. The debug log shows an error in Positioner setup, but nothing that should cause the spinner to activate. You usually only see the spinner when lots of resources are being used. Seems you have something running besides Positioner setup.
 
The coding for Positioner setup needs updating. Shown below in the screencap, the red is the correct code, and the green code is what is in TNAP5. Probably the best thing to do here is to forget about updating this in TNAP 5, and focus instead on TNAP 5.1. Your spinner and lagging problem may still exist, even if this code is corrected as you may have something running. You can check and monitor what is running by opening a terminal and typing top.

Positioner-setup-diff.webp


Here is what the top command in terminal looks like with Positioner setup running Autofocus.
Screenshot from 2024-03-28 00-18-24.webp
 
Back
Top