PJLink Class 1 vs Class 2: Specify Capabilities Without Assuming Them

Choose PJLink Class 1 or Class 2 by the operations your installation needs, then verify those operations on the exact projector and controller combination. A Class 2 label is useful procurement information, but it does not replace an input map, an authentication compatibility check or a test of status delivery through the installed network.

For an integrator, the practical output is a capability matrix. It should separate mandatory opening and closing controls from convenience features so that a mixed fleet remains usable when a particular model lacks a nonessential function.

Translate a class label into project requirements

The Epson EB-PU series specification, section 3.4, separately lists Class 1 control and query operations and Class 2 search, notification and additional information operations. Use that arrangement to ask targeted questions rather than copying the entire table into a specification.

For example, a control panel might need power status on all projectors, while a service dashboard benefits from serial numbers and software versions. Those are different acceptance requirements. A device that meets the first requirement should not silently be displayed as defective because a diagnostic enhancement is absent.

This table is a suggested project worksheet, not a declaration of SoftControl protocol support.

Test the common operating baseline first

Commission one projector manually before enabling automatic discovery. Confirm its address, identity, authentication settings and a read-only query. Epson's wired-network instructions show that network addressing and the PJLink password are explicit setup tasks; a class declaration does not configure either of them.

Run the essential operations with notifications disabled or unavailable. This establishes the polling fallback you will need when network policy prevents unsolicited device messages. Then enable advanced behavior individually. Record whether a missing response means unsupported, unavailable in the current power state, or simply not received.

Do not assume that discovery and control traverse the same permitted path. A network team may deliberately restrict discovery traffic between segments. That decision can coexist with fully working addressed control, so specify manual device enrollment as an operational fallback when appropriate.

Handle differences without hiding them

Label capability gaps clearly in the configuration. An unavailable field should appear as unsupported or unknown, rather than as a zero value. Cache stable identity information separately from operational state so a temporarily unreachable projector does not lose its asset identity.

When swapping a model, validate input mapping and mute behavior again. The connector name printed on the chassis is not a universal protocol parameter. Controller support for Class 2 discovery also does not prove support for every Class 2 query or notification type.

Acceptance for a mixed fleet

Test at least one unit of every model and firmware combination intended for deployment. For each, save the working baseline, unsupported enhancements, authentication mode, standby behavior and recovery after a controller restart. Disconnect notification delivery during the test and verify that the operator still receives an honest state indication.

Turn the capability matrix into a replacement approval checklist. When purchasing changes a projector model, review every required operation before accepting it as equivalent. Include what the controller actually implements, not just what the projector advertises. An advanced device feature that the chosen driver cannot consume has no operational benefit for that workflow, although it may remain useful to another supported management tool. Recheck enhancements separately from the essential operating baseline.

The existing PJLink reference supplies the broader command context. Use this guide's matrix when discussing a repeatable fleet configuration with SoftControl partners, and validate product-specific capabilities before promising them to a customer.