CS-I8XQ II-2.8mm and CS-I5XQ II-2.8mm: Gen-2 Active Deterrence Camera

Quick answer: The published CS-I8XQ II-2.8mm and CS-I5XQ II-2.8mm specifications describe 8MP/5MP imaging, up to 50 m IR, 30 m white light, red/blue warning lights, a microphone and speaker, and card support up to 1 TB. Check the supplied revision, firmware and client before promising a rule or warning workflow. Illumination distance is not identification distance, card capacity does not prove a card is included, and a warning does not guarantee that an incident stops.

On this page

What changed from Gen 1 to Gen 2?

The current catalog compares I and II configurations on physical pages 17–18. Page 17 clearly labels the 5MP models; page 18 repeats an I heading above the 8MP columns. The separately named CS-I8XQ II-2.8mm data sheet, SPEC:V5, corroborates the II model and its figures below. Do not treat the duplicated catalog heading as a new SKU or use an I/II suffix interchangeably on a quote.

The comparison rows show 0.002 Lux, IP66, Metal housing, a microphone and speaker, Audio I/O 1/1 and Alarm I/O 1/1 across the four printed configurations. Compression, temperature and power are omitted from those comparison pages, but appear in the model-specific II data sheets discussed below. Use the ip camera user manual for the actual supplied model and revision when setting it up; a similar housing does not prove identical firmware or functions.

Choose the camera from the measured scene and the supported task. Confirm usable detail, backlight performance, illumination, warning behavior and recording capacity at the required distance. Neither the I/II label nor a longer quoted light distance proves that a person can be identified or that every analytic can run together.

How does EW deterrence work on these turrets?

EW and NightBright icons appear on the catalog comparison pages. The two II data sheets explicitly list Early Warning and sound/light linkage options. Start with the supported person/vehicle rule, then confirm how that particular firmware, NVR and client arm the rule and trigger the lights or speaker. Do not infer the same trigger options for every I model from a page-level icon, and do not equate EW with an independently certified life-safety function. A practical commissioning sequence is:

1. Draw the perimeter or tripwire zone on ground where nobody should be after hours, and keep it off public sidewalks and neighboring property.
2. Select supported human/vehicle filters for the actual rule, then test nuisance triggers such as wind, headlights, shadows and animals. Classification may reduce some unwanted alerts; it does not eliminate them. Confirm which pet filters the firmware permits.
3. Tie EW to an arming schedule: active at night and on weekends, quiet during business hours.
4. Choose a short voice message and test the volume at the edge of the zone.
5. Check the output before connecting another device. Both II SPEC:V5 sheets, physical page 4, list a TTL alarm output at 30 mA, 12 VDC. This is not evidence of a voltage-free relay contact or permission to drive a strobe or panel input directly. Confirm interface type, polarity, load and isolation with the revision-specific documentation and use an appropriate interface where required.
6. Agree a commissioning/observation period and review actual triggers with the customer. Record changes and acceptance; do not assume a fixed two-week delay is available on every job.

A microphone and speaker do not establish every talk-down, notification or warning workflow. Use the CASE Connect handover guide to plan a check with the actual camera, NVR, app and firmware. Test the required audio direction and permissions, and keep recording under the approved site policy. Android is available; iOS is forthcoming. Do not promise feature parity across clients or publish an unverified web-access URL.

Which analytics does Gen 2 print, and which need extra care?

The catalog’s second-configuration AI rows list Perimeter, Tripwire, Double Tripwire, Object Abandon, Object Missing, Heatmap, Loitering, Running, Parking, People Counting, Crowd Detection, Helmet Detection, On Duty Detection, Visible Light Smoke & Fire Detection, Fire Exit Occupancy Detection, Face Capture, and Human / Vehicle / Non-motor Vehicle / Pet Classification (Dog, Cat). The named II SPEC:V5 sheets also describe these function families across physical pages 3–4. A printed function is not proof of simultaneous availability, a particular notification path, or measured performance at your site. Match a supported function to the agreed task:

Smoke, fire and fire-exit analytics

Visible-light smoke, fire and fire-exit analytics analyze the image. These catalog and data-sheet entries do not establish approval to replace required fire detection, egress inspections or alarm systems. Treat them as supplementary operator alerts, verify the exact firmware and scene, and have the responsible life-safety designer review the proposed use under the locally applicable requirements.

Face capture

The II data sheets list detection of up to 32 faces and capture of up to 16 faces in a scene. Those are published feature limits, not a face-recognition accuracy guarantee or permission to collect biometric information. Read the facial recognition and privacy review before enabling a face-data workflow. Confirm the actual task, legal basis, access, retention and deletion process with the responsible reviewer, and test concurrent analytics on the supplied firmware.

Where should you mount them, and how do you handle audio?

