The complete model and document edition come first
A family suffix helps identify a product, but does not replace the model-specific acquisition, forwarding and role specifications. Use the corresponding 2026 product document and explicit model confirmations. Do not infer universal protocol support from ARM, Lite or E alone.
Reviewed examples
- Page 2 of the HMI1002-ARM document states more than 500 acquisition protocols. This does not confirm every arbitrary name, version or role.
- Page 2 of the HMI1002-Lite document lists Modbus, BACnet and Simulator. Verify the particular driver and communication role separately.
- Page 2 of the HMI1002-Lite-E document lists Modbus RTU, Modbus TCP and Simulator.
- Page 2 of the BAC1002-Lite-E document lists Modbus RTU and Simulator. Do not carry over the HMI model’s Modbus TCP acquisition scope.
Simulator is a simulation driver, not a physical interface. Verify acquisition and forwarding independently: a BACnet forwarding interface does not establish BACnet acquisition support.