Write fails and I need to read the config back into RM before writing the new config?

Q I'm using radio manager to administer a rental fleet of R7 handsets via WiFi. When I am reprogramming between projects, I regularly hit an issue where the write fails and I need to read the config back into RM before then writing the new config. What could cause this issue?

A The most likely cause is that the radio was reprogrammed outside of Radio Management since then, either using CPS or another instance of RM. Even if no changes were made, this puts the fingerprint out of sync and will generate an out of sync error (I can't recall the exact wording and error code).

To prevent someone else from tinkering with these radios, you can add TLS-PSK codeplug protection or, if it's not a major headache, just live with it (it also depends on what you mean by regularly).

If you do chose to use the former, be sure to keep a copy of the key somewhere safe because, if you lose it, you're screwed (a saltier word comes to mind).

In case that's not what you're seeing, it would be useful if you could post the error message in the comments. When the write job fails, you will need to go into Job View (wrench/spanner icon top right) and click on the failed job to see what caused it to fail.