An LPR fault is easier to investigate when the system is separated into four stages: obtaining an image, producing a usable plate read, receiving the intended trigger, and delivering the result to parking software. A failure at one stage can look like a failure elsewhere. Begin with the observed symptom and the actual device architecture, rather than replacing hardware or changing several settings at once.
This guide applies to parking and vehicle-access installations, including commercial premises, residential sites, factories and other managed lanes. Camera menus, status messages, electrical interfaces and service procedures differ by model. The English messages used below are examples; consult the installed product’s documentation for their precise meaning.
Before troubleshooting the lane
Arrange safe traffic management and an authorized assistance route before testing. Record the fault, time, affected lane and recent changes. Preserve permitted logs and the current configuration before a planned restart or adjustment. Keep pedestrians and vehicles outside hazardous movement areas during maintenance.
Start with observations available from normal user interfaces and external indicators. Opening enclosures, testing power supplies, fuses, internal lens cables, relay circuits or electrical terminals belongs to trained, authorized personnel following the equipment’s isolation procedure. Do not bridge safety inputs, bypass protective devices or apply an unspecified voltage to an input to test a trigger. Never assume that a relay or terminal on one model has the same rating or function on another.
Quick diagnosis table
| Symptom | Possible fault area | First useful check | Next direction |
|---|---|---|---|
| No image | Power, connection, stream/input configuration or camera hardware | Device status and an authorized direct live view | Trace the actual image path before changing recognition settings. |
| No License Plate | Unreadable image, ROI, supported format or recognition settings | Inspect the saved frame at the event time | Restore readable capture and then verify detection settings. |
| Vehicle passes with no event | Trigger mode, detector, input mapping or timing | Compare detector state with the application’s input/event log | Identify where the trigger stops, using model-specific diagnostics. |
| Acquiring license plate persists | Device/service availability, authentication, event transport or configuration | Check device results against software receipt logs | Follow the integration path; the message alone does not prove a network fault. |
| Low correct-read rate | Capture quality, traffic conditions, format support or processing | Review representative successful and failed frames | Adjust the relevant factor and repeat the acceptance test. |
| Wrong lane or vehicle | Coverage, recognition region, direction or trigger placement | Compare the event with the physical lane | Refine the zone and timing without excluding valid vehicles. |
Fault 1: no image from the LPR camera
Recognition cannot be assessed without a stable image. Map the real signal path. An IP system may run from camera to network switch to recognition service and display. An analog or embedded system may use a video input and a separate recognition unit. A motorized lens cable controls the lens on some models; it is not a universal link in every camera’s video path.
Check power and device availability
Observe the device and switch indicators through normal access. Check whether the authorized management interface reports the camera online, and whether a direct live view is available. An indicator light alone does not prove adequate power under load, and a failed ping does not prove a powered-off camera because network policy may block it.
If power is suspected, a qualified technician should check the documented supply type, PoE capability and budget, connectors and protection devices using the approved procedure. Do not connect a spare adapter solely because its plug fits. Voltage, polarity, power capacity and PoE method must match the product specification.
Check optics and supported lens controls
Inspect the exterior for a cover, dirt, condensation or damage. If a motorized lens is fitted, check supported focus/zoom controls in the interface. A focus fault can produce a blurry image without causing total video loss. Internal lens-drive connections should be inspected only under the manufacturer’s service procedure; do not open a sealed camera for an unqualified field check.
Inspect the connection path
Review accessible power, network or video connections for strain, looseness and visible weather damage without disturbing energized terminals. Outdoor connectors can suffer water ingress or corrosion even when the cable sheath looks intact. A qualified technician can substitute a compatible known-good cable or supported port in a controlled test, recording one change at a time.
Use the installation’s specified shielding, earthing, surge protection and weather sealing. Do not improvise connections or infer internal cable condition from appearance alone. A temporary improvement after moving a connector needs investigation, not simply repeated reseating.
Check the recognition or display input
If the camera has a direct image but the application does not, inspect the configured source. For IP devices, verify the documented stream URL or profile, device address, credentials, supported encoding and access permissions. For analog equipment, a technician should confirm the correct supported input and signal type. A lane with separate overview and plate cameras must use the intended plate stream.
Check relevant service logs for authentication, unsupported stream or timeout errors. Avoid changing all network and image settings together. Keep passwords and access tokens out of screenshots or support files sent through ordinary channels.
Decide whether repair or replacement is justified
A missing image does not automatically mean a failed camera. After compatible power, cable, input and configuration checks, document whether the fault remains with the device in a controlled test. Ask the manufacturer or qualified service team to assess internal failure. Moving equipment to another live lane without planning can disrupt that lane and invalidate the comparison.
Fault 2: the system reports no license plate
In some products this means an image was received but no valid result was produced; other interfaces use the message differently. First inspect the frame associated with the event, not only a clear live view captured later. A human-readable plate is a useful starting point, but does not by itself establish software support or correct configuration.
Inspect the plate in the captured image
- Is the full plate visible rather than cropped or obscured?
- Is the character detail large and sharp enough for the selected recognition engine?
- Is motion blur present at the actual vehicle speed?
- Are sunlight, headlights or IR washing out the characters, or is the image too dark?
- Do a barrier arm, bodywork, tow hitch, dirt or plate frame hide relevant detail?
- Does the vehicle pass within the configured readable distance and zone?
Check whether the camera moved
Vibration, an impact, a loose bracket, nearby maintenance or wind can change the view. Compare it with the accepted lane plan or saved reference image. Confirm that the normal vehicle path still crosses the intended capture zone. Do not aim only at one convenient parked car if moving vehicles take different positions.
Review focus, zoom, exposure and illumination
| Observed image | What to investigate | Possible correction to verify |
|---|---|---|
| Blurred plate | Focus, motion, exposure time and vibration | Use the model’s focus procedure, supported exposure settings or a better capture position. |
| Plate too small | Field of view, distance and stream resolution | Adjust compatible optics or position while retaining required coverage. |
| Bright unreadable plate | Gain, exposure, IR reflection and headlights | Tune supported lighting/exposure and test near and far vehicles. |
| Dark plate | Illumination, exposure profile and night mode | Restore suitable supported lighting without introducing saturation. |
| Readable plate but no result | ROI, format support, trigger/direction and recognition service | Check the relevant settings and event logs before replacing optics. |
WDR behavior and exposure profiles differ by camera. Follow the model’s plate-capture guidance and test moving traffic. A brighter general scene is not necessarily a better recognition image. Do not copy shutter, gain or illumination values from another model without verifying the intended operating conditions.
Check the recognition region
The region of interest, or ROI, should include the actual plate path at the required capture positions. A very large region can include adjacent lanes or background vehicles; a small or misplaced region can exclude legitimate plates. Adjust it against recorded examples from the relevant lane and confirm that different vehicle heights and paths remain covered.
Check supported countries and plate formats
If the software uses a country or region selection, verify it against the actual plate mix and the licensed recognition capability. Plate layouts, scripts, colors and temporary formats differ. A menu selection does not add unsupported formats. Confirm changes against the product documentation and retain a fallback for plates the installed system cannot read reliably.
Fault 3: a vehicle passes but no trigger event appears
Do not assume every lane uses a ground loop. A camera may use continuous analysis, a video line, a loop detector, radar, another supported sensor, an external input or an authorized software command. Identify the configured mode and intended event before examining wiring.
Confirm the trigger method
Compare the lane documentation with the application settings. Check whether a direction rule, schedule, disabled input or operating mode is suppressing events. If the system has a supported manual diagnostic trigger, use it only under the planned safe test procedure; it must not bypass barrier protections.
Compare detector status with the event
For a loop-based lane, observe the detector’s normal indicators or diagnostic interface while a controlled test vehicle occupies the intended area. Check documented fault states and whether the vehicle actually crosses the detection zone. Similar observations apply to radar or other sensors using their own instructions.
If the detector does not report occupancy or an event, an authorized technician should investigate the loop or sensor, its supply, configuration and physical installation. Do not adjust sensitivity indiscriminately: it can change detection of motorcycles, nearby vehicles or persistent occupancy. Roadwork and electrical tests need the appropriate site controls.
Check whether the host receives the signal
A detector indication does not prove the host received the correct event. Use supported input diagnostics or logs to compare detector state, controller input and application event. A technician should verify input type, contact logic, timing and wiring against both devices’ documents. A dry-contact output, a powered output and a safety circuit are not interchangeable.
Never short terminals or inject voltage as a generic test. Do not reuse a safety input as an access trigger without an approved design. If the interface is undocumented or a terminal may be damaged, stop that electrical test and seek the equipment supplier’s procedure.
Check trigger timing against the image
An event can arrive before the plate reaches the readable zone or after it leaves. Review time-aligned event logs and images. Confirm trigger position, direction and any supported delay against the vehicle path. After changes, test different vehicle lengths and speeds so one successful car does not conceal an ongoing timing problem.
Fault 4: the application remains on acquiring a plate
A waiting message can mean missing results, a disconnected service, an integration error or an application-specific state. Compare the camera’s local result with what the parking application receives. This separates a recognition problem from a delivery or display problem.
Check device and service state
Confirm power and status through authorized interfaces. Capture relevant timestamps and errors before a planned restart. Coordinate any interruption with the operator and verify startup afterward. If the problem returns, investigate the cause rather than treating repeated reboots as a repair.
Check the lane network
- Check accessible cable connections, switch status and the documented device address.
- Investigate address conflicts, subnet/gateway settings and approved routing.
- Check firewall or VLAN permissions with the network administrator; do not disable protections as a shortcut.
- Assess intermittent loss, link changes and clock synchronization using authorized tools.
- For event integrations, verify the agreed protocol, destination, port, authentication and message format.
Devices need a permitted communication path; they do not always need to share the same subnet. A successful ping alone does not prove that the application port, credentials or event delivery work. Conversely, blocked ping traffic may coexist with a working application connection.
Check the recognition service and parking application
Confirm that the required service and licensed module are enabled, that the application selects the correct device and that credentials remain valid. Compare lane/device IDs, configured endpoints and supported software/firmware versions. Logs may distinguish timeout, authentication failure, rejected payload and an offline device.
For systems with a separate recognition host and industrial computer, trace both connections. Preserve example event identifiers and timestamps so support can match records across components. Remove passwords, tokens and unnecessary personal information from diagnostic exports.
Review lane configuration
Check entrance/exit direction, lane number, camera or host address, device ID, trigger mode, supported region, ROI and barrier linkage against the approved configuration. If a recent change preceded the fault, compare with the saved configuration and follow the site’s change procedure.
A working adjacent lane can help reveal differences, but do not copy its complete configuration: addresses, IDs, physical direction, geometry and safety arrangements may be unique. Use a controlled correction with a clear recovery plan.
Verify recognition quality after repair
Camera angle and mounting height
Confirm a complete, sharp plate with adequate image size and a suitable angle. Check that mounting and view match the vehicle path, and that the barrier does not block the plate. A repaired connection does not guarantee the camera has retained its accepted alignment.
The actual capture zone
The best reading point is where the plate is usable, not necessarily the center of the full image. At a barrier it may be near the stop line; in a moving lane it must match the expected speed and direction. Verify the near and far boundaries and the processing time available.
Day and night illumination
Test both daytime and nighttime conditions, including headlights and reflective plates. Review the supported exposure profile, shutter, gain, WDR and illumination together. Excess light can erase characters; insufficient light can force blur or noisy images. Recheck after any lighting adjustment.
ROI, trigger and direction
Confirm where the software looks, when it acts and which travel direction it accepts. Test adjacent traffic and permitted vehicle positions. Refining the ROI must not exclude taller vehicles, motorcycles or valid paths that the project is supposed to support.
Real-vehicle acceptance
Use the site’s expected mix: cars, SUVs, commercial vehicles and motorcycles where supported; relevant front/rear plate layouts; varied reflectivity and realistic cleanliness; slow and faster permitted approaches; day and night. Include uncertain reads and assistance routes, not only successful examples.
Record the number of observed vehicles, correctly read plates, missing/incorrect results, duplicate events, manual interventions and correct session pairing where relevant. Agree the denominator and acceptance targets. Check safe barrier behavior through the approved commissioning procedure; a good OCR result alone is not a safety test.
Maintenance checklist
Set intervals from the environment, duty cycle, equipment instructions and observed faults. The table gives review triggers, not a universal weekly or monthly servicing promise.
| Item | Check | Purpose | When to review |
|---|---|---|---|
| Lens/window | Dirt, water marks, insects and condensation | Maintain readable images | At the site-defined interval and after contamination or quality decline |
| Mounting | Movement, damage or vibration | Retain alignment | During inspections and after impact or nearby work |
| Power path | Approved supply and visible fault status; technical checks by qualified staff | Investigate outages or restarts | According to maintenance instructions and recurrent symptoms |
| Network/video path | Connectors, weather sealing and stability | Avoid image and communication loss | During inspections and after ingress or intermittent faults |
| Illumination | Coverage, function and plate reflection | Maintain night capture | At scheduled checks and after lighting changes |
| Detector/trigger | Supported event diagnostics and physical zone | Confirm capture timing | At scheduled checks and after sensor or road changes |
| ROI and direction | Actual plate paths within the configured region | Avoid missed or wrong-lane reads | After camera or layout adjustment |
| Software configuration | Lane, device, trigger and supported region | Maintain correct operation | After authorized software/configuration changes |
| Logs | Recurring failures, exceptions and service status | Detect trends | At an interval suited to traffic and incident risk |
When to replace parts or escalate
Intermittent cable faults
Water, aging, damaged conductors or connectors can cause intermittent loss, but the symptom alone does not identify the cable. A qualified technician can make a compatible substitution and verify whether the fault follows the cable. Use the specified outdoor protection for a permanent replacement and retest the lane.
Camera repair or replacement
Escalate when the image fault remains after documented compatible supply, cable, interface and configuration checks. Provide the model, observed behavior and controlled test results. Internal boards, sealed optics and serviceable modules should be assessed under the manufacturer’s repair process rather than replaced speculatively.
Detector replacement
A missing, delayed or unstable trigger may originate in the loop, sensor alignment, configuration, interference, wiring or detector. Confirm the cause before replacement. After a compatible replacement, verify detection coverage and event timing and complete the installed barrier’s required safety checks.
Repeated communication faults
Provide support with the affected lane, timestamps, device and software versions, sanitized configuration, relevant errors and permitted sample frames. Wiring photographs should be taken only when safe and by authorized personnel. Use an approved secure channel for any necessary sensitive information; never include passwords in ordinary screenshots.
Diagnose in order
Follow the image path, plate visibility, trigger event, communication and application configuration. Change one relevant factor at a time and record the result. Return the lane to normal operation only after the agreed functional and safety checks. Shunjie project support, OEM options and replacement compatibility must be confirmed for the installed products and configuration.
Frequently asked questions
1. Why is there no image?
Possible causes include power, connection, stream/input configuration, credentials or hardware. Check authorized status and live view first. Internal wiring and power tests require qualified service procedures.
2. Why does it report no license plate?
Check the product’s message definition, then the captured frame. Confirm complete, readable characters, sufficient size, supported format, ROI and the correct trigger or direction.
3. Why is there no response to a passing vehicle?
Verify the actual trigger mode and compare detector status with host input and application logs. The cause may be detection, timing, mapping or configuration; do not bypass safety circuits to force a result.
4. Why is the plate overexposed at night?
Reflective plates, gain, exposure and IR intensity can combine to saturate characters. Use the model’s supported settings, review alignment and retest near and far vehicles.
5. Why does acquiring a plate never finish?
The application may lack a result or connection, or may be in another waiting state. Compare local recognition with received events and inspect services, authentication, routing and lane configuration.
6. Does higher resolution always improve accuracy?
No. The plate must be sharp, exposed correctly, visible and supported. Higher resolution can also increase processing load. Check capture quality, timing and the selected engine’s stream requirements.
7. How often should maintenance occur?
Use the manufacturer’s instructions and a site-specific schedule based on traffic, weather and observed quality. Clean sooner after contamination and inspect after impacts or configuration changes; no single interval suits every lane.
8. Video trigger or ground-loop trigger?
Both may be suitable when supported. Choose according to lane layout, vehicle types, timing and integration requirements. Validate the actual detection zone and fallback behavior; neither choice replaces the barrier’s required safeguards.
Technical reference and support
The Axis License Plate Verifier manual illustrates product-specific recognition regions, access scenarios and diagnostics; its ports and wiring details must not be transferred to unrelated equipment. For Shunjie assistance, send the sanitized project details through our contact page.
