DSD+ and Tier 3 systems

pro92b

Mutated Member
Premium Subscriber
Joined
Jun 27, 2002
Messages
1,961
seagravebuff60 - One final bit of info on 2.448 the first version. The East Mountain site ID format L13-x.x is displayed with Airspy and discriminator tap inputs. However when I used a RTL-SDR V3 I got the message about blocking the switch to L13 and the sites ID as L12-x. So DSD+ erroneously handles the inputs differently depending on what the signal source is. All the testing with new virgin installations had no bearing on the issue.

scottjpalmer - I'd love for there to be a communications link from the author so we know what's going on. It can be indirect but needs to be semi-official so we know it isn't just someone's possibly uninformed opinion.
 

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
16,097
Location
BEE00
seagravebuff60 - One final bit of info on 2.448 the first version. The East Mountain site ID format L13-x.x is displayed with Airspy and discriminator tap inputs. However when I used a RTL-SDR V3 I got the message about blocking the switch to L13 and the sites ID as L12-x. So DSD+ erroneously handles the inputs differently depending on what the signal source is. All the testing with new virgin installations had no bearing on the issue.
I realize this whole thing with DSD+ is in flux/turmoil, however one thing @seagravebuff60 and I discovered earlier is that the results vary depending on whether you have DSD+ set to CC Monitor (1 of 2) vs Combined CC/VC Monitor. The "Blocking network ID change" messages seems to show up only when in Combined CC/VC Monitor mode for whatever reason, so try switching to CC Monitor (1 of 2) instead, see if that makes a difference.
 

scottjpalmer

Member
Joined
May 4, 2020
Messages
48
seagravebuff60 - One final bit of info on 2.448 the first version. The East Mountain site ID format L13-x.x is displayed with Airspy and discriminator tap inputs. However when I used a RTL-SDR V3 I got the message about blocking the switch to L13 and the sites ID as L12-x. So DSD+ erroneously handles the inputs differently depending on what the signal source is. All the testing with new virgin installations had no bearing on the issue.

scottjpalmer - I'd love for there to be a communications link from the author so we know what's going on. It can be indirect but needs to be semi-official so we know it isn't just someone's possibly uninformed opinion.
I hear where you're coming from, I guess you'll just have to take my word for it that the author said to me in an email that they know 2.448 is broken and that they're working on fixing it.
 

seagravebuff60

Short Bus Reject
Feed Provider
Joined
Jun 11, 2016
Messages
1,076
Location
New York State
I think that the 2 versions of 2.448 and the conflicting System ID and Sites are just adding to the confusion (for me to handle at least). I'm just going to wait to see if it's fixed in a future update. It's not worth my time anymore.

The complete lack of support and or communication from the DSD+ author is ridiculous. If you "Sell" a product/software at least support it.
 

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
16,097
Location
BEE00
Some examples of how to deal with the new changes in 2.457...


 
Top