TNAP-5.1 Image Discussion

[el bandido]

TNAP 5.1 images are available now for supported receivers running TNAP 5. The TNAP 5.1 images are available under Flash image in the receiver menus and should be considered Test images as they are not 100% complete. The TNAP 5.1 images are considered to be stable, but may contain errors. TNAP 5.1 images will be posted in the download section of Legitfta once they are considered to be complete.

Several changes are in TNAP 5.1. Some of these changes may be noticed or not, depending on what you use the receiver for. An effort to improve the satellite scan performance has been made in enigma2 by adjusting timeout timers. IMO, some of the timers were set too long which in turn caused longer scan times due to waiting on the timeout timer.

Adjustments were made to the satellite blindscan plugin which allows signal in db to be seen before scanning a satellite. A motor start switch has also been added to keep the satellite dish motor from starting when you don't want it to. The satellite dish motor will still start automatically if needed once blindscan is started. Otherwise, you have to start the satellite motor. Either way, the satellite dish antenna needs to be aimed accurately at the satellite before blindscan starts!

A few adjustments were made to Positioner setup. Logs for Positioner setup now shows both lock and signal in db for a given position when running Auto focus. The Positioner setup is a good tool for satellite alignment, maintenance, and satellite dish antenna setup. Currently Positioner setup favors c band actuators, but efforts have been made to improve ku band as well.

TNAP 5.1 will also have miscellaneous updates from OpenPLi, and again, some of these updates may be noticed while others will not.

Overall, TNAP 5.1 will hopefully be seen as an improvement. Things like displaying signal below lock were added recently to TNAP 5 images and this feature is available to receivers or drivers that support it in TNAP 5.1. Detailed blindscan and satellite scan logs now show what the receiver saw for signal in db at the time when the transponder and or channels were logged.

Please report any problems, issues, or comments about TNAP 5.1 in this thread. Thanks to all that help and continue to support the TNAP images! EB

[Megatron817]

Thanks for the test image. Did find it crashed when scanning in the ATSC channels.

[el bandido]

The ATSC crash should be fixed. Images have been updated. Run Flash image again in receiver menus to get the fix or update.


You may notice a scan time improvement in ATSC.
18191

[el bandido]

Some attention has been given to the SF8008 Supreme and should also work on the SF8008. The file structure of the SF8008 and similar receivers such as Ustym4kpro allow for the mounting of the 4 assigned image slots with one command. It is easy to edit images when they are mounted, and the mounting is done automatically at boot if some requirements are met.

Some sort of storage greater than 2GB should be used as mounting the image slots can take some room. The storage path has to be: /media/usb in the receiver files. Make two folders in this storage path named Exactly slot4 and slot4.4. Reboot the receiver and you should find all 4 image slots mounted in the slot4 folder. The image slots will be mounted even if they don't contain an image.

Deleting the slot4 folder while the images are mounted in it will result in a fairly fatal error. Deleting the slot4 folder while the images are mounted is the same as deleting all 4 images at once!. The slot4.4 folder exists for removing the mounted images. You may delete the slot4.4 folder at anytime. The slot4 folder will be empty and nothing will be automatically mounted if the slot4.4 folder Does Not exist.

Be careful with this one!
18192

[el bandido]

A manual dish motor start has been added to the blindscan plugin. This feature was added to keep the motor from making unwanted starts. When Start Dish Motor is set to "yes", a call to move the satellite dish will be made and the signal level of the first transponder in the satellite list for the target satellite will be displayed.

The 5G repack changed many transponder frequencies in c band, which means several satellites will show no signal for the first transponder in the targeted satellite transponder list. Editing the satellites.xml file located by default in /etc/tuxbox can help solve this. A few satellites on c band currently do not have an active or full-time transponder. So some satellites in c band may show 0 for a signal ---even with editing until a full time transponder becomes available.

It will be up to the individual user to edit the satellites.xml file.

18193


89w-C band does not have a full-time transponder. This is a great satellite for feeds!
18194

[el bandido]

Show satellite Signal-Below-Lock is available on supported receivers in TNAP5.1. The Sf8008 Supreme supports showing a signal below lock with only enigma2 image modifications. The supported Edision receivers need a modified driver to show signal below lock. Modified drivers for the Edision are available in the Plugin feeds under extra. Currently there is no modification for signal below lock for the Original SF8008.

18195


The signal below lock feature needs to be enabled in the Antenna setup for each tuner.
18196

[lme]

After today's update, still missing some setting options:
18198

18199

18200
18201

..or they are some "cosmetics" settings, not critical.
And the link to openpli site regarding picon are confusing.
In every image, I use to just make a "/picon" folder, & copy all my saved picons in it.

[el bandido]

After today's update, still missing some setting options:
18198

18199

18200
18201

..or they are some "cosmetics" settings, not critical.
And the link to openpli site regarding picon are confusing.
In every image, I use to just make a "/picon" folder, & copy all my saved picons in it.

You do realize that these screenshots are OpenVix image????? So what are you asking here? You want OpenVix settings to be included in TNAP?

[lme]

You do realize that these screenshots are OpenVix image????? So what are you asking here? You want OpenVix settings to be included in TNAP?

They are in TNAP5 also !!!:

1820218203

..but they are not in 5.1 version.

[stephan94]

Hello
no problem with picons with the new version 5.1.

[Megatron817]

They are in TNAP5 also !!!:

1820218203

..but they are not in 5.1 version.

I see the setting to turn on Show picons in channel selection list by using OpenWebif under settings and Channel selection menu. That Channels selection menu is missing in the gui screens of tnap 5.1 .

[el bandido]

Press menu button 2 times in Channel Selection.
18207

[lme]

can't post anythig in Forum: C-Band Wildfeed Finds

[el bandido]

The forums are being worked on. You cannot easily attach anything right now either. Hopefully things will be straightened soon.

[lme]

Noticed 2 issues when updated tnap5 to 2024-3-24 and tnap 5.1, osmio4k+:
1) the box is sluggish when navigating through menus;
2) the versions are messing up the settings on the positioner, shifting the sat position by 17 clicks to the east.
no such issues with tnap5, 2024-3-12 update, or other image.
Any suggestions ?

[el bandido]

I do not have a working MIO+ to test. Does anyone else have the sluggish problem when navigating the menus?

Positioner locations are stored in the positioner, Not in the FTA receiver. All the enigma2 image can do is call a number such as positoon #1. The exact location of position #1 is stored in the positioner itself. So how can an image make a positioner 15 counts off when the location is stored in the positioner?

[lme]

I do not understand either: the positions # are the same in the box and the positioner.
It's strange that the same number of wrong counts (17), ocured.

I also noticed 2 different modules sizes:
TNAP5.1
avl6261.ko=68,656
wlan.ko=3,994,940

TNAP5
avl6261.ko=103,940
wlan.ko=3,995,836

[cyberham]

When saving the index for a motor position, the user is asked if you really want to save the position. You can answer yes, no or save index in the setup tuner.

[lme]

I know how the index works, but the problem is with the # of counts sent by the box to the positioner.
After using the fine tuning feature the box becames sluggish.

[el bandido]

Noticed 2 issues when updated tnap5 to 2024-3-24 and tnap 5.1, osmio4k+:
1) the box is sluggish when navigating through menus;
2) the versions are messing up the settings on the positioner, shifting the sat position by 17 clicks to the east.
no such issues with tnap5, 2024-3-12 update, or other image.
Any suggestions ?

Looks like an update is slowing the menu navigation down some. Let's see what can be done about fixing this issue.

[el bandido]

Please Flash the 0424 image that is online now and see if things work better.
Thanks

[lme]

Please Flash the 0424 image that is online now and see if things work better.
Thanks

"No updates available" message on software update menu !
what is "0424 image" ?

[el bandido]

Flash the image. Not update the image.

18243

[lme]

No improvement on my mio4k+ box: as soon i go in "signal finder" menu or any other tuner submenu, the sluggishness starts !
beside this, there are only 2 options for video output: dvi or rca only; no HDMI option, despite the fact that there are some other items listed with "controlled by HDMI" option !

1824418245

[el bandido]

The thing to do here may be to quit building the Edision receivers and let TNAP 5 be the last Edision build. My Edision MIO+ no longer works and My MIO 4K has a few issues. Anyway, we will see what needs to be done.

Thanks for testing it.

[stephan94]

