Every selected protocol must match
Selecting Modbus RTU and Modbus TCP on the acquisition side means that one model must satisfy both requirements. Multiple forwarding protocols and hardware counts are combined with the same AND rule. Results use reviewed structured specifications, rather than matching any one requirement.
Manual names are not replaced by similar protocols
You can enter and add a protocol used by your equipment. Check its version, transport and client/server role as well. For example, Modbus RTU and a driver explicitly qualified as a Server are not interchangeable merely because their names are similar. An unlisted manual name needs review and is not automatically assigned to a protocol family.
What to do when there are no results
Remove nonessential conditions individually and check the results again. You can also provide the equipment model, communication manual and point list to technical support. Missing evidence is not proof of incompatibility, but it is not a confirmed match either. A stated protocol count does not replace checking the exact driver and role.