Resumen del contenido incluido en la página 1
OWNER'S MANUAL
________________
MODEL V79 PDI-1 AND V80 PDI-2
SWITCH INPUT AND OPTICALLY
ISOLATED INPUT MODULES
BayTech Publication #U140E105
Resumen del contenido incluido en la página 2
Thank you for selecting a BayTech Model V79 PDI-1 Switch Input Module or Model V80 PDI-2 Optically Isolated Input Module. The data provided in this Owner's Manual explains the various ways you can operate the V79 PDI-1 or V80 PDI-2, and how to configure your unit. We suggest that you read this manual carefully before attempting to install a PDI, and that you place special emphasis on correct cabling and configuration. If you have any problems with your installation, please contact a BayTech ap
Resumen del contenido incluido en la página 3
TABLE OF CONTENTS 1 GENERAL 1 ............................................................................................................................................................................................ 1.1 V79 PDI-1 MODULE 2 .................................................................................................................................................. 1.2 V80 PDI-2 MODULE 2 .....................................................................................
Resumen del contenido incluido en la página 4
5 CONFIGURATION 19 ........................................................................................................................................................................... 5.1 MENU-DRIVEN CONFIGURATION 19 ..................................................................................................................... 5.1.1 CONFIGURATION MAIN MENU 21 .................................................................................................. 5.1.2 MODULE STATUS 22
Resumen del contenido incluido en la página 5
1 GENERAL BayTech's PDI modules are designed for use with the M16 and M8 (DAC) Data Acquisition Controllers. Both modules are used to detect events where an event is defined as a change-in-state of an input and return to the original state. The V79 PDI-1 module is used for the detection of switch closure in applications requiring notification of device status such as burglar alarms, fire alarms, event counters and timers, process control, etc.. The V80 PDI-2 is used for the detection of optic
Resumen del contenido incluido en la página 6
1.1 V79 PDI-1 MODULE The main features of the V79 PDI-1 module are sixteen microprocessor-controlled input channels that can be connected with individual ground returns, or a common single-point ground. The input channels provide a flexible, reliable method to detect and report the change-in-state of a circuit. The change can be from infinite resistance (open) to continuity (closed), and vice versa. For example, the change- in-state could be for a set of form C (dry) relays or switch contacts.
Resumen del contenido incluido en la página 7
These optically isolated inputs provide an efficient means for the monitoring of external process and control functions. All functions provided by the board are programmable through a series of detailed configuration menus. Additional functionality is made available through the use of BayTech or user provided application software. Input connections to the PDI-2 are made through a standard DC-37F connector. 2 SPECIFICATIONS 2.1 V79 PDI-1 SWITCH INPUT STATUS MODULE o (typical for 25 C unless ot
Resumen del contenido incluido en la página 8
2.2 V80 PDI-2 OPTICALLY ISOLATED INPUT MODULE MODULE TYPE PDI-2A PDI-2B NUMBER OF INPUTS: 16 16 INPUT VOLTAGE RANGE: 5-24 100-130 AC/DC MAXIMUM INPUT CURRENT: 50ma 20ma MINIMUM TURN ON CURRENT:8ma 8ma MAX TURN ON TIME: 1ms 1ms MAX TURN OFF TIME: 1ms 1ms VOLTAGE ISOLATION: 500V 500V (Input to Input and Input to ground) POWER REQUIREMENTS: +5VDC, 40 ma typical (provided by M16/M8 pwr supply) DEBOUNCE TIME: 0 to 60000 ms (software selectable) ENVIRONMENTAL: o o Operating
Resumen del contenido incluido en la página 9
3 INSTALLATION The PDI-1 and PDI-2 are installed in the M Series chassis as described in Section 3.5 of the base unit operator's manual. NOTE: The PDI-1 or PDI-2 cannot be installed as Module 1. If an PDI-1 or PDI- 2 is removed from a module slot and a different PDI-1 or PDI-2 is installed in that location, the newly installed module acquires the previous module's configuration. Moving an PDI-1 or PDI-2 to a different module location requires reconfiguration because the configuration paramete
Resumen del contenido incluido en la página 10
3.2 PDI-2 AC INPUT SETUP The PDI-2 module has two banks of dip switches which are used to add ripple filtering for AC inputs. AC input is selected by individual channel. Location of the dip switches is shown in Figure 3. CHANNEL SW1 SW2 1 1 2 2 3 3 Figure 3 4 4 5 5 6 6 7 7 8 8 9 1 10 2 11 3 12 4 13 5 14 6 15 7 16 8 Table 1 Dip switch SW1 1-8 provides filtering control for channels 1-8 while SW2 1-8 controls channels 9-16. Refer to Table 1 to determine wh
Resumen del contenido incluido en la página 11
4 OPERATION This section discusses the general PDI operation (Section 4.1), user-programmable features (Section 4.2), data commands (Section 4.3), event sample reporting (Section 4.4), and presentation (Section 4.5). 4.1 GENERAL The V79 PDI-1 and V80 PDI-2 modules are used in applications requiring notification of device status (e.g., burglar and fire alarms, event counters/timers, process control, etc.). The PDI-1 module has 16 channel switch inputs providing a reliable method to detect and re
Resumen del contenido incluido en la página 12
4.2 USER-PROGRAMMABLE FEATURES You may program the Sampling Setup, Reporting Setup, and Dynamic Configuration on the PDI which are discussed in Section 4.2.1 through Section 4.2.3 respectively. 4.2.1 SAMPLING SETUP Sampling Setup allows you to program the Debounce Delay and Latch Polarity for the input channels. The Debounce Delay is used to guard against erroneous events. An event will not be valid unless the input channel has remained at a changed state for the debounce duration. The deboun
Resumen del contenido incluido en la página 13
4.2.2.2 REPORT START TIME Report Start Time is the time reporting begins when Schedule Reporting Method is selected. The start of reporting may be delayed up to 24 hours from the current time recorded by the M Series time-of-day clock and reporting will occur in cyclic periods as determined by the Report Interval. The default Report Start Time is 00:00. 4.2.2.3 REPORT INTERVAL You may program the PDI to report in repetitive periods using Schedule Reporting Method, where the PDI will report all
Resumen del contenido incluido en la página 14
4.2.2.6 TERMINATING CHARACTER(S) The Terminating Character(s) is added at the end of an event sample to match the requirements of the host terminal or application software. The Terminating Character(s) consists of one or two hexadecimal characters. The default Terminating Characters are 0D Hex ( ) followed by 0A Hex ( Carriage Return Line ). Feed 4.2.3 DYNAMIC CONFIGURATION You may enable or disable Dynamic Configuration for the PDI. Dynamic configuration mode allows non-verbose or "on-the-fl
Resumen del contenido incluido en la página 15
2. Once the PDI is selected, it will go into Command Mode and allow you to send data commands. The PDI data commands begin with two capital letters designating the specific command and are terminated with a Carriage Return. Most data commands also require a number between the command letters and Carriage Return. This number is typically the desired channel(s) for the data command. If you have a requirement to send the data command to multiple channels simultaneously, you may use one of the f
Resumen del contenido incluido en la página 16
4.3.1 CLEAR EVENT BUFFER COMMAND The Clear Event Buffer (CB) command is used to clear all stored event samples from the buffer of the selected channel(s). The Clear Event Buffer command has the following format: CB n where c = Channel# (1 to 16 or 0 for all). 4.3.2 CLEAR EVENT COUNTER COMMAND The Clear Event Counter (CC) command is used to reset the event counter for one or more channels to zero without reading the value of the event counter. The function of the event counters is discussed
Resumen del contenido incluido en la página 17
4.3.4 REPORT ALL BUFFERED EVENTS COMMAND The Report All Buffered Events (RA) command instructs the PDI to report all event samples currently stored in the buffer of the selected channel(s). The Report All Buffered Events command has the following format: RA n where c = Channel# (1 to 16 or 0 for all). 4.3.5 REPORT EVENT COUNTER COMMAND The Report Event Counter (RC) command instructs the PDI to report how many times an event has occurred for one or more channels since the last time a counter
Resumen del contenido incluido en la página 18
4.3.7 REPORT EVENT LATCH DATA COMMAND The Report Event Latch Data (RL) command instructs the PDI to report the active state of the initial event and the time the initial event occurred (if time tagging is enabled). This command does not reset the latch buffer. The Report Event Latch Data has the following format: RL c where c = Channel# (1 to 16 or 0 for all). 4.3.8 REPORT EVENT COUNTER AND RESET COMMAND The Report Event Counter and Reset (RO) command instructs the PDI to report how many
Resumen del contenido incluido en la página 19
4.3.10 REPORT A SINGLE BUFFERED EVENT COMMAND The Report A Single Buffered Event (RS) command instructs the PDI to report the first event sample stored in the buffer of the selected channel(s). The Report A Single Buffer Sample command has the following format: RS c where c = Channel# (1 to 16 or 0 for all). 4.4 EVENT SAMPLE REPORTING An event is defined as a change-in-state of an input channel and return to the original state. An event may be started on a rising edge (LO to HI) or a fall
Resumen del contenido incluido en la página 20
The PDI module can observe, record, and report when an event happened, how long the event lasted, and how many events occurred for each individual channel. The initial occurrence of an event will set the event latch bit and store the associated time in the latch buffer. You may read the state of the initial event and the time it was recorded (if time tagging is enabled) by issuing the RL or RR commands. Each occurrence of an event starts the duration counter and increments the event counter.
