How to Develop CC-Link Compatible Products
description
Transcript of How to Develop CC-Link Compatible Products
Basic flow from development to release
How to Develop CC-Link Compatible Products
CLPA-Europe 2011
Basic flow from development to release
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.
Basic flow from development to release
Determine the type of product to be developed based on amount of data to be handled and functionality required.
Action: Decide type of product
REMOTEI/O
REMOTEDEVICE
INTELLIGENT DEVICE
MASTER/LOCAL
DRIVER S/W
Basic flow from development to release
Determine the type of product to be developed based on amount of data to be handled and functionality required.
Action: Decide type of product
REMOTEI/O
REMOTEDEVICE
INTELLIGENT DEVICE
MASTER/LOCAL
DRIVER S/W
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
Local:
A device that can perform
1:n cyclic transmission and transient transmission
with the master and other local
stations
Master:
A device that has the control
information (parameters) and controls
the entire network. One per network
Driver S/W
Software that runs on the user
application in order to access
the network circuit
Basic flow from development to release
CC-Link interface board Q50BD-CCV2 and data-bookUse CC-Link V2 interface board
(Q50BD-CCV2)
Action: Choose method of development
From sample code & documents
Use “Embedded adapter”
Use dedicated ASIC (MFP2N, MFP2AN)
Use dedicated ASIC (MFP3N),
or third party gateway
Use ASIC (MFP1N) & Object Code
Use ASIC (MFP1N) & Source Code
MFP3N Data Book and MFP3N / Comms. ASIC or
gateway maker datasheet and network controller
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
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
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
REMOTEI/O
REMOTEDEVICE
INTELLIGENT DEVICE
MASTER/LOCAL
DRIVER S/W
Documents, Materials/Note
Basic flow from development to release
Action: Development
Prepare documents and materials according to type of station and method
of development you choose
Purchase manual,data book
Software licenseagreement
Purchase materials(embedded adapter, MFP,
parts etc.)
CC-Link Partner Association
supports your development
Basic flow from development to release
Action: Take conformance test
Conformance test must be taken when development is complete
Connectibilit
y
Noise immunity
Aging test
proofed
proofed
proofed
Basic flow from development to release
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
Basic flow from development to release
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: DevelopmentAction: Development
Review
Basic flow from development to release
NONO
NONO
NONO
NONO
NONO
YESYES
YESYES
YESYES
YESYES
Consider ASIC Consider gateway
In-house CC-link development considerations
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote I/O
Have we the in-house development expertise?
Are projected volumes high Enough to meet target ROI?
Do we only need CC-Link connectivity?
Have we the development capacity?
Can we manage certification, Maintenance & future support?
YESYES
Basic flow from development to release
Device type I/O points
Registers RWr/RWw
Extended cyclic settings
Data handling
V1.1 or V2.0*
ASIC or gateway**
Remote I/O station
<2048 256/256 No Bit data only
V1.1 MFP2N
MFP2AN
Remote I/O station
<8192 2048/2048 Yes Bit data only
V1.1 MFP3N
Remote device station
<8192 2048/2048 Yes Bit and word data
V2.0 MFP3N
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
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Remote Device
Master/Local, Intelligent Device
…Comparison of CC-Link Version 1.1 and 2.0
Driver Softwarefor PCI interface board
Remote I/O
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Please push a Button
Basic flow from development to release
Development of
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
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Method
ContentsUse of Embedded
Adapter or gatewayUse of Communication
ASIC MFP2NUse of Communication
ASIC MFP2AN
I/O Points Max 32 points Max. 32 points Max. 16 points
Category PCB pattern design H/W design H/W design
Specified Parts
All specified parts are already implemented
Crystal oscillator,RS485 driver,Zener diode,
Filter etc.
Crystal oscillator,RS485 driver,Zener diode,
Filter etc.
Timescale ShortLonger compared
to Embedded Adapters/gateways
Longer compared to Embedded Adapter/gateways
Note
Effective to shortendevelopment period,
and to develop various products
Suitable for development of remote I/O
Suitable for development of compact Remote I/O
Basic flow from development to release
Development of
CC-Link Remote I/O is easily and quickly developed by using Embedded I/O Adapter which includesCC-Link interface, I/O interface, power circuit, etc.
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Block diagram of Embedded Adapter
COMMS ASIC
CRYSTAL
LEDSTATION NO.,
BAUD RATE SWITCHMedia I/F(RS485)
I/O
IN
TE
RF
AC
E C
IRC
UIT
PW
CIR
CU
IT
I/O 0 ~I/O F
Only suitable for PCB mounting!!!
…by using pcb mounted Embedded Adapter
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
… by using pcb mounted Embedded Adapter
Feature
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 terminalis usable.
Has potential to reduce development costs and het product to market sooner.
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
… by using pcb mounted Embedded Adapter
Lineup
AJ65MBTL1N-16D16 points DC input adapter (sink type)
AJ65MBTL1N-16T16 points transistor output adapter (sink type
AJ65MBTL1N-16DT8 points DC input, 8 points transistor output adapter(sink type)
AJ65MBTL1N-32D16 points DC input adapter (sink type)
AJ65MBTL1N-32T16 points transistor output adapter (sink type)
Basic flow from development to release
I/O 0 ~I/O 1F
I/O LEDSTATION NO. SWITCHBAUD RATE SETTING
MEDIA INTERFACE(RS-485)
I/O
IN
TE
RF
AC
EC
IRC
UIT
I/O
PIN
CO
NT
RO
L
HARDWARELOGICI/O
TYPE SETTING
OU
TP
UT
BU
FF
ER
INP
UT
BU
FF
ER
DPLL
HDLCCLOCK
DIVIDINGCIRCUIT
MONITORINGTIMER
OSCILLATOR
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
MFP2N
Development of
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.
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
H/W DESIGN ONLY!!!
…by Using ASIC (MFP2N, MFP2AN)
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
…by using ASIC (MFP2N)
Feature (MFP2N)
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
Input points
Output points
1 8 points ----
2 ---- 8 points
3 16 points ---
4 --- 16 points
5 8 points 8 points
6 32 points ---
7 --- 32 points
8 16 points 16 points
I/O Type
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
… for compact I/O by using ASIC (MFP2AN)
Feature (MFP2AN)
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
1.0
14.0± 0.2
16.0± 0.2
16.0
±0.
2
14.0
±0.
2
1.0 0.22 0.05+0.04-
M0.10 0.5
7576
5150
2625
1001
2MFPPC96003N
Lot No.
0.10
1.45
0.5± 0.2
0.17
0.03
+0.
07-
1.0± 0.2
Input points
Output points
1 8 points ----
2 ---- 8 points
3 16 points ---
4 --- 16 points
5 8 points 8 points
I/O Type
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Example of Implementation
LED
SWITCHESMFP2
I/O INTERFACE
OSCILLATOR
…by using either ASIC (MFP2N or MFP2AN)
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
…by using ASIC (MFP2N, MFP2AN)
Documents
Order Model Name Package Unit Manufacturer
MFP2N (PC96003N)
A6GA-CCMFP2NN60F
A6GA-CCMFP2ANN300FContains 60 pieces Contains 300 pieces Purchase from
Mitsubishi ElectricMFP2AN
(PC96007N)A6GA-CCMFP2NN60F
A6GA-CCMFP2AN300FContains 60 pieces Contains 300 pieces
Document Name Document No Contact
MFP2N CC-Link Remote I/O station communication LSI MFP2N
SH(NA)-80622ENG Purchase from Mitsubishi
ElectricMFP2AN CC-Link Remote I/O station communication LSI MFP2AN
SH(NA)-80623ENG
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.
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
…by using LSI (MFP2N, MFP2AN)
Recommended
Parts
Product Name Model Name Manufacture
Filter ZCYS51R5-M3PAT01
MCT7050-A401 TDK
Sinka Japan
RS485 Driver SN75ALS181NS Texas Instruments
Crystal Oscillator DS0751SB 80MHz Daishinku Corp.
Zener DiodeRD6.2Z-T2B-A
HZU6.2ZTRF-E
NEC Electronics
Renesas Technology
When communication line is insulated Avago Technologies
HCPL-2611 500EPhotocoupler
HCPL-M611 500E
Avago Technologies
Manufacture
HCPL-0720 500E
HCPL-7720 500EPhotocoupler
Model NameProduct Name
PhotocouplerPS9661L3-E3
PS9117-F3-ANEC Electronics
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Contact:Any questions about development of CC-Link compatible products
CC-Link Partner Association Europe
Basic flow from development to release
Development of
Please push a Button
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Or click for reference section
Basic flow from development to release
Development of
Remote I/O
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
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.
Data Type
Number Of Occupied Stations
Note1 station 2 stations 3 stations 4 stations
Remote input bits (S=>M) 32 points 64 points 96 points 128 points16 points are reserved by the system
Remote output bits (M=>S) 32 points 64 points 96 points 128 points
Remote Register
Words
Master=>Slave 4 words 8 words 12 words 16 words
Slave=>Master 4 words 8 words 12 words 16 words
CC-Link Version 1.1
Basic flow from development to release
Development of
Remote I/O
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor Q80BD-J61BT11N
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
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
Up to 32 words
Up to 32 words
Up to 128 words
Up to 96 wordsUp to 64 words
Up to 128 words
Up to 96 wordsUp to 64 words
Up to 896 points
Up to 640 points
Up to 384 points
Up to 128 pointsSlave=>Master bits
16 points are reserved by the system
Up to 896 pointsUp to 640 pointsUp to 384 pointsUp to 128 pointsMaster=>Slave bits
4 stations3 stations2 stations1 station
NoteNumber Of Occupied Stations
Data Type
Slave=>Master words
Slave=>Master words
Basic flow from development to release
Development of
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.
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Method
ContentsUse of MFP3N ASIC
Use of embedded communication
module
Use of netX firmware
and stack
Category H/W & S/W design H/W design H/W & S/W design
Specified Parts
Crystal oscillator,RS485 driver,Zener diode,
Filter etc.
Not required (included in embedded communication
module)
Crystal oscillator,RS485 driver,Zener diode,
Filter etc.
Supplier From Mitsubishi Electric From third-party supplier From third-party supplier
Remote I/O
Basic flow from development to release
Development of
Remote I/O
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
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 MFP3N that implements the
CC-Link protocol.S/W development is needed in addition to H/W development
*1 SRAM or equivalentSTATION NO. SWITCHBAUD RATE SETTING
PHYSICAL MEDIUM INTERFACE RS 485
DPLL
HDLCCLOCK
DIVIDINGCIRCUIT
MONITORINGTIMER
OSCILLATOR
MFP3N
ME
MO
RY
CP
U
HARDWARELOGIC
Set according to the station information pattern
RE
CE
IVE
BU
FF
ER
*1
SE
ND
BU
FF
ER
*1
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.
Number ofI/O pointsNumber ofoccupiedstationsData length
ADDRESS 7
DATA 8 or 16
CONTROL
Basic flow from development to release
Development of
Remote I/O
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
…by using MFP3N
Mainprocedure
Time over?
Read refreshdata
RX、RWr informationHold/Clear procedure
Change setting value of time overNormal time value => Initial time value
Main procedureof device side
Write refreshdata
Yes
No
Example of Flow chart
Feature (MFP3N)
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 Device
Basic flow from development to release
Development of
Example of Implementation
SWITCHES
MFP3N
OSCILLATOR
CPU
…by using MFP3N
Remote I/O
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Basic flow from development to release
Development of
Documents
Dedicated
Communication
ASIC
Document Name Document No. Contact
MFP3N Data Book
CC-Link Remote Device station Communication
LSI MFP3NSH(NA)-080624ENG
Purchase from Mitsubishi
Electric
Order Model Name Package Unit Contact
MFP3N (PC96004N)
A6GA-CCMFP3NN60F Contains 60 pieces Purchase from Mitsubishi
ElectricA6GA-CCMFP3NN300F Contains 300 pieces
Dedicated communication ASIC is supplied through Mitsubishi Electric products sales network.
…by using MFP3N
Remote I/O
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Basic flow from development to release
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
…by using MFP3N
Recommended
Parts
Product Name Model Name Manufacture
Filter ZCYS51R5-M3PAT01
MCT7050-A401 TDK
Sinka Japan
RS485 Driver SN75ALS181NS Texas Instruments
Crystal OscillatorKC7050B80 Series
FX0-37FNB; 80MHzKyocera Kinseki Corp.
Zener DiodeRD6.2Z-T2B-A
HZU6.2ZTRF-E
NEC Electronics
Renesas Technology
When communication line is insulated Avago Technologies
HCPL-2611 500EPhotocoupler
HCPL-M611 500E
Avago Technologies
Manufacture
HCPL-0720 500E
HCPL-7720 500EPhotocoupler
Model NameProduct Name
PhotocouplerPS9661L3-E3
PS9117-F3-ANEC Electronics
Basic flow from development to release
Development of
Remote I/O
Master/Local, Intelligent Device
Driver Softwarefor Q80BD-J61BT11N
Remote Device
• 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
…by using Anybus-CC embedded communication module
01011011010101100110011010010101101010110011010100010110110101011001100110101011011010101100110011010011100101011010110101010
Data from Network
01011011010101100110011010010101101010110011010100010110110101011001100110101011011010101100110011010011100101011010110101010
Data to Network
Cyclic Data
Cyclic Data
Acyclic Request
Acyclic Response
Acyclic Handling
Diagnostic Handling
Alarm
Diagnostics
Net
wo
rk
Anybus-CC
01011011010101100110011010010101101010110011010100010110110101011001100110101011011010101100110011010011100101011010110101010
Data from Network
01011011010101100110011010010101101010110011010100010110110101011001100110101011011010101100110011010011100101011010110101010
Data to Network
Cyclic Data
Cyclic Data
Acyclic Request
Acyclic Response
Acyclic Handling
Diagnostic Handling
Alarm
Diagnostics
Net
wo
rk
Anybus-CCSoftware Application interface (API)
www.anybus.com
Basic flow from development to release
• 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
Anybus-CC Development Tools
Development of
Remote I/O
Master/Local, Intelligent Device
Driver Softwarefor Q80BD-J61BT11N
Remote Device
www.anybus.com
provides comprehensive development tools to get you quickly up and running with your development.
Basic flow from development to release
Development of
…by using Network Controller (netX)
Remote I/O can bedeveloped by usingnetX Network Controller whichimplements theCC-Link protocol.
The netX 5 is one of four (4) types of network controllermodules on a single chip(netX 50netX 100netX 500)
http://www.hilscher.com/netx.html
Remote I/O
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Basic flow from development to release
Development of
Contact:Any questions about development of CC-Link compatible products
CC-Link Partner Association Europe
Remote I/O
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Basic flow from development to release
Development of
Please push a Button
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote I/O
Remote Device
Or click for reference section
Basic flow from development to release
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.
Method
ContentsUse of Q50BD-CCV2
Interface boardUse of MFP1N
Category Compact board 70 x80mm Object development method
CommunicationSimple interface with user circuit
board using general purpose bus interface
Use of a dual port RAM enables easy
communication between network and user application
circuits
Supplier From Mitsubishi Electric From Mitsubishi Electric
Development of
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote I/O
Basic flow from development to release
Development of
Remote I/O
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Master/Local, Intelligent Device
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.
…of using Q50BD-CCV2 embedded interface boardB
US
IN
TE
RF
AC
E
STATION NO. SWITCHBAUD RATE SETTING
STATION NO. SWITCHBAUD RATE SETTING
MEDIUM INTERFACE RS 485
MEDIUM INTERFACE RS 485
DPLLDPLL
HDLCHDLC
CL
OC
KD
IVID
ING
CIR
CU
IT
CL
OC
KD
IVID
ING
CIR
CU
IT
OS
CIL
LA
TO
RO
SC
ILL
AT
OR
OSCILLATOROSCILLATOR
ROMROM
RAMRAM
EEROMEEROM
BU
S C
ON
TR
OL
RECEIVEBUFFER
SENDBUFFER
DMACDMAC
WATCH-DOG
TIMER
WATCH-DOG
TIMER
ERRORDETECTION
CIRCUIT
ERRORDETECTION
CIRCUIT
I/O PORT REGISTER
COMMUNIC.
CONTROL
HA
RD
WA
RE
AN
D S
OF
TW
AR
EO
F P
AR
TN
ER
DE
VIC
E
DU
EL
PO
RT
RA
M
DU
EL
PO
RT
RA
M
CPUCPU
HOST DEVICE
CC-LINK INTERFACE BOARD
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote 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 isunnecessary
Basic flow from development to release
Development of
Remote I/O
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Master/Local, Intelligent Device
…of using Q50BD-CCV2 embedded interface board
Feature Q50BD-CCV2
Protocol and interfaceis implemented on a mother board
Firmware to interface with the Q50DB-CCV2is developed using the procedures in theBuilt-in Interface Board data book (SH(NA)080700ENG-D)
Basic flow from development to release
Development of
Remote I/O
…of using MFP1N
Master/ Local or Intelligent device, which handlesmessage 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
MFP1NB
US
IN
TE
RF
AC
E
STATION NO. SWITCHBAUD RATE SETTING
MEDIUM INTERFACE RS 485
DPLL
HDLC
CL
OC
KD
IVID
ING
CIR
CU
IT
OS
CIL
LA
TO
R
OSCILLATOR
ROM
RAM
EEROMB
US
CO
NT
RO
L
RECEIVEBUFFER
SENDBUFFER
DMAC
WATCH-DOG
TIMER
ERRORDETECTION
CIRCUIT
I/O PORT REGISTER
COMMUNIC.CONTROLH
AR
DW
AR
E A
ND
SO
FT
WA
RE
OF
OT
HE
R P
AR
TN
ER
DE
VIC
E
DU
EL
PO
RT
RA
M
CPU
HOST DEVICE
CC-LINK INTERFACE
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
…of using MFP1N
Feature MFP1N
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
METHOD
CONTENTS
OBJECT CODE
SOURCE CODE
Host side CPU Need No need
Host side S/W Need 8 points
I/F or bus G/ADual port I/F
G/ANo need
MPU Specified Any
Parts Many Less
Difficulty Easy Not easy
Cost for development
Low High
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
…of using MFP1N
INCLUDED IN OBJECT
Task Structure
HOST INTERFACE
OS
, T
IME
R
INIT
IAL
ISA
TIO
N
MFP1N DRIVER
MESSAGE CONTROL
NETWORK CONTROL
CYCLIC TRANSMISSION
TRANSIENTTRANSMISSION
UN
IQU
E F
UN
CT
ION
Need to develop(Essential task)
Need to develop(Optional task)
Disclosedsource code
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
…of using MFP1N
Task Structure
TASK NAME DESCRIPTION
Initialisation Generates and initialises each task and starts the operating system
OS, timer Manages and schedules each task
Host InterfaceTakes care of handshake with the host side and communication of data with the
CC-Link interface side
Network Control Starts the data link, communicates parameters, and initialises SB/SW devices
Cyclic Transmission Checks the status of each station, and disassembles and assembles message packets
Message Control Takes care of dividing software message data into transient transmission tasks
MFP1N Driver Takes care of MFP operations and data
Transient Transmission
Transmits messages according to commands from the host
Receives request messages from remote stations and sends them to the host side
Unique Function This task should be added if any unique functions should be included
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote 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.
NAME NOTE CONTACT
Communication S/W for CC-Link interface board (Object Code)
License fee is payable Mitsubishi Electric
Object code is delivered in the form of ROM or file, and it is royalty free.
Basic flow from development to release
Development of
Remote I/O
…of using MFP1N and Object Code
Documents
Master/Local
(dual port memory
interface)
Dedicated
Communication
ASIC
Choose documents depending on type of station and arrangement used.
Document Name Document No. Contact
Compatible Product Development Tool with Object Software
SH (NA)-080701ENGPurchase from
Mitsubishi Electric
Order Model Name Package Unit Manufacture
MFP1N (PC96002M)
A6GA-CCMFP1NN60F Contains 60 pieces Purchase from Mitsubishi
ElectricA6GA-CCMFP1NN300F Contains 300 pieces
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
…of using MFP1N and Object Code
Specified Parts
Recommended
Parts
Specified MPU should be used for interface to the MFP1N
Product Name Order Model Name Manufacturer
MPU N80C186XL-20 Intel Corporation
Same recommended parts as Remote I/O are needed (Filter, RS485 Driver, Crystal oscillator, etc.)
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
…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.
Name Contact
Source code and related documents CLPA-EU
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
…of using MFP1N and Source Code
Specified Parts
Recommended
Parts
Same recommended parts as Remote I/O are needed (Filter, RS485 Driver, Crystal oscillator, etc.)
Any MPU can be chosen and used for interface to the MFP1N
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
Contact:Any questions about development of CC-Link compatible products
CC-Link Partner Association Europe
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Please push a Button
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Or click for reference section
Basic flow from development to release
Development of
Remote I/O
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
…of using Driver Software (Q80BD-J61BT11N & Q81BD-J61BT11)
Driver S/W can be developed in order to use PCI busCC-Link interface board (Master/Local station) in combination with various OS. (ex. VxWorks, iRMX, etc)
Developing according to Windows sample code and related document
APPLICATION
VxWorks, iRMX, etc.
DRIVER
(Target of development)
CC-LinkMaster/Local
PCI/Q80BD-J61BT11N
PCI Express/Q81BD-J61BT11
Basic flow from development to release
Development of
Remote I/O
…of using Driver Software (Q80BD-J61BT11N & Q81BD-J61BT11)
Feature
CC-Link PCI and PCI Express board are widely installed in combination with Windows, andcan be used on other operating systems.
Driver is easily developed based on sample C++ code for Windows NT 4.0.(Study and analyse logic of source code)
Document (Development Procedure), which describes specification of PCI boards and driver, etc, helps you to study and analyse sample code.
Test programs are attached for your evaluation test.
BCN-*****-*BCN-*****-*
Flow chart
BCN-*****-*
Initial procedure
Flow chart
BCN-*****-*
Initial procedure
Sample drive source codeDDOCcLin . h/ / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / // / DDOCcLin.h-OCcLink Application I/ F / // / Copyright(C) 1998 MITSUBISHI Electric / // / All Right Reserved / // / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / /
BCN-*****-*
Sample drive source codeDDOCcLin . h/ / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / // / DDOCcLin.h-OCcLink Application I/ F / // / Copyright(C) 1998 MITSUBISHI Electric / // / All Right Reserved / // / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / /
BCN-*****-*
Function tree
BCN-*****-***
Function tree
BCN-*****-***
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
…of using Driver Software (Q80BD-J61BT11N & Q81BD-J61BT11)
Seperate ManualsNote:Hardware manual
included with product
PCI Board/
PCI Express
Document Name Document No. Contact
CC-Link V2
Q80BD-J61BT11N Driver Reference Manual (PCI)
SH(NA)080702ENGPurchase from
Mitsubishi Electric
CC-Link V2
Q81BD-J61BT11 Driver Reference Manual (PCI Express)
SH(NA)080527ENGPurchase from
Mitsubishi Electric
Name Model Name Contact
PCI Interface Board Q80BD-J61BT11N From Mitsubishi Electric
PCI Express Board Q81BD-J61BT11 From Mitsubishi Electric
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Development of
Remote I/O
…of using Driver Software (Q80BD-J61BT11N & Q81BD-J61BT11)
Contact:Any questions about development of CC-Link compatible products
CC-Link Partner Association Europe
Remote I/O
Remote Device
Master/Local, Intelligent Device
Driver Softwarefor PCI interface board
Basic flow from development to release
Supporting Information
Remote I/O
Free CLPA Documents
Reference Materials Contacts
CLPA Membership
Protocol Specification BAP-05026-J
Implementation Specification BAP-05027-G
Profile Specification BAP-05028-E
Master/Local Station Conformance Test Specification BAP-C0401-021-A
Intelligent Device Station Conformance Test Specification BAP-C0401-020-A
Remote Device Station Conformance Test Specification BAP-C0401-012-B
Remote I/O Station Conformance Test Specification BAP-C0401-015
CC-Link Conformance Test Regulation BAP-05012-D
CC-Link Conformance Test Regulation (Cable) BAP-05013-A
For full list of documentation go to www.clpa-europe.com
CC-Link Versions 1.1 & 2.0s
…CLPA documents available to members (free)
Basic flow from development to release
Supporting Information
CC-Link Compatible Product Development Guidebook (Free) L(NA)-08025-A
Minimising EMI problems (datasheet) CLPA-EU-6057
CC-Link V1.1 & V2.0 CLPA-EU-1221
CC-Link Remote I/O Station Communication LSI MFP2N
CC-Link Remote I/O Station Communication LSI MFP2AN
CC-Link Remote Device Station Communication LSI MFP2N (Version 2.0 compatible)
Compatible Product Development Tool with Object Software Master/Local & Intelligent Device Station
SH(NA)-080622ENG-C
SH(NA)-080623ENG-C
SH(NA)-080622ENG-C
SH(NA)-080701ENG-D
Remote I/O
Free CLPA Documents
Reference Materials Contacts
CLPA Membership
CC-Link Versions 1.1 & 2.0
…Reference manuals
…Mitsubishi Development Data books (Chargeable)
Basic flow from development to release
Supporting Information
Remote I/O
Free CLPA Documents
Reference Materials Contacts
CLPA Membership
CC-Link Versions 1.1 & 2.0
Device type I/O points
Registers RWr/RWw
Extended cyclic settings
Data handling
V1.1 or V2.0*
ASIC or gateway**
Remote I/O station
<2048 256/256 No Bit data only
V1.1 MFP2N
MFP2AN
Remote I/O station
<8192 2048/2048 Yes Bit data only
V1.1 MFP3N
Remote device station
<8192 2048/2048 Yes Bit and word data
V2.0 MFP3N
Version 1.1 and Version 2.0 are both current. V2.0 was added to allow more data per transmission
…Comparison of CC-Link Version 1.1 and 2.0
Basic flow from development to release
Supporting Information
CLPA HQ
Japan
www.cc-link.org
CLPA Europe
Germany & UK
www.clpa-europe.com
CLPA Americas
USA
www.cc-linkamerica.org
Mitsubishi Electric Europe
Germany
www.mitsubishi-automation.com
Mitsubishi Electric America
USA
www.meau.com
HMS/Anybus www.hms.se www.anybus.com
Hilscher www.Hilscher.com
Remote I/O
Free CLPA Documents
Reference Materials Contacts
CLPA Membership
CC-Link Versions 1.1 & 2.0
…Contact list
Basic flow from development to release
Supporting Information
Registered member: No annual membership fee
Access to free data books and basic document, but no rights
Regular member: Annual membership 1000€
As Registered, plus access product data books & to develop compatible products
Executive member: Annual membership 2000€.
As Regular, plus access to working groups, technical, and marketing committees
Board Member: By invitation of CLPA HQ only.
As above but with voting rights
For full membership information go to www.clpa-europe.com
Remote I/O
Free CLPA Documents
Reference Materials Contacts
CLPA Membership
CC-Link Versions 1.1 & 2.0
…CLPA Membership levels