• Height: choose a mounting height from the target distance, viewing angle, occlusion, tamper risk and safe servicing access. Check actual face detail in the recorded image at the proposed height; do not treat a general mounting-height rule as a guarantee for this lens or scene.
• Distance: 164 ft (50 m) IR and 98 ft (30 m) white light are maximum illumination distances, not identification distances. On a 2.8 mm lens, plan identification much closer; the IR range guide explains why.
• Light spill: aim the white light and the red and blue light at the protected area, not at a public road or a neighbor’s windows.
• Weather: IP66 is printed; still form a drip loop and seal the cable entry, and confirm a matching junction box per the spec sheet.

Decide separately whether the job needs a spoken warning, live talk-down, listening or recorded audio. Obtain the required site-specific privacy and legal review before enabling the relevant functions; a microphone specification is not consent. Record the agreed configuration and permissions, then test the actual firmware/client path. If audio recording is not approved, verify that it stays disabled rather than assuming the speaker setting controls it.

8MP or 5MP: which Gen 2 turret fits the job?

The published II maximum image formats are 3840×2160 for the 8MP model and 3072×1728 for the CS-I5XQ II-2.8mm. Both have a 2.8 mm lens, but their SPEC:V5 sheets list different horizontal views: 99.7° and 104.5° respectively, on physical page 2. Compare actual framing, required detail, lighting and recording load. More pixels alone do not establish better usable identification at the edge of a scene.

• Evaluate the 8MP option where the agreed task benefits from its pixel count; verify the recorded detail at the most difficult part of the actual scene.
• Evaluate the 5MP option against the same required detail and lighting test. Do not approve or reject it solely because the scene is called a door, yard or passage.
• Size the NVR from real stream bitrates against the recorder’s printed incoming bandwidth.

Spec table: CS-I8XQ II-2.8mm and CS-I5XQ II-2.8mm as printed

The CS-I5XQ II-2.8mm data sheet and the named 8MP sheet, both SPEC:V5, add details absent from the catalog comparison. Physical page 4 lists DC12V±25% for both: 8MP at max. 10 W DC / 11 W PoE, and 5MP at max. 9 W DC / 10 W PoE; both specify IEEE 802.3at for PoE. They list −40°C to 65°C and operating humidity ≤95% RH. These are published revision figures; confirm the supplied unit, power source, environment and required configuration before a project commitment.

What to tell your customer

Suggested customer wording, subject to the agreed scope: We will confirm the supplied model and test the supported person/vehicle rule, lighting and audio warning with the actual firmware and client. We will record the zones, schedule, permissions and acceptance results. Unwanted alerts remain possible, a warning does not guarantee prevention, and supplementary video analytics do not replace required fire protection. The proposal will identify the exact camera and written service terms.

FAQ

What is the difference between the CS-I8XQ II-2.8mm and the CS-I8XQ I-2.8mm?

The current 8MP catalog comparison shows 3840×2160 at 20fps in the first configuration and 30fps in the second, with 30 m versus 50 m IR and 15–20 m versus 30 m white light. Its duplicated I heading needs care. The explicitly named II SPEC:V5 sheet corroborates the II figures, 1 TB card support, red/blue light and TWDR. Confirm the actual I/II model and firmware; do not infer that every listed function is simultaneous.

Is EW deterrence available on both generations?

The catalog’s page-level EW icon does not establish every warning mode on every I/II device. The II SPEC:V5 sheets list EW and sound/light linkage options, while the active deterrence guide explains how to plan a warning task. Confirm the actual rule, arming schedule, light/audio modes and client behavior in the revision-specific documentation and a bench test before writing them into a proposal.

Can the smoke and fire detection replace a smoke detector?

No. A listed video smoke/fire analytic is not evidence that the camera can replace a required detector or fire alarm system. Keep it as a supplementary alert and have the responsible life-safety designer confirm its role, required equipment and locally applicable rules. Document the accepted limitation and the response process.

Should the built-in microphone be turned on?

Enable only the audio functions needed for the documented job and permitted under the site-specific privacy/legal review. Confirm listening, speaker/talk-down and recorded audio separately; approval of one does not automatically approve the others. Test the actual camera, NVR, client and firmware, and retain the approved settings in the handover record.

What warranty applies to these turrets?

The catalog pages show a six-year camera warranty badge. Use the warranty-by-category guide as an overview, then confirm the actual SKU/revision, written order terms, exclusions and service route before promising coverage. Warranty handling runs through the supplying installer or dealer; an end user should contact the company that supplied the system. Camera coverage, recorder/hard-drive terms and any separately agreed onsite service are distinct commitments.

References

• Current CASE catalog and revision-specific manuals
• Confirm a model, configuration or integration
• ONVIF Conformant Products database