1 / 61

How to Develop CC-Link Compatible Products

How to Develop CC-Link Compatible Products. CLPA-Europe 2011. Action: Register as a CLPA member (Regular or higher). CLPA Regular Membership is required in order to develop CC-Link compatible products.

mya
Download Presentation

How to Develop CC-Link Compatible Products

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. How to Develop CC-Link Compatible Products CLPA-Europe 2011

  2. Action: Register as a CLPA member(Regular or higher) CLPA Regular Membership is required in order to develop CC-Link compatible products. CC-Link Specifications (Protocol, Implementation and Profile) will be provided free of charge if you register as a CLPA member.

  3. Action:Decide type of product Determine the type of product to be developed based on amount of data to be handled and functionality required. DRIVER S/W REMOTEI/O REMOTEDEVICE INTELLIGENT DEVICE MASTER/LOCAL

  4. Action:Decide type of product Determine the type of product to be developed based on amount of data to be handled and functionality required. DRIVER S/W REMOTEI/O REMOTEDEVICE INTELLIGENT DEVICE MASTER/LOCAL A device that can only use bit data A device that can use bit and word data A device that can perform 1:n cyclic transmission and transient transmission with the master station Master: A device that has the control information (parameters) and controls the entire network. One per network Local: A device that can perform 1:n cyclic transmission and transient transmission with the master and other local stations Driver S/W Software that runs on the user application in order to access the network circuit

  5. Action: Choose method of development Embedded I/O adapter User’s manual and Embedded I/O adapter MFP2N Data Book or MFP2AN Data Book and MFP2N or MFP2AN / Comms. ASIC Use “Embedded adapter” Use dedicated ASIC (MFP2N, MFP2AN) CC-Link interface board Q50BD-CCV2 and data-book MFP3N Data Book and MFP3N /Comms. ASIC or gateway maker datasheet and network controller Use dedicated ASIC (MFP3N), or third party gateway DRIVER S/W Master and Local station H/W and S/W design specification, MFP1N/ Comms. ASICDual-port interface G/A or PCI bus G/A / Comms. ASIC Use CC-Link V2 interface board (Q50BD-CCV2) Use ASIC (MFP1N) & Object Code REMOTEI/O REMOTEDEVICE INTELLIGENT DEVICE MASTER/LOCAL Software for CC-Link ASIC (Source code /LicenseMaster/Local and Intelligent device stations software source code disclosure specification. MFP1N Data book (Source disclosure edition) and MFP1N /Comms. ASIC Use ASIC (MFP1N) & Source Code From sample code & documents Documents, Materials/Note

  6. Action: Development Prepare documents and materials according to type of station and method of development you choose Purchase materials(embedded adapter, MFP, parts etc.) Purchase manual,data book Software licenseagreement CC-Link Partner Association supports your development

  7. Action:Take conformance test Conformance test must be taken when development is complete Connectibility Aging test Noise immunity proofed proofed proofed

  8. Action:Release Products passing the conformance test can be released and marketed as CC-Link compatible products CC-Link logo can be printed on products and / or documents CC-Link compatible products can be promoted on CLPA web pages worldwide - free of charge CC-Link compatible products can be feature in documentation / catalogues published by CLPA - free of charge

  9. Action:Release Action:Pass Action:Take conformance test Action: Development Action: Choose method of development Action:Decide type of product Action: Register as a CLPA member(Regular or higher) Action: Development Review Action: Development

  10. In-house CC-link development considerations • Have we the in-house • development expertise? Driver Software for PCI interface board Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device YES YES YES YES YES NO NO NO NO NO Consider ASIC Consider gateway Can we manage certification, Maintenance & future support? Are projected volumes high Enough to meet target ROI? • Do we only need CC-Link • connectivity? Have we the development capacity?

  11. Development of Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device …Comparison of CC-Link Version 1.1 and 2.0 Version 1.1 and Version 2.0 are both current. V2.0 was added to allow more data per transmission *See also CC-Link Specification (Overview Protocol) BAP-05026-J ** Consult your gateway supplier

  12. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device Please push a Button

  13. Development of Driver Software for PCI interface board Driver Software for PCI interface board Remote Device Remote Device Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device There are three methods to develop CC-Link Remote I/O products. You can select a suitable one depending on schedule, target cost and capacity of data you need. CC-Link Version 1.1

  14. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device Block diagram of Embedded Adapter PW CIRCUIT COMMS ASIC I/O INTERFACE CIRCUIT I/O 0 ~I/O F CRYSTAL LED STATION NO.,BAUD RATE SWITCH Media I/F (RS485) …by using pcb mounted Embedded Adapter CC-Link Remote I/O is easily and quickly developed by using Embedded I/O Adapter which includes CC-Link interface, I/O interface, power circuit, etc. Only suitable for PCB mounting!!!

  15. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device 16 or 32 points are controlled by ultra compact size. 53 or 85 (W), 22 (H), 31.5 (D) mm. Two Embedded adapters can be mounted side by side and implemented in one board. Pin header is equipped for connecting to outer circuit. Any connector or terminal is usable. Has potential to reduce development costs and het product to market sooner. … by using pcb mounted Embedded Adapter Feature

  16. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device AJ65MBTL1N-16D 16 points DC input adapter (sink type) AJ65MBTL1N-32D 16 points DC input adapter (sink type) AJ65MBTL1N-16T 16 points transistor output adapter (sink type AJ65MBTL1N-32T 16 points transistor output adapter (sink type) AJ65MBTL1N-16DT 8 points DC input, 8 points transistor output adapter (sink type) … by using pcb mounted Embedded Adapter Lineup

  17. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device MFP2N HARDWARELOGIC I/O TYPE SETTING MONITORINGTIMER Retrieves the bit information from the reception data and stores it in the output buffer. Sends the bit information from the input buffer to the polling response data OUTPUTBUFFER CLOCKDIVIDING CIRCUIT OSCILLATOR I/O 0 ~I/O 1F HDLC I/O PIN CONTROL I/O INTERFACECIRCUIT INPUTBUFFER DPLL I/O LED STATION NO. SWITCHBAUD RATE SETTING MEDIA INTERFACE(RS-485) …by Using ASIC (MFP2N, MFP2AN) Remote I/O can be developed without detailed knowledge of CC-Link protocol by using a dedicated communication ASIC type MFP2N or MFP2AN, that implements theCC-Link protocol. H/W DESIGN ONLY!!!

  18. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device Protocol is implemented into 100 pin QFP package (14 mm square) Up to 32 points can be controlled Various combinations of input and / or outputs can be realised …by using ASIC (MFP2N) I/O Type Feature (MFP2N)

  19. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device Protocol is implemented into 80 pin QFP package (12 mm square) Up to 16 points can be controlled Various combination of input and / or output can be realised … for compact I/O by using ASIC (MFP2AN) Feature (MFP2AN) I/O Type

  20. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device OSCILLATOR LED SWITCHES MFP2 I/O INTERFACE …by using either ASIC (MFP2N or MFP2AN) Example of Implementation

  21. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device …by using ASIC (MFP2N, MFP2AN) Documents Dedicated Communication ASIC Dedicated communication ASIC is supplied through Mitsubishi Industrial Automation products sales network.Please ask their our salesman about pricing and delivery time.

  22. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device Product Name Model Name Manufacture Photocoupler HCPL-7720 500E Avago Technologies HCPL-0720 500E HCPL-2611 500E Photocoupler Avago Technologies HCPL-M611 500E Photocoupler PS9661L3-E3 NEC Electronics PS9117-F3-A …by using LSI (MFP2N, MFP2AN) Recommended Parts When communication line is insulated

  23. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device Contact: Any questions about development of CC-Link compatible products CC-Link Partner Association Europe partners@clpa-europe.com

  24. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device Please push a Button Or click for reference section

  25. Development of Driver Software for PCI interface board Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device Data capacity handled by a Remote device, can be changed depending on number of occupied station. 16 points in the latter half are reserved by the system. Version 1.1 data capacity . Decide number of occupied stations for the device, according to data size you need. CC-Link Version 1.1

  26. Development of Driver Software for Q80BD-J61BT11N Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device Data Type Number Of Occupied Stations Note 1 station 2 stations 3 stations 4 stations Master=>Slave bits Up to 128 points Up to 384 points Up to 640 points Up to 896 points 16 points are reserved by the system Up to 128 points Up to 384 points Up to 640 points Up to 896 points Slave=>Master bits Up to 32 words Up to 64 words Up to 96 words Up to 128 words Slave=>Master words Up to 32 words Up to 64 words Up to 96 words Up to 128 words Slave=>Master words Data capacity handled by a Remote device, can be changed depending on number of occupied station. 16 points in the latter half are reserved by the system. Version 2.0 data capacity . Decide number of occupied stations for the device, according to data size you need. CC-Link Version 2.0

  27. Development of Driver Software for PCI interface board Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device There are three methods to develop CC-Link Remote Device products. You can choose one of them, depending on schedule, target cost and capacity of data you need.

  28. Development of Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device MFP3N Set according to the station information pattern Number ofI/O pointsNumber ofoccupiedstationsData length HARDWARELOGIC MONITORINGTIMER Retrieves the bit and word information from the reception data and stores it in the receive buffer. Sends the bit and word information from the send buffer to the transmission data. RECEIVEBUFFER *1 CLOCKDIVIDING CIRCUIT OSCILLATOR CPU HDLC SENDBUFFER *1 DPLL ADDRESS 7 MEMORY DATA 8 or 16 CONTROL STATION NO. SWITCHBAUD RATE SETTING PHYSICAL MEDIUM INTERFACE RS 485 *1 SRAM or equivalent A remote device, that handles both bit and word data. Can be developed without detailed knowledge of CC-Link protocol by using a dedicated communication ASIC type MFP3Nthat implements the CC-Link protocol. S/W development is needed in addition to H/W development

  29. Development of Driver Software for PCI interface board Remote Device Master/Local, Intelligent Device Protocol is implemented into a 100 pin QFP package (14 mm square) Up to 128 points of I/O and 32 words data can be controlled (4 stations occupied) S/W accessing MFP3N is developed according to flow chart in data book Remote I/O …by using MFP3N Feature (MFP3N)

  30. Development of Driver Software for PCI interface board Remote Device Master/Local, Intelligent Device OSCILLATOR SWITCHES MFP3N CPU Remote I/O …by using MFP3N Example of Implementation

  31. Development of Driver Software for PCI interface board Remote Device Master/Local, Intelligent Device Remote I/O …by using MFP3N Documents Dedicated Communication ASIC Dedicated communication ASIC is supplied through Mitsubishi Electric products sales network.

  32. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device Product Name Model Name Manufacture Photocoupler HCPL-7720 500E Avago Technologies HCPL-0720 500E HCPL-2611 500E Photocoupler Avago Technologies HCPL-M611 500E Photocoupler PS9661L3-E3 NEC Electronics PS9117-F3-A …by using MFP3N Recommended Parts When communication line is insulated

  33. The Anybus-CC software interface is network protocol independent. This allows the host application to support all major networking systems using the same software driver, without loss of functionality or performance. Multi-network connectivity in one development step, with instant access to CC-Link (V1.1 or 2.0) other fieldbuses, Ethernet, wireless and serial networks Continuous technology maintenancewhen communication standards change to support for new upcoming network technologies without the need to change the automation device Development time 1-3 months for multiple network with fast ROI Development of Driver Software for Q80BD-J61BT11N Remote Device Master/Local, Intelligent Device Remote I/O …by using Anybus-CC embedded communication module Software Application interface (API) • www.anybus.com

  34. Development of Driver Software for Q80BD-J61BT11N Remote Device Master/Local, Intelligent Device Remote I/O provides comprehensive development tools to get you quickly up and running with your development. Anybus-CC Development Tools • Starter-kit • Two Anybus-CC modules • Serial RS232 carrier board • Sample CF-connectors • CD with Anybus-CC documentation and software • Applications Driver • Software driver implementing the Anybus-CC interface (just add data and commands) • Supports parallel and serial interface • Portable to any hardware and software platform • Sample application Software • Emulates a motor drive application with control (I/O data) and parameters • Uses the application driver to interface the Anybus-CC • www.anybus.com

  35. Development of Driver Software for PCI interface board Remote Device Master/Local, Intelligent Device Remote I/O …by using Network Controller (netX) Remote I/O can bedeveloped by usingnetX Network Controller which implements the CC-Link protocol. The netX 5 is one of four (4) types of network controller modules on a single chip (netX 50 netX 100 netX 500) http://www.hilscher.com/netx.html

  36. Development of Driver Software for PCI interface board Remote Device Master/Local, Intelligent Device Remote I/O Contact: Any questions about development of CC-Link compatible products CC-Link Partner Association Europe partners@clpa-europe.com

  37. Development of Driver Software for PCI interface board Remote Device Remote I/O Master/Local, Intelligent Device Please push a Button Or click for reference section

  38. Development of Driver Software for PCI interface board Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device There are two methods to develop CC-Link Master stations, standby masters, local stations and intelligent device stations. You can choose one of them, depending on schedule and target cost needed.

  39. Development of Driver Software for PCI interface board Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device HOST DEVICE CC-LINK INTERFACE BOARD OSCILLATOR WATCH-DOGTIMER COMMUNIC.CONTROL RECEIVEBUFFER SENDBUFFER I/O PORT REGISTER DMAC CPU OSCILLATOR HDLC DUELPORTRAM CLOCKDIVIDING CIRCUIT BUS CONTROL BUS INTERFACE HARDWARE AND SOFTWAREOF PARTNER DEVICE DPLL EEROM ROM ERRORDETECTIONCIRCUIT RAM STATION NO. SWITCHBAUD RATE SETTING MEDIUM INTERFACE RS 485 …of using Q50BD-CCV2 embedded interface board Master/ Local or Intelligent device, which handles message data and / or controls CC-Link network, can be developed by using an Interface board that implements CC-Link protocol and network control.

  40. Development of Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device …of using Q50BD-CCV2 embedded interface board Driver S/W development is needed in addition to HW development License agreement is unnecessary

  41. Development of Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device Protocol and interface is implemented on a mother board Firmware to interface with the Q50DB-CCV2 is developed using the procedures in the Built-in Interface Board data book (SH(NA)080700ENG-D) …of using Q50BD-CCV2 embedded interface board Feature Q50BD-CCV2

  42. Development of Driver Software for PCI interface board Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device HOST DEVICE CC-LINK INTERFACE MFP1N OSCILLATOR SENDBUFFER I/O PORT REGISTER COMMUNIC.CONTROL RECEIVEBUFFER WATCH-DOGTIMER DMAC CPU OSCILLATOR HDLC DUELPORTRAM BUS CONTROL CLOCKDIVIDING CIRCUIT BUS INTERFACE DPLL HARDWARE AND SOFTWAREOF OTHER PARTNER DEVICE EEROM ROM ERRORDETECTIONCIRCUIT RAM STATION NO. SWITCHBAUD RATE SETTING MEDIUM INTERFACE RS 485 …of using MFP1N Master/ Local or Intelligent device, which handles message data and / or controls CC-Link network, can be developed by using MFP1Nthat implements CC-Link protocol and network control. S/W development is needed in addition to H/W development

  43. Development of Driver Software for PCI interface board Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Protocol is implemented into a 100 pin QFP package (20 mm x 14 mm square) Firmware to control MFP1N is developed,based on either Object or Source code There are some differences between two methods in order to develop device …of using MFP1N Feature MFP1N

  44. Development of Driver Software for PCI interface board Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device HOST INTERFACE Need to develop(Essential task) TRANSIENTTRANSMISSION NETWORK CONTROL Need to develop(Optional task) INITIALISATION OS, TIMER UNIQUE FUNCTION MESSAGE CONTROL Disclosedsource code CYCLIC TRANSMISSION MFP1N DRIVER …of using MFP1N Task Structure INCLUDED IN OBJECT

  45. Development of Driver Software for PCI interface board Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device …of using MFP1N Task Structure

  46. Development of Driver Software for PCI interface board Remote Device Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device Master/Local, Intelligent Device …of using MFP1N and Object Code License Agreement S/W license agreement (MFP1N Technology Agreement ) is required in order to develop Master/Local or Intelligent device using MFP1N and Object code. Object code is delivered in the form of ROM or file, and it is royalty free.

  47. Development of Driver Software for PCI interface board Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device …of using MFP1N and Object Code Documents Choose documents depending on type of station and arrangement used. Master/Local (dual port memory interface) Dedicated Communication ASIC

  48. Development of Driver Software for PCI interface board Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device …of using MFP1N and Object Code Specified Parts Specified MPU should be used for interface to the MFP1N Same recommended parts as Remote I/O are needed (Filter, RS485 Driver, Crystal oscillator, etc.) Recommended Parts

  49. Development of Driver Software for PCI interface board Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device …of using MFP1N and Source Code License Agreement S/W License agreement (MFP1N Technology Agreement ) is required in order to develop Master/Local or Intelligent device using MFP1N and Source code.

  50. Development of Driver Software for PCI interface board Remote Device Remote I/O Remote I/O Master/Local, Intelligent Device …of using MFP1N and Source Code Specified Parts Any MPU can be chosen and used for interface to the MFP1N Same recommended parts as Remote I/O are needed (Filter, RS485 Driver, Crystal oscillator, etc.) Recommended Parts

More Related