Hello,
No, I am not the author of the SDR# DSD plugin.
73 Eric
No, I am not the author of the SDR# DSD plugin.
73 Eric
The DSD+ program does not control SDR devices. That is done by the FMP and FMPA programs. Those programs get their trunk voice call tuning instructions from the .traffic files that DSD+ 1.101 creates when the -rc (role is control channel monitor) command line option is used. Any developer may create an application that uses the RF channel metadata in the .traffic file names to control a serially controlled scanner.DSDPlus refuses to add functionality to control radios (only SDRs).
Hello,Hi Eric,
I'm kinda running out out options here. Since the DSD variants are not a good choice, DMRdecode Java will not work with serial commands to control the radio, and DSDPlus refuses to add functionality to control radios (only SDRs).
One glimmer of hope though. I recently was added to the CML Microcontroller technical portal with access to the data sheets and more importantly user manuals. Their DMR chip is awesome and would provide all that's needed to fully decode DMR. There is a C program written in LPCXpresso that controls their demo board that is pretty straight forward. The demo board also had the AMBE vocoder chip on board.
The only problem is that the demo board works in the 442 to 450 MHz range, below commercial users. That's not a problem for development because I can use my IF to RF converter (see my digital conversion method article on RR) to allow my ICOM radios with 10.7 RF output a constant 450.000 MHz to the board. But this method would not work with the AOR DV-1because it does not have an accessible IF output.
CML also makes a development board/controller interface that works with discriminator input which would be a better choice. However the DMR chip's function image does not support Limiter Discriminator yet, it's only IQ based right now.
I need to ask CML a few questions to determine which development board to purchase. I will post the project when I have all the equipment.
The DSD+ program does not control SDR devices. That is done by the FMP and FMPA programs. Those programs get their trunk voice call tuning instructions from the .traffic files that DSD+ 1.101 creates when the -rc (role is control channel monitor) command line option is used. Any developer may create an application that uses the RF channel metadata in the .traffic file names to control a serially controlled scanner.
The DSD+ program does not control SDR devices. That is done by the FMP and FMPA programs. Those programs get their trunk voice call tuning instructions from the .traffic files that DSD+ 1.101 creates when the -rc (role is control channel monitor) command line option is used. Any developer may create an application that uses the RF channel metadata in the .traffic file names to control a serially controlled scanner.
Hello,
I do not see how it would improve the situation as you would still need to write the trunking logic that reads the control channel data and controls the radio.
Part of my changes to DSD brings the decoding up to the level of DMRDecode. You could extend DMRDecode as source is available. Both DSD and DMRDecode are designed as data dump viewers so the same program elements are needed to extend them. The data from the control channel needs to be organized into data structures and used by added code to track the state of the trunked system.
It appears this trunking logic is already in DSD+ and it would be easier to write a program like FMP and FMPA that takes the output of DSD+ and sends tune commands to a radio.
73 Eric
The DSD+ program does not control SDR devices. That is done by the FMP and FMPA programs. Those programs get their trunk voice call tuning instructions from the .traffic files that DSD+ 1.101 creates when the -rc (role is control channel monitor) command line option is used. Any developer may create an application that uses the RF channel metadata in the .traffic file names to control a serially controlled scanner.
... and DSDPlus refuses to add functionality to control radios (only SDRs).
According to :
Digital Speech Decoder (software package - The RadioReference Wiki)
and
https://github.com/szechyjs/dsd
v1.6.0 beta for window exe and 1.7.0-dev in source code
If you are referring to DSD+ the the public release is 1p101 and the Fastlane is v2.18
"DSDPlus" sends you the lastest release when you sign up for the Fastlane.
Cheers
The first link you posted does not display anything. I am a windows only person. I did not learn the github or dev source code stuff. I am not referring to DSDPlus, but I do have fastlane 2.18.
I was referring to Windsd that was posted here in this thread back on page 5.
http://forums.radioreference.com/vo...-improvements-i-am-working-5.html#post2250039
I was just on my way to respond to you in the other thread here http://forums.radioreference.com/vo...re/344727-cap-dsd-fastlane-2-18-question.html
I believe you are referring the "original" DSD which is a linux-based program. If you really want to use it on Windows, check out these somewhat complicated install instructions. But just out of curiosity, why do you want to use the original DSD? AFAIK Development stopped years ago, and DSD+ (i.e. fastlane) is far, far, far superior to the original DSD in virtually all material respects. (I believe the original DSD decodes D-Star data, which DSDPlus does not yet decode, but the Audio itself sounds better in DSDPlus)