operating instructions mc-card - lenzedownload.lenze.com/td/mc-cardv1-0en.pdf · mc−can2 3 10...

BA_MC−Card.N*{

Ä.N*{ä

Operating Instructions

Industrial PC

�

MC−xxx

MC card

L−force Controls

MC-PN

x

ACTIVE

LINK

RJSS-5381

RJSS-5381

SYSST0ST1ST2

� Before you start working, read ...

ƒ these instructions

ƒ the operating instructions for the standard device

Follow the enclosed safety instructions!

The sets of documentation are part of the "PC−based Automation" and"Controller−based Automation" manual collection which you can find on the DVDs ofthe same name, or on the Internet at http://www.Lenze.com in the "Services &Downloads" area.

Contents i

� 3BA_MC−Card EN 1.0

1 About this documentation 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Validity information 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Target group 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Document history 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Conventions used 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 Notes used 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Safety instructions 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Product description 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Scope of supply 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 Identification 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Variants 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.1 Overview 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.2 MC−CAN2 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.3 MC−ETC, MC−ETH 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.4 MC−ISI 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.5 MC−PBM, MC−PBS 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3.6 MC−PNC, MC−PND 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Electrical installation 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Important notes 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Mounting 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 Wiring and Configuration 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.1 MC−CAN2 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.2 MC−ETC, MC−ETH 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.3 MC−ISI 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.4 MC−PBM, MC−PBS 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.5 MC−PNC, MC−PND 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Appendix 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Use of the PCAN view/PCAN Explorer with MC−CAN2 43. . . . . . . . . . . . . . . . . . . . . .

5.2 Contact data of system partners 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

About this documentationValidity information

1

� 4 BA_MC−Card EN 1.0

0Fig. 0Tab. 0

1 About this documentation

1.1 Validity information

These instructions are valid for

ƒ MC−CAN2 (dual CAN controller) from version 01

ƒ MC−ETH (Ethernet controller) as of version 01

ƒ MC−ETC (EtherCAT controller) as of version 01

ƒ MC−ISI (serial interfaces) from version 01

ƒ MC−PBM (PROFIBUS master) from version 01

ƒ MC−PBS (PROFIBUS slave) from version 01

ƒ MC−PNC (PROFINET controller ) as of version 01

ƒ MC−PND (PROFINET device) as of version 01

1.2 Target group

This documentation is directed at qualified skilled personnel according to IEC 60364.

Qualified skilled personnel are persons who have the required qualifications to carry outall activities involved in installing, mounting, commissioning, and operating the product.

� Tip!

Information and auxiliary devices related to the Lenze products can be foundin the download area at

http://www.Lenze.com

1.3 Document history

Material number Version Description

.N*{ 1.0 11/2013 TD29 First edition

About this documentationConventions used

1


1.4 Conventions used

Type of information Identification Examples/notes

Spelling of numbers

Decimal separator Point In general, the decimal point is used.For instance: 1234.56

Warnings

UL warnings �Given in English and French

UR warnings �Text

Program name » « PC softwareFor example: »Engineer«, »Global DriveControl« (GDC)

Icons

Page reference � Reference to another page with additionalinformationFor instance: � 16 = see page 16

Documentation reference � Reference to another documentation withadditional informationFor example: � EDKxxx = seedocumentation EDKxxx

About this documentationNotes used

1


1.5 Notes used

The following pictographs and signal words are used in this documentation to indicatedangers and important information:

Safety instructions

Structure of safety instructions:

� Danger!

(characterises the type and severity of danger)

Note

(describes the danger and gives information about how to prevent dangeroussituations)

Pictograph and signal word Meaning

Danger!

Danger of personal injury through dangerous electrical voltage.Reference to an imminent danger that may result in death orserious personal injury if the corresponding measures are nottaken.

� Danger!

Danger of personal injury through a general source of danger.Reference to an imminent danger that may result in death orserious personal injury if the corresponding measures are nottaken.

Stop!Danger of property damage.Reference to a possible danger that may result in propertydamage if the corresponding measures are not taken.

Application notes


� Note! Important note to ensure troublefree operation

� Tip! Useful tip for simple handling

� Reference to another documentation

Special safety instructions and application notes


� Warnings! Safety note or application note for the operation according toUL or CSA requirements.The measures are required to meet the requirements accordingto UL or CSA.� Warnings!

Safety instructions 2


2 Safety instructions

� Danger!

Disregarding the following basic safety measures may lead to severe personalinjury and damage to material assets!

ƒ Lenze drive and automation components ...

... must only be used for the intended purpose.

... must never be operated if damaged.

... must never be subjected to technical modifications.

... must never be operated unless completely assembled.

... must never be operated without the covers/guards.

... can − depending on their degree of protection − have live, movable or rotating partsduring or after operation. Surfaces can be hot.

ƒ All specifications of the corresponding enclosed documentation must be observed.

This is vital for a safe and trouble−free operation and for achieving the specified productfeatures.

The procedural notes and circuit details provided in this document are proposals whichthe user must check for suitability for his application. The manufacturer does notaccept any liability for the suitability of the specified procedures and circuit proposals.

ƒ Only qualified skilled personnel are permitted to work with or on Lenze drive andautomation components.

According to IEC 60364 or CENELEC HD 384, these are persons ...

... who are familiar with the installation, assembly, commissioning and operation ofthe product,

... possess the appropriate qualifications for their work,

... and are acquainted with and can apply all the accident prevent regulations, directivesand laws applicable at the place of use.

Product descriptionScope of supply

3


3 Product description

3.1 Scope of supply

Number

Name

1 MC card

1 Mounting Instructions

� Note!

After receipt of the delivery, check immediately whether the items match theaccompanying papers. We do not accept any liability for deficiencies claimedsubsequently.

Claim

ƒ visible transport damage immediately to the forwarder

ƒ visible deficiencies/incompleteness immediately to your Lenzerepresentative.

3.2 Identification

Type code MC − xxx − xx

Module Card

CAN2 = dual CAN controllerETC = EtherCAT controllerETH = Ethernet controllerISI = serial interfacesPBM = PROFIBUS masterPBS = PROFIBUS slavePNC = PROFINET controllerPND = PROFINET device

Version

Product descriptionVariants

Overview

3


3.3 Variants

3.3.1 Overview

MC card Function For the use with

MC−CAN2 For connection to a CAN fieldbus;the card features 2 independentCAN interfaces

� IPC 3241 C� IPC CPC 2800� IPC CS 5800 − 9800� IPC EL 1800 − 9800� Controller 3200 C� Controller p500

MC−ETC For connection to a EtherCATnetwork

� IPC 3241 C� IPC CPC 2800� IPC CS 5800 − 9800� IPC EL 1800 − 9800

MC−ETH For connection to a Ethernetnetwork

� IPC 3241 C� IPC CPC 2800� IPC CS 5800 − 9800� IPC EL 1800 − 9800

MC−ISI For the connection to RS 232,RS 422, or RS 485; the card has 2independent serial interfaces


MC−PBM For connection to a PROFIBUSsystem as master


MC−PBS For connection to a PROFIBUSsystem as slave


MC−PNC For connection to a PROFINETsystem as control system (controllerinterface connection)


MC−PND For connection to a PROFINETsystem as device (device interfaceconnection)


Product descriptionVariantsMC−CAN2

3


3.3.2 MC−CAN2

Application as directed

The MC−CAN2 is a plug−in card for the connection of a Lenze device to a CAN fieldbus. Itprovides 2 independent CAN interfaces.

The MC card is used as directed if it is solely used in lenze device with MC card interface. Adifferent use, or one beyond these purposes, is not permissible.

Elements

CAN2

CAN2

CAN1

MC-

��

�

�

�

MC−CAN2−001

Pos. Description

� Front panel

Printed circuit board

� Coding

� Standard device connection

� Bus system connection


MC−CAN2

3


Technical data

MC−CAN2

Conformity, approval, directive

Conformity

CE EN 61000−6−4EN 61000−6−2

EMC Directive Class A,industrial premises

Approval

UR UL 508CSA C22.2

Process Control Equipment (File−No. E236341)

Directive

RoHS − Products lead−free in accordance with CEDirective 2011/65/EU

General data and operating conditions

See standard device

Electrical data

Current < 0.2 A at standard device supply voltage of 24 V

Electrical isolation to thefieldbus

yes

Mechanical data

Mass < 0.1 kg

Communication

Type CAN, ISO011898

Protocol CAN

Topology Line, terminated on both sides with 120 �

Node Master or Slave

Number of nodes max. 63

Max. baud rate 1 MBaud

Bus length � CAN communication manual

�

� Warnings!

Use only together with appropriate cable connectors, provided with screws forsecurement and secure connector to avoid loosening.

For use in controlled environment only.

�

� Warnings!

A utiliser exclusivement avec des connecteurs de câble à vis adaptés. Fixer lesconnecteurs pour éviter toute déconnexion.

Destiné uniquement à des zones à environnement contrôlé.

Product descriptionVariantsMC−ETC, MC−ETH

3


3.3.3 MC−ETC, MC−ETH


The MC−ETH is a plug−in card for connecting a Lenze device to a Ethernet network.

The MC−ETC is a plug−in card for connecting a Lenze device as master to a EtherCATnetwork.


� Note!

This is a device of class A. It can cause radio interference in residential areas. Inthis case, the operator may have to take special measures. Any costs arisingfrom these measures must be paid by the operator.

Elements

��

�

�

SPEED

LINK

LAN

MC-ETH

RJSS-5381

�MC−ETH−001

Pos. Description

� Front panel


� Coding


� Network connection


MC−ETC, MC−ETH

3


Technical data

MC−ETH, MC−ETC

Conformity, directive

Conformity

CE EN 61000−6−4EN 61000−6−2


Directive



See standard device

Electrical data



yes

Mechanical data

Mass < 0.1 kg

MC−ETH

Protocol TCP/IP

Baud rate 10/100/1000 Mbits

Connection RJ45 socket to EN 50173

MC−ETC

Protocol EtherCAT

Baud rate 100 Mbits

Connection RJ45 socket to EN 50173

Product descriptionVariantsMC−ISI

3


3.3.4 MC−ISI


The MC−ISI is a plug−in card via which a Lenze device can exchange serial data withperipheral devices.

It provides two independent, electrically isolated interfaces.

ƒ COM A: RS232

ƒ COM B: RS422 or RS485 (switchable)


Elements

MC-ISI

12

34

ON

��

�

�

�

�

�

MC−ISI_001

Pos. Description

� Front panel


� Coding


� COM A connection (RS232)

� COM B connection (RS422/RS485)

� DIP switch


MC−ISI

3


Technical data

MC−ISI


Conformity

CE EN 61000−6−4EN 61000−6−2


Approval

UR UL 508CSA C22.2


Directive



See standard device

Electrical data



yes

Mechanical data

Mass < 0.1 kg

Communication

Type Serial interface

COM A

Type RS232, electrically isolated

Isolation 2.500 Vrms

ESD protection 15 kV

COM B

Type RS422/485 (switchable), electrically isolated

Isolation 2.500 Vrms

ESD protection 15 kV

Baud rate 600 Baud ... 115.2 kBaud

Data frame 5, 6, 7, 8 and 9 Bit

Parity Even, odd, none, space & mark

�

� Warnings!



�

� Warnings!



Product descriptionVariantsMC−PBM, MC−PBS

3


3.3.5 MC−PBM, MC−PBS


The MC−PBM and MC−PBS are plug−in cards for connecting a Lenze device to a PROFIBUSsystem.

Whereas the slave interface connection (MC−PBS) serves to address the device as a nodeunder a PROFIBUS control, the master interface connection (MC−PBM) serves to enable theuser to establish a control on the basis of PROFIBUS.


Elements

��

�

�

��

PROFIBU

S

MC-PN

x

SYSST0ST1ST2

�

�MC−PBx−001

Pos. Description

� Front panel


� Coding


� Fieldbus connection

� Status LEDs


MC−PBM, MC−PBS

3


LED Colour Status Meaning at MC−PBM Meaning at MC−PBS

SYS Green On Communication is running, thedevice has at least established a

connection to one configured node

Slave is in cyclic data exchange withDP master

Blinking with 5Hz

No error within configuration,communication has stopped, or

ready for communication, but noconnection to a slave

Slave has no cyclic data exchangewith DP master

Is blinkingirregularly

Start−up: No or incorrect configuration, commissioning required; runtime:host−watchdog time error

Yellow Blinking with 1Hz Device is in bootstraploader mode and is waiting for firmware download

Blinking with 5Hz

Firmware download is carried out

Is blinkingirregularly

Hardware or fatal system error detected

− Off Supply voltage for the device is missing, or hardware is defective

ST0 − − No function


ST2 Red On Device has a communicationproblem with at least one

PROFIBUS−DP slave or has detected ashort circuit

Application program(communication mode: synchronous

to bus/device−controlled) is nolonger synchronous to the bus cycle

Yellow Is blinkingirregularly

Device is within the PROFIBUS ringand shares the token with other

PROFIBUS master devices

−

On Device holds the PROFIBUS tokenand can transmit telegrams

Slave has receivedparameter/configuration data fromthe DP master and has reached the

DataExchange state

− Off Connection to Ethernet exists. Slave has not reached theDataExchange state

Product descriptionVariantsMC−PBM, MC−PBS

3


Technical data

MC−PBM, MC−PBS


Conformity

CE EN 61000−6−4EN 61000−6−2


Approval

UR UL 508CSA C22.2


Directive



See standard device

Electrical data



yes

Mechanical data

Mass < 0.1 kg

Communication

Type PROFIBUS−DP, ISO 7498

Protocol PROFIBUS−DP

Topology Line, system

Node MC−PBM (Master) / MC−PBS (Slave)

Max. number of nodes persegment

max. 32

Max. number of nodes persystem

max. 128

Baud rate� 24

Bus length

�

� Warnings!



�

� Warnings!




MC−PNC, MC−PND

3


3.3.6 MC−PNC, MC−PND


The MC−PNC and MC−PND are plug−in cards for connecting a Lenze device to a PROFINETsystem.

Whereas the device interface connection (MC−PND) serves to activate the device as a nodeunder a PROFINET control, the controller interface connection (MC−PNC) serves to establishan individual control system on the basis of PROFINET.


��

�

�

ACTIVE

LINK

PROFIN

ET

MC-PN

x

RJSS-5381

RJSS-5381

SYSST0ST1ST2

��

��

MC−PNx−001

Elements

Pos. Description

� Front panel


� Coding


� Bus system connection

� Status LEDs

� Link /Active LED

Product descriptionVariantsMC−PNC, MC−PND

3


LED Colour Status Meaning at MC−PNC Meaning at MC−PND

SYS Green On Operating system is running

Yellow Blinking with 1Hz Error during boot process

On Boot loader waits for boot process

− Off No supply voltage or defect hardware

ST0 Red On Together with ST1 "Red On": no validmaster licence

System error: Watchdog time−out; channel, genericor extended diagnostics is available

Blinking with 2Hz

System error:invalid configuration

DCP signal service is enabled via thebus

− Off No error

ST1 Red On No connection/no link. Or (togetherwith ST0 "Red On") no valid master

licence

No configuration or slow physicalconnection or no physical connection

Blinking with 2Hz

Configuration error: Not allconfigured I/O devices are

connected.

No data exchange

− Off No error


Link Green On Connection to Ethernet exists

− Off No connection to Ethernet

Active Yellow Blinking Device transmits/receives Ethernet frames


MC−PNC, MC−PND

3


Technical data

MC−PNC, MC−PND


Conformity

CE EN 61000−6−4EN 61000−6−2


Approval

UR UL 508CSA C22.2


Directive



See standard device

Electrical data



yes

Mechanical data

Mass < 0.1 kg

MC−PNC (controller)

I/O data � Configurable up to max. 5760 bytes input� Configurable up to max. 5760 bytes output

Data transport � Ethernet frames

Communication � PROFINET IO−RT– cyclic and acyclic

Acyclic data � Read, write, record: max. 1 kbyte/request� Alarms

Functions � Cyclic process data� Buffering host−controlled data exchange of cyclic data� Minimum cycle time: 1 ms� Different cycle times are configurable for different devices� Max. 32 devices can be configured� DCP� Context management via CL−RPC� One buffer is available per device for diagnostic data

Special features � No support for– RT over UDP– Multicast communication– DHCP

� Only one IOCR1 per IO device is possible, IOCR data length:1024 bytes

� Max. number of the connectable IO devices decreases to25 when cycle times lower than 4 ms are used.

� NameOfStation of the IO controller cannot be set via theDCP Set NameOfStation service but only by theconfiguration during the start

Product descriptionVariantsMC−PNC, MC−PND

3


MC−PND (device)

I/O data � Configurable up to max. 1024 bytes input� Configurable up to max. 1024 bytes output

Communication � PROFINET IO−RT– VLAN and priority tagging– cyclic and acyclic

Functions � Cyclic process data� Acyclic read and write requests� Process and diagnostic alarm: 200 bytes� DCP� Context management via CLRPC� Generic diagnostics, channel diagnostics, extended

channel diagnostics: 200 bytes� Comparison of the setpoints / actual values of the

configuration

Special features � Maximum number of modules: 244� Maximum number of submodules: 1� No support for

– RT over UDP– Multicast communication

� Only one device instance is supported

�

� Warnings!



�

� Warnings!



Electrical installationImportant notes

4


4 Electrical installation

4.1 Important notes

Stop!

Short circuit and static discharges

The printed circuit board and the standard device contain components whichare endangered in the case of short circuit or static discharge.

Possible consequences:

ƒ The printed circuit board or devices connected are destroyed.

Protective measures:

ƒ For all operations on the printed circuit board, the latter as well as thestandard device have to be in a deenergised state. This in particular appliesto the connection/disconnection of the printed circuit board and theconnection/disconnection of connectors.

ƒ All persons handling printed circuit boards must regard ESD measures.

ƒ Connector contacts must not be touched.

ƒ Printed circuit boards must only be touched in contact−free places and mustonly be placed on suitable bases (e. g. on ESD packaging or conductivefoamed material).

ƒ Printed circuit boards must only be transported and stored in ESDpackaging.

� Note!

For mounting the unit, the housing of the industrial PC has to be opened(� documentation for the standard device).

4.2 Mounting

SPEED

MC-ETH

RJSS-5381

RJSS-5381

SPEED

LINK

LAN

MC-ETH

RJSS-5381

RJSS-5381

� �

�

ACTIVE

LINK

PROFIN

ET

MC-PN

x

RJSS-5381

RJSS-5381

RJSS-5381

RJSS-5381

SYSST0ST1ST2

LINK

LAN

ACTIVE

LINK

PROFIN

ET

MC-PN

x

RJSS-5381

RJSS-5381

RJSS-5381

RJSS-5381

SYSST0ST1ST2

MC−PNx−002

Electrical installationWiring and ConfigurationMC−CAN2

4


4.3 Wiring and Configuration

4.3.1 MC−CAN2

Wiring

Pin assignment Description Connection type Cable type

1

6

CAN bus connectionPin 1: not assignedPin 2: CAN−LOW (LO)Pin 3: CAN−GND (CG)Pin 4: not assignedPin 5: not assignedPin 6: CAN−GND (CG)Pin 7: CAN−HIGH (HI)Pin 8: not assignedPin 9: not assigned

9−pole SUB−D plug See following table

MC−CAN−003

CG

CAN

LO HI CG

CAN

LO HI CG

CAN

LO HI

R R

AnA2A1

EL100−009

A1 Node 1A2 Node 2An Node nCG CAN−GNDLO CAN−LOWHI CAN−HIGHR 120 �−bus terminating resistor

Specification of the transmission cable

We recommend the use of CAN cables in accordance with ISO 11898−2:

CAN cable in accordance with ISO 11898−2

Cable type Paired with shielding

Impedance 120 � (95 ... 140 �)

Cable resistance/cross−section

Cable length � 300 m � 70 m�/m / 0.25 � 0.34 mm2 (AWG22)

Cable length 301 � 1000 m � 40 m�/m / 0.5 mm2 (AWG20)

Signal propagation delay � 5 ns/m

Electrical installationWiring and Configuration

MC−CAN2

4


Use of the MC card in Windows� XP or Windows� Embedded Standard 2009

In order to use the communication card in Windows� XP, a device driver is required whichis part of the "communication software (CAN)". It is included on the "PC basedAutomation" DVD and can also be found at www.Lenze.com in the download area. Thedevice driver assumes the entire management of the interface.

The following files are installed with the device driver:

ƒ can2bdrv.sys (visible in the Windows device manager as "CAN2 Bus Driver")

ƒ can2fdrv.sys (visible in the Windows device manager as "CAN Device")

ƒ mccan2services.exe (visible in the Windows task manager as "McCAN2 WrapperService")

The communication card is configured via the Lenze system bus configurator. The settingsentered there are valid for all applications which communicate via this card.

Parameter Value range Comment

Baud rate 5, 10, 20, 50, 100,125, 250, 500,1000

in kbps

Time limit for the node search 0.5 ... 10 s Total time the bus scan is waiting for the feedback ofall nodes

Communication time−out 0.1 ... 10 s Time up to which a CAN node must have responded;after that an error is reported.

Parameter channel 0, 1, 2 0: CANopen1: Lenze system bus parameter channel 12: Lenze system bus parameter channel 2

Repeat tests 1 ... 10 Repetition of the CAN telegrams in case of an error

Expansion slot (MC1 / MC2) 1, 2 Number of the module card slot at the IPC (seelabelling of the slots at the IPC)

Channel (CAN1 / CAN2) 1, 2 Number of the CAN terminal on the corresponding card(see labelling at the front panel of the card)

Electrical installationWiring and ConfigurationMC−CAN2

4


For diagnostic purposes, the following tools are provided on the "PC based Automation"DVD:

ƒ PCAN view: Simple CAN monitor

ƒ PCAN stat: Status monitor of the device driver

Further information on how to apply these diagnostic programs can be found in theappendix.

The device driver contains a user interface which can be addressed with the followingtools:

ƒ PCAN Light

A simple DLL interface for accessing max. one communication card MC−CAN2. The API"PCAN Light" comprises all functions for initialising, parameter setting, exchangingdata, and reading out status information.

The API comes in two DLLs on the "PC based Automation" DVD: PCAN_MC_CAN.DLLfor accessing CAN1 and PCAN_MC_CAN2.DLL for accessing CAN2, hence the CANterminals of the first plugged MC−CAN2 card. The access to a second MC−CAN2 card isnot possible with PCAN Light but only by means of the integrated developmentenvironments PCAN Evaluation or PCAN Developer (see below).

Further information on "PCAN Light" can be obtained from the online help for "PCANLight" on the "PC based Automation" DVD. There you will also find the source code ofexample programs for a quick training.

CAUTION: In order to use "PCAN Light" together with the MC−CAN2 card, you must getan additional licence. This is coupled with the communication card and made visible bya licence sticker. Before using "PCAN Light", please check if you have got the requiredlicence since otherwise you would violate the copyright.

ƒ PCAN Evaluation / PCAN Developer

These complex integrated development environments provide more comprehensivefunctions than PCAN Light; e.g.:

– Event operation

– Error frame handling

– Operation of several clients with one hardware

The integrated development environments can be obtained from the Peak company(� 44).

� Note!

Addressing the communication card from your own applications requiresspecial programming skills. Lenze does not offer any support regarding thismatter.

The communication card is compatible with the technology of Peak (� 44).There you will get the required support.


MC−CAN2

4


Use of the MC card in Windows� CE

In Windows� CE the card interact via control system. All required drivers are installed

� Note!

No special support is provided currently if you use the communication card inyour own applications. For special projects, please contact your sales office.

Electrical installationWiring and ConfigurationMC−ETC, MC−ETH

4


4.3.2 MC−ETC, MC−ETH

Wiring

Description Connection type Cable type

SPEEDLINK

LAN

MC−ETH port"Link" LED:On: Connection OKBlinking: Data transfer"Speed" LED:Off: 10 MbpsGreen: 100 MbpsYellow: 1000 Mbps

MC−ETC port"Link" LED:On: Connection OKBlinking: Data transfer"Speed" LED:Green: 100 Mbps

RJ45 socket

CAT5 S/UTP or CAT5e S/FTP(recommended) networkcable, max. cable length

100 m

MC−ETH−003

� Note!

If the RJ45 plug connection is exposed to oscillating or vibrating stress:

ƒ Use a strain relief in the immediate vicinity of the RJ45 socket.

ƒ Select the contact surface on which the device is mounted as fixing point ofthe strain relief.

ƒ Comply with the related minimum bending radius of the cable used.


In order to use the communication card in Windows� XP, a device driver is required. It isalready pre−installed and also included on the "PC based Automation" DVD. For theimplementation of the communication card in your own applications, use "WinSockets",which are provided by corresponding programming systems. A special library is notrequired.

� Note!

Addressing the communication card from your own applications requiresspecial programming skills. Lenze does not offer any support regarding thismatter. However, we can refer you to service providers who executecustomised programming and are familiar with Lenze Industrial PCs.


MC−ETC, MC−ETH

4



You can use the card in Windows� CE only with IPCs, not with controllers.

In order to be able to use the communication card in Windows� CE, a device driver isrequired. It is already pre−installed. For integrating the communication card into individualapplications, use so−called "WinSockets" which are provided by the correspondingprogramming systems. A special library is not required.

Electrical installationWiring and ConfigurationMC−ISI

4


4.3.3 MC−ISI

Configuration

DIP switch for setting the mode:

DIP switch Description

1 2 3 4

ON

Pos. 1 = ON: RS485 modePos. 2 = ON: RS422 modePos. 3 = ON/OFF: four−wire conductor/two−wire conductor (only relevant for RS485 mode)Pos. 4 = ON/OFF: echo function activated/deactivated (only relevant for RS485 mode +two−wire conductor)

MC−ISI_004

Set the mode:

Mode DIP switch setting

RS485 mode, two−wire conductor, deactivated echo function (default)RS485 mode, two−wire conductor, activated echo functionRS485 mode, four−wire conductorRS422

Pos. 1 = ONPos. 1+4 = ONPos. 1+3 = ONPos. 2 = ON

� Note!

ƒ If switch 1 = ON (RS485), switch 2 must be set to OFF;if switch 2 = ON (RS422), switch 1 must be set to OFF.

ƒ The echo function monitors the RS485 bus for collisions.

Further settings:

MC−ISI_003

Jumper Function

JP1 plugged−on to ENA: default setting

JP3 plugged−on to HW: default setting

JP5 plugged−on: terminating resistor for RS422−/485 mode activatedopen: terminating resistor for RS422−/485 mode deactivated

Do not assign JP2! Lenze service personnel only.


MC−ISI

4


Wiring

COM A (RS232):


1

6

Pin 1: DCDPin 2: RXDPin 3: TXDPin 4: DTRPin 5: GNDPin 6: DSRPin 7: RTSPin 8: CTSPin 9: RI

9−pole Sub−D plug Control cable

MC−CAN−003

1 DCD2 RXD3 TXD4 DTR

5 GND6 DSR

7 RTS

8 CTS

9 NC

1 DCD2 RXD3 TXD4 DTR

5 GND6 DSR

7 RTS

8 CTS

9 NC

COM A

RS232

xxx

MC−ISI_005

COM B (RS422/485):


1

6

Pin 1: NCPin 2: TXD+Pin 3: RXD+ (Data+)Pin 4: NCPin 5: GNDPin 6: NCPin 7: TXD−Pin 8: RXD− (Data −)Pin 9: NC

9−pole Sub−D plug Control cable

MC−CAN−003

1 NC2 TXD+3 RXD+4 NC5 GND6 NC7 TXD-8 RXD-9 NC

1 NC2 TXD+3 RXD+4 NC5 GND6 NC7 TXD-8 RXD-9 NC

RS422(4-wire)

RS485(2-wire)COM B COM Bxxx xxx

1 NC2 TXD+3 RXD+4 NC5 GND6 VCC7 TXD-8 RXD-9 NC

1 NC2 TXD+3 RXD+4 NC5 GND6 VCC7 TXD-8 RXD-9 NC

MC−ISI_006

� Note!

The terminating resistor at the physically first and last node must be activated(� 30).

Electrical installationWiring and ConfigurationMC−ISI

4



In order to use the communication card in Windows� XP, a device driver is required.

Usually, the communication card in the IPC is already mounted and the driver is installedand configured. Thus, an installation is only required if the communication card has beenordered separately or the system is to be set up anew.

The device driver can be found on the "PC based Automation" DVD or on the Internet atwww.Lenze.com in the download area.

� Note!

The communication card is configured via jumper and DIP switch. The drivercannot be used for this purpose.

� Note!

Addressing the communication card from your own applications requiresspecial programming skills. Lenze does not offer any support regarding thismatter. However, we can refer you to service providers who executecustomised programming and are familiar with Lenze Industrial PCs.



� Note!



MC−PBM, MC−PBS

4


4.3.4 MC−PBM, MC−PBS

Wiring


1

2

3

4

5

6

7

8

9

PROFIBUS connectionPin 1: not assignedPin 2: not assignedPin 3: RxD/TxD−P(B)Pin 4: RTSPin 5: M5VPin 6: P5VPin 7: not assignedPin 8: RxD/TxD−N(A)Pin 9: not assigned

9−pole Sub−D socket See following table

epm−t223

RxD/TxD-P(B)

Schirm

Master Slave

3

8

3

8

Schirm

P5V P5V

M5V M5V

330� 330�

330� 330�

220� 220�

Schirm

3

8RxD/TxD-N(A)

5

6

RxD/TxD-P(B)

RxD/TxD-N(A)

Slave

RxD/TxD-P(B)

RxD/TxD-N(A)

5

3

8

6

SLIO090

� Note!

The PROFIBUS cable must be terminated with its surge impedance.

Specification of the transmission cable

� Note!

Only use cables complying with the listed specifications of the PROFIBUS userorganisation.

Field Values

Specific resistance 135 ... 165 �/km, (f = 3 ... 20 MHz)

Capacitance per unit length � 30 nF/km

Loop resistance < 110 �/km

Core diameter > 0.64 mm

Core cross−section > 0.34 mm2

Cores Twisted double, insulated and shielded

Electrical installationWiring and ConfigurationMC−PBM, MC−PBS

4


Baud rate / length of bus cable

Baud rate [kBit/s] Length [m]

9.6 − 93.75 1200

187.5 1000

500 400

1500 200

3000 − 12000 100



The device driver assumes the entire management of the interface and contains a simpleC interface which is addressed via a DLL. The user is only responsible for the transfer of thecorrect parameters to the device driver. All dependencies on the operating system likeinterrupt management and time monitoring are executed by the driver.

The driver comprises all functions for initialising, parameter setting, exchanging data, andreading out status information. It operates in the polling or interrupt mode and controlsmaximally two cards in an IPC.

Together with the device drivers, example programs are supplied in the source code for aquick training. Other components are an installation program for registration at theoperating system and the SyCon.net bus configurator of the master.

� Note!

The communication card is based on the netX technology of the Hilschercompany (� 44). Further information on the programming interface andprogramming examples for the CIF Device Driver can be obtained from theHilscher company.

Only drivers approved by Lenze may be used.

Addressing the communication card from your own applications requiresspecial programming skills. Lenze can only assist you in the basiccommissioning of the card. If you have special questions about programming,the Hilscher company will help you after contacting Lenze. There, alsochargeable services can be ordered.

Usually, the communication card in the IPC is already mounted and the driver is installedand configured. Thus, the following steps are only required if the communication card hasbeen ordered separately or the system is to be set up anew.

The "cifX Device Driver" and the corresponding documentation can be found on the "PCbased Automation" DVD or on the Internet at www.Lenze.com in the download area.


MC−PBM, MC−PBS

4


� How to install the device driver:

1. Switch on the IPC after installing the communication card.

The operating system recognises the new hardware and the "Found New HardwareWizard" starts.

2. Select Install from a list or specific location.

3. Insert the "PC based Automation" DVD into the DVD drive and click Next.

4. Select the Search the best driver in these locations option field and the Searchexchangeable disk storage (floppy disk, CD,..) control field in the following dialog.

5. Click Next.

The CifX driver is installed. The installation progress is displayed. At the end, the wizardreports that the software for the "cifX PCI/PCIe Device" has been installed.

6. Click Complete.

7. Check if the communication card has been installed correctly:

– Start the Windows� system control.

– If you have set the "classic view", double−click the System entry. If you have set the"category view", select Performance and Maintenance � System.

– Select the Hardware register from the "System properties" dialog.

The device manager is opened. If no error is reported under "CIFx CommunicationInterface" � "CifX PCI/PCIe Device", the communication card has been installedcorrectly.

Electrical installationWiring and ConfigurationMC−PBM, MC−PBS

4


� How to configure the device driver:

1. Start the "cifX Driver Setup Utility":

– Open the Windows� system control.

– If you have set the "classic view", double−click the cifx Setup entry. If you have setthe "category view", first select Other Control Panel Options in the left windowarea and then double−click the cifx Setup entry.

� Tip!

If, in an exceptional case, the device driver is to be installed before thecommunication card has been installed, start the "cifX Driver Setup Utility" viathe Windows Explorer. For this purpose, go to the x:\Programs\cifX DeviceDriver folder and double−click cifX Setup.exe.

After the application has started, its user interface is displayed. Use the object tree inthe left window area to open the corresponding dialog pages in which you assign afirmware file to the communication card.

� Note!

The navigation pane can be shown and hidden via the Hide navigation pane /Show navigation pane icon.

2. Assign the bus−specific firmware file to the communication channel 0 (CH#0):

– Go to the object tree and open the Active Devices folder and the (sub) folder of thecommunication card (e.g. cifX0 ( )) you want to configure.

– Click the communication channel you want to assign to a firmware file. Therespective dialog page is displayed.

– Go to the Downloads (Modules) area, click the Add button and select the firmwarefile (*.nxf) in the following menu.

– Confirm the selection with OK. The file path and the name of the firmware file aredisplayed in the "File" list.

– Click the Apply button.


MC−PBM, MC−PBS

4


3. Exit the "cifX Driver Setup Utility" application via the File � Quit menu.

� Note!

Only for MC−PBM (Master):

ƒ Configure the bus via the host application or the bus configurator"SyCon.net".

Only for MC−PBS (Slave):

ƒ Configure the bus via the warm start parameters in the "cifX Driver SetupUtility". Further information can be obtained from the online help of the"cifX Driver Setup Utility" and the documentation of Hilscher.


A) IPCs

The following conditions must be met for operating the card:

1. There must be a "Config" folder on the CF card in the storage drive.

2. This folder must contain a firmware file named "Firmware.nxt".

3. The card must be configured:

– MC−PBS (MPI): Configuration via an end application.

– MC−PBM: There must be a "Config.dbm" file in the "Config" folder. Furtherinformation on this can be found in the documentation for your FDT frameapplication.

At the next system start, the driver loads the firmware and the configuration from the"Config" folder to the communication card.

� Note!


B) Controller


� Note!


Electrical installationWiring and ConfigurationMC−PNC, MC−PND

4


4.3.5 MC−PNC, MC−PND

Wiring

Description Connection type Cable type

1 8

Ethernet connectionPin 1: TX+Pin 2: TX−Pin 3: RX+Pin 4: Term1*Pin 5: Term1*Pin 6: RX−Pin 7: Term2**Pin 8: Term2**

RJ45 socketNetwork cable CAT5 S/UTP orCAT5e S/FTP (recommended),

cable length max. 100 m

MC−PNx−003

* Bridged and terminated by RC circuit against PE** Bridged and terminated by RC circuit against PE

� Note!

The device supports the auto−crossover function where RX and TX can beexchanged, if required.

� Note!

If the RJ45 plug connection is exposed to oscillating or vibrating stress:

ƒ Use a strain relief in the immediate vicinity of the RJ45 socket.

ƒ Select the contact surface on which the device is mounted as fixing point ofthe strain relief.

ƒ Comply with the related minimum bending radius of the cable used.


MC−PNC, MC−PND

4




The device driver assumes the entire management of the interface and contains a simpleC interface which is addressed via a DLL. The user is only responsible for the transfer of thecorrect parameters to the device driver. All dependencies on the operating system likeinterrupt management and time monitoring are executed by the driver.

The driver comprises all functions for initialising, parameter setting, exchanging data, andreading out status information. It operates in the polling or interrupt mode and controlsmaximally two cards in an IPC.

Together with the device drivers, example programs are supplied in the source code for aquick training. Other components are an installation program for registration at theoperating system and the SyCon.net bus configurator of the master.

� Note!

The communication card is based on the netX technology of the Hilschercompany (� 44). Further information on the programming interface andprogramming examples for the CIF Device Driver can be obtained from theHilscher company.

Only drivers approved by Lenze may be used.

Addressing the communication card from your own applications requiresspecial programming skills. Lenze can only assist you in the basiccommissioning of the card. If you have special questions about programming,the Hilscher company will help you after contacting Lenze. There, alsochargeable services can be ordered.

Usually, the communication card in the IPC is already mounted and the driver is installedand configured. Thus, the following steps are only required if the communication card hasbeen ordered separately or the system is to be set up anew.

The "cifX Device Driver" and the corresponding documentation can be found on the "PCbased Automation" DVD or on the Internet at www.Lenze.com in the download area.


4


� How to install the device driver:

1. Switch on the IPC after installing the communication card.

The operating system recognises the new hardware and the "Found New HardwareWizard" starts.

2. Select Install from a list or specific location.

3. Insert the "PC based Automation" DVD into the DVD drive and click Next.

4. Select the Search the best driver in these locations option field and the Searchexchangeable disk storage (floppy disk, CD,..) control field in the following dialog.

5. Click Next.

The CifX driver is installed. The installation progress is displayed. At the end, the wizardreports that the software for the "cifX PCI/PCIe Device" has been installed.

6. Click Complete.

7. Check if the communication card has been installed correctly:

– Start the Windows� system control.

– If you have set the "classic view", double−click the System entry. If you have set the"category view", select Performance and Maintenance � System.

– Select the Hardware register from the "System properties" dialog.

The device manager is opened. If no error is reported under "CIFx CommunicationInterface" � "CifX PCI/PCIe Device", the communication card has been installedcorrectly.


MC−PNC, MC−PND

4


� How to configure the device driver:

1. Start the "cifX Driver Setup Utility":

– Open the Windows� system control.

– If you have set the "classic view", double−click the cifx Setup entry. If you have setthe "category view", first select Other Control Panel Options in the left windowarea and then double−click the cifx Setup entry.

� Tip!

If, in an exceptional case, the device driver is to be installed before thecommunication card has been installed, start the "cifX Driver Setup Utility" viathe Windows Explorer. For this purpose, go to the x:\Programs\cifX DeviceDriver folder and double−click cifX Setup.exe.

After the application has started, its user interface is displayed. Use the object tree inthe left window area to open the corresponding dialog pages in which you assign afirmware file to the communication card.

� Note!

The navigation pane can be shown and hidden via the Hide navigation pane /Show navigation pane icon.

2. Assign the bus−specific firmware file to the communication channel 0 (CH#0):

– Go to the object tree and open the Active Devices folder and the (sub) folder of thecommunication card (e.g. cifX0 ( )) you want to configure.

– Click the communication channel you want to assign to a firmware file. Therespective dialog page is displayed.

– Go to the Downloads (Modules) area, click the Add button and select the firmwarefile (*.nxf) in the following menu.

– Confirm the selection with OK. The file path and the name of the firmware file aredisplayed in the "File" list.

– Click the Apply button.


4


3. Exit the "cifX Driver Setup Utility" application via the File � Quit menu.

� Note!

Only for MC−PNC (Controller):

ƒ Configure the bus via the host application or the bus configurator"SyCon.net".

Only for MC−PND (Device):

ƒ Configure the bus via the warm start parameters in the "cifX Driver SetupUtility". Further information can be obtained from the online help of the"cifX Driver Setup Utility" and the documentation of Hilscher.


A) IPCs

The following conditions must be met for operating the card:

1. There must be a "Config" folder on the CF card in the storage drive.

2. This folder must contain a firmware file named "Firmware.nxt".

3. The card must be configured:

– MC−PBS (MPI): Configuration via an end application.

– MC−PBM: There must be a "Config.dbm" file in the "Config" folder. Furtherinformation on this can be found in the documentation for your FDT frameapplication.

At the next system start, the driver loads the firmware and the configuration from the"Config" folder to the communication card.

� Note!


B) Controller

At the time the Lenze controllers can only communicate with the MC−PND via controlsystem, not with the MC−PNC.


� Note!


AppendixUse of the PCAN view/PCAN Explorer with MC−CAN2

5


5 Appendix

5.1 Use of the PCAN view/PCAN Explorer with MC−CAN2

Peak System Technik GmbH provides the PCAN Explorer software for the diagnostics of aCAN network. The PCAN view program is the basic free−of−charge version of this program.When using these programs with the MC−CAN2 card, please observe the following:

ƒ In the PCAN software, the MC−CAN2 card is not represented as hardware but asclient of a network. For this reason, the networks in the PCAN software arerepresented as "internal networks" as if these networks would have no connectionto a hardware.

ƒ The status bar of the PCAN Explorer indicates a symbol with a crossed out hardwareeven with a correct connection. Information such as "Busheavy" is not displayed inthe status bar.

ƒ The PCAN view shows information such as "Busheavy" only for one second, then itdisappears again.

The network names are defined as follows:

Expansion slot Connection Network name

MC 1 CAN 1 LSysbusNet1




The following illustration shows how the MC−CAN2 and the connected networks arerepresented in the PCAN stat diagnostic program.

The baud rate is exclusively selected via the system bus configurator, not via networknames.

The windows "Receive" and Transmit" now continuously show the telegrams.

Details of the PCAN view, PCAN stat and PCAN Explorer programs can be found in thecorresponding online helps.

AppendixContact data of system partners

5


5.2 Contact data of system partners

Hilscher

Hilscher Gesellschaft für Systemautomation mbH

Rheinstraße 15

D−65795 Hattersheim

+49 6190 / 9907−0

www.hilscher.com

Peak

Peak System Technik GmbH

Otto−Röhm−Str. 69

D−64293 Darmstadt

+49 6151 / 8173−0

www.peak−system.com

AppendixContact data of system partners

5


�© 11/2013

� Lenze Automation GmbHHans−Lenze−Str. 1D−31855 AerzenGermany

Service Lenze Service GmbHBreslauer Straße 3D−32699 ExtertalGermany

� +49�(0)51 54 /�82−0 � 00�80�00�/ 24�4�68�77 (24 h helpline)

� +49�(0)51 54 /�82 − 28 00 � +49�(0)51�54�/ 82−11 12

� [email protected] � [email protected]

� www.Lenze.com

BA_MC−Card � .N*{ � EN � 1.0 � TD29

10 9 8 7 6 5 4 3 2 1

operating instructions mc-card - lenzedownload.lenze.com/td/mc-card__v1-0__en.pdf · mc−can2 3 10...

Documents

operating instructions mc-card - lenzedownload.lenze.com/td/mc-cardv1-0en.pdf · mc−can2 3 10...