1 Package Contents
| Item | Qty | Notes |
|---|
| Camera | 1 | Taiwan licence-plate box camera or bullet camera, as ordered |
| Power adapter | 1 | DC 12V, DC 5.5-2.1 mm connector |
| Mounting bracket | 1 | Matched to the form factor |
| User manual | 1 | Electronic version only; all products ship with an electronic manual |
Check that the packaging is intact and all items are present. If anything is missing, do not install the device and contact support. All products ship with an electronic manual only.
2 Before Installation
2.1 Choosing the position
| Mounting height | 3 m ~ 3.5 m for car lanes (above or beside), tilt 10° ~ 25°; 2 m ~ 2.5 m for motorcycle or mixed lanes |
| Recognition distance | Vehicle 3 m ~ 8 m from the lens; plate area at least 1/8 of the frame height |
| Field of view | Lens along the direction of travel, plate facing the lens, no large side angle |
| Lighting | Avoid direct headlight glare; provide fill light at night entrances and avoid strong backlight |
2.2 Mounting differences
| Item | Box camera | Bullet camera |
|---|
| Position | Wall, door frame, pole | Crossbeam, bracket, fence pole |
| Angle adjustment | Front tilt plus side fixing | Adjustable bracket tilt |
| Cabling | Lead cable, neat wall routing | Rear cable entry, keep water-tight |
2.3 Installation steps
| Step | Action | Content |
|---|
| 1 | Confirm the position | Check position, angle and cable route on site; aim the lens along the direction of travel |
| 2 | Fix the bracket | Fix the bracket to the wall, pole or crossbeam with expansion bolts; make sure it is level and firm |
| 3 | Mount the camera and route cables | Fit the camera to the bracket, set tilt and pan, then tighten; connect the RJ45 cable and the DC 12V power lead and secure the cables with ties |
| 4 | Power on and aim | The indicator lighting up means power is on; open the web UI, check the live view, confirm plates are sharp and unobstructed, and fine-tune the angle |
Safety: power off before removing the sunshield or protective cover; after installation check the water-tight connector seals; IP66 allows rain but not immersion; run cables through conduit beside the lane so vehicles cannot catch or crush them.
3 First-Time Setup
The device is configured through its web UI from a PC, tablet or phone. Google Chrome is recommended on a PC.
Quick preview: the LAN playback address is http://[device IP]/open/live-play/?a=1 (a=1 is channel 1, and so on), which previews the image directly in a browser.
3.1 Tuning plate recognition
| Symptom | Action |
|---|
| Plate unreadable | Adjust the focal length or the device position so the plate covers at least 1/8 of the frame height |
| Headlight overexposure | On the bullet camera, check the sunshield is fitted; adjust the angle away from direct headlights |
| Poor recognition at night | Add ambient light or fill light at the entrance; make sure day/night mode is set to auto |
| Wrong results on angled plates | Large tilt or side angles distort characters; adjust the mounting angle so the plate faces the lens |
| Flickering detection box | Caused by vibration; check the bracket is firm and the lane surface is stable |
| Numbers often misread | Usually the plate is too small, too far or dirty; shorten the distance and clean the lens, then retry |
3.2 Setup steps
| Step | Action | Content |
|---|
| 1 | Check connectivity | The PC and the device must be on the same switch or router |
| 2 | Find and change the device IP | Use the Device Search Tool (download link from our sales team). If the device is not found, tick "Force search" in the tool |
| 3 | Open the login page | Enter the new device IP in Chrome to open the web login page |
| 4 | Log in | Use the factory default account, then change the default password immediately |
| 5 | Set the system time | Click "Sync with PC time". The device time cannot be set manually and can only be obtained by syncing |
| 6 | Set the image orientation | In Settings → Image Rotation choose the correct orientation to avoid an upside-down image |
| 7 | Confirm resolution | The main stream defaults to 2560×1440 and can be switched to 1920×1080 / 1280×720 |
4 Status Overview
The configuration UI has two panes: the function menu on top and the content pane below. After logging in you land on Status Overview, which shows how the device is running.
| Device information | Serial number, firmware version, uptime |
| Network information | Local IP address, network status |
| Utilisation | CPU and memory usage |
| Storage | Free space on the SD card or disk |
| Language | Chinese / English UI switch |
4.1 System time sync
Clicking "Sync with PC time" sets the device time to that of the connected PC. The time cannot be set manually; after a power cycle, sync again if it drifts. Snapshot and recording timestamps rely on the system time, so make sure it is accurate.
Performance note: do not exceed the hardware capacity for concurrent RTSP pulls; CPU usage should stay below 90%.
5 Web UI Reference
The channel settings page configures the video source address, push address, recording switch, HLS switch and snapshots for each channel.
| Channel switch | Enable or disable pulling for a channel; multi-select for batch switching |
| Channel preview | Preview the configured source; available stream URLs are shown below the image |
| Video source | Set the source stream address; ONVIF cameras can be found with the search button |
| RTMP push address | The push address provided by your streaming provider |
| RTMP push switch | Enable or disable pushing |
| Recording switch | Enable or disable recording of the video source |
| HLS switch | Enable HLS output (some streaming platforms depend on it) |
| Source format | Shows H.264 / H.265; most platforms only accept H.264 for RTMP push |
| Pull / push bandwidth | Bitrate of the source and of the RTMP push |
| Snapshot settings | Snapshot switch, upload address and interval (requires UI version ≥ 1.20.0.27) |
| Advanced | Compatibility mode for the source, audio source, UDP and similar options |
5.1 Snapshot upload API
| Upload URL | http://[IP]/upload?id=xxx&channel=xxx&filename=snap_0.jpg |
| Method | POST, Content-Type: multipart/form-data |
| Parameter id | Device serial number |
| Parameter channel | Channel number, starting at 1 |
| Parameter filename | Uploaded file name |
| Local snapshot URL | http://[device IP]/tmp/snap_0.jpg (snap_0 is channel 1, and so on) |
| Remote snapshot URL | http://[serial].[cloud domain]:9502/tmp/snap_0.jpg |
Note: for other formats or to deliver snapshots to another platform, contact our sales team for custom development.
6 Network Configuration
6.1 Wired network
Single-port devices: with DHCP enabled the router assigns an address (not fixed); disable DHCP to set a static IP. Dual-port devices: eth0 is the WAN port and eth1 the LAN port.
Note: eth0 and eth1 must not be on the same subnet. Before configuration the fixed IP is 192.236.192.15, and the eth1 LAN port cannot be found by the Device Search Tool.
6.2 WiFi and 4G
| WiFi | 2.4 GHz only, no 5 GHz |
| 4G and WiFi | Choose one; they cannot be used together |
| SIM card | 4G only, no 5G; China Mobile / Unicom / Telecom supported |
| APN SIM | Not supported |
| IoT SIM | Unrestricted IoT SIM cards supported |
| Directional SIM | The carrier must open the required domains and ports and whitelist them |
| Overseas SIM | Supported; set the matching APN |
6.3 Cross-subnet access
WebRTC cross-subnet viewing is supported through protocol traversal on the cloud platform. Once traversal is in place, one terminal can view across subnets without data charges; without it, traffic is relayed by the cloud platform and incurs data charges, with no limit on the number of terminals.
7 Video Sources and ONVIF
7.1 ONVIF search
| Step | Action | Content |
|---|
| 1 | Pre-checks | The camera and the device must be on the same LAN, and ONVIF must be enabled on the camera |
| 2 | Search | Click the Search button next to the source field; the device scans the LAN for ONVIF IP cameras |
| 3 | Authenticate | Select the camera, click Get Stream, and enter the ONVIF user name and password |
| 4 | Save the stream | After validation the stream indices appear: 0 = main stream, 1 = sub stream, 2 = third stream; pick one and click Save to Channel |
| 5 | Check details | Review bitrate, frame rate and resolution in Stream Details |
Common failures: ① the camera and the device are on different subnets; ② ONVIF is not enabled on the camera; ③ SmartH264 / SmartH265 is enabled on the camera and must be turned off, otherwise the camera cannot be found.
7.2 Device capabilities
| Interface protocols | ONVIF, GB28181; compatible with Hikvision VMS-4200 |
| NVR compatibility | Hikvision, Dahua and other mainstream recorders |
| Remote control | Remote start / stop of recording, snapshot control and capture |
| Motion-detection callback | Not exposed via SDK in the standard version; only remote video retrieval |
| Orientation switch | Supported but not automatic; set manually in the web UI |
| Scheduled snapshots | Scheduled JPG snapshots uploaded to a cloud server |
| Secondary development | HTTP API with full documentation |
8 Recording and Storage
8.1 Storage options
| SD card | Expandable storage, sized by capacity and retention days |
| NVR | Central storage on an NVR |
| Cloud storage | Separate integration and billing; Alibaba Cloud / Tencent Cloud; other providers require assessment |
| NAS | Not supported in the standard version; custom integration billed separately |
8.2 Recording behaviour
| Continuous recording | Round-the-clock recording supported |
| Overwrite | When storage is full the oldest files are deleted automatically; recording never stops |
| Retention | Actual days depend on card capacity, bitrate settings and scene activity |
| Remote control | Start or stop recording remotely from the web UI |
Estimate: at 4 Mbps for the 2560×1440 main stream, a 32 GB SD card holds about 17 hours and a 128 GB card about 70 hours. Actual figures depend on encoder settings and scene activity.
9 GB28181 Platform Integration
The camera registers to a GB28181 server as a client so that the platform can manage it centrally.
| Step | Action | Content |
|---|
| 1 | Get platform parameters | Obtain the SIP service settings from the GB28181 server |
| 2 | Fill in the settings | Enter the SIP server address, transport protocol, SIP ID, SIP domain and related fields |
| 3 | Save and register | After saving, the device registers with the GB28181 server |
| 4 | Verify | Once registered, the device appears in the server device list |
Note: acting as a GB28181 server (platform side) is supported only by streaming-server products; this camera only supports registering to a GB28181 platform.
10 FAQ
10.1 Taiwan plate recognition
| Question | Answer |
|---|
| What is the recognition accuracy? | An optional algorithm capability; figures are provided after the algorithm version is confirmed commercially |
| Which plates are supported? | Taiwan new and legacy car plates, motorcycle plates and E-prefix EV plates; see Appendix A |
| Can it read motorcycle plates? | Yes. Motorcycle plates are smaller, so keep them large enough in frame and shorten the recognition distance |
| Do heavy motorcycle yellow / red plates work? | Black on yellow and white on red plates are within range; validate on site |
| What about damaged or obscured plates? | The rate drops sharply; badly damaged plates may produce only a snapshot with no number |
| What vehicle speed works? | Low-speed traffic (≤ 20 km/h). There is no strobe fill light, so high-speed capture needs a dedicated plate-capture device |
| Recognition is poor at night? | Add ambient or fill light and avoid pointing the lens into headlights |
| Can it do whitelist checks or barrier control? | The device outputs results; whitelist comparison and barrier control are implemented on the platform side and require custom integration |
| Which fields are in the result? | Plate number, confidence, snapshot and timestamp; extra fields depend on the API documentation |
| Can snapshots go to my own server? | Yes. Set the upload address in the snapshot settings; JPG over HTTP POST |
10.2 Product and system
| Question | Answer |
|---|
| What operating system does the camera run? | Linux |
| Is secondary development supported, with documentation? | Yes, over an HTTP API with full documentation |
| Is portrait resolution supported? | Yes, switched manually in the web UI; it is not automatic |
| The image is upside down, how do I fix it? | Settings → Image Rotation, then choose the correct orientation |
| Can the resolution be changed? | Yes, the main stream supports 2560×1440 / 1920×1080 / 1280×720 |
| Can the device time be set manually? | No, only by syncing with the PC time |
| What is the operating voltage? | Above 10.8 V and below 13.2 V |
| How much power does it draw, and how long will a battery last? | Around 12V / 100mA; a 30000mAh battery lasts about 30 hours |
| Is there a Bluetooth interface? | No built-in Bluetooth in the standard version; an external module can be added |
| Are there IO pins on the board? | Yes, TTL and IO |
| Is the power connector DC 5.5-2.1? | Yes |
10.3 Network and streaming
| Question | Answer |
|---|
| How do I push to my own server? | Generate an RTMP push address on the server and enter it in the channel settings |
| What does my server need? | RTMP support |
| Can it push to a locally deployed streaming server? | Yes |
| Is RTSP push supported? | No; the push protocol is RTMP |
| Is it compatible with Hikvision or Dahua recorders? | Yes |
| Do the 4G and WiFi models have a wired port? | Yes |
| Does 4G also support WiFi? | No. 4G and WiFi are mutually exclusive (4G SIM only, WiFi 2.4 GHz only) |
| Is WebRTC cross-subnet viewing supported? | Yes, with protocol traversal on the cloud platform. With traversal, one terminal can view across subnets at no data cost; without it, the cloud relays traffic and data charges apply, with no limit on terminals |
| The camera cannot be found, what should I check? | Check the subnet, whether ONVIF is enabled, and whether SmartH264 / SmartH265 is turned off; or tick Force search |
10.4 Storage and features
| Question | Answer |
|---|
| Which storage options are there? | SD card; NVR. Cloud storage requires separate integration and billing (Alibaba Cloud / Tencent Cloud); other providers require a cost assessment |
| Continuous recording? How many days? Does it overwrite? | Continuous recording is supported; retention depends on card size, and the oldest files are overwritten automatically |
| Can recording be started and stopped remotely? | Yes |
| Can it store to a NAS? | Not in the standard version; custom integration billed separately |
| Can it upload scheduled snapshots to a cloud server? | Yes, as JPG |
| Is there snapshot control? | Yes |
| Is motion-detection alarm with SDK data supported? | Not currently; only remote video retrieval |
| Is there a cloud platform? | Yes, a test link is available |
10.5 4G and SIM cards
| Question | Answer |
|---|
| Are there SIM restrictions? Do IoT or directional SIMs work? | Unrestricted SIMs work, including logistics IoT SIMs; directional SIMs require the carrier to open and whitelist the relevant domains and ports |
| Does the 4G camera support APN SIMs? | No APN SIMs; ordinary unrestricted SIMs only |
| Do overseas 4G data SIMs work? | Yes, with the matching APN |
| How is the 4G SIM billed? | Per carrier plan, as quoted by our sales team |
| How do I check data balance and top up? | Bind the SIM number or ICCID in the device management mini app; the app name is provided by our sales team |
11 After-Sales and Warranty
11.1 Terms
| Warranty | As agreed in the commercial contract |
| Manual format | Electronic manuals only for all products |
| Returns | Per the returns policy on the product page |
11.2 Support channels
| Manuals and FAQ | docs.xvipcloud.com |
| Device Search Tool | Download link from our sales team |
| Developer documentation | docs.xvipcloud.com |
| Business contact | Contact our sales team |
11.3 Routine maintenance
| Lens cleaning | Wipe the lens regularly; dust and rain residue affect recognition |
| Water-tightness | Check the connector seals before and after the rainy season |
| Time check | After a power cycle, check the system time and re-sync if needed |
| SD card check | Check card health regularly; SD cards are wear items |
| Cable protection | Run cables through conduit beside the lane to avoid knocks and crushing |
| Ventilation | Do not enclose the device; ensure airflow under long high-load operation |
Appendix A Plate Styles and Recognition Range
Taiwan has issued new-style plates for all cars and motorcycles since December 2012, using a three-letter prefix plus four digits. Legacy plates issued from 1992 are still in wide use. The recognition range is as follows.
A.1 Recognition range
| Plate style | Format | Example | Notes |
|---|
| New-style car plate | 3 letters + 4 digits | ABC-1234 | 380 × 160 mm; black on white for private cars, red on white for some commercial categories |
| New-style motorcycle plate | 3 letters + 4 digits | ABC-1234 | Smaller than a car plate; black on white for ordinary heavy motorcycles |
| Heavy motorcycle plate | 3 letters + 4 digits | ABC-1234 | Black on yellow (over 250 cc), white on red (over 550 cc) |
| Legacy car / motorcycle plate | 2~3 letters and 2~4 digits, position varies | AA-1234 / AAA-123 / 123-AAA | Issued from 1992; still widely in use |
| EV plate | E-prefix and other dedicated ranges | EAB-0001 | Dedicated ranges for electric cars and motorcycles, including white on green styles |
A.2 On-site notes
| Plate condition | Dirt, distortion and decorative frames lower the rate sharply; badly damaged plates may only be snapshotted |
| Camera angle | Large tilt or side angles distort characters; keep the plate facing the lens |
| Plate size | Below 1/8 of frame height characters cannot be read; shorten the distance or use a longer focal length |
| Vehicle speed | ≤ 20 km/h recommended; high-speed capture needs a dedicated plate-capture device |
Scope: plate styles and formats follow the current rules of the Taiwan region transport authority. Special plates (temporary, test, diplomatic, brown classic-vehicle plates and similar) are outside standard recognition; validate on site.