Архив за 15.02.2020

I was given a mobile phone station antenna (870MHz-960MHz). What cool projects can I make with it?

The antenna is the typical rectangular one from a Base Station. What can I use it for?

submitted by /u/pkmpad
[link] [comments]

Using Windows Subsystem For Linux

submitted by /u/sirio2012
[link] [comments]

Can I run 2 LNA’s

I have the rtl l band patch antenna which receives all of the aero band perfectly however it needs to be moved. ive knocked up an extension lead of about 20ft of rg58 coax,and as expected quite a bit of signal loss due to the extension. I have the rtl wideband amplifier so can I use this in conjunction with the inbuilt LNA or would I run into any problems?

Many thanks in advance.

submitted by /u/sirio2012
[link] [comments]

Off-Topic • Re: .NET/Python developer resources

Hello, just though I would make some observations here...
The plug-in manager, I realize, itself is a third-party plug-in. It does not cleanup well.
I designed the Plugin Manager. It does exactly what it is supposed to do. It leaves behind the original DLL files because the plugin manager is designed for (by specific requests from) many users in the SDR# community who wanted the ability to have several different configs for their plugins and load / unload them at will. It is kind of hard to load a plugin if the DLL was deleted. The original beta featured the ability to delete the plugins, but some people ended up corrupting their installs by deleting critical dll files. Everything in the plugin was by purpose.
I've also noticed SDR# does not handle exceptions well

SDR# handles IT'S OWN exceptions properly. It does not, and was not designed to handle exceptions in third party plugins. That is the responsibility of the plugin maker. If you are using the interface properly and implementing your own exception handling in your code this should not be a problem.

You are correct in stating that SDR# will not load a plugin that throws exceptions. This was by design I believe as the interface is proxied (and for good reason).
You can not "Close" your plugin. This call (void) from SDR# through the interface is simply to inform you that SDR# ITSELF is closing and allows you to do finalization and preform unmanaged code clean up. (Release resources....blah blah blah.)

Again, .NET does NOT allow unloading of dynamically loaded assemblies. Therefore if you want to change something in your plugin and view the results you either have to properly configure your debugger and debug it during design time OR you can use your own code to restart the app thereby unloading the assemblies, but remember, someone may have multiple running instances of SDR# so you need to know which instance to close or else your going to end up shutting them all down.

SDR# does not contain any interfaces that contain any void that allow you to restart it. (That I am aware of anyway).

Also, you NEED to program your plugins in C# NOT VB or you will not be able to do anything of more use than tuning the radio and adjusting the bandwidth or preforming simple GUI tasks. Any use of DSP or data processing of the IQ, Audio or RDS streams and the like requires the UNSAFE directive in your compiler which VB WILL NOT allow (See UNMANAGED MEMORY)

THERE IS NO USER REFERENCE for the API for SDR# there are many reasons for this which you can learn through research on this forum and on the Airspy.io forums.

The libraries and interfaces in the API are very self explanatory.

OK, so I will give you a bit of a run down on plugin programming here:

1) Use C#

2) Use C#

3) In your designer, use XCpy to copy your .dll files and .pdb files into the SDR# root directory post build.

4) Configure your build action to launch SDR#.exe after successful compile and the debug session will start with your plugin code once the app starts loading your dll. Then you can step through your own code and see what's up.

5) There is an error log in the SDR# root directory (usually) when SDR# happens to crash with the dirty low down on wwhat caused the crash.

6) The "MagicLine" as it is so called in the "plugin.xml" file is there to point SDR# to the root namespace and entry point of your plugins dll. In order for SDR# to even see it you MUST precede your namespace with SDRSharp. or nothing will work. The "plugin name" attribute is arbitrary but my plugin manager just uses the entry point name of the plugin.

7) Don't forget to code in C#

8)Three dlls are key to designing your own basic plugins for SDR#

They are:

SDRSharp.Common - The ISharpPlugin interface to structure your plugin & the ISharpControl interface to allow to to recieve and send commands and events from / to SDR# for tuning the detectors, changing detectors etc,etc,etc.

SDRSharp.Radio - has many many many interfaces to work with DSP, including demodulators, buffers of all types, the base type for Complex numbers, filters, converters, FTT etc, etc. AND a Utils library used for conversion of types used in SDR# and a common place for all users to store their plugin settings (ie: the SDR# config file). It make your coding much more standard and easier to use.

SDRSharp.PanView - holds the definitions, objects and interfaces for using and creating the Spectrum Analyzers, the Waterfalls and the definitions for the custom events they use.

Just about anything you need to make a plugin for SDR# has been provided for you by the author.

KEY NOTE HERE: There is a unwritten social contract that when you use SDR# and it's associated libraries, one of which is - DO NOT try to circumvent the proxie by using reflection or other nefarious tricks. This is a big 'No No'. ( Among other things.)

AirSpy.io has a lot of great programmers on there that will also help you out if you have a new question just as they do here. Search through all the previous posts. your questions might have already been answered.

By the way, my name is Eddie from SDRPlugins.com. I wrote a lot of plugins for SDR#. With NO knowledge from the start. If you need any direction I can offer my knowledge (as it is - still alot I don't know) to help you out where possible.

No one really helped me and I had to learn everything FROM SCRATCH. Which of course is the most rewarding way ;)

If you review some of my previous posts on here, you will see references to other plugin coders websites with lots of helpful tips. Also, if you look in the downloads section of the AirSpy website, there is a package towards the bottom with 3 plugins in it that - if you open them in your desginer will teach you very quickly how things are done in SDR#. There is an IF Spectrum analyzer (Zoom FFT), The Band Plan plugin and the Noise blanker? (I think).


Have fun.

Statistics: Posted by EddieMac74 — Sat Feb 15, 2020 8:53 am

RTL-SDR Discussion • Re: rtl-sdr drivers: Osmocom daily build

Thank you Slim for Question1.

I have answered myself Question2.
Given win10 64bit and sdr# 32bit
only 32bit "osmocom weekly release" works for me.
(when I copy 64 bit release sdrsharp.exe doesn't start).

(by the way: one should remember also to rename librtlsdr.dll to rtlsdr.dll)


Statistics: Posted by CaptainNemo — Sat Feb 15, 2020 8:41 am

SDR with DMR decode

Is there yet a good way to SDR rcv and decode DMR radio without it being a 400 step process across 6 videos and 8 apps? I have a skywave linux install that has some really nice stuff, and it seems like its really close, but if its there, I'm really missing it.

submitted by /u/RobPatton
[link] [comments]

Off-Topic • Re: .NET/Python developer resources

I think I figured it out. The plug-in manager, I realize, itself is a third-party plug-in. It does not cleanup well. I was wondering why I could get my plug-in to load initially, but not after a few runs (even after reinstalls). This is because despite removing the plug-in, the manager doesn't remove DLLs or the settings. Turns out, my plug-in broke when it would start the REST server at SDR launch (but wouldn't break if I launched it once everything was loaded). So when I reinstalled, the checkbox setting was still there and would try to launch my REST server. Wrote a couple PS scripts to cleanly add/remove plugins and helped a lot.

I've also noticed SDR# does not handle exceptions well. If a plug-in has a problem, it'll throw an unhandled exception. If a plug-in has a problem, SDR# should unload it. Unfortunately, if it doesn't initialize correctly, SDR# still tries to run the Close command as if it's working fine. There's no indication a plug-in is null at startup.

Statistics: Posted by tyler.montney — Sat Feb 15, 2020 4:09 am

Февраль 2020
Пн Вт Ср Чт Пт Сб Вс
« Янв   Мар »