Upgrade to new software version. Support of Multiple Drive Handling, Wireless Direct, and Condition-based Monitoring.
5.3
VLT® Motion Control Tool MCT 10
Operating Guide
Introduction
1 Introduction
1.1 Purpose of this Operating Guide
This manual provides basic knowledge required to use the MCT 10 Set-up Software with Danfoss drives. Familiarity with the following is assumed:
•
MS®-Windows™ at user level.
•
Set-up, process knowledge, and operation of drive.
•
Use of and linkage with communication equipment.
The manual does not provide any detailed information regarding specific applications or possible solutions and related parameter
combinations in the set-up and use of a drive. Refer to the operating guide and design guide of the drive. Any update of the manual
and instructions related to the MCT 10 Set-up Software is available at www.danfoss.com.
Familiarity with the PC or PLC master of the system is assumed. Issues regarding hardware or software produced by other manufacturers are beyond the scope of this manual and are not the responsibility of Danfoss.
Refer to the appropriate manuals for more information about master-to-master communication, or communication to a non-Danfoss slave.
1.2 Manual and Software Version
This manual is regularly reviewed and updated. All suggestions for improvement are welcome.
The original language of this manual is English.
1.3 Intended Use
The MCT 10 Set-up Software enables full system configuration and control. With MCT 10, it is possible to monitor the entire system
more efficiently for faster diagnosis and better preventive maintenance.
MCT 10 is designed as an interactive commissioning tool for quick and easy commissioning of the following drive series:
For planning a new communication network offline. The MCT 10 contains a complete database with all Danfoss Drives products.
•
For commissioning drives online.
•
For easy replacement of drives.
•
For easy expansion of networks with more drives.
•
For back-up of parameter settings of drives in a communication network.
•
The MCT 10 supports PROFIBUS DP-V1 communication via a master class 2 connection. This connection eliminates the need for
an extra communication network.
The communication framework part of MCT 10 is handling the control of the fieldbuses. It provides enhanced capabilities allowing
multiple concurrent fieldbus communication. Several fieldbuses can be configured and combined in the same network within MCT
10.
Introduction
N O T I C E
If several fieldbuses are created with the same type, make sure that they are configured with different scan ranges.
1.4 System Requirements
To use the VLT® Motion Control Tool MCT 10, the IBM-compatible computer must meet the following minimum system requirements:
4 GB of available space on the hard drive.
•
MCT 10 runs on Windows™ 10 32/64-bit editions.
1.5 Software Modules
The VLT® Motion Control Tool MCT 10 Set-up Software is supplied in 2 modules:
•
MCT 10 Set-up Software for:
-
Setting the drive parameters.
-
Copying parameter sets to and from a drive.
-
Documentation/printout of set-up, including diagrams.
-
Servicing and fault analysis.
•
APoss program for creating APoss programs.
1.5.1 Features of the VLT® Motion Control Tool MCT 10
•
Project-oriented PC tool, 1 tool for all drive series.
•
Links to all Windows applications possible.
•
Supports Siemens CP PCMCIA-and PCI cards for PROFIBUS DP-V1 master class 2 connection.
•
Supports standard interfaces: COMx, USB, RS232 (Flux).
•
Siemens PG/Field PGs already have the required hardware.
•
View is highly individually configurable.
•
Downwards compatibility with Dos-Dialog (*.mnu) and WinDialog (*.vlt).
•
Windows™ Explorer-like interface for quick and easy start-up and navigation.
The following manuals related to VLT® Motion Control Tool MCT 10 are available:
•
VLT® PROFIBUS DP-V1 MCA 101 Installation Guide.
•
Design guides for the relevant drives.
Refer to www.danfoss.com/en/about-danfoss/our-businesses/drives/ for more information.
It is also possible to find video training material on this site for operating the MCT 10.
Drives in the VLT® HVAC Drive FC 102, VLT® AQUA Drive FC 202, and VLT® AutomationDrive FC 302 series are equipped with a USB
port. Communication from a PC can be established using a standard A–B male-to-male USB cable connected to the drive. No extra
hardware or bus configuration is required. If the PC is equipped with more than 1 USB port, several drives can be connected. The
USB bus is automatically added to the network bus list.
Establish a hardwired connection through:
•
Standard built-in RS485, or
•
USB port.
The USB interface socket allows devices to be connected and disconnected using hot swapping. When connecting a drive using
USB, MCT 10 Set-up Software automatically adds on to the bus list.
If the VLT® PROFIBUS DP-V1 MCA 101 or the VLT® EtherNet/IP MCA 121 option is mounted in the drive, establish the connection
through:
•
PROFIBUS master class 2 connection (MSAC 2), or
•
Ethernet-based network.
N O T I C E
Connect soft starters either via a USB cable or via ethernet.
N O T I C E
RISK OF DAMAGE TO PC USB HOST CONTROLLER
When connecting the PC to the drive through the USB cable, there is a risk of damaging the PC USB host controller.
Follow the recommendations for grounding described in the Operating Guide for the relevant drive.
-
Use a USB isolator with galvanic isolation to protect the PC USB host controller from ground potential differences when con-
-
necting the PC to a drive through a USB cable.
Do NOT use a PC power cable with a ground plug when the PC is connected to the drive through a USB cable.
-
Communication from a PC can be established via RS232 to RS485 converters or via USB to RS485 converters.
Illustration 3: Communication from a PC
4.2 Manual Fieldbus Configuration
After installation, configure the non-plug-and-play networks via the fieldbus configuration dialog.
Right-click Network and select Add/Remove/Configure Buses.
Illustration 4: Refreshing the Fieldbus List
4.
Add, remove, or configure the properties for the connected buses.
Set-up of Communication
Illustration 5: Fieldbus Configuration
5.
Scan the network for active drives to make MCT 10 indicate available drives on the non-plug-and-play fieldbuses.
4.3 Automatic Scan
Only the USB fieldbus is scanned automatically when a drive is connected to the PC. For non-plug-and-play fieldbuses, scan manually for active drives.
4.3.1 Scan Range Configuration
Enter the preferred scan setting by right-clicking SerialCom and then selecting Configure Driver.
Adding a standard bus RS485 or PROFIBUS to the network tree configures the scan range to scan the entire address range. The
Ethernet-TSC bus is added using the current IP address settings.
The fieldbus scan range can be configured in several ways:
•
Right-click the Fieldbus icon in the network tree and select Configure Bus.
•
Mark the Fieldbus icon in the network tree and select Configure under Communication in the main menu bar.
•
Open the Fieldbus Configuration dialog, right-click the Network icon, and select Add/Remove/Configure Buses.
Right-click the Fieldbus icon in the network tree and select Scan Bus for active drives.
•
Mark the Fieldbus icon in the network tree and select Scan/Refresh under Communication in the main menu bar.
•
Mark the Fieldbus icon in the network tree and select the Scan icon on the toolbar.
The Scanning for Drives window appears and indicates the progress of the scan.
Illustration 7: Progress of Network Scanning
4.4 Set Up the Drive with RS485 Data Communication
All drives can be configured to 300, 1200, 4800, 9600 (default), 19200, 38400, 57600, or 115200 baud. The serial configuration is
always configured with:
•
8 data bits.
•
1 stop bit.
•
Even parity.
4.4.1 Configuring the Fieldbus
When using an RS485 converter as the Advantech ADAM converter, MCT 10 Set-up Software indicates online drives available on the
fieldbus after scanning the bus.
N O T I C E
Protocol and advanced settings are for performance optimization and should normally not be changed.
Open the Serial Fieldbus Configuration dialog box or right-click the appropriate fieldbus.
Illustration 8: Serial Fieldbus Configuration
2.
Set the COM port number.
Set-up of Communication
When using USB to RS485 converters, the actual COM port number can be identified from the device manager part of the
Windows control panel.
3.
Set the baud rate, parity, and the number of stop bits (must match the settings in the drive).
4.
Set the fieldbus scanning range to the available address to limit the time scanning for active drives.
5.
Press OK to activate settings or select to restore the default settings.
4.4.2 USB Data Communication
Illustration 9: Network Bus List
When the USB cable is disconnected, the drive connected via the USB port is removed from the network bus list.
4.5 Set-up of Soft Starter
Setting up connectivity to the VLT® Soft Starter MCD 500 and VLT® Soft Starter MCD 600 requires that the USB communication module is mounted on the soft starter. Communication from a PC can be established using a standard A–B male-to-male USB cable
connected to the USB communication module. If the PC is equipped with more than 1 USB port or a USB HUB, several soft starters
can be connected.
All soft starters can be configured to 300, 1200, 4800, 9600 (default), 19200, 38400, 57600, or 115200 baud. The serial configuration
is always configured with:
•
8 data bits.
•
1 stop bit.
•
No parity.
Illustration 10: Serial Configuration of Soft Starters
4.5.1.1 Configuring the Fieldbus
Procedure
1.
Add and configure the bus from the Fieldbus Configuration dialog.
If the bus is already added to the network, it can be reconfigured by right-clicking on the appropriate soft starter fieldbus.
2.
Set the COM port number. The actual COM port number can be identified from the device manager part of the control
panel.
3.
Set the baud rate, parity, and the number of stop bits (must match the setting in the soft starter).
4.
Reset to Default restores the general settings and fieldbus scanning to factory configuration values.
4.5.1.2 Using the Hilscher NetIdent Protocol
Use the tool for searching for devices and for identifying and changing IP addresses. The tool also has a filtering function.
With VLT® Soft Starter MCD 600, a parameter file (PAR file) can be exported from the soft starter to a USB stick and copied into VLT®
Motion Control Tool MCT 10. After changing the file in MCT 10, the PAR file can be copied back to the USB stick and applied to the
soft starter.
Procedure
Create an MCD 600 project soft starter.
1.
Right-click the project folder.
2.
3.
Select Import parameters.
From the dialog, select the file to import.
4.
A dialog opens showing information about the selected file.
Setting up PROFIBUS DP-V1 communication requires a VLT® PROFIBUS DP-V1 MCA 101 option module. Communication from a PC
using PROFIBUS DP-V1 can be established using a PROFIBUS PCMCIA card or a card installed in the PC. The PROFIBUS cable from the
drive is connected to the 9-pin sub D socket connector on the card.
Illustration 12: PROFIBS DP-V1 Communication
Consult Siemens www.siemens.com for the latest supported cards for PCs.
N O T I C E
Connectivity via PROFIBUS DP-V1 to a VLT® AutomationDrive FC 302 utilizing the VLT® PROFIBUS Converter MCA 114 with option
firmware version 2.03 is not possible from MCT 10 Set-up Software. Use the fieldbus or USB bus instead.
4.6.1 Configuring PROFIBUS DP-V1
When using a PROFIBUS interface card with the associated driver installed, MCT 10 Set-up Software indicates online drives available
on the specific PROFIBUS after scanning the bus for active drives.
Configure the bus from the Fieldbus Configuration dialog or by right-clicking the appropriate PROFIBUS bus.
Illustration 13: PROFIBUS Fieldbus Configuration
2.
Set the board number.
3.
Set the fieldbus scanning range to the available addresses only to limit the time used for scanning active drives.
4.
Press OK to activate or reset to restore factory default settings.
Set-up of Communication
4.6.2 DP-V1 Connection and PG/PC Interface
The MCT 10 Set-up Software PROFIBUS DP-V1 fieldbus plug-in utilizes the Siemens SoftNet driver available from Step7, or alternatively Simatic NET, to establish connectivity via the supported master class 2 cards such as CP5511 or CP5512.
N O T I C E
STEP7 Lite version does not support the SoftNet driver.
4.6.2.1 Setting Up the PG/PC Interface
This procedure explains how to set up the PG/PC Interface from default configuration to open the PROFIBUS connection from MCT
10.
Cabling and terminations must be in accordance with wiring and cabling requirements for PROFIBUS.
Configure Access Point of the Application to CP_L2_1 pointing to the master class 2 card used.
3.
Set Interface Parameter Assignment Used corresponding to the master class 2 card used.
4.
Select Properties to configure the station- and network parameters.
Station parameters:
-
Set PG/PC is the only master on the bus to Active if no PLC is active on the bus. Use the Diagnostics described later to
select a valid PROFIBUS address.
Network parameters:
-
Set the Transmission rate to the same baud rate as the PLC if it is active.
5.
Use DP as Profile and click OK to close the Properties dialog.
Select Test to verify the access path and network configuration. If a sharing violation is detected, the test results in an error
message. When the test result is successful, select Read to identify the active PROFIBUS nodes available on the network.
Make sure that the address defined for the PG/PC interface does not conflict with an active node.
Right-click a PROFIBUS and select Scan for active drives. MCT 10 Set-up Software identifies the same node IDs, except PLCs.
Set-up of Communication
4.6.3 PROFIBUS Multitelegrams
With the Parameters allowed per telegram drop-down list, it is possible to configure the number of requests to be associated within a
multitelegram. The standard allows up to 40 telegrams to be associated.
The following options are available:
•
Maximum speed (default configuration). Handles the association automatically and adapts the number of telegrams for each
drive according to the series. Can be used in PROFIBUS networks containing both old and new Danfoss drives.
•
Conservative. Always associates 10 telegrams within a multitelegram. This option is useful when communicating only with old
products such as the VLT® Decentral Drives FCD 300, VLT® DriveMotor FCM 300, series derived from VLT® HVAC Drive FC 102,
VLT® AQUA Drive FC 202, and VLT® AutomationDrive FC 302.
•
Single request. Only 1 request per telegram.
4.7 Ethernet-TSC Data Communication
To set up an Ethernet-TSC (transparent socket channel) communication, the VLT® EtherNet/IP MCA 121 option module is required
within the drive. Communication from a PC can be established using a standard Ethernet cable connected to the drive.
4.7.1 Ethernet-TSC Configuration
An Ethernet-TSC bus is scanned using DDP (drive discovery protocol). The protocol does not require an IP port number and IP scan
range. It identifies drives based on the MAC addresses.
N O T I C E
When scanning through different subnets or remotely via a VPN tunnel, it is advised not to utilize the ADDP protocol but to use
an IP range.
Click Refresh to generate a list of all active drives in the Ethernet. The list appears in the Ethernet Fieldbus Settings dialog when the
scan is complete.
Drive types without any IP configuration use their Auto IP Class B address, which is 169.254.yy.xx, with yy.xx corresponding to the
last 2 segments in the MAC address. Several uncommissioned drives without any IP configuration can be scanned on the same network.
Select a device from the Discovered Drives list to;
•
Get more information about the device.
•
Assign a static IP address, a subnet mask, or default value to the drive.
•
Set up DHCP (dynamic host configuration protocol) look-up.
When scanning using an IP range, the Ethernet telegrams are transmitted as traditional TCP/IP packages routed out in a router,
switch, or manage switch without requiring any changes. The disadvantage is an increased scanning time, and drives without IP
address configured are not identified.
N O T I C E
Identification of drives using the VLT® EtherNet/IP MCA 121 option is possible only from option firmware version 1.03 or newer. If
using options with firmware versions earlier than 1.03, configure parameter 12-89 Transparent Socket Channel Power to 0 to pre-