Disclaimer:

"SDRgadgets is independently maintained and not officially affiliated with FlexRadio Systems or its employees.  The content and information provided are that of the respective author(s) and contributors."

 

Who else, would like an SDRgadgets V2.0 refresh?

I'm willing, if I can gets some help, and feedback. The content has gone stale, and the more help I can get, the faster it will get freshened.

Would You Like to Help?

SDRgadgets content is created by it's users. The content seen in the wiki portion of SDRgadgets is always in need of updates, corrections, and new content additions.

SDRgadgets would appreciate any help you can provide.

How to contact me, NO5J:

To contact me privately, email is probably best, My Inbox get's more attention than anything else. My address is good on QRZ.

you could also use my sdrgadgets.com, address by prepending my callsign to @sdrgadgets.com. Both aliases send mail to the same account inbox.

What we are about: 

Welcome. SDR (Software Defined Radio) technology continues to forge ahead, often faster than it's being documented. With such a moving target it's still important that it does get documented. and that then those documents get updated so that they keep up with the latest changes. Relying on PDF files you found online often results in old, or incomplete information.SDRgadgets aims to be a "Live" source of information. To achieve "Live" we need "You", as many of "You" as possible. We are trying to provide an easy to manage, easy to learn, framework, of the tools needed to document the state of the art and the bleeding edge. Why wait for some unnamed "other" to get around to creating and publishing another outdated website or PDF file, that you need right now? As we work our way thru all the changes in the technology, we figure out how it works by doing "it" much of the time. SDRgadgets is just asking that you do the next step, As soon as you discover how something works, take a stab at explaining it to the rest of us, write your discoveries up, and write them up here.  When you've done that, link to "it", instead of linking another old PDF, Live should work better than PDF. you might end up typing less too.

As a member of the Flexradio Community, this website is yours, feel free to post your information or any other articles of interest to other Flexradio or SDR users.

Think, Peer created, Peer edited, Peer published, Peer reviewed, Peer maintained. Peer owned. Join the team!, Be the solution!, You know you can do your part!, All you need is time. Find some. We're waiting!

Posting of articles:

On the wiki, nothing is too short, or too trivial, post it, type it just once, then use it by linking to it within your posts in the Community and elsewhere.

If you have content that just can't be wikified, ask and we will set you up with your own named category on the Joomla front end where you can create blog-like articles. This blog-like content will still need to conform to all of the other SDRgadgets content rules.

Please continue to grow SDRgadgets.

As the collection grows, we encourage everyone to participate by taking the time to correct, whatever needs correcting and also to continue contributing new content.

#SDRgadgets IRC is on Freenode.

For the discussion of SDRgadgets, and SDRgadgets member support, we can always be found in #SDRgadgets on chat.freenode.net using your IRC client of choice.

IRC discussions can be done in real-time. 

As you might suspect, we can also be found in #FlexRadio on Freenode. Let's keep the SDRgadgets topics in #SDRgadgets as much as possible.

SDRgadgets Wiki is online.

I upgraded MediaWiki to the latest stable LTS version 1.27.

I changed the default skin to foreground, which in my opinion provides a better look and simpler operation. There are still other skins installed, which you can switch to in your user preferences.

Just smile and think ... He must be working on it again!

So pardon the dust!

Watch us Evolve!

We have installed Mediawiki on SDRgadgets (Actually, the wiki came first, the Joomla frontend was added a few days later to provide a more familiar looking landing page, to avoid scaring people off.) To provide users with a better way to document what needs documenting. Using the wiki you can create How-To articles, or any other form of useful content, that will never go stale or obsolete and also be able to store the articles categorized in a way that makes sense. Also, the wiki will allow the article contents to be searchable, so when you don't know where you should look try the wiki's Search feature, or just Browse around till you find the answers your after. Still, can't find something? Maybe it's because we don't have your content. When you do figure out, or find what you're looking for, the wiki is the ideal place to document what you've learned and help out others in the Community too. Any registered user can edit the wiki.

Think you've found an error in a Wiki article, then before you forget about it, do a little editing and fix it, if you have the time. The wiki has a revision control system built in, so if something's messed up we should be able to back out of any messes, SDRGadgets is yours, make it shine. The wiki will also let several authors easily collaborate on an article. It's not much harder to edit than typing a post in the Community!   You can add Images, Sounds, and Videos to articles on the Wiki. If we build it, they will come! I know I've heard that phrase somewhere.  

I've taken additional steps to protect your contributions, the entire server is now being backed up hourly. All of SDRgadgets should now be restore-able. Your content will have persistence. SDRgadgets can keep improving.

 About: SSL

Website SSL certificates are expensive. Therefore, they are really not in our budget. Our previous SSL certificate expired a while ago, but because it was only really needed to provide an encrypted connection for our user's to log in with, and because very few users have registered an account, and also because we are sharing all of our content with the world (we have no secrets except for user's passwords), there hasn't been any pressing need to fix the expired certificate issue.

