Firmware and Data Updates on Radar Detectors

Updates are the field most often forgotten in a quote and most often argued about after the sale. A unit's firmware can change its behavior, and any data feature needs a stated update path. Settle the update questions before the order, in writing.

Firmware

Confirm the firmware version for the production run, and record it. Ask how a firmware change is made: over a cable to a computer, through a phone connection, or not at all. A unit that cannot be updated is not a defect, but it must be described that way in the listing. If updates exist, confirm who provides the update file, in which languages the updater runs, and what happens to settings during an update.

Data features

Where a unit carries stored data, such as marked locations the driver saves, confirm what the data contains, where it lives, and how it is updated. Update method and update cost belong on the specification sheet. Do not describe any data feature beyond the supplier's written description, and do not describe data features as enforcement-related in any way; stored data in this product category describes the driver's own saved points and settings.

Version discipline in production

Ask the factory to record the firmware version per production run and to state it in the shipping documents. If a version changes between runs, the change is notified in writing and, where behavior changes, approved again. This is the same discipline as any other component change.

Listing language

• State whether the unit is updatable, and by what method.
• State whether updates are free or paid, and who hosts them.
• Never promise future features. A listing describes the unit as it ships.

Update questions are cheap to ask and expensive to discover. They belong on the specification sheet next to the band list, not in the comments after the first return.