On my MIO4K with TNAP 5.1 it only says DVI instead of HDMI, but that doesn't change the viewing quality on the TV.
I think it's an error of indication.
It's true that sometimes I have the impression that it goes more slowly in the different menus, but that's not always the case,
I've changed my skin and I have the impression is all OK
that this problem is no longer there ( these are just impressions )

[el bandido]

No improvement on my mio4k+ box: as soon i go in "signal finder" menu or any other tuner submenu, the sluggishness starts !
beside this, there are only 2 options for video output: dvi or rca only; no HDMI option, despite the fact that there are some other items listed with "controlled by HDMI" option !

1824418245


On my MIO4K with TNAP 5.1 it only says DVI instead of HDMI, but that doesn't change the viewing quality on the TV.
I think it's an error of indication.
It's true that sometimes I have the impression that it goes more slowly in the different menus, but that's not always the case,
I've changed my skin and I have the impression is all OK
that this problem is no longer there ( these are just impressions )

Flash the 0425 image that is available online. Thanks.

[stephan94]

the speed in the menus is now perfect, DVI is still there but it doesn't bother me.

[lme]

Can't go past "..fallback...,,," message.

18248

E2 crash:

18247

[lme]

Reflashed the last version, and during the setup I skipped the internet connection settings.
The image was installed good, and then I set the network (wlan connection).
Did the online update, and looks like the new version is installed.

[ArloG]

Interesting how diligence and persistence made it work.
Wondering. Is there a utility or command line that will layout, zero fill a partition from another running slot to prep it for a USB image flash?
Is that even a thing or is all of that done when doing a USB install? Some place a while back hinted that remnants could be left behind if the new image was smaller than the one it replaces.
Good question?

[lme]

Well, started to do some signal adjustings. As soon as I enter the "signal finder" menu , the box is slowing down to the point that is just stahls, and i have to unplug it to be able to get it back to useable situation.
See the dreadful spinner as the box struggles to respond to the comands:

1824918250
I guess is getting more sluggish as in the previous 5.1 version.

[Megatron817]

Well, started to do some signal adjustings. As soon as I enter the "signal finder" menu , the box is slowing down to the point that is just stahls, and i have to unplug it to be able to get it back to useable situation.
See the dreadful spinner as the box struggles to respond to the comands:

1824918250
I guess is getting more sluggish as in the previous 5.1 version.

Try the PLi-FullNightHD skin. I do see the sluggishness with the GlamourAuraFHD skin here as well.

[ArloG]

Would setting a swap file help? How about memory/processor usage? It is swamped?

[el bandido]

Let's see what can be done about this. Some major changes may be needed. Thanks for the feedback.

[lme]

Try the PLi-FullNightHD skin. I do see the sluggishness with the GlamourAuraFHD skin here as well.

changed the skin, but still slugginess, not so bad like on Aura, but still there. no such behavior on other pli based images.

[lme]

Would setting a swap file help? How about memory/processor usage? It is swamped?

here are pic of memory activity: mem1 is before going into "positioner setup" menu.
mem2 is after, when the sluggishness started.

18251

18252

I do not find any major changed, unless I need new glasses !

[el bandido]

Please Flash 0426. You should find some improvements. Thanks.
18253

[lme]

Installing the 0426 version went well. All online updates installed ok.
Everything was good till I enter positioner setup-fine movement. After playing with the step e & step w, the sluggishness started to show up to the point that at the "exit" command the screen goes black for few seconds before you can see where you are in the menu. This is happening with Aura skin.
Fullnight hd skin performs a bit better with shorten lagging time in between the commands.
Overall, looks that it is an improvement for osmio4k+, fullnight hd skin, at least. Aura skin is still bad.

[el bandido]

What happens when you flash the image without restoring anything?

The Positioner setup may be the problem as it is logging signal in db. This is the only thing that has changed in Positioner setup.

[el bandido]

All online updates installed ok.

The online updates may be causing it. Let me tear the feeds down and rebuild them.

[lme]

One personal issue: trying to remove softcams-ncam, I get this message suggesting how to do it witch I do not understand, due to my missing e2 knowledge.

18256

[Megatron817]

What happens when you flash the image without restoring anything?

The Positioner setup may be the problem as it is logging signal in db. This is the only thing that has changed in Positioner setup.

I think the sluggish behavior is the satfinder system plugin that gets updated when doing an online software update. The 2024-04-26 image for the Mio4k+ is fine until a software update is done. I reverted the satfinder system plugin from before the software update and all is good again here.

[lme]

I think the sluggish behavior is the satfinder system plugin that gets updated when doing an online software update. The 2024-04-26 image for the Mio4k+ is fine until a software update is done. I reverted the satfinder system plugin from before the software update and all is good again here.
Can you post it ?
thx.

[Megatron817]

extract first then replace it at usr/lib/enigma2/python/plugins/SystemPlugins and reboot.

[lme]

extract first then replace it at usr/lib/enigma2/python/plugins/SystemPlugins and reboot.

Thank you.
I guess the place for the files is: usr/lib/enigma2/python/plugins/SystemPlugins/SATFINDER.
It is working better, but is missing "service list" in signal finder menu. So I replaced your plugin.pyc with the one from my tnap5 backup.

[lme]

An issue with the "backup suite": tryied to make backups with 2 diff USB brands, of 2 diff images, and both failed.
18258

18259

18260

18261

[eastof111]

Backupsuite is letting you know that it's missing the zip file in the usr_bin directory.

[lme]

I understood that, so where is zip file ?
So, I took the chance and loaded the missing zip file from the tnap5 backup.
Now backupsuite is working.

[eastof111]

Don't have the same receiver as you, but I am guessing this file should work. If not, someone with the same receiver as you will have to upload.

Can't upload files right now, the BBS is still in repair mode....

[lme]

Thx, but I fix it: see #49.

[lme]

Any suggestions for post #42 ?

[el bandido]

In telnet, What is the output of: opkg list-installed

[lme]

In telnet, What is the output of: opkg list-installed

a bunch of lines like these:

1826218263

...and more.

[el bandido]

In telnet, the command opkg list-installed Does exactly what it says. It lists the packages that are installed, and yes, there are quite a few items in the list. The idea was to see what you had installed, but it doesn't look like that is gonna happen. Wait a bit and there will be another image which should straighten it out. If it doesn't get straightened out or fixed in the next image, then let me know and we will do something else.

[lme]

In telnet, the command opkg list-installed Does exactly what it says. It lists the packages that are installed, and yes, there are quite a few items in the list. The idea was to see what you had installed, but it doesn't look like that is gonna happen. Wait a bit and there will be another image which should straighten it out. If it doesn't get straightened out or fixed in the next image, then let me know and we will do something else.

So what should I look for in this list ?

[ArloG]

Easy. Scroll through the list of installed packages.
Find your ncam plugin. Highlight the line with your mouse. Smack <enter>.
That line appears at the bottom of the list. Scroll back to the beginning of that line.
Type in opkg -remove at the beginning of the line. Add a space so there is one between the command and the plugin name.
Scroll to the end on the line.
Smack <enter>.
There's more than one way to skin a cat, I know. But it works for me.

Remove ncam? Where's the fun in that? Unless it is set to autostart in the softcam manager, it remains dormant.

18265

[lme]

The problem is that "e2-plugins-softcams-ncam" is not on the list, but is in the remove plugins-softcams list !!!

[el bandido]

As mentioned earlier, the plugin problem should fix itself on the next update. Let me know if it doesn't and we will do something else.

[el bandido]

TNAP-5.1 images dated 0429 are online and available for Flash installation. These images should fix the rest of the issues, and appear to be solid in my tests of the MIO4K receiver. Positioner setup (Autofocus) has been checked along with satellite Blindscan, and some time was spent observing different features. No issues were found here.

Some sort of comments or feedback on the blindscan plugin would be appreciated. Signal in db has been added to the blindscan plugin for motorized dish systems to ensure the dish is aimed correctly before blindscanning a satellite. The dish motor does not move until started by the user, Unless the blindscan is started and the dish needs to move to the targeted satellite. Setting the blindscan plugin this way stops unwanted dish movement even on dual tuner systems.

About
18266

A find of 75 Transponders in a blindscan of 117w is Very Good!
18267

No problems found in Positioner setup or Autofocus.
18268

Please post any problems, comments, or issues with the 0429 image.

[el bandido]

