Before you can enter all inputs and input units (= 'I' units) into your TELETASK project, it is essential to have a good understanding of some basic items.
In contrast with the 'O' interfaces, the 'I' interfaces are less conveniently arranged because there is a wider range of input units and input interfaces available. Additionally, interfaces which may be both input and output are added to the inputs list.
As with the 'O' units, the 'I' units are divided in a functional as well as in a system related way.
There are four different types of input units:
- General Interface
- these are all TELETASK (AUTOBUS connected) touch panels, touchscreens, etc… (See more details in the overview list further in this text). When somebody pushes a button on a touch panel, a command is sent to the central unit, and the predefined action for this button is done.
- Digital Input Interface
- digital inputs are contact inputs for all kind of external on/off signals like there are from standard voltage free push buttons (any brand), motion detectors (often via a relay to be connected to the voltage free contact inputs of the TELETASK input). When the concerned external contact is closed, the input unit or interface generates the related command and the central unit processes this command just like it was coming from a touch panel and the predefined action is done.
- Analogue Inputs
- analogue inputs are the connection between the TELETASK system and the different kinds of TELETASK sensors. The sensors send their signal to the analogue input (internal in the central unit or external on AUTOBUS). This signal is continuously processed by the central unit and depending on the related function, actions are taken at certain times.
- AV - Interface
- (Audio/Video) This is a whole family of different general and dedicated (brand dependant) interfaces. All audio interfaces are AUTOBUS interfaces. By these interfaces it becomes simple to control connected audio systems with standard buttons and/or special touch panels and touchscreens.
Beside of the functional classification, the 'I' interfaces can also be classified based on the way they are connected with the TELETASK central unit.
There are two groups to be distinguished:
- Direct or Internal 'I' Interfaces
- these 'I' interfaces are integrated in the central unit. Depending on the type of central unit you use, there may be different types of internal 'I' interfaces available in the central unit. Please refer to the concerning data sheet of your central unit for more details.
- AUTOBUS 'I' Interfaces
- these 'I' interfaces are connected on the AUTOBUS. Most of the 'I' interfaces are of this kind (TDS12117, 16 digital inputs for voltage free contacts).
The address setting is necessary for the system to be able to communicate with the individual interfaces and modules. Every 'I' unit and interface has its own address. All external AUTOBUS connected 'I' interfaces have a hardware or software address setting on the interface itself (just like Output interfaces).
The address numbering starts with an 'AUTOBUS number'. Then PROSOFT ads for internal use an 'I' to the address. This way it will be very clear in PROSOFT that it concerns an 'I' interface. This is necessary because there are also TELETASK AUTOBUS 'O' interfaces which become an address (these are the output interfaces). These 'O' addresses are unrelated of the 'I' addresses. This means that there can be an 'O16' and an 'I16'. In the 'O' and 'I' address groups every address is unique. There can't exist 2 'O16' addresses or 2 'I16' addresses.
The actual 'I' address starts with '00'; these are the Master functions on the remote control. The first address which can be defined on an interface is '01'. PROSOFT automatically generates an address for every new 'I' interface which is added to the system. Be sure that this address is created for the 'I' interface or that the set-up in PROSOFT can be adapted to the set-up of the 'I' interface. Differences between the hardware (on the interface) address setting and the software (PROSOFT) address setting can result in incorrect and unpredictable behavior of the system. Please check this before starting-up the TDS system.