AMX NetLinx-KNX Integration

The task is to extend an existing AMX NetLinx program on an NX-3200 controller by adding a new feature set that enables seamless, bidirectional communication with a KNX installation. Remote access to the live system, its current source code, and a KNX IP gateway will be provided through a VPN.

Scope
The existing codebase is stable; no bug-fix work is needed. The focus is strictly on developing and inserting well-structured NetLinx modules (Duet or classic, whichever you feel is best) that expose KNX group addresses so the NX-3200 can trigger and monitor lighting, HVAC, and any other KNX-enabled devices in the building. If a reusable third-party library makes sense, feel free to recommend it; otherwise a clean, from-scratch implementation is acceptable.

Deliverables
• NetLinx source files and compiled .tkn modules implementing KNX integration
• A small demo routine showing how to call the new functions from the existing program
• A concise README covering installation, customisable parameters, and KNX address mapping
• One live remote test session to verify that commands sent from the AMX touch panel reach KNX devices and that KNX state changes are reflected back on the panel

Acceptance criteria
1. All KNX group addresses listed in the brief respond within one second to AMX triggers.
2. Status feedback from KNX updates the AMX UI without manual refresh.
3. No existing AMX functions or timers are broken, and CPU utilisation on the NX-3200 remains within normal operating range after 24-hour soak test.

NetLinx Studio, TPDesign5, and a Git repository are already in place; commits must compile cleanly with the current NetLinx firmware. Once the above criteria are met and documentation is complete, the job is considered done.