TNAP-4.2-Test Images for Edision MIO/MIO+

el bandido

el bandido

TNAP-Images
Administrator
Test images for TNAP-.4.2 will be available soon.

TNAP 4.2 is more or less an updated version of TNAP 4.1. Some of the updates or changes are:
* Blindscan Plugin Updated to accept more lnb types
* WebIf updated
* Signal Finder updated
* Positioner Setup updated
* Satellites.xml updated
* Kernel 5.15

Some other plugins or items are to be added.
TNAP 4.2 images are tested to boot, but load any image or software at your own risk.

tnap4.2-test_20220115120202.webp


screenshot_20220115121520.webp

Issues or Problems:
GlamourAuraFHD skin crash
Blindscan
 
Last edited:
Two issues found. 1.Audio selection crashes with audio button and yellow button. 2. C-band 5150 no blind scan, says no transponders found.
 
Do an online update to take care of the audio issue.
Will need to look at the blindscan plugin and see why the 5150 lnb is not working. I am using 5750 l.o.
 
Hallo

small problem with the other skins.
when you call (for example with glamour aura skin) the second "infobar" there is a crash.
when I loaded version 4.2 I took the setting of 4.1
here the log error
 

Attachments

to try the blindscan in KA-Band
it is necessary to wait a little bit so that I can
change the specific LNB
 

Attachments

  • snow.webp
    snow.webp
    350.4 KB · Views: 6
Audio fixed but 5150 blind scan is finding Horizontal transponders as Vertical and Horizontal. No vertical transponders are found.
 
Megatron817 said:
Audio fixed but 5150 blind scan is finding Horizontal transponders as Vertical and Horizontal. No vertical transponders are found.
Click to expand...

I confirm the problem that Megatron817 discovered, Blindscan band C does not find anything (L and R) while by manual search everything is there
 

Attachments

  • bs Cband 42.webp
    bs Cband 42.webp
    40.2 KB · Views: 8
  • bs 42.webp
    bs 42.webp
    74.9 KB · Views: 9
Installed and running now on Ku only including all online updates available. I had some green screens of death but they seemed related to attempting blind scan without first scanning in at least one transponder on each satellite. Once at least one transponder was scanned in, then blind scan worked extremely well catching everything. I also had green screens when pressing the yellow or blue button but that was due to not programming those buttons first. The receiver is working well now.

Curious to learn about the "AutoBouquetsMaker" new feature.
 
stephan94 said:
Hallo

small problem with the other skins.
when you call (for example with glamour aura skin) the second "infobar" there is a crash.
when I loaded version 4.2 I took the setting of 4.1
here the log error
Click to expand...

Please Check for updates online. Second infobar works fine here.

glamour-second-infobar_20220117103253.webp
 
cyberham said:
Installed and running now on Ku only including all online updates available. I had some green screens of death but they seemed related to attempting blind scan without first scanning in at least one transponder on each satellite. Once at least one transponder was scanned in, then blind scan worked extremely well catching everything. I also had green screens when pressing the yellow or blue button but that was due to not programming those buttons first. The receiver is working well now.

Curious to learn about the "AutoBouquetsMaker" new feature.
Click to expand...

Thanks for the information.
Blindscan should not care if a channel or transponder is scanned. A green screen is nothing more than a recorded error. When the operating sees a fatal error, it records it in a log (crash log or debug log), then restarts the operating system. So usually we have no idea what happened unless the log is attached (See post #12).

TNAP colored buttons are pre-programmed. Here is the way they are setup:
Red = Positioner setup
Green = Channel list
Yellow = Audio selection
Blue = blindscan.

Pressing the yellow button would cause a crash. Online updates have fixed this issue.
Colored remote buttons may also be changed or programmed by the user.

The AutoBouquetsMaker plugin automatically makes bouquets. This plugin is designed for use in Europe. AutoBouquetsMaker contains a scanner that is currently being used in the Signal finder plugin. I will have to figure out what needs to be done in this area. Maybe keep the scanner and ditch the rest of the plugin if that is possible? AutoBouquetsMaker could be made or designed to work in North America, similar to how it works in Europe. But no one seems interested in doing the needed work.

https://github.com/oe-alliance/AutoBouquetsMaker
 
Back
Top