3000 Series TS-2 Firmware v3.6

Transcription

1 3000 and 3000E Traffic Controllers 3000 Series TS-2 Firmware v3.6 Peek Traffic is pleased to announce the release of Version 3.6 of the TS-2 firmware for the 3000 Series Traffic Controllers. The primary purpose of this release is to enhance the I/O mapping functions of the controllers and to improve communications reliability. This update also adds a couple of new overlap modes, improves the onscreen interface, and corrects a few issues reported in previous versions of the firmware. Product... TS-2 Firmware for 3000 and 3000E Traffic Controllers Version...Version 3.6 Release Date...11/23/04 Importance of This Update This is an important update for TS and 3000E Traffic Signal Controllers. It is a required update for any TS or 3000E Controllers that will use I/O mapping. If this update is performed on controllers used with the CLMATS central software system, CLMATS must be updated to version 2.4 (or higher) as well, to gain access to all of the new features. Product Compatibility This firmware is designated part number 8216A Version 3.6, and is released for use in all field and production 3000 and 3000E Traffic Controllers that have been designated NEMA TS-2 units. It should not be installed in units that communicate via Protocol-90. It can be used to update earlier versions of series 8216A firmware and also series 5921 firmware. Contents Upgrade Process... 2 Installing Updated Firmware to EPROMS... 2 Installing Updated Firmware to Flash Memory... 3 Updating the Modem Setup String... 5 Enhancements... 6 Communications Improvements... 6 I/O Mapping Additional New Features Other Issues Addressed in this Release Additional Guidance Note If this update is used to replace 5921 firmware, the controller will no longer be compatible with the Smartways software. Also, be aware that an update from the 5921 firmware requires that all Special and Restricted Menu settings be cleared before the update is applied. This release requires version 2.4 or higher of CLMATS. The firmware should not be used with versions of CLMATS older than v2.4 and is not compatible with Smartways. This version of firmware does not support 3000E operations with a 3800EL Master controller in 7 bit mode. Information furnished by Peek is believed to be accurate and reliable, however Peek does not warranty the accuracy, completeness, or fitness for use of any of the information furnished. No license is granted by implication or otherwise under any intellectual property. Peek reserves the right to alter any of the Company's products or published technical data relating thereto at any time without notice. p/n Revision 9 Page 1 of 32 11/23/2004

2 Delivery Methods This firmware may be delivered to the controller in one of two ways: either as two binary files that can be burned to the controller s EPROM memory chips, or as a single binary file that can be loaded into Flash memory via the controller s Port 2 serial port. This latter option is only available on 3000E controllers that are designated Flash Memory Enabled. If you are updating EPROM chips that will be placed into your 3000 or 3000E controller, the proper checksums for the two binary files are listed in Table 1. Table 1 Checksums for v3.6 TS and 3000E firmware (Build 335) EPROM Checksum value (hex) 0 6F7E 1 3FDC Upgrade Process Whether your controller uses programmable EPROMS or internal flashable RAM to install new firmware, there are two steps to the upgrade process. First, load the new firmware based on the hardware that you have. The next two sections describe how to do this on EPROM and Flash memory controllers. After the firmware update, go to the next section to update the modem setup string (if an external modem is used with your 3000 series controller.) Installing Updated Firmware to EPROMS To upgrade an EPROM-equipped 3000 or 3000E Traffic Controller in the field, follow these instructions: 1. If you ordered updated EPROMS from Peek rather than just the firmware files, skip down to step Locate the following items in order to burn the updated firmware to EPROMS: Two 4MB EPROMs (28 pin DIP package), these may be recycled out of field units an EPROM burner capable of holding a 4MB EPROM EPROM burning software the two binary files containing the updated 3000E firmware 3. If the EPROMs were used previously, erase them. 4. Insert one of these blank EPROMs into the burner and burn the firmware file named b335-0.bin onto it. Label it 3.6 EPROM Insert the other blank EPROM into the burner and burn the firmware file named b335-1.bin onto it. Label it 3.6 EPROM Observing all safety and other municipal ordinances, place the intersection to be updated into flash. 7. Power down the 3000 Series Traffic Controller. 8. Open the front panel and remove the two EPROMS that are currently installed in the unit. Replace them with your updated versions, being sure to place the properly labeled EPROM in each socket. 9. Restore power to the unit. 10. As the unit powers up, it performs a series of database verification tests. If any of the seven databases in the controller s memory have been corrupted in any way, this test will detect it. If any problems are seen, the unit will display an error screen, as shown in the next figure. Any databases that have problems are listed on this screen. The only way to proceed to a running state is to acknowledge this error screen by pressing the CLEAR button. Any of the controller databases may be seen to be corrupt: Controller, Coordination, Time of Day, Preemption, Option, Special, and BIU I/O Mapping. Note The BIU I/O Mapping database error message will not appear (even if there is corruption in this database area of memory) unless I/O mapping is currently configured to be ACTIVE. Page 2 of 32

3 Database sections are corrupt! [Controller] [Coordination] Press the [CLEAR] key to clear the above sections and continue. Figure 1 Power-on Self Test Error Message If this window appears, press the CLEAR key to go ahead and start the controller. 11. If any database errors were detected, you will need to load good files into the controller before using the controller to run an intersection. This can be done by choosing to load default databases (MM > 3. Change Data > 8. Utilities > 1. Default Data Load menu,) or you can load a good set of databases from CLMATS, an EPROM card, or by using a Pocket PC handheld device with the Pocket Central utility software loaded. If there were no database errors detected, proceed to the next step. 12. Press 1 for Dynamic Displays. 13. Press 1 for Controller Func(tions). 14. Examine the Normal Status screen for proper operation and cycling. 15. If everything appears to operating normally, return the intersection to normal operation. * Installing Updated Firmware to Flash Memory If the 3000E controller shows the Flash Memory Enabled logo on its front panel, it should be updated using: a single binary firmware file from Peek Traffic, and a laptop computer or Pocket PC handheld device connected to Port 2. Note Additional information about these types of upgrades are available in the release notes for the Firmware Upgrade Utility for Windows (99-395) and for the Pocket Central Utility for Pocket PC (99-393). The following hardware and software are required in order to perform this type of upgrade: a 3000E controller that is designated Flash Memory Enabled Either a laptop PC running Windows NT, Windows 2000, or Windows XP OR a Pocket PC device running Pocket PC 2002 or Pocket PC 2003 a serial cable to connect the PC or Pocket PC device to Port 2 of the traffic controller If using a PC for the upgrade, you will also need the 3000E Firmware Upgrade Utility for Windows, which is available from Peek Traffic If using a Pocket PC device for the upgrade, you will need the Pocket Central software, which is available from Peek Traffic Important Although previous 3000E products were updated using removable and programmable EPROM memory chips, and although it is possible to remove the Flash chips from the newer devices, it is highly recommended that you do not remove these chips from the units. Firmware updates for Flash Memory Enabled units should only be performed using the following procedure. * In the past, customers have also been told to clear any central overrides that may be active in the controller whenever attempting to create a Healthy Controller situation. If overrides are an issue, the clearance process has changed, as described on page 29. Page 3 of 32

4 The basic steps required to upgrade a Flash memory-equipped 3000E controller in the field are listed here: 1. Locate the binary firmware v3.4 file that you received from Peek Traffic. (8216A build 335.pfw) 2. Store the firmware file in a known location on the PC or Pocket PC where the update utility will be run. 3. Observing all safety and other municipal ordinances, place the intersection to be updated into flash. 4. Power down the 3000 Series Traffic Controller. 5. Connect the PC or Pocket PC to the device using the required serial cable. 6. Open the Firmware Upgrade Utility on the PC (or the Pocket Central software on the Pocket PC device.) 7. Place the controller into Flash Memory mode by powering up while holding down the SHIFT and PGUP keys. 8. Use the Utility to query the device about its current firmware. 9. Load the 8216A build 335.pfw firmware file into the Utility s memory. 10. Send the new firmware to the controller. 11. When both the PC and the controller show that the firmware update has completed, press the END key on the 3000E to restart the unit with the new firmware. Disconnect the PC or Pocket PC from the controller. 12. As the unit powers up, it performs a series of database verification tests. If any of the seven databases in the controller s memory have been corrupted in any way, this test will detect it. If any problems are seen, the unit will display an error screen, as shown in the next figure. Any databases that have problems are listed on this screen. The only way to proceed to a running state is to acknowledge this error screen by pressing the CLEAR button. Any of the controller databases may be seen to be corrupt: Controller, Coordination, Time of Day, Preemption, Option, Special, and BIU I/O Mapping. Note The BIU I/O Mapping database error message will not appear (even if there is corruption in this database area of memory) unless I/O mapping is currently configured to be ACTIVE. Database sections are corrupt! [Controller] [Coordination] Press the [CLEAR] key to clear the above sections and continue. Figure 2 Power-on Self Test Error Message If this window appears, press the CLEAR key to go ahead and start the controller. 13. If any database errors were detected, you will need to load good files into the controller before using the controller to run an intersection. This can be done by choosing to load default databases (MM > 3. Change Data > 8. Utilities > 1. Default Data Load menu,) or you can load a good set of databases from CLMATS, an EPROM card, or by using a Pocket PC handheld device with the Pocket Central utility software loaded. Or, of course, you also have the option of reprogramming the controller using the keyboard interface. If there were no database errors detected, proceed to the next step. 14. Press 1 for Dynamic Displays. 15. Press 1 for Controller Func(tions). 16. Examine the Normal Status screen for proper operation and cycling. 17. If everything appears to operating normally, return the intersection to normal operation. * * In the past, customers have also been told to clear any central overrides that may be active in the controller whenever attempting to create Page 4 of 32

5 Updating the Modem Setup String Significant improvements have been made to the 3000 Series communications processing logic. As a result, a couple of changes should be made to a modem setup string for the controller (if your controller uses an attached modem for communications with CLMATS.) To change the setup string, you will need to go to the Communications & System Setup Menu (MM > 3. Change Data > 5. Comm/System Setup.) On this menu, select option 2. Comm Setup, and then page down to the third screen. (These Com Setup screens have changed in firmware v3.6, as is described in these release notes on page 7.) The following changes should be made to the string: Auto answer must be OFF. Previously it was ON for 3000 series controllers, but with the new firmware, answering the modem is handled by the controller firmware rather than by the modem. (typically: S0=0 ) Error correction should now be set to ON. In the past, we had recommended that it be turned OFF. (The commands are &M4 for U.S. Robotics modems and \N2 for LPM modems.) a Healthy Controller situation. If overrides are an issue, the clearance process has changed, as described on page 29. Page 5 of 32

6 Enhancements Added in This Firmware Release Communications System Improvements The 3000 Series communications system itself, as well as the interface screens used to configure it, have been modified in several ways to improve operation and ease-of-use. More Useful Communications Status Screens In previous versions of the firmware, the 3000 series controllers had two Comm status screens that could be accessed under item 10 (SHIFT-0) on the Dynamic Display menu. These Comm status screens were designed to display the status of communications with an M3000 Series Master Controller. But the ports of the 3000 series controller can be used with many other devices than just a master controller. Because of this, the Comm status screens have been made more general so they can display simple communications status parameters for either Port 2 or Port 3. Also, the labeling on these screens has been made more easy to understand. Previously, the top screen in this area was called the Controller-Master Comm Dynamics screen. It is now called the MIZBAT Dynamic Status screen, and it shows what MIZBAT commands have just been sent and received by the controller. It also shows a timeout timer that is used whenever an sp or mp command is received. (The sp and mp commands are polling requests from central.) MIZBAT Dynamic Status Last command received : sp Last command transmitted : sq Master polling timer : 59.1 Press ONE to remove circuit overrides from central: No overrides active Figure 3 New Dynamic Comm Status screen If the polling timer reaches zero, the screen will display Timeout for the Master polling timer and the master override will automatically deactivate in the controller. This screen can also be used to manually clear circuit overrides received from central. If you want to clear an override locally, press the 1 key on this screen. (This functionality has not changed from earlier versions of the firmware.) Previously, if one paged down from the old Controller-Master Comm Dynamics screen you would see a very cryptic Communications Debug Dynamic Data screen. This debug screen has been replaced with a pair of Comm Port Status screens, as shown here: Status Comm Port 2 CD : No Modem : Answering CTS : Yes Timer : 0 DTR : Yes Unused: 2 TXBD : 0 RXBD : 4 Figure 4 Comm Port Status screen (showing the status of Port 2) Use the PGDN key to switch to the Port 3 version of this status screen. These screens cannot be edited in any way; they are simply there to provide feedback on the status of the two comm ports on the 3000E. The top three parameters on the left side of the screen show the communication signal line states. The bottom two (TXBD and RXBD) are the Transmit Buffer Descriptor (which should always be 0) and the Receive Buffer Descriptor (which goes from 0 to 7 and then wraps back to 0.) Modem This line displays a status message showing the current state of the device (assumed to be a modem) connected to the port. The possible messages that can show up here are listed in Table 2. Page 6 of 32

7 Table 2 Modem Status Messages Message Notes DTR LOW/DTR HIGH This switching tells the modem attached to the port to reset. After these changes happen, the controller sends the modem initialization string that you have specified. INITIALIZING Waiting Answering Connected Dialing Ph#1 Dialing Ph#2 No modem After the initialization string has been sent, but before the modem is back up and operating under the new settings. This is the message displayed when the modem is up and running, and the controller is waiting for an incoming call. Displayed when an incoming call has been detected, but normal communications haven t been established yet. Displayed after good communications have been established. Displayed when the modem is calling out, using the primary phone number. If the Alternate Phone Number circuit is active (TOD circuit 121: PH2 ) and a Secondary phone number has been entered in the Phone settings screen, then this number will be tried, but only after Dialing Ph#1 fails. When this event occurs, the Modem status line will display this message. This message appears when no modem is attached to the port, or the modem is off. Timer This countdown timer shows the timeout count when an incoming or outgoing call is attempted. Unused This shows the number of trash characters that have been detected in the communications stream. More Intuitive Comm Port Setup Screens The Comm Port Setup screens have been reorganized so the parameters are easier to understand and use. Previously, when one entered the Comm Setup Screens from the Communications & System Setup menu (MM > 3 > 5 > 2), the controller presented four setup screens (accessible by paging down.) The first of these was a screen where the Master Port, Monitor Port, and Central Port were assigned. This screen has been removed. Now, the controller goes straight to the Comm Port 2 Setup screen: Setup Comm PORT 2 Port type : None Baudrate : Hardware : Normal Data bits : 8 Comm Copy : No Parity : No PgDn for more comm setup Figure 5 Comm Port 2 Setup screen Whenever Port 2 on the front of the 3000 Series controller is accessed, these settings are used. Use the arrow keys to navigate, and the Y/N key to change the value for a parameter. Port type This setting is only used by the controller when it is set to Monitor, indicating that an intersection monitor is connected via this port. Note that this setting also allows a monitor to be connected via a modem (if anyone would want to do so.) Baudrate Sets the data transfer speed for this port. The firmware will accept values of : 1200, 2400, 4800, 9600, 14400, 19200, 38400, 57600, and baud. (But the selected rate can only be achieved if the device attached to this port can also communicate at this speed.) This parameter is not displayed if Hardware is set to Ethernet. Comm Copy This setting replaces the parameter in the Closed Loop Master/ID screen called Allow Comm Transfer Between Ports 2&3. What this command does is tell the controller to echo the input on this port to the other port. (This works for data input to either port.) Although this setting appears on both the Port 2 and Port 3 screens, there is only a single value for this parameter in the database. So setting this value to Y or N on one port automatically sets it to the same value on the other port. Page 7 of 32

8 Hardware This tells the controller what type of hardware is attached to this port: It can be set to either an AT Modem (i.e. a Hayes compatible modem), Normal or Ethernet. (Port 2 does not have the Ethernet option.) Table 3 Proper Hardware settings for various Port 2 and 3 devices Port card or hardware Proper Hardware Setting RS232 (direct connect) Normal RS232 (with external modem) Serial/Ethernet combo card Fiber FSK Modem AT Modem Ethernet Normal Normal Data bits The number of bits per byte. (Can be either 7 or 8.) This parameter is not displayed if Hardware is set to Ethernet. Parity The type of parity check used on bytes to verify that no bit-level changes have occurred during transmission. (Even, Odd, or No parity check). This parameter is not displayed if Hardware is set to Ethernet. Pressing PGDN from this screen will allow you to set the same parameters for Comm Port 3. The Setup Comm Port 3 screen is identical to the Port 2 screen, except that there is an additional Hardware setting: Ethernet. If Hardware is set to Ethernet, the right column parameters are hidden. (Ethernet forces these values to their fixed Ethernet values: , 8, No.) Port type : None Hardware : Ethernet Comm Copy : No Setup Comm PORT 3 PgDn for more comm setup Figure 6 Comm Port 3 Setup screen with Hardware set to Ethernet Paging down yet again will take you to the screen where the modem s AT setup string is entered. In firmware v3.6, this screen has been modified to make it easier to enter the desired string. (Note that the firmware automatically puts an AT at the beginning of this string, so you do not need to enter these letters.) Setup AT Modem String AT&F ^ ABCDEFGHIJKLMNOPQRSTUVWXYZ ,\%& Press HELP to display help screen The caret symbol (^) shows where the next character will be added on the third line. To add a character, move the highlight cursor (within the alphabet listing) to the desired letter, using the left and right arrow keys, and press ENTER. Removed Comm Transfer from the Closed Loop ID Screen The Closed Loop Master/ID screen (option 1 on the Communications & System Setup Menu) no longer has the Allow Comm Transfer Between Ports 2&3 parameter settings. The reason for this is that these parameters were not related to the closed loop master ID. This setting is now available as the Comm Copy parameter on the Comm Port Setup screens. Page 8 of 32

9 Removed Printer Comm Port Settings A confusing aspect of communications setup in the 3000 Series controllers prior to the version 3.6 firmware was the fact that comm settings were stored in multiple locations, depending on the intended use. The best example of this were the communications settings on the Utilities > Printer Menu, where option 1 allowed one to set communications settings for a serial printer attached to Ports 2 or 3. This screen has been removed. Although the option is still there, selecting it now shows a help window that explains the change. Instead, a printer will now use the communications settings that are assigned to whichever port it is plugged into, as configured on the normal Comm Setup screen. (Main Menu > 3 > 5 > 2). Addition of NTCIP Comm Parameter Screens To TS-2 Firmware Up until the release of the version 3.6 firmware, the NTCIP configuration settings for the 3000 controllers could only be accessed in a special NTCIP/TS-2 version of the firmware. The three screens used to set NTCIP Comm settings are now available on the Communications & System Setup Menu. Communications & System Setup Menu 1. Closed Loop ID 6. Port 1 Setup 2. Comm Setup 7. System Name 3. Phone Numbers 8. Contact Name 4. Event Call In 9. HDLC Address 5. Log Data Figure 7 Version 3.6 TS-2 Communications & System Setup Menu Items 7, 8, and 9 are new to the TS-2 firmware. Option 7, the System Name screen, displays this message: System Name: ABCDEFGHIJKLMNOPQRSTUVWXYZ #&. RIGHT & LEFT ARROW POSITIONS CURSOR. Up & Down Arrows Select Character. Figure 8 System Name Setup Screen Although a System Name is unique to NTCIP, it is not required for successful communication. System Name, or sysname as it is known in the MIB tree, is additional information for the users of the system. It is typically set to a string describing the overall System. As an example, one might set this string to Southeast Section while the intersection s name might be Main & First St. Option 8 on the Communications & System Setup Menu is similar to the System Name Setup Screen, except this is where the Contact Name is entered: Contact Name: ABCDEFGHIJKLMNOPQRSTUVWXYZ #&. RIGHT & LEFT ARROW POSITIONS CURSOR. Up & Down Arrows Select Character. Figure 9 Contact Name Setup Screen Page 9 of 32

