Search results

This SDR# 'next' v1920 is a experimental version. What changes that have been done are not documented so who knows why things are not working, let alone what will be needed to rectify them. I'm not willing to invest time to get plug-ins working for a version that has no roadmap for future...

I don't use SDR++ but I didn't find any information about a plug-in API. SDR++ is programmed in C++ and I've not really done much in the way of learning it.

SDR# should be set to NFM. For NFM, there can be: Narrow @ 12.5 kHz - ~2.5 kHz deviation Wide 25 kHz - ~5 kHz deviation (I think HAMs may use 6 kHz) You are unlikely to get help there for the plug-ins I've updated. I can't test this (or any other) plug-in with this '1920 next' version as it...

The above applies to SDR# at least up to and including v1716. The above does not apply to newer versions of SDR# which now makes the squelch available in WFM. I'm not sure exactly when that changed.

OK, I can see what's happening. In your right image (88.5), you have not enabled the Squelch (the left checkbox) which is used to update the Squelch enable and Squelch threshold settings in SDR#. So you need to set the Squelch enable=Unchecked. When Squelch is not set, then the squelch will...

When WFM is selected in SDR#, the squelch checkbox and threshold value are disabled. This is because of SDR# and not related to the plug-in. I guess the thinking is that broadcast FM stations are continuous therefore the squelch is not needed to be available.

SDR# minimal version was experimental. This version no longer exists, it is now "sdrsharp-x86-next" I did upload a fix (v1.4.5.0) for the issue with the buttons but looks like I wasted my time (again) .

When you add a frequency to the database, you should have already set the Mode(detectorType)=WFM and Bandwidth=192KHz in SDR#. This will then store these settings for that entry that can be recalled when you double click it. Alternative to deleting and creating a new entry, you could manually...

You will find that change available in the latest download. Latest version (v1.1.2.5) can be found in this post here: Download

It is when a value, algorithm and answer are provided in video (and GitHub for the algorithm). Example: value = 5 algorithm - lets just say this is just to double the value (value * 2 ) answer = 10 But when you do their way, it doesn't work and you get: 2*10=55. You should be able to...

Has anyone really looked into what has been presented in this demonstration video? This video is 'showing' what is needed to make a ESI (the encrypted SSI) into a true SSI. (TA61) It claims at least three known ESI/SSI pairs can be used to generate the SCK/CCK which then can be used for further...

OK, I see where the elements in question are now. These four sub elements come under the 'Cell re-select parameters' in the D_NWRK_BROADCAST PDU. The plug-in does decode the 'Cell re-select parameters' (and also the 'Cell load CA') but does not break them down and display them in the 'Neighbour...

In what PDU are they transported? This are probably calculated and based on values that are already shown in the Network Info > Current/Neighbour cell tabs. see: MS_TXPwr_Max_Cell, RXLevel_Access_Min, Access_Parameter Funny how people always think that. Latest version (v1.8.9.0) can be...

The plug-ins will either work or they won't. I won't chase the development of SDR# again like I did when the Telerik version came about. SDR# has not seen a real stable version since v1716. Almost everything (UI related) after was just horrible and buggy/clunky. Now just when it was settling...

Seems both plug-ins are determining the same thing. The frequency is new/unknown. Maybe try using the latest versions of Frequency Manager v1.1.9.0 and Frequency Scanner v2.4.3.0 plug-ins. Beyond that, nothing else comes to mind as to what else it could be. Latest version (v1.1.9.0) can be...

Check that the saved entries frequency (in the Frequency Manager) exactly matches what the VFO is landing on when scanning stops. As a side note, if any entries are added or modified in the Frequency Manager while the Frequency Scanner or Audio Recorder is running, you will need to stop/start...

Testing your zipped up folder of SDR#: The no connection issue seems to be because of the empty (and invalid) 'Sampling Mode' field for the RTLSDR dongle. This should be 'Quadrature sampling'. Not sure how it became invalid for you. Apart from that, the SDR# sound is heard as expected with no...

I still stand by what I said about the DCS plug-in not causing this. In any case, if you are willing, archive/zip up your SDR# folder and post it to a file hosting site (like MEGA) and send me the link in a PM. Make sure the issue is occurring in that version of SDR# before you zip up and send...

If the DCS plug-in is causing a 'no audio' condition, it's because the code 'Squelch' is enabled in DCS panel. This would still be the case even if the 'Detect' is not checked. You will see a 'Mute' to right of the squelch set DCS code value. CTCSS & DCS Decoder plug-ins: Latest version...

Where did all these plug-ins come from? Are they the ones I have updated? If you installed plug-ins from the SDR# Community Installer, then I can't help you as these are the out dated versions of the SDR# plug-ins. If you are using my latest version (v1.3.5.0), I don't know why it doesn't work...