Please provide the EXACT path of the setting you are looking for in the image that actually has it. A screenshot of the setting would help, but is not needed if the exact path is shown along with image make and build.
TNAP-6 Image Discussion
- Thread starter EnoSat
- Start date
Please provide the EXACT path of the setting you are looking for in the image that actually has it. A screenshot of the setting would help, but is not needed if the exact path is shown along with image make and build.
I have checked the TNAP6 image files and do not see a problem. I checked OpenVix enigma2 image files and find no reference for a bouquet toggle form unsorted to sorted in alphabetical order. No such setting for bouquets exist in OpenVix enigma2 image that I can find. The problem you are having is not a TNAP6 problem or at least none that I can find by looking at the file systems of two different images
Anytime you edit, you are subject to get warnings about errors or corruption as shown below:
It should be noted that the "&" symbol exists in enigma2 satellite files. In Unix/Linux systems, "&" is a special character that runs commands in the background. This is likely causing some operations to fail. The "&" symbol will be removed in TNAP images satellite.xml files.
As a test, the Demon Editor was used to jumble up the 101w bouquet.
The edited bouquet keeps the same order in TNAP6 . It does not get sorted alphabetically (Sort by Name).
I do not edit much of anything or use bouquets on a regular basis as I have no need for such. Others have meticulously edited everything in the channel selection to their personal liking and tastes which is great. Editing or altering satellite.xml or satellite channel files can easily cause errors or corruption. Carefully check what you have in the way of channel files and you will probably find the problem. To get into alpahbetical order, you are going to need a command similar to "order by name". In the channel selection file, we do not have that and neither does OpenVix.
Bouquet queries use "ORDER BY bouquet", Not "ORDER BY name":
Anytime you edit, you are subject to get warnings about errors or corruption as shown below:
It should be noted that the "&" symbol exists in enigma2 satellite files. In Unix/Linux systems, "&" is a special character that runs commands in the background. This is likely causing some operations to fail. The "&" symbol will be removed in TNAP images satellite.xml files.
As a test, the Demon Editor was used to jumble up the 101w bouquet.
The edited bouquet keeps the same order in TNAP6 . It does not get sorted alphabetically (Sort by Name).
I do not edit much of anything or use bouquets on a regular basis as I have no need for such. Others have meticulously edited everything in the channel selection to their personal liking and tastes which is great. Editing or altering satellite.xml or satellite channel files can easily cause errors or corruption. Carefully check what you have in the way of channel files and you will probably find the problem. To get into alpahbetical order, you are going to need a command similar to "order by name". In the channel selection file, we do not have that and neither does OpenVix.
Bouquet queries use "ORDER BY bouquet", Not "ORDER BY name":
Strange but makes sense. To make life easier I did write the vix lamedb to the fresh TNAP image.
I think I'll try read the TNAP image after a channel scan with it's own native lamedb and see what happens.
Could it be the lamedb version perhaps? Just that in previous versions using a saved file writtten to them, ordering wasn't an issue.
Thanks!
I think I'll try read the TNAP image after a channel scan with it's own native lamedb and see what happens.
Could it be the lamedb version perhaps? Just that in previous versions using a saved file writtten to them, ordering wasn't an issue.
Thanks!
Per chance, did you make life even easier and transfer the settings file from the Vix image?
When dealing with a test image or really any different image, it is best to start with a "Fresh Install" which means nothing is transferred from an existing image to the new or test image. This ensures things are set correctly (hopefully) and also ensures any problems that are seen are related to the image and not to the transferred files.
The settings file may have config. statements along with other things that are not compatible form one image to the next, or there can be issues in files that are not seen in one image but are seen in another image.
What is almost always safe to transfer between images are the nims in settings, but sometimes even that is problematic. I am fairly certain though, the nims in settings are compatible from Vix to OpenPli type images. OpenATV I think the nims are different. Enigma2 has to be put to sleep or you have to be editing a slot that is not currently loaded to change most things in /etc/enigma2. Other things in /etc/enigma2 that can usually be safely transferred between images are the channel files such as lamedb and bouquets. Any other file besides these should probably not be transferred between images.
Finally, the satellites.xml that the nims were created with or the satellite.xml that the channel files were created with needs to be transferred. Using a satellites.xml that was not being used when the nims or channel information was created can cause problems.
When dealing with a test image or really any different image, it is best to start with a "Fresh Install" which means nothing is transferred from an existing image to the new or test image. This ensures things are set correctly (hopefully) and also ensures any problems that are seen are related to the image and not to the transferred files.
The settings file may have config. statements along with other things that are not compatible form one image to the next, or there can be issues in files that are not seen in one image but are seen in another image.
What is almost always safe to transfer between images are the nims in settings, but sometimes even that is problematic. I am fairly certain though, the nims in settings are compatible from Vix to OpenPli type images. OpenATV I think the nims are different. Enigma2 has to be put to sleep or you have to be editing a slot that is not currently loaded to change most things in /etc/enigma2. Other things in /etc/enigma2 that can usually be safely transferred between images are the channel files such as lamedb and bouquets. Any other file besides these should probably not be transferred between images.
Finally, the satellites.xml that the nims were created with or the satellite.xml that the channel files were created with needs to be transferred. Using a satellites.xml that was not being used when the nims or channel information was created can cause problems.
They'reee baaaaack! Nice update.
Your first question. I started from scratch with the settings. Found out that even patching in the nims section of settings from a previous TNAP install gave strange results. So, started the setup process just like any other new image using the wizard.
I did keep the stock, out of box satellites.xml. Oh yeah, definitely using init 4 and init 3 or just init 4, reboot in putty. Although did not since it was approached as a brand new image.
When I get some time this evening I'll sit down and fire up v6. I noticed something that sparked a few questions.
I mentioned that channels were not in the order that I'm used to seeing when the lamedb is transferred from E Channelizer. Being in alpha order.
Now. If it's the combination of button presses to be able to firstly change chanels in the current bouquet with the 4-way up/down button. While being able to change bouquets with the page up/down button on the osmio4k remote.
Need to spend some time to streamline that op. That's how it's done with ViX anyhow.
One satellite (bouquet) was in the same order as it was in the channel editor. While other ones were not. Sorry, jumped to conclusions.
The gears were spinning. The ViX lamebd transferred to TNAP6 glitched for me it seemed.
Could it possibly be the lamedb version that ViX uses is different from v6?
I do like how v6 is getting a few tekkie mods such as show signal below lock. The selection of tuner drivers. Nice!
A pipe dream. Some sort of an SDR/Spectrum Analyzer plugin to manually zip up and down a frequency range To seek and prove obscure, wild feed sigs. are indeed present, even though not modulated.
Maybe it is a trait of Pli. Some of the setup menus like network lack some of the things I'm used to. Samba, etc. Perhaps things added from the plugins menu? Which is pleasantly populated.
As well as the ServiceApp thingy in Setup>System.
Anyhow probably because it was never an issue and channels transferred and showed in the order that I set them in with the channel editor. I screwed up and thought there was a setting to force alpha or how they were imported. Oops!
Oh. Hey. About the SF8008 newest models. Hit and miss findings over on Ricks. We have different tuner drivers for the osmio4k receivers. Not sure about the mini. What is the opinion of fimware stability and performance currently as far as development advancements and giltch discovery and fixes? It there one and only one SF8008 tuner driver?
Thx! Nice update here.
Your first question. I started from scratch with the settings. Found out that even patching in the nims section of settings from a previous TNAP install gave strange results. So, started the setup process just like any other new image using the wizard.
I did keep the stock, out of box satellites.xml. Oh yeah, definitely using init 4 and init 3 or just init 4, reboot in putty. Although did not since it was approached as a brand new image.
When I get some time this evening I'll sit down and fire up v6. I noticed something that sparked a few questions.
I mentioned that channels were not in the order that I'm used to seeing when the lamedb is transferred from E Channelizer. Being in alpha order.
Now. If it's the combination of button presses to be able to firstly change chanels in the current bouquet with the 4-way up/down button. While being able to change bouquets with the page up/down button on the osmio4k remote.
Need to spend some time to streamline that op. That's how it's done with ViX anyhow.
One satellite (bouquet) was in the same order as it was in the channel editor. While other ones were not. Sorry, jumped to conclusions.
The gears were spinning. The ViX lamebd transferred to TNAP6 glitched for me it seemed.
Could it possibly be the lamedb version that ViX uses is different from v6?
I do like how v6 is getting a few tekkie mods such as show signal below lock. The selection of tuner drivers. Nice!
A pipe dream. Some sort of an SDR/Spectrum Analyzer plugin to manually zip up and down a frequency range To seek and prove obscure, wild feed sigs. are indeed present, even though not modulated.
Maybe it is a trait of Pli. Some of the setup menus like network lack some of the things I'm used to. Samba, etc. Perhaps things added from the plugins menu? Which is pleasantly populated.
As well as the ServiceApp thingy in Setup>System.
Anyhow probably because it was never an issue and channels transferred and showed in the order that I set them in with the channel editor. I screwed up and thought there was a setting to force alpha or how they were imported. Oops!
Oh. Hey. About the SF8008 newest models. Hit and miss findings over on Ricks. We have different tuner drivers for the osmio4k receivers. Not sure about the mini. What is the opinion of fimware stability and performance currently as far as development advancements and giltch discovery and fixes? It there one and only one SF8008 tuner driver?
Thx! Nice update here.
Bouquets and lamedb REQUIRE the satellites.xml that they were created with to work properly. A look at the coding will show OE Alliance and OpenPLi use almost identical items when it comes to lamedb and bouquet creation. When you find a bug in one, you usually find the same or similar bug in the other version. Start with post 111 in this thread and you will see indeed bugs or issues that are common in OpenPli are also common in Oe Alliance or OpenVix: https://forums.openpli.org/topic/102179-testbuild-scarthgap/page-6 . What I am trying to tell you is there is probably nothing wrong with the file structure of TNAP 6. The most likely problem is in what you are trying to put in it. No way to know without seeing seeing the exact files that are trying to be installed.
TNAP 6 begins the integration of AI technology into the image. Some features are built strictly using AI with one example being the wheel loader for Edision driver selection. AI has also assisted in scan edits and other areas of the TNAP 6 image. Provisions are being made to close TNAP and make it strictly a private type image as the bullshit from the fta community is very discouraging at times. People complain about the TNAP image, this forum, and other things that they do not support or have anything to do with. But after close to 25 years on the satellite internet forums, it is understood that people will be people. But at some points, it is nice to hear crickets instead of the noise of city life, hence Closing TNAP may be a great idea.
Other AI enhancements or starts in TANP 6 include pidscan using TSDuck. While adding a spectrum analyzer seems like a grand idea, in reality it is not going to do a whole lot due to the limits of what is available in receiver resources. A proper pidscan though can show things at times that are normally not seen.
There is a thing called a manifest or in lieu of a manifest opkg list-installed The manifest will show Samba is already installed in TNAP, so why do we need a menu for something that is already installed??? A careful look at the manifest will also show other things installed by default into the image. The idea behind TNAP is to keep it simple and neat. If something is needed, then add it. There is no reason to have hundreds of plugins in the plugins download when only a few of them even remotely apply to North America. Some Plugins in TNAP exist for Europe because some users there assist in the TNAP design.
Ocgaton SF8008...again...
The Octagon SF8008 was released around 2017 if memory serves. It was released with a SiLabs demod referred to as the tuner in receiver menus. Octagon released another SF8008 Supreme in 2023, 2024 year range that had Internal SSD capability and Avalink Demod, which is called tuner in the receiver's menus. This updated receiver also has improved wifi. And Now Octagon releases again the same Si2166D Demod that it originally had in 2017, calling it something "New". This is the exact same receiver from 2017 except for the internal SSD and wifi. All three of these receivers run the exact same image. The coders for Octagon simply stuck the Avalink driver in with the SI2166D driver to make a "One Size Fits All" image.
Rick Caylor was mentioned. Rick Caylor sells stuff. He does not support the stuff he sells and is most likely ignorant about the 3 models of SF8008. Sell it and make a buck. That is the deal, along with squashing any conversation about similar receivers when possible. And automatically delete conversations about cheap receivers. The FTA community in North America is blessed to have a person like Rick, but he is in it for the money and not as a hobby.
Improvements to the TNAP download site are being made. See: https://tnapimages.com/
Making improvements to tnapimages.com and other things in life have taken away from improving TNAP 6. But it is all a matter of time, Good Lord willing... OSMio4k, 4kplus, and OSmini4K all use the same driver.
TNAP 6 begins the integration of AI technology into the image. Some features are built strictly using AI with one example being the wheel loader for Edision driver selection. AI has also assisted in scan edits and other areas of the TNAP 6 image. Provisions are being made to close TNAP and make it strictly a private type image as the bullshit from the fta community is very discouraging at times. People complain about the TNAP image, this forum, and other things that they do not support or have anything to do with. But after close to 25 years on the satellite internet forums, it is understood that people will be people. But at some points, it is nice to hear crickets instead of the noise of city life, hence Closing TNAP may be a great idea.
Other AI enhancements or starts in TANP 6 include pidscan using TSDuck. While adding a spectrum analyzer seems like a grand idea, in reality it is not going to do a whole lot due to the limits of what is available in receiver resources. A proper pidscan though can show things at times that are normally not seen.
There is a thing called a manifest or in lieu of a manifest opkg list-installed The manifest will show Samba is already installed in TNAP, so why do we need a menu for something that is already installed??? A careful look at the manifest will also show other things installed by default into the image. The idea behind TNAP is to keep it simple and neat. If something is needed, then add it. There is no reason to have hundreds of plugins in the plugins download when only a few of them even remotely apply to North America. Some Plugins in TNAP exist for Europe because some users there assist in the TNAP design.
Ocgaton SF8008...again...
The Octagon SF8008 was released around 2017 if memory serves. It was released with a SiLabs demod referred to as the tuner in receiver menus. Octagon released another SF8008 Supreme in 2023, 2024 year range that had Internal SSD capability and Avalink Demod, which is called tuner in the receiver's menus. This updated receiver also has improved wifi. And Now Octagon releases again the same Si2166D Demod that it originally had in 2017, calling it something "New". This is the exact same receiver from 2017 except for the internal SSD and wifi. All three of these receivers run the exact same image. The coders for Octagon simply stuck the Avalink driver in with the SI2166D driver to make a "One Size Fits All" image.
Rick Caylor was mentioned. Rick Caylor sells stuff. He does not support the stuff he sells and is most likely ignorant about the 3 models of SF8008. Sell it and make a buck. That is the deal, along with squashing any conversation about similar receivers when possible. And automatically delete conversations about cheap receivers. The FTA community in North America is blessed to have a person like Rick, but he is in it for the money and not as a hobby.
Improvements to the TNAP download site are being made. See: https://tnapimages.com/
Making improvements to tnapimages.com and other things in life have taken away from improving TNAP 6. But it is all a matter of time, Good Lord willing... OSMio4k, 4kplus, and OSmini4K all use the same driver.
Last edited:
Excellent! And a "Work-in-Progress" it is. Also a place to leave a message if needed...
good job!
EnoSat
Legit VIP
Some attempts at a spectrum analyzer date back to the days of Relook 400 or Cuberevo 900 with enigma1 (unfortunately the link to the source code is no longer working).
https://legitfta.com/forum/attachment.php?attachmentid=18917&d=1749284065
Pidscan works well with dvbsnoop so far, although it no longer names some new stream types correctly (for example pid 4094 for DCII).
The first (year 2018) to try using TSDuck in OE was athoik from the image team SDG (SDG Image 6).
It is good to continue this effort.
PS: It wasn't open linux, but once upon a time Dr.HD implemented an analyzer into its regular receiver.
Attachments
Last edited:
I appreciate seeing that spectrum, but IMO, it would take resources to run it, and it really would not give us much in a FTA receiver unless maybe you had a TBS tuner connected, which would be interesting. TSDuck has been dropped I think, so reviving it again pays homage to Athoik. Work will continue with MODCOD as time permits.
@Arlo,
I appreciate your candid response, and I understand the skepticism about AI - it's completely understandable given how it's often misrepresented or over-hyped. Let me clarify what AI integration in TNAP actually means, because it's nothing like the "I'll be back" scenario you mentioned, and it's certainly not the intrusive "AI search results" that Yahoo and others force on users.
When I mention AI assistance in TNAP development, I'm talking about a collaborative tool - think of it as an extremely knowledgeable programming assistant that never gets tired, never forgets syntax, and can analyze code patterns across thousands of files instantly. Here's what it actually does:
Real AI Examples from TNAP Development:
When working on the wheel loader for Edision driver selection, AI helped identify optimization patterns that reduced load time by analyzing similar implementations across different platforms
For the low symbol rate satellite transponder reception (below 1000), AI assisted in refactoring the demodulator code to handle edge cases that were causing reception issues
In implementing TSDuck integration, AI helped parse through the extensive TSDuck documentation and create efficient bindings for the Enigma2 environment
For blindscan improvements, AI analyzed existing scan algorithms and suggested mathematical optimizations that improved scan speed without sacrificing accuracy
This isn't some autonomous system making decisions - it's me asking specific technical questions and getting detailed answers with code examples. Think of it like having a senior developer who's read every programming book, analyzed every open-source satellite receiver project, and can instantly recall any of it when needed.
What AI Doesn't Do:
It doesn't "take over" anything
It doesn't make autonomous decisions about your receiver
It doesn't collect data or "phone home"
It doesn't change how TNAP operates for end users
The AI integration I'm talking about is purely on the development side. When you use TNAP, you're not interacting with AI at all - you're using code that was improved with AI assistance during development. It's like saying a car was "designed with CAD software" - the CAD doesn't ride along with you; it just helped make a better design.
Regarding the "closing TNAP" consideration - I hear your concerns, and you make valid points. The SDR# example is a perfect cautionary tale. The frustration comes from spending hundreds of hours improving something, only to have people complain about free work they didn't contribute to. But you're right - the community benefits from open development, and spite-closing would hurt the very people who appreciate the work.
As for the manifest and terminal usage - fair point about beginners. Perhaps a simple GUI option to view installed packages would be more user-friendly than expecting terminal usage. The goal is to keep things clean, not to make them unnecessarily complex.
The AI assistance has genuinely accelerated development and improved code quality. It's not marketing hype or forced integration - it's a practical tool that helps solve real technical challenges faster and more efficiently than working alone. No Skynet, no HAL 9000, just better code through enhanced development tools. Hopefully This makes clearer the AI integration into TNAP.
@Arlo,
I appreciate your candid response, and I understand the skepticism about AI - it's completely understandable given how it's often misrepresented or over-hyped. Let me clarify what AI integration in TNAP actually means, because it's nothing like the "I'll be back" scenario you mentioned, and it's certainly not the intrusive "AI search results" that Yahoo and others force on users.
When I mention AI assistance in TNAP development, I'm talking about a collaborative tool - think of it as an extremely knowledgeable programming assistant that never gets tired, never forgets syntax, and can analyze code patterns across thousands of files instantly. Here's what it actually does:
Real AI Examples from TNAP Development:
When working on the wheel loader for Edision driver selection, AI helped identify optimization patterns that reduced load time by analyzing similar implementations across different platforms
For the low symbol rate satellite transponder reception (below 1000), AI assisted in refactoring the demodulator code to handle edge cases that were causing reception issues
In implementing TSDuck integration, AI helped parse through the extensive TSDuck documentation and create efficient bindings for the Enigma2 environment
For blindscan improvements, AI analyzed existing scan algorithms and suggested mathematical optimizations that improved scan speed without sacrificing accuracy
This isn't some autonomous system making decisions - it's me asking specific technical questions and getting detailed answers with code examples. Think of it like having a senior developer who's read every programming book, analyzed every open-source satellite receiver project, and can instantly recall any of it when needed.
What AI Doesn't Do:
It doesn't "take over" anything
It doesn't make autonomous decisions about your receiver
It doesn't collect data or "phone home"
It doesn't change how TNAP operates for end users
The AI integration I'm talking about is purely on the development side. When you use TNAP, you're not interacting with AI at all - you're using code that was improved with AI assistance during development. It's like saying a car was "designed with CAD software" - the CAD doesn't ride along with you; it just helped make a better design.
Regarding the "closing TNAP" consideration - I hear your concerns, and you make valid points. The SDR# example is a perfect cautionary tale. The frustration comes from spending hundreds of hours improving something, only to have people complain about free work they didn't contribute to. But you're right - the community benefits from open development, and spite-closing would hurt the very people who appreciate the work.
As for the manifest and terminal usage - fair point about beginners. Perhaps a simple GUI option to view installed packages would be more user-friendly than expecting terminal usage. The goal is to keep things clean, not to make them unnecessarily complex.
The AI assistance has genuinely accelerated development and improved code quality. It's not marketing hype or forced integration - it's a practical tool that helps solve real technical challenges faster and more efficiently than working alone. No Skynet, no HAL 9000, just better code through enhanced development tools. Hopefully This makes clearer the AI integration into TNAP.
THAT was a very thought out and intuitive response El Bandido! Instead of getting peeled out you made some very clear reasons and explanations. My AI impression may be one sided but I do understand "programs that write programs" all the while debugging and identifying bottlenecks and providing alternates.
On another site there is a discussion as to a receiver that decodes 4:2:2 (it never ends, don't it). It carries on to narrow down to an Apple TV and Nvidia Shield. Specs and capabilities are posted for both.
Although I hate them with a passion. It looks like Apple comes out tops. A fellow there keeps posting a Chat GPT (he calls it "his friend") of the 2019 Shield. BTW I really like the latest Fire TV Cube.
I'm not up on the Shield and a quick specs search comes up with basically what you see on most FTA satellite related vendors sites. Stock release factory info.
Keeping with the subject. It takes folks like you that go in-depth to try and beat the crap out of a devices capabilities and prove true or BS of the printed nomenclature. And you've done one heck of a good job at that.
AI can be approached in many ways now that we are in the middle of the 2020's. Trust your gut. Question "authority". We were joking about knowing where you are driving to and getting a constant.....
REE-Calculating.
Linux applications. GNU. Stuff. Hard work and protecting intellectual properties is fine. True open source projects that get pulled aside by a group with a ton of work given to them. And eventually deemed closed source. All the while "forks" of the same root project which remain open source. And when someone finds a way to write a bit of code that duplicates the functions of the closed source module(s).
With the guys yelliing that the stole it. Did they really? Not so sure.
No need to get into depth. If TNAP is modeled after OpenPlli. Using plugins created by people who do it because they enjoy it. And proud to distribute it. The blindscan plugin. The elusive Services feature in Signal finder. Cool and useful things. I know so little of what it takes to integrate workable variants of any of them for different E2 (or any program, architecture out there) images.
As far as the spectrogram that Eno showed. Choppy, ancient. Still an awesome idea. It would, exactly like you, we, us, would see using an SDR, spectrum analyzer tapped into a LNBF.
The idea of using a TBS card to scan. Looking for wild feeds. Being able to see when a transponder gets turned on and configured from the ground station for an event.
Or just letting a person know a signal is present, modulated or just a carrier wave.
During ball season a few satellites get almost weekly uplinks with freqs. and such all over the place. But it takes work, intuition, patience, and time on an E2 receiver "hammering" the satellite with blindscans finding them. Most don't have a SA to hang off of a tapped coax line. But it would be a rush to see a new spike on the display. Plug the frequency into the receiver. And see what materializes.
The same I would do using a DVB PCIe card in a pc and stabbing in into the receiver, and possibly (me, definitely!) adding it into the satellites.xml file.
Oh. Mista' Kotta', Mista' Kotta' !!! A few posts back. E Channelizer. I'm using an older version. Can select lamedb v4 & v5. I just use the default v4 and always have.
Awhile back I put up a sample of a chunk of the .xml. You responded that if anyone used it, it would corrupt their .xml. Which was 100% true if c/p into theirs exactly as shown.
The E Channelizer channel editor writes satellites.xml with each line starting with 4 padded spaces. A stock, out of box .xml starts with two tabs.
Reveal all (unprintable) characters in notepad++ or whatever XML editor du-jour. And there it is. It still works an any image that I ever used without any errors. You know, to streamline setup. Writing the channel list into a receiver. Init 4 and transferring the .xml into the receiver. Then either a reboot or Init 3 command. So that might just be my issue in TNAP v6 with the alpha ordering. Which BTW after looking into it a bit more. Some channels are in the editor order and some persist in alpha order. So that is my screw-up and up to be to decipher.
Okay. Thanks for the cool AI explanation and lesson. Let me let us get back to the TNAP 6 discussion. Oh. Look out. That Eno is a smart cookie. He's helped me out several times and always very patient and informative. Haha! ahl be bock.
On another site there is a discussion as to a receiver that decodes 4:2:2 (it never ends, don't it). It carries on to narrow down to an Apple TV and Nvidia Shield. Specs and capabilities are posted for both.
Although I hate them with a passion. It looks like Apple comes out tops. A fellow there keeps posting a Chat GPT (he calls it "his friend") of the 2019 Shield. BTW I really like the latest Fire TV Cube.
I'm not up on the Shield and a quick specs search comes up with basically what you see on most FTA satellite related vendors sites. Stock release factory info.
Keeping with the subject. It takes folks like you that go in-depth to try and beat the crap out of a devices capabilities and prove true or BS of the printed nomenclature. And you've done one heck of a good job at that.
AI can be approached in many ways now that we are in the middle of the 2020's. Trust your gut. Question "authority". We were joking about knowing where you are driving to and getting a constant.....
REE-Calculating.
Linux applications. GNU. Stuff. Hard work and protecting intellectual properties is fine. True open source projects that get pulled aside by a group with a ton of work given to them. And eventually deemed closed source. All the while "forks" of the same root project which remain open source. And when someone finds a way to write a bit of code that duplicates the functions of the closed source module(s).
With the guys yelliing that the stole it. Did they really? Not so sure.
No need to get into depth. If TNAP is modeled after OpenPlli. Using plugins created by people who do it because they enjoy it. And proud to distribute it. The blindscan plugin. The elusive Services feature in Signal finder. Cool and useful things. I know so little of what it takes to integrate workable variants of any of them for different E2 (or any program, architecture out there) images.
As far as the spectrogram that Eno showed. Choppy, ancient. Still an awesome idea. It would, exactly like you, we, us, would see using an SDR, spectrum analyzer tapped into a LNBF.
The idea of using a TBS card to scan. Looking for wild feeds. Being able to see when a transponder gets turned on and configured from the ground station for an event.
Or just letting a person know a signal is present, modulated or just a carrier wave.
During ball season a few satellites get almost weekly uplinks with freqs. and such all over the place. But it takes work, intuition, patience, and time on an E2 receiver "hammering" the satellite with blindscans finding them. Most don't have a SA to hang off of a tapped coax line. But it would be a rush to see a new spike on the display. Plug the frequency into the receiver. And see what materializes.
The same I would do using a DVB PCIe card in a pc and stabbing in into the receiver, and possibly (me, definitely!) adding it into the satellites.xml file.
Oh. Mista' Kotta', Mista' Kotta' !!! A few posts back. E Channelizer. I'm using an older version. Can select lamedb v4 & v5. I just use the default v4 and always have.
Awhile back I put up a sample of a chunk of the .xml. You responded that if anyone used it, it would corrupt their .xml. Which was 100% true if c/p into theirs exactly as shown.
The E Channelizer channel editor writes satellites.xml with each line starting with 4 padded spaces. A stock, out of box .xml starts with two tabs.
Reveal all (unprintable) characters in notepad++ or whatever XML editor du-jour. And there it is. It still works an any image that I ever used without any errors. You know, to streamline setup. Writing the channel list into a receiver. Init 4 and transferring the .xml into the receiver. Then either a reboot or Init 3 command. So that might just be my issue in TNAP v6 with the alpha ordering. Which BTW after looking into it a bit more. Some channels are in the editor order and some persist in alpha order. So that is my screw-up and up to be to decipher.
Okay. Thanks for the cool AI explanation and lesson. Let me let us get back to the TNAP 6 discussion. Oh. Look out. That Eno is a smart cookie. He's helped me out several times and always very patient and informative. Haha! ahl be bock.
FWIW,
You are not gonna get very far with coding aspirations using a free version of chatgpt or any AI Free Version. Those versions simply exists as demos. The good AI's that can code cost money, and depending on the project, you may need more than one. Coding AI's are subject to errors just like humans, so uttermost attention at all times is needed. But the results, when you get them are nothing short of impressive. There is an art to using AI's in coding. It is not Plug N Play.
So to be clear, we are not using the cracker jack box type Free Version of ChatGPT, we are using coder versions of AI that require money to run. Will get started back on finishing this TNAP6 image as time permits. Have not been able to do anything with it for over a month now, which is unusual.
You are not gonna get very far with coding aspirations using a free version of chatgpt or any AI Free Version. Those versions simply exists as demos. The good AI's that can code cost money, and depending on the project, you may need more than one. Coding AI's are subject to errors just like humans, so uttermost attention at all times is needed. But the results, when you get them are nothing short of impressive. There is an art to using AI's in coding. It is not Plug N Play.
So to be clear, we are not using the cracker jack box type Free Version of ChatGPT, we are using coder versions of AI that require money to run. Will get started back on finishing this TNAP6 image as time permits. Have not been able to do anything with it for over a month now, which is unusual.
Hi
Octagon sf8008 Supreme V3
Do you know if there is a way to fix a bug with the silab tuners in blind scan in C band With a transponders that in blind scanning, it increases 8 points and does not lower the channels.
In total there are several if we put together the transponders of the entire arc that cause this problem there are 1 or two per satellite
Sat 101W MGM
The most problematic is 4060 H 30000 DVB S2 8psk, in blind scan it is downloaded as 4068H3000 DVB S QPSK and does not scan the channels, it skips them
Octagon sf8008 Supreme V3
Do you know if there is a way to fix a bug with the silab tuners in blind scan in C band With a transponders that in blind scanning, it increases 8 points and does not lower the channels.
In total there are several if we put together the transponders of the entire arc that cause this problem there are 1 or two per satellite
Sat 101W MGM
The most problematic is 4060 H 30000 DVB S2 8psk, in blind scan it is downloaded as 4068H3000 DVB S QPSK and does not scan the channels, it skips them
Attachments
Sad to hear that about the SiLabs tuner. A couple of things though:
In terminal, run these two commands:
init 4
ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/enigma.log 2>&1
Attach the enigma.log file that will be generated to a post here. Log will be in /tmp of receiver files.
Make for certain or Be sure it is the SF8008 V3 that is the problem. A drifting lnb will do the same thing. If a pattern can be found, then it may be fixed.
I think SiLabs 2166D has a hardware blindscan option. It might be a good idea to activate it and see if the problem is in it too. The thing is to find a pattern as one most likely exists.
In terminal, run these two commands:
init 4
ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/enigma.log 2>&1
Attach the enigma.log file that will be generated to a post here. Log will be in /tmp of receiver files.
Make for certain or Be sure it is the SF8008 V3 that is the problem. A drifting lnb will do the same thing. If a pattern can be found, then it may be fixed.
I think SiLabs 2166D has a hardware blindscan option. It might be a good idea to activate it and see if the problem is in it too. The thing is to find a pattern as one most likely exists.
If the problem is the SF8008 V3 with silab, I have two Titanium LNBs and it does the same thing on both of them on the same transponders and a friend also has the SF8008 V3 with Norsat LNB and it does the same thing to him.
The temporary solution is to remove the problematic transponders from the list or any logs and redo the blind scan. Suppose the transponder successfully downloads only 3 or 5 more points and then downloads the channels, but it doesn't always work, so it could be a software error.
We've already tried 3 different images and the same thing happens.
I left out an important part.
Do everything over again just like you did, except BlindScan the satellite while the log is running. If you have another problematic satellite, you may BlindScan it as well. The idea is to see what the raw output of the blindscan is and the log will show that. --or least it should. Thanks.
Do everything over again just like you did, except BlindScan the satellite while the log is running. If you have another problematic satellite, you may BlindScan it as well. The idea is to see what the raw output of the blindscan is and the log will show that. --or least it should. Thanks.
You give me the same thing. There is no Blindscan information in the log. A blindscan of the satellite has to be performed while the log is running:
init 4
ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/enigma.log 2>&1
BlindScan The problem Satellites
Then...
Attach the enigma.log file that will be generated to a post here. Log will be in /tmp of receiver files.
Blindscan has to be done while the log is running.
init 4
ENIGMA_DEBUG_LVL=5 enigma2 > /tmp/enigma.log 2>&1
BlindScan The problem Satellites
Then...
Attach the enigma.log file that will be generated to a post here. Log will be in /tmp of receiver files.
Blindscan has to be done while the log is running.