Omron 3G8F7-CRM21 User Manual
  1. Manuals
  2. Brands
  3. Omron Manuals
  4. Motherboard
  5. 3G8F7-CRM21
  6. User manual
Omron 3G8F7-CRM21 User Manual

Omron 3G8F7-CRM21 User Manual

Componet master board for pci bus/ compactpci bus
Hide thumbs
Table of Contents

Quick Links

Cat. No. W485-E1-02
3G8F7-CRM21 (for PCI Bus)
3G8F8-CRM21 (for CompactPCI Bus)
CompoNet Master Board
for PCI Bus / CompactPCI Bus
TM
USER'S MANUAL
Table of Contents
loading

Related Manuals for Omron 3G8F7-CRM21

Summary of Contents for Omron 3G8F7-CRM21

  • Page 1 Cat. No. W485-E1-02 3G8F7-CRM21 (for PCI Bus) 3G8F8-CRM21 (for CompactPCI Bus) CompoNet Master Board for PCI Bus / CompactPCI Bus USER’S MANUAL...
  • Page 2 Association, Inc. Other product names and company names in this manual are trademarks or registered trademarks of their respective companies. The copyright of the CompoNet Master Boards for PCI Bus and for CompactPCI Bus, and related software belongs to OMRON Corporation.
  • Page 3 3G8F7-CRM21 (for PCI Bus) 3G8F8-CRM21 (for CompactPCI Bus) CompoNet Master Board for PCI Bus / CompactPCI Bus User’s Manual Revised September 2013...
  • Page 5 OMRON Product References All OMRON products are capitalized in this manual. The word "Unit" is also capitalized when it refers to an OMRON product, regardless of whether or not it appears in the proper name of the product.
  • Page 6 OMRON. No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice.

  • Page 7: Table Of Contents

    TABLE OF CONTENTS PRECAUTIONS........Intended Audience ............General Precautions .
  • Page 8 TABLE OF CONTENTS Access to Detailed Status Group ..........PC Watchdog Timer.
  • Page 9 TABLE OF CONTENTS APPENDIX D Sample Program ........153 D-1 Sample Program.
  • Page 10 TABLE OF CONTENTS...

  • Page 11: About This Manual

    PCI Bus and the 3G8F8-CRM21 CompoNet Master Board for CompactPCI Bus. The CompoNet Master Board functions as the CompoNet Master Unit. There are two types: One is compatible with PCI bus (model # 3G8F7-CRM21), and the other is compatible with CompactPCI bus (model # 3G8F8- CRM21) .
  • Page 12 Related Manuals Cat No. Model Name Description W485 3G8F7-CRM21 Provides the specifications of CompoNet Master Board for the CompoNet Master Board PCI Bus and for CompactPCI (this manual) 3G8F8-CRM21 Bus Operation Manual W457 CRT1 Provides the specifications of CR1-series CompoNet...
  • Page 13 Omron’s exclusive warranty is that the Products will be free from defects in materials and work- manship for a period of twelve months from the date of sale by Omron (or such other period expressed in writing by Omron). Omron disclaims all other warranties, express or implied.
  • Page 14 Disclaimers Performance Data Data presented in Omron Company websites, catalogs and other materials is provided as a guide for the user in determining suitability and does not constitute a warranty. It may represent the result of Omron’s test conditions, and the user must correlate it to actual application requirements. Actual per- formance is subject to the Omron’s Warranty and Limitations of Liability.
  • Page 15 PRECAUTIONS This section provides general precautions for use of the CompoNet Master Boards. The information contained in this section is important for the safe, reliable application of the CompoNet Master Board. You must read this section and understand the information contained before attempting to set up or operate a CompoNet Network using CompoNet Master Boards.

  • Page 16: Intended Audience

    It is extremely important that a PLC and all PLC Units be used for the specified purpose WARNING and under the specified conditions, especially in applications that can directly or indirectly affect human life. You must consult with your OMRON representative before applying a PLC System to the above-mentioned applications.

  • Page 17: Safety Precautions

    Safety Precautions Safety Precautions Do not attempt to take any Unit apart or touch the component inside while the power is WARNING being supplied. Doing so may result in electric shock. Do not touch any of the terminals or terminal blocks while the power is being supplied. WARNING Doing so may result in electric shock.
  • Page 18 Application Precautions • Fail-safe measures must be taken by the customer to ensure safety in the event of incorrect, missing or abnormal signals caused by broken signal lines, momentary power interruptions or other causes. • Configure the control circuits so that the power to the PC (near the CompoNet Master Board) will be on after the power to the I/O Slave Units.
  • Page 19 Application Precautions • Mounting or removing a CompoNet Master Board • Assembling devices • Setting rotary switches • Connecting cables or wiring the system • Connecting or disconnecting the connectors • Close the PC cover before wiring work. This is used to prevent wire waste from entering the PC.

  • Page 20: Conformance With The Ec Directives

    However, the installation and configuration of such machinery and apparatus in which the OMRON products are mounted and used will differ according to their characteristics. Thus it is virtually impossible for OMRON to ensure the conformity of an entire system to the relevant EMC Directives.

  • Page 21: Outline Of Componet And Componet Master Board

    Component Name and Function ........1-3-1 3G8F7-CRM21 (for PCI Bus)......1-3-2 3G8F8-CRM21 (for CompactPCI Bus) .

  • Page 22: Overview Of The Componet Network

    Overview of the CompoNet Network Section 1-1 Overview of the CompoNet Network CompoNet is a field network designed for communications between the input and output components on the shop floor and a personal computer (or PC) or a PLC. CompoNet requires less wiring labor but provides high maintainability. The PC and the CompoNet Slave Unit exchange input and/or output data cyclically through a CompoNet Master Board.

  • Page 23: Overview Of The Componet Master Board

    CompoNet Master Board is a board that has a mastering function to control inputs and outputs for the Slave Units connected to the CompoNet network. The Board is either compatible with PCI bus (Model # 3G8F7-CRM21) or with CompactPCI bus (Model # 3G8F8-CRM21).

  • Page 24: Component Name And Function

    Component Name and Function Section 1-3 Component Name and Function 1-3-1 3G8F7-CRM21 (for PCI Bus) Board ID Switch LED Indicators (MS and NS) This is used to set the board ID. It is set as a They indicate the Module Status (MS) decimal number.

  • Page 25: 3G8F8-Crm21 (For Compactpci Bus)

    Section 1-3 Component Name and Function 1-3-2 3G8F8-CRM21 (for CompactPCI Bus) Board ID Switch LED Indicators (MS and NS) This is used to set the board ID. It is set as a They indicate the Module Status (MS) decimal number. The number must not and Network Status (NS) that are overlap the IDs for other CompoNet Master defined in the CompoNet protocol.

  • Page 26: Led Indication

    Section 1-4 LED Indication LED Indication MS (Module Status) : To indicate the node status. (green and red) NS (Network Status) : To indicate the communications status. (green and red) LED Name Indicating state Status Meaning Green light Normal state The Master Board is in normal operation.

  • Page 27: Network Construction Procedure

    Network Construction Procedure Section 1-5 Network Construction Procedure The following is the basic flow of a network configuration. See Appendix E: 1) Decide the number of I/O points. Construction of a Examine the number of inputs and outputs on the entire system. CompoNet Network 2) Correspond the I/O points to Slave Units.

  • Page 28: Board Preparation Procedure

    Section 1-6 Board Preparation Procedure Board Preparation Procedure The following is the basic flow of a Board preparation. See Section 2: 1) Set the board ID for the CompoNet Master Board. Installation and Select one from 0 to 9. Setup 2) Mount the Board on the PC.

  • Page 29: Specifications

    Section 1-7 Specifications Specifications 1-7-1 General Specifications Item Specifications 3G8F7-CRM21 (PCI) 3G8F8-CRM21 (CompactPCI) Bus specification PCI bus Rev2.2 PICMG 2.0 R3.0 32-Bit 3U Number of mountable 4 pieces 7 pieces boards Compatible OS Microsoft Windows 2000, Windows XP (32-bit edition),...

  • Page 30: Dimensions

    Section 1-7 Specifications 1-7-3 Dimensions 3G8F7-CRM21 (PCI) (unit: mm) 3G8F8-CRM21 (CompactPCI) (unit: mm)

  • Page 31: Installation And Setup

    SECTION 2 Installation and Setup Mounting a Board ..........2-1-1 Confirmation .

  • Page 32: Mounting A Board

    Mounting a Board Section 2-1 Mounting a Board 2-1-1 Confirmation Before you mount a CompoNet Master Board on the PC, confirm the following: Note CompoNet Master Boards support Windows Plug & Play. Item Description Unused PCI bus slot Be sure that the PC you will use has an unused PCI bus slot. Duplication of CompoNet Master Boards use IRQs.

  • Page 33: Mounting The Board On The Pc

    Section 2-1 Mounting a Board Note In the factory setting, the Board ID is set to 0. 2-1-3 Mounting the Board on the PC After setting the ID, mount the CompoNet Master Board on the PCI slot of the Precautions for Correct Use •Be sure to turn off the PC and all peripheral devices, when you mount or remove a CompoNet Master Board.

  • Page 34: Installing The Drivers

    Installing the Drivers Section 2-2 Installing the Drivers If you are using Windows 2000, Windows XP, Windows Vista, or Windows 7, use the Add New Hardware Wizard provided by the OS to install the CompoNet Master Board driver. Procedures are provided here for Windows 2000 and Windows 7. When you use Windows XP or WindowsVista, displays and procedures differ only slightly, but you can take the similar steps.
  • Page 35 Section 2-2 Installing the Drivers 2. On the wizard page of Install Hardware Device Drivers, select the button for Search for suitable driver for my device (recommended). Click the Next button. 3. On the wizard page of Locate Driver Files, check the box for CD-ROM drive.
  • Page 36 Section 2-2 Installing the Drivers 4. When the required driver file is found, click the Next button. 5. The installation is complete when the following page is shown and the Finish button is clicked.
  • Page 37 Installing the Drivers Section 2-2 Windows 7 Note For Windows 7, you must log as the administrator to install the driver. 1,2,3... 1. After the Board is installed in the computer, start the Device Manager. New hardware will be detected automatically. Open the Device Manager, double-click Other devices.
  • Page 38 Section 2-2 Installing the Drivers 3. How do you want to search for driver software? will be displayed. Click Browse my computer for driver software. 4. Place the enclosed CD-ROM into the CD-ROM drive. 5. Browse for driver software on your computer will be displayed. Click the Browse Button, specify the CD-ROM drive (see following figure), and click the Next Button *.
  • Page 39 Section 2-2 Installing the Drivers 6. The following dialog box will be displayed. Click Install this driver software anyway to start installation. 7. The installation will start.
  • Page 40 Section 2-2 Installing the Drivers 8. A completion message (see the following figure) is displayed after the installation process is completed. Click the Close Button to complete driver installation.

  • Page 41: Connecting The Communications Cables

    Connecting the Communications Cables Section 2-3 Connecting the Communications Cables This section outlines the connection procedures in a CompoNet network system by using a round cable I or Flat Cable I. 2-3-1 Connecting a Round Cable An Open Type Connector (DCN4-TB4) is used to connect a CompoNet Master Board to the trunk line of either round cable I or II.
  • Page 42 Connecting the Communications Cables Section 2-3 Precautions for Correct Use Please be aware that the wiring of the Open Type Connector (DCN4-TB4) will protrude into the adjacent panel. Provide any measures to prevent it from interfering with the connector and other component of the neighboring PCI Board.

  • Page 43: Connecting A Flat Cable

    Section 2-3 Connecting the Communications Cables 2-3-2 Connecting a Flat Cable A Flat Connector Plug (DCN4-BR4 or DCN5-BR4) is used to connect a CompoNet Master Board to the trunk line of either Flat Cable I or II. A Flat Connector I Plug (DCN4-BR4) is used with Flat Cable I, while a Flat Connector II Plug (DCN5-BR4) is used with Flat Cable II.
  • Page 44 Provide any measures to prevent it from interfering with the connector and other component of the neighboring PCI Board. •In a configuration where plural 3G8F7-CRM21 CompoNet Master Boards for PCI Bus are used, only one side of adjacent two Boards shall use a DCN4- MD4 Multidrop Connector.

  • Page 45: Connecting The Communications Power Supply Cables

    Section 2-4 Connecting the Communications Power Supply Cables Example of multidrop connection of Flat Cable I DCN4-BR4 Flat Connector Plug DCN4-MD4 Multidrop Connector DCN4-TM4 Terminating Resistor Word Slave Unit Connecting the Communications Power Supply Cables When a round cable II, Flat Cable I or Flat Cable II is used, the Slave Units can be supplied with the communications power through the CompoNet Master Board.
  • Page 46 Section 2-4 Connecting the Communications Power Supply Cables...

  • Page 47: Functions

    SECTION 3 Functions Settings at Communications Cycle Startup ......3-1-1 Settings Required for Starting the Communications Cycle ..Access to I/O Data .

  • Page 48: Settings At Communications Cycle Startup

    Section 3-1 Settings at Communications Cycle Startup Settings at Communications Cycle Startup The function CPNT_StartCycle is used to start the communications cycles for the CompoNet Master Board from the user application. The function CPNT_StartCycle uses the data rate and the number of occupied nodes as arguments.
  • Page 49 Section 3-1 Settings at Communications Cycle Startup • Note Every 16 points of a Word IN Slave Unit or a Word OUT Slave Unit occupies 1 node. For example, when a Word Slave Unit has 64 points and is allocated with the node address #10, it actually occupies the node address #10, #11 #12 and #13.

  • Page 50: Access To I/O Data

    Section 3-2 Access to I/O Data Access to I/O Data 3-2-1 Allocation of I/O Data In the CompoNet network system, the I/O data is allocated separately for Word IN Slave Units, Word OUT Slave Units, Bit IN Slave Units, and Bit OUT Slave Units.
  • Page 51 Section 3-2 Access to I/O Data Precautions for Correct Use When a Slave Unit occupies plural allocation areas, other Slave Units which have the occupied node addresses cannot participate. Example: When a Slave Unit with node address 0 exists in a network and it occupies 2 words in the IN area and 4 words in OUT area, Word IN Slave Units whose node addresses are 0 or 1, and Word OUT Slave Units whose node addresses are 0, 1, 2 or 3 cannot participate.
  • Page 52 Section 3-2 Access to I/O Data • 16-Point Word IN Slave Unit IN area • 16-Point Word OUT Slave Unit OUT area • 32-Point Word IN Slave Unit IN area • 32-Point Word OUT Slave Unit OUT area • 16-Input and 16-Output Word MIX Slave Unit OUT area IN area Allocation for Bit IN...
  • Page 53 Section 3-2 Access to I/O Data BIT IN Data Allocation Area Word address [BIT IN 7] [BIT IN 6] [BIT IN 5] [BIT IN 4] [BIT IN 3] [BIT IN 2] [BIT IN 1] [BIT IN 0] [BIT IN 15] [BIT IN 14] [BIT IN 13] [BIT IN 12]...
  • Page 54 Section 3-2 Access to I/O Data Precautions for Correct Use When a Slave Unit occupies plural allocation areas, other Slave Units which have the occupied node addresses cannot participate. Example: When a Slave Unit with node address #0 exists in a network and it occupies 2 bits in the Bit IN area and 4 bits in Bit OUT area, Bit IN Slave Unit whose node address is 0, and Bit OUT Slave Units whose node address is either 0 or 1 cannot participate.

  • Page 55: Status

    Section 3-3 Status • 4-Point Bit OUT Slave Unit BIT OUT area • 2-Input and 2-Output Bit MIX Slave Unit BIT OUT area BIT IN area 3-2-2 Access to I/O Data There are two methods for access to I/O data: synchronous and asynchronous.

  • Page 56: Detailed Status Group

    Section 3-3 Status Status Description Participation flag When a Slave Unit participates in the network, the bit corresponding to the node address will be on. Once the target Slave Unit is participating, the bit remains on. It stays on even the Slave Unit separates due to a communications error.

  • Page 57: Explicit Messages

    Section 3-4 Explicit Messages Status Description Error log It stores the error log. Registration table It stores the registration table example made from the example information of the Slave Units currently participating. Precautions for Correct Use For a Word Mixed Slave Unit, use the status for the node address of the Word Input Slave Unit.
  • Page 58 Section 3-5 Detailed Settings at Communications Cycle Startup Example Registration table Model Node address CRT1-ID16 CRT1-ID16-1 CRT1-OD16 Master Board The model differs. Compare Due to this difference, the Slave Unit cannot participate. CompoNet network Slave Unit Slave Unit Slave Unit IN Slave Unit IN Slave Unit OUT Slave Unit...

  • Page 59: Communications Stop Due To Communications Error Function

    Section 3-5 Detailed Settings at Communications Cycle Startup *3 When the I/O communications manual startup mode is used, it is not after the power-on but after the remote I/O communications startup switch is started. Setting the Registered This is the time from when the communication cycles for CompoNet Master Slave Unit Participation Board starts until when a registered Slave Unit is determined to have Time...

  • Page 60: In Data Zero Clear Due To Communications Error Function

    Section 3-5 Detailed Settings at Communications Cycle Startup communications started function CPNT_ChangeToRunState in the Windows operation systems and by the command START_IOCYCLE for shared memory access. 3-5-4 IN Data Zero Clear Due to Communications Error Function This function is used to clear (to zero) all the input data or IN data of any IN or MIX Slave Units that have communications error.

  • Page 61: Operation By Api Functions

    SECTION 4 Operation by API Functions (Procedures used in WindowsOS) Access to I/O Data ..........4-1-1 General Access to I/O Data.

  • Page 62: Access To I/O Data

    Access to I/O Data Section 4-1 Access to I/O Data 4-1-1 General Access to I/O Data This is the procedure by which to use the API functions and access the I/O data. Read the Basic status group, and confirm that the expected Slave Unit is participating and that no communications error has occurred.
  • Page 63 Section 4-1 Access to I/O Data 4-1-2 I/O Data Access Synchronous with CompoNet Communications This is the procedure by which to use the API functions and access the I/O data while maintaining node-by-node synchronicity. (Open Board) CPNT_Open (Start communications cycles) CPNT_StartCycle Loop Start (Read Basic status group)
  • Page 64 Access to I/O Data Section 4-1 4-1-3 Access to I/O Data (with Initial OUT Data-Value Setting Function) When the communications cycle is started without making any initial setting for the OUT data, it keeps sending 0 data until the OUT write function is executed.

  • Page 65: Detailed Setting At Communications Cycle Startup

    Section 4-2 Detailed Setting at Communications Cycle Startup Detailed Setting at Communications Cycle Startup This is the procedure by which to use the detailed setting functions such as the Registration table, and to start the communications. Use the function CPNT_StartCycleEx and notify the CompoNet Master Board of the detailed settings.

  • Page 66: Explicit Messaging

    Section 4-3 Explicit Messaging Explicit Messaging 4-3-1 Explicit Messaging This is the procedure by which to use periodic polling from the user application, execute explicit messaging, and confirm the response. (Open Board) CPNT_Open (Start Communications cycles) CPNT_StartCycle Loop Start I/O process and so on An Explicit message request? (Send Explicit Message) CPNT_SendExplicit...
  • Page 67 Explicit Messaging Section 4-3 4-3-2 Explicit Messaging by Windows Messages This is the procedure by which to use the Windows messages, execute explicit messaging and confirm the response. (Open Board) CPNT_Open (Start Communications cycles) CPNT_StartCycle (Register Notice of Explicit Response Message Received) CPNT_RegReceiveExplicitNotifyMessage Loop Start...

  • Page 68: Setting The Time Information

    Section 4-4 Setting the Time Information Setting the Time Information The CompoNet Master Board saves the error occurrence time at the same time when it saves the error history in the internal non-volatile memory. Time data must be notified periodically from the user application to the Board so that the correct time is recorded.

  • Page 69: Implementing The Reset Request

    Section 4-5 Implementing the Reset Request Implementing the Reset Request To use the Reset service of Identity Objects, a logic must be programmed so that the CompoNet Master Board requests a reset and the user application resets the Board. (The logic is not required if you do not use the Reset service of Identity Objects.) Open Board CPNT_Open...

  • Page 70: Access To Detailed Status Group

    Section 4-6 Access to Detailed Status Group Access to Detailed Status Group 4-6-1 Reading the Detailed Status Group The function CPNT_GetStatusEx is used to read out the detailed status group. (Open Board) CPNT_Open (Start Communications cycles) CPNT_StartCycle Loop Start I/O process and so on (Read Detailed status group) CPNT_GetStatusEx Loop End...
  • Page 71 Section 4-6 Access to Detailed Status Group 4-6-2 Clearing the Detailed Status Group The Master Status, Error Counter and Error Log in the Detailed Status Group can be cleared or reset. This is the procedure by which to clear them. (Open Board) CPNT_Open (Start Communications cycles)

  • Page 72: Pc Watchdog Timer

    Section 4-7 PC Watchdog Timer PC Watchdog Timer The CompoNet Master Board has the PC Watchdog Timer (PC WDT) function. This is used to stop the communications automatically whenever the user application, by which the Board is controlled, stops. While the PC WDT function is enabled, the communications automatically stops unless the user application updates the timer value within a specified timeframe.

  • Page 73: Board Hardware Error Notification

    Section 4-8 Board Hardware Error Notification Board Hardware Error Notification This is the function by which to notify the user application of the error when the CompoNet Master Board has stopped due to a hardware error. Here is the procedure by which to use the function: Open Board CPNT_Open Start Communications cycles...
  • Page 74 Section 4-8 Board Hardware Error Notification...

  • Page 75: Operation By Accessing To Shared Memory

    SECTION 5 Operation by Accessing to Shared Memory (Operation procedures in other environments other than Windows OS) Basic Procedures ..........5-1-1 Outline of Board Control.

  • Page 76: Basic Procedures

    Basic Procedures Section 5-1 Basic Procedures 5-1-1 Outline of Board Control In addition to reading from and writing to the Shared memory, these functions are used to control the CompoNet Master Board: Function Description Interrupt It is used for these processes: (PCI interrupt) [Interrupt by the PC to the Board] •...

  • Page 77: Control Of The Interrupt From Board To Pc

    Basic Procedures Section 5-1 5-1-3 Control of the Interrupt from Board to PC Here is the procedure by which to process interrupts from the CompoNet Master Board to the user application: [Initial process] Before you start the communications (or you issue the command OPEN_SYSTEM/OPEN_SYSTEMEX), set the Interrupt Mask (or select to notify the interrupt by causes or to confirm it by polling).

  • Page 78: Communications Cycle Control Procedures

    Communications Cycle Control Procedures Section 5-2 5-1-4 Command Access Control Step Operation procedure Access to Shared Memory Set the command. Set the command to notify to the CompoNet Master → Board in the Command Area (PC BD) (0x3200). Notify the command set. In the Interrupt Trigger register (0x0002), set the CMD flag to 1.
  • Page 79 Communications Cycle Control Procedures Section 5-2 Initial state OPEN_SYSTEM/ OPEN_SYSTEMEX Communications Cycle Operation STOP_CYCLE Communications (IDLE state) Cycle Operation [for a specified period of time] (IDLE state) Communication stop STOP_IOCYCLE START_IOCYCLE Communications Cycle Operation (RUN state) STOP_CYCLE These functions are used during the communications cycle operation. Function Description Communications...

  • Page 80: Controls From The Initial Process To Communications Cycle Startup

    Communications Cycle Control Procedures Section 5-2 5-2-2 Controls from the Initial Process to Communications Cycle Startup Step Operation procedure Access to Shared Memory Confirm the PCI Get the base address of shared memory space and the resources. Interrupt line from the Board ID and the contents in the PCI configuration register.

  • Page 81: Control Of I/O Data Access

    Communications Cycle Control Procedures Section 5-2 5-2-3 Control of I/O Data Access [Asynchronous access] Constant reads and writes to and from the I/O Data Group (0x0100) are supported in the normal communications cycles. [Synchronous access] Follow these steps in order to use synchronous access: Step Operation procedure Access to Shared Memory...

  • Page 82: Control Of Event Access

    Communications Cycle Control Procedures Section 5-2 Step Operation procedure Access to Shared Memory Read a response for the The REQUEST_STATUS command response from the command CompoNet Master Board is stored in the Command area → REQUEST_STATUS. PC) (0x3210). Read it. Release the command Set the CMD_ACK flag of the Interrupt Clear register acknowledgment...

  • Page 83: Setting The Time Information

    Setting the Time Information Section 5-3 Step Operation procedure Access to Shared Memory Wait the notice to tell Wait that the SND_ACK Interrupt cause of the Interrupt event capturing Cause Indication register (0x0005) changes to 1 completes. periodically. (This is the case when the SND_ACK is confirmed by polling.) Clear the Interrupt cause...

  • Page 84: Pc Watchdog Timer

    PC Watchdog Timer Section 5-5 [REQ_RES by interrupts] Step Operation procedure Access to Shared Memory Confirm the Interrupt Confirm the cause of REQ_RES interrupt in the Interrupt cause. Request Indication register (0x0005). Clear the Interrupt cause. Set the REQ_RES flag of the Interrupt Clear register (0x0006) to 1.

  • Page 85: Board Hardware Error Notification

    Board Hardware Error Notification Section 5-6 [Disabling the PC Watchdog Timer] Step Operation procedure Access to Shared Memory Set the command Set the time-out value for CompoNet Master Board in the → SET_PC_WDT. Command area (PC BD) (0x3200) to 0. This is used to set the command SET_PC_WDT.
  • Page 86 Board Hardware Error Notification Section 5-6 [BD_WDT by an interrupt] Step Operation procedure Access to Shared Memory Confirm the interrupt Confirm the BD_WDT interrupt cause in Interrupt Cause cause. Indication register (0x0005). Clear the interrupt cause. Set the BD_WDT flag of the Interrupt Clear register (0x0006) to 1.

  • Page 87: Troubleshooting

    SECTION 6 Troubleshooting LED Indications and Error Handling....... . 6-1-1 Identifying Errors .

  • Page 88: Led Indications And Error Handling

    Section 6-1 LED Indications and Error Handling LED Indications and Error Handling CompoNet Master Board has two LED indicators: MS LED for Board status and NS LED for network status. They indicate an error occurrence and the error content. This section explains the LED indicators and how to handle the errors. The explanation assumes that the CompoNet Master Board has been set up properly.

  • Page 89: Led Indication During Normal Operation

    Section 6-1 LED Indications and Error Handling 6-1-2 LED Indication During Normal Operation State Meaning Power not supplied The power is not supplied. It waits for a startup by the user application. Wait for startup Green The communications stops. The state is achieved when the user application explicitly requests a Communications stopped Green communications stop.

  • Page 90: Error Log

    Section 6-2 Error Log 6-1-4 Error Identification by StateStatus The errors monitored by NS Indicator lighting or flashing are identifiable by StateStatus of the Basic status group. In the Windows operation systems, use the function CPNT_GetStatus to access the Basic status group. In other environment, access to the shared memory area directly.

  • Page 91: Error Code And Description List

    Error Log Section 6-2 Error Log Saving Area When an error is detected, it is saved, along with the time when the error occurred, as an error in the CompoNet Master Board RAM. Some errors are fatal and they are also saved in the EEPROM. Those error logs saved in the EEPROM are retained even after the CompoNet Master Board is shutdown or reset.
  • Page 92 Error Log Section 6-2 Error Description Detailed Information EEPROM Code 1st byte 2nd byte 0x0375 Communication Stop due to a 0x10: Word IN Slave Unit Node address (Hex) Communications Error Word MIX Slave Unit [Cause] 0x20: Word OUT Slave Unit A communications error occurs when the 0x40: Bit IN Slave Unit Communications Stop due to...

  • Page 93: Api Function Reference

    APPENDIX A API Function Reference A-1 Function List ..........A-1-1 Board Control API Functions .

  • Page 94: Function List

    Function List Section A-1 Function List This section describes API functions provided by DLL. A-1-1 Board Control API Functions They provide the initial and final processing for CompoNet Master Board. This includes opening or closing a specified board. API function Description CPNT_Open To open a specified board...

  • Page 95: I/O Data Access Api Functions

    Section A-1 Function List A-1-4 I/O Data Access API Functions These access the I/O data. API function Description CPNT_GetAccessToIO To get an access right to I/O data CPNT_ReleaseAccessToIO To release the access right to I/O data CPNT_GetInData To read the IN data from IN Slave Unit CPNT_GetBitInData To read the Bit IN data from Bit IN Slave Unit CPNT_SetOutData...

  • Page 96: Board Control Api

    Section A-2 Board Control API Board Control API A-2-1 CPNT_Open (Open Board) Purpose Open the Board that has the specified ID, and enable it for use. Call Format HANDLE CPNT_Open(WORD BoardId) ; Argument Type Parameter Direction Description WORD BoardId ID of Board to be opened Specified range: 0x0 to 0x9 (0 to 9) Returned value When the function succeeds, the open device handle is returned.

  • Page 97: Communications Control Api

    Communications Control API Section A-3 Returned value It returns TRUE when the function succeeds. It returns FALSE when an error occurs. The error details can be obtained with the function GetLastError. • Remarks With this function, the Board is reset. All data that has been set is cleared. Handle is not closed.
  • Page 98 Section A-3 Communications Control API Argument Type Parameter Direction Description HANDLE Handle Device handle obtained with the function CPNT_Open CPNT_SOFT *SoftwareTable IN Specify the number of occupied WARE_TABLE nodes. WORD DataRate Specify the data rate. 0: 4 Mbps 1: 3 Mbps 2: 1.5 Mbps 3: 93.75 kbps Returned value...

  • Page 99: Cpnt_Startcycleex (Start Communications Cycles In The Detailed Setting)

    Section A-3 Communications Control API A-3-2 CPNT_StartCycleEx (Start Communications Cycles in the Detailed Setting) Purpose Start the communications cycles in the detailed setting. Call Format BOOL CPNT_StartCycleEx( HANDLE Handle, CPNT_SOFTWARE_TABLE*SoftwareTable, WORD DataRate, CPNT_EX_TABLE *ExTable, WORD EnableList Argument Type Parameter Direction Description HANDLE Handle...
  • Page 100 Section A-3 Communications Control API Flag Description Logical error 0 (OFF): Disabled checking item flag 1 (ON): Enabled This is used to set the items to be checked when a Slave Unit re-participates after a communications error. When it is enabled, set the necessary data to the structure CPNT_EX_TABLE.
  • Page 101 Section A-3 Communications Control API LogicalCheck Flag Description VendorCode 0 (OFF): Not Checked 1 (ON): Checked DeviceType ProductCode MajorRevision 4 to 15 Reserved area Always set 0 (OFF). CPNT_NET_PARAM structure Type Parameter Description WORD EventEnable 0x0000: Event enabled 0x0001: Event disabled When the event function is disabled, the communications cycle becomes shorter.
  • Page 102 Section A-3 Communications Control API CPNT_REGIST_TABLE structure Type Parameter Description WORD RunSet This is used to set the Registration table function. Flag Description Registration Always set it to 1 (ON) table enabled when the Registration flag table is used. All Registered 0 (OFF): Disabled Slave 1 (ON): Enabled...

  • Page 103: Cpnt_Stopcycle (Stop Communications Cycles)

    Section A-3 Communications Control API Type Parameter Description WORD VendorCode[3 These items must be set when the relevant flags for RegSet are selected to check. Set the values of Slave Unit Identity object WORD DeviceType[38 information. WORD ProductCode[ 384] BYTE MajorRevision[ 384] I/O size information format...

  • Page 104: A-3-4 Cpnt_Changetorunstate (Transition To Run)

    Section A-3 Communications Control API Argument Type Parameter Direction Description HANDLE Handle Device handle obtained with the function CPNT_Open Returned value It returns TRUE when the function succeeds. It returns FALSE when an error occurs. The error details can be obtained with the function GetLastError.

  • Page 105: Status Access Api

    WORD DeviceType Device type of the Board, It is 0x000C. WORD ProductCode Product code of the Board. It is 0x0015 for the product 3G8F7-CRM21. It is 0x0016 for the product 3G8F8-CRM21. BYTE MajorVersion Major board revision BYTE MinorVersion Minor board revision...

  • Page 106: A-4-3 Cpnt_Getstatus (Read Basic Status Group)

    Section A-4 Status Access API Argument Type Parameter Direction Description HANDLE Handle Device handle obtained with the function CPNT_Open DRIVER_VER *VersionInfo Pointer to store the version SION_INFO information Returned value It returns TRUE when the function succeeds. It returns FALSE when an error occurs. The error details can be obtained with the function GetLastError.

  • Page 107: Cpnt_Getstatusex (Read Detailed Status Group)

    Section A-4 Status Access API A-4-4 CPNT_GetStatusEx (Read Detailed Status Group) Purpose Read the Detailed status group. Call Format BOOL CPNT_GetStatusEx ( HANDLE Handle, CPNT_STATUSEX *StatusEx, WORD StatusExInfo Argument Type Parameter Direction Description HANDLE Handle Device handle obtained with the function CPNT_Open CPNT_STATU *StatusEx...

  • Page 108: A-4-5 Cpnt_Resetstatusex (Clear Detailed Status Group)

    Section A-4 Status Access API StatusExInfo Flag Parameter Duplication error flag 0 (OFF): Not the item to read among the Detailed status group, Registration error 1 (ON): Item to read among the Detailed status (Registered Slave group not participating) flag Registration error (Non-registered Slave participating)

  • Page 109: A-4-6 Cpnt_Setdatetime (Write Time Data)

    Section A-4 Status Access API StatusExInfo Flag Description Duplication error flag These statuses cannot be cleared. Set 0 (OFF). Registration error (Registered Slave not participating) flag Registration error (Non-registered Slave participating) flag Repeater configuration error EO Slave Unit Master status 0 (OFF): Not the item to clear among the Detailed status group, Error counter...

  • Page 110: I/O Data Access Api

    Section A-5 I/O Data Access API Returned value It returns TRUE when the function succeeds. It returns FALSE when an error occurs. The error details can be obtained with the function GetLastError. Remarks To execute this function, the communications cycles must be running. CPNT_DATETIME structure Type Parameter...

  • Page 111: Cpnt_Getindata (Get In Data From Word In Slave Unit)

    Section A-5 I/O Data Access API Returned value It returns TRUE when the function succeeds. It returns FALSE when an error occurs. The error details can be obtained with the function GetLastError. Remarks To execute this function, the I/O communications must be running. A-5-3 CPNT_GetInData (Get IN Data from Word IN Slave Unit) Purpose...

  • Page 112: Cpnt_Setoutdata (Set Out Data In Word Out Slave Unit)

    Section A-5 I/O Data Access API Argument Type Parameter Direction Description HANDLE Handle Device handle obtained with the function CPNT_Open WORD *BitIN Specify the pointer to store Bit IN data. Requires the area equivalent to Word size (32 bytes max) WORD WordOffset Specify the Word offset for the Bit...

  • Page 113: Explicit Messaging Api

    Section A-6 Explicit Messaging API A-5-6 CPNT_SetBitOutData (Set Bit OUT Data to Bit OUT Slave Unit) Purpose Set the Bit Out data in Bit OUT Slave Units. Call Format BOOL CPNT_SetBitOutData ( HANDLE Handle, WORD *BitOUT, WORD WordOffset, WORD WordSize Argument Type Parameter...

  • Page 114: Cpnt_Peekexplicit (Check Response Received)

    Section A-6 Explicit Messaging API Remarks To execute this function, the communications cycles must be running. CPNT_EXPLICIT_REQ structure Type Parameter Description BYTE This is used to identify to which explicit message a response is addressed. The same value is added to the response of a sent explicit message.

  • Page 115: Cpnt_Unregreceiveexplicitnotifymessage (Unregister Notice Of Explicit Response Message Received)

    Section A-6 Explicit Messaging API Call Format BOOL CPNT_RegReceiveExplicitNotifyMessage( HANDLE Handle, DWORD ThreadId, HWND hWnd, UINT Msg Argument Type Parameter Direction Description HANDLE Handle Device handle obtained with the function CPNT_Open DWORD ThreadId ID of the thread to notify (No setting: NULL) HWND hWNd...

  • Page 116: A-6-5 Cpnt_Receiveexplicit (Get Explicit Response Message)

    Section A-6 Explicit Messaging API A-6-5 CPNT_ReceiveExplicit (Get Explicit Response Message) Purpose Read the Explicit response message. Call Format BOOL CPNT_ReceiveExplicit ( HANDLE Handle, CPNT_EXPLICIT_RES *ExplicitRes Argument Type Parameter Direction Description HANDLE Handle Device handle obtained with the function CPNT_Open CPNT_EXPLI *ExplicitRes Set the pointer to store the...

  • Page 117: Pc Watchdog Timer Api

    Section A-7 PC Watchdog Timer API PC Watchdog Timer API A-7-1 CPNT_EnablePCWDTTimer (Enable PC WDT) Purpose Enable or disable the PC Watchdog Timer. Call Format BOOL CPNT_EnablePCWDTTimer ( HANDLE Handle, WORD Timer Argument Type Parameter Direction Description HANDLE Handle Device handle obtained with the function CPNT_Open WORD Timer...

  • Page 118: Board Request Notification Api

    Section A-8 Board Request Notification API Board Request Notification API A-8-1 CPNT_RegBDWDTNotifyMessage (Register Board Hardware Error Message) Purpose Register the Windows message to notify a Board hardware error. Call Format BOOL CPNT_RegBDWDTNotifyMessage ( HANDLE Handle, DWORD ThreadId, HWND hWnd, UINT Msg Argument Type Parameter...

  • Page 119: A-8-3 Cpnt_Regresetnotifymessage (Register Board Reset Request Message)

    Section A-8 Board Request Notification API A-8-3 CPNT_RegRESETNotifyMessage (Register Board Reset Request Message) Purpose Register the Windows message to request a Board reset. Call Format BOOL CPNT_RegRESETNotifyMessage ( HANDLE Handle, DWORD ThreadId, HWND hWnd, UINT Msg Argument Type Parameter Direction Description HANDLE Handle...

  • Page 120: Errors Detectable By Functions

    Section A-9 Errors Detectable by Functions Errors Detectable by Functions If an error occurs while an API function is executed, details of the error can be obtained with the function GetLastError. Error code Value Error content and Action to be taken CPNT_INVALID_HANDLE 0x20000001 Driver handle value is invalid.

  • Page 121: Shared Memory Interface

    APPENDIX B Shared Memory Interface B-1 PCI Resources ..........B-1-1 PCI Configuration Register Information.

  • Page 122: Pci Resources

    PCI Resources Section B-1 PCI Resources B-1-1 PCI Configuration Register Information Register Value Description Vendor ID 0x10CB Omron Device ID 0x0024 CompoNet Revision ID 0x01 Class code 0x028000 Other network controller Header type 0x00 Basic header type Base address Set by PC BIOS...

  • Page 123: Pci Register Specifications

    PCI Register Specifications Section B-2 PCI Register Specifications B-2-1 PCI Register Map Offset Name Access rule 0x0000 Board ID Read 0x0001 Board reset Write 0x0002 Interrupt control register Interrupt trigger Write (Interrupt from PC to Board) 0x0003 Interrupt request Read confirmation 0x0004 Interrupt control register...

  • Page 124: Interrupt Control Register (Interrupt From Pc To Board)

    PCI Register Specifications Section B-2 B-2-4 Interrupt Control Register (Interrupt from PC to Board) This register is used to make an interrupt request from the PC to the Board. When you use the Interrupt Trigger register and set the flag to cause into 1, an interrupt occurs on the Board.

  • Page 125: Interrupt Control Register (Interrupt From Board To Pc)

    PCI Register Specifications Section B-2 B-2-5 Interrupt Control Register (Interrupt from Board to PC) This register is used to control interrupts from the Board to the PC. The Interrupt Mask register is used to specify the generation of an interrupt by a certain cause.
  • Page 126 PCI Register Specifications Section B-2 Interrupt Request Indication (Offset 0x0005) bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0 Flag BD_WDT REQ_ACC INIEND Unused REQ_RES SND_ACK BD_SND CMD_ACK _ACK Access rule Initial value Interrupt Clear (Offset 0x0006) bit7 bit6 bit5 bit4 bit3 bit2 bit1...

  • Page 127: Shared Memory Area Specifications

    Shared Memory Area Specifications Section B-3 Shared Memory Area Specifications B-3-1 Shared Memory Area Map Offset Group Name Word size Access Update timing address (Byte size) 0x0010 to Board Initialization end notification Initialization 0x0011 information group 0x0012 to Running program ID Initialization 0x0013 0x0014 to...

  • Page 128: B-3-2 Board Information

    Shared Memory Area Specifications Section B-3 Offset Group Name Word size Access Update timing address (Byte size) → 0x3200 to CMDarea group CMD area (PC 0x3203 → 0x3210 to CMD area (BD 0x3213 → 0x3300 to Event area Explicit Event area (PC 0x3521 group (546)
  • Page 129 Shared Memory Area Specifications Section B-3 Data in detail Name Access Description ProgId Read 0xFFFF: Waits for the command OPEN_SYSTEM. 0x0001: The system firmware is running. 0xEEEE: The PC WDT is out and stops. Identity information This is the Identity Object information of the CompoNet Master Board. Data format Offset address: 0x0014 Offset...

  • Page 130: B-3-3 Basic Status Group In Detail

    Shared Memory Area Specifications Section B-3 B-3-3 Basic Status Group in Detail Participation Flag This indicates the participation flag of each node. Data format Offset address: 0x0042 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Word IN/MIX Slave Unit Participating Flags (These values are the corresponding part of each node address.) 15 14 13 12 11 10...
  • Page 131 Shared Memory Area Specifications Section B-3 Communications This indicates the communications error flag of each node. Error Flag Data format Offset address: 0x007A Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Word IN/MIX Slave Unit Communications Error Flags (These values are the corresponding part of each node address.) 15 14 13 12 11 10...
  • Page 132 Shared Memory Area Specifications Section B-3 StateStatus Data format Offset address: 0x00B2 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 StateStatus Detailed format Name Access Description Communications Read 0 (OFF): Normal error occurred on 1 (ON): An error occurred.

  • Page 133: Clock In Details

    Shared Memory Area Specifications Section B-3 Name Access Description Operation Read 0 (OFF): One of the following: an error monitoring occurred, the I/O communications not ((!D0)&D6&D7) started or a non-registered Slave Unit is participating. 1 (ON): All of the following: in normal communications and I/O communications, and all of the registered Slave Units have...

  • Page 134: I/O Data In Details

    Shared Memory Area Specifications Section B-3 B-3-5 I/O Data in Details Word IN Data This stores the IN data from a Word IN Slave Unit. Data format Offset address: 0x0100 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 IN data of Word IN/MIX Slave Unit #0 IN data of Word IN/MIX Slave Unit #1 IN data of Word IN/MIX Slave Unit #2...
  • Page 135 Shared Memory Area Specifications Section B-3 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Node Node Node Node Node Node Node Node Node Node Node Node Node Node Node Node Node Node Node...
  • Page 136 Shared Memory Area Specifications Section B-3 Bit OUT Data This stores the Bit OUT data given to a Bit OUT Slave Unit. Data format Offset address: 0x0280 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Node 7 Node 6 Node 5 Node 4 Node 3 Node 2 Node 1 Node 0 Node Node...

  • Page 137: Detailed Status Group In Details

    Shared Memory Area Specifications Section B-3 B-3-6 Detailed Status Group in Details Duplication Error Flag This is the duplication error flag for a node. This error occurs not only due to a duplication but also when a Slave Unit stops because of unstable communications. Data format Offset address: 0x0300 Offset...
  • Page 138 Shared Memory Area Specifications Section B-3 Detailed format Name Access Description Duplication error flag Read ON: Duplication error occurs OFF: Normal Registration Error This is the Registration error flag (Registered Slave not participating) for each (Registered Slave Not node. Participating) Flag Data format Offset address: 0x0338 Offset...
  • Page 139 Shared Memory Area Specifications Section B-3 Detailed format Name Access Description Registration error Read ON: A Registration error (Registered Slave not (Registered Slave participating) occurs. not participating) flag OFF: Normal Registration Error This is the Registration error (Non-registered Slave participating) flag for each (Non-registered Slave node.
  • Page 140 Shared Memory Area Specifications Section B-3 Detailed format Name Access Description Registration error Read ON: A Registration error (Non-registered Slave (Non-registered participating) occurs. Slave participating) OFF: Normal flag Repeater This is the Repeater configuration error flag for each node. Configuration Error Data format Offset address: 0x0398 Offset...
  • Page 141 Shared Memory Area Specifications Section B-3 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 Detailed format Name...
  • Page 142 Shared Memory Area Specifications Section B-3 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 Flags for Repeater Units...
  • Page 143 Shared Memory Area Specifications Section B-3 Detailed format Name Access Description Node causing a Read It stores the MAC address (or the address on communications CompoNet protocol) of the Slave Unit or the stop Repeater Unit that caused a communications stop due to communications error.
  • Page 144 Shared Memory Area Specifications Section B-3 If the error counter value exceeds the threshold, the CompoNet Master Board will deem the relevant Slave or Repeater Unit to have a communications error. The error counter can also be used to determine the network quality, even when there is no communications error.
  • Page 145 Shared Memory Area Specifications Section B-3 Network Power State This can be used to confirm whether network power is being supplied to the CompoNet Master Board. Data format Offset address: 0x05DA Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 NetPower StateStatusDetailed format Name...
  • Page 146 Shared Memory Area Specifications Section B-3 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 +703 Vendor Code of Bit IN/MIX Slave Unit #127 +704 Vendor Code of Bit OUT Slave Unit #0 +831 Vendor Code of Bit OUT Slave Unit #127 +832...
  • Page 147 Shared Memory Area Specifications Section B-3 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 +1919 Major Revision of Bit IN/MIX Slave Major Revision of Bit IN/MIX Slave Unit #63 Unit #62 +1920 Major Revision of Bit OUT Slave Unit Major Revision of Bit OUT Slave Unit +1983 Major Revision of Bit OUT Slave Unit...
  • Page 148 Shared Memory Area Specifications Section B-3 I/O size information format Flag Description 0 to 4 Number of IN Set the number of IN points of Slave Units. channels (points) Set the Bits 0 to 5 to 0 (OFF), when the number of IN points is zero.
  • Page 149 Shared Memory Area Specifications Section B-3 Data format Offset address: 0x1C9C Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Repeater configuration info of Word IN/MIX Slave Unit #0 Repeater configuration info of Word IN/MIX Slave Unit #63 Repeater configuration info of Word OUT Slave Unit #0 +127 Repeater configuration info of Word OUT Slave Unit #63...
  • Page 150 Shared Memory Area Specifications Section B-3 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Alarm information Alarm information Alarm information Alarm information of Bit IN/MIX of Bit IN/MIX of Bit IN/MIX of Bit IN/MIX Slave Unit #3 Slave Unit #2...
  • Page 151 Shared Memory Area Specifications Section B-3 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 +316 64th error code +317 64th detailed code +318 Minute of the 64th error occurrence Second of the 64th error occurrence (0 to 59) (0 to 59) +319...

  • Page 152: B-3-7 Cmd Area In Detail

    Shared Memory Area Specifications Section B-3 B-3-7 CMD Area in Detail CMD area (PC→BD) A request command made by the PC to the CompoNet Master Board has the following format. The data size is fixed. If a command has no argument, 0x0000 will be stored.

  • Page 153: B-3-8 Event Area In Detail

    Shared Memory Area Specifications Section B-3 B-3-8 Event Area in Detail Event area (PC→BD) This area is used when an explicit request message is sent by the PC to the CompoNet Master Board or to a Slave or Repeater Unit. Data format Offset address: 0x3300 Offset...
  • Page 154 Shared Memory Area Specifications Section B-3 Event Area (BD→PC) This is the area in which to store an explicit response message for the explicit request message. Data format Offset address: 0x3600 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Byte length size after Offset+1 (2 to 542) Reserved (0x00) 0x02...

  • Page 155: B-3-9 Setting Area In Detail

    Shared Memory Area Specifications Section B-3 End code (hex) Description MRES SRES The command is not in the specified format. Header error The response exceeds the maximum length. The destination is in the state that cannot receive an explicit message. CompoNet Master Board is in initialization process.
  • Page 156 Shared Memory Area Specifications Section B-3 Data format Offset address: 0x3908 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Data rate Detailed format Name Access Description Data rate Read/Write 0: 4 Mbps 1: 3 Mbps 2: 1.5 Mbps 3: 93.75 kbps...
  • Page 157 Shared Memory Area Specifications Section B-3 Data format Offset address: 0x390C Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 Function setting Time to wait for a registered Slave Unit to participate Reserved (0x00) Checking items for the Registration Table...
  • Page 158 Shared Memory Area Specifications Section B-3 Offset (Word) 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00 +1282 Product Code of Word OUT Slave Unit #63 +1283 Product Code of Bit IN/MIX Slave Unit #0 +1410 Product Code of Bit IN/MIX Slave Unit #127 +1411...
  • Page 159 Shared Memory Area Specifications Section B-3 Detailed format Name Access Description Function setting Read/Write Sets the Registration table function. Flag Description Registration Set it to 1 (ON) when table enabled the Registration tables flag are used. All Registered 0 (OFF): Disabled Slave 1 (ON): Enabled Participation...
  • Page 160 Shared Memory Area Specifications Section B-3 I/O size information format Flag Description 0 to 4 Number of IN Set the number of IN channels of Slave Units. channels (points) Set the Bits 0 to 5 to 0 (OFF), when the number of IN channels is zero.
  • Page 161 Shared Memory Area Specifications Section B-3 Detailed format Name Access Description Event function Read/Write 0x0000: Enabled enabling 0x0001: Disabled The communications cycle becomes shorter when the Event function is not used. In that case, explicit messages cannot be sent to Slave Units or Repeater Units.

  • Page 162: Command Specifications

    Command Specifications Section B-4 Command Specifications B-4-1 Command List See Appendix B.3.7 for the command format. Group Command name Code Description Common OPEN_SYSTEM 0x0001 This starts the system with the basic setting of data rate and number of occupied nodes. Then it starts the communications cycles.
  • Page 163 Command Specifications Section B-4 • Remarks To issue this command, the setting areas of the software table and data rate must be set. Command OPEN_SYSTEMEX Purpose Open the CompoNet Master Board, and let it be ready to be used. Code 0x0002 Argument Function...
  • Page 164 Command Specifications Section B-4 • Network parameter • Slave Unit parameter Command START_IOCYCLE Purpose Start the I/O communications. Code 0x1001 Argument None Set 0x0000. Response code Normal end: 0x0000 At an error: Status change not allowed: 0x8101 • Remarks This command is used to start the I/O communications, when the I/O communications manual startup function is enabled or after the I/O communications is explicitly stopped.
  • Page 165 Command Specifications Section B-4 Command STOP_CYCLE Purpose Stop the communications cycles. Code 0x1003 Argument None Set 0x0000. Response code Normal end: 0x0000 At an error: Status change not allowed: 0x8101 • Remarks To resume the communications, the CompoNet Master Board must be reset. •...
  • Page 166 Command Specifications Section B-4 Command REQUEST_RESETSTATUS Purpose Issue a request to clear the Detailed status group. Code 0x2002 Argument Clearing status 1-WORD data, items Set the bits to clear to 1 (ON) and the bits not to clear to 0 (OFF).

  • Page 167: Communications Performance

    APPENDIX C Communications Performance C-1 Remote I/O Communications Performance......C-1-1 Input time (Slave Unit Æ Master Board) ..... C-1-2 Output time (Master Board Æ...

  • Page 168: Remote I/O Communications Performance

    Section C-1 Remote I/O Communications Performance Remote I/O Communications Performance This section explains the remote I/O communications performance of the CompoNet Master Board. Input time (Slave Unit → Master Board) C-1-1 This is the input time for the CompoNet network. The input time refers to the time until the input signal of an IN Slave Unit is captured by the Master Board application.
  • Page 169 Section C-1 Remote I/O Communications Performance C-1-3 Descriptions of Parameters Input Slave Unit input delay time Output Slave Unit output delay time Communications cycle time NetCyc Time allotted for IN frames in communications cycle time NetIn Time allotted for OUT frame in communications cycle time NetOut Input processing time at the Master Board CrmIn...
  • Page 170 Section C-1 Remote I/O Communications Performance Conditions Data rate Word Outputs Word Inputs Bit outputs Bit inputs 4.0 Mbit/s 16 Units 32 Units 64 Units 32 Units (16 × 4.06 µs) + (32 × 11.81 µs) + (64 × 0.57 µs) + (32 × 10.25 µs) ≈ 0.81ms S1 is the correction coefficient that is used when more than 32 Word IN Slave Units are connected.
  • Page 171 Section C-1 Remote I/O Communications Performance S1 Calculation Example Conditions Data rate Word Inputs 4.0Mbps 60 Units 60 × 3.38 µs ≈ 0.202 ms S2 is the correction coefficient that is used when more than 64 Bit IN Slave Units are connected.
  • Page 172 Section C-1 Remote I/O Communications Performance Slave Units Data rate 4.0 Mbit/s 3.0 Mbit/s 1.5 Mbit/s 93.75 kbit/s Slave Unit Type 4.06 µs 5.37 µs 10.88 µs 170.93 µs Word Output Unit 4.06 µs 5.37 µs 10.88 µs 170.93 µs Bit Output Unit K Calculation Example Conditions...

  • Page 173: Sample Program

    APPENDIX D Sample Program D-1 Sample Program..........

  • Page 174: Sample Program

    Section D-1 Sample Program Sample Program The CD packaged with the product contains the sample program. The program corresponds to the descriptions in Section 4 and 5. Read the text document, Readme.txt, in the CD to understand the sample program in detail. The program is created to explain the API and the shared memory access.

  • Page 175: Installation And Setup

    APPENDIX E Installation and Setup CompoNet Network Specifications ....... . . E-1-1 Communications Specifications .

  • Page 176: Componet Network Specifications

    CompoNet Network Specifications Section E-1 CompoNet Network Specifications E-1-1 Communications Specifications Item Specifications Communications protocol CompoNet Network protocol Types of communications Remote I/O communications, i.e., program-less, constant data sharing with Slave Units; and message communications, i.e., occasional (as required) explicit message communications with Slave Units and occasional (as required) Explicit message communications with PLC Data rate 4 Mbps *1, 3 Mbps, 1.5 Mbps or 93.75 kbps...

  • Page 177: E-1-2 Communications Cables

    CompoNet Network Specifications Section E-1 E-1-2 Communications Cables Cable types The following four types of cables can be used in a CompoNet network: round cable I, round cable II, Flat Cable I and Flat Cable II. Do not use other types of cables. Cable type Major applications With or without a...
  • Page 178 CompoNet Network Specifications Section E-1 Model number Specification Available from UNICOMPO FC I-T Flat Cable I Nichigoh Communication Electric Wire Co., Ltd. UNICOMPO FC II-T Flat Cable II UNICOMPO RC I-T Round Cable I UNICOMPO RC II-T Round Cable II CNS-F I Round Cable I (stationary use) Dyden Corporation...
  • Page 179 CompoNet Network Specifications Section E-1 Flat Cable I (DCA4-4F10 Standard Flat Cable) Black: BS Red: BS White: BDH Blue: BDL Conductor Insulation Application Nominal Allowable cross- current (A) color section BS + (positive side of 0.75 5 max. communications power supply) −...
  • Page 180 CompoNet Network Specifications Section E-1 Types of Flat Cable II other than DCA5-4F10 can be used as long as they conform to the CompoNet specifications. Ask the cable manufacturer for information on which products are applicable to CompoNet. Precautions for Correct Use •As for the products conforming the CompoNet specifications and their manufacturers, check the ODVA website at the following address: http: // www.odva.org/...

  • Page 181: E-1-3 Maximum Length And Maximum Number Of Connectable Slave Units For Each Type Of Cable

    CompoNet Network Specifications Section E-1 Component Cable Specifications Round Cable I Round Cable II Flat Cable I Flat Cable II Type Signal Signal Power Signal Power Signal Power Conductors 0.75 mm × 2 0.75 mm × 0.75 mm × 0.5 mm ×...
  • Page 182 CompoNet Network Specifications Section E-1 Slave Unit T-branch connection Multidrop connection Terminating Resistor Branch line length Trunk line length CompoNet Master Board Terminating Trunk line Resistor Repeater Repeater Repeater Unit Unit Unit Branch line Slave Unit Branch line Branch line Branch line Branch line Sub-trunk...
  • Page 183 CompoNet Network Specifications Section E-1 In Data Rate of 3 Mbps Item Round cable I or II Flat Cable I or II Length of a trunk line or a sub- 30 m (90 m) 30 m (90 m) trunk line (Maximum length when two Repeater Units are used) Length of a branch line 0.5 m...
  • Page 184 CompoNet Network Specifications Section E-1 *3 Branch lines support T-branch connections. In Data Rate of 93.75 kbps Item Round cable I Round cable II Flat Cable I or II Length of a trunk line or a sub- 500 m (1500 m) Unrestricted wiring can trunk line (Maximum length when be done for a total...

  • Page 185: Wiring Formations

    Wiring Formations Section E-2 The Same Address You can use the same node address again for different node address types as Can Be Used for long as long as the same areas are not allocated. Different Node You cannot use the same address for a Word Mixed Slave Unit and Word Address Types Output Slave Unit because the same areas would be allocated.

  • Page 186: E-2-2 Unrestricted Wiring Formation

    Wiring Formations Section E-2 E-2-2 Unrestricted Wiring Formation In this formation, there is no distinction between the trunk line and branch lines. There are no wiring restrictions as long as the total cable length per segment does not exceed 200 m. There is also no limit in the number of branches.

  • Page 187: Wiring For A Componet Network

    Wiring for a CompoNet Network Section E-3 Wiring for a CompoNet Network A CompoNet Network requires wiring of following lines. • Two communications signal lines: BDH (or communications data high) and BDL (or communications data low), • Two communications power supply lines: one for communications and the other for internal circuits of Slave Units.

  • Page 188: Wiring Round Cable Ii

    Wiring for a CompoNet Network Section E-3 Multidrop Connectors can also be used to connect the Slave Units in parallel. Master Board or Repeater Unit Terminating Resistor (121 ) Commu- nications Open Type Connector Communications Communications Slave Unit Slave Unit Slave Unit Open Type Connector Communications...
  • Page 189 Wiring for a CompoNet Network Section E-3 Communications power supply connector Master Board or Repeater Unit Communications power supply, 24 VDC Communications power supply Communications power supply lines (2) Relay terminal block Terminating Communications signal lines (2) Resistor (121 ) Open Type Connector Slave Unit Slave Unit...

  • Page 190: E-3-3 Wiring Flat Cable I Or Ii

    Wiring for a CompoNet Network Section E-3 E-3-3 Wiring Flat Cable I or II • Flat Cables are used as the two communications signal lines and the two communications power supply lines that connect the Master Board or a Repeater Unit with the Slave Units. •...

  • Page 191: Connectors

    Wiring for a CompoNet Network Section E-3 E-3-4 Connectors Round cable I or II Master Board Slave Unit/ Cable branches connections Repeater Unit T-branch Multidrop connections connections connections Open Type Open Type Commercially Open Type Connector Connector available relay Connector terminal Open Type Open Type...

  • Page 192: Connecting Nodes

    Wiring for a CompoNet Network Section E-3 Cable extension Flat Connector Socket + Flat Connector Plug Flat Connector Socket Flat Connector Socket Trunk line or sub-trunk line Trunk line or sub-trunk line Flat Connector Plug Flat Connector Plug E-3-5 Connecting Nodes This section explains the procedures to connect Units that compose a CompoNet network.

  • Page 193: Branching Communications Cables

    Wiring for a CompoNet Network Section E-3 When Using Flat Use a Flat Connector Plug to connect Flat Cable I or II to the Master Board. Cable I or II with Flat Connector Plugs • Flat Cable I with DCN4-BR4 Flat •...
  • Page 194 Wiring for a CompoNet Network Section E-3 Using Flat Cable I or II The communications cables are branched by a Flat Connector Socket and a with Flat Connector Flat Connector Plug. Sockets and a Flat Connector Plugs • Flat Cable I Attach a DCN4-BR4 Flat Connector I Plug which is already connected to Flat Cable to a DCN4-TR4 Flat Connector I Socket.

  • Page 195: E-3-7 Extending Communications Cables

    Wiring for a CompoNet Network Section E-3 Using Flat Cable I with Multidrop Connectors DCN4-BR4 Flat Connector I Plug DCN4-MD4 Multidrop Connector Slave or Repeater Unit Using Flat Cable II Flat Cables II does not support multidrop connections. E-3-7 Extending Communications Cables The cable length for the trunk line, sub-trunk lines, branch lines and sub- branch lines can be extended by up to 10 levels with the use of Flat Connectors.

  • Page 196: Connection Locations For Terminating Resistors

    Wiring for a CompoNet Network Section E-3 Flat Cable II Attach a DCN5-BR4 Flat Connector II Plug to a DCN5-TR4 Flat Connector II Socket having an internal stopper. DCN5-TR4 Flat DCN5-TR4 Flat Connector II Socket Connector II Plug E-3-8 Connection Locations for Terminating Resistors A Terminating Resistor must always be connected to and located at the opposite end of the trunk line or a sub-trunk line from the Master Board or a Repeater Unit.
  • Page 197 Wiring for a CompoNet Network Section E-3 Types and There are 2 types of Terminating Resistors: the connector type and the Characteristics of terminal-block type. Terminating Resistors Type Connector type Terminal-block type Name Terminating Resistor Model DCN4-TM4 DCN5-TM4 DRS1-T 121 Ω 121 Ω...
  • Page 198 Wiring for a CompoNet Network Section E-3 When the line is Flat Cable I DCN4-TM4 Terminating Resistor Flat Connector Plug DCN4-MD4 Multidrop Connector Communications connector of a Slave or Repeater Unit (an upstream port) Method 3 Connect a Terminating Resistor to the trunk line or a sub-trunk line cable.

  • Page 199: E-3-9 Connection Locations For Communications Power Supplies

    Wiring for a CompoNet Network Section E-3 E-3-9 Connection Locations for Communications Power Supplies This section explains the locations to connect the communications power supplies. Using Round Cable II, Example: Flat Cables I or II Flat Cable I or Flat Cable II 24-VDC communications power supply...

  • Page 200: Preparing And Mounting Flat Connectors On The Cables

    Preparing and Mounting Flat Connectors on the Cables Section E-4 * The communications power terminals must be connected to the BS+ and BS− terminals of the upstream port (PORT1) of the Repeater Unit. See Appendix E.5 for detailed wiring procedures for a communications power supply.
  • Page 201 Preparing and Mounting Flat Connectors on the Cables Section E-4 Precautions for Correct Use •A Flat Connector cannot be reworked once it has been prepared. •Hold the connector body to plug in or pull out the connector. •After connecting the connector, pull it lightly to confirm the connection is secured.

  • Page 202: Preparing Connectors For Round Cable Ii

    Preparing and Mounting Flat Connectors on the Cables Section E-4 Required Tools Name Appearance Model Purpose Special Tool DWT-A01 A pressure welding tool (Pliers) for DCN4-TR4 Flat Connector I Socket and a DCN4-BR4 Flat Connector I Plug Special Tool DWT-A02 A pressure welding tool (Pliers) for DCN5-TR4 Flat...
  • Page 203 Preparing and Mounting Flat Connectors on the Cables Section E-4 2. Setting the Cable Stopper Close the cover of the Flat Connector I Socket. Secure the hook. Press down the cable stopper until it clicks into place and does not return. Cable stopper 3.
  • Page 204 Preparing and Mounting Flat Connectors on the Cables Section E-4 5. Pressure-Welding the Connector Use a DWT-AT01 Special Tool (Pliers) to pressure-weld and connect the cable. 5-1 Align the center (see arrow) of the connector cover with the center of the pressure-welding block on the DWT-A01 Pliers.

  • Page 205: Preparing Connectors For Flat Cable I

    Preparing and Mounting Flat Connectors on the Cables Section E-4 E-4-2 Preparing Connectors for Flat Cable I Preparing and Names of Flat Connecter Socket components Mounting the DCN4- TR4 Flat Connector Cover Housing Sockets Cable labels (Black, blue/green, white, and red) Cable confirmation slot Black 1.
  • Page 206 Preparing and Mounting Flat Connectors on the Cables Section E-4 3. Mounting the Cable For T-branch connections 3-1 Confirm that the cable colors match the cable label colors. Place the cable in the cover. 3-2 lose the cover and sandwich the cable. Secure the hook. For Cable extension or connecting a Terminating Resistor Insert the tip of the cable all the way into the cable stopper in the cover.
  • Page 207 Preparing and Mounting Flat Connectors on the Cables Section E-4 Note Once it is attached, the housing cannot be removed from the cover. If you attempt to remove it forcibly, you may damage the connector. 5. Pressure-Welding the Connector Use a DWT-A01 Special Tool (Pliers) to pressure-weld and connect the cable. 5-1 Align the center (see arrow) of the connector cover with the center of the pressure-welding block on the DWT-A01 Pliers.
  • Page 208 Preparing and Mounting Flat Connectors on the Cables Section E-4 Preparing and Names of Flat Connector Plug components Mounting the DCN4- BR4 Flat Connector Cable labels (Flat cable: black, blue/green, white, and red) Plugs Black Lock lever 1. Cutting the Cable At the tip of the cable, cut the cable perpendicular to the cable length.
  • Page 209 Preparing and Mounting Flat Connectors on the Cables Section E-4 3. Pressure-Welding the Connector Use a DWT-A01 Special Tool (Pliers) to pressure-weld and connect the cable. 3-1 Align the center (see arrow) of the connector cover with the center of the pressure-welding block on the DWT-A01 Pliers.

  • Page 210: Preparing Connectors For Flat Cables Ii

    Preparing and Mounting Flat Connectors on the Cables Section E-4 E-4-3 Preparing Connectors for Flat Cables II Preparing and Names of Flat Connector Socket components Mounting the DCN5- TR4 Flat Connector Sockets Cover 1. Cutting the Cable (required only when the cable is extended or when a Terminating Resistor is connected) At the tip of the cable, cut the cable perpendicular to the cable length.
  • Page 211 Preparing and Mounting Flat Connectors on the Cables Section E-4 3. Mounting the Cable 3-1 Place the cable on the Connector with its white line facing upward, near the cover opening. (Top view) Connector Center of the Cable connector (Cover opening) White line For T-branch connections White line...
  • Page 212 Preparing and Mounting Flat Connectors on the Cables Section E-4 3-2 Hold the cable to prevent dislocation. Close the cover to sandwich the cable. Note When it is for cable extension or for connecting a Terminating Resistor, be sure to insert the cable tip all the way to the cable stopper in the cover. Be sertain the cable won't come out.
  • Page 213 Preparing and Mounting Flat Connectors on the Cables Section E-4 4-3 Confirm that the cable is properly pressure-welded as shown below: It must be locked. No space here. Preparing and Names of Flat Connector Plug components Mounting the DCN5- BR4 Flat Connector Plugs Cover 1.
  • Page 214 Preparing and Mounting Flat Connectors on the Cables Section E-4 2-2 Hold the Cable to prevent dislocation. Close the cover to sandwich the Cable. 3. Pressure-welding the Connector Use a DWT-A02 Special Tool (Pliers) to pressure-weld and connect the Cable. 3-1 Place the Connector on the pressure-welding block of the DWT-A02 Special Tool (Pliers).

  • Page 215: Wiring For Power Supply

    Wiring for Power Supply Section E-5 3-3 Confirm that the cable is properly pressure-welded as shown below. It must be locked. No space here. Wiring for Power Supply Operation of a CompoNet Network needs following power supplies. • Communications power supply: for communications with connected Units and for operations of internal elements of these Units.
  • Page 216 Wiring for Power Supply Section E-5 Communications I/O power power supply terminals supply terminals I/O power supply 24 VDC Master Board Round Cable I Overcurrent protection (current limit: 4 A) Communica- tions power When complying with UL standards, supply install a device to limit the current 24 VDC between the external power supply and the Unit to 4 A or less for the...

  • Page 217: Communications Power Supply Specifications

    E-5-1 Communications Power Supply Specifications The communications power supply must meet the following specifications. Commercially available power supply units can be used. An OMRON S82- series Power Supply Unit is recommended, however, as to supply communications power to CompoNet system.

  • Page 218: Wiring The Communications Power Supply

    Wiring for Power Supply Section E-5 Precautions for Correct Use With the Slave Units of network power supply type, the external I/O devices are also supplied power through the communications power supply connected to the Master Board or a Repeater Unit, via Flat Cables. Therefore, the output current of communications power supply must include the consumption current and the actual load current of the external I/O devices into calculation.

  • Page 219: E-5-3 Current Consumed By Slave Units And Repeater Units

    Wiring for Power Supply Section E-5 E-5-3 Current Consumed by Slave Units and Repeater Units See the CRT1 Series CompoNet Slave Units and Repeater Units Operation Manual, doc # W457. E-5-4 Communications Power Supply Connection Example Using round cable I When a round cable I is used, the communications power cannot be supplied through the communications cable.
  • Page 220 Wiring for Power Supply Section E-5 Using a Repeater Unit Master Board * When complying with UL standards, install a device to limit the current between the external power supply and the Unit to 4 A or Round Cable I less for the communications power supply.
  • Page 221 Wiring for Power Supply Section E-5 Not using a Repeater Unit Communications power supply Overcurrent connector Communications protection* power supply * When complying with UL standards, install a (current limit: 4 A) device to limit the current between the Master Board external power supply and the Unit to 4 A or less for the communications power supply.
  • Page 222 Wiring for Power Supply Section E-5 Using a Repeater Unit Communications power supply connector Overcurrent Communications protection* power supply (current limit: 4 A) Master Board Power * When complying with UL standards, install a supply device to limit the current between the external power supply and the Unit to 4 A or less for the communications power supply.
  • Page 223 Wiring for Power Supply Section E-5 Restrictions The following restrictions apply when supplying communications power through a round cable II, Flat Cable I, or Flat Cable II. • The communications power supply can be connected at only one location for the trunk line and one location each for the sub-trunk lines. •...
  • Page 224 Wiring for Power Supply Section E-5 • Provide a separate power supply each for the Master Board trunk line, for the upstream, and for the downstream trunk line of a Repeater Unit. Use separate power supplies for the trunk line and the sub-trunk line downstream from a Re- peater Unit.

  • Page 225: E-5-5 Precautions In Supplying Power To Slave Units

    Wiring for Power Supply Section E-5 Master Board Round cable I Communications power supply connector * When complying with UL standards, install a Overcurrent Shared communications device to limit the current between the protection* and I/O power supply Repeater external power supply and the Unit to 4 A or (current limit: 4 A) Unit less for the communications power supply.
  • Page 226 Multidrop Connectors have allowable current limits. The current flow on the points where these connectors are used must not exceed the limits. Connector name Model Allowable current limit Remark Communications 3G8F7-CRM21 5A (UL: 4A) Round cable I or II, Flat Cable power supply I or II 3G8F8-CRM21 connectors on...
  • Page 227 Wiring for Power Supply Section E-5 Voltage Drop Cable Voltage Drop Voltage drop (V) = Current flow (A) ×Cable conductor resistance (Ω/m) ×Cable length (m) ×2 If the voltage drop is too large and the power supplied to the farthest Slave Unit exceeds the allowable range, a Repeater Unit must be added and the power must be supplied from the Repeater Unit.

  • Page 228: E-5-6 Precautions When Providing The I/O Power Supply

    Wiring for Power Supply Section E-5 E-5-6 Precautions when Providing the I/O Power Supply When building a system, consideration must be given to the methods to supply the communications and the I/O power. The consideration includes not only the hardware elements, such as selecting power supplies and cables that confirm the allowable currents and the voltage drop, but also cost and software factors, such as system operation at power supply errors.

  • Page 229: Other Precautions

    Wiring for Power Supply Section E-5 E-5-7 Other Precautions Power Supply Errors A system can be stopped entirely if a power supply error occurs. When you want to avoid the full system stop to assure the system security, you may consider providing several power supplies in a network, and group the Slave Units with individual power supplies.
  • Page 230 Wiring for Power Supply Section E-5...
  • Page 231 Index CPNT_GetBitInData CPNT_GetBoardVersion Alarm Information CPNT_GetDriverVersion All Registered Slave Participation Standby Mode CPNT_GetInData All Registered Slave Unit Participating Flag CPNT_GetStatus Allowable Current CPNT_GetStatusEx API function CPNT_IsExistBoard Asynchronous access CPNT_Open CPNT_PeekExplicit CPNT_ReceiveExplicit CPNT_RefreshPCWDTTimer Basic status group CPNT_RegBDWDTNotifyMessage Bit IN Data CPNT_RegReceiveExplicitNotifyMessage Bit OUT Data CPNT_RegRESETNotifyMessage Board ID...
  • Page 232 Index Flags of Interrupt from Board to PC Open Type Connector Flags of Interrupt from PC to Board OPEN_SYSTEM Flat Cable I OPEN_SYSTEMEX Flat Cable II Optimizing Communications Cycle Flat Connector Plug Flat Connector Socket Participated Slave Unit Identity Table Participation Flag I/O power supply Participation flag...
  • Page 233 Index Terminating Resistor Using Different Cable Types Voltage Drop Word IN Data Word OUT Data...
  • Page 234 Index...
  • Page 235 Revision History A manual revision code appears as a suffix to the catalog number on the front cover of the manual. Cat. No. W485-E1-02 Revision code The following table outlines the changes made to the manual during each revision. Page numbers refer to the previous version.
  • Page 236 Revision History...

This manual is also suitable for:

3g8f8-crm21

Table of Contents