TNAP images currently Does Not have a frequency spacing rule or requirement for transponders. Most enigma2 images require transponders with the same polarity to be spaced 2 or 4 MHZ apart.

Shown below, the MIO4K logged a transponder at 3929V and another transponder at 3930V on a blindscan of 117w. This is sort of a moot point in this case because neither transponder had channels or even a lock. But there are other transponders in the world that are spaced less than 2MHz apart that have channels or services. The Blindscan in TNAP is currently unfiltered and unregulated. Whatever is found is shown and scanned with very few exceptions. Really the only rule being it has to be a satellite transponder or at least resemble one.

18272

[lme]

Better version.
Found 1 not important issue in "signal finder": missing "service list" option, as it was in previous versions.

18273

[lme]

Just found that I can't remove softcam-ncam:

18274

also, when switching from one transponder to another, the signal jumps to the sky (45db, 26db, etc), before settling to whatever is normal:

1827518276

On a dead tp is doing the same:
18277

[el bandido]

In terminal, Enter this command: opkg remove --force-remove enigma2-plugin-softcams-ncam

REBOOT
Check installed Plugins.
Let me know if that does not work.


For the signal issue, Is Allow signal below lock turned On or Off?

Online updates should fix the signal meter shown in post#62.

[lme]

The removal went good.
The "Allow signal below lock" is off.
Well, the adding of the "service list" is slowing down the system, more then before with the dreadful spinner:

18278

[el bandido]

As a test, set "Allow signal below lock" to ON. see what effect that has on the signal level.

As another test change the skin for something simple and one that does not poll a lot. Try PLi HD night or something similar.

[lme]

With "Allow signal below lock" to ON, signal finder is showing a signal on dead tp:

18279

As for the sluggishness I replaced the 3 files in Satfinder folder with the ones from previous version, & sluggishness is gone

[el bandido]

Okay. Attach what you replaced.
I don't think there has been any updates to Satfinder in at least six months. Be interesting to see what you replaced with what we have. Thanks.

[lme]

Here it is:

18280

the only diff. is the size of 1 file: "plugin.pyc".

[el bandido]

Please use the private message system (pm) for random chatter that has nothing to do with this thread.

So Without making any other changes, installing that satfinder plugin makes your receiver run correctly, yes? What else is broken or in need of repair?

[lme]

Yes.
It looks like it is a normal run for whatever features I use, in all images, except "tnap mod" I didn't check it yet.
I will ask my friend how tnap 5.1 runs in osmiomini4k.
Can't say anything about other features (pluto, iptv, etc), I do not use.
Thank you for your work.

[eastof111]

Flashed 04-29-2024 version Supreme to slot 4.

Setup completed without any problems.

Switching channels on 101 c band (same mux) takes about 5 to 10 seconds. While staying on the same mux, switching channels are almost instant. A few minutes later, switching channels on same mux, takes 15 seconds. Nuts!

Switched to 87 ku and switched channels on same news mux and it took almost 30 seconds to tune in a channel. Switched to another channel in same mux and dropped down to 10 seconds. A few minutes later switched again and tune in was almost instant. Switched again and tune took 10 seconds.

While in 101 c band mux, went to system and selected signal finder. It took 15 seconds to display. Exited and returned a few minutes later and display was instant.

Rebooted to slot 3 (build date 02-22) where everything works well for me except with a few quirks that I avoid.

18281

[lme]

I noticed a little discrepancies on signal level between aura skin & plifullhd skin: aura shows better signal (+1-2db) over pli skin !
Here is a crush log from yesterday. Maybe EB can find any more info:

18282

[el bandido]

Where the infobar gets the db reading can be set in the MIO receivers. Look in one of the two the settings menus for this option.

Looks like the crash file comes from a python file that is different than what we are using. You will need to do an online update that will be available in a few minutes so everyone is on the same satfinder plugin.

Our satfinder contains a dvbreader that may be the heart of the problem with slowness. There are reasons WHY OpenPLi doesn't put the dvb reader in with the satfinder, but we should be able to get away with some things because the build here is only for a few receiver models.

Remember to delete any .py files before doing an online update!

[el bandido]

Flashed 04-29-2024 version Supreme to slot 4.

Setup completed without any problems.

Switching channels on 101 c band (same mux) takes about 5 to 10 seconds. While staying on the same mux, switching channels are almost instant. A few minutes later, switching channels on same mux, takes 15 seconds. Nuts!

Switched to 87 ku and switched channels on same news mux and it took almost 30 seconds to tune in a channel. Switched to another channel in same mux and dropped down to 10 seconds. A few minutes later switched again and tune in was almost instant. Switched again and tune took 10 seconds.

While in 101 c band mux, went to system and selected signal finder. It took 15 seconds to display. Exited and returned a few minutes later and display was instant.

Rebooted to slot 3 (build date 02-22) where everything works well for me except with a few quirks that I avoid.

18281



Try online update and see if things improve. Use the receiver menus or in terminal: opkg update && opkg upgrade

18283

[stephan94]

I don't have the 8008 supreme.
but with the Ustym 4K Pro (which is the twin brother of the other 8008) I've had absolutely no problems (so far).
changes between programmes are quick the signalfinder is very fast
the blindscan works well
I don't use the positioner (another receiver controls the antenna)
[Only registered and activated users can see links] ([Only registered and activated users can see links])
[Only registered and activated users can see links] ([Only registered and activated users can see links])

[el bandido]

The dvbreader.so in the satfinder plugin allows the preview of channels or services on a transponder to be seen. The dvbreader.so is an executable with permission set at 0755.

The dvbreader.so has been in TNAP satfinder for some time. I will take a guess and say that some previous attempts to fix Satfinder crashes AFTER the dvbreader.so was added has allowed the dvbreader.so to run while navigating the menus. This would explain the problems of sluggish operation in the receivers.

The Satfinder that is in the feeds now goes back probably at least a year and a half. The file size of this Satfinder is small in part because there are no efforts to fix crashes in it. You can add swap files (band aid on a bullet wound), install more memory, or whatever else you want to do. But if the dvbreader.so is allowed to run when it should not run, then you will have problems!

[lme]

"The dvbreader.so in the satfinder plugin allows the preview of channels or services on a transponder to be seen. The dvbreader.so is an executable with permission set at 0755."
..but this file had & has 326 permission !!!! Should I change it to 755 ?
the other 2 files in the folder have permission 647.

[el bandido]

Do not change any permissions!

Permissions for dvbreader.so are changed in python.

[lme]

Last 5.1 version + updates, is working normal at my end (osmio4k+).

[lme]

Are there 5.1 versions for MOD and osmiomini 4k ?

[el bandido]

5.1 version for MOD??? Sorry. I do not understand.

Edision os mio/mini 4k have the same updates you have. The same image on the feeds...etc. The Mini should load the 5.1 test image in Flash image first and then update it online.

Currently supporting in TNAP5.1:
Ustym4kPro
SF8008 & SF8008 Supreme
Edision 4K - MIO,MIO+, & Mini

(Some others are supported but not listed.)

[lme]

5.1 version for MOD??? Sorry. I do not understand.

Edision os mio/mini 4k have the same updates you have. The same image on the feeds...etc. The Mini should load the 5.1 test image in Flash image first and then update it online.

Currently supporting in TNAP5.1:
Ustym4kPro
SF8008 & SF8008 Supreme
Edision 4K - MIO,MIO+, & Mini

(Some others are supported but not listed.)

this is what I'm talking about MOD version:

18284

[el bandido]

You have a choice of 4 drivers. Two of these drivers have been modded.

[el bandido]

Online Software update is available, dated 05-03-2024.This update is an extension of previous updates to the satfinder. Execute permissions for dvbreader.so have "supposedly" been removed to allow dvbreader.so execute privileges only when reading the stream. Previous satfinder versions had dvbreader with execute privileges at boot.

[Executive]

Last 5.1 version + updates, is working normal at my end (osmio4k+).

ditto

[eastof111]

Updated the Supreme to 05-03 and the sluggishness is gone. Blind scanned various and random ku sats without any problems. :bigclap:

[cyberham]

After the latest online updates, it seems to me my blind scans are faster. For example a blind scan of 99W Ku just now took 2:07. Very quick. Part of this may be related to installing a larger (4-foot) dish so the received signals are stronger and stand out from the noise. In the past, they had been getting very slow lasting over 5 or 6 minutes just to scan some Ku sat bands only. The software is stable for me.

