1. Manuals
  2. Brands
  3. ICC Manuals
  4. Gateway
  5. XLTR-1000
  6. Instruction manual

ICC XLTR-1000 Instruction Manual

Multiprotocol rs-485 gateway
Hide thumbs Also See for XLTR-1000:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Instruction Manual
ICC
Instruction Manual
INDUSTRIAL CONTROL COMMUNICATIONS, INC.
XLTR-1000
Multiprotocol RS-485 Gateway
March 1, 2010
ICC #10756
© 2010 Industrial Control Communications, Inc.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the XLTR-1000 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for ICC XLTR-1000

Summary of Contents for ICC XLTR-1000

  • Page 1 Instruction Manual INDUSTRIAL CONTROL COMMUNICATIONS, INC. XLTR-1000 Multiprotocol RS-485 Gateway March 1, 2010 ICC #10756 © 2010 Industrial Control Communications, Inc.
  • Page 2 XLTR-1000 User's Manual Part Number 10756 Printed in U.S.A. ©2010 Industrial Control Communications, Inc. All rights reserved OTICE SERS Industrial Control Communications, Inc. reserves the right to make changes and improvements to its products without providing notice. Industrial Control Communications, Inc. shall not be liable for technical or editorial...
  • Page 3 PPLICABLE IRMWARE Modbus – BACnet Firmware Version 2.100 Modbus – Metasys Firmware Version 2.100 Modbus – Toshiba Firmware Version 2.100 Modbus – Sullair Firmware Version 2.100 BACnet – Metasys Firmware Version 2.100 BACnet – Toshiba Firmware Version 2.100 BACnet – Sullair Firmware Version 2.100 Metasys –...
  • Page 4 Usage Precautions Operating Environment • Please use the interface only when the ambient temperature of the environment into which the unit is installed is within the following specified temperature limits: -10 ∼ +50°C (+14 ∼ +122°F) Operation: -40 ∼ +85°C (-40 ∼ +185°F) Storage: •...

  • Page 5: Table Of Contents

    TABLE OF CONTENTS Introduction .................. 6 Features ..................7 Gateway Concepts ............... 8 Precautions and Specifications..........10 Installation Precautions ...............10 Maintenance Precautions ..............11 Inspection ....................11 Maintenance and Inspection Procedure ..........11 Storage....................12 Warranty....................12 Disposal ....................12 Environmental Specifications ..............12 Gateway Overview ..............13 Power Supply Electrical Interface ............14 RS-485 Port Electrical Interface ............14 Installation ..................
  • Page 6 Protocol Configuration .................27 8.6.1 Modbus RTU Master ...............27 8.6.2 Modbus RTU Slave.................33 8.6.3 Modbus RTU Sniffer ...............39 8.6.4 BACnet MS/TP Client ..............43 8.6.5 BACnet MS/TP Server ..............50 8.6.6 Metasys N2 Slave ................57 8.6.7 Toshiba ASD Master ...............63 8.6.8 Sullair Supervisor Master ..............68 Protocol-Specific Information...........

  • Page 7: Introduction

    1. Introduction Congratulations on your purchase of the ICC XLTR-1000 Multiprotocol RS-485 Communications Gateway. This gateway allows information to be transferred seamlessly between various RS-485-based networks. In addition to the supported fieldbus protocols, the gateway hosts a USB interface for configuring the gateway via a PC.

  • Page 8: Features

    The gateway can be connected to a PC via a USB mini type-B cable. This simultaneously supplies power while providing the ability to configure the gateway, monitor data, and update firmware on the device using the ICC Gateway Configuration Utility. Refer to section 8.1 for more information.

  • Page 9: Gateway Concepts

    3. Gateway Concepts The XLTR-1000 is a member of the Millennium Series communication gateways. Members of this family are designed to provide a uniform interface, configuration and application experience. This commonality reduces the user’s learning curve, reducing commissioning time while simplifying support. All Millennium Series gateways are configured using the ICC Gateway Configuration Utility.
  • Page 10 The Millennium Series gateways also provide a powerful data-monitoring feature that allows the user to view and edit the database in real time, as well as view the status of service objects via the ICC Gateway Configuration Utility’s Monitor tab when connected via USB to a PC.

  • Page 11: Precautions And Specifications

    4. Precautions and Specifications Rotating shafts and electrical equipment can be hazardous. Installation, operation, and maintenance of the gateway shall be performed by Qualified Personnel only. Qualified Personnel shall be: • Familiar with the construction and function of the gateway, the equipment being driven, and the hazards involved.

  • Page 12: Maintenance Precautions

    4.2 Maintenance Precautions • Do Not attempt to disassemble, modify, or repair the gateway. Contact your ICC sales representative for repair or service information. • If the gateway should emit smoke or an unusual odor or sound, turn the power off immediately.

  • Page 13: Storage

    4.6 Warranty This gateway is covered under warranty by ICC, Inc. for a period of 12 months from the date of installation, but not to exceed 18 months from the date of shipment from the factory. For further warranty or service information, please contact Industrial Control Communications, Inc.

  • Page 14: Gateway Overview

    5. Gateway Overview USB connector “RS-485 A” terminal block “RS-485 A” TX and RX LEDs “RS-485 B” TX and RX LEDs Gateway status LED Gateway Overview (Front) Power terminals “RS-485 B” terminals Shield terminal Gateway Overview (Back)

  • Page 15: Power Supply Electrical Interface

    Voltage rating ......7 - 24VDC Minimum Current rating ..50mA (@24VDC) • Typical current consumption of the XLTR-1000 when powered from a 24V supply is approximately 15mA. • ICC offers an optional 120VAC/12VDC power supply (ICC part number 10755) that can be used to power the gateway from a standard wall outlet.
  • Page 16 Figure 2: RS-485 Interface Circuitry Schematic Figure 3 highlights the terminals on the gateway’s “RS-485 B” terminal block that are specific to RS-485 network connections. Equivalent terminals exist on the “RS-485 A” terminal block for connection to that separate subnet. Figure 3: “RS-485 B”...

  • Page 17: Installation

    6. Installation The gateway’s installation procedure will vary slightly depending on the mounting method used. Before mounting the gateway, install the 4 black rubber feet (Figure 4) onto the bottom of the enclosure. Figure 4: Rubber Feet 6.1 Mounting the Gateway The gateway may be mounted on a panel, a wall or a DIN rail.

  • Page 18: Din Rail Mounting

    6.1.2 DIN Rail Mounting The DIN rail adapter (Figure 6) can clip onto 35mm and G-type rails. To mount the gateway to a DIN rail, clip the DIN rail adapter onto the DIN rail and mount the gateway on the screws (the screws should already be seated into the adapter at the proper height).

  • Page 19: Wiring Connections

    6.2 Wiring Connections Note that in order to power the unit, a power supply must also be installed. Refer to section 5.1 for more information. Mount the unit via the desired method (refer to section 6.1). Connect the various networks to their respective plugs/terminal blocks. Ensure that any wires are fully seated into their respective terminal blocks, and route the network cables such that they are located well away from any electrical noise sources, such as adjustable-speed drive input power or...

  • Page 20: Led Indicators

    7. LED Indicators The gateway contains several different LED indicators, each of which conveys important information about the status of the unit and connected networks. These LEDs and their functions are summarized here. 7.1 Gateway Status The gateway has one dichromatic LED to indicate the status of the device. On startup, the LED blinks a startup sequence: Green, Red, Green, Red.

  • Page 21: Configuration Concepts

    PC. The gateway is configured by the ICC Gateway Configuration Utility PC application. For information on how to install the utility, refer to the ICC Gateway Configuration Utility User’s Manual. The following will briefly describe how to configure the gateway using the configuration utility.

  • Page 22: Timeout Configuration Tab

    Status list. Section 8.4.2 describes how to view the status of a service object. For more information, refer to the ICC Gateway Configuration Utility User’s Manual. 8.2 Timeout Configuration Tab The gateway can be configured to perform a specific set of actions when network communications are lost.

  • Page 23: Timeout Time

    Note that this feature is only used with slave/server protocols. This is not the same as the timeout value used for master/client protocols. For more information, refer to section 8.3. There are two separate elements that comprise the timeout configuration: •...

  • Page 24: Port Configuration Tabs Protocol Selection Group

    Length This field is the number of data elements for this timeout object. The total number of bytes modified by this timeout object is determined by the length multiplied by the number of bytes in the data type selected (1, 2 or 4). 8.3 Port Configuration Tabs Protocol Selection Group This section describes each available field in the Protocol Selection group of the port configuration tabs.

  • Page 25: Service Object Configuration

    For slave/server protocols, the response delay is the number of milliseconds the device will wait before responding to a request. This is a useful feature for certain master devices or infrastructure components (such as radio modems) that may require a given amount of time to place themselves into a “receiving mode” where they are capable of listening for slave responses.

  • Page 26: Viewing The Status Of A Service Object

    Database Address This is the starting address in the gateway’s database that is used to mirror the data on the network. The number of bytes allocated for the service object data is determined by the data type and the number of objects in the service object. Data Type This field specifies how many bytes are used to store each object in the service object.

  • Page 27: General Object Editing Options

    automatically added into the Status list in the Monitor tab (status addresses can also be added manually in the Monitor tab by typing the address and clicking Add Status Address). This window will show the value of each of the counters and a translation of the current status and last error.

  • Page 28: Protocol Configuration

    During configuration, it therefore makes no difference whether port A or port B is assigned to each specific network in use. For more details on how to use the configuration utility, refer to the ICC Gateway Configuration Utility User’s Manual.
  • Page 29 Type This group designates the Modbus data type that this service object will access. Choose from Holding Register, Input Register, Coil Status, or Input Status. Description This field is a description of the service object. It is not used on the gateway, but serves as a reference for the user.
  • Page 30 Note that the multiplier imposes range limitations on network data values. For example, if the multiplier is 0.01, then the network data can achieve a maximum value of only 655 (since 65535 is the maximum value that can be stored in 16 bits in the database).

  • Page 31: Configuration Example

    Big Endian Enable Big Endian if the transmitted values are encoded in big-endian, 16-bit word order, i.e. the most significant 16-bit word is before the least significant 16- bit word. Word-Size Reg Enable Word-Size Reg if each target register is 16-bits wide, but two 16-bit registers comprise one 32-bit value.
  • Page 32 • Connect the gateway to the PC via a USB mini type-B cable. • Open the configuration utility and select the XLTR-1000 (see section 8.1 for more information on selecting a device). • Click on the RS-485 B Configuration tab.
  • Page 33 • Enter “21” into the Start Discrete field. • Enter “2” into the Num Discretes field. • Enter “18” into the Database Addr field. • Click Create. Finishing Up • Configure the RS-485 A port for the other protocol to be used in accessing the drive through the gateway.

  • Page 34: Modbus Rtu Slave

    8.6.2 Modbus RTU Slave Modbus RTU Slave can be configured on either RS-485 port by selecting Modbus RTU Slave from the protocol dropdown menu. By default, the gateway’s entire database is accessible via the register mapping mechanism discussed in section 9.1.2.2. 8.6.2.1 Protocol Selection Group Protocol Select Modbus RTU Slave from this dropdown menu.
  • Page 35 Type This group designates the Modbus register type(s) that this object will remap. Choose Holding Register and/or Input Register to assign which register type(s) to remap. Description This field is a description of the register remap object. It is not used on the gateway, but serves as a reference for the user.
  • Page 36 Big Endian Enable Big Endian if the transmitted values are to be encoded in big-endian, 16- bit word order, i.e. the most significant 16-bit word is before the least significant 16-bit word. Word-Size Register Enable Word-Size Register if each target register is 16-bits wide, but two 16-bit registers are to comprise one 32-bit value.
  • Page 37 • Connect the gateway to the PC via a USB mini type-B cable. • Open the configuration utility and select the XLTR-1000 (see section 8.1 for more information on selecting a device). • Click on the RS-485 A Configuration tab.
  • Page 38 Remap floor 1’s command data registers: • Enter “3003” into the Start Reg field. • Enter “3” into the Num Regs field. • Enter “112” into the Database Addr field. • Click Create. Finishing Up • Configure the RS-485 B port for the other protocol to be used in accessing the floors of the building.
  • Page 39 Where are the monitor and command values? Modbus Register Database Address Floor 1 Monitor Data 1 0 (upper byte) & 1 (lower byte) (Register 1000) Floor 1 Monitor Data 2 2 (upper byte) & 3 (lower byte) (Register 1001) Floor 1 Monitor Data 3 4 (upper byte) &...

  • Page 40: Modbus Rtu Sniffer

    8.6.3 Modbus RTU Sniffer The Modbus RTU Sniffer driver can be configured on either RS-485 port by selecting Modbus RTU Sniffer from the protocol dropdown menu. The Modbus RTU Sniffer driver is passive (listen only), and uses service objects to define what registers to log values for from the network traffic.
  • Page 41 Start Reg This field defines the starting register number for a range of registers associated with this service object. Enter a value between 1 and 65535. Num Regs This field defines the number of registers associated with this service object. Enter a value between 1 and 125.
  • Page 42 Connect the gateway to the PC via a USB mini type-B cable. • Open the configuration utility and select the XLTR-1000 (see section 8.1 for more information on selecting a device). Configure the RS-485 B port using the above requirements •...
  • Page 43 • Enter “14” into the Start Reg field. • Enter “1” into the Num Regs field. • Enter “6” into the Database Addr field. • Click Create. Finishing Up • Download the configuration to the gateway (see section 8.1 for more information on downloading a configuration to a device).

  • Page 44: Bacnet Ms/Tp Client

    8.6.4 BACnet MS/TP Client BACnet MS/TP Client can be configured on either RS-485 port by selecting BACnet MS/TP Client from the protocol dropdown menu. The gateway can read and write the present value property of BACnet objects hosted by other devices on the network.
  • Page 45 Max Master This field is the highest allowable address for MS/TP master nodes on the network. Any address higher than this will not receive the token from the gateway. Enter a value between 0 and 127. Note that this value must be greater than or equal to the configured Address for the gateway.
  • Page 46 Dest Address Note that this field is available only when the Use Static Device Binding checkbox is checked. This field is used to manually define the address of the BACnet device that the gateway should target for this service object. Enter a value between 0 and 127.
  • Page 47 • Connect the gateway to the PC via a USB mini type-B cable. • Open the configuration utility and select the XLTR-1000 (see section 8.1 for more information on selecting a device). • Click on the RS-485 A Configuration tab.
  • Page 48 Configure the RS-485 B port (BACnet client) using the above requirements • Click on the RS-485 B Configuration tab. • Select BACnet MS/TP Client from the protocol dropdown menu. • Enter the Baud Rate settings to match that of the drive. •...
  • Page 49 • Enter the device instance of the drive into the Dest Dev Inst field. • Enter “2” into the Start Inst field. • Enter “1” into the Num Insts field. • Enter “16” into the Database Addr field. • Select 32-bit Unsigned from the Data Type dropdown menu.
  • Page 50 Where are the monitor and command values? Database BACnet Object Modbus Discrete / Register Address 0 & 1 Register 1 – lower 16 bits Output Frequency (Analog Input 1) 2 & 3 Register 2 – upper 16 bits 4 & 5 Register 3 –...

  • Page 51: Bacnet Ms/Tp Server

    8.6.5 BACnet MS/TP Server BACnet MS/TP Server can be configured on either RS-485 port by selecting BACnet MS/TP Server from the protocol dropdown menu. The BACnet MS/TP server can host a wide variety of user-defined BACnet objects. Whenever the BACnet MS/TP server is enabled, the BACnet device object is always present and must be properly configured.
  • Page 52 Configuration tip: The Address and Max Master fields greatly affect network performance. For best results, set all device addresses consecutively, starting with address 0, ending with a device with a configurable Max Master field at the highest address. Then set that device’s Max Master field to its address. This will prevent any unnecessary poll for master packets on the network and thereby maximize efficiency.
  • Page 53 Units Applies to analog objects only. Select the desired units from this dropdown menu. If the desired units are not available in the dropdown menu, select Other Units and enter the enumerated value (as defined by the BACnet Specification) in the Unit Value field. Bitmask Applies to binary objects only.
  • Page 54 • Connect the gateway to the PC via a USB mini type-B cable. • Open the configuration utility and select the XLTR-1000 (see section 8.1 for more information on selecting a device). • Click on the RS-485 A Configuration tab.
  • Page 55 • Create BACnet objects to map the data from the BAS into the gateway’s database. The monitor object data will start at database address 0 and the command object data will start at database address 100. Create objects for floor #1’s monitor data For the first object, enter the following: •...
  • Page 56 Create objects for floor #2’s command data For the first object, enter the following: • Select Analog Value from the Type selection group. • Enter “F2 Cmd Data 1” into the Object Name field. • Enter “2003” into the Instance field. •...
  • Page 57 Where are the monitor and command values? BACnet Object Database Addresses Floor #1 Monitor Data 1 (AV1000) 0 (upper byte)..3(lower byte) Floor #1 Monitor Data 2 (AV1001) 4 (upper byte)..7(lower byte) Floor #1 Monitor Data 3 (AV1002) 8 (upper byte)..11(lower byte) Floor #2 Monitor Data 1 (AV2000) 12 (upper byte)..15(lower byte) Floor #2 Monitor Data 2 (AV2001)

  • Page 58: Metasys N2 Slave

    8.6.6 Metasys N2 Slave Johnson Controls Metasys N2 slave can be configured on either RS-485 port by selecting Metasys N2 Slave from the protocol dropdown menu. The Metasys N2 slave driver can host a wide variety of user-defined N2 objects. This section will discuss how to configure the Metasys N2 driver.
  • Page 59 Database Addr This field is the database address where the Metasys object’s current value will reside. Enter a value between 0 and 4095 (0x0 – 0xFFF). A note for analog objects: Depending on the designated Data Type, the maximum allowable database address is 4095, 4094, or 4092 for 8-bit, 16-bit, or 32-bit sized objects, respectively.
  • Page 60 • Connect the gateway to the PC via a USB mini type-B cable. • Open the configuration utility and select the XLTR-1000 (see section 8.1 for more information on selecting a device). • Click on the RS-485 A Configuration tab.
  • Page 61 Create output objects for floor #1’s command data For the first object, enter the following: • Select Analog Output from the Type selection group. • Enter “F1 Cmd Data 1” into the Object Name field. • Enter “1” into the Instance field. •...
  • Page 62 • Select 32-bit Unsigned from the Data Type dropdown menu. • Enter “1” into the Multiplier field. • Click Create. Repeat these steps for the other two AI objects, increasing the Object Name by 1, Instance by 1, and Database Addr by 4 each time.
  • Page 63 Where are the monitor and command values? Metasys Object Database Addresses Floor #1 Monitor Data 1 (AI1) 0 (upper byte)..3(lower byte) Floor #1 Monitor Data 2 (AI2) 4 (upper byte)..7(lower byte) Floor #1 Monitor Data 3 (AI3) 8 (upper byte)..11(lower byte) Floor #2 Monitor Data 1 (AI4) 12 (upper byte)..15(lower byte) Floor #2 Monitor Data 2 (AI5)

  • Page 64: Toshiba Asd Master

    8.6.7 Toshiba ASD Master Toshiba ASD Master can be configured on either RS-485 port by selecting Toshiba ASD Master from the protocol dropdown menu. The Toshiba ASD Master protocol uses service objects to make requests. For more information on service objects, refer to section 8.4. Each parameter in a service object is mapped to 2 bytes in the database (the data size is fixed at 16-bit, as this is the native data size of Toshiba ASD parameters).
  • Page 65 unchecked, as attempts to read a service object targeting destination address 255 will invariably time out. Start Param This field defines the starting parameter number for a range of drive parameters associated with this service object. Enter a value between 0 and FF99. For example, the drive’s output frequency typically resides at parameter FE00.
  • Page 66 • Connect the gateway to the PC via a USB mini type-B cable. • Open the configuration utility and select the XLTR-1000 (see section 8.1 for more information on selecting a device). • Click on the RS-485 A Configuration tab.
  • Page 67 • The default mapping of the gateway’s database into the Modbus register space will be used in this example, so no register remap objects need to be created. Configure the RS-485 B port (Toshiba ASD) using the above requirements • Click on the RS-485 B Configuration tab.
  • Page 68 • Enter “2” into the Num Params field. • Enter “8” into the Database Addr field. • Ensure that the “write” function code check box is checked, and then select the desired Write Function Code. Because this service object will be used to write to drive command registers (which exist only in RAM), either “P”...

  • Page 69: Sullair Supervisor Master

    8.6.8 Sullair Supervisor Master Sullair Supervisor Master can be configured on either RS-485 port by selecting Sullair Master from the protocol dropdown menu. The Sullair Master protocol uses service objects to make requests. For more information on service objects, refer to section 8.4. Except for display parameters, each parameter in a Sullair supervisor service object is mapped to 2 bytes in the database (the data size is fixed at 16-bit).
  • Page 70 5, 6, and 7 respectively. Configure the gateway using the above requirements • Connect the gateway to the PC via a USB mini type-B cable. • Open the configuration utility and select the XLTR-1000 (see section 8.1 for more information on selecting a device).
  • Page 71 Configure the RS-485 B port using the above requirements • Click on the RS-485 B Configuration tab. • Select Sullair Master from the protocol dropdown menu. • Create Service Objects to read and write the desired parameters. Because the pressure and temperature parameters are located at contiguous indexes (107 –...
  • Page 72 Where are the monitor and command values? Controller Parameter Database Address (Parameter Index) P1 (107) 0 & 1 P2 (108) 2 & 3 P3 (109) 4 & 5 P4 (110) 6 & 7 T1 (111) 8 & 9 T2 (112) 10 &...

  • Page 73: Protocol-Specific Information

    9. Protocol-Specific Information This section will discuss topics that are specific to each of the supported protocols. 9.1 Modbus RTU 9.1.1 Modbus RTU Master 9.1.1.1 Overview The gateway supports the Modbus RTU master protocol on both of its RS-485 ports. Some notes of interest are: •...

  • Page 74: Modbus Rtu Slave

    the changed register or discrete value(s) (if the write function is enabled). For more information on configuring Modbus service objects, refer to section 8.6.1.2. 9.1.1.3 Register and Discrete Mapping Holding and Input Registers Modbus registers are mapped in the database as 2-byte values. This means that each register in a service object takes up two database addresses.
  • Page 75 • Database data can be accessed as either holding registers (4X references) or input registers (3X references). For example, accessing database address 1300 involves accessing holding register 41301 or input register 31301 (i.e. offset 1301). • Specific bits within the database can be accessed as either coils (0X references) or discrete inputs (1X references).
  • Page 76 mapped to database address 46. So reading registers 24 and 25 will return data from addresses 46 and 62 in the database, respectively. 9.1.2.3 Coil & Discrete Input Mappings The Modbus RTU slave driver provides read/write support for coils (0X references) and read-only support for discrete inputs (1X references).

  • Page 77: Modbus Rtu Sniffer

    discrete will access. Because of this, it is possible to indirectly remap discretes using register remap objects. If a register has been remapped to an alternate database address, then the discretes that map to that register will also be remapped to that alternate address. 9.1.3 Modbus RTU Sniffer 9.1.3.1 Overview The gateway supports a Modbus RTU sniffer driver on both of its RS-485 ports.

  • Page 78: Bacnet Ms/Tp

    V2.100 BACnet Protocol Revision: Product Description: The XLTR-1000 is a multiprotocol RS-485 to RS-485 gateway. This product supports native BACnet, connecting directly to the MS/TP LAN using baud rates of 4800, 9600, 19200, 38400, 57600, 76800, and 115200. The device can be configured as a BACnet Client or as a BACnet Server.
  • Page 79 Segmentation Capability: None Segmented requests supported Window Size ________ Segmented responses supported Window Size ________ Standard Object Types Supported: See “Object Types/Property Support Table” for object details. Data Link Layer Options: BACnet IP, (Annex J) BACnet IP, (Annex J), Foreign Device ISO 8802-3, Ethernet (Clause 7) ANSI/ATA 878.1, 2.5 Mb.
  • Page 80 Refer to section 9 for other supported protocols. Datatypes Supported: The following table summarizes the datatypes that are accepted (in the case of a write property service) and returned (in the case of a read property service) when targeting the present value property of each supported object type. Service Object Type Read...
  • Page 81 Object Types/Property Support Table The following table summarizes the Object Types/Properties supported. Object Type Property Binary Binary Binary Analog Analog Analog Device Input Output Value Input Output Value Object Identifier Object Name Object Type System Status Vendor Name Vendor Identifier Model Name Firmware Revision App Software Revision...

  • Page 82: Bacnet Ms/Tp Client

    9.2.2 BACnet MS/TP Client 9.2.2.1 Overview The gateway supports BACnet MS/TP client on both of its RS-485 ports. Some notes of interest are: • The gateway supports reading and writing the present value property of BACnet objects in devices on the network. •...
  • Page 83 device instance is associated with. By default, the gateway will use dynamic device binding if a service object is not configured to use static device binding. Static Device Binding Not all BACnet devices support dynamic device binding. If the gateway needs to request data from an MS/TP slave, or an MS/TP master that doesn’t support dynamic device binding, then static device binding must be used.

  • Page 84: Bacnet Ms/Tp Server

    9.2.3 BACnet MS/TP Server 9.2.3.1 Overview The gateway supports BACnet MS/TP server on both of its RS-485 ports. Some notes of interest are: • Fully configurable BACnet objects. • Supported BACnet objects include: Analog Input Analog Output Analog Value Binary Input Binary Output Binary Value •...
  • Page 85 Reinitialize Device This service is used to reset the device. The gateway does not distinguish between a warm and cold restart. This service is password protected. To successfully reset the gateway, “icc” must be used as the password.

  • Page 86: Metasys N2 Slave

    9.3 Metasys N2 Slave The gateway supports the Johnson Controls Metasys N2 slave driver on both of its RS-485 ports, and supports N2 analog input, analog output, binary input and binary output object types. 9.3.1 Overview Some notes of interest are: •...

  • Page 87: Metasys Objects

    9.3.2 Metasys Objects • Analog input (AI) objects are used for monitoring analog status items. AI objects support low alarm limits, low warning limits, high warning limits, high alarm limits and differential values. Change of state (COS), alarm and warning functions can also be enabled. An AI object will accept an override command, but will not change its actual value or indicate override active.

  • Page 88: Toshiba Asd Master

    9.4 Toshiba ASD Master 9.4.1 Overview The gateway supports the Toshiba ASD Master protocol on both of its RS-485 ports. This protocol allows direct connection to Toshiba adjustable-speed drives with RS-485 ports that support the Toshiba protocol, such as the G7/Q7/H7 and AS1/FS1/G9/H9/Q9 families.

  • Page 89: Toshiba Service Objects

    RS-485 port configurations & options available for the various Toshiba drives, please refer to the relevant Toshiba documentation for your drive. • When using the “W” function code to write drive configuration parameters, be sure to follow Toshiba’s guidelines regarding the number of times a specific parameter can be written without risk of EEPROM damage.

  • Page 90: Sullair Supervisor Master

    9.5 Sullair Supervisor Master • The gateway acts as a Sullair Supervisor Protocol network monitor device (master) via either of its RS-485 ports. It can automatically adapt to the Supervisor network configuration (sequencing or non-sequencing/slave mode). • Any numerically-addressed parameter defined by the Supervisor protocol is directly accessible (machine type = parameter #1, etc.).

  • Page 91: Sullair Service Objects

    Parameter Item Note Source Number Digital Shutdown Digital Inputs Run Time Load Time Display 1 Line of Display Display 2 Line of Display • The baud rate is fixed at 9600 baud. • The gateway Supervisor interface is primarily a system monitor and configuration device.

  • Page 92: Troubleshooting

    LED flashes • Any other number of flashes indicates an error indicates an internal device error. code. Please contact ICC for further assistance. • The USB cable is Unplug and reconnect the USB plugged into both the cable.

  • Page 93: Appendix A: Database Endianness

    11. Appendix A: Database Endianness A key feature of the Millennium Series gateways is the ability to change the byte order storage scheme for data in the database between big endian and little endian. The database endianness is the convention used to store multi-byte data to or retrieve multi-byte data from the database.
  • Page 94 This example shows how the hex value 12345678 is retrieved from the database using a big endian byte order. Since the hex value 12 is at address “a”, the lowest address, it is the most significant byte. Figure 15: Big Endian Retrieval This other example shows how the hex value 12345678 is retrieved...

  • Page 95: Ex: Modbus - Profibus

    The selection of the correct byte ordering is crucial for coherent interaction between these two types of networks on the gateway. The following presents examples of how the database endianness affects end-to-end communication between networks and when each byte-ordering scheme should be used. 11.1 Ex: Modbus - Profibus This example shows the interaction between a network using an object value method (Modbus) and one using a bag of bytes method (Profibus) to exchange...

  • Page 96: Ex: Modbus - Devicenet

    Figure 18: Modbus - Profibus Little Endian 11.2 Ex: Modbus - DeviceNet This example shows the interaction between a network using an object value method (Modbus) and one using a bag of bytes method (DeviceNet) to exchange data. The gateway reads holding registers 1 and 2 from the Modbus network, stores the data into the database, and then sends the 4 bytes of input data onto the DeviceNet network.

  • Page 97: Ex: Bacnet - Devicenet

    In contrast, Figure 18 shows the effects of configuring the database for big- endian byte order. Holding registers 1 and 2 again have values of 0x1234 and 0x5678, respectively. However, when the DeviceNet device receiving the input data from the gateway interprets these values, the resulting pairs of 2-byte values become 0x3412 and 0x7856, thus receiving incorrect values for holding registers 1 and 2.
  • Page 98 Figure 21: BACnet - DeviceNet Little Endian Conversely, Figure 22 illustrates the consequences of configuring the database for big-endian byte order using this scenario. Once again, Analog Value 0 has a value of 0x12345678. But now, when the DeviceNet device interprets the 4 bytes of input data sent by the gateway, the resulting 4-byte value is 0x78563412, thus receiving an incorrect value for Analog Value 0.

  • Page 99: Ex: Bacnet - Modbus (Analog Objects-Registers)

    11.4 Ex: BACnet - Modbus (Analog Objects-Registers) This example exhibits two networks that both use an object value scheme to exchange data. In this scenario, the database endianness is irrelevant if the data types are the same for both networks. This example shows communication between a BACnet network and a Modbus network using two 16-bit analog value BACnet objects and two 16-bit Modbus holding registers.

  • Page 100: Ex: Bacnet - Modbus (Binary Objects-Discretes)

    11.5 Ex: BACnet - Modbus (Binary Objects-Discretes) This example also contains two networks that both employ an object value method for exchanging data, but unlike the previous example, the database endianness affects the end-to-end alignment of the data. In this example, communication is taking place between a BACnet network and a Modbus network using single-bit data elements.
  • Page 101 Figure 26: BACnet - Modbus (Binary Objects & Discretes) Big Endian...

  • Page 102: Appendix B: Status Information

    12. Appendix B: Status Information This section details the information that is enabled by checking the Reflect Status checkbox while configuring a service object. Figure 27 diagrams the structure of this status information. Because this 16-byte structure resides in the database at a user-designated location, it can be accessed from the opposite port in order to continuously determine the performance of the corresponding service object.
  • Page 103 Table 6: Status / Error Codes Status / Error Code Description (Hex) 0x00 No Error 0xF0 Invalid Data Address 0xF1 Data Error 0xF2 Write To Read-Only 0xF3 Read From Write-Only 0xF4 Target Busy 0xF5 Target Error 0xF6 Cannot Execute 0xF7 Mode Error 0xF8 Other Error...
  • Page 104 INDUSTRIAL CONTROL COMMUNICATIONS, INC. 1600 Aspen Commons, Suite 210 Middleton, WI USA 53562-4720 Tel: [608] 831-1255 Fax: [608] 831-2045 http://www.iccdesigns.com Printed in U.S.A...

Table of Contents