TNAP-4-Test Images for Edision MIO/MIO+ - Discussion

[el bandido]

Discuss this Topic here.

Link to files: [Only registered and activated users can see links]

[voomvoom]

I notice a plugin:
sundtek control center plugin
?'s
what is it for?
how does it work?
do you need a sundtek tuner to use it?
Thanks..!!

Al

[el bandido]

The Sundtek Control Center Plugin is only useful for Sundtek usb devices. I have some of the Sundtek devices, and had this plugin installing as default for my use. This plugin should be removed from default install as no one can use it unless they have Sundtek usb devices.

[el bandido]

Video bootlogos can also be available in TNAP-4 images. A video bootlogo will play a short video that can be viewed while the receiver is booting instead of the single picture we have now. A video bootologo will take a bit more space, maybe anywhere from 2-10 MB as compared to about half a MB for a boorlogo picture. I can put up a test image with bootlogo video if someone wants to test it.

[maor77gt]

Hello El Bandido, I would like to know if this new version of TNAP has already solved the problem that arose when scanning sat with tp at less than 4Mhz, where it took the tp as repeated, for example the sat 101w SES 1.

I have an Edision Os Mio Plus 4K

Thank you very much and sorry for the English, I use google translator

[el bandido]

Yes.
Sat 101w SES 1, C band will scan correctly.
Transponder spacing is set to 2MHz in TNAP.

[el bandido]

DVB Driver Update is available online.

17037

[el bandido]

Here is a bit of information about receiver time.
TNAP-4 is based on OpenPLi.
OpenPLi images seem to favor the time being set by the satellite or terrestrial transponder (Transponder Time).
North America does not have many satellite transponders that the correct time can be gotten from as compared to Europe.

TNAP-4 will show more favor towards Internet time as compared to previous versions of TNAP. Transponder time will still be available for those that do not have the receiver connected to the internet, but the SystemTime default for TNAP-4 will be NTP (Internet).

Flashing TNAP-4 and then restoring settings, or using previous settings file(s) may change the default setting of TNAP-4 SystemTime.
The NTP sync in SystemTime has been set to 5 minutes by some users as a way to fix time sync problems or issues. The receiver code looks at transponder time, and may "dump" or reset the time under the right set of conditions. I am very reluctant to change or adjust the dvb time settings or its logic as it may cause unseen problems.

TNAP-4 will attempt to check and/or set the Internet time during boot or a restart of enigma2. These extra time checks should give a more accurate time overall, and avoid the time being reset to 1970 or some other weird time during boot, providing an internet connection is available. These extra Internet time checks are embedded in the code and are not part of the SystemTime plugin. These extra checks should not bother a receiver that is set to Transponder Time.

My suggestion for setting the time in TNAP-4 is simple: Provide the receiver with a wired or wireless internet connection, verify the timezone is correct, and make no other adjustments. The Internet time check comes when the wireless Internet should be up and working.
For systems without an internet connection: Change the SystemTime plugin setting "Sync time using" to "Transponder". Then set the receiver to boot to a channel that has the correct time, such as a Terrestrial channel or Heroes on 101w c band.

Geolocation is ran during setup to help set your time zone correctly. Geolocation Is Not supposed to be ran again after setup.

More or less, Connect the receiver to the internet, verify the timezone is correct, and forget about the receiver time. The correct default for SystemTime in TNAP-4 is shown below. If for some reason the time is not correct, A Reboot of the box should fix it. We will see...

17038


TNAP-4 time updates are not available online, and an image containing them has not been publicly uploaded. TNAP-4 test version #3 or higher will have time updates. The receiver has a decent internal clock, but it is not battery powered. Checking or setting the time every 5 minutes should not be needed.

[el bandido]

TNAP-4 also includes a program to test net speed. Most incorrect time issues in North America can probably be traced to a bad, poor, or erratic internet connection. This net speed program has been added to verify a decent. Internet connection.

17039

17040

17041

[el bandido]

Edision MIO receivers use epoch time. More information on this can be found in the link.
[Only registered and activated users can see links]

Edision MIO receivers contain a Real Time Clock (RTC). RTC information may be found in the link.
[Only registered and activated users can see links]

A forced time sync was added to enigma2 code to assist receivers without a RTC some 12 years ago.
[Only registered and activated users can see links]
17042

I think the forced time sync is what has been causing time issues for some users. My MIO always has the correct time, but it is mainly on ATSC channels, where the correct time is transmitted in the stream. My MIO+ is used for different things, but I have seen time issues with it on occasion. Most users in Europe will have the correct time in their satellite transponder streams, so this explains why there are not many time complaints from them.

North America needs a fta receiver that can keep the correct time regardless of what is happening with the receiver signal. Our options are:
(1) Connect the receiver to the Internet, and sync with Internet time.
(2) Set the receiver to boot on a channel that has correct time, and sync with the time that is in the stream.
(3) Set time manually.