Having said this, the Start Dish Motor feature seems not to be working now after these updates (or earlier updates?) though the feature worked previously. For 99W Ku, when I tried it this morning even with the dish manually peaked and receiving the first transponder of 11718 H 2390 Montana PBS at 9.3 dB, the reading shown by the Start Dish Motor feature is 2.08 dB. Similar happened on 103W Ku. I normally always manually peak the dish before blind scanning anyway so this feature doesn't matter to me.

[el bandido]

The blindscan plugin starts the dish motor by tuning the first transponder for the satellite to be blindscanned in the satellites.xml list. Pretty much, this has to happen, else the satellite dish does not move. All we are doing is getting a signal reading from that first transponder in the satellites.xml and displaying it. So if the dish moves, or if the dish is commanded to move, then eventually, the signal displayed will come form the first transponder in satellites.xml.

Of course you know how to start the thing: Highlight Start Dish Motor, then use the left or right arrow keys to trigger the motor to move. Once you do that, the first transponder in the satellites.xml for the satellite to be scanned will eventually have its signal displayed. There's not much of a way around this.

Somethings to check are signal for the first transponder in signal finder, and if the dish actually did move. The dish will be commanded to move again when blindscan actually starts because the tuner is going to be commanded to tune again.

18290

18291

[cyberham]

The way you describe is how it worked a short time ago. To simplify, I motored the dish to 129W Ku. There is only one active Ku transponder that scans in on this satellite: Reuters. I deleted other programmed tps from this satellite using TS-satellites Editor. So satellites.xml has only 1 tp listed. Signal Finder shows good SNR of 11.9 dB locked for Reuters. I use Start Dish Motor and it shows 2.64 dB. I do a blind scan and results show Reuters at good SNR locked. satellites.xml and blind scan results file attached. Everything is working except the dB reading showing when Start Dish Motor is activated is not correct. It seems a display issue not a function issue.

By the way, notice the Blindscan Frequency Range is not correct as printed in the Scan Results attached. On the Blind Scan screen display the range selected is correct as 11700 / 12900. This is probably not related; just a report printing issue.


18292
18293
18294

[el bandido]

A lot of times, files are supposed to be designed a certain way or have content entered a certain way. If Not, then problems may exist!

Transponder information in satellites.xml is expected to be in a certain order. This is the order the blindscan plugin is looking for in a satellite transponder in satellites.xml:
freq, sr, pol, fec, inv, orb, sys, mod, roll, pilot, MIS, pls_mode, pls_code, t2mi
Most of the time in coding, 1 is 0 in a list. So transponder 1in satellites.xml will be coded as 0
Here is the code where blindscan puts together the transponder for starting the dish motor:
transponder = (tps[0][1] // 1000, tps[0][2] // 1000, tps[0][3], tps[0][4], 2, orb_pos, tps[0][5], tps[0][6], tps[0][8], tps[0][9], eDVBFrontendParametersSatellite.No_Stream_Id_Filte r, eDVBFrontendParametersSatellite.PLS_Gold, eDVBFrontendParametersSatellite.PLS_Default_Gold_C ode, eDVBFrontendParametersSatellite.No_T2MI_PLP_Id, eDVBFrontendParametersSatellite.T2MI_Default_Pid)

Here is a satellite transponder from the satellites.xml in TNAP-5.1:
(freq, sr, pol, fec, inv, orb, sys, mod, roll, pilot, MIS, pls_mode, pls_code, t2mi)
<transponder frequency="11718000" symbol_rate="2390000" polarization="0" fec_inner="2" system="1" modulation="2" />


Here is the same transponder from the satellites.xml that you posted:
(freq, sr, pol, fec, inv, orb, sys, mod, roll, pilot, MIS, pls_mode, pls_code, t2mi)
<transponder system="1" fec_inner="2" frequency="11718000" polarization="0" symbol_rate="2390000" modulation="2" />

The first item in the transponder is supposed to be frequency. The first item in your transponder is system. No way this is gonna work!

The Blindscan Frequency Range is recorded by what was being displayed when the blindscan started. I am going to guess you have two or more satellites using slightly different lnb settings, and you were moving between them when doing a blindscan. Fix the satellites.xml problem first and see if this issue is also fixed.

[cyberham]

The way my satellites.xml file is organized is the way the Edision created it in some previous version of TNAP.

So I did a test. I created a brand new satellite using TS-Satellites Editor in TNAP5.1. This new satellite in satellites.xml is created exactly as my file shows. Not as you describe. So there is no point my "fixing" my file since as soon as I create a new satellite then that new satellite would be organized "incorrectly" in satellites.xml per your description.

I checked backups I have of my satellites.xml from December 2023. I also checked a backup of my satellites.xml from 2022. The frequency has never been listed first in any of those backups. It seems we are saying that satellites.xml files created before TNAP5.1 are not compatible with TNAP5.1. Yet if I use TNAP5.1 now to create a new satellite, this new satellite listing in satellites.xml is created incorrectly. I'm not sure where I go from here. Perhaps I just accept I can't use the Start Dish Motor feature. Everything else is working fine so I won't worry about it.

[el bandido]

Online Flash images have been updated to 0505. These images contain a dropbear update (see link).
[Only registered and activated users can see links](software)

TNAP-5.1 images should be considered stable and usable.

18296

[el bandido]

The way my satellites.xml file is organized is the way the Edision created it in some previous version of TNAP.

So I did a test. I created a brand new satellite using TS-Satellites Editor in TNAP5.1. This new satellite in satellites.xml is created exactly as my file shows. Not as you describe. So there is no point my "fixing" my file since as soon as I create a new satellite then that new satellite would be organized "incorrectly" in satellites.xml per your description.

I checked backups I have of my satellites.xml from December 2023. I also checked a backup of my satellites.xml from 2022. The frequency has never been listed first in any of those backups. It seems we are saying that satellites.xml files created before TNAP5.1 are not compatible with TNAP5.1. Yet if I use TNAP5.1 now to create a new satellite, this new satellite listing in satellites.xml is created incorrectly. I'm not sure where I go from here. Perhaps I just accept I can't use the Start Dish Motor feature. Everything else is working fine so I won't worry about it.


Edision Does Not Create Satellites.xml Files!
The satellites.xml is a system file and is generated in the enigma2 image build. The satellites.xml file is created elsewhere, and not by enigma2 directly, but satellites.xml file is put into a normal enigma2 image build. The satellites.xml resides in /etc/tuxbox of system files.

TS Sat Editor creates satellite.xml files or modifies satellite.xml files and puts them in /etc/enigma2 of receiver files. The enigma2 image has 2 satellite.xml files when TS Sat Editor is used, and possibly when some other editors are used.

During image updates or new image installs, most users that understand how will restore settings from the previous image and think "All is Well". Most of the time All Is Well, but other times, a problem is simply reintroduced. When you restore settings, you basically restore the contents of /etc/enigma2 which would include the satellites.xml file if one is present.

Enigma2 is set to use satellites.xml file and some other .xml files if they reside in enigma2. So if you have a satellite.xml file in /etc/enigma2, then it is used and the system satellites.xml file which is in /etc/tuxbox is ignored.

It is a good idea to Not Restore Settings at some points in time and make a Fresh Install. Most of the time when this is suggested, it is ignored because restoring settings is easy-painless. A fresh install takes a bit of work.

Attached are satellite.xml files taken from the feeds of TNAP 4.2, TNAP5, and TNAP5.1. You will note all of these satellites.xml files have a dated header at the top and are designed the same way as previously listed. A satellites.xml file that was generated using TS Sat Editor Today is also included, and it too is generated in the same format and is readable by the blindscan plugin.

This tidbit at the top means something and should not be deleted like it is in your satellite.xml files: <?xml version="1.0" encoding="UTF-8"?>

Where or how you got your satellites.xml and how or why it is in that condition is debatable. At the end of the day though, it does not matter. Either remove it from /etc/enigma2 and start proper by using TS Sat Editor to copy the real satellites.xml file in /etc/tuxbox or forget about it and be happy with what you have. Most likely, this won't be the last conversation about it because the blindscan plugin has been modified, and errors in satellites.xml will be obvious..

[cyberham]

Something occurred to me after sleeping on it. Maybe I am configuring my system incorrectly.

I have a total of 5 LNBs configured:
Tuner A: LNB1, LNB2, LNB3
Tuner B: LNB1, LNB2

I've always wondered if I should be configuring these instead as follows:
Tuner A: LNB1, LNB2, LNB3
Tuner B: LNB4, LNB5

Also, Tuner B/LNB2 is funky since it's a Shaw Direct LNB. Its LO frequency is 10075 MHz with a scan range of 11025 to 12225 MHz. It's designed to cover lower Ku and upper Ku. Maybe this and the above configurations are causing problems. I will reprogram using unique LNB numbers for the whole system.

I understand your point about carrying forward old files. In general in past, I haven't done this for the concern you mention. However, in transitioning from TNAP5 to TNAP5.1, I did carry forward using the "lazy way". I think for the transition from TNAP4.2 to TNAP5, I didn't carry forward but allowed the system to create new files.

I understand more. I will go away and probably reflash fresh and reconfigure. It's all fun & games.

[Megatron817]

TS-satellites editor changes the format and removes the top header about the xml version and encoding. I noticed this years back when I got in to enigma2. Might be better to use Notepad++ for editing and not TS-satellites editor if it matters as far as the blind scan plugins goes. I haven't had any problems that I know about having My Sat xml in the wrong format but I have fixed my sat xml file to the tnap 5.1 version and edited with notepad++ to keep this format.

[el bandido]

It's all fun & games.

It's a Hobby! So nothing should be a big deal. For your system, each individual lnb should be assigned its own number. Other than that, whatever works, use it.

To straighten out the satellites.xml thingy, simply Delete satellites.xml in /etc/enigma2 and Reboot. Nothing else needs to be done, but you may lose channels on some satellites due to satellite names being different. The TS Sat Editor may be used.

When updating,
Channel files and Bouquets can usually be carried forward without issues, though some may not work due to satellite name changes.
Any nims settings in the settings file of /etc/enigma2/settings may be copied and reused.
Almost everything else in the /etc/enigma2 folder should be dumped. OR Notes should be made if anything else is kept.

As it is now, Many satellites, especially C band will display no signal in the blindscan plugin because the first transponder in satellites.xml will not have a signal. It will be up to the individual user to fix this because no one is maintaining the TNAP satellites.xml file besides Lyngsat.

[el bandido]

TS Sat Editor appears to make a decent satellites.xml file. The header is proper as shown below. This should run without errors, but I have not tested it.

18299

[cyberham]

I'm on it! Nobody could pay me to have this much fun. Hope somebody is paying you. I'm going to fix things first on satellites.xml then update to the 0505 online version after.

[Megatron817]

TS Sat Editor appears to make a decent satellites.xml file. The header is proper as shown below. This should run without errors, but I have not tested it.

18299

If you use the TS-Satellite editor to make updates and save then the format is changed. Never had an issue with that format though.

[el bandido]

If that be True, then the TS Sat Editor needs to be modified to work correctly or removed from feeds.

Some parts of the system work fine as long as the satellites.xml is configured in a way that can be read. Signal finder is a good example. I don't know what it would take to make the blindscan plugin perform like the signal finder for showing a signal. Showing a signal for a transponder or showing Lock in the blindscan plugin has always been problematic. At the end of the day, it may simply be removed and forgotten about.

[Megatron817]

I added the 102.9w dummy satellite to the TNAP5.1 Satellites xml file so the 103w ku-band Radio channels can be setup in the tuner setup menu.
I did a fresh install and seen the radio channels were their in TNAP 5.1 but could not be setup.

[ArloG]

Don't know anything about TS Sat Editor. Nor ever found a reason to need it.
I have my master satellites.xml tucked away along with incremental updates. As well as offloaded backup images on my pc.
On a new image flash it is always used to replace the one included in it. Just an easy drag with Filezilla.
It is trimmed with all of the sats that I'll never be able to 'see'.
And when scrolling through the list for tuner setup, scanning, etc. Works out much more easy. For me.

Not really sure what magic the editor does. But every blindscan for transponders where the results are in /tmp gets compared with the corresponding satellite in satellites.xml.
A few minutes of editing to append the /tuxbox file and I'm good to go.
Even due to differences in the specified satellite tp's in the /tuxbox file , if one is given as 4040 H 30000 and the scan results in 4038 H 29998. I overwrite it.
I guess differences in LNB LO freq. drift, etc. causes that.

When I was pissin' around with old DN, Direc LNBF's which have different LO freq's. Including the "special" LNBF for 118W. That's where doing a little math to figure out why my scans were coming up with transponders that just didn't make sense. Hah. I learned! Eventually.

One thing for sure. Just a single space off in your satellite.xml can cause the next boot to corrupt your entire tuner setup, channel lists. Boot errors letting you know your .xml is borked.
So a flashable image backup is mandatory. And being able to manipulate the file structure through terminal and your FTP application.

I know, I know. "Don't ever change your satellites.xml file". Before someone barks at me. Apparently that seems like what TS Sat Editor is doing, or let's you do. Right!

[el bandido]

I added the 102.9w dummy satellite to the TNAP5.1 Satellites xml file so the 103w ku-band Radio channels can be setup in the tuner setup menu.
I did a fresh install and seen the radio channels were their in TNAP 5.1 but could not be setup.

Every satellite needs a transponder. Try adding or copying a transponder and install it in your new location. REBOOT.

Also, the satellites.xml for TNAP5.1 is unfinished. There are active satellites missing because Lyngsat thinks they are no longer being used!

[Megatron817]

Every satellite needs a transponder. Try adding or copying a transponder and install it in your new location. REBOOT.

Also, the satellites.xml for TNAP5.1 is unfinished. There are active satellites missing because Lyngsat thinks they are no longer being used!

I added the transponder for the dummy sat 102w . file from previous post has been replaced. Thanks.

[el bandido]

My information from earlier was Wrong! The TS Sat Editor provides a format that works, even though the order is wrong, or at least not consistent with the satellites.xml format used in the image. Seems another file straightens things out and allows it to work, so the TS Sat Editor will work "As Is" and will supply signal to the blindscan plugin if a signal exists.

Some updates were done to the Blindscan plugin, including fixing the wrong frequency being displayed when an User defined lnb is being used. Other adjustments were made that might allow the transponder signal to be read more easily. Pretty much, the features in TNAP should work for everyone equally. Be sure to say something if there are more problems getting a satellite to show signal in the Blindscan plugin when using motorized systems.

Updates to satellites.xml were done and allow the Muzak channels to play.

18302

[lme]

"This tidbit at the top means something and should not be deleted like it is in your satellite.xml files: <?xml version="1.0" encoding="UTF-8"?>"
My satellites file, shows a different encoding:

18304

Is it important to be UTF-8 ?
I use "Syntext Serna Free 4.4" program, to edit/modify my satellites.xml file.
Thx.

[el bandido]

I do not know why the encoding is up there, or what happens if a different encoding is used, or if No encoding is used. As long as everything runs OK, then do not worry about it. But if you have problems, try to remember the satellites.xml is not set the same as the build.

[cyberham]

...Be sure to say something if there are more problems getting a satellite to show signal in the Blindscan plugin when using motorized systems....

...Updates to satellites.xml were done and allow the Muzak channels to play.
I installed the "correct" satellites.xml provided above by Megatron817. I then flashed using the new 0505 online software. It seems when I used TS-Satellites Editor that the satellites.xml format went back to the "incorrect" format. So I decided not to worry about it. I use this editor frequently since it is convenient for quickly adding satellites and transponders and I'm familiar with it. But I notice the Start Dish Motor still doesn't work. It's only a curiosity. I don't need to use it really.

Mood Music works fine on 103W. But the Mood Music tp has also been on 101W in parallel for some time. We should be preparing to shift to 101W from 103W for this feature since we know the life of 103W is limited. How would we do that?

[el bandido]

I installed the "correct" satellites.xml provided above by Megatron817. I then flashed using the new 0505 online software. It seems when I used TS-Satellites Editor that the satellites.xml format went back to the "incorrect" format. So I decided not to worry about it. I use this editor frequently since it is convenient for quickly adding satellites and transponders and I'm familiar with it. But I notice the Start Dish Motor still doesn't work. It's only a curiosity. I don't need to use it really.

Mood Music works fine on 103W. But the Mood Music tp has also been on 101W in parallel for some time. We should be preparing to shift to 101W from 103W for this feature since we know the life of 103W is limited. How would we do that?

Start Dish Motor still doesn't work? The dish does not Move???

Please read Again post#106 of this thread. The TS Sat Editor itself Is Not the problem and may be used. My apologies for supplying the wrong information, but it appeared to be correct at the time!

There is an online update for blindscan (Menu--->Setup--->Software update). Install the update, Reboot the receiver. See if the Start Dish Motor still doesn't work. If there is a problem, then it needs to be fixed!

Moving the music channels is no big deal. They can be moved to 101w if you KNOW that is the new permanent location. This is not a hard thing to do.

[eastof111]

I do not know why the encoding is up there, or what happens if a different encoding is used, or if No encoding is used. As long as everything runs OK, then do not worry about it. But if you have problems, try to remember the satellites.xml is not set the same as the build.

Slightly off topic....
I've been using the Vix supported site [Only registered and activated users can see links] for many years to create satellite,xml files. It provides both UTF-8 and iso8859-1 formats. Guessing the encoding header is for stb and dvb cards, there doesn't appear to be an explanation of difference in formats. See comparative xmls.

18305 18306

There is also a good lamedb to satellite.xml converter tool one can use to compare a lamedb file to a satellite.xml file for missing items.

[ArloG]

Header from my satellites.xml:

<?xml version="1.0" encoding="utf-8"?>
<!-- Created by E-Channelizer on 17 Feb, 2024 at 12:23 - [Only registered and activated users can see links] -->

Header from a blindscan:

<?xml version="1.0" encoding="iso-8859-1"?>

No issues at all copying lines from a blindscan to your satellites.xml as long as indents line up perfectly.

[cyberham]

Start Dish Motor still doesn't work? The dish does not Move???...

...Moving the music channels is no big deal. They can be moved to 101w if you KNOW that is the new permanent location. This is not a hard thing to do.
Using Start Dish Motor, the dish definitely moves correctly. And blind scan works fine. Faster than ever actually. The only issue is the wrong dB reading in the Blind Scan screen that is displayed. Even if there is only one frequency listed for a satellite (e.g. 129W Reuters) then the displayed dB shows incorrectly. In this example, 2.67 dB displays when the actual SNR is 11.6 dB.

18308

For the Mood Music, if it's easy to change, then we can just wait until they aren't on 103W anymore.

[el bandido]

Interesting..... I wonder Why I get a similar signal on 129w. No Reuters for me!
18309

Like I said earlier, When you start the dish motor, the first transponder is tuned in the satellites.xml. There is not much of a way around this. If the signal is not working on one satellite, then it would reason other satellites have issues. So what other satellite besides 129w ku has a signal issue?

All transponders on 129 are very low signal for me. I do get "BEAM_SES15WB_W01_0029" which tells me I am on the satellite.

Scan Report

< File created on Tuesday, May 07, 2024 at 02:37:06 >
< Satellite = 129.0W Ku-band SES 15 >
< Receiver = SF8008-Supreme >
< Enigma2 Image = Tnap 5.1 >
< Kernel Version = 4.4.35 >
< DVB Driver Date = 2024-01-04 >
< Blindscan Frequency Range = 10700 to 12750 MHz >
< Blindscan Symbol Rate Range = 1 to 60 Msps >
< Blindscan Only Free Channels or Services? = False >
< Tuner = Tuner B: AVL62X1 (DVB-S2) >


< 'DVB-S2 QPSK 10772H / 52542 / AUTO' > Tp# 1
< Transponder SNR =['2.77db'-Locked], LNB Power = 66.98 >
< Tue, 07 May 2024 02:37:15 />

< 'DVB-S2 QPSK 10887H / 52542 / AUTO' > Tp# 2
< Transponder SNR =['2.9db'-Locked], LNB Power = 72.48 >
< Tue, 07 May 2024 02:37:23 />

< 'DVB-S2 QPSK 11056V / 34284 / 1/2' > Tp# 3
< Transponder SNR =['1.28db'-Locked], LNB Power = 66.06 >
< Tue, 07 May 2024 02:37:30 />

< 'DVB-S2 32APSK 11056H / 30002 / 3/4' > Tp# 4
< Transponder SNR =['3.45db'-UnLocked], LNB Power = 67.89 >
< Tue, 07 May 2024 02:37:34 />

< 'DVB-S2 QPSK 11113H / 52093 / 1/2' > Tp# 5
< Transponder SNR =['3.2db'-Locked], LNB Power = 71.56 >
< Tue, 07 May 2024 02:37:42 />

< 'DVB-S2 QPSK 11228H / 52093 / AUTO' > Tp# 6
< Transponder SNR =['4.79db'-Locked], LNB Power = 83.49 >
< Tue, 07 May 2024 02:37:49 />

< 'DVB-S2 QPSK 11574V / 24998 / AUTO' > Tp# 7
< [1] BEAM_SES15WB_W01_0029 --- UnKnown Service Type E: 1:0:E:1E:1D:1:906AD36:0:0:0: SNR = 3.52 />
< [2] NoName 1:0:0:1:1D:1:906AD36:0:0:0: SNR = 3.52 />
< Transponder SNR =['3.52db'-Locked], LNB Power = 67.89 >
< Tue, 07 May 2024 02:37:53 />

< 'DVB-S2 QPSK 11574H / 34283 / 1/2' > Tp# 8
< Transponder SNR =['2.43db'-Locked], LNB Power = 77.99 >
< Tue, 07 May 2024 02:37:56 />

< 'DVB-S2 QPSK 11810V / 12000 / 1/2' > Tp# 9
< Transponder SNR =['655.22db'-UnLocked], LNB Power = 66.06 >
< Tue, 07 May 2024 02:38:04 />

< 'DVB-S2 QPSK 11846V / 5811 / 1/2' > Tp# 10
< Transponder SNR =['0.26db'-UnLocked], LNB Power = 58.72 >
< Tue, 07 May 2024 02:38:22 />

< 'DVB-S2 QPSK 11861V / 1400 / 8/9' > Tp# 11
< Transponder SNR =['0.97db'-UnLocked], LNB Power = 51.38 >
< Tue, 07 May 2024 02:38:41 />

< 'DVB-S2 32APSK 11978V / 7500 / 3/4' > Tp# 12
< Transponder SNR =['0.88db'-UnLocked], LNB Power = 59.64 >
< Tue, 07 May 2024 02:38:59 />

< 'DVB-S2 QPSK 12003V / 8274 / AUTO' > Tp# 13
< Transponder SNR =['1.3db'-UnLocked], LNB Power = 63.31 >
< Tue, 07 May 2024 02:39:18 />

< 'DVB-S2 32APSK 12014V / 2272 / 3/4' > Tp# 14
< Transponder SNR =['2.66db'-UnLocked], LNB Power = 56.88 >
< Tue, 07 May 2024 02:39:36 />

< 'DVB-S2 QPSK 12022V / 4125 / AUTO' > Tp# 15
< Transponder SNR =['654.71db'-UnLocked], LNB Power = 59.64 >
< Tue, 07 May 2024 02:39:55 />

< 'DVB-S2 32APSK 12104V / 16728 / 3/4' > Tp# 16
< Transponder SNR =['0.37db'-UnLocked], LNB Power = 64.22 >
< Tue, 07 May 2024 02:40:03 />

< 'DVB-S2 8PSK 12122H / 17001 / 3/5' > Tp# 17
< Transponder SNR =['1.38db'-UnLocked], LNB Power = 64.22 >
< Tue, 07 May 2024 02:40:12 />

< 'DVB-S2 32APSK 12136V / 16726 / 3/4' > Tp# 18
< Transponder SNR =['1.38db'-UnLocked], LNB Power = 64.22 >
< Tue, 07 May 2024 02:40:20 /> <

Blind Scan Time = 5 Min. 26 Sec.
2 Channels ( TV = 2 Radio = 0) 18 of 18 Transponders Scanned.

[cyberham]

Interesting..... I wonder Why I get a similar signal on 129w. No Reuters for me!

Like I said earlier, When you start the dish motor, the first transponder is tuned in the satellites.xml. There is not much of a way around this. If the signal is not working on one satellite, then it would reason other satellites have issues. So what other satellite besides 129w ku has a signal issue?

All transponders on 129 are very low signal for me. I do get "BEAM_SES15WB_W01_0029" which tells me I am on the satellite.
129W was just a simple example since I only blind scan in one transponder. And it is always strong. Here on the west coast 129W upper Ku is almost empty. Every satellite shows 2.67 dB when I use the Start Dish Motor feature. There was a time in the recent past when you first described this feature that it worked correctly on my receiver including the correct blind scan screen dB reading. What changed?

18310

[el bandido]

Dunno what changed. Lets find out.
Take one of your other image slots in the receiver and load the TNAP 5.1 image in the feed (Menu--->Setup--->Flash image) Do Not restore anything at all. After the image installs, do an online update. Then setup a couple or three satellites and see how things work.

These features such as motor start and showing signal in the blindscan plugin should work equal for everyone, provided the image is set correctly. The signal in the blindscan plugin works exactly as it should across both tuners in my system.

You are the only one that has showed any interest in this feature, so either you are the only one that blindscans with a motorized dish or no one else cares about it. The best solution may be to put the TNAP 5 blindscan plugin back in the 5.1 image and forget about it.

[ArloG]

Isn't 129W ku a DN DSS sat? And if so is should be circular polarization?
I could be wrong.

[cyberham]

Isn't 129W ku a DN DSS sat? And if so is should be circular polarization?
I could be wrong.
You're thinking of the old 129W. Now 129W SES15 has one linear Reuters transponder. See here ([Only registered and activated users can see links]).

[cyberham]

Dunno what changed. Lets find out. ...
I loaded the current TNAP5.1 image fresh. Tested. Problem still there. I then started stepping back in time loading each image fresh. 0427: bad. 0412: Good! The feature works if I load 0412 with no updates. Then I online updated 0412: Bad.

[ArloG]

So what's wrong with just parking your dish on the sat that you wish to scan and doing it? That's how I've always done it.
Just like the dish aim tweaker plugin. I found that if you use it and it bumps the dish back and forth searching for the strongest signal.
It can screw up the rest of the reference counts for the rest of your stored positions. Having you going through and manually peaking signals and storing the new position.
Or just going into the dish controller and resetting the zero reference.
I'm all for sending the goto command and letting the dish stop. And then scanning. Crazy, ain't it!
"evly machine a-have it rimitation"

[cyberham]

I loaded the current TNAP5.1 image fresh. Tested. Problem still there. I then started stepping back in time loading each image fresh. 0427: bad. 0412: Good! The feature works if I load 0412 with no updates. Then I online updated 0412: Bad.
I'll let you figure out why but here's the news. The Start Dish Motor feature is now working completely on the latest image (0505) including displaying the correct dB level in the Blind Scan window. Not related to solving this, I reconfigured my whole system to put the motor on Tuner B and a fixed dish on Tuner A. This is probably temporary since Tuner A is superior and I'll likely change the motor back to Tuner A later. Perhaps because of this, or because I flashed an older image (0412) that allowed the feature to work, I now have it working even on the latest image.

I'm getting to like this feature. Now...if we could have some way to select a list of satellites in advance to blind scan then we could walk away and come back later to all the blind scan results.

[el bandido]

So what's wrong with just parking your dish on the sat that you wish to scan and doing it? That's how I've always done it.
Just like the dish aim tweaker plugin. I found that if you use it and it bumps the dish back and forth searching for the strongest signal.
It can screw up the rest of the reference counts for the rest of your stored positions. Having you going through and manually peaking signals and storing the new position.
Or just going into the dish controller and resetting the zero reference.
I'm all for sending the goto command and letting the dish stop. And then scanning. Crazy, ain't it!
"evly machine a-have it rimitation"

TNAP and most other images are designed for Motorized Satellite Systems that are not broken or need of repair.
Fix your dish system and you will not have these problems!

Now I gotta ask:
Why are you even bothering to post in this thread? You have berated about the TNAP image not living up to your personal expectations and have berated other images because the channel guide does not equal what a pay satellite receiver has. So why post in this thread? You don't use the TNAP image, you don't like the TNAP image ...etc. Are you bored or just Trolling?

[el bandido]

More efforts to improve blindscan signal. Online Software Update for Edision.

18311

[cyberham]

I'll let you figure out why but here's the news...
A little more news. I reversed my programming: motor is back on Tuner A and fixed dish is on Tuner B. Problem has returned.

ADDED: Just did the online updates. Problem gone. Conincidence?

[el bandido]

A little more news. I reversed my programming: motor is back on Tuner A and fixed dish is on Tuner B. Problem has returned.

Per Post#123,
Did you Notice there is an online update??? Menu--->Setup--->Software update. See if that fixes it. Thanks for your efforts!

[cyberham]

Per Post#123,
Did you Notice there is an online update??? Menu--->Setup--->Software update. See if that fixes it. Thanks for your efforts!
Yes. I installed and issue is resolved.

[el bandido]

Yes. I installed and issue is resolved.

There is One issue left.
Octagon SF8008 has only one signal to deal with. Edision has three. Signal levels for Edision are different in T2MI and Non-T2MI drivers. What about Tuner 2 in the Edision MIO+? What does it show?

With the last Blindscan update installed, Can you set up tuner 2 as a motorized dish for about 3 satellites and tell me what the signal shows as compared to what it should be when the dish motor starts. If we can get the signal values for tuner 2 we can calibrate it.

Thanks.

[cyberham]

...If we can get the signal values for tuner 2 we can calibrate it....
With Tuner B configured with the motor, the Start Dish Motor function moves the dish correctly but there are no readings.
129W: Blind Scan screen shows 0 dB. Should be 12.0 dB.
123W: Blind Scan screen shows 0 dB. Should be 12.0 dB.
117W: Blind Scan screen shows 0 dB. Should be 10.4 dB.

[el bandido]

Now we meed the values being outputted. and do the following:

Go to signal finder and tune the first transponder 117w. Note the signal value.
Telnet to the receiver
cd /usr/lib/enigma2/python
enter this command to see what the blindscan plugin thinks the transponder signal values are.
python Dvbcsvb.py
Copy what the above command outputs. and then also copy what the value for the transponder is in signal finder.

If we have what the blindscan thinks the signal is compared to what the signal really is, then we can make a somewhat usable value to be outputted in blindscan plugin.

You may repeat this for the other 2 satellites.

[cyberham]

Copy what the above command outputs. and then also copy what the value for the transponder is in signal finder....

117W:
BitError 0; Status 31; SNR 458.74; Strength 41942
Signal Finder: 10.5 dB

123W:
BitError 0; Status 31; SNR 439.08; Strength 39976
Signal Finder: 10.2 dB

129W:
BitError 0; Status 31; SNR 537.38; Strength 44563
Signal Finder: 12.4 dB

[cyberham]

I notice Media Player no longer works. If I click it in the Menu, the spinning wheel starts and the box is completely locked. I must remove DC plug on rear panel to restart the box. I've tried this twice.

[el bandido]

Media Player works on SF8008. I will see about Edision.

Please do the online Software update and see if the changes to Blindscan Plugin work on tuner 2 for signal in db.
Thanks.

[cyberham]

..see if the changes to Blindscan Plugin work on tuner 2 for signal in db....
Reading reported for 129W is 1209 dB. Similar for other two satellites. The number needs to be divided by 100.

[el bandido]

Please do the online Software update (Again). See if the math is correct. Thanks.

[cyberham]

Please do the online Software update (Again). See if the math is correct. Thanks.
Numbers are good!

18314

[el bandido]

Excellent!
Seems like it is working in Edision like it has been working in SF8008 Supreme.

Now you should be able to blindscan across two motorized tuners, and select position to blindscan on either tuner without getting unwanted motor movement.

You should be able to blindscan feed satellites such as 89 west c band from any position or any tuner. The ideas about moving the dish to the target satellite and then blindscanning it are great until you run into satellites that have no active channels. Sometimes there are good things to watch on 89w. Other times it is empty. 87west c band is similar.

Anyway, I guess we can say the signal id in blindscan plugin is working now for everyone. Thanks for having the patience to test it.

[el bandido]

I notice Media Player no longer works. If I click it in the Menu, the spinning wheel starts and the box is completely locked. I must remove DC plug on rear panel to restart the box. I've tried this twice.

Media Player opens, loads files, plays files...etc in SF8008 Supreme.
Media Player opens, shows folders...etc., but cannot play files in OSMIO4k because no video files are available. Otherwise, it seems to work in the MIO.

IF you continue to have problems with it, then make a debug log in telnet by doing the following commands:
init 4
ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/debug.log 2>&1

Now run the Media Player and let it lock up. Then get the log from the receiver, /tmp/debug.log, zip it and attach it.

[cyberham]

... zip it and attach it.

Attached.18315

ADDED: I really don't use the media player anymore. I used to use it to stream TV channels from around the world by loading m3u files onto Edision. But now, using the plugin Freearhey, I download the streaming files and just play them on the Edision like a satellite channel. So I can also record them too for time shifting if I choose. But I'm just curious why the Media Player causes the Edision to lock up.

[el bandido]

Put the attached files into the receiver. Here is the location:
/usr/lib/enigma2/python/Plugins/Extensions/MediaPlayer

REBOOT and see if the crash or image freeze continues.

[stephan94]

Congratulations :yes1:
when I read all the progress made with the positioner with the dBs that are indicated (is it also active for the Uclan Ustym?), I wonder if for fun I'm not going to try turning the antenna with the MIO 4K (although I'm very happy with my Openbox S3 mini HD as a positioner).

[el bandido]

Yes, Uclan Ustym has this. I do not know how it will work on Eastern satellites. Let me know if youi have problems.

[el bandido]

Sf8008 Shown below. Your Ustym is almost identical to this receiver.
18317

Everything should work in the Ustym, but the satellite may id as W instead of E for Europe. Or some other small problems...

Try it and see how it works.

[cyberham]

Put the attached files into the receiver....
Fixed! There already were files with the same names in that location but their suffixes were .pyc instead of .py.

[frankviana]

Thanks for all work.

Good to see transponders with low symbol rate.

I need test signals before lock, but I need 1 transponder to test here in Brazil with my motorized dish 5m (117w to 20e) with 3 kind of lnbf.

I'll post same things that need to fix with ISDB-T, same as OpenPli.

Tune the transponders, but don't store the channel names, then appear unavailable. OpenATV/OE-Alliance show correctly.

This post below using Vuzero4k, but happens for all OpenPli images (I tried all my boxes here using same both ISDB-T usb adapters: sf8008, osmini4k, h9se, etc)

[Only registered and activated users can see links]

See:

18318

18319

18320

18321

18322

18323

18324

Thanks

[el bandido]

@ frankviana,
I think we can fix that...Maybe.
Please start a thread on it in this section:
[Only registered and activated users can see links]

