Physical Camera Installation Guide

InstallUse this field guide to position, mount, and commissiontest cameras so thatfor SiteTrax.io receivesOCR. sharp,The complete,numbered well-litsteps views of the identifiers your project is configured to read. This guide coverscover fixed Gate and BringBYOC Yourcameras. Own Camera (BYOC) installations,For vehicle-mounted Driveor cameras,handheld andcapture, camerause positioningthe forproduct Mobilelinks and Snap capture.below.

DesignBefore principle:permanent mounting: choosesend therepresentative capturerecorded positionfootage aroundto theSiteTrax.io identifier,for its motion, and the required evidence.review. A cameraclear thatview showsof a vehicle clearly does not necessarily showmake its textidentifiers clearly enough for OCR.readable.

Quick reference: fixed Gate cameras

Project-specific acceptance: minimum character pixel height, allowable viewing angles, usable capture duration, and commissioning pass rates must be agreedStart with these published SiteTrax.io forrecommendations, eachthen project. There is currently no universal SiteTrax.io threshold for these values. Numerical examples below explain design calculations; they are not acceptance criteria or performance guarantees.

Suggested installation sequence. Agree responsibilities and acceptance criteria for your project. Selectvalidate the image to enlarge.

1. Establish the deployment requirements

Read the Gate Camera Installation Requirements and Guidelines before planning fixed hardware. For a third-party camera, also complete the BYOC evaluation. Confirm the following with the site owner and SiteTrax.io before drilling holes or selecting a lens.

Required outputs: container ID, chassis ID, trailer ID, USDOT number, license plate, or other explicitly configured text. Photograph representative markings and record their location, orientation, smallest character size, and height above the road. Confirm support for specialized assets or text with SiteTrax.io; this guide does not establish support for every OCR application. Traffic envelope: eachactual lane and direction,markings. vehicle dimensions, lateral wandering, stopping locations, maximum operating speed, reversing, queues, tailgating, and simultaneous adjacent traffic. Capture conditions: minimum and maximum target distance, direct sun, shadows, headlights, night lighting, rain, dust, spray, seasonal vegetation, and expected vibration. Infrastructure:Measure mounting surface,height service access, power, camera power requirements, network route, upload capacity, and ownership of maintenance and remote configuration. Processing and evidence: project, camera identity, required asset types, direction mapping, coordinates, timestamps, upload destination, retention, and downstream delivery. Acceptance plan: representative test population, independently verified identifiers, thresholds per asset type and condition, exception treatment, andfrom the personroad responsiblesurface for sign-off.

Mark each camera, capture zone, light, traffic direction, and obstruction on a site sketch. A capture zone isto the partcentre of the vehicle path in which the required marking is visible, sufficiently detailed, sharp, and correctly exposed. The full camera view will usually be larger than this zone.

2. Select the views and camera positions

Fixed gates: assign views by lane, direction, and target

The Gate installation guide recommends at least one camera per lane and identifies two cameras per lane as best practice. Design dedicated coverage for each direction. Allocate the views to the identifiers that must be captured; do not assume two cameras in arbitrary positions will capture every asset.

Gate Operations acknowledges that a single camera can support both directions when placement and configuration capture them reliably. Treat this as a project-specific design that needs validation, including opposing traffic and occlusion. It does not replace the dedicated-camera baseline.lens.

TargetItem	PlacementStarting approach

