Why does Hikvision ANPR show 1111111?

If you have just pressed the Hikvision Alarm Server Test button and Ruby ANPR shows 1111111, 0% confidence and UNKNOWN direction, that can be completely normal.

During Ruby ANPR deployment testing, the Hikvision Alarm Server Test function produced a synthetic event with a distinctive signature:

Registration: 1111111 Confidence: 0.0% Direction: UNKNOWN Images: dark / test images may be supplied

This is a connectivity test, not a real plate read

The Test button is designed to check the configured destination. It is not the same as driving a real vehicle through the ANPR detection area.

So when 1111111 appears immediately after pressing Test, do not start changing OCR settings, zoom or plate-recognition rules. First recognise that the synthetic event has already proved something valuable.

What the 1111111 event proves

Camera → hostname / DNS → HTTP or HTTPS transport → Ruby ANPR ingest endpoint → authentication key → database → image storage → dashboard

If the event appears, the end-to-end delivery route is functioning.

What it does not prove

  • The camera is physically aimed at the correct capture zone.
  • The zoom level is suitable for real plates.
  • Exposure and shutter settings are ideal.
  • Forward and Reverse event linkage is configured correctly.
  • The camera will read every real registration accurately.

Your next test should be a known real vehicle

Once the synthetic Test appears, leave the network destination alone and drive one known vehicle through the configured detection area. Then compare the real event with what you expect:

  • registration number
  • confidence percentage
  • camera name
  • IN or OUT direction
  • plate image
  • vehicle image
  • detection scene

If 1111111 keeps appearing without pressing Test

That is different. Check whether the camera, another installer or an automated process is repeatedly invoking a test function. A normal live vehicle event should carry actual vehicle metadata rather than the synthetic Test signature.

If the Test button does nothing

Work backwards through the transport path: hostname resolution, port, protocol, URL path, API key and web-server access logs. Avoid changing OCR or physical camera settings until you know the request is actually reaching the server.

A successful synthetic Test is good news. Treat it as proof that the integration route works, then validate the ANPR configuration with a real vehicle.