SDR# SDR# CTCSS and DCS decode plugins

[nj3h]

Greetings,

I have downloaded and installed the latest from The Wraith 2008 (vers (1.3.5.0) for both plugins. I cannot get them to show the appropriate code. I have set the mode to NFM, even though, Hams use WFM (gramted on 10 KHz wide). But still no codes come thru.

I have posted at the Airspy Groups.io page.

Any help will be most appreciated. I am using Win 10, an Airspy R2, and version 1920-Next of SDR#.

Regards,
George

 

[thewraith2008]

... I have set the mode to NFM, even though, Hams use WFM (gramted on 10 KHz wide). But still no codes come thru.

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)

I have posted at the Airspy Groups.io page.

You are unlikely to get help there for the plug-ins I've updated.

... I am using Win 10, an Airspy R2, and version 1920-Next of SDR#.

I can't test this (or any other) plug-in with this '1920 next' version as it just crashes on start. (with no added plug-ins or changes used)
What is the requirement for this SDR# version now?
Recommended version is 1716 but it should work up and including v1919.

 

[TheButcher]

1732 works great.

Any chance of a CTCSS plugin for SDR++ per chance ? Pretty Please ?

Good work by the way

 

[thewraith2008]

Any chance of a CTCSS plugin for SDR++ per chance ? Pretty Please ?

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.

 

[TheButcher]

Interesting. I am not a programmer.

SDR++ is pretty good. Quiet a bit faster than SDR#. It is basically very similar to SDR#.

I am trying to migrate to SDR++ entirely, but I miss the fact that SDR++ does not have CTCSS decoding capability. SDR++ has "Band Plan" capability, which is really cool. Rig Control is also wicked. SDR# has a plugin for that (to be used in conjunction with DSD-FME. And supports the TCP "Audio Sink" (passes audio over TCP to DSD-FME).

It works great on Ubuntu too.

Anyhow, love your work...

 

[nj3h]

Greetings,

I do not get any software crashes using the latest DCS and CTCSS plugins with versions 1919 and 1920 of SDR#. However, with 1920, I get no codes appearing in the plugin. 1919 seems fine.

So I tried KG-Tone, which is over a decade old. 1919 works fine with KG-Tone. However, KG-Tone will not work with version 1920.

I have the same settings in 1919 as I have in 1920. So there must be a reason, unknown to me, why I am having an issue with 1920 decoding tones.

Any and all ideas are welcome.

Regards,
George

 

[thewraith2008]

I have the same settings in 1919 as I have in 1920. So there must be a reason, unknown to me, why I am having an issue with 1920 decoding tones.

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 development.

Any and all ideas are welcome.

Just use a SDR# version that is known to work with the plug-ins you want to use.

 

[TheButcher]

"I'm not willing to invest time to get plug-ins working for a version that has no roadmap for future development."

SDR++ seems promising. A young fellow is developing the project. And I am liking his software ! I have used and enjoyed SDR# for years, but I feel that SDR++ is the stronger of the two.

To me it's plugins that make these programs useful. Bandplan and CTCSS Decoder.

Now if DSD+ FL used Rig Control and TCP Audio Sink to work with SDR++ or SDR#, I'd be very happy !

Shame SDR++ uses a foreign language to you mr. thewraith2008 and shame that SDR++ doesn't have any/much documentation for plugin development. SDR++ uses good interface for adding plugins IMHO. Check it out. Plonk .dll into plugins directory and it shows in the UI. From the UI, plugins can be enabled / disabled. Very nice...


ps. I am using SDR# 1.0.0.1732 with CTCSS plugin version 1.3.5.0 just fine...

 

[thewraith2008]

SDR++ did look OK but I forget if I liked it or not when I tried it.

One thing that is a deal breaker for me using these other SDR programs apart from lack of plug-ins or similar (built-in) features is the simple process of tuning the frequency. SDR# has the best and most intuitive way of doing this.
At least now days we are spoiled for choice with all these available SDR programs.

With SDR++, I kind of get the impression that one person is trying to add all these popular features/plug-ins/modules themselves.
This has resulted in a lot of partly implemented features or slow development of them.
With SDR# plug-ins, some of these have taken many years to grow in to what they are now. That's a lot of work/time for one person.