Verify with real assetsrecommendation Rear container and chassis markingsIDs The Gate guide suggests approximatelyAbout 3 ft (about 1 m) mounting height for capturingabove the backsroad. ofKeep containers and chassis. Use this as an initial camera-height reference. The low chassisboth marking andlocations the required container marking are both visible; tires, mudguards, chassis beams, and rear fittings do not block them.visible. Container-Container ID only rear markings 4–6 ft above the road. The Gate guiderequirements suggestsgive approximatelyan 4–6approximate ftmetric (aboutrange of 1.3–2 m). Set the final height and aim for the actual marking positions. Required horizontal and vertical text remains fully in frame across the fleet and lane envelope.m. TrailerCamera IDscoverage At least one camera per lane; two per lane is the published best practice. Assign each view to its intended lane, direction, and side markings, including USDOT Choose the side of the lane that exposes the required panel. Aim toward the marked surface, allowing enough context for the configured detector. Tractor, trailer, and carrier identifiers are not confused; logos, straps, adjacent equipment, and articulation do not hide the target.markings. LicenseVehicle plates, where configuredspeed Use10 amph view(16 km/h) or less through the capture zone. Recorded video 1920 × 1080 at 30 fps; MP4; clips no longer than 1 minute. Lens 6 mm or longer is the published recommendation. Select the actual focal length for the camera sensor, distance, and exposurerequired suitedview.

Sources: Gate requirements and Input Video specification. These heights apply to the platestated fixed rear views, not every OCR installation. Other views, distances, angles, minimum character size in pixels, and acceptance rates are project-specific.

1. Agree the capture plan

Installer + SiteTrax.io: confirm the identifiers, asset types, lanes, directions, maximum speed, and day/night operation. Mark camera positions, lights, traffic paths, and the intended reading area on a site sketch. This reading area is the capture zone. Agree test conditions, sample counts, required read rates, and the person who will sign off. Record separate targets for each required identifier type. Customer/installer: arrange mounting, power, network access, and maintenance. Confirm the BYOC requirements before buying third-party hardware.

2. Trial the position and reflectiveframing

material.

AUse separatea platerepresentative viewvehicle mayat bethe needed.capture Platezone. Trial the applicable height from the table before drilling permanent fixings. Aim as squarely as practical at the required markings. Keep text level; avoid steep downward or sideways views. Adjust optical zoom and focus so the smallest required text is readable in headlights and darkness as well as daylight; an exposure that reads a plate may leave container markings too dark. Yard inventory or other configured OCR Map the requiredsaved assetrecording facesat andfull accessibleresolution. viewingDigital routes. Arrange additional views where one positionzoom cannot seerestore allmissing required markings. Coverage includes the intended rows and heights. Hidden or inward-facing identifiers require another view or an exception process.

These Gate heights are starting recommendations for the stated rear-view use cases, not universal dimensions for side views, plates, elevated structures, or vehicle-mounted cameras. Measure camera height at the lens center and record the final value.

Choose geometry before adjusting software

Illustrative marking locations and field of view; not to scale. Identifiers are fictional. Confirm coverage of your actual assets; additional views may be needed.

Place a representative asset in the proposed capture zone under controlled site conditions. Identify the exact marked surface to be read. Temporarily position the camera at the proposed height and offset using a secure trial mount. Observe the actual recording stream. Aim as nearly perpendicular to the marked surface as practical. Reduce sideways perspective and excessive downward tilt. Level camera roll so the scene is not unnecessarily rotated; naturally vertical container text should remain fully visible.detail. Check the nearest and farthest targetvehicle positions,positions and normal lane wandering. Include the highestcomplete and lowest markings, and both edges of the permitted vehicle path. Allow margin for movementidentifier without sacrificing text detail.clipping. Check thatqueues, adjacent traffic, barriers, gateand arms,vehicle posts,structures protectivefor bollards,obstruction. mirrors,If both container and passingchassis vehiclesIDs cannot maskbe thecaptured identifier at the required moment. If one view cannot meet all requirements,clearly, change the position, narrow its assignment,position or add anothera view. DoRecord notmoving compensatesamples forand anreview obstructedthem orwith tinySiteTrax.io identifierbefore bysecuring increasingthe OCRfinal confidence thresholds.position.

