Hikvision iDS-2CD7A26G0/P-IZHSY ANPR setup

This DeepinView ANPR model is the camera used during Ruby ANPR production testing and is confirmed for the Alarm Server workflow.

The iDS-2CD7A26G0/P-IZHSY is a confirmed Ruby ANPR model. During live testing it successfully delivered ANPR events to Ruby ANPR over HTTPS, including real registrations, evidence images, direction metadata and the positioning heartbeat.

Recommended Ruby ANPR event destination

Destination / Hostname: anpr.yourdomain.com Protocol: HTTPS Port: 443 URL: /ingest.php?key=YOUR_CAMERA_API_KEY ANPR Protocol Type: HIKVISION ANR: Enable

Step 1 — create the camera in Ruby ANPR

Add the camera in the Ruby ANPR Cameras page and copy its generated ingest endpoint. Treat the API key as a secret. Do not publish it in documentation, screenshots or public logs.

Step 2 — configure Hikvision Alarm Server

Enter the Ruby ANPR hostname, HTTPS protocol, port 443 and generated URL in the camera's Alarm Server configuration. Use the hostname rather than the server IP so SSL and virtual-host routing work correctly.

Step 3 — press Test

The Hikvision Test function should send a synthetic event. In Ruby ANPR this can appear as:

1111111 0.0% confidence UNKNOWN direction

That is expected for the connectivity test. Once it arrives, the transport route is working.

Step 4 — configure both Forward and Reverse

For correct IN / OUT reporting, configure both direction linkages in the Road Traffic / arming-linkage setup.

forward → IN reverse → OUT

If only one direction is enabled, Ruby ANPR will only receive that side of the vehicle movement.

Step 5 — enable the 60-second heartbeat

Enable GPS / Positioning Upload and set the interval to 60 seconds. Ruby ANPR uses the authenticated positioning request to maintain Last seen and camera-health status without creating a false vehicle capture.

Step 6 — run a real vehicle test

Drive a known vehicle through the capture area and confirm:

  • registration is correct
  • confidence is sensible
  • IN / OUT direction is correct
  • plate image is present
  • vehicle image is present where configured
  • detection scene is present where configured

If you see many UNKNOWN events

Do not immediately assume the Ruby ANPR parser is at fault. During testing, a large number of UNKNOWN/no-plate detections were traced to incorrect physical camera zoom. Correcting the camera view resolved the issue.

Cloudflare and HTTPS

This model has been used successfully with a public HTTPS Ruby ANPR endpoint behind Cloudflare. If a configuration change appears not to work, distinguish camera transport issues from browser asset caching; they are separate problems.

What a healthy finished setup looks like

  • real registrations arrive reliably
  • three evidence images appear when supplied
  • Forward and Reverse display as IN and OUT
  • Last seen updates from the 60-second positioning heartbeat
  • Hikvision Test creates the synthetic 1111111 event
  • camera status remains Online during quiet periods
This is the strongest currently proven Ruby ANPR reference model because the complete workflow has been tested in real use.