Driver Type
Categories
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Networking
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
Driver Type
Categories
- Recent Updates
- Access Control
- Amplifier
- A/V Receiver
- Climate and Pool Control
- Disc Player / Changer
- Display
- DSP
- DVR
- Irrigation / Sprinklers
- Lighting Control
- Matrix Switch
- Media Server and Player
- Multi-Room A/V
- Networking
- Power and Rack Management
- Security
- Surveillance
- Teleconferencing
- Training
- Tuner
- Utility
- Video Projector
Generic TCP Server
This driver allows a TCP client device to connect to the RTI processor and trigger event-based programming.
Up to 100 events are allowed.
Each command MUST end with (_x) with ‘x’ being the command number.
If command 1 was to be “open gate” it would look like: open gate_1
If command 2 was to be “close gate” it would look like: close gate_2
Carriage returns and/or line feeds are not required.
[Generic] [TCP Server] [IP] Version [1.0]
Introduction
This driver allows a TCP client device to connect to the RTI processor and trigger event-based programming.
Version History
Version 1.0
Initial Release
System Requirements & Prerequisites
RTI System Requirements
Integration Designer: 11.12 or later.
XP FW: 22.3.31 or later.
Driver Information
Allows a TCP client to connect to the RTI processor and trigger an event.
Up to 100 events are allowed.
Network Requirements
You must define a port for the driver to open for client communications.
The port number you define MUST be higher than 1024.
The processor will require a fixed IP address via a static reservation, or the setting of a static IP address.
Driver Configuration
Initial Setup
Add the Driver
Add the "Generic TCP Server" driver to Global in Integration Designer
Choose a port number
Enter a port number under “Server Settings”
Set how many commands are required
Under “Number of commands” click the dropdown and set how many commands/events you require.
Name your commands. Each command MUST end with (_x) with ‘x’ being the command number. If command 1 was to be “open gate” it would look like: open gate_1 If command 2 was to be “close gate” it would look like: close gate_2
Carriage returns and/or line feeds are not required.
User Interface
The drive requires no user interface. It is purely event based. No pages are required on a controller.
Driver Features
Commands
The driver features NO commands. It is purely event based.
Variables
The driver has no feedback variables. It is purely event based.
Events
Each command has a corresponding event in the driver events section. In each event, place what you want to happen when the driver receives the applicable command.
Testing Your Events
Once you have configured the driver and your events, upload your file to the processor. You can then test by opening a simple Telnet session at the processor’s IP address and the port you defined in the driver’s properties. Type out your command name i.e.: my command_1 and hit enter.
System Testing
Integration Designer 11.14.1:
XP Processor Model: XP-3
XP Processor Firmware: 25.9.24
Support Contact
RTI Control
+ 1.952.253.3137
support@rticontrol.com