In our situation the roles are reversed, the SSL encryption protects SDRgadgets from hackers trying to steal our user's passwords, in order to cause SDRgadgets harm. All of the other information our server exchanges with a user's web browser is open source licensed and intended to be shared with everyone. So we really only have that one secret that needs protecting.Never the less I'm working on fixing the problem.

I'd prefer to not have to go the Self-Signed Certificate route. Which we were using in the past. I don't want our user's web browsers popping open "hazardous warnings" when they log in, and then having to override the warnings by accepting our Self-Signed certificate, anymore.

 So I'm working on it.

 Update 08/23/16:

Yesterday ...

I created another Self-Signed certificate so that https:// connection would at least encrypt, even though the connection will be flagged as unsafe by every web browser currently available. If you create an exception for the Self-Signed certificate, SSL encrypt the connection. But that's just not going to be good enough.

Then Today ...

I discovered the existence of Let's Encrypt, a certificate authority that launched on April 12, 2016 that provides free X.509 certificates for Transport Layer Security (TLS) encryption via an automated process designed to eliminate the current complex process of manual creation, validation, signing, installation, and renewal of certificates for secure websites.

It sound's like Let's Encrypt, might be just what I need. So I'm muddling my way thru the Installation and setup of the Let's Encrypt client software, Then I'll muddle my way thru getting an SSL certificate for SDRgadgets, thru them.

I hope this pans out!

Either it's a buggy client or I've got something misconfigured (usually I've got something misconfigured), So ... I'll keep working on it until I know how to make it work (usually possible, sometimes takes a while) but it's a plan! I better get busy! meanwhile, the Self-Signed certificate can keep things encrypted for those that want encryption (I do). 

Update 09/02/16:

I finally got the Let's Encrypt SSL certificates working and have set the Joomla front end to force SSL connections.

I'll try to force SSL connections for the entire SDRgadgets.com domain now.

Hopefully, I won't break things, time, and testing will tell I guess!

Try using https:// URLs for every connection, that's where I'm headed with this.

The Let's Encrypt certificates, do have to be renewed every 90 days, What would you expect for free? I guess I've got 90 days to figure out how to automate the renewals. I don't mind the extra work involved when it's FREE.

Update 09/03/16:

I remembered (finally), that in order for SDRgadgets members to be able to use SSL connections to our websites, that I had forgotten to open up the firewall for SSL, That's fixed now!

Update 12/11/16

Ok the first Lets Encrypt certificate auto-renewal didn't!

Please pardon my dust!

This ought to be fixable. 

Update 12/24/16

The SSL certificates for all the projects on Sdrgadgets have all been renewed. SSL should be working for everyone again.

These Certificates are normally good for 90 days, I'm hoping to set the server up, to automatically renew them every 60 days. The most recent auto renewal failed which is why SSL was broken. So when it breaks again in @90 days, the next auto-renewal failed too. But I've got the calendar marked for the renewal date, so hopefully, that won't be an issue.

Update 03/17/2017

As you may have expected, I forgot all about the SSL certificate expiration, and again the auto-renewal failed. Manually renewal worked and everything should now be working. I won't be speculating about the next renewal, I'll try harder though. 

Update 06/01/2017

Success at last! After another failure at auto-renewal, and with another SSL certificate expiration due in @15 days, I decided to tackle rewriting my renewal script from scratch, now it works! I created a monthly cronjob for it. If the next renewal succeeds in a month then The SSL issues should all be solved. 

 Login Module Fixes

I've been playing around with the websites Login module, there are actually two of them, the default Joomla login and the Slogin Social Login. Slogin is being used to provide the Google+, and Facebook one click logins, but we also need the regular Username/Password style login if something goes wrong with the Social Logins. Slogin has a built in Username/Password option Which you may have been looking at for a few weeks, but it's clunky and nearly impossible to modify, so I have it disabled currently. I re-enabled the Joomla default login module. Which cause the redundant Logout buttons in the upper region of the front page. Either button can be used to Logout, they perform the exact same thing. Meanwhile, I'll continue Googling for hints on how to remove the extra button. Still, I think the extra log out button looks better than the forced User(linefeed)name, Pass(linefeed)word, label appearance of Slogins built in.  By the way, Facebook and Twitter logins have been re-enabled for the Joomla front end.

06/30/2018

Yeah the Slogin, Google logins are broken currently, it's a complicated setup, and I haven't figured out what the problem is.

But I'm going to try and fix it. In the meantime as always contact me for any login issues, such as lost passwords.

07/03/2018

The Google login works intermittently, which isn't helping the troubleshooting any.

07/04/2018

I've added a user editable article, and linked it to the top of the User Menu "SDRgadgets Links" I'm hoping it gets used.

I'd prefer to keep the links as bullet points, styling until someone comes up with a better idea.