For a flat target facing along a lane, a useful geometry estimate is horizontal angle = atan(lateral offset / forward distance)Measure and verticalrecord anglelens =height, atan(heightcamera-to-target differencedistance, /and horizontallane ground distance).offset. Use thededicated heightlane/direction differenceviews betweenas the lensbaseline. andA the target marking, not simply height above ground. These estimates change when the asset turnsshared or thebidirectional textview isrequires onvalidation awith sideSiteTrax.io; panel.see Gate Operations.

For

license-plate

Illustrative capture,coverage Axis recommends keeping the combined camera-to-travel angle below 30°. This is external plate-camera guidance,only; not a SiteTrax.ioscale limit for container, chassis,drawing or genericprescribed OCR.mounting Minimize obliquity and validate the final geometry with SiteTrax.io. See Axis: License plate capture.geometry.

3. SelectSecure the lens, framing,camera and focuscabling

The

SiteTrax.ioUse APIa —rigid Input (Video) recommends 1920 × 1080 at 30 frames per secondmount and specifiesmanufacturer-approved afixings lens of 6 mm or longer, warning about distortion with lenses below 5 mm. For a fixed/BYOC design, use that guidance and confirm the sensor, working distance, and field of view with SiteTrax.io. Do not substitute a phone's advertised equivalent focal length for an industrial camera's physical lens specification.

Frame the required asset region with sufficient contextsuitable for the configuredstructure detector.and Dooutdoor notconditions. cropProtect downlow cameras from vehicle impact. Keep the camera and cables outside vehicle clearance and pedestrian routes. Provide safe maintenance access. Fit weatherproof glands, connector protection, strain relief, and drip loops. Follow the hardware instructions for power, grounding, and surge protection. Tighten fixings to isolatedthe lettersmanufacturer's withoutspecification, SiteTrax.iosecure confirmingcables, thatand label the detectorcamera canand operatenetwork on that view.connection. UseClean opticalthe lenslens/window. selectionRecheck orframing opticaland zoomfocus toafter obtaintightening; usable text detail. Enlargingsave a low-resolutionreference preview with digital zoom does not recover missing character strokes.image. Inspect individual frames from the actual saved/uploaded video at native pixel size.

4. Check themoving smallestimages in daylight and mostdarkness

distant required text, not only the largest identifier near the center.

• MeasureBlurred charactermoving heighttext: inshorten pixels and record it for SiteTrax.io review. Check edge distortion and foreshortening as well as pixel count.

Focus on the target marking within the capture zone. Verify the near and far limits remain sharp, and repeat under night illumination. If autofocus hunts between vehicles, agree a stable focus configurationexposure with the camera supplier or SiteTrax.io; add suitable light if the result becomes too dark. 30 fps alone does not prevent blur. Washed-out text or glare: adjust lighting position/output and SiteTrax.io.exposure. Check actual painted and reflective markings. Dark

or uneven text:

 illuminate the complete capture zone and retest at night. Check focus after day/night switching. IllustrativeGhosting sizingor calculation:bands: review WDR and lighting flicker settings with athe 1080-pixel-highsupplier, imageusing coveringrecorded 3.0moving mfootage. vertically at a flat, face-on target plane, a 0.10 m character occupies approximately 1080 × 0.10 / 3.0 = 36 pixels. At a 6.0 m vertical field it occupies about 18 pixels. This estimates sampling only; perspective, compression, lens quality, focus, and motion can still prevent a read. See

The EdmundGate Optics: Resolution.

Cognex's OCRMaxlighting guidance illustratesprovides whya OCRstarting systemsarrangement. specifyLamp characteroutput size in pixels. Its product-specific recommendations mustis not bea adoptedmeasurement asof SiteTrax.iolight reaching the marking; acceptance thresholds.depends on the recorded result.

Simulated image-quality examples, not SiteTrax.io detections or OCR test results.

Inspect

5. actualCommission: recordedcompletion frameschecklist

at

Copy this checklist into the expectedinstallation speedrecord. Tick each item only when its evidence is available.

