Hannes Matuschek
Hannes Matuschek
Does it say something like "Enter program mode" before writing?
And with dmrconf it works? If so, this is really weird.
> qdmr doesn't appear to put the radio into "Memory Prog" mode when trying to write the db. This is a text string shown on the screen when the radio...
> Additionally, is there a mechanism here to validate that the stuff dmrconf has written to the radio is actually there? For now not.
> The `Got device ID 'MD-760P'.` is a bit suspect. This used to be a hexadecimal string in earlier builds. > Sadly no improvement/progress with the callsign db upload to...
The weird thing is, that dmrconf works and qdmr doesn't. Both use the same code to communicate with the device. To this end, I can only imagine one way this...
Oh that is not good. Does the normal codeplug read/write work with qdmr? If it does, could you capture the database write using dmrconf and qdmr using wireshark under linux?...
Thanks for the captures, I've found an issue with the bank selection which could explain why the uploaded call-sign DB does not work. However, the qdmr issue is still unsolved....
E.g. DMR-ID ``` > Request, len=0x07 > | 00000000 02 50 52 4f 47 52 41 | .PROGRA < Response, len=0x01 < | ACK > Request, len=0x02 > | 00000000...
Had you installed the libdmrconf library? If so, there might be an issue that qdmr gets linked against the installed (old) version instead of the version build along the application....