Need to use just one receiver. The Sf8008 Supreme would be nice.
The image needs to be setup on a slot by itself as a fresh install. Consider it to be a test image as we might mess it up.
The image needs one scan of DVB T. Do not add any satellite channels or services. Just one scan of DVB T.
Make a debug log of the DVB T scan. In telnet, use this command before the DVB T scan:
init 4
ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/dvb-T-debug.log 2>&1
After the scan completes, get the dvb-T-debug.log from /tmp of receiver files and attach it.
Then you need to attach the settings file, and the lamedb file located in /etc/enigma2 of receiver files.
Finally, In telnet, need the output of: cat /proc/bus/nim_sockets

If you can start a thread in the proper section and do all of that, we may have enough information to see what the problem is. Most likely, a small change will need to be made in enigma2, which means an image will have to be built. But we will see...

[frankviana]

Ok my friend.

I'll create new topic and will see.

I have sf8008 4k (not supreme) and osmini4k. Both don't work... All OpenPli don't work DVB-T/ISDB-T (siano and dib0700) tuners here.

We need this tuner working, because now, only OE-A works.

Among the countries that adopted this system are Argentina, Bolivia, Brazil, Chile, Costa Rica, Ecuador, Japan, Paraguay, Peru, Uruguay, Venezuela. In the testing or implantation phase are Angola, Philippines, Suriname and Botsuana.

