Explore model variants side by side. Compare acquisition scope, forwarding protocols and physical ports, then open a model for its full specifications and documents.
Match device-side protocols and the host system first, then check ports, wireless connections and capacity. Candidates below use confirmed model specifications.
You need multiple serial and Ethernet protocols
Check models confirmed to cover all acquisition protocols for serial and Ethernet connections. Check protocol scope and physical port counts separately. Confirm dedicated CAN, KNX TP and 2-wire MBus connections for the specific model.
Start by checking these three families for HMI1002-Lite and the listed variants with the same scope. For other acquisition protocols, check models with the corresponding coverage.
The listed HMI1002-Lite-E variants have confirmed Modbus RTU acquisition. Lite-E scope differs by series; this rule does not apply to every Lite-E model.
Check each model’s listed acquisition protocols and the required host-system protocol. A model suffix alone does not establish equivalent acquisition capability.
These models have no listed acquisition scope suitable for this decision. Check their model notes and provide device make, model and protocol documentation.
This guidance narrows the candidates. Confirm communication roles, read/write direction, the point list, wiring and model-specific resources before final selection.
“Unconfirmed” means documentation does not establish a value; it does not mean zero or unsupported.