☐ Position: final lens height, distance, lane offset, camera/lens model, and installation photos recorded. ☐ Coverage: every required marking remains visible across normal vehicle positions; each lane and direction tested. ☐ Image quality: saved moving clips checked in daylight and darkness at night.

4. Control motion and illumination together

Speed, shutter, and recording duration

For fixed Gate installations, the Gateagreed guidemaximum recommendsspeed; trafficno atblocking 10blur, mph (16 km/h)glare, or below, using suitable site traffic controls. Position the read zone where the intended speed is actually achieved. A vehicle accelerating after a stop or bouncing on a speed bump may still produce unusable frames.

Frame rate and exposure are different. Thirty frames per second describes how often images are captured; shutter time describes how long each image gathers light. A 30 fps video can still contain motion-blurred text. Shorten exposure until moving character edges remain distinct, then provide enough illumination for that exposure. See Edmund Optics: Camera sensors, frame rate, and shutter speed.

Illustrative motion calculation: for lateral movement of 4.47 m/s (10 mph) across a target plane spanning 4 m over 1920 pixels, image motion is approximately 2,146 pixels/s. At 1/1000 s exposure, motion during exposure is about 2.1 pixels; at 1/250 s it is about 8.6 pixels. This is a simplified transverse-motion example, not a recommended shutter setting. Approach motion, perspective, and camera movement require separate evaluation.

Coordinate event detection, pre-event recording, post-event recording, and clip segmentation with SiteTrax.io. Capture must start before the identifier enters the usable zone and continue until the required views are recorded. Test slow traffic, stopping, reversing, and closely spaced vehicles. The theoretical available frames are frame rate × usable path length / speed; frames outside the focus or exposure limits do not count as useful evidence.

Lighting for painted and reflective text

The existing Gate guide recommends a 5,000-lumen, 7,000 K LED light positioned approximately 20 ft from the scanned objects. Use that as a published starting recommendation, then validate the actual installation. Lumens describe total light output; they do not specify the illumination reaching a marking. Beam spread, angle, distance, surface reflectance, weather, and exposure determine the result. There is no universal lux target established here.

Illuminate the entire usable capture zone, including low chassis text and the extremes of the lane. Aim lights to avoid hard shadows from door hardware and underframes.clipping. Keep☐ the light source out of the camera's direct view and manage driver glare. Test on wet surfaces and light-colored as well as dark assets. Inspect recorded moving text for flicker bands, bright hotspots, clipped white areas, and noise. Select lighting and exposure settings that work together; a visually bright scene is insufficient. Test the actual painted, printed, or reflective markings under the intended visible/IR lighting. Do not assume an IR plate illuminator will preserve contrast on every painted asset identifier. Check daylight, dusk, night, and day/night switching. Retest after changing illuminator position, intensity, camera exposure, or lens settings.

Retroreflective plates return light toward its source, so Axis recommends placing external IR illumination near the plate camera. Excess illumination or gain can wash out plate characters. Axis also warns that some WDR implementations create motion artifacts; disable WDR or use a suitable motion-safe mode for plate capture according to the camera manual. These plate-specific choices need separate validation for other markings. Source: Axis: License plate capture.

The AXIS Q1800-LE manual provides examples of balancing shutter, gain, focus, and illumination. Follow the manual for the camera actually installed; its menu names and numerical defaults are not SiteTrax.io-wide settings.

5. Install the fixed mounting hardware

Use a qualified installer for the structure, electrical work, and access equipment involved. Follow the selected camera, bracket, enclosure, and power equipment instructions. This procedure does not specify structural loads, anchor sizes, torque, or electrical protection for an unknown installation.

