TNAP-5 Image Discussion

el bandido said:
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.
Click to expand...

I do not use Autofocus. You try to use " Fine movement" option. That is what I use, and nothing else is is running besides Fine movement. After few Fine movements, the box becomes sluggish in every use: when browsing the channel list or any other list in the menus.
 
Megatron817 said:
Tnap 5 crash when doing a new manual scan of ATSC channels.
Click to expand...
This happened to me one time a couple weeks ago. I don't use the feature since, if it's like other ATSC scan functions in TVs, it will delete channels not found on a given new scan. My channels are distant and not always receivable so I don't want to lose them.
 
lme said:
I do not use Autofocus. You try to use " Fine movement" option. That is what I use, and nothing else is is running besides Fine movement. After few Fine movements, the box becomes sluggish in every use: when browsing the channel list or any other list in the menus.
Click to expand...


I don't think you understand. If nothing else was running, then your receiver would not work!

Several things are always running in the system. The spinner shows there is a slow down in the system. It is going to be hard to fix without seeing the problem as it does not exist here. Typing top in terminal shows some of the processes that are running. Typing opkg list-installed in terminal will show a good listing of items. The problem may/may not have anything to do with Posditioner setup.
 
cyberham said:
I didn't know this. I know it moves the dish to a pre-saved motor position when a different satellite is selected. But how can you fine tune (and save?) using Signal Finder? For Ku also?
Click to expand...

You are not using a actuator and positioner...

A c band actuator usually has a controller or positioner. The controller or positioner has provisions for saving locations. A ku motor does not have these options.
 
el bandido said:
...A c band actuator usually has a controller or positioner. The controller or positioner has provisions for saving locations. A ku motor does not have these options.
Click to expand...
So you use the controller or positioner to actually fine tune and then save the position in that box. The Signal Finder just displays the results.
 
Here is a good transponder to test the signal-below-lock feature. You need about 12.6 db for Lock and about 13.5 db for picture. This feed will be active for a while.

Satellite = 89w - c band
Transponder = DVB-S2 32APSK 4080V / 36499 / 3/4

89w-32apsk.webp


Code: 
                         Scan Report 

< File created on Thursday, March 28, 2024 at 12:44:33 > 
< Satellite =  89.0W C-band Galaxy 28 89.1 W >
< Receiver =  SF8008-Supreme >
< Enigma2 Image = Tnap 5 > 
< Kernel Version = 4.4.35 > 
< DVB Driver Date = 2023-07-25 > 
< Blindscan Frequency Range = 3625 to 4800 MHz > 
< Blindscan Symbol Rate Range = 1 to 60 Msps > 
< Blindscan Only Free Channels or Services? = False  > 
< Tuner = Tuner A: AVL62X1 (DVB-S2) >


< 'DVB-S2 8PSK 4031H / 15001 / 5/6' > Tp# 1
< Transponder SNR =['1.38db'-UnLocked], LNB Power = 84.41 >
< Thu, 28 Mar 2024 12:44:45 /> 

< 'DVB-S2 32APSK 4080V / 36499 / 3/4' > Tp# 2
< [1] CAM 17 - 17 GREEN  1:0:1:9:1:FFFF:A958FF0:0:0:0: SNR = 13.0  /> 
< [2] CAM 15 GREEN  1:0:1:A:1:FFFF:A958FF0:0:0:0: SNR = 13.0  /> 
< [3] CAM 10 GREEN  1:0:1:B:1:FFFF:A958FF0:0:0:0: SNR = 13.0  /> 
< [4] BEAUTY  1:0:1:C:1:FFFF:A958FF0:0:0:0: SNR = 13.0  /> 
< [5] RF CAM 1  1:0:1:D:1:FFFF:A958FF0:0:0:0: SNR = 13.0  /> 
< [6] RF CAM 3  1:0:1:E:1:FFFF:A958FF0:0:0:0: SNR = 13.0  /> 
< [7] RF CAM 5  1:0:1:F:1:FFFF:A958FF0:0:0:0: SNR = 13.0  /> 
< [8] OBTW  1:0:1:10:1:FFFF:A958FF0:0:0:0: SNR = 13.0  /> 
< Transponder SNR =['13.0db'-Locked], LNB Power = 91.75 >
< Thu, 28 Mar 2024 12:44:52 /> 

< 'DVB-S2 8PSK 4170H / 11501 / 3/4' > Tp# 3
< [9] NCAA Div 2  1:0:19:1:1:1:A95104A:0:0:0: SNR = 13.51  /> 
< Transponder SNR =['13.51db'-Locked], LNB Power = 91.75 >
< Thu, 28 Mar 2024 12:44:55 /> < 

Blind Scan Time = 2 Min. 03 Sec.
9 Channels ( TV = 9  Radio = 0)  3 of 3 Transponders Scanned.
 
The problem is a mixing of enigma2. TNAP5.1 updates were added to the TNAP 5 feeds. So it causes errors. The only way to fix it is to load an image that does not contain the errors. Online updates do not work because the tainted enigma2 shows a higher version than TNAP 5. The only way out is to load a backup or image that does not have this problem. Apologies are in order for this error!
 
el bandido said:
The problem is a mixing of enigma2. TNAP5.1 updates were added to the TNAP 5 feeds. So it causes errors. The only way to fix it is to load an image that does not contain the errors. Online updates do not work because the tainted enigma2 shows a higher version than TNAP 5. The only way out is to load a backup or image that does not have this problem. Apologies are in order for this error!
Click to expand...

