el bandido

Thanks to everyone working on Scarthgap! It will be a nice image once finished.

But for anyone trying Home builds, I would suggest trying the default branch, develop until Scarthgap matures a bit.

Look in /etc/opkg of receiver files.

@frankviana,

I sent you a link for the two files. Would like to know if it works. Thanks.

Copper coated steel coax is usually made using cheap or inferior materials. The outer jacket of steel cored coax may crack or allow water to be absorbed quicker than coax with a solid copper core. Any coax used for satellite tv should have an outdoor or direct burial rating.
 

Copper coated steel will also corrode and rust in the presence of any moisture. The corrosion or rust  may run down the coax a few millimeters or more. Shown below is an example of a corroded and rusted copper coated steel coax.
 

No one insisted you test these images. Trying to blame the developers will not help your situation. I doubt your receiver is actually bricked as this is not easy to do with enigma2 type receivers. Reloading the image should fix it unless you have a hardware issue. 

Went from this:
< File created on Sunday, December 19, 2021 at 18:59:54 >
< 'DVB-S 11711R / 19998 / 7/8' > Tp# 1
< (1)MBCM />  1:0:1:290:2BD:1001:AE6ADBF:0:0:0:
< (2)ANTEN />  1:0:1:2665:2BD:1001:AE6ADBF:0:0:0:
< (3)SPRT+ />  1:0:1:2666:2BD:1001:AE6ADBF:0:0:0:
< (4)EASY   (Radio #1) />  1:0:2:2669:2BD:1001:AE6ADBF:0:0:0:
< (5)TVPI />  1:0:1:26A5:2BD:1001:AE6ADBF:0:0:0:
< (6)GWFSH />  1:0:1:26D6:2BD:1001:AE6ADBF:0:0:0:
< (7)ETNEW />  1:0:1:26D9:2BD:1001:AE6ADBF:0:0:0:
< (8)ETGLB />  1:0:1:26DA:2BD:1001:AE6ADBF:0:0:0:
< (9)ETDRA />  1:0:1:26DB:2BD:1001:AE6ADBF:0:0:0:
< (10)YOYO />  1:0:1:26E8:2BD:1001:AE6ADBF:0:0:0:

To This:
< File created on Sunday, December 19, 2021 at 19:57:12 >
< 'DVB-S 11711R / 19999 / AUTO' > Tp# 1
< (1)11711V SID 0x290 />  1:0:1:290:2BD:0:AE6ADBF:0:0:0:
< (2)11711V SID 0x2665 />  1:0:1:2665:2BD:0:AE6ADBF:0:0:0:
< (3)11711V SID 0x2666 />  1:0:1:2666:2BD:0:AE6ADBF:0:0:0:
< (4)11711V SID 0x2669   (Radio #1) />  1:0:2:2669:2BD:0:AE6ADBF:0:0:0:
< (5)11711V SID 0x26a5 />  1:0:1:26A5:2BD:0:AE6ADBF:0:0:0:
< (6)11711V SID 0x26d6 />  1:0:1:26D6:2BD:0:AE6ADBF:0:0:0:
< (7)11711V SID 0x26d9 />  1:0:1:26D9:2BD:0:AE6ADBF:0:0:0:
< (8)11711V SID 0x26da />  1:0:1:26DA:2BD:0:AE6ADBF:0:0:0:
< (9)11711V SID 0x26db />  1:0:1:26DB:2BD:0:AE6ADBF:0:0:0:
< (10)11711V SID 0x26e8 />  1:0:1:26E8:2BD:0:AE6ADBF:0:0:0:

 

The attached screencap is the DishNetwork satellite at 118.7w. Yes, a couple of channels lost their names on this satellite when the scan.cpp file was changed today, but who wants to watch this? I say change it since it helps other services that are actually useful.
 

There are about 4 satellite companies in North America. Canada has 2, and the United States has two.
Canada has Shaw, and Bell, with Bell sometimes being called BEV. The United States has DishNetwork and Direct TV. None of these 4 satellite providers uses encryption that can be seen on any fta receiver. In other words, you have to buy their receivers to use their satellite services.
 

In 2006, DishNetwork had a few channels that were open or unencrypted. Today, everything Dish has is encrypted except for a few  DishNetwork channels that advertise DishNetwork.
 

I guess it has been a year or longer since I scanned a DishNetwork satellite with a fta receiver, but I remember the channel names not displaying correctly the last time I scanned them. Several years ago, the channel names would display correctly on enigma2 receivers when a DishNetwork satellite was scanned. The channel names would display along with the epg.
 

If there is a problem the 2006 DishNet "fix" is causing, then IMO, it should be removed because any DishNet fix from 2006 can no longer be used. I will try to setup a DishNetwork satellite later today, and see what the channels scan as. The DishNetrok satellites are circular polarized, and everything else for North America that is fta in the ku band is linear. So I will need to change a lnb and re-aim a satellite dish to check DishNetwork.

Click on one of your links to understand the problem.
 

 

The requested URL /feeds/openpli-8-rc/all/Packages.gz was not found on this server.

The feeds for OpenPLi-8-rc no longer exist as this was a Release Candidate image.

Install the latest OpenPLi-8 here: https://openpli.org/...plus/Duo 4K SE/

The only problems I have with a tone signal meter is being able to hear it, and understanding how much stronger or weaker the signal is compared to how the tone changed.
Signal in db in a consumer fta receiver is not really accurate when compared to commercial equipment, but it is pretty much infinite in most receivers. Signal in db will keep climbing while snr in % stops at 100, which seems to be about 15db.

A picture of my 3.6 meter dish, with his 2.4 meter brother is attached.

Your app rating is done.
I think adding an option to make the audio speak or say the db reading would be nice. OR have the audio say the value in % , then immediately say the value in db. Do not know how well that would sound without trying it, but it is a suggestion.
 

Anyway, the other 10 or 20 apps that I have tried all had the same issue as they all favor the main read more in % than in db, and I cannot remember any of audio apps speaking in db instead of %.  So I think if you could get the audio to speak somehow in db, then your app would have a unique feature! The audio is the only thing I suggest changing or making a setting for as the rest of the displays work fine for me.

I find this app also works for ATSC which is the standard for U.S. terrestrial signals. It takes at least 15 db(snr) for our terrestrial signals to open. and again it would be nice to have an app that has audio in db instead of an app with audio that keeps repeating 100 whilst you climb 10 meters up the tower move the beam antenna several degrees in each direction. 

Very Nice app. Thanks!
My only complaint or comment is it is pretty useless for adjusting a dish precisely on a strong transponder. It would be much better if the signal audio could read in db instead of percent.  100% SNR is 15db on my receiver, and many transponders are stronger than that. The graph stays pegged at 100 percent a lot. Would also help to show db in tenths or hundredths, such as 15.03 db.

Guys, could you please name boxes which have been tested with TBS 5925 and proved to do ACM, VCM, MIS as well as 16APSK and 32APSK.

Thank you.

Add Edision OS Mini to my post# 207. This is a  New receiver for me, and the test results for TBS5925 are the same as my other Vu+ receivers.

Location = United States
Receiver(s) = Vu+ Duo2, Vu+ Zero
ACM = Yes
VCM = Unknown (unable to test)
MIS = Unknown (unable to test)
16APSK = Yes
32APSK = Yes
 

Note:
Cannot find a 32APSK tv channel to test. I would probably need a dish over 5 meters in diameter to get a 32APSK tv channel. 32APSK is confirmed using other sources such as data transponders.