Here is what works for me:Is there a way to save that help file as a .txt? This doesn't work:
dsd-fme.exe -h >Help.txt
Code:
dsd-fme -h > help.txt 2>&1
Here is what works for me:Is there a way to save that help file as a .txt? This doesn't work:
dsd-fme.exe -h >Help.txt
dsd-fme -h > help.txt 2>&1
GREAT ! thanks !It was purely a display bug where the last packed octet was printed but not collected properly, thus the random value in it. I honestly hadn't noticed because I never bother looking at that bit. Regardless, the bug has been fixed, its been pushed to the aw_dev branch for now pending further testing. Further testing by somebody else, won't be me.
The bug only affected the printed AMBE value, it didn't affect the bit array ambe_d, where the 49-bit decoded voice frame is usually held, nor did it in any way impact the late entry MI/IV value held by the ambe frame, that MI extraction process is carried out separately from the mbe voice portion, and has both Golay applied to it and a CRC check.
If you are getting late entry errors often, then it means that for one thing, you aren't getting the initial link control headers nor the PI header, and it probably means that you are also having tons of reception errors if it is often bad or having to assert itself over the current internal LFSR generated MI/IV value. If you are getting tons of decode errors, then you should look at either cleaning up your signal into DSD-FME, or there is some interference on that channel, or the signal is just too weak, or maybe even too strong if its nearby to you.
Another thing to keep in mind is that if that system is also TXI enabled, the late entry key/alg has to compete for time with the TXI information, so its possible that on super short talk spurts with TXI enabled, and encryption enabled, if you miss the PI header, or have bad signal, it may have to wait multiple superframes, and by that time, the call could very well be over. Using the -0 and/or -3 option may be required to both disable the late entry alg/key and also force it to attempt RC4 decryption at all times, but it can only use one key value if you go that route, no key loading.
How do we make the screen stop scrolling like mad?
And how do we tell it to tune SDR++ to a new frequency for trunking? I have a 2-channel Cap+ system in a .csv, but SDR++ always stay on one frequency.
When I do get a voice call, no audio comes through.
I just wanted to pop by and say thanks for all your hard work on this over the years. Your contribution of dsd-fme to the hobbyist community is very much appreciated by myself, an I expect very many others.Alright guys, sorry I haven't been on lately... I'm just a bit burned out and have realized that I'd like to spend my free time doing other things. I've also realized, that I think I've taken the original DSD source code as far as I can take it in its current form, and just jamming more and more things into it isn't going to help much or 'make it better' at this point.
Post your command line and .csv file contents. Then we will cross the no audio bridge once we get the other straightened out.How do we make the screen stop scrolling like mad?
And how do we tell it to tune SDR++ to a new frequency for trunking? I have a 2-channel Cap+ system in a .csv, but SDR++ always stay on one frequency.
When I do get a voice call, no audio comes through.
dsd-fme.exe -fs -F -i tcp -C capacity_plus_chan.csv -T -N
A couple of things, I would try without the "-F" unless it really needs it.Ok, sorry. This is what I'm running:
dsd-fme.exe -fs -F -i tcp -C capacity_plus_chan.csv -T -N
dsd-fme.exe -fs -F -i tcp -U 4532 -C capacity_plus_chan.csv -T -N 2> log.ans
Your .csv file may have extra crap from excel, causing DSD-FME to not recognize the intended content. Edit with a text editor like notepad. It should look like this:The .csv is as follows:
ChannelNumber(dec),frequency(Hz) (do not delete this line or won't import properly)
1,463600000
2,463600000
3,463950000
4,463950000
5,464162500
6,464162500
dsd-fme.exe -fs -F -i tcp -U 4532 -C capacity_plus_chan.csv -T -N 2> log.ans
-t 2
if on a Cap+ system, sometimes those short beacon bursts don't trigger fast enough, so we need to tell DSD-FME to increase the hangtime to 2 seconds before hunting for a new rest channel.Will I hear the digital noise, or does it only unmute for calls in the clear?
I don't know about 1.3.4, but you should be able to upgrade from 1.3.0 to 1.3.2 (latest on lwvmobile's GitHub page) by runninghi i have an old version of dsd fme installed on dragon os based on ubuntu how can i upgrade mbelib 1.3.0 to new version 1.3.4
git pull
from the mbelib directory.