Use this workflow to install, connect, program, and validate a supported radar with Axon Fleet 3. The exact cable, connector, firmware, serial parameters, and menu names depend on the radar model and the current Axon integration guide.
Configuration warning: Do not substitute a generic serial cable or guess pinouts. Use the approved Axon radar cable kit and the radar manufacturer’s manual. The two verified Fleet 3 cable families referenced here are Stalker DSR Dual SL and Kustom Signals RP1/E3.
1
Identify the exact radar package
☐ Record radar manufacturer, model, revision, serial number, front/rear configuration, and display type.
☐ Confirm the Fleet 3 vehicle has the correct approved integration cable: Stalker DSR Dual SL kit or Kustom Signals RP1/E3 kit as applicable.
☐ Obtain the current Axon Radar Integration User Guide and the radar operator/installation manual.
☐ Confirm whether the installation uses one radar, dual radar, rear radar, a remote display, or a separate control head.
2
Plan power and mounting
☐ Mount the radar and display where the manufacturer specifies, with a clear forward/rear field and secure vibration-resistant hardware.
☐ Use the vehicle-specific fused power and ignition-enable plan; do not power the radar from an unprotected accessory lead.
☐ Route the radar cable away from airbags, pedals, steering components, sharp edges, heat, and high-current alternator/starter wiring.
☐ Provide strain relief at the radar, Fleet Hub, and any display/control connector.
3
Connect the approved interface
☐ Power down the vehicle and Fleet system before connecting the interface cable.
☐ Connect the radar-side plug to the correct port and the Fleet-side plug to the designated Hub radar port.
☐ For dual radar, label front and rear channels and verify that each cable reaches the intended radar.
☐ Check connector locks, pin alignment, shielding/ground continuity, and that no terminals are pushed back.
4
Program the radar itself
☐ Enter the radar manufacturer’s setup/service menu using the approved service procedure.
☐ Set the correct vehicle side/channel: front or rear; configure dual-unit addressing if the model supports it.
☐ Set operating mode, direction logic, target priorities, units, speed display, patrol/target mode, and alert behavior according to agency policy.
☐ Set the communication protocol, baud rate, parity, data bits, stop bits, and output mode only from the current radar/Axon guide—never from a guessed value.
☐ Save/write the configuration, power-cycle the radar, and confirm settings persist.
5
Configure Fleet 3 and Axon Evidence
☐ In the authorized Axon administration workflow, select the Fleet 3 vehicle and open the radar integration/device settings.
☐ Assign the radar to the correct vehicle and identify the front/rear channel or device name.
☐ Confirm the integration is enabled and that radar events/data are associated with the correct recording source.
☐ Apply/save the configuration and allow the Fleet Hub to restart or reload the integration if prompted.
☐ Record the vehicle ID, radar serial number, cable kit, firmware versions, and final programming values in the install record.
6
Calibrate and validate on a controlled test
☐ Perform the radar manufacturer’s alignment/verification procedure; do not rely on a visual guess alone.
☐ With the vehicle stationary, verify radar status, display, direction, and front/rear identification.
☐ On a safe closed course or approved test area, generate known targets and compare displayed radar data with the radar display and Fleet recording.
☐ Start and stop recording, trigger a radar event, and confirm the event/data is time-aligned with the video.
☐ Test ignition off, shutdown delay, restart, intermittent cable movement, and key-off current draw.
Radar Programming Resources
Open the applicable guide before programming a production vehicle.
Access note: Axon and manufacturer pages may require an account, authorization, or a model-specific document. If a link changes, start from the vendor’s support page and search the exact radar model.
Radar-to-Fleet 3 Programming Diagrams
Workflow diagrams only. They do not replace approved pinout, firmware, or serial-setting documentation.
NO PINOUTS SHOWN
1. Overall data path
Program the radar, connect the approved interface, then configure the Fleet 3 vehicle record and verify that radar data is accepted.
2. Stalker DSR Dual SL
Use the DSR-specific cable and manual. Program each radar identity, confirm front/rear mapping, save, power-cycle, then test both channels independently.
3. Kustom Signals RP1/E3
Use the correct RP1/E3 cable length and Kustom-specific programming procedure. Confirm output, power-cycle persistence, and event alignment with Fleet video.
Manufacturer-specific checkpoints
Stalker DSR Dual SL
Verify the dual-radar cable kit, front/rear channel assignment, radar addressing, and the Stalker-required communication/output settings before testing.
Kustom Signals RP1/E3
Verify the correct RP1/E3 cable length and connector family, radar mode, display/output settings, and the Kustom-specific programming procedure.
Acceptance checklist
☐ Fleet Hub recognizes the radar without communication faults.
☐ Correct front/rear radar is shown on the display and in the vehicle record.
☐ Radar data appears with the correct recording and event marker.
☐ Known targets produce repeatable readings in the approved test area.
☐ No cable, power, ignition, or ground fault appears during vibration testing.
☐ Vehicle shuts down normally and key-off current returns to the expected sleep range.
What is verified vs. variable: Axon publishes dedicated Fleet 3 radar cable kits and references a Radar Integration User Guide. Exact pinouts, serial settings, radar menu values, firmware compatibility, calibration targets, and Evidence configuration are model-, revision-, and agency-dependent. Confirm those items in the current controlled documentation before programming a production vehicle.