Reporting Issues (Patreon)

There needs to be some standard about how bug/glitch reports are made because nicFW is very complex and when people report bugs they always miss vital information.

Every bug report should state that this post has been read and understood.

The most important thing in any report is NOT describing the fault, that is in fact very unimportant. A bug report should be primarily a set of instructions telling me how to replicate the problem. If I can see the problem occuring myself on my radio, I don't need a description, I can see for myself what's happening. This is the factor that most don't seem to understand. In order to fix something I have to experience it. Most of the time, when folk describe an issue, I duplicate what I can from their description and I end up not being able to reproduce it, and it ends there as there's nothing more I can do without further information.
So to reiterate, a bug report should be a set of instructions detailing how to create and experience the issue.

How to make the instructions?

Return the radio to a default state. That means writing your backup 880spi file back to the radio. This will put nicFW in a completely new "just flashed" default condition.

Now, document every single step you take from this new default condition in order to make the issue occur. This should be as minimal as possible.

State what version of the firmware you are using, if it's not the latest version, then don't make the report. I'm not interested in bug reports from previous versions, I cannot test them.

If the report involves usage of the RMS confirm you are using the same version RMS as the Firmware.