I'll send you the logs and all that you need to solve.

Thanks
==================

[el bandido]

Use the SF8008. Just easier for me maybe.

Most likely, the problem is identification. The channels scan, but they probably end up being listed as something else. So the receiver cannot link the DVB T tuner to the channels scanned with DVB T tuner. We will see.....

[frankviana]

Use the SF8008. Just easier for me maybe.

Most likely, the problem is identification. The channels scan, but they probably end up being listed as something else. So the receiver cannot link the DVB T tuner to the channels scanned with DVB T tuner. We will see.....

Impossible sf8008 because we have 2 problems using OpenPli:

Appear s2x instead DVB-T and.... if solve DVB-T, we have same gray channels (no store refference channels). First, need fix nim_sockets and after, second problem.

[Only registered and activated users can see links]

Osmini4k need fix only second problem (gray channels)

For SF8008 and osmini4k, only SPA fixed both problems (appear DVB-T and store all channels). For sf8008, OpenATV appear as S2X too (no way to test DVB-T).

[Only registered and activated users can see links]

Thanks.

[el bandido]

A scan issue has been found and hopefully solved.
105W- C band has thousands of radio or service entries. Most of these are dead and are only active at certain times, but a blindscan or Service scan will list these services. And there are thousands of them.

Here is a scan of 105w-C band using TNAP 5.1 image dated 5-12-2024:
18364

The scan shown above is a blindscan and the plugin was set to scan all services and Not "Only free scan". Changing the blindscan plugin to "Only free scan" for this satellite will result in an enormous amount of scan time due to the number of services.

Here is a scan of 105w-C band after Today's online update:
18365

As you can see, a tremendous difference in the scan after the update.

Telnet or terminal update = opkg update && opkg upgrade

Update using the receiver menus = Menu--->Setup--->Software update
It is suggested to select option one as shown.
18366

Scan logs for these two scans attached.

This problem has existed for some time and is in more than One image type. Glad to see it fixed here!

[el bandido]

What else is broken, does not work, needs adjusting or repair?

[Megatron817]

Pluto tv has an update.

[eastof111]

The recall or previous key is not working in TNAP. When the key is pressed, it will go back to the previously viewed channel. Pressed again, the prior channel will display, etc.

In ATV the recall button will popup a history display of ALL prior channels
allowing the selection of any previously viewed channels. This still works in my other receiver with Satdreamgr too.

18370

Tried to assign a history display for the recall key with Setup>Usage & Gui>Hotkey Settings
But it does not work.... when any key is pressed, it won't allow to select a key and to assign it.

[BREDLE]

That 105 W update processed seamlessly online and worked effectively in under 5 minutes. Way to go El Bandido!

[eastof111]

Selecting plugins get a bad magic number....

[el bandido]

I managed to upload a python 3.10 plugin for the Positioner setup. This problem only exists in the SF8008. The wrong Plugin has been removed from the feeds. For now, Delete the Positioner setup plugin using the receiver menus. Then do an online update.

[el bandido]

This one is a Real Doozy!

We should have a new feature for scanning. Look at the very bottom of the screencap.
18374

[el bandido]

Unlocked transponders or transponders without a signal can be a big headache in scanning as they waste time. The flip side of an unlocked transponder or a transponder with no signal is the State of the transponder may change if you wait long enough. What was Unlocked may lock, or what has no signal may produce a signal. It all depends on how much time you want to wait.

Transponders are timed by the symbol rate on a sliding scale. For example, you may have a 5 second delay to wait for a transponder to become scannable if the symbol rate is 30,000 or higher. But you may want to wait 50 seconds for a transponder to show useful life if it is below 500, or extremely small symbol rate wise.

The scan is just part of it. The wait time is the tune timeout time and it is active every time the transponder changes.. So you cannot adjust the scan time without adjusting the tuning time the way things are set in the coding. We can make two options though and switch between them.

Option One will favor a fast scan. If the transponder does not have Lock, then it will be excused in roughly 4 seconds. Most of the lowest symbol rate transponders, The ones below a thousand, will be missed as they cannot usually lock in 4 seconds. But it does not have much of an effect on the other transponders. My tests setting a scan up like this show a dramatic increase in overall blindscan speed, but the small transponders are not only lost in the scan, they almost become unusable because the timeout timer starts every time a transponder changes.

Option 2 will favor the low symbol rate transponders. Unlocked transponders will be given the same amount of time as Locked transponders in hope they might change their state --which sometimes happens. Transponders below 500 can be given 50 seconds to lock as there are not many of them, but when one is found, you will have to wait until it resolves or times out.

Basically this gives two images in one. You can cull the unlocked transponders and do a few scans. Then turn unlocked transponders back on and enjoy the radio channels that the small transponders are on. My tests show this system works good. I will see about getting some images out that have this capability soon. Some adjustments will need to be made. We will see how it ends up...

[stephan94]

This is a really excellent idea.
Will this future possibility of different scanning times be independent of motor use?
in my case the antenna is directed by another positioner