Woodward AtlasPC Hardware Manual
  1. Manuals
  2. Brands
  3. Woodward Manuals
  4. Control Systems
  5. AtlasPC
  6. Hardware manual

Woodward AtlasPC Hardware Manual

Digital control
Hide thumbs Also See for AtlasPC:
Table of Contents

Advertisement

Quick Links

Download this manual
Hardware Manual
AtlasPC™ Digital Control
Volume 2
Manual 85586 consists of 2 volumes (85586V1 & 85586V2).
Manual 85586V2 (Revision G)

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the AtlasPC and is the answer not in the manual?

Questions and answers

Related Manuals for Woodward AtlasPC

Summary of Contents for Woodward AtlasPC

  • Page 1 Hardware Manual AtlasPC™ Digital Control Volume 2 Manual 85586 consists of 2 volumes (85586V1 & 85586V2). Manual 85586V2 (Revision G)
  • Page 2 Revisions—Text changes are indicated by a black line alongside the text. Woodward Governor Company reserves the right to update any portion of this publication at any time. Information provided by Woodward Governor Company is believed to be correct and reliable. However, no responsibility is assumed by Woodward Governor Company unless otherwise expressly undertaken.

  • Page 3: Table Of Contents

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Contents Volume II contains the AtlasPC™ detailed Distributed I/O information. For all other hardware information, see Volume I. I/O ..................1  ISTRIBUTED 1. PC104 P ..........2  HAPTER ROFIBUS NTERFACE Introduction ......................2  ...
  • Page 4 Figure 2-1. Typical CAN Network Example ............19   Figure 6-1. Allen-Bradley Flex I/O Configuration ..........51   Figure 6-2. AtlasPC Chassis GAP Block .............. 54   Figure 6-3. Example of GAP Application FB_Module .......... 54   Figure 6-4. FB_EQUIP Block Example ..............55  ...
  • Page 5 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Illustrations and Tables Figure 6-54. MODBUS_M Block Group 3 Analog Write RPT Example ....97   Figure 6-55. MODBUS_M Block Group 4 Analog Write RPT Example ....97   Figure 6-56. 3170-MBS Status Information Addresses ........99  ...
  • Page 6 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Illustrations and Tables Figure 6-108. Automation Direct Modbus RS-232 Serial Connection ....137   Figure 6-109. T1K-08ND3 Sink/External Power Configuration ......138   Figure 6-110 Example of T1K-08ND3 Module Wiring ........139   Figure 6-111. T1K-08ND3 Memory Map ............139  ...

  • Page 7: Distributed I/O

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Distributed I/O The AtlasPC™ control supports industry standard field bus protocols to take advantage of distributed I/O products from alternate manufacturers. Through various networking options, expansion of the AtlasPC system is virtually unlimited.

  • Page 8: Pc104 Profibus Interface

    Woodward Interface Tools Hardware for End Users Profibus Module The Profibus hardware module used on the AtlasPC control system is a PC/104 form factor ApplicomIO PC104-DPIO board, equipped with one Profibus port, capable of handling Profibus-DP (Distributed Peripherals) protocol in both Master (Class1, Class2) and Slave modes up to 12Mbps.
  • Page 9 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Interface Cables and Connectors The Profibus network is a balanced transmission line corresponding to the standard EIA RS-485, terminated at both ends. The Profibus standard EN50170 defines two variations of the bus cable for Profibus-FMS and Profibus-DP.
  • Page 10 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The cable specification below is provided for convenience and is typical for the Profibus industry. Belden 3079A Profibus Cable 57 lbs/1,000 ft (~85 kg/1000 m) Weight: NEC PLTC CL2 CMG CEC CMG Ratings: #22 AWG solid high conductivity Cu (~0.3 mm²)
  • Page 11 It is the user’s responsibility to ensure EMC compliance of their system, if necessary, by using distributed modules that are CE compliant. The following Profibus slave hardware has been tested with the AtlasPC control to confirm functionality. 1) All Woodward devices designed for Profibus...
  • Page 12 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 2) Allen-Bradley Flex I/O Part Number Description 3170-PDP I/O Network Interface for Profibus (Slave) (ProSoft Technologies) 1794-IB16 Discrete Input (Sink) 1794-OV16 Discrete Output (Sink) 1794-OW8 Discrete Output (Relay) 1794-IE8/B Analog Input (Current)

  • Page 13: Software For Application Developers

    GSD files and assigning network addresses. Once the Profibus I/O configuration is completed, it must be downloaded to the AtlasPC control and stored with the GAP application. Woodward...
  • Page 14 Even though they can use other IRQ settings, it is necessary that they share IRQ 5 for proper operation and to prevent conflict with other devices in the AtlasPC system. All IRQs are factory set and must not be changed by the end user.
  • Page 15 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Select DPRAM Base Address D4000, Interrupt Vector IRQ 5, and PC104/ISA PC104_DPIO. Select OK. Woodward...
  • Page 16 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Under Protocol, select Properties. Select 12 Mbit in Baud Rate. Select OK. Before a slave head (Network Interface Module) can be selected, the associated GSD file must be in the equipment library. If the GSD file doesn’t already exist in the library, it must be downloaded and saved within the Applicom setup files (C:\Program Files\ApplicomIO\2.1\Equipment Library\Profibus_gsd).
  • Page 17 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) In this example the Station number is selected as 001. (This is what is referred to as the node number.) Select the Modules Configuration Tab. Woodward...
  • Page 18 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 m. Build the module configuration by dragging the desired modules from the Available Module(s) window to the Configured Module(s) window. Select OK when done. This completes the Applicom setup. Once created, the Profibus configuration files can be found on the programming station under c:\program files\applicomIO\2.1\configIO\config_name.
  • Page 19 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Save the configuration and copy all files from the ConfigIO directory to the AtlasPC control using AppManager. (C:/Woodward/Applications directory) Profibus Software Configuration (GAP) After creating the Profibus I/O configuration, the GAP application must be programmed to match.
  • Page 20 Once completed, the GAP application must be compiled and downloaded to the AtlasPC control using AppManager. Once the GAP application is started on the AtlasPC control’s PC, the Profibus module will automatically initialize and start the Profibus Network. All nodes will be updated from the Applicom module in a circular queue fashion, once every scan rate.

  • Page 21: Pc104 Devicenet Interface

    Woodward Interface Tools Hardware for End Users DeviceNet Module The DeviceNet hardware module used on the AtlasPC control system is a PC/104 form factor ApplicomIO PC104-DVNIO board, equipped with one DeviceNet port capable of handling DeviceNet protocol in both Master/Scanner and Slave modes up to 500 Kbps.
  • Page 22 Manual 85586V2 The ODVA standard for DeviceNet defines two variations of the bus cable that are compatible with the Phoenix COMBICON connector on the AtlasPC control— Thick and Thin types. The Thick cable is preferred and recommended for all uses. Most DeviceNet cable is not rated for temperatures above 80 °C, so be careful during installation to avoid hot routing areas.
  • Page 23 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) The cable specification below is provided for convenience and is typical for the DeviceNet industry. Belden 3082A DeviceNet Cable 108 lbs/1,000 ft Weight: UL PLTC, CMG, AWM, C(UL) AWM I/II A. Flame...
  • Page 24 Network Length Length of the CAN cabling is variable depending on many factors. Cable type is one factor that significantly affects maximum length. Woodward recommends only the “thick” cable type which is capable of the maximum length. CAN allows for a single trunk with drops to each (or multiple) nodes. The number of drops is not limited nor is the number of nodes applied on a single drop.

  • Page 25: Figure 2-1. Typical Can Network Example

    Terminating resistors should not be installed at the end of a drop line. They should be installed only at the two ends of the trunk line. Since termination resistors cannot be placed at the end of a drop line, the AtlasPC control is not provided with built-in network termination resistors. Woodward...
  • Page 26 The DeviceNet network is different from many others in that a 24 Vdc power supply is distributed with the network. The AtlasPC system does not provide this supply, and all customers using DeviceNet will have to provide a separate and isolated supply to ensure proper network operation.
  • Page 27 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) 2) Allen-Bradley Flex I/O Part Number Description 1794-ADM I/O Network Interface for DeviceNet (Slave) 1794-IB16 Discrete Input (Sink) 1794-OV16 Discrete Output (Sink) 1794-OW8 Discrete Output (Relay) 1794-IE8/B Analog Input (Current) 1794-OE4/B...

  • Page 28: Software For Application Developers

    The DeviceNet network is configured using the DeviceNet Configuration Tool provided on CD-ROM with the AtlasPC control (ApplicomIO 2.1 Console). This tool supports defining the AtlasPC DeviceNet board as a master or slave device. For master operation, the slave devices are defined and configured by importing their EDS files and assigning network addresses.
  • Page 29 Even though they can use other IRQ settings, it is necessary that they share IRQ 5 for proper operation and to prevent conflict with other devices in the AtlasPC system. All IRQs are factory set and must not be changed by the end user.
  • Page 30 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Under Board Configuration, select Add Board. Under Add New Board, select Diagnostic and Manual Configuration. Select DPRAM Base Address D4000, Interrupt Vector IRQ 5, and PC104/ISA PC104_DVNIO. Woodward...
  • Page 31 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Under Files --> Properties, Make sure Expert Mode is Checked. Woodward...
  • Page 32 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Under Protocols, select Properties. Select the correct Values for the Network. The DeviceNet Net Timeout will be 4 times the expected packet rate, and must be set with care. Drag and Drop all nodes in the Network from the Equipment Library to the DeviceNet Master.
  • Page 33 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Select a unique MACID for each node Select Little Endian vs Big Endian. If a node cannot be found in the Library, It can be added using Library Add. m. Select the EDS file supplied by the Nodes Manufacturer.
  • Page 34 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The Atlas can also be configured as a DeviceNet Slave, by selecting DeviceNet Local Slave. First Select a MACID. Then enter the relevant number of bytes in the appropriate fields. Once all nodes have been entered, select File Save.
  • Page 35 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Copy all files from the ConfigIO directory to the AtlasPC control’s PC using AppManager. Once created, the DeviceNet configuration files can be found on the programming station under c:\program files\applicomIO\2.1\configIO. Woodward...
  • Page 36 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 DeviceNet Software Configuration (GAP) After creating the DeviceNet I/O configuration, the GAP application must be programmed to match. The steps necessary to program the DeviceNet module in GAP are as follows: Select FB_MODULE for slot 6 and or 7 in the Atlas Chassis.
  • Page 37 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Every Node is then defined using specific GAP blocks (SPC, VPC, SWIFT) or generic blocks (FB_AI, FB_AO, FB_BI, FB_BO). For examples of a complete GAP setups for DeviceNet, see the Distributed I/O Examples later in this chapter.
  • Page 38 Once completed, the GAP application must be compiled and downloaded to the AtlasPC control using AppManager. Once the GAP application is started on the AtlasPC control’s PC, the DeviceNet module will automatically initialize and start the DeviceNet Network. All nodes will be updated from the Applicom module in a circular queue fashion, once every scan rate.

  • Page 39: Pc104 Ethernet Interface

    AtlasPC™ control. The AtlasPC control has one Ethernet port on the CPU and one optional PC104 Ethernet board. If the second PC104 Ethernet board is installed, it can be used ®...
  • Page 40 Most users will purchase finished cables, but the following information is provided for users that need to build custom cables. The AtlasPC control requires double-shielded cable (SSTP) for Ethernet in order to be appropriately immune to EMC in industrial environments. Below are the general requirements for Category 5 Ethernet cable.
  • Page 41 Standard Lengths: Table 3-2. Belden Ethernet cable Cable Connectors The typical Ethernet cable connector is an RJ45 style connector. The following products are provided for reference and are compatible with the AtlasPC RJ45 interface connector. Manufacturer Website Tyco Electronics (Amp) 5-569550 www.amp.com...
  • Page 42 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Ethernet Connector Pinout Connector Signal Mnemonic RJ45F Shielded RJ45 female receptacle Shield AC Coupled to Chassis Table 3-3. RJ45 10/100 Base-TX Pinout Use shielded Ethernet cable only! Use of non-shielded cable may result in permanent system damage.
  • Page 43 Woodward recommends halving these maximum distances for use in industrial environments. Shielding Double shielded Ethernet cable must be used between the AtlasPC control and any other devices. Standard Ethernet cables used in office environments are NOT shielded. Unshielded cables will very likely lead to communication problems and unreliable control operation.

  • Page 44: Software For Application Developers

    • If two or more AtlasPC controls are to be used on the same network, the IP addresses must be changed to unique addresses (valid for your particular network) or to DHCP mode, whichever is appropriate in order to avoid address conflicts.
  • Page 45 Whether you use DHCP or fixed address networks, you must configure all AtlasPC units, and to ensure proper operation of both ports, they must be on different domains. Refer to the Woodward software manual supplied with your control for further details.

  • Page 46: Chapter 4. Serial (Modbus) Interface

    (15 m/50 ft). In practice the standard is largely ignored beyond the most rudimentary implementation of electrical signals (±3 to ±15 volts). Woodward's implementation will support speeds up to 115K baud in AtlasPC systems. The actual specification allows 19.2K baud at up to 15 m (50 ft). Woodward...
  • Page 47 (1200 m/4000 ft) at high baud rates (115K). Woodward's implementation of RS-422 is actually a 4-wire RS-485 communications network. Since Woodward convention has been to call this RS- 422, this manual will continue to do so. However, it may be important to understand that the actual port is RS-485.
  • Page 48 For 2-wire networks, a termination network should be used at the two physical ends of the network. For 4-wire networks, Woodward has elected to use a termination network only across the receiver lines at either end of the network.
  • Page 49 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Shielding Shielded cable is required between the AtlasPC control and any other devices. Unshielded cables and improperly shielded cables are likely to cause communication problems and unreliable control operation. The shield must always be ac-coupled (connected through a capacitor) at one end and connected directly to earth on the opposite end for proper operation.
  • Page 50 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 SmartCore SIO # 3 Connector and Pinout Connector Signal Mnemonic DB9F Shielded DB9 female receptacle Shield CPU Comm 1 Connector and Pinout Connector Signal Mnemonic DB9F Shielded DB9 female receptacle SIG COM.
  • Page 51 It is the user’s responsibility to ensure EMC compliance of their system, if necessary, by using distributed modules that are CE compliant. The following Serial Modbus slave hardware has been tested with the AtlasPC control to confirm functionality. 1) All Woodward devices designed for Modbus.

  • Page 52: Software For Application Developers

    For more information on these and additional software tools mentioned in this chapter, see Woodward software manual 26103 (NT RTOS) or 26199 (VxWorks RTOS). The AtlasPC control is configured to communicate with a Serial network by performing the following steps: Determine slave and I/O modules to be used.
  • Page 53 AtlasPC Digital Control, Vol. II (Distributed I/O) Serial (Modbus) Software Configuration (Protocol) The AtlasPC control supports both the ASCII and RTU versions of the Modbus protocol. RTU is more widely used since it is the more efficient of the two.

  • Page 54: Pc104 Canopen Interface

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Chapter 5. PC104 CanOpen Interface CanOpen is a protocol that uses CAN (Controller Area Network). Currently, Woodward is developing the AtlasPC™ CanOpen interface module, and will document its use in this chapter in the near future. Woodward...

  • Page 55: Chapter 6. Distributed I/O Examples

    Direct, or any other supplier of Distributed I/O systems. It is hoped that these specific examples of I/O module configurations can be used as a foundation for building a majority of the AtlasPC control applications where Distributed I/O is needed. Ease in applying the Woodward software interface may differ from vendor to vendor.

  • Page 56: Allen-Bradley Flex I/O Example

    The 3170-PDP is a Network Interface Adapter that communicates between the FLEX I/O module backplane and AtlasPC/Master across the PROFIBUS DP network. The 3170-PDP module is a slave device to the AtlasPC control, and is a master controller of the FLEX I/O modules. The I/O data exchange occurs as follows: Output data is sent from the AtlasPC control across the PROFIBUS DP network to the 3170-PDP adapter.

  • Page 57: Figure 6-1. Allen-Bradley Flex I/O Configuration

    The number of read words or writes words can be 0 or more. In this example, the first read word received by the AtlasPC control from the Network Interface Adapter (3170-PDP) is the Adapter Status Word. This is followed by the input data from each Node, in the order of the installed I/O modules.
  • Page 58 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 This PSFT0882.GSD file is used by ApplicomIO tool to help set up the system. The ApplicomIO configuration tool automatically reads the PSFT0882.GSD file and extracts defaults used in the data exchange.
  • Page 59 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Module Document P/N Discrete Input (Sink) 1794-5.4 Discrete Output (Sink) 1794-5.29 Discrete Output (Relay) 1794-5.19 Analog Input (Current) 1794-5.6 Analog Output (Current) 1794-5.5 Thermocouple Input 1794-6.5.7 RTD Input 1794-6.5.4 Profibus Interface FLEX-UM-PDP-1.2...

  • Page 60: Figure 6-2. Atlaspc Chassis Gap Block

    GAP Application When setting up a new GAP application, create the chassis block with the appropriate network interface configuration for the AtlasPC control chosen. In Figure 6-2, an Applicom Profibus Master Network interface adapter is located in slot 6 and an Applicom Master DeviceNet Network interface adapter in slot 7.

  • Page 61: Figure 6-4. Fb_Equip Block Example

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Node 1 Ch. G1N1_ B16.BI_02 through 16 not shown Node 2 Ch. G1N2_OV16.BO_02 through 16 not shown Node 3 Node 4 Ch. G1N4_ E8/B.AI_02 through 16 not shown Node 5 Ch. G1N5_OE8/B AO_02 through 04 not shown Node 6 Ch.
  • Page 62 Once done, it is easier to find specific functions and I/O within a large GAP application. In this example, Woodward has formulated certain nomenclature rules to facilitate ease in navigating through the example application. Here are some rules to follow:...
  • Page 63 AtlasPC control per system, then they would be A2, A3, etc. 2. The board slots in the AtlasPC control are referred to as slots A01 – A07. The Profibus slot is A06 and the DeviceNet slot is A07 in this example.
  • Page 64 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 From the GSD file, the number of read and write addresses and their order were defined based on the physical order of the modules and the memory maps defined by Allen-Bradley. The GAP application is also constructed in the same order that the modules are ordered.

  • Page 65: Figure 6-5. 3170-Pdp Network Interface Memory Map

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) ProSoft Network Interface Adapter (3170-PDP) Module Based on the address spreadsheet, the ProSoft Network Interface Adapter 3170- PDP has one read and one write address word allocated in the memory map.

  • Page 66: Figure 6-6. Example Of 3170-Pdp Memory Map Read Gap Block

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The node address (Group address) changed bit is set when the node address switch setting has been changed since power up. The new node address does not take affect until the adapter has been powered down and then powered back up.

  • Page 67: Figure 6-7. Example Of 1794-Ib16 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Allen-Bradley 24 Vdc Sink Input (1794-IB16) Module In this example, the 1794-IB16 module is plugged into a 1794-TB3S base. See Figure 6-7 for example of 1794-IB16 module wiring. DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-IB16...

  • Page 68: Figure 6-8. 1794-Ib16 Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The memory map indicates that there are two read addresses and one write address. The condensed format used to set up the address spreadsheet only uses one read and one write address. See Figure 6-8 for memory map of Allen- Bradley 1794-IB16 Discrete input module.

  • Page 69: Figure 6-10. Example Of 1794-Ib16 Write Gap Block

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Data Word to be written to Module Spreadsheet Addresses Figure 6-10. Example of 1794-IB16 Write GAP Block To read the discrete input bits for the 1794-IB16 module, individual FB_BI blocks were used. See Figure 6-11 for example of GAP block configuration.
  • Page 70 By setting TRUE on the BI_R_1 input, the fault output is non-latching. Allen-Bradley 24 Vdc Sink Output (1794-OV16) Module In this example, the 1794-OV16 is connected to a Woodward 16 channel relay module. See Figure 6-12 for example of 1794-OV16 module wiring.

  • Page 71: Figure 6-12. Example Of 1794-Ov16 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) +28VDC TB49 + DISTRIBUTED I/O 28COM TB50 - Allen-Bradley FLEX I/O 1794-OV16 J1-23 Woodward J1-24 DISCRETE OUTPUT 16 Channel Relay J1-21 (-COM) P/N 5441-691 J1-22 (+24VDC) J1-19 DO (+) P/N 5441-419 (-COM) PBI.A1.A06.G1.N2_BO_01...

  • Page 72: Figure 6-14. Example Of 1794-Ov16 Gap Write Blocks

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 To write the discrete output bits for the 1794-OV16 module, individual FB_BO blocks were used. See Figure 6-14 for example of GAP write block configuration. Spreadsheet Address Bit to be written to Module (True or False from GAP application) Figure 6-14.

  • Page 73: Figure 6-15. Example Of 1794-Ow8 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) In this example, the relay outputs are individually fused to protect the module. See Figure 6-15 for example of 1794-OW8 module wiring. DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-OW8 RELAY OUTPUT (-COM)

  • Page 74: Figure 6-16. 1794-Ow8 Module Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-16. 1794-OW8 Module Memory Map To write the discrete output bits for the 1794-OW8 module, individual FB_BO blocks were used. See Figure 6-17 for example of GAP write block configuration.

  • Page 75: Figure 6-18. Example Of 1794-Ie8/B Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Allen-Bradley Analog Input (1794-IE8/B) Module In this example, loop powered transducers are shown. See Figure 6-18 for example of 1794-IE8/B module wiring. DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-IE8/B To 24COM ANALOG INPUT...

  • Page 76: Figure 6-19. 1794-Ie8/B Input Module Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The memory map indicates that there are nine read addresses and one write address. The condensed format used to set up the address spreadsheet specifies the same. See Figure 6-19 for the input memory map and Figure 6-20 for the output memory map for the 1794-IE8/B module.

  • Page 77: Figure 6-21. Example Of 1794-Ie8/B Read And Write Gap Blocks

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) In this example, this write block is set up with Range Select bits for all channels set to 0-21mA. The read block is set up to be able to read the status of the underrange bits for all channels and the Power Up bit (PU).

  • Page 78: Figure 6-22. 1794-Ie8/B And 1794-Oe4/B Analog Data Format Table

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-22. 1794-IE8/B and 1794-OE4/B Analog Data Format Table Figure 6-23. Example of 1794-IE8/B GAP Analog Write Blocks Woodward...

  • Page 79: Figure 6-24. Example Of 1794-Oe4/B Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Allen-Bradley Analog Output (1794-OE4/B) Module See Figure 6-24 for example of 1794-OE4/B module wiring. DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-OE4/B ANALOG OUTPUT 4-20mA AO (+) Load PBI.A1.A06.G1.N5_AO_01 AO (-) VO (+)

  • Page 80: Figure 6-25. 1794-Oe4/B Module Input Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The memory map indicates that there is one read address and 13 write addresses. The condensed format used to set up the address spreadsheet specifies one read address and 6 write addresses. From the output memory map addresses 6-9 are not used and 10-13 are used to specify safe state values that are not available in the condensed format.

  • Page 81: Figure 6-27. 1794-Oe4/B Write Range Selection Bits

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-27. 1794-OE4/B Write Range Selection Bits In this example, the read block is set up to monitor the four broken wire addresses and the power up bit on the module. The write blocks are set up to configure the module for multiplex control and 0-20mA range.

  • Page 82: Figure 6-29. Example Of 1794-Oe4/B Gap Analog Write Blocks

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 To write the analog output words for the 1794-OE4/B module, individual FB_AO blocks were used. The addressing for the analog output blocks needs to be in bytes like the analog input blocks. To convert from spreadsheet bit addresses to bytes, take the first bit of the word in the spreadsheet for the 1794-OE4/B module and divide by 8 bits/byte (96÷8=12).

  • Page 83: Figure 6-30. Example Of 1794-It8 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Allen-Bradley Thermocouple Input (1794-IT8) Module In this example, the first six channels are used for thermocouples and the last two channels are used for monitoring the reference junction temperatures. See Figure 6-30 for example of 1794-IT8 module wiring.

  • Page 84: Figure 6-31. 1794-It8 Module Input Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The memory map indicates that there are eleven read addresses and 3 write address. The condensed format used to set up the address spreadsheet specifies eleven read addresses and 4 write addresses. The extra write word is not defined in the memory map, therefore no GAP block is used.

  • Page 85: Figure 6-33. 1794-It8 Write Word 0

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-33. 1794-IT8 Write Word 0 Figure 6-34. 1794-IT8 Hardware First Notch Filter Woodward...

  • Page 86: Figure 6-35. 1794-It8 Write Word 1 And 2

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-35. 1794-IT8 Write Word 1 and 2 (Note: Write Words 2 & 3 should be labeled 1 & 2) In this example, the first read block is set up to monitor the all of the under and overrange bits on the module.

  • Page 87: Figure 6-36. Example Of 1794-It8 Read And Write Gap Blocks

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-36. Example of 1794-IT8 Read and Write GAP Blocks To read the analog input words for the 1794-IT8 module, individual FB_AI blocks were used. Again, the addressing for the analog input blocks need to be in bytes.

  • Page 88: Figure 6-37. 1794-It8 Input Scaling

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-37. 1794-IT8 Input Scaling Again, from the 1794-IT8 manual, the range of the cold junction (reference junction) sensor is 0-70 °C. This converts to 32 to 158 °F. It has been found that the AI_RL_1 and AI_RH_1 must be scaled to one hundred times the AI_BL_1 and AI_BH_1 values.

  • Page 89: Figure 6-38. Example Of 1794-It8 Gap Analog Read Blocks

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Spreadsheet Address Output to GAP Application (Bytes) Reference Junction Minimum Temp Maximum Temp Scale Low Scale High Figure 6-38. Example of 1794-IT8 GAP Analog Read Blocks Allen-Bradley RTD Input (1794-IR8) Module See Figure 6-39 for example of 1794-IR8 module wiring.

  • Page 90: Figure 6-39. Example Of 1794-Ir8 Module Wiring

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-IR8 RTD INPUT with TB3TS BASE RTD (+) RTD (-) PBI.A1.A06.G1.N7_RTD_01 Signal Return RTD (+) PBI.A1.A06.G1.N7_RTD_02 RTD (-) Signal Return RTD (+) PBI.A1.A06.G1.N7_RTD_03 RTD (-) Signal Return RTD (+) PBI.A1.A06.G1.N7_RTD_04...

  • Page 91: Figure 6-40. 1794-Ir8 Module Input Memory Map

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-40. 1794-IR8 Module Input Memory Map Underrange bits—These bits are set if the input signal is below the input channel's minimum range. Overrange bits—These bits are set if 1), the input signal is above the input channel's maximum range, or 2), an open detector is detected.

  • Page 92: Figure 6-42. 1794-Ir8 Write Word 0

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-42. 1794-IR8 Write Word 0 Figure 6-43. 1794-IT8 Hardware First Notch Filter Woodward...

  • Page 93: Figure 6-44. 1794-It8 Write Word 1 And 2

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-44. 1794-IT8 Write Word 1 and 2 In this example, the first read block is set up to monitor the all of the under and overrange bits on the module. The second read block monitors the Powerup bit, Critical Error bits, Calibration Range bit, Calibration Done bit, and Calibration Bad bit.

  • Page 94: Figure 6-45. Example Of 1794-Ir8 Read And Write Gap Blocks

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-45. Example of 1794-IR8 Read and Write GAP Blocks To read the analog input words for the 1794-IR8 module, individual FB_AI blocks were used. Again, the addressing for the analog input blocks needs to be in bytes.

  • Page 95: Figure 6-47. Example Of 1794-Ir8 Gap Analog Read Blocks

    The 3170-MBS is a Network Interface Adapter that communicates between the FLEX I/O module backplane and AtlasPC/Master across a serial RS-485 connection. The 3170-MBS module is a slave device to the AtlasPC control, and is a master controller of the FLEX I/O modules. The I/O data exchange occurs as follows: Output data is sent from the AtlasPC control across the RS-485 connection to the 3170-MBS adapter.

  • Page 96: Figure 6-48. Allen-Bradley Flex I/O Configuration

    In order to simplify the nomenclature used in creating the GAP application, certain naming conventions were changed with respect to the manufacturer’s naming convention. In this example, Woodward refers to the node address as the Group address. The 3170-MBS Group address (Node address), is set by a dip switch located on the 3170-MBS module.
  • Page 97 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Vertical Read Addresses IB16 OV16 IE8/B OE4/B Empty Slot 41001 41016 41031 41046 41061 41076 41091 41106 41002 41017 41032 41047 41062 41077 41092 41107 41003 41018 41033 41048 41063 41078...

  • Page 98: Figure 6-49. Modbus_M Block Example

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Use the following documents from the manufacturer to obtain the Memory Maps and related information. Module Document P/N Discrete Input (Sink) 1794-5.4 Discrete Output (Sink) 1794-5.29 Discrete Output (Relay) 1794-5.19 Analog Input (Current) 1794-5.6...
  • Page 99 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) The E_ERR_1_x output field on the MODBUS_M block is used to display Exception Error on PORT_1 per RPTx. It latches TRUE when an exception error is detected. E_NUM_1_X (hidden) displays the error number. See Table 12.7.1.3-3 for exception errors.

  • Page 100: Figure 6-50. Modbus_M Block Rpt Window Example

    It was found that the Allen-Bradley adapter couldn’t accept more than 45 write requests per group. If more than 45 analog write addresses are listed, the 3170-MBS will not communicate with the AtlasPC control. From the Address Spreadsheet, it can be seen that the Allen-Bradley modules require all read and write addresses be in the 40000 block of addresses.

  • Page 101: Figure 6-51. Modbus_M Block Group 1 Analog Read Rpt Example

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Within the MODBUS_M RPT window, there are four repeats for each group (RPTbw1, RPTbr1, RPTar1, and RPTaw1). Each one of these RPT fields opens another window which displays the addresses assigned for that particular group.

  • Page 102: Figure 6-52. Modbus_M Block Group 2 Analog Read Rpt Example

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-52 shows all of the used read addresses for Group 2 (41001-41120, Analog Read) Figure 6-52. MODBUS_M Block Group 2 Analog Read RPT Example Figure 6-53 shows the used write addresses for Group 2 (41201-41245, Analog Write).

  • Page 103: Figure 6-54. Modbus_M Block Group 3 Analog Write Rpt Example

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-54 shows all of the used write addresses for Group 3 (41246-41290, Analog Write) Figure 6-54. MODBUS_M Block Group 3 Analog Write RPT Example Figure 6-55 shows all of the used write addresses for Group 4 (41291-41294, Analog Write).
  • Page 104 AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 ProSoft Modbus Interface (3170-MBS) Module In addition to the individual I/O module read and write addresses, there are several status read addresses provided by the 3170-MBS Interface module. These status words can be used to monitor the condition of the I/O modules via the GAP application.

  • Page 105: Figure 6-56. 3170-Mbs Status Information Addresses

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-56. 3170-MBS Status Information Addresses Addresses 40121 to 40129 are all status words that represent 16 individual Boolean output conditions. For the GAP application to read the individual bits associated with the 16 bit words in the status addresses above, an A_TO_16B GAP Block is used.

  • Page 106: Figure 6-58. Example Of 3170-Mbs Memory Map Analog Read Gap Blocks

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The remaining Adapter status words (40154 – 40163 and 40171 – 40173) are all 16 bit words and can be handled by the GAP application as an analog values. An A_NAME block is used to connect the specific status function with the addresses entered in the MODBUS_M block.

  • Page 107: Figure 6-59. Example Of 1794-Ib16 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-IB16 To 24VDC Com To +24VDC DISCRETE INPUT (-COM) (+24VDC) DI (+) MBI.A1.A02.G1.N1_BI_01 (-COM) (+24VDC) DI (+) MBI.A1.A02.G1.N1_BI_02 (-COM) (+24VDC) DI (+) MBI.A1.A02.G1.N1_BI_03 (-COM) (+24VDC) DI (+) MBI.A1.A02.G1.N1_BI_04...

  • Page 108: Figure 6-61. 1794-Ib16 Input Filter Time Bit Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 In this example, this module was set up with filter times of 256us for all inputs, Counter Reset set to off, and Counter set to standard input filtered data. See Figure 6-61 for input filter time bit map.

  • Page 109: Figure 6-63. Example Of 1794-Ov16 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Allen-Bradley 24 Vdc Sink Output (1794-OV16) Module In this example, the 1794-OV16 is connected to a Woodward 16 channel relay module. See Figure 6-63 for example of 1794-OV16 module wiring. +28VDC...

  • Page 110: Figure 6-64. 1794-Ov16 Module Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The memory map indicates that there are zero read addresses and one write address. See Figure 6-64 for memory map of 1794-OV16 module. Figure 6-64. 1794-OV16 Module Memory Map To write the discrete output bits for the 1794-OV16 module, a B16_TO_A block is used.

  • Page 111: Figure 6-66. Example Of 1794-Ow8 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Allen-Bradley Relay Output (1794-OW8) Module In this example, the relay outputs are individually fused to protect the module. See Figure 6-66 for example of 1794-OW8 module wiring. DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-OW8...

  • Page 112: Figure 6-67. 1794-Ow8 Module Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The memory map indicates that there is one read address and one write address. See Figure 6-67 for memory map of 1794-OW8 module. Figure 6-67. 1794-OW8 Module Memory Map To write the discrete output bits for the 1794-OW8 module, again a B16_TO_A block is used.

  • Page 113: Figure 6-69. Example Of 1794-Ie8/B Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Allen-Bradley Analog Input (1794-IE8/B) Module In this example, loop powered transducers are shown. See Figure 6-69 for example of 1794-IE8/B module wiring. DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-IE8/B To 24COM ANALOG INPUT...

  • Page 114: Figure 6-70. 1794-Ie8/B Input Module Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The memory map indicates that there are nine read addresses and one write address. See Figure 6-70 for the input memory map and Figure 6-71 for the output memory map for the 1794-IE8/B module.

  • Page 115: Figure 6-72. Example Of 1794-Ie8/B Read And Write Gap Blocks

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) In this example, the write block is set up with Range Select bits for all channels set to 0-21mA. The read block is set up to be able to read the status of the underrange bits for all channels and the Power Up bit (PU).

  • Page 116: Figure 6-73. 1794-Ie8/B And 1794-Oe4/B Analog Data Format Table

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-73. 1794-IE8/B and 1794-OE4/B Analog Data Format Table From MODBUS_M (Address 41046) From MODBUS_M (Address 41053) Figure 6-74. Example of 1794-IE8/B GAP CALCULATE Scaling Blocks Woodward...

  • Page 117: Figure 6-75. Example Of 1794-Oe4/B Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Allen-Bradley Analog Output (1794-OE4/B) Module See Figure 6-75 for example of 1794-OE4/B module wiring. DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-OE4/B ANALOG OUTPUT 4-20mA AO (+) Load MBI.A1.A02.G1.N5_AO_01 AO (-) VO (+)

  • Page 118: Figure 6-76. 1794-Oe4/B Module Input Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The memory map indicates that there is one read address and 13 write addresses. Output memory map addresses 6-9 are not used and 10-13 are used to specify safe state values that are not used in this example. Therefore, the output memory map words 0-5 correspond to the first six write words specified in the address spreadsheet.

  • Page 119: Figure 6-78. 1794-Oe4/B Write Range Selection Bits

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-78. 1794-OE4/B Write Range Selection Bits In this example, the read block is set up to monitor the four broken wire bits and the power up bit on the module. The write blocks are set up to configure the module for multiplex control and 0-20mA range.

  • Page 120: Figure 6-80. Example Of 1794-Oe4/B Gap Analog Write Blocks

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 To write the analog output words for the 1794-OE4/B module, CALCULATE blocks were again used. For the 1794-OE4/B module to output the correct current, the GAP block must convert the engineering units requested to raw counts used by the module.

  • Page 121: Figure 6-81. Example Of 1794-It8 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Allen-Bradley Thermocouple Input (1794-IT8) Module In this example, the first six channels are used for thermocouples and the last two channels are used for monitoring the reference junction temperatures. See Figure 6-81 for example of 1794-IT8 module wiring.

  • Page 122: Figure 6-82. 1794-It8 Module Input Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 The memory map indicates that there are eleven read addresses and 3 write address. See Figure 6-82 for the input memory map and Figures 6-83 through 6-86 for the output memory map for the 1794-IT8 module.

  • Page 123: Figure 6-84. 1794-It8 Write Word 0

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-84. 1794-IT8 Write Word 0 Figure 6-85. 1794-IT8 Hardware First Notch Filter Woodward...

  • Page 124: Figure 6-86. 1794-It8 Write Word 1 And 2

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-86. 1794-IT8 Write Word 1 and 2 (Note: Write Words 2 & 3 should be labeled 1 & 2) In this example, the first read block is set up to monitor the underrange and overrange bits on the module.

  • Page 125: Figure 6-87. Example Of 1794-It8 Read And Write Gap Blocks

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) To MODBUS_M (Address 41276) To MODBUS_M (Address 41277) To MODBUS_M (Address 41278) From MODBUS_M From MODBUS_M (Address 41085) (Address 41086) Data Words to be Data words read from written to Module Module Figure 6-87.

  • Page 126: Figure 6-88. 1794-It8 Input Scaling

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-88. 1794-IT8 Input Scaling A divide by 10 block is used to scale the thermocouple outputs. Again, from the 1794-IT8 manual, the range of the cold junction (reference junction) sensor is 0- 70 °C.

  • Page 127: Figure 6-89. Example Of 1794-It8 Gap Analog Read Blocks

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Analog Temperature From MODBUS_M (To GAP Application) (Address 41077) Reference Junction Temperatures Figure 6-89. Example of 1794-IT8 GAP Analog Read Blocks Woodward...

  • Page 128: Figure 6-90. Example Of 1794-Ir8 Module Wiring

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Allen-Bradley RTD Input (1794-IR8) Module See Figure 6-90 for example of 1794-IR8 module wiring. DISTRIBUTED I/O Allen-Bradley FLEX I/O 1794-IR8 RTD INPUT with TB3TS BASE RTD (+) RTD (-) MBI.A1.A02.G1.N7_RTD_01 Signal Return RTD (+) MBI.A1.A02.G1.N7_RTD_02...

  • Page 129: Figure 6-91. 1794-Ir8 Module Input Memory Map

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) The memory map indicates that there are eleven read addresses and 3 write address. See Figure 6-91 for the input memory map and Figures 6-92 through 6-95 for the output memory map for the 1794-IR8 module.

  • Page 130: Figure 6-93. 1794-Ir8 Write Word 0

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-93. 1794-IR8 Write Word 0 Figure 6-94. 1794-IT8 Hardware First Notch Filter Woodward...

  • Page 131: Figure 6-95. 1794-It8 Write Word 1 And 2

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-95. 1794-IT8 Write Word 1 and 2 In this example, the first read block is set up to monitor the underrange and overrange bits on the module. The second read block monitors the Powerup bit, Critical Error bits, Calibration Range bit, Calibration Done bit, and Calibration Bad bit.

  • Page 132: Figure 6-96. Example Of 1794-Ir8 Read And Write Gap Blocks

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 To MODBUS_M (Address 41291) To MODBUS_M (Address 41292) To MODBUS_M (Address 41293) From MODBUS_M (Address 41101) From MODBUS_M (Address 41100) Data Words to be Data word read from written to Module Module Figure 6-96.

  • Page 133: Automation Direct Terminator I/O Example

    RS-232 connection. The T1K-MODBUS module is a slave device to the AtlasPC control, and is a master controller of the Terminator I/O modules. The I/O data exchange occurs as follows. Output data is sent from the AtlasPC control across the RS-232 connection to the T1K-MODBUS adapter. The network interface adapter then automatically transfers the data across the Terminator I/O backplane to the output modules.

  • Page 134: Figure 6-99. Automation Direct Terminator I/O Configuration

    In order to simplify the nomenclature used in creating the GAP application, certain naming conventions were changed with respect to the manufacturer’s naming convention. In this example, Woodward refers to the node address as the Group address. The T1K-MODBUS Group address, (Node address), is set by two rotary switches located on the front of the T1K-MODBUS module.
  • Page 135 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Module Byte # Read Address Bits Write Address Bits T1K-MODBUS None None T1K-08ND3 10000-10008 None T1K-16ND3 10009-10016 None 10017-10024 None T1K-16TD1 None 00000-00008 None 00009-00016 T1K-08TRS None 00017-00024 Module Word # Read Addr.

  • Page 136: Figure 6-100. Modbus_M Block Example

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Nomenclature When creating a new GAP application, it is important to establish a well organized block naming convention up front. Once done, it is easier to find specific functions and I/O within a large GAP application. Though not shown in this example, the Category and Block Names could follow similar nomenclature rules to those shown in Chapter 1 (Profibus).
  • Page 137 Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) CODE NAME MEANING The following are generated by the slave. NO ERROR Error free ILLEGAL Message function received is not an allowable action for FUNCTION addressed slave. (Unsupported or illegal function code).

  • Page 138: Figure 6-101. T1K-Modbus Adapter Addressing Table

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-101. T1K-MODBUS Adapter Addressing Table In the RPT window for the MODBUS_M block, the BR_F_CODE and AR_F_CODE fields specify the Boolean and Analog read Function Codes for Modbus. The Boolean Read Function Code input defines the Boolean read and...

  • Page 139: Figure 6-102. Modbus_M Block Rpt Example

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-102. MODBUS_M Block RPT Example Within the MODBUS_M RPT window, there are four repeats (RPTbw1, RPTbr1, RPTar1, and RPTaw1). Each one of these RPT fields opens another window which displays the addresses assigned for that particular RPT. See specific module sections below for memory map function assignment.

  • Page 140: Figure 6-103. Modbus_M Block Boolean Write Rpt Example

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-103. MODBUS_M Block Boolean Write RPT Example Figure 6-104 shows all of the used read input addresses for Discrete Input modules (T1K-08ND3 and T1K-16ND3), addresses 10001 to 10024. Figure 6-104. MODBUS_M Block Boolean Read RPT Example Figure 6-105 shows all of the used read input addresses for analog Input modules (T1F-16AD-1 and T1F-14THM), addresses 30001 to 30060.

  • Page 141: Figure 6-105. Modbus_M Block Analog Read Rpt Example

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) The Automation Direct analog modules use two address words per channel. The first word is used, and the second is not used. The unused address must be accounted for when addressing the modules and therefore requires each channel to increment by two addresses.

  • Page 142: Figure 6-106. Modbus_M Block Analog Write Rpt Example

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-106. MODBUS_M Block Analog Write RPT Example Automation Direct Modbus Interface (T1K-MODBUS) Module Woodward...

  • Page 143: Figure 6-107. T1K-Modbus Dip Switch Settings

    The T1K-MODBUS adapter will support RS-232, RS-422, and RS-485 connections. In this example, the connection between the AtlasPC control communications port (Comm 02) and the T1K-MODBUS adapter was wired as a RS-232 connection. See Figure 6-108 for example of RS-232 connection.

  • Page 144: Figure 6-109. T1K-08Nd3 Sink/External Power Configuration

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Automation Direct Discrete Input (Sink) (T1K-08ND3) Module The T1K-08ND3 can be configured for sink or source detection with internal or external power. In this example, the unit is configured for sink mode with external power.

  • Page 145: Figure 6-110 Example Of T1K-08Nd3 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) DISTRIBUTED I/O Automation Direct T1K-08ND3 DISCRETE INPUT Input 0 Input Com0-0 MBI.A1.A02.G1.N1_BI_01 Common V0-0 Internal Supply Voltage Input 1 Input Com0-1 MBI.A1.A02.G1.N1_BI_02 Common V0-1 Internal Supply Voltage Input 2 Input Com0-2 MBI.A1.A02.G1.N1_BI_03...

  • Page 146: Figure 6-113. T1K-16Nd3 Sink/External Power Configuration

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Automation Direct Discrete Input (Sink) (T1K-16ND3) Module The T1K-16ND3 can be configured for sink or source detection with internal or external power. In this example, the unit is configured for sink mode with external power.

  • Page 147: Figure 6-114 Example Of T1K-16Nd3 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) DISTRIBUTED I/O Automation Direct T1K-16ND3 DISCRETE INPUT Input 0 Input Com0-0 MBI.A1.A02.G1.N2_BI_01 Common V0-0 Internal Supply Voltage Input 1 Input Com0-1 MBI.A1.A02.G1.N2_BI_02 Common V0-1 Internal Supply Voltage Input 2 Input Com0-2 MBI.A1.A02.G1.N2_BI_03...

  • Page 148: Figure 6-116. Example Of T1K-16Nd3 Read Gap Blocks

    (Address 10024) Figure 6-116. Example of T1K-16ND3 Read GAP Blocks Automation Direct Discrete Output (Sink) (T1K-16TD1) Module In this example the T1K-16ND3 was connected to a Woodward 16 channel relay module. See Figure 6-117 for example of T1K-16ND3 module wiring. Woodward...

  • Page 149: Figure 6-117. Example Of T1K-16Nd3 Module To Relay Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) +28VDC TB19 + DISTRIBUTED I/O 28COM TB19 - Woodward Automation Direct T1K-16TD1 +28VDC J1-23 16 Channel Relay +28VDC J1-24 DISCRETE OUTPUT Module 28COM J1-21 Output 0 28COM J1-22 Output P/N 5441-691...

  • Page 150: Figure 6-119. Example Of T1K-16Td1 Gap Write Blocks

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 To MODBUS_M (Address 00001) To MODBUS_M From GAP Application (Address 00016) Figure 6-119. Example of T1K-16TD1 GAP Write Blocks Automation Direct Relay Output (T1K-08TRS) Module See Figure 6-120 for example of T1K-08TRS module wiring.

  • Page 151: Figure 6-120. Example Of T1K-08Trs Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) DISTRIBUTED I/O Automation Direct T1K-8TRS RELAY OUTPUT Valve Output 0 Co l MBI.A1.A02.G1.N4_BO_01 Valve Output 1 Co l MBI.A1.A02.G1.N4_BO_02 Valve Output 2 Co l MBI.A1.A02.G1.N4_BO_03 Valve Output 3 Co l MBI.A1.A02.G1.N4_BO_04...

  • Page 152: Figure 6-122. Example Of T1K-08Trs Gap Write Blocks

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-122. Example of T1K-08TRS GAP Write Blocks Automation Direct Analog Input (T1F-16AD-1) Module In this example, the T1F-16AD-1 is wired with loop powered transducers. See Figure 6-123 for example of T1F-16AD-1 module wiring.

  • Page 153: Figure 6-123. Example Of T1F-16Ad-1 Module Wiring

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) DISTRIBUTED I/O Automation Direct T1F-16AD-1 ANALOG INPUT -20mA Input 0 Input Source Com0-0 MBI.A1.A02.G1.N5_AI_01 Common V0-0 External Supply Voltage -20mA Input 1 Input Source Com0-1 Common MBI.A1.A02.G1.N5_AI_02 V0-1 External Supply Voltage...

  • Page 154: Figure 6-124. T1F-16Ad-1 Analog Input Module Memory Map

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-124. T1F-16AD-1 Analog Input Module Memory Map To scale the analog input for the T1F-16AD-1 module, CURVE_2D blocks were used. For the GAP block to convert the raw counts read from the T1F-16AD-1 module to engineering units, the relationship between raw counts and engineering units is specified in the CURVE_2D block.

  • Page 155: Figure 6-125. T1F-16Ad-1 Current Input Module Resolution

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) Figure 6-125. T1F-16AD-1 Current Input Module Resolution Since each channel has two read words, each block address is incremented by two, starting at 30001 and going to 30031. From MODBUS_M (Address 30001)

  • Page 156: Figure 6-127. Example Of T1F-16Da-1 Module Wiring

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Automation Direct Analog Output (T1F-16DA-1) Module See Figure 6-127 for example of T1F-16DA-1 module wiring. DISTRIBUTED I/O Automation Direct T1F-16DA-1 ANALOG OUTPUT Output 0 -20mA Output Load Com0-0 MBI.A1.A02.G1.N6_AO_01 Common V0-0...

  • Page 157: Figure 6-128. T1F-16Da-1 Module Memory Map

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) The memory map indicates that there are no read addresses and 64 byte (32 words) write addresses. Each Analog channel uses 4 bytes. The first and second bytes of a channel contain the analog data. The third and fourth bytes are not used at this time.

  • Page 158: Figure 6-129. T1F-16Da-1 Control Byte Table

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-129. T1F-16DA-1 Control Byte Table To MODBUS_M (Address 40002) Data Word to be written to Module Figure 6-130. Example of T1F-16DA-1 Control Byte GAP Block Woodward...

  • Page 159: Figure 6-131. T1F-16Da-1 Current Output Module Resolution

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) To scale the analog output words for the T1F-16DA-1 module, CURVE_2D blocks were used. The GAP block converts the input, in milliamps, to raw counts used by the T1F-16AD-1 module. The milliamp to raw count relationship can be found in the Automation Direct manual T1K-INST-M.

  • Page 160: Figure 6-133. Example Of T1F-14Thm Module Wiring

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Automation Direct Thermocouple Input (T1F-14THM) Module In this example, Type K thermocouples are used. See Figure 6-133 for example of T1F-14THM module wiring. DISTRIBUTED I/O Automation Direct T1F-14THM THERMOCOUPLE INPUT Chromel...

  • Page 161: Figure 6-134. T1F-14Thm Thermocouple Module Memory Map

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) According to Automation Direct, the T1F-14THM module uses the same memory map as the T1F-16AD-1 module. Based on this memory map, there are 64 byte (32 words) addresses and no write byte addresses. See Figure 6-134 for memory map of Automation Direct T1F-14THM Thermocouple module.

  • Page 162: Figure 6-135 For T1F-14Thm Jumper Configuration Tables

    AtlasPC Digital Control, Vol. II (Distributed I/O) Manual 85586V2 Figure 6-135 for T1F-14THM Jumper configuration Tables Figure 6-136 for T1F-14THM Jumper Locations It has been found that the thermocouple value must be scaled to one tenth the value output by the T1K-MODBUS interface module. A divide by 10 block is used to scale the thermocouple inputs.

  • Page 163: Figure 6-137. Example Of T1F-14Thm Gap Divide Blocks

    Manual 85586V2 AtlasPC Digital Control, Vol. II (Distributed I/O) From MODBUS_M (Address 30033) From MODBUS_M (Address 30057) To GAP Application (Deg F) Figure 6-137. Example of T1F-14THM GAP DIVIDE Blocks Woodward...
  • Page 164 Email and Website—www.woodward.com Woodward has company-owned plants, subsidiaries, and branches, as well as authorized distributors and other authorized service and sales facilities throughout the world. Complete address / phone / fax / email information for all locations is available on our website.

Table of Contents