LWK Development radar and ALPR in CDE CAD

LWK Development's seeker_dual radar runs the plates around a patrol car through CDE CAD's records and sends every speed an officer locks to their MDT. When they write the citation, its Speeding Information fills from the lock.

What seeker_dual and CDE CAD do together

  • The plate reader runs nearby plates through CDE CAD and alerts on stolen or impounded vehicles, expired registration, no insurance, and CAD flags such as warrants, BOLOs and your own custom flags
  • Each speed lock reaches the CAD with the plate, direction of travel, street, zone and postal, weather and patrol car; CDE CAD keeps an officer's locks for 12 hours, the latest 25
  • A citation's Speeding Information section lists the officer's locks this shift; picking one fills the speed, Radar, direction, officer position, weather, device make and model, serial, calibration date and certificate, and the operator's radar certificate number
  • A citation whose plate matches a lock fills itself, on the report writer, Dashboards 4, 10 and 11, Flex and the mobile report page
  • Your community's custom plate designs show on seeker_dual's plate reader
  • Only on-duty CDE CAD law enforcement can use the radar; it powers on in the first emergency vehicle after going on duty and auto locks at 80 mph by default

LWK Development + CDE CAD FAQ

Does CDE CAD work with LWK Development's radar?

Yes. CDE CAD maintains a build of LWK Development's seeker_dual, a Stalker Dual DSR radar for FiveM. With the CDECAD resource on the same server, its plate reader runs plates through CDE CAD and every speed lock reaches the officer's MDT and citation.

Where does the operator certificate number come from?

From the officer's own active radar certification in CDE CAD, such as the certificate id of an Academy course they passed.

Does this need an ALPR setup in seeker_dual?

No. seeker_dual runs plates through CDE CAD on its own when the CDE_CAD_API_KEY convar is set.