I was able to fix it by swapping out the serviceScan from another older copy of tnap 5. No problems and I like how everything is working so far with the blindScan of 105W C band. Doesn't hang any more. Thanks!
 
A manual motor start has been added to the blindscan plugin. I am not going to fool with trying to put tease features in the TNAP5 version and plan to add these updates to the 5.1 version.

Really there are only two ways to identify a satellite in a FTA receiver. The first way is to receive the satellite beacon, which is 100% accurate, but impossible AFAIK for a FTA satellite receiver to do. The second way is to use transponder signals.

Using transponder signals for satellite identification in a FTA receiver is nothing short of messy We do not have a decent source of transponder information that is updated regularly and contains the information needed for satellite identification. Shown in the video below is what I am talking about. At least half of the satellites viewable in North America do not have the first transponder in the satellites.xml list active.

Satellites come and go. Transponders are active, then become inactive....etc. There are dedicated groups in Europe who keep their satellites.xml list updated, but not a single person does that in North America.The exception would be the occasional person who posts to Lyngsat hoping their find will be added. Once something is added to Lyngsat in North America, it usually stays there for months or years after it becomes inactive. So Lyngsat is better than nothing, but almost useless.

TVROSAT is supposed to have accurate satellite listings, but much of their stuff is either outdated, wrong, or Both.

So the basic thing is an active satellite transponder needs to be installed First in the satellites.aml file for each orbit location both C and Ku band that are viewable in North America. Then the list has to be maintained else satellites will quit identifying when accessed by the blindscan plugin. The video below shows what that looks like. And this is exactly Why satellite identification is not in current TNAP images.

It would be nice to have every available satellite identify when called in the blindscan plugin. But in North America, that is probably more of a Pipe Smokin' Dream than anything else.

 
Currently the only Edision 4K I have that works is the MIO. Some of this stuff is difficult to do and impossible to check without having the actual receiver. TNAP5.1 test images are being added to the Flash image of the receiver. The MIO I can check, but the other two Edision's I cannot check.

tnao5.1-test.webp
 
el bandido said:
Currently the only Edision 4K I have that works is the MIO. Some of this stuff is difficult to do and impossible to check without having the actual receiver. TNAP5.1 test images are being added to the Flash image of the receiver. The MIO I can check, but the other two Edision's I cannot check.

View attachment 18179
Click to expand...

So, I take it that there is a test 5.1 image for osmio 4K plus also.
Maybe there should be a new thread named "TNAP-5.1 image discussions". Just a suggestion.
 
So little time. Dunno if a chinabox receiver like the dreamlink t5 or linkbox 8000 that I have are considered 'fta'. But both do in fact identify satellites by beacon ID.
I always wondered why E2 receivers didn't do the same thing. There must be a secret.

EB. Your gut feeling. Is the SF8008 Supreme a good idea to buy right now? Seems like you've given it the torture test.
I know you're interested in good bluetooth functionality. What about a proven USB BT dongle?

Could you do a brief on which image/tuner driver combo seems to be working the best?
And perhaps a quick comparison rundown of your mio and the 8008. There is a whole lot of stuff up there.
 
Ali chipsets...Lol. Talk is cheap! Please demonstrate Today with a video the satellite identification ability of the dreamlink t5 or linkbox 8000. Make a video of these receivers properly identifying every satellite in your entire c band arc Today. Thanks in Advance because I know you will do this! In the name of Science, It Must Be Done!

The SF8008 Supreme is a decent FTA receiver. There is a thread on the Supreme. The "New" Supreme is nothing more than a new receiver using mostly dated parts. Pretty much that it is it. There are pluses and minuses when comparing the Supreme to a MIO. Currently the SF8008 Supreme or one of its variants is the only thing on the market. Everything about it that I have found has been covered in the thread already. Anything else I find will be added. Take it or leave it. No arm twisting required.
 
There is really no need to prove anything. I don't BS. I would invite you to do the same if you doubt me. I'm sure you must have a similar receiver in "the pile".
Matter of fact. When trying to hunt and store sats into my ASC-1 with the mio currently used. There was a bit of wtf trying to figure out which one I was on.
You know. The overlapping ku sat signals. I'm thinking like on 117-119 (example). Where the LO for 119 would have to been set at 11250 with the correct lnbf.
A blindscan results in transponders that just-don't-exist. Leading again to a scratch your ass and wtf!-mumble.
Until you realize you're getting bleed over from 119 (maybe). Dust off that T5. Slap it on the coax. Enter the tp's in question into the menu along with ones you know are...117. And wa-frikin'-la!
Toggle through them and the beacon ID shows right up in the screen. Ahh sweahs fo' god.
If anyone has an ASC-1 up for grabs Please let me know. As long as it works. I don't care about flaky relays. I've been parked on 127W for way too long.
Then we can drink a lot of beer and put fans in front of us and see who gets wet first. I'll post enough photos to have breakfast over.

The SF8008 Supreme with 2 identical AVL tuners enough is enticing. And the communities look as if the deficiencies are at least being identified. That's why I axed.
Getting out of the Broadcom chipset world into the new ones is a bit questionable as far as what the manufacturers are willing to address and modify code.
 
Okay then you had a "Special Model" FTA Receiver.
FTA receivers with Ali chipsets Did Not have beacon satellite identification. They used a satellite file or file similar to it. Satellite ID was done using the satellite transponders for satellite identification---same as the rest of the FTA receivers, enigma2 included.
 
Back
Top