10 This is also not required for NTCIP operation, but instead is additional information defined in the <required> system NODE of the MIB tree. Contact Name is used to identify a person or agency responsible for this unit, particularly in the case of a fault or problem condition. Option 9 on the Communications & System Setup Menu is the place to add physical/hdlc network addresses for an NTCIP controller: PHYSICAL/HDLC NETWORK ADDRESSES PORT 2: PHYSICAL ADDRESS : 0 HDLC GROUP ADDRESS: 0 PORT 3: PHYSICAL ADDRESS : 0 HDLC GROUP ADDRESS: 0 Figure 10 HDLC Address Setup Screen If the controller is to be used as an NTCIP unit, the operator must specify the controller s physical address. This is similar to the Intersection ID number for TS-1 and non-ntcip TS-2 units. The physical address range is 1 to Physical address 63 is a test address. This special test address tells the controller to respond to ANY Physical Address. If the controller s Physical Address is set to 63, then the controller will accept any incoming message regardless of how it is addressed. However, this is typically used for testing purposes and should not be implemented in an active intersection as communication collisions are likely to occur. The HDLC Group Address is used if Central needs to send a broadcast message to more than one controller at a time. Group addresses range from 1 to 8191, although address 63 is reserved as an all stations address. A group address 63 message must always be transmitted as a single byte (with all bits set.) A message received with a Group Address of 63 will force the controller to respond, regardless of its actual Group Address setting. Since the NTCIP 3000-series controller can communicate on either Port 2 or Port 3, the user has the option to enter physical and HDLC addresses for either port. Note The NEMA-defined object, syslocation, also under the system NODE of the MIB tree, corresponds to the Controller s database value for Intersection Name. This entry can be found in the controller s programming in the Unit Config/Sec. Code menu. Unit-to-Unit Transfer Menu Removed This set of commands, seldom used by operators of the 3000 Series controllers, was removed from the interface for a couple of reasons: To simplify the interface To free up system resources for other tasks There are other ways to copy controller databases between units, namely: EEPROM cards, programmable flash memory and utilities, and via CLMATS 3000 series controllers rarely sit next to one another in the field The Transfer menu was option 2 on the Utilities menu. (Main menu > 3 > 8). Page 10 of 32

11 BIU I/O Mapping The NEMA standard defines a system to map the inputs and outputs of a TS-2 controller to the various internal functions of the controller. This I/O Mapping standard has now been implemented in the TS-2 version of the 3000 Series firmware. This section explains these new cabinet interconnection options for 3000 Series TS-2 Type 1 controllers. In particular, it discusses the usage of Bus Interface Units (BIUs) with a 3000 series controller and an MMU. It explains how to map the signals from the controller's port 1 connector to the various BIU input and output pins. The NEMA Standards for Controller Input and Output The 3000 and 3000E Traffic Signal Controllers are available in several flavors, meeting the requirements of the most common cabinet standards. The oldest standard covered is the NEMA TS-1 standard. The 3000 Series are also available in TS-2 Type 1 and Type 2 variants. The TS-2 firmware also now supports the NTCIP communications protocol. But what exactly do all of these letters mean when one is dealing with a controller out in the field, standing next to a busy roadway? The basic description of the I/O standards follow. The rest of this I/O Mapping topic goes on to describe one of them in particular; the use of a 3000 series controller in a TS-2 Type 1 cabinet. TS-1 The connections to the cabinet hardware are made through three standard, round, multi-pin connectors, typically labeled A, B, and C. These connectors are military specification (aka 'MilSpec' or sometimes called Amphenol ) connectors. In a TS-1 controller, the outputs of the controller are permanently connected to the pins on these three connectors. The pin assignments for these connectors on a TS-1 type 3000 series controller are listed on pages of the 3000 Series Operating Manual (p/n 8204C). TS-2 Type 1 With the TS-2 standard, NEMA applied a more sophisticated method of connecting the controller to the cabinet. Instead of hardwired pins, control inputs and outputs are routed using high-speed serial instructions. The Type 1 standard replaces the three TS-1 connectors with a single, 10-pin, round, power connector (usually labeled 'A') and an RS-485 data port (labeled 'Port 1'). Instead of one pin for each function, data is sent and received serially via this data port. Port 1 is also known as the SDLC port, which stands for the Synchronous Data Link Control protocol. SDLC was defined by IBM. In the Type 1 standard, data is routed through Port 1 to two or more Bus Interface Units, or BIUs, and then to the rest of the cabinet and intersection hardware. The power connector (port 'A') pins are defined on page 359 of the 3000 Series Operating Manual. The Port 1 pins are defined on page 375 of the manual. Peek uses I/O codes to map input and output signals to the pins on the BIUs. These codes are listed on page 14 of this bulletin, and page 16 lists a way to create custom mappings. TS-2 Type 2 The Type 2 variant of the TS-2 standard is a sort of hybrid between TS-1 and TS-2 Type 1. Internally, it uses the same communications protocols used in the TS-2 Type 1 controller to map the controller's outputs to the same three MilSpec (MS-A, B, C) connectors from a TS-1 controller. However, the TS-2 Type 2 controller also has the ability to move its outputs around on the pins of the three connectors. This is known as "Signal Head Steering." A Type 2 controller may also include the communications ports of a Type 1 controller to facilitate additional data exchange between the controller, an MMU, detector racks, a master controller, and a PC. The input and output mapping of a standard 3000 Series Type 2 controller are listed on pages of the 3000 Series Operating Manual. Type 2 port configuration is beyond the scope of this bulletin; more details are available in Chapter 11: "Comm and System Setup" of the 3000 Series Operating Manual. Page 11 of 32

