Welcome to GOFASTMOTORSPORTS.com ... ... ... Green Flag - Green Flag - Go Go Go ... ... Brought to you by Ricks Satellite - Where the Big Dish Rules!

Ricks Satellite Wildfeed and Backhaul Forum
Register Latest Topics
 
 
 


Reply
  Author   Comment   Page 2 of 4      Prev   1   2   3   4   Next
majortom

Avatar / Picture

Registered:
Posts: 4,836
Reply with quote  #16 
For SNR you don't want a Percentage, it's meaningless..
you as an engineer or technician ya wanna see snr in decibels, not a percentage..
Else I think your little project would be a wasted effort, actually taking a step backwards.
Post an example what ya got, maybe we can help sort it out.
would also help to know what drivers you are using..


__________________
Perfect 10 7.5' mesh Chapparal C/Ku Co-Rotor feed, Norsat 8115 CBAND, Norsat 4106A Ku Thomson Saginaw Actuator, Vbox positioner,
Home Brew Polarotor683 Servo circuit. Openbox S9, Prof7500, v4l-updatelee linux drivers installed.
merkin

Registered:
Posts: 716
Reply with quote  #17 
i agree with @majortom
in order to show dB correctly as a percentage you would need to determine the modulation and fec of the acquired signal.  
if not you could have a SNR reading from a 8psk 9/10 signal look the same as 8psk 2/3 when in reality the link margin for the former could be just a fraction of the latter.
iz5rng

Registered:
Posts: 33
Reply with quote  #18 
Hello, thanks for replies, I did some improvements this week end and now my device appears in the following video.

https://drive.google.com/open?id=0ByM0VPEX6PH_ZllRUVJjT2Y5SHM

After the first nag screen it asks for frequency polarization and symbol rate.
I assume for the moment universal lnb only by default.
Then asks for confirmation and tune the selected trasponder.
I get level signal and snr.

I used Darksky ready made distribution for my raspy and updatelee tune-s2 application cloned via git.

Then I simply added lcd and buttons controls.

For tuning I call repeatly the inside function check_frontend...but I don't know if this is the right method.

I don't know if it's possible to share google drive links.
If not I ask the administrator  to delete the link immediately.

As told I am not a programmer, I am just and hobbiest...so please be kind with me :-) :-)
Any suggestion is very appreciated.
Thank you.
Max.

DarkSky

Registered:
Posts: 2,241
Reply with quote  #19 
Max:

Good job! Looks like your project is shaping up nicely. It looks to me you have snr of 5403.3. I do not know if it is a decimal point issue or not (5.4? But 54.0 seems a little stout). Another thought is, are you accidently still dealing with % with the snr some how accidently.

I tested here with UDL's tune-s2 and majortom's fork on his bitbucket (which I use) and it appears majortom's fork is more up to date with the DVB-5 specs with the snr than UDL's.

project.png 

Majortom's fork:

mt.png 

UDL:

udl.png 

Here is where I get confused being I am the last person in the world to give advice on programming and my knowledge involving different dvb devices and how they work are next to nothing but majortoms mods to align things with dvb5 specs seem to be moving the decimal point with the snr a different direction where you need to be going.

mt-mods.png 
Hopefully majortom or some one else smarter than me will be able to help you with your coding.

Again; Nice job it looks like you are almost there with your project.

FYI:

I do not know what image you are using of mine but I have been including majortom's fork of tune-s2 with the image for a while now. It is in the system path if you want to test it and see what it reports if you have not over written it with UDL's. It was in /usr/local/bin.

Ray

iz5rng

Registered:
Posts: 33
Reply with quote  #20 
Hello Darksky, thank you for your help!
Yes...those values are strange...but if I run tune-s2 from /usr/local/bin from your "distro" they are strange too...
I am using this distro you suggested me in this post

https://rickcaylor.websitetoolbox.com/post/show_single_post?pid=1293203293&postcount=90&forum=106995

Everything works perfectly at the first time with my skystar HD usb and with this old model.

I attach a screenshot from my raspy running your tune-s2.
Maybe something don't go well with my skystar device?
I really don't know.

For my lcd application I simply git cloned the updatelee repo with this:
git clone https://bitbucket.org/updatelee/tune-s2.git

By the way I am very happy I made something that is quite working although it still have some issue.
Thank you for help.
Massimo.

Attached Images
Click image for larger version - Name: Istantanea - 03042017 - 23%3A00%3A11.png, Views: 10, Size: 64.89 KB 

DarkSky

