Compatibility
Protocol support, stated honestly.
Version 1.0 is validated against the published PJLink specification and deterministic TCP/UDP simulation. No physical projector model is claimed as hardware certified. Projector Fleet is independent and is not affiliated with or endorsed by JBMIA or any projector manufacturer.
| Capability | Coverage | Validation |
|---|---|---|
| Class 1 monitoring | Power, input, mute, errors, lamp usage, manufacturer, model, name | Protocol + simulator |
| Class 1 control | Power, input, video/audio mute | Protocol + simulator |
| Class 2 monitoring | Inputs, input names, serial, software, resolution, filter usage | Protocol + simulator |
| Class 2 control | Freeze and supported volume commands | Protocol + simulator |
| Authentication | Legacy MD5 and enhanced SHA-256 challenge response | Official vectors + simulator |
| Discovery | Class 2 broadcast search and response parsing | Protocol + simulator |
Why hardware results can differ
Manufacturers may expose different input lists, optional Class 2 capabilities, firmware behavior, authentication modes, and network restrictions. Broadcast discovery may be blocked across VLANs or by Wi-Fi client isolation even when manual TCP control works.
Before a live event
- Confirm the exact projector model and current firmware documentation.
- Test on the intended VLAN and Wi-Fi configuration.
- Verify every required control while the physical output is safely observable.
- Run a pre-event refresh and review unavailable, warning, and error states.
- Keep the manufacturer's supported control method available as a fallback.
Report a result
Email support@aronscolaro.com with the manufacturer, model, firmware, PJLink class, command, and a redacted report. Never include credentials.