Skip to content

Conversation

@OH1KH
Copy link

@OH1KH OH1KH commented Nov 8, 2018

(while waiting that someone writes GUI for dmrconfig).

I have used this script to get a little automation for codeplug fixing process. Seems to work, but GUI would be very very appreciated.

(while waiting that someone writes GUI for dmrconfig)
@sergev
Copy link
Collaborator

sergev commented Dec 4, 2018

Hi Sakari,
Thank you for the useful script. Looks like a good start for a user friendly interface for dmrconfig. I would propose a few improvements.
(1) On "Read from radio" phase, check that the radio is being connected. Do not progress to the Edit step until a valid configuration is obtained from the radio.
(2) In addition to a text backup, always save a binary backup like 2018.12.04_11:35:55_device.img.
(3) After exiting from editor, ask the user for confirmation before writing to the radio.
(4) Use /usr/bin/dialog for user interaction.

@sergev sergev added enhancement New feature or request in development The topic is currently under development labels Dec 4, 2018
@OH1KH
Copy link
Author

OH1KH commented Dec 5, 2018

Hi!

  1. Hmm... lsusb to find it out. Perhaps Do you have better ideas?
    Progress to edit can be done also if jumping directly to .conf (fixing old file ->1st starting parameter), not always via reading it from radio. Lot more quicker.
  2. It can be done, but is it really needed? I have used same binary for many .conf versions with success.
    And because we can not change any settings there it should be always same.
  3. Good point
  4. I do not have that in my Fedora28/LXDE. I have used it few times many years ago (>10). (I Like more command console) I check if it is in repository.

@OH1KH
Copy link
Author

OH1KH commented Dec 5, 2018

  1. Hmm.. Afterwards it can be done with exit code and loop back. Yes.
    But before... could we have " dmrconfig -i Radio model info" or something that jus tinforms the radio name we have connected (or exit code 255 if not connected).
    I.E. the same 1st line as in reading "Connected to..." but without device reading after that.

@olewsaa
Copy link

olewsaa commented Aug 13, 2025

I have written a script that take very simple input from some very simple text files containing the bare minimum of information needed and generate a dmrconfig configuration file. Take a single DRM repeater, you which normally need to add a range of TGs. This is automatically done and all the numbering of entries is also done automatically. In some ways this is even simpler than using a spreadsheet like GUI. It's available on git for testing. My goal was "how simple can I make it?".

I have chosen to make one zone per digital repeater and a small regional zone for the analog repeaters. All digital repaters have the same set of talkgroups to make it simple.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request in development The topic is currently under development

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants