MDC configuration - Fleet 3

Axon Fleet 3 uses the vehicle’s MDC to interface with the hub through Fleet Dashboard, which lets a user start/stop recordings, review and tag videos, view Automated License Plate Reader (ALPR) hits, and modify user preferences.

MDC system requirements

Axon Fleet Dashboard has the following minimum specifications for PC:

  • Operating system – Windows 10 or later
  • Processor – Intel Core i5-11th Gen or newer
  • Memory – 8 GB RAM or more
  • Storage – 10 GB of free space
  • Display – 1024x768 or higher
  • Network – 1 Gbps ethernet port or 1 Gbps USB3 ethernet adapter

While hardware with lower specs may still function, meeting these requirements will ensure the best possible experience with Axon Fleet Dashboard.

Multicast DNS

Fleet Dashboard uses Multicast DNS (mDNS) to discover the Fleet Hub.

If the MDC uses Windows 10, it supports Multicast DNS by default and no action is needed.

Firewall settings

Firewall considerations:

  • Only Dashboard's inbound sign-in flow requires momentarily inboard traffic.
  • Fleet Hub and Dashboard originate all traffic (except noted above) for outbound communication; whenever a port is referenced below, it is always initiated by outbound traffic.

Fleet Dashboard must be able to reach the Fleet Hub via axoncar.local on the following ports:

  • 8000 (TCP): Used by Dashboard to authenticate against Axon Service; inbound traffic only, temporary port usage
  • 8090 (TCP): Used for displaying the Axon Dashboard content, LiveView (using wss:// over 8090), and downloading Dashboard application updates
  • 8100 (TCP): Used for playing videos
  • 5353 (UDP): Used by Dashboard to discover the hub via Multicast DNS
  • 53 (UDP): Used by DNS for fallback, Dashboard to Hub discovery, and router local domain configuration

Additionally, Fleet Dashboard must be able to access the following internet addresses:

  • *.evidence.com (TCP 443) for signing into Axon Service
  • Port 80 (outbound) for reachability checks to Axon Service
  • fleetevidenceping.com (TCP 443) for Wi-Fi Direct Offload
  • Any SSO provider domains you use
  • If you have implemented network-based controls to manage internet access, you might find that your user, client, or device access won't connect with Axon Cloud Services unless specific network configurations are made; for help with this, see Managing network allowlists with Axon Cloud Services on my.Axon.

Proxy settings

Create a local proxy bypass rule to ensure axoncar.local traffic is not directed to the proxy and allow the MDC to communicate directly with the Fleet Hub on the in-vehicle LAN.

If using a traditional proxy, it should allow traffic to all internet addresses listed in Firewall settings. LINK

Adding axoncar.local to an allowed list should not be necessary.

Dashboard notifications

Dashboard displays notifications for ALPR hits. The default Windows setting for how long notifications are displayed is five seconds. Axon recommends making the display time longer so officers have more time to respond. This setting is found in the Ease of Access section. For more details on this setting, see Dashboard ALPR settings at My.Axon or the Axon Dashboard User Guide on the Fleet 3 product page.

 

Next topic: MDC configuration

 

Last modified - 28 April 2026