Registered:
Posts: 2,241
Reply with quote  #21 
Quote:
Originally Posted by iz5rng
Hello Darksky, thank you for your help!
Yes...those values are strange...but if I run tune-s2 from /usr/local/bin from your "distro" they are strange too...
I am using this distro you suggested me in this post

https://rickcaylor.websitetoolbox.com/post/show_single_post?pid=1293203293&postcount=90&forum=106995

Everything works perfectly at the first time with my skystar HD usb and with this old model.

I attach a screenshot from my raspy running your tune-s2.
Maybe something don't go well with my skystar device?
I really don't know.

For my lcd application I simply git cloned the updatelee repo with this:
git clone https://bitbucket.org/updatelee/tune-s2.git


Well that image is a little old (kernel 4.6) but area21 says he had found that his skystar stoped working after @ kernel 4.6. I believe you do not have his exact model though. The last image posted had kernel 4.9 and is upgradeable to the current 4.11.0-rc2 kernel. With that said it does seem to me that it could be some issue with your device looking at your last attachment using majortom's fork of tune-s2. Majortom probably has more insight on the matter.

Majortom and I run into some issues with his pi 2 trying to upgrade the kernel 4.6 and it took us a while to figure out what the problem was. Basically the bootcode and some other files in the /boot partition had to be upgraded before it would boot.

So a lot of water has gone under the bridge since kernel 4.6 and v4l/linux may or may not made improvements on your paticular skystar (could even be worse). If you have an extra sdcard you could install the image with the 4.9 kernel and see if things are better with the tune-s2 in that image:

https://drive.google.com/file/d/0B-hVZ4SWSiuKUFM0WVlqMWFSUHc/view?usp=sharing

This image will boot the pi's 1, 2 or 3 automatically and has the new raspberry pi PIXEL desktop and if all is good with your skystar you can upgrade to the current kernel 4.11.0-rc2.

Ray
majortom

Avatar / Picture

Registered:
Posts: 4,836
Reply with quote  #22 
From your tune-s2 printout, your device uses an stv0299 frontend.
I doubt anyone has modified that driver in years.
The easy thing to do is to go back to printing out percentages and call it a day.

But if it was me, I would at least try and play around with this function in stv0299.c to
see if there is a way to have it output snr values in dB instead of the legacy
"cooked" values. But I don't have any devices using that. Nor am I a programmer either.
Would likely require some test equipment, and the datasheet for the device to really sort
out what it is doing though.

Here is what I think is the function of interest in the frontend driver, stv0299.c that would need rewriting.

Code:

static int stv0299_read_snr(struct dvb_frontend* fe, u16* snr)
{
        struct stv0299_state* state = fe->demodulator_priv;
        s32 xsnr = 0xffff - ((stv0299_readreg (state, 0x24) << 8)
                           | stv0299_readreg (state, 0x25));
        xsnr = 3 * (xsnr - 0xa100);
        *snr = (xsnr > 0xffff) ? 0xffff : (xsnr < 0) ? 0 : xsnr;
        return 0;
}


__________________
Perfect 10 7.5' mesh Chapparal C/Ku Co-Rotor feed, Norsat 8115 CBAND, Norsat 4106A Ku Thomson Saginaw Actuator, Vbox positioner,
Home Brew Polarotor683 Servo circuit. Openbox S9, Prof7500, v4l-updatelee linux drivers installed.
iz5rng

Registered:
Posts: 33
Reply with quote  #23 
"Call it a day" took me some google search for meaning ahahahaha [biggrin][biggrin]
But at the end i think it's the preferred way, I really don't feel so good putting my hands inside drivers....

...a really stupid question: to burn Darksky image to my sdd I must decompress it using bz2 then dd the tar files to sdd. Is it right?
Thank you.

DarkSky

Registered:
Posts: 2,241
Reply with quote  #24 
Quote:
Originally Posted by iz5rng
...a really stupid question: to burn Darksky image to my sdd I must decompress it using bz2 then dd the tar files to sdd. Is it right?
Thank you.


"Call it a day" pretty well "hits the nail on the head" does it not? (now google that)
I bet in Italy you have metaphors we have not heard either. Just having some fun........

This should normally do it:

tar -xvf rpi-arch-pi-2-3-490.tar.bz2

Then write rpi-arch-pi-2-3-490.img to a sdcard as with the normal raspberry pi image procedure using dd. If you burn it to a micro sdcard then you will have the capability to use the same card to boot up the pi 1 (with sdcard adapter) and the pi's 2/3. The card will be interchangeable although the speed of the rpi is pretty much useless for running heavy programs it does stream good over the lan using updateDVB.

If all still is good after testing with your skystar device then we can upgrade the kernel to 4.11.0-rc2. Let me know how it turns out with kernel 4.9.

Ray
iz5rng

Registered:
Posts: 33
Reply with quote  #25 
Quote:

"Call it a day" pretty well "hits the nail on the head" does it not? (now google that)
I bet in Italy you have metaphors we have not heard either. Just having some fun........


Great Darksky!! I never imagine it will say "be exactly right" ahahah very nice!!
Maybe in the next conversation I'll try to use this metaphor! I surely will impress my colleagues! ahahahah

Back to our discussion I just tried your image on my raspi and got the same result.
Skystar is correctly identified and can tune a trasponder but snr is still in numeric no sense format.
I attach a screenshot below.
So...what do you and @Majortom suggest? What could be the easyest solution to get it working?
Thank you
Max.
Screenshot at 2017-01-17 00-49-05.png 

DarkSky

Registered:
Posts: 2,241
Reply with quote  #26 
With what majortom said above with no one changing the code for the driver in years; it probably means they will not for what ever reason. So if all else is good with the device and locks and plays video you could "Just call it a day" and enjoy it and as a country boy would say here "In my neck of the woods" "If it ain't broke, don't fix it". Have some more fun with google..... lol
DarkSky

Registered:
Posts: 2,241
Reply with quote  #27 
Max:

I just discoverd that in the link above I posted the link for my arch linux image for the pi by mistake so if you clicked on that link you are running arch linux instead of the Raspberry Pi Pixel image.

Unless you want to learn some new commands here is the link to the PIXEL image:

https://drive.google.com/file/d/0B-hVZ4SWSiuKdjdwVFNjbGY0T3M/view?usp=sharing

I am truly sorry for the mistake.

Here are some pics of the 2 desktops. The kernels are the same; just different distros and desktop enviorments.

Ray

Attached Images
Click image for larger version - Name: pixel-desktop.jpe, Views: 5, Size: 287.79 KB  Click image for larger version - Name: arch-desktop.png, Views: 5, Size: 103.71 KB 

area21

Registered:
Posts: 76
Reply with quote  #28 

For my Official Raspbian Pixel image, kernel v4.4.50-v7+
Technisat Skystar USB HD
Crazycat tune-s2

Signal and snr aren't correct either  [smile]

Note : i run tune-s2 from inside tune-s2 folder as in screenshot.

@Darksky, regarding that USB device, it works with all kernels however the problem is after kernel v4.4.50 red light(power) and green light(signal) are flashing on and off simultaneously after i kill VDR or tune-s2 or whatever other application.

Attached Images
Click image for larger version - Name: tune-s2.png, Views: 11, Size: 97.93 KB 

iz5rng

Registered:
Posts: 33
Reply with quote  #29 
Quote:
For my Official Raspbian Pixel image, kernel v4.4.50-v7+
Technisat Skystar USB HD
Crazycat tune-s2


A little off topic, sorry.

Area21, is this the device you have?
If yes we need to share some information for use with linux.

300px-TechniSat_SkyStar_USB_HD.jpg 

iz5rng

Registered:
Posts: 33
Reply with quote  #30 
Googleing around I found two interesting points:
1) UpdateLee wrote on this forum some years ago about our snr problem and at the end there is a patch.
https://patchwork.kernel.org/patch/2653281/
Maybe it's possible to recover something.... The patch is for femon the "official" app but if it works I can also mind to switch to it.

2) The strange snr number is not strange at all. Infact it's the decimal representation, if converted to hex it become very interesting.
In femon documentation I see snr can vary from 0x0000 to 0xffff so it's possible to have percentage displayed. It's not "professional" as db showing but....it's a way to "call it a day".

Max.
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Fellow Members, your posts are welcome here! Do not worry about posting everything perfect. Different receivers and LNB's will give you different Frequencies and Symbol Rates. Some set top boxes, PCI cards and USB receivers, Do Not Require all of the same information that others may need. It is not Required to post everything that others may need to tune in a feed. It is just most important to share the find. We can always adjust the Frequency and Symbol Rates and try the various Modulations and FEC's on our own receivers until we get a lock and then give a polite reply with what works for your receiver, as that information might help others as well. We all appreciate the efforts and energy of the Posters!

Thank You for Visiting GOFASTMOTORSPORTS.com - Keep Your Eyes on the Sky and the Track!