Room control
Gateways: checking direction, points and functions across protocols
A gateway can link data between systems, but selection starts with the function you want to share. Define which side supplies the data, which side interprets it and what confirmation the AV interface needs before choosing by connector.
Direction changes the application
Intesis IN701-KNX manual version 1.4.7, published May 16, 2024, includes order code IN701KNX1000000 and several applications. It identifies IN-BAC-KNX as KNX to BACnet server and IN-KNX-BAC as BACnet client to KNX. These are different family functions; requesting a “BACnet/KNX gateway” is not specific enough.
For BACnet client to KNX, the manual describes COV subscription or periodic reads of configured BACnet objects and association of Present_Value with KNX group objects. Identify the actual application and project; a documented function is not evidence that it is already configured.
Request an interpretable point map
| Item | What to compare | Decision |
|---|---|---|
| Source and destination | Source object/property and destination point | Specify the shared information and its direction. |
| Type and unit | Boolean, number or states; unit and scale | Avoid translating a state as a measurement or setpoint. |
| Access | Read/write support and approval at each end | Request only the functions needed. |
| Updates | Event/subscription or periodic reads where supported | Define when data becomes stale. |
| Capacity | Part number, application and object/association limits | Count the map’s requirements, not just devices. |
| Feedback | Result, queried value and communication state | Separate request acceptance, received data and AV result. |
What to check after selecting the combination
For a later test, agree on a noncritical point, expected value, destination representation and freshness criteria. Include communication-loss detection and what to display after reconnection. Defining only the command path leaves feedback unresolved.
If writing is needed, the professional responsible for each system must identify the supported point and permission. This preparation requires no bus connection, device discovery or project changes. Safety, access control, fire systems, machinery and motorized movement are outside the AV scope.
Proposed example: sharing a reading
Suppose an AV interface needs a building environmental reading through another system. The map should preserve meaning and units, identify updates and indicate a missing source. Translating a point name does not establish that the entire path works.
- Approved source → object, property and unit.
- Gateway with documented application → mapped point.
- Destination system → interpretable data and communication state.
Start without a complete point map
Share the desired function, equipment labels or a preliminary diagram, even if models or dimensions are missing. Identify who maintains each system’s documentation and editable project. GLMedia can help define the AV need before an integration proposal is requested.
Questions for choosing a gateway
Does bidirectional mean every function is translated?
No. Review the data and services supported by each application, their direction and limits. Two communication directions do not establish complete interoperability.
Does an Ethernet or serial adapter perform the translation?
Not because of its connector. Translation requires a documented protocol function and a data map compatible with both ends.
Can I inquire with only a gateway photo?
Yes. Its label helps identify the part number. Add the information you need to share and the systems involved to determine which documents are missing.