First, I'd like to thank you for writing this package.
This made it possible for me to actually use a DMR radio, and it made it possible for me to use a DMR radio with my normal, everyday driver-PC running GNU/Linux Debian OS.
After writing my codeplug for Radioddity GD-77, re-configuring it couple of times, I have found what looks like a bug.
The issue occurs when dmrconfig parses device.conf file and produces device.img file.
Specifically, in the section 'Grouplist', during the parsing/compiling device.img file, regardless of the actual content of lines from 41 to 49, data is corrupted and replaces with repeating value of:
for the 'Name' it's a symbol '_'
for the value of 'Contact' it is a number '65535,' repeating seventeen times.
The rest of the line, from 49 and so on - completely ignored/lost.
To illustrate the issue better, please take a look of the following excerpts:
This is a header for the reference:
Grouplist Name Contacts
This is excerpt from 'device.conf' for the 'Grouplist' section:
To verify this, I used:
$ dmrconfig -c device.img device.conf
followed by :
$ dmrconfig device.img
... to see what device.img looks like before writing it in to the radio.
I have tested and verified the same issue when 'devcie.conf' is used to configure the radio via:
$ dmrconfig -c device.conf
It results in the same data corruption in lines mentioned above and written in to the radio.
Now, this dose not result in abnormal radio operation.
Radio reloads config after writing procedure is completed and dose not indicate that something in it's memory incorrect, other than whatever user configured in those lines - 'brakes' expected behavior of the frequency channel with DMR broadcast just because RxGroups are miss-configured.
Please let me know if it makes sense what the issue is.... and if you need additional information to diagnose and replicate the problem.
Again, thank you so very much for your development effort and sharing it with the rest of us.
Hello Sergei...
First, I'd like to thank you for writing this package. This made it possible for me to actually use a DMR radio, and it made it possible for me to use a DMR radio with my normal, everyday driver-PC running GNU/Linux Debian OS.
After writing my codeplug for Radioddity GD-77, re-configuring it couple of times, I have found what looks like a bug.
The issue occurs when dmrconfig parses device.conf file and produces device.img file.
Specifically, in the section 'Grouplist', during the parsing/compiling device.img file, regardless of the actual content of lines from 41 to 49, data is corrupted and replaces with repeating value of: for the 'Name' it's a symbol '_' for the value of 'Contact' it is a number '65535,' repeating seventeen times.
The rest of the line, from 49 and so on - completely ignored/lost.
To illustrate the issue better, please take a look of the following excerpts:
This is a header for the reference: Grouplist Name Contacts
This is excerpt from 'device.conf' for the 'Grouplist' section:
--------------------------------------
39 GroupList39 - 40 GroupList40 - 41 RxG-NRY-Global 41 42 RxG-MRY-1 42 43 RxG-MRY-Cali 43 44 RxG-MRY-NCal 44 45 RxG-MRY-TAC 45 46 RxG-test-01 46 47 RxG-test-02 47 48 RxG-MRY-DMR-Tech 48 49 GroupList49
Message Text 1 HELLO!
--------------------------------------
And this is what ends up in 'device.img':
--------------------------------------
39 GroupList39 - 40 GroupList40 - 41 65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535 42 65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535 43 65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535 44 65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535 45 65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535 46 65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535 47 65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535 48 65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535,65535
Message Text 1 HELLO!
--------------------------------------
To verify this, I used: $ dmrconfig -c device.img device.conf
followed by : $ dmrconfig device.img ... to see what device.img looks like before writing it in to the radio.
I have tested and verified the same issue when 'devcie.conf' is used to configure the radio via:
$ dmrconfig -c device.conf
It results in the same data corruption in lines mentioned above and written in to the radio. Now, this dose not result in abnormal radio operation. Radio reloads config after writing procedure is completed and dose not indicate that something in it's memory incorrect, other than whatever user configured in those lines - 'brakes' expected behavior of the frequency channel with DMR broadcast just because RxGroups are miss-configured.
Please let me know if it makes sense what the issue is.... and if you need additional information to diagnose and replicate the problem.
Again, thank you so very much for your development effort and sharing it with the rest of us.