-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log DMR messages/SMS to text file #186
Comments
I'd definitely find something like this useful, too, with the exception that I'd like to have all the decoded data available, preferably as JSON lines. Not sure I understand what the difference between "into text file" and "in log file" in 1. and 2. is(?). But would it make sense to do it just for DMR? Or put another way, if someone starts implementing such a feature, should it maybe be built in such a way that other modes could easily be plugged into this "advanced logger" later on? Also, designing the logging format in such a way that it can be extended later or may not/should not be considered a trivial task. I should be able to do this, but would likely require a little guidance to get started. |
@lwvmobile what do you think, would this kind of more-structured-logging make sense? |
If its something you want to work on, then by all means, go ahead. Other than that, I really can't suggest a good starting point for your project, since data logging is spread out all over the place. I would bargain that doing such work is not going to be a trivial task however, really just depends on how deep you want to go with it. If you work on it and make commits to your own fork, when it get to a maturity level, then I may consider pulling it into a development branch on this end, but for the time being, I don't have any plans to do any heavy coding or substantial rewrites to add new features, like a logging system. The only work on DSD-FME I'll be doing in the foreseeable future is just tweaks to trunking and minor fixes as required. I'm not currently taking on any new feature requests. |
@lwvmobile Atleast option to write message output to text file can be added? |
LRRP messages and other location messages already are, when known, but I don't have any handling for most text messages, mostly because its hard to get actual samples with known text messages in them. I do have handling for TIII UDT text messages as is in the DMR ETSI manual, but Moto and other vendor specific versions, I don't have enough information on how they are handled to know when the message is a text vs any other arbitrary information sent out in data blocks. |
@romanremus Can you send some wav file samples of that when that occurs? |
of course, as soon as I manage to register, I will gladly send you LWVMOBILE |
Hello Lwvmobile, just a question, could you make sure we have a terminal that works in Windows? , I tried something with PDCurses but I have no good results, or could you create DSD-FME with an interface like DSDPlus? the code is super good, but in order to be able to enjoy the call alert or to see certain data, it must be run only in cygwin, or at least you can help me to create an interface, thank you very much |
@romanremus I am able to run it just fine in powershell, maybe open a new ticket to discuss that issue? |
@TeddJohnson Hello, Thank you for the answer, I really liked that DSD-FME could have an interface that could work in Windows, like DSDPlus for example, I tried some options, I'm not a programmer, do you think it can be created? |
Presently, dsd-fme displays received DMR messages and other metadata of all decoded calls on terminal. Requested that following options are added:
Simple option is to pipe the complete dsd output to text file, but I was looking for more cleaner and structured approach so that subsequently intercepted metadata can be imported to database (SQLite) for more analysis.
The text was updated successfully, but these errors were encountered: