Setting up plate recognition properly.

• The softwareVISEC reads plates from the camera stream, logs them, and can act on a reading. It is included in every license, including the free one camera license.
• The right camera1080p or better. The plate is what matters, not a nice picture of the whole car — frame for the plate and let everything else be a bonus.
• The right lensVarifocal, megapixel-rated, IR-corrected (day/night), with a DC-Iris or P-Iris. A longer focal length for a more distant lane. The lens is the component people under-spend on and then blame the software.
• The right infraredMost plate-reading setups use 850nm illumination. Plates are retro-reflective, so mount the illuminator as close to the lens as you can — that is what sends the light back into the lens instead of past it. Choose the illuminator for the distance and the spread you need.

• Aim at the plate, not the sceneA camera set up to photograph the whole vehicle usually gives the plate too few pixels. Fill as much of the frame with the plate as the lane allows.
• Keep the angle downThe flatter the camera is to the plate, the more of the characters it sees. A steep downward or sideways angle is the most common reason a good camera reads badly.
• Night is often easier than dayBecause plates reflect infrared, a properly lit plate at night frequently reads more cleanly than one shot into low afternoon sun.
• Speed is rarely the problemVISEC reads plates at over 100 kph (60 mph), so gate and entrance speeds are well within range. Plates from more than 80% of the world's countries are supported.

• Set the region and the eventsRight-click the camera (or View › Video Devices › Properties › LPR) and open Configure Regions & Events. Mark the part of the picture to read — a tighter region is both faster and more accurate.
• Turn the log onIn the events and actions box press Add and choose write log for selected camera. Without this, plates are read but nothing is kept.
• Choose what gets savedThe LPR settings control whether data is logged, whether plate images and full frame images are saved, and in which file formats.

• Search the logView › License plate log lists the readings, and you search it by plate instead of scrubbing through hours of video.
• Jump to the momentDouble-click a plate in the log and the video plays from the reading. This is what turns a dispute into a thirty-second lookup.

• A local database of platesUnder the LPR properties, manage local license plate database keeps the plates you know, with fields for name, address, phone, email and status alongside each one.
• Alerts and gatesAn action on a reading can show an alert window, send an email, or drive a camera output to open a gate or a barrier — through the inputs and outputs already built into ONVIF and Axis cameras. See access control.
• Flagging the unrecognisedA vehicle where no plate could be read can raise its own alert, which at a controlled gate is usually the thing you most want to know about.

• A text fileThe simplest integration: VISEC writes every reading to a text file in a folder, and your own script or software reads it. No API to learn.
• An HTTP POSTFor a live feed into another system, VISEC can POST each reading as it happens, over the LAN or the internet. The post carries the plate, the image and the fields you have defined, and VISEC can authenticate to the receiving system if it needs to.
• The fields it can sendAlongside the reading, the stored contact fields are sent as MISC_NAME, MISC_ADDR, MISC_PHONE, MISC_EMAIL, MISC_EMAIL1, MISC_EMAILSMS and MISC_STATUS. Your own fields are prefixed FLD_. Set it up under the LPR events and actions with data dump or HTTP notification.
• Using VISEC as the LPR engine onlyThis is how sites run VISEC behind an existing VMS: VISEC does the plate reading and posts the results into the other system, which keeps doing everything else.

Still stuck on something? Ask us and we will walk you through it →