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.
Thread: TNAP-5.1 Image Discussion
Results 101 to 105 of 105
-
05-05-2024,10:12 AM.
.
.
Meine Dreambox One ist ein Stück Scheiße!.
-
Post Thanks / Like - 1 Thanks, 0 Likes, 0 Kiss My AssMegatron817 thanked for this post
-
05-05-2024,10:56 AM
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.Last edited by Megatron817; 05-05-2024 at 12:12 PM.
-
Post Thanks / Like - 1 Thanks, 0 Likes, 0 Kiss My Assel bandido thanked for this post
-
05-05-2024,11:11 AM
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!
-
05-05-2024,11:43 AM
-
Post Thanks / Like - 1 Thanks, 0 Likes, 0 Kiss My AssMegatron817 thanked for this post
-
-
Post Thanks / Like - 1 Thanks, 0 Likes, 0 Kiss My Assel bandido thanked for this post