12 Cabinet Components A typical TS-2 Type 1 controller is designed to communicate with up to four terminal and facility (T/F) BIU units, four detector (DET) BIUs, and one malfunction management unit (MMU). Figure 11 Typical Connections to a TS-2 Type 1 controller Page 12 of 32

13 But most cabinets will require considerably less hardware. The simplest TS-2 Type 1 setup for a typical cabinet would have only one BIU to route signal outputs and pedestrian inputs, and an MMU to monitor operations. Figure 12 Peek's BIU Card Figure 13 Simple TS-2 Type 1 configuration BIUs A Bus Interface Unit (BIU) is a standard piece of hardware in a TS-2 Type 1 cabinet that acts as a communications interface between the controller, the backplane (terminals, load switches, facilities, etc.), and the detector racks. Its functions include accepting controller digital signals, routing and controlling load switch outputs, and conditioning and converting call inputs coming to the controller from terminals, facilities, and detectors. A BIU is defined as part of the NEMA TS-2 standard and there are a variety of manufacturers of compatible BIU units in the industry. Any of these will work with the 3000 Series TS-2 Type 1 controller as long as they have an up-to-date version of firmware installed. Row B Row A TOP of card pin1a The rear connector of the BIU is where the cabinet inputs and outputs are connected. Each rear connector has two vertical rows of 32 pins, with the rows labeled 'A' and 'B'. In the standard, Pin 1A is defined to appear at the top right when looking at the back of the card from the rear. From this angle, the B row of pins is on the left side. MMU An MMU, such as Peek Traffic's Double Diamond Malfunction Monitoring Unit, compares the output of the controller to the actual signals at the field terminals. It has a customized Compatibility Card installed in the slot at the lower left corner of the unit. The MMU uses this to check the operation of the Controller, and the various signal lines, for conditions that cannot be allowed to occur in the intersection. The controller also double-checks the operation of the MMU. If a problem is detected, either the MMU or the controller can then place the intersection into the Flash state. Figure 14 Pins on a BIU card Page 13 of 32

14 Default BIU Input/Output Mapping By default, a 3000 Series controller that has been configured for TS-2 Type 1 operation will route its inputs and outputs through Port 1 using these I/O Codes, which correspond to these BIU pins. Table 4 I/O Mapping Codes for BIUs 1 and 2 BIU 1 Pins I/O Code NEMA Functions BIU 2 Pins I/O Code NEMA Functions 2a 1021 Ch 1 Red Driver (O) 2a 2021 Ch 9 Red Driver (O) 2b 1022 Ch 1 Yellow Driver (O) 2b 2022 Ch 9 Yellow Driver (O) 3a 1031 Ch 1 Green Driver (O) 3a 2031 Ch 9 Green Driver (O) 3b 1032 Ch 2 Red Driver (O) 3b 2032 Ch 10 Red Driver (O) 4a 1041 Ch 2 Yellow Driver (O) 4a 2041 Ch 10 Yellow Driver (O) 4b 1042 Ch 2 Green Driver (O) 4b 2042 Ch 10 Green Driver (O) 5a 1051 Ch 3 Red Driver (O) 5a 2051 Ch 11 Red Driver (O) 5b 1052 Ch 3 Yellow Driver (O) 5b 2052 Ch 11 Yellow Driver (O) 6a 1061 Ch 3 Green Driver (O) 6a 2061 Ch 11 Green Driver (O) 6b 1062 Ch 4 Red Driver (O) 6b 2062 Ch 12 Red Driver (O) 7a 1071 Ch 4 Yellow Driver (O) 7a 2071 Ch 12 Yellow Driver (O) 7b 1072 Ch 4 Green Driver (O) 7b 2072 Ch 12 Green Driver (O) 8a 1081 Ch 5 Red Driver (O) 8a 2081 Ch 13 Red Driver (O) 8b 1082 Ch 5 Yellow Driver (O) 8b 2082 Ch 13 Yellow Driver (O) 9a 1091 Ch 5 Green Driver (O) 9a 2091 Ch 13 Green Driver (O) 9b 1092 Ch 6 Red Driver (O) 9b 2092 Ch 14 Red Driver (O) 10a 1101 Ch 6 Yellow Driver (O) 10a 2101 Ch 14 Yellow Driver (O) 10b 1102 Ch 6 Green Driver (O) 10b 2102 Ch 14 Green Driver (O) 11a 1111 Ch 7 Red Driver (O) 11a 2111 Ch 15 Red Driver (O) 11b 1112 Ch 7 Yellow Driver (O) 11b 2112 Ch 15 Yellow Driver (O) 12a 1121 Ch 7 Green Driver (O) 12a 2121 Ch 15 Green Driver (O) 12b 1122 Ch 8 Red Driver (O) 12b 2122 Ch 16 Red Driver (O) 13a 1131 Ch 8 Yellow Driver (O) 13a 2131 Ch 16 Yellow Driver (O) 13b 1132 Ch 8 Green Driver (O) 13b 2132 Ch 16 Green Driver (O) 14a 1141 TBC Auxiliary 1 (O) 14a 2141 TBC Auxiliary 3 (O) 14b 1142 TBC Auxiliary 2 (O) 14b 2142 Free / Coord Status (O) 15a 1151 Preempt 1 Status (O) 15a 2151 Preempt 3 Status (O) 15b 1152 Preempt 2 Status (O) 15b 2152 Preempt 4 Status (O) 16a 1161 Preempt 1 Detector (I) 16a 2161 Preempt 5 Status (O) 16b 1162 Preempt 2 Detector (I) 16b 2162 Preempt 6 Status (O) 17a 1171 Test A (I) 17a 2171 Preempt 3 Detector (I) 17b 1172 Test B (I) 17b 2172 Preempt 4 Detector (I) 18a 1181 Automatic Flash (I) 18a 2181 Preempt 5 Detector (I) 18b 1182 Dimming Enable (I) 18b 2182 Preempt 6 Detector (I) 19a 1191 Manual Control Enable (I) 19a 2191 CNA II (I) 19b 1192 Interval Advance (I) 19b 2192 Spare 20a 1201 Min Recall all Phases (I) 20a 2201 Spare 20b 1202 External Start (I) 20b 2202 Spare 21a 1211 TBC On Line (I) 21a 2211 Spare 21b 1212 Stop Time Ring 1 (I) 21b 2212 Inhibit Max Ring 1 (I) 22a 1221 Stop Time Ring 2 (I) 22a 2221 Inhibit Max Ring 2 (I) 22b 1222 Max II Ring 1 (I) 22b 2222 Local Flash Status (I) 23a 1231 Max II Ring 2 (I) 23a 2231 MMU Flash Status (I) 23b 1232 Force Off Ring 1 (I) 23b 2232 Alarm 1 (I) 24a 1241 Force Off Ring 2 (I) 24a 2241 Alarm 2 (I) 24b 1242 CNA I (I) 24b 2242 Free (I) 25a 1251 Walk Rest Modifier (I) 25a 2251 Test C (I) 25b 1252 Opto Ped Detector 1 (I) 25b 2252 Opto Ped Det 5 (Sig Plan A) (I) 26a 1261 Opto Ped Detector 2 (I) 26a 2261 Opto Ped Det 6 (Sig Plan B) (I) 26b 1262 Opto Ped Detector 3 (I) 26b 2262 Opto Ped Detector 7 (I) 27a 1271 Opto Ped Detector 4 (I) 27a 2271 Opto Ped Detector 8 (I) In the standard NEMA TS-2 Type 1 mapping, BIUs 1 through 4 are used for terminal and facilities connections, with BIU01 providing the core critical connections, such as signal outputs and pedestrian and preemption inputs. BIU02 expands these capabilities for more signals and detectors. Page 14 of 32

15 BIUs 3 and 4 provide more phase and status information connections. Table 5 I/O Mapping Codes for BIUs 3 and 4 BIU 3 Pins I/O Code NEMA Function BIU 4 Pins I/O Code NEMA Function 2a 3021 Timing Plan A (O) 2a 4021 Phase 1 On (O) 2b 3022 Timing Plan B (O) 2b 4022 Phase 2 On (O) 3a 3031 Timing Plan C (O) 3a 4031 Phase 3 On (O) 3b 3032 Timing Plan D (O) 3b 4032 Phase 4 On (O) 4a 3041 Offset 1 (O) 4a 4041 Phase 5 On (O) 4b 3042 Offset 2 (O) 4b 4042 Phase 6 On (O) 5a 3051 Offset 3 (O) 5a 4051 Phase 7 On (O) 5b 3052 Automatic Flash Status (O) 5b 4052 Phase 8 On (O) 6a 3061 Syst Spec Function 1 (O) 6a 4061 Phase 1 Next (O) 6b 3062 Syst Spec Function 2 (O) 6b 4062 Phase 2 Next (O) 7a 3071 Syst Spec Function 3 (O) 7a 4071 Phase 3 Next (O) 7b 3072 Syst Spec Function 4 (O) 7b 4072 Phase 4 Next (O) 8a 3081 Reserved 8a 4081 Phase 5 Next (O) 8b 3082 Reserved 8b 4082 Phase 6 Next (O) 9a 3091 Reserved 9a 4091 Phase 7 Next (O) 9b 3092 Status Bit A Ring 1 (O) 9b 4092 Phase 8 Next (O) 10a 3101 Status Bit B Ring 1 (O) 10a 4101 Phase 1 Check (O) 10b 3102 Status Bit C Ring 1 (O) 10b 4102 Phase 2 Check (O) 11a 3111 Status Bit A Ring 2 (O) 11a 4111 Phase 3 Check (O) 11b 3112 Status Bit B Ring 2 (O) 11b 4112 Phase 4 Check (O) 12a 3121 Status Bit C Ring 2 (O) 12a 4121 Phase 5 Check (O) 12b 3122 Red Rest Ring 1 (I) 12b 4122 Phase 6 Check (O) 13a 3131 Red Rest Ring 2 (I) 13a 4131 Phase 7 Check (O) 13b 3132 Omit Red Clear Ring 1 (I) 13b 4132 Phase 8 Check (O) 14a 3141 Omit Red Clear Ring 2 (I) 14a 4141 Address Bit 0 (I) 14b 3142 Ped Recycle Ring 1 (I) 14b 4142 Address Bit 1 (I) 15a 3151 Ped Recycle Ring 2 (I) 15a 4151 Address Bit 2 (I) 15b 3152 Alternate Sequence A (I) 15b 4152 Address Bit 3 (I) 16a 3161 Alternate Sequence B (I) 16a 4161 Address Bit 4 (I) 16b 3162 Alternate Sequence C (I) 16b 4162 Spare 17a 3171 Alternate Sequence D (I) 17a 4171 Spare 17b 3172 Phase 1 Omit (I) 17b 4172 Spare 18a 3181 Phase 2 Omit (I) 18a 4181 Spare 18b 3182 Phase 3 Omit (I) 18b 4182 Spare 19a 3191 Phase 4 Omit (I) 19a 4191 Reserved 19b 3192 Phase 5 Omit (I) 19b 4192 Reserved 20a 3201 Phase 6 Omit (I) 20a 4201 Reserved 20b 3202 Phase 7 Omit (I) 20b 4202 Reserved 21a 3211 Phase 8 Omit (I) 21a 4211 Reserved 21b 3212 Phase 1 Hold (I) 21b 4212 Phase 1 Ped Omit (I) 22a 3221 Phase 2 Hold (I) 22a 4221 Phase 2 Ped Omit (I) 22b 3222 Phase 3 Hold (I) 22b 4222 Phase 3 Ped Omit (I) 23a 3231 Phase 4 Hold (I) 23a 4231 Phase 4 Ped Omit (I) 23b 3232 Phase 5 Hold (I) 23b 4232 Phase 5 Ped Omit (I) 24a 3241 Phase 6 Hold (I) 24a 4241 Phase 6 Ped Omit (I) 24b 3242 Phase 7 Hold (I) 24b 4242 Phase 7 Ped Omit (I) 25a 3251 Phase 8 Hold (I) 25a 4251 Phase 8 Ped Omit (I) 25b 3252 Opto In Timing Plan A (I) 25b 4252 Opto In Offset 1 (I) 26a 3261 Optp In Timing Plan B (I) 26a 4261 Optp In Offset 2 (I) 26b 3262 Opto In Timing Plan C (I) 26b 4262 Opto In Offset 3 (I) 27a 3271 Opto In Timing Plan D (I) 27a 4271 Spare Page 15 of 32

16 If used, BIUs 9, 10, 11, and 12 are installed into detector racks and provide inputs for standard detectors, such as loop, WIM, or video detectors. Unlike the T/F BIUs, the default definitions for detection BIUs only use 32 of the 64 backplane pins. Table 6 I/O Mapping Codes for BIUs 9 and 10 BIU 9 Pins I/O Code NEMA Functions BIU 10 Pins I/O Code NEMA Functions 9b 9092 Channel 1 Call (I) 9b A092 Channel 17 Call (I) 10a 9101 Channel 2 Call (I) 10a A101 Channel 18 Call (I) 10b 9102 Channel 3 Call (I) 10b A102 Channel 19 Call (I) 11a 9111 Channel 4 Call (I) 11a A111 Channel 20 Call (I) 11b 9112 Channel 5 Call (I) 11b A112 Channel 21 Call (I) 12a 9121 Channel 6 Call (I) 12a A121 Channel 22 Call (I) 12b 9122 Channel 7 Call (I) 12b A122 Channel 23 Call (I) 13a 9131 Channel 8 Call (I) 13a A131 Channel 24 Call (I) 13b 9132 Channel 9 Call (I) 13b A132 Channel 25 Call (I) 14a 9141 Channel 10 Call (I) 14a A141 Channel 26 Call (I) 14b 9142 Channel 11 Call (I) 14b A142 Channel 27 Call (I) 15a 9151 Channel 12 Call (I) 15a A151 Channel 28 Call (I) 15b 9152 Channel 13 Call (I) 15b A152 Channel 39 Call (I) 16a 9161 Channel 14 Call (I) 16a A161 Channel 30 Call (I) 16b 9162 Channel 15 Call (I) 16b A162 Channel 31 Call (I) 17a 9171 Channel 16 Call (I) 17a A171 Channel 32 Call (I) BIUs 11 and 12 simply provide another 32 detector inputs. Table 7 I/O Mapping Codes for BIUs 11 and 12 BIU 11 Pins I/O Code NEMA Function BIU 12 Pins I/O Code NEMA Function 9b B092 Channel 33 Call (I) 9b C092 Channel 49 Call (I) 10a B101 Channel 34 Call (I) 10a C101 Channel 50 Call (I) 10b B102 Channel 35 Call (I) 10b C102 Channel 51 Call (I) 11a B111 Channel 36 Call (I) 11a C111 Channel 52 Call (I) 11b B112 Channel 37 Call (I) 11b C112 Channel 53 Call (I) 12a B121 Channel 38 Call (I) 12a C121 Channel 54 Call (I) 12b B122 Channel 39 Call (I) 12b C122 Channel 55 Call (I) 13a B131 Channel 40 Call (I) 13a C131 Channel 56 Call (I) 13b B132 Channel 41 Call (I) 13b C132 Channel 57 Call (I) 14a B141 Channel 42 Call (I) 14a C141 Channel 58 Call (I) 14b B142 Channel 43 Call (I) 14b C142 Channel 59 Call (I) 15a B151 Channel 44 Call (I) 15a C151 Channel 60 Call (I) 15b B152 Channel 45 Call (I) 15b C152 Channel 61 Call (I) 16a B161 Channel 46 Call (I) 16a C161 Channel 62 Call (I) 16b B162 Channel 47 Call (I) 16b C162 Channel 63 Call (I) 17a B171 Channel 48 Call (I) 17a C171 Channel 64 Call (I) Note On BIUs 9, 10, 11, and 12, the detector outputs such as Detector Reset Slots 1,2, 3 & 4 are not mappable. These are the default pin inputs and outputs for the eight available BIUs in a TS-2 Type 1 cabinet. If you wish to program the inputs/outputs of the BIUs to be something other than what is shown in these four tables, refer to the next section. Page 16 of 32

17 Customizing BIU Input and Output Mapping BIU I/O Mapping allows the operator of a 3000 Series traffic controller to assign any controller input or output to any physical BIU input or output pin. Outputs are always directly assigned to BIU output pins. But for inputs, a given BIU input can be driven by a logical combination of two other inputs, or two other outputs, or an input and an output. These virtual inputs and outputs can be combined to set the state of a BIU input using one of six possible logical operators: AND, OR, NOR, NAND, AND-, or OR-. Note A logical NOT can be achieved by using the OR- (OR NOT) operator. To achieve a signal inversion, place a 0 (zero) in the A input of the operator, and the signal you wish to invert in the NOT B input. Since A is always OFF in this case, the output is then just NOT B. This flexibility allows a controller's seldom-used inputs and outputs to be reassigned for additional input and output availability, or it can be used to reduce the number of BIUs required in a given cabinet, and finally, it can give the user more power compared to existing functions such as Dynamic Omits, Dynamic Recalls, etc. Note The mapping of BIU inputs and outputs is NOT part of the NEMA TS-2 standard. This is a modification of otherwise NEMA compatible hardware to perform a non-standard function. All of these mappings are done using four-digit I/O Mapping Codes which follow a specific pattern, based on which BIU is being addressed and which pin and row on that BIU is being used for the function. The previous section provided the default mapping of I/O Codes to controller functions, but any input or output can be mapped to nearly any BIU pin, with the exception that some pins are hard-designated as inputs only, and some others are designated outputs only. See Table 8 (page 26) for details on which pins can be mapped as inputs and which can be outputs. Each Map code has four digits of the form XYYZ, where: X YY = the BIU number. If using BIUs 10, 11, or 12, the codes are A, B, and C, respectively. (To type an A on the 3000 interface: press SHIFT-0, to type a B: SHIFT-1, and to type a C: SHIFT-2.) = the pin number, from 01 to 32. Pins are numbered from the top of the card to the bottom. Z = the Row indicator, where Row A = 1 and Row B = 2 For example, if one wanted to map to the 12 th pin in the B row of BIU 11, the I/O Mapping Code to use would be B122. All of the TS-2 Type 2 BIU I/O Mapping tools are controlled from a single menu under the Change Data > Utilities menu. When navigating from the Main Menu of a 3000 Series controller, press 3 > 8 > 9 to access the I/O Mapping Menu. Note Option 9 (the I/O Mapping Menu) is only available on the Utilities menu of the TS-2 and NTCIP versions of the 3000 Series firmware. The TS-1 version of the firmware does not have an Option 9 on the Utilities menu. BIU I/O Mapping (v2.0) Menu 1. Activate Mapping 5. Load Nema map 2. Clear BIU I/O Map 6. Copy MMU Channels 3. Input mapping 7. Copy to EEPROM 4. Output mapping 8. Copy from EEPROM Figure 15 I/O Mapping Menu (before activation) Page 17 of 32

18 If you select option 1 on this screen and activate BIU I/O Mapping, the screen will change, displaying: BIU I/O Mapping (v2.0) Menu 1. Deactivate Mapping 5. Load Nema map 2. Clear BIU I/O Map 6. Copy MMU Channels 3. Input mapping 7. Copy to EEPROM 4. Output mapping 8. Copy from EEPROM MAPPING IS ACTIVE! Figure 16 I/O Mapping Menu (with mapping active) Caution Selecting Items 1 or 2 on the above menu while the controller is operating an intersection will cause an MMU Fault and place the intersection in Flash. It is recommended that I/O Mapping be set up in a bench environment only. One other note about using the custom BIU I/O Mapping with a 3000 Series controller... if you opt to use the custom mapping feature, be aware that the Dimming feature cannot be used. If a given output that normally drives a phase or pedestrian indication is set to use dimming, and the output is mapped to provide a different output, then the output would not be "steady". To avoid this possibility, Dimming is ignored if I/O Mapping is active. Activating/Deactivating BIU I/O Mapping The default state is to have BIU I/O Mapping deactivated, as is indicated by the first option on the BIU I/O Mapping Menu (Figure 15). This means that the TS-2 Type 1 controller will use the default mapping shown in the "Default BIU Input Output Mapping" section of these release notes. However, if you wish to create a custom mapping for the BIU inputs and outputs, the changes must be made, and then after all the map setting changes have been made, the last step is selecting option 1 on the I/O Mapping Menu (Main Menu > 3 > 8 > 9) to activate the mapping function. Activating I/O Mapping When you select the activation option, the following warning will appear: WARNING: The controller will remap all inputs and outputs to reflect any changes made! Press ENTER to proceed or MENU to cancel Figure 17 Warning message when Activating the User Map If the ENTER button is pressed at this point, the controller will go ahead and activate the custom mapping. BIU I/O MAP LOADED Press MENU key to exit this screen Figure 18 Status screen showing that the mapping has been activated Page 18 of 32

19 After the mapping has been activated, the I/O Mapping Menu will display a new, rather understated message at the bottom: BIU I/O Mapping Menu 1. Deactivate Mapping 5. Load Nema map 2. Clear BIU I/O Map 6. Copy MMU Channels 3. Input mapping 7. Copy to EEPROM 4. Output mapping 8. Copy from EEPROM MAPPING IS ACTIVE! Figure 19 I/O Mapping Menu with the user's map activated Deactivating the I/O Mapping If a custom mapping is already implemented and you wish to deactivate it, first go to the BIU I/O Mapping Menu (Main Menu > 3 > 8 > 9), verify that the bottom of the screen shows the "MAPPING IS ACTIVE!" message. If you are sure that you do actually want to deactivate the mapping, then select 1. Deactivate User Map and press the ENTER key. Deactivating the User Mapping will return the 3000 Series controller to using the factory default, i.e. NEMA-standard, BIU mapping scheme. Clearing BIU I/O Mappings The number 2 item on the BIU I/O Mapping Menu is the Clear BIU I/O Map control. This command will clear out whatever is currently stored in the input and output map fields, as well as the virtual input and output states in the controller, and replace them with zeros. After selecting this command, a warning message appears: WARNING: The controller will clear the entire BIU I/O map! Press ENTER to proceed or MENU to cancel Figure 20 Warning message when clearing the Input Map If the user is certain that she wishes to clear these user-defined values, pressing the ENTER button will erase them. The following screen will verify that the data has been erased: BIU I/O MAP CLEARED Press MENU key to exit this screen Figure 21 Verification of the cleared BIU mapping Page 19 of 32

20 Configuring Input Mappings Selection 3 on the BIU I/O Mapping Menu displays a series of screens where the input signals can be assigned. To assign a signal to a pin, enter the code numbers for Inputs and Virtual Inputs, or Virtual Outputs. Use the Y/N key to toggle between AND, AND-, NAND, OR, OR-, and NOR on the logical operator line of the screen. VD: Puts a vehicle call when activated Line 1 Input or Output Logical Operator Line 2 Input or Output VD01 VD02 VD03 VD04 VD05 VD06 VD07 VDO OR AND AND- OR- OR- OR OR OR PGDN or PGUP for more inputs In the example screen above: 1. Vehicle Detector 1 Input (VDø1) will be active when Vehicle Detector 1 Input (9092) is active, OR when Vehicle Detector 16 Input (9171) is active. 2. Vehicle Detector 2 Input (VDø2) will be active when Vehicle Detector 14 Input (9161) AND Vehicle Detector 15 Input (9162) are both active. 3. Vehicle Detector 3 Input (VDø3) will be active when Vehicle Detector 3 Input (9102) is active AND Phase 2 is not active (4022, AND-). Here 4022 will be entered in the Phase 2 On output field also. However, Phase 2 On can be mapped to any available output pin on any BIU (See Table 11 on page 26.) 4. Vehicle Detector 4 Input (VDø4) shall be active when Vehicle Detector 4 Input (9111) is active OR Phase 3 is not next (4071, OR-). Here 4071 will be entered in Phase 3 Next Output field also, however Phase 3 Next can be mapped to any available output pin on any BIU (See Table 11 on page 26.) 5. Vehicle Detector 5 Input (VDø5) is the inverse of the Vehicle Detector 12 Input (9151). See page 24 for a table of the abbreviations used in these screens. (Table 9) Using the Logical Operators with Input Mappings The programmable inputs of the BIUs can be programmed to respond to a pair of logical inputs using one of these six logical operators. These operators specify what signal will be reported to the controller, based on the logical state of each of the two input sources. Table 8 Logical I/O Mapping operators Operator Logical Meaning Description AND (A AND B) If Line 1 AND Line 2 are ON, the Input is ON AND- (A AND NOT B) If Line 1 is ON AND Line 2 is OFF, the Input is ON NAND (NOT(A AND B)) If Line 1 is OFF AND Line 2 is OFF, the Input is ON OR (A OR B) If either Line 1 OR Line 2 are ON, the Input is ON OR- (A OR NOT B) If either Line 1 is ON OR Line 2 is OFF, the Input is ON NOR (Neither A NOR B) If Line 1 is OFF AND Line 2 is OFF, the input is ON Note To create a NOT input using the above operators, simply use the OR- operator and enter the signal to be inverted in the line 2 input. Then set line 1 to 0 (zero). The output of this logical operation is just the inverse of the input signal. Page 20 of 32