Prepare the work area.Delivery: Coordinatetest a lane closure or controlled work zone. Keep personnel and equipment clear of vehicle paths, gate movement, and overhead hazards. Verify the support. Use a rigid surface suitable for the complete camera, bracket, enclosure, lighting, and environmental loads. Avoid loose fencing, flexing sheet metal, or vibrating machinery as unassessed supports. Mark the verified position. Transfer lens-center height, setback, and direction from the successful trial. Check service clearance and the full vehicle swept path before fixing the bracket. Install the bracket. Use manufacturer-approved fasteners and anchors appropriate to the substrate. Tighten to the specified torque. Install any required safety retention. Do not guess a torque value. Fit and aim the camera. Set pan, tilt, roll, zoom, and focus while viewing the intended recording profile. Tighten adjustment locks and recheck the view after tightening; the aim can move. Protect a low mount. Locate collision protection so it protects the camera without blocking the low identifier or restricting traffic clearance. Preserve safe access for lens cleaning. Weatherproof correctly. Use the approved outdoor enclosure, cable glands, seals, and junction boxes. Match glands to cable diameter, seal unused entries, and retain required drainage or ventilation. Arrange cable entries and drip loops to keep runoff away from connectors in accordance with the equipment instructions. Route and secure cables. Provide strain relief and a controlled service loop. Protect cable from abrasion, pinching, wheels, sharp edges, and moving gates. Use cable and conduit suited to the environment, observing the equipment's bend-radius and separation requirements. Verify power and connectivity. Confirm supply/PoE compatibility and total demand, including lights or heaters where applicable. Follow manufacturer requirements for grounding, bonding, and surge protection. Test the installed cable path and network connection under operating load. Record the installation. Label camera and cable ends. Photograph the bracket, camera aim, cable entries, lights, and final field of view. Retain the camera model, serial number, firmware, lens, and final settings in the handover record.

6. Adapt the installation for Drive, Mobile, and Snap

SiteTrax.io Drive

Follow the Drive Installation and Usage Guide for the supplied exterior camera, magnetic mount, USB connection, tablet dock, and vehicle power connection.

Choose an exterior view of the required asset faces. Keep wipers, antennas, vehicle bodywork, reflections, and load attachments out of the capture area. Confirm the supplied mount is appropriate for the actual surface and operating conditions. Check attachment before each run and after a knock; do not assume a magnetic mount is suitable for every panel or speed. Route cables clear of steering, pedals, doors, airbags, and moving parts. Secure the tablet and dock without obstructing the driver. Confirm the live camera view before moving. Set up and operate recording while safely stopped, or use an appropriate passenger/operator procedure. Test the intended route, offset, turns, surface vibration, and relative speed. Change route or speed where identifiers blur or disappear. The fixed Gate mounting heights are not a Drive mounting specification. Verify recordings finish uploading, including after returning to Wi-Fi coverage. Arrange continuous-capture access and training through SiteTrax.io as described in Capture — Android.

Mobile and Snap

For handheld or temporarily supported capture, stand in a safe permitted position with a clear view of the asset and required identifier. Hold the device steady, keep the lens clean, avoid digital enlargement as a substitute for suitable distance, and verify focus and glare in the preview. Include the complete marking and enough asset context for detection.

Snap is documented for three-second, single-asset captures. Use the Snap tutorial to check the preview and upload workflow. Continuous yard scanning belongs to the enabled Android Capture workflow. Do not extrapolate fixed-camera lens dimensions to a phone without confirming the capture device with SiteTrax.io.

7. Confirm SiteTrax.io ingestion and project setup

A readable local preview is only the first check. The delivered video must preserve the same useful detail andvideos reach the correct processing configuration.

ConfirmSiteTrax.io project andwith camera identity,the required processing types, capture coordinates,timestamp and directionlocation interpretationinformation. Follow Input Video and the BYOC guide. ☐ Results: compare known identifiers with SiteTrax.io. Record changes using the principlesactual in Organization Configuration. Verify the delivered MP4 follows API — Input (Video): recommended 1080p/30 fps, clips no longer than the recommended one minute, required creation-time metadata, and GPS subtitle data or the agreed static-camera override. Confirm codec and any deviations during integration. For BYOC, test the agreed S3 upload path and processing flow using the BYOC guide. Camera/network compatibility alone does not prove ingestion compatibility. Verify sustained upload capacity during busy periods. Check whether buffering and recovery are supported by the selected equipment, then test the agreed recovery procedure for an upload interruption. Review the resulting video and asset recordresults in SiteTrax.io Intelligence. UseVerify Navigatingentry/exit theclassification Intelligencewhere Interfacerequired. ☐ Acceptance: record tested passages, correct reads, incorrect reads, and no reads for Videos,each Assets,identifier project/date filters,type and recordtest feedback.condition. If downstream delivery is in scope, verify a real commissioned detection arrivesCompare with the expectedagreed fieldstargets; atlog exceptions and sign-off. ☐ Handover: save final settings, reference clips, site sketch, support contacts, and the configuredcleaning/inspection destination. Refer to API — Output (JSON) for integration details.

For entry/exit uses, test each actual direction and reversing separately. Camera/project designation and image-relative heading are different evidence. Follow Gate Operations for direction mapping and pairing; a name such as “North Gate” does not establish direction.

8. Commission with representative traffic

Agree the sample size and pass criteria with SiteTrax.io before testing. Use real assets with independently verified identifiers. Include both routine and difficult conditions; a parked daytime example is not sufficient to accept a moving, day-and-night installation.

Test group Include Record Coverage and geometry Every lane and direction; near/far and left/right positions; required asset families, text heights, and orientations. Complete target visibility, pixel size, focus, obstructions, and usable capture zone. Motion Normal and maximum agreed speed; stop/start; reversing; close following and adjacent traffic where applicable. Blur, capture timing, missed passages, repeated results, and direction correctness. Lighting and environment Day, low sun/backlight, dusk, night, headlights, and relevant wet or adverse conditions when available. Exposure, glare, shadows, flicker, day/night transitions, and any condition not yet tested. End-to-end processing Upload, processing, image/video evidence, project/camera attribution, coordinates, timestamps, and configured downstream delivery. Source clip and detection references, exact expected/read identifiers, processing outcome, and delivery failures. Operational recovery Approved restart or connectivity-recovery test and post-maintenance aim check. Return to capture, upload recovery, preserved settings, and exceptions requiring intervention.

Keep an independent passage log with expected identifiers and asset types. Compare it with source clips and processed results. Separate these measures and publish their denominators:

Capture coverage: eligible physical passages with usable identifier evidence divided by all eligible passages in the test log. End-to-end correct identification: eligible passages with the complete correct required identifier in SiteTrax.io divided by all eligible passages. Where two identifiers are required, record both individual and paired outcomes. Read correctness: independently verified correct returned identifiers divided by the returned identifiers assessed, with the treatment of repeated readings stated. Exceptions: missed capture, unreadable text, wrong identifier, incomplete required pair, duplicate handling, incorrect direction, and upload/processing failure reported separately.schedule.

Acceptance record: Project/camera ___ · Identifier type ___ · Condition/speed ___ · Tested ___ · Correct ___ · Incorrect ___ · No read ___ · Target ___ · Result ___ · Date/approver ___.

Do not label the share of A0 records as OCR accuracy. A0 indicates acceptance under processing rules, not independently verified truth. Ause stored row iscounts notor necessarilyan aA0 uniquestatus physicalas passage,proof andof combinedaccuracy. processing can include synthetic pair records. ApplySee How Intelligence Usesuses SiteTrax.io Datadata. whenFor assessingmissing outcomes.

Resolve failed cases and repeat the affected tests. Record exclusions rather than silently removing difficult assets. If an essential condition cannot be tested, identify that limitation and the required follow-up before declaring full acceptance.

9. Troubleshoot the image before changing OCR rules

Symptom Check first Corrective action Identifier too smalluploads or missingresults, at an edge Native recorded frames, lane extremes, lens and view width. Reposition or adjust optical framing; add a dedicated view if context and text detail cannot coexist. Sharp when stopped, blurred when moving Exposure time, actual speed, vibration, and lighting. Shorten exposure, improve light, stabilize the mount, or reduce speed; retest moving traffic. One distance sharp, another soft Focus and required depth of field. Refocus or redesign the usable zone/lens configuration. Verify near and far limits. Night failures only Saved night video, illumination coverage, reflective hotspots, contrast, and focus. Adjust light position/output and exposure together. Test real markings after day/night switching. Ghosted or banded characters WDR, lighting flicker, and image processing. Test appropriate camera modes and lighting settings with the supplier; compare moving recorded frames. Intermittent occlusion Queueing, adjacent lanes, gate hardware, and asset structures. Move the capture zone or provide another view; tuning cannot reveal hidden text. Readable local video, no expected record Upload completion, delivered format/metadata, project configuration, access, and date filters. Followuse the Troubleshooting Guide.

Other capture methods and BYOC/APIongoing ingestion checks.

Wrong entry/exit classification Actual movement, heading, role designation, and direction mapping. Review configuration with SiteTrax.io and retest both directions and reversing.

For escalation, provide the project, camera model/identity, timestamp and timezone, expected identifier/type, source clip or detection reference, a sample failed frame, current settings, and installation photos through the approved support channel. Do not include passwords, tokens, access keys, or secrets.

10. Handover and maintenancechecks

Before

handover, retain the site sketch; camera/lens inventory; final mounting heights, offsets, distances, and angles; recording and exposure settings; day/night sample clips; lighting arrangement; network/power details; direction mapping; commissioning log; agreed acceptance criteria; unresolved limitations; and customer/SiteTrax.io ownership contacts.

The customer owns site infrastructure and physical camera maintenance. SiteTrax.io provides processing, orientation/detection advice, and camera-tuning guidance; upgrade and remote-management responsibilities must

Vehicle-mounted: follow the agreedDrive deploymentinstallation model.guide Seefor mounting, cabling, and power. Check vibration and moving footage; the fixed Gate responsibilitiesheights above do not apply. Handheld: follow Capture Android or Snap. Keep the required markings complete, steady, and BYOCwell responsibilities.

lit. SetMaintenance: ainspect site-specificcleanliness, inspection schedule for lens/window cleaning,alignment, fasteners, alignment, seals, cable protection, illuminators,cables, and vegetationlights oron newthe obstructions.agreed Recheckschedule. Repeat affected tests after impacts,impact, storms,relocation, maintenance,or changes to lightingcamera settings, lighting, or lane geometry, firmware changes, and camera replacement. Compare the current view with the accepted reference image and repeat affected day/night moving tests after changes. Review capture gaps and exceptions routinely. A reduction in stored activity is a reason to investigate, not proof of a hardware outage. Maintain a manual exception process for missing, damaged, obscured, or otherwise unreadable markings. OCR cannot reconstruct evidence that the camera did not capture.layout.

SourceReference notes

Reviewed 23 September 2026. SiteTrax.ioExternal productguidance and deployment statements above are linked tosupports the applicable documentation at the point of use. Current Intelligence guidance is used for application navigation and record interpretation; the retired service portal is not the commissioning destination.

External references provide imaging principlesapproach: andPlate manufacturer-specificRecognizer examples,camera not certification of a SiteTrax.io deployment:setup, Axis licensemounting plate captureguidance; AXIS Q1800-LE manual; Edmund Optics resolution; Edmund Optics camera sensors;, and CognexVisy OCRMaxTruck configurationOCR Portal. TheTheir applicableproduct-specific hardwareheights, manualsangles, speeds, and theaccuracy project-specificclaims are not SiteTrax.io acceptance plan govern the final installation.limits.