One thing we do not need is forced time syncs that were mentioned earlier because the MIO receivers seem to have RTC capability.

As a test, and As an example, I left the MIO receiver on a dead channel to see how the time would react. It should be noted that this test was done After the forced time syncs had been removed from enigma2. The SystemTime plugin was set so it would not sync for days. Here are the results of this test:

A channel was selected that was dead, or without signal.
17043

Settings in SystemTime plugin were set so the time would not sync during this test.
17044

The receiver was not touched for several hours, and the receiver maintained correct time.
17045

The time was synced to check accuracy.
17046

It looks to me that the time sync amounted to about half a second. Given that the amount of time for the test was over 6 hours (6X4=24), I would guess the receiver time might be off by a second or two in a period of one day. If this is a true test, and it holds, how often would we need to sync the time?

So more or less, code introduced 12 years ago to satisfy receivers without RTC is causing time problems in North America today. At least that is the way it looks to me. The MIO receiver should not have to be synced several times a day in order to keep correct time. They are built better than that.

As to why some have time problems, and others do not, It is the way the receiver is set up, and how it is used. We will see about fixing this time issue in TNAP4 since the problem seems to be better understood.

[el bandido]

Transponder spacing has been moved to 1 MHZ in TNAP-4. Earlier versions of TNAP had 2 MHz transponder spacing. A 1 MHZ spacing will allow transponders 1 MHz apart to be scanned. This change should not be noticed by the average user, but those that have a decent dish and watch the horse racing feeds on 95w c band might appreciate it.

[el bandido]

The BackupSuite Plugin has been modified to show the image name along with the date. This addition might help determine what backup files are being loaded.

17051

[el bandido]

Autofocus in Positioner setup has been modified to check 50 positions in either direction for calibration purposes. I doubt there are many who use this feature, but it works quite well.

17052

17053

[el bandido]

The satellites .xml file has been updated.
The atsc.xml file has been cut to scan no higher than 653 MHz.
The extra plugins and skins have been added. TNAP-4-test#3C images will have these plugins with an online update. The updated satellites.xml is not available as an online update today.

More or less, TNAP-4-test#3C images are the completed version of TNAP-4 except for a few odds and ends, plus cosmetics.

[el bandido]

There was a delay in completing the bootlogos for tnap-4. In the future, bootlogos will be made before the image is created.

YouTube Plugin seems to work OK.
17073


There may be issues when installing skins due to data file or other file clashes. The skin authors are different which means this will not be easy to fix.
For skin installs, I suggest doing a full image backup first, then install whatever skin you want. Then if there is a mistake or errors, you can reload the backup, fix the error, and reinstall the skin.

In the error example shown below, the glamouraurafhd skin is to be installed, but fails because some files have already been installed by the cobaltfhd skin. Unfortunately, there is not a second chance at installing a skin. The backup image will need to be installed, cobaltfhd skin will need to be removed, then the glamouraurafhd skin can be loaded.
17074

[Megatron817]

Im going to test Kodi on Openpli 8 rc when I get a chance and see if that version is ok on the Mio.If works maybe it could be planted in to TNAP 4.It's a no go on Openvix latest. I been mostly using Satdreamgr 8 for Kodi. Now I have netflix installed and working with it but it was a big fiasco with the login.

[Megatron817]

It is no go with kodi version on openpli 8 rc. no inputstream adapted so that means no netflix or amazon but youtube should work with some api keys installed.

[stephan94]

In the error example shown below, the glamouraurafhd skin is to be installed, but fails because some files have already been installed by the cobaltfhd skin. Unfortunately, there is not a second chance at installing a skin. The backup image will need to be installed, cobaltfhd skin will need to be removed, then the glamouraurafhd skin can be loaded.
17074

Hello ,
Yes it happens when some converter or renderer or even plugins have already been installed by another skin.
But that doesn't make it impossible to install the following skin.
it suffices (for example with filezilla) to manually install the new skin, avoiding the need to install the files already present.
with this method there is no problem.

[MCelliotG]

The problem is that this skin's author finds it perfectly normal to use other people's work without permission...
He could have simply renamed the converter but hey...

[el bandido]

Here is another one:
17077

I guess I could unpack all the skins that are on the feeds, strip the converters out of them, then pre-load the converters into the image. Doing that would probably fix it, but would probably take a year to do... Or maybe add some preinstall files to some of these skins and check for clashes before loading anything.

[stephan94]

The problem isn't just with convert or renderer,
this often also happens with plugins already installed,
for example a lot of skins work with the weatherplugin,
the following skin also wants to install this one,
and that stops the whole installation procedure.
It is true that if each skin had its own converter and renderer these problems would not exist.

manual installtion is the most convenient way I find to not have all these problems.