Drive Monitor V5.

5
The instructions in this file take precedence over statements made in other documents.
Please read the contents of this file carefully as it contains important information regarding installation and
application of the software.
Before printing out this file, please make sure that the right and left margins are set to
approximately 25 mm for A4 "portrait" orientation .

Table of Contents
Overview of Functions
Installation Instructions
1
Hardware requirements
2
Software requirements
3
Installing and removing the software
User Information
1
Documentation
Important notes
1
Important notes / Limitations of function
2
DriveMonitor general
3
MICROMASTER / MIDIMASTER / COMBIMASTER information
4
MASTERDRIVES information
5
SIMOREG information
6
SIMOVERT PM information
7
Known problems

Overview of Functions
DriveMonitor
The DriveMonitor is the start-up tool for drives in product families
SIMOVERT MICRO/MIDI/COMBIMASTER
SIMOVERT MASTERDRIVES
SIMERVERT MV
SIMOREG
SIMADYN
Unlike Drive ES Basic Software, the Drive Monitor operates without project structure and only on the file
system. And - also in contrast to Drive ES Software - communication is possible via USS only.

Installation Instructions
The installation instructions contain important information which you will need to install the software.
Please carefully read these instructions before commencing with installation.

1 Hardware requirements
In order to work with the DriveMonitor software, you need a programming device or a PC with the
following minimum requirements for processor speed/performance, RAM and graphics capability:

PG or PC

Pentium III, 1 GHz min., (> 1 GHz recommended)

1 GB main memory (2 GB recommended)
Screen resolution 1024768 pixels, 16-bit color depth

Free Disk space > 3 GB

1.1 Memory requirements

The DriveMonitor requires approximately 670 MB of memory.

2 Software requirements
2.1 Operating system
DriveMonitor software requires one of the following Microsoft operating systems:
Microsoft Windows 2000 SP4

Microsoft Windows 2003 Server SP2

Microsoft Windows 2008 Server
Microsoft Windows XP Professional SP2 *) und SP3
Microsoft Windows VISTA Business SP1 **)
Microsoft Windows VISTA Ultimate SP1 **)
Microsoft Windows 7 Professional (32 / 64 Bit)
Microsoft Windows 7 Ultimate (32 / 64 Bit)
Microsoft Internet Explorer V6.0 or higher

*) Restricted scope of testing

**) Greatly restricted scope of testing, i.e. installation at your own risk after acknowledgement of a
corresponding prompt.
To be able to operate Drive ES software under MS Windows 2000/MS Windows XP/MS Windows Server
2003/MS Windows Vista/MS Windows 7, you must at least have registered as the main user. You must
possess administration rights to be able to install Drive ES software packages. A message reminding you
will be output during installation.

2.2 Compatibility with other software products

The DriveMonitor can be installed on the same computer as SIMOVIS, but it is not possible to run these
two applications simultaneously.

2.3

Communication via OPC PROFIBUS BusServer (DRIVECOM User Group

e.V.)

2.3.1 SIEMENS OPC PROFIBUS BusServer "OPC.SimaticNET.PD"

DriveMonitor has to have SIMATIC NET V6.4 or higher (SIMATIC NET CD 2006) in order to communicate
via the OPC PROFIBUS BusServer "OPC.SimaticNET.PD".
You will find the OPC settings and the instructions for installing and configuring a PC station as a DPMaster in the Help for the Drive ES ComParam (via the menu "Extras" -> "ONLINE settings" -> Help).

2.3.2 Other OPC PROFIBUS BusServers

Other BusServers can be used for communication provided they support the Data Transport utility. For
more information, please see: http://www.drivecom.org/download.html "DriveServer Guideline for ProfibusDP"

3 Installing and removing the software

3.1 Installation
Before starting the setup routine, please end all applications (e.g. MS Word etc.) and close the "Control
Panel" window, since MS Windows will restart after installation of DriveMonitor software to ensure
complete entry of all system variables.
Place your DriveMonitor CD into the CD drive. The software is installed via an operator-controlled setup
routine which starts automatically. If the routine does not start automatically, call "install.bat" in the root
directory of the CD.
Before you can use the installed software, you must restart MS Windows. If you do not restart MS
Windows, the newly installed software will only be partially executable and data may be lost. If the
installation routine is aborted, you will also need to restart MS Windows.
Notes
The installation path will be selected according to the DriveMonitor installation.
-------------------------------------------------------------------------It is not possible to select a drive from the selection list on some PCs/PGs. In this case, simply enter the
drive and path name in the appropriate box (e.g. "C:\DriveMonitor").
-------------------------------------------------------------------------The DriveMonitor software is automatically registered in MS Windows 95/98/NT/2000. You must not use
MS Windows tools, such as the Explorer, to move or rename DriveMonitor files or folders or to modify
DriveMonitor data in the MS Windows registry. If you make any modifications of this type, the program
may cease to run correctly.
If an error concerning MSIEXEC.exe is reported during installation under Windows 98, this error may have
been caused by a defective or obsolete MSI.DLL (the version should be >= 2.0.2600.2). Help for rectifying
the error can be found with search engines in the Internet under the keys "MSIEXEC.EXE" and
"MSI.DLL".

3.2 Removal
Note
You must remove software products in conformance with MS Windows procedures.
To remove a software package (e.g. "DriveMonitor"), use the MS Windows "Add/Remove Programs"
application (select Start > Settings > Control Panel > Add/Remove Programs on the MS Windows
interface). This is the only way to remove software under MS Windows.

To remove DriveMonitor software packages, it is absolutely essential to delete individual components and
product families. If you install a new version of the DriveMonitor in another directory, the DriveMonitor will
not be able to find the previously installed databases.
Entries made by the system in files WINSTART.BAT/CONFIG.SYS/AUTOEXEC.BAT are not deleted when
software is de-installed. Furthermore, files generated dynamically by DriveMonitor might not be erased
when software is removed. These residual files are detected by the Uninstall tool which displays the
message " Some elements could not be removed. You should manually remove items related to the
application." You can, but do not need to delete these files.

User Information
1 Documentation
When you install this documentation, you can read and/or print out the DriveMonitor software
documentation.
You will also find the documentation of the DriveMonitor software se documents on the CD-ROM on the
"Manual" file.
Once you have installed DriveMonitor, the documentation will also be accessible as online help.

Important notes
1

Important notes / Limitations of function

1.1

General

Should update problems occur when configuring the drive monitor (e.g. when calling up a dialog box),
they can be remedied by minimizing them in the task bar and then maximizing them again.

While starting DriveMonitor on a PC with Windows Vista out of STEP 7 the following errors occure:
- "p7vrvapx.dll: The following function couldn't be loaded"
- "AutApiSupport couldn't be loaded"
- "An error occurred when the application was started"
Background: DriveMonitor needs administrator rights on a PC with Windows Vista Business or
Ultimate if it is started out of STEP 7. Therefore STEP 7 must be executed with administrator rights. A
right click on the shortcut "SIMATIC Manager" opens a contextual menu and there STEP7 can be
executed as administrator.
Alternatively the UAC (User Account Control) of Windows Vista can be turned of (Control Panel ->
User accounts).
While starting DriveMonitor on a PC with Windows XP the following error can occure:
"p7vrvisx.exe - Illegal System DLL Relocation"
To fix this error the following patch from Microsoft had to be downloaded and installed: KB935448

Communication via the SIEMENS OPC BusServer "OPC.SimaticNET.PD":

This BusServer may require up to 70 seconds (timeout time) before it detects the loss of the
connection. However, the loss of the connection is normally detected after approx. 15 seconds
(compare timeout).

Communication with DriveCom via an OPC BusServer:

The rate of communication orders can be changed if the utilization of the PC appears to be too high
when running the OPC BusServer.
The default setting is 100 msec (equivalent to 64 in hexadecimal).
This value can be changed in the registry:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\SIEMENS\STEP7\2.0\Applications\p7vrvisx
Element: "OPC_DelayUpdateList" of type DWORD.
The element will be automatically generated in the registry the first time you go online.

List of all offline parameters:

The "List of all offline parameters" button has been removed from the FPP List area and moved into
the FPP Explorer area.

Free parameterizations that can be stored in files with the extension .nnn:
The files are stored in the DriveMonitor system directory. For example, MASTERDRIVES MC files are
stored under "..\DriveMonitor\P7vrvisx\system\device\MDMC". The new free parameterization
converts all the *.nnn files in this directory. After conversion, the files are transferred into the
BackupNNN subdirectory. The free parameterization checks whether there are *.nnn files at every
start so that other *.nnn files can be integrated into the free parameterization on each occasion.

Axis control panel:

The introduction of the axis control panel and the changes in the communication this requires can lead
to disturbances in the device identification, therefore we don't recommend working online with more
than one or two devices simultaneously.

The Menue Prompted Start-Up (actually available for MASTERDRIVES MC, MASTERDRIVES MC
Compact Plus MASTERDRIVES VC(CUVC), MASTERDRIVES VC Compact Plus, SIMOREG DC
Master) may be used only once in a drive's window. Do not start twice (in both panes).

The "graphical diagnostics" (currently available for MASTERDRIVES MC, MASTERDRIVES MC

Compact Plus) can only be called in one window if the drive window is split (do not start in both
windows!).

If some of the columns of the comparison result are not visible in the print preview, the portrait setting
can be changed to landscape in the printer settings. The widths of the columns of the comparison
result can also be adjusted to improve the preview and printout still further.

Do not call graphic evaluation of trace memory more than in more than one drive window or subwindow. End the trace before switching to another drive window. Failure to observe these instructions
may result in an errored trace recording.

The SIMOREG 6RA24 cannot be identified by the DriveMonitor. The firmware of the SIMOREG
6RA24 does not support that feature.

The DriveMonitor can only be started once per time. A second call of the DriveMonitor results in
message that the DriveMonitor is already started. This message must be acknowledged before the
actually running DriveMonitor is closed otherwise DriveMonitor reports an error on shut down.

The decimal point must always be used in wait commands in scripts when decimal values have to be
checked.

If a drive window is split and the split is then removed, the dialog in the deselected window is not
closed but merely hidden. The can lead to problems. In order to avoid this, the complete free
parameterization or parameter list should be selected in the deselected part.

When a delta upload is converted from one device version to a higher one, a complete set of
parameters is generated on the basis of the factory setting, and not just
the parameters of the delta upload. Responses are subject to long delays when the conversion is initiated
under Windows ME.

1.2

Communication with USS

The communication via USS only works correctly, if the number of process data words (PZD) are
accordingly set in the drive and in DriveMon. For safety reasons the number of PZD-words will be
automatically set to the value, which has been entered as the number of PZD in the Drive Properties
(Drive ES Manager). This is performed during establishing the USS communication and only for drives of
the families SIMOVERT MASTERDRIVES and SIMOREG DC MASTER.
The factory default settings in the drives and in Drive ES-Manager are accordingly 2 words.
Attention:
The communication may be erroneous after a factory setting had been performed in a drive.
For MICROMASTER drives the number of PZD-words is fixed (2 words), so that no problems are to be
expected.
The USS Busscan function attempts to identify devices connected with the set baud rate and PZD
number. The baud rate and PZD number are not automatically changed during the identification
procedure.

1.3

MASTERDRIVES

When parameterizing device version 2.2 of MASTERDRIVES MC or MASTERDRIVES MC Plus under

Windows 98/ME, resources may become inadequate during upload or download. In this case, a more
recent Windows version should be installed.

Simulate PROFIBUS DP master:

The "PROFIBUS DP master" function only works if the first word of the drive response frame contains
the same status word as the PROFIdrive profile.

Operating screens for the basic positioner:

The "Application example basic positioner" script has to be loaded under the "Select application" menu
item before the operating screens can be used. This script ensures that the connections needed for the
screens to function are parameterized.

The maximum value of the rated traverse rate may be exceeded when using high resolution encoders.
In this case, the encoder resolution and/or the actual value weighting factor have to be changed for
technical control reasons in order to prevent malfunction of the control.

If the connectors are missing in the PROFIBUS diagnostics screen, this can be rectified by opening a
change connector dialog in the parameter list, and reopening the PROFIBUS diagnostics screen.

Menu prompted start-up for Masterdrives MC V1.3x:

For the correct working of the menue prompted start-up (base unit and technology) in online mode
please set the access rigths (P53) to be enabled for all sources. Also set the "menu selection" (P60) to
"UpR/fr.Access" ( parameter value 7).
Base unit: When defining the drive type (rated power) some MLFB's (order numbers) are displayed
and can be selected, which are not approved for MASTERDRIVES MC. During the download the

menu prompted start-up will try to set the selected value into P70 (MLFB). If this selected value is not
approved for MASTERDRIVES MC, it will be refused by the drive (the old value in P70 remains valid).
Result: The menu prompted start-up should be repeated. This error will be fixed in the sw. version 1.4
of MASTERDRIVES MC/MC Compact Plus.
Base unit: If the selection of the motor temperature sensor is "No sensor", the parameter P131 (motor
temperature sensor) will be set to either "1" (KTY sensor) or won't be set at all. The correct value
should been "0". Result: The user has to enter the correct value "0" into the selection field. If this is not
done, the old value in P131 remains valid.
Base unit: If in the Drive Properties in the Drive ES Manager the number of process data words (PZD,
factory default setting=2) has been changed (e.g. to the value 4), the result of the menu prompted
start-up will cause communication errors because the factory default setting will then have been reestablished (PZD=2). Result: the menu prompted start-up may only be performed with PZD=2
(P703=2). After having terminated the menu prompted start-up the number of process data words can
be changed without problems (P703 and in the Drive ES Manager!).

With PROFIBUS communication between DriveMon and MASTERDRIVES, the communication will be
lost after the drives's parameters have been reset to the FACTORY SETTINGS (which also causes
the communication board CBP to be re-initialized). The communication can only be re-established by
terminating and restarting DriveMon and switching the MASTERDRIVES base unit OFF and ON. This
problem will be solved in communication boards CBP, SW versions greater than 1.24. The menu
prompted start-up also causes a reset to factory settings and therefore only may be used with
communication boards CBP, SW version greater than 1.24. There are no such restrictions when using
USS communication.

If the script command WRITE is used to write "index 0" of an indexed parameter, index 1 will be
written according to the specification. But the new value will not be displayed before the drive is reinitialized (voltage reset).

For a learned database which is not supported by the normal installation the Menu prompted start-up
should not be started.

Scripts which are created by the Menu prompted start-up are not available in the SIMATIC Manager.
They must be imported through the normal import function of the SIMATIC Manager.

It is not possible to load the firmware of any option board via the PROFIBUS.

Prompted parameterizing technology applications can no longer be loaded under Simovis as from
SIMOVERT V 5.1.3.1.

When loading the application 'SIMOTION link => standard message frame 5' in the prompted
parameterizing technology, the error message "Canceled" can be ignored as only the last command of
the script (Reboot 0) is not properly evaluated.

Parameter 60 of both the basic device and the technology should not be changed during the prompted
parameterization.

The rated motor current ( P102 ) for the MASTERDRIVE VC Compact Plus is sometimes incorrectly
entered in the script for the prompted parameterization of the basic device. This parameter must be
checked on the PMU or OP1S.

MASTERDRIVE VC Compact Plus: Only values between 0.6A and 6553.5A can be entered in
parameter 102. Other values must be entered on the operator panel front.

1.4

PROFIBUS Communication / Communication Board CBP

When using CBP for process data control via Drive ES without an active class 1 master, the message
control must be set to zero in the basic unit (parameter number P722). Note: When starting up a class 1
master, the monitoring time must be set to higher than zero (default value: 10).

1.5

Printing

Parameters that have been changed must be stored prior to printing. Otherwise, the changed parameter
values might be lost.

1.6

T400 technology board

To enable DriveMonitor to recognise the technology, the "Ident. Par." parameter must be present and have
a value 134 to denote the T400.

1.7

SIMOREG DC-MASTER

The device identification for a Simoreg DC-Master shows the firmware version of optioncards not correctly.
With parameters r060 und r065 the correct version can be read.

DriveMon general

2.1

ONLINE settings bus type USS

Select bus type USS in the DriveMon menu ONLINE Settings. Changes will not take effect until you start
the DriveMon again.
For USS bus operation a RS232 to RS485 converter is required. It is recommended that this converter
should offer some form of electrical isolation in order to protect the PC and be capable of operating at a
minimum of 9600 Baud in order to obtain a reasonable response.
Recommended: SIEMENS interface converter US1,
order No.: 6SX7005-0AA00.
Alternatively, for MICROMASTER/MIDIMASTER/COMBIMASTER SIEMENS OPM2, order No.: 6SE32900XX87-8BF0-Z "ISSUE D or Higher" can be also used.
Single drive operation (point-to-point, RS232) for:
PC (COMx) and PG7xx (COM2):
Pin 2 ---> transmit line of the drive (see below),
Pin 3 ---> receive line of the drive (see below),
Pin 5 ---> reference potential of the drive (see below).
To connect to the COM1 of a PG7xx a 25-pin to 9-pin adapter can be used.
If your PC/PG still only has USB interfaces instead of the RS232 interface, you can use conventional
USB<->RS232 adapters. Please ensure that the relevant manufacturers' current drivers are used. The
following adapters are used in the test:
www.loginpc.de; item number: 41USBMODEM

2.2

USB-RS232 adapter made by Manhattan, in the Conrad Catalog

www.roline.com; item number: 12.02.1086

ONLINE settings bus type PROFIBUS/DP

Hardware Communications boards (PC):

MPI-ISA, for baud rates up to 1.5MBd, order No.: 6ES7793-2AA01-0AA0

CP5611 (PCI), for baud rates up to 12MBd, order No.: 6GK1561-1AA00

CP5511 (PCMCIA), for baud rates up to 12MBd, order No.: 6GK1551-1AA00

For further details please refer to the online help within the Drive ES Manager, topic "Set PG/PC
interface...".
Communication boards for the drives: see below.

Information about

3.1 MICROMASTER / MIDIMASTER / COMBIMASTER

information
This section details how to configure MICROMASTER 3, MICROMASTER 3 Vector, MIDIMASTER Vector
and COMBIMASTER 2 for use with DriveMon. These include hardware installation and inverter
parameterisation.
Full details of drive and PROFIBUS parameter sets can be found in the respective product handbooks.

3.1.1 Hardware Installation

DriveMon can communicate with the drive using either USS bus or PROFIBUS DP. Both of these
interfaces operate over an RS485 bus.
a) Bus typ USS:
Refer to the respective drives handbook for the control terminal connections.
b) Bus typ PROFIBUS DP
Communication Modules for the drives (slaves):
CB15 PROFIBUS DP module up to 12MBd, order No.: 6SE3290-0XXX87-8PB0 for Micromaster3,
Micromaster 3 Vector, Midimaster Vector
CB155 PROFIBUS DP module up to 12MBd, order No.: 6SE9996-0XXA20 for Combimaster 2
Refer to the respective CB15 and CB155 handbooks for configuring the PROFIBUS modules with the
drives.

3.1.2 Drive Parameter Settings

Before communication with DriveMon can take place, the following parameters must be configured for
each of the Micromaster 3, Micromaster 3 Vector, Midimaster Vector and Combimaster 2 drives on the
network:
a) In USS bus mode (P099 = 0)
P009 = 3

All parameters can be read and written.

P091 = 0 - 30

This is the drives slave address for USS.

Each drive on the bus must have a different address,
otherwise bus communication will fail (not effective for PROFIBUS).

P092 = 3 - 6

Drive baud rate for USS.

The baud rate must be the same for all drives on the USS bus.

For a reasonable bus response it is recommended that 9600baud (option 6) is used

(not effective for PROFIBUS).
P093 = 0

no USS bus timeout.

P094 = User

This is the serial link nominal setpoint, which is user and drive dependent.
Setpoints are transmitted to the drive as percentages.
This value represents the 100% setpoint value.
Note the maximum motor frequency P013 must be equal to
or greater than P094 for the 100% setpoint to be reached.

P095 = 1 or 2

If P095 = 1 then 0.01Hz resolution is enabled and the setpoint values

entered into the drives control bar within DriveMon represent percentages
e.g. if P094 = 50Hz then 50% = 25Hz.
If P095 = 2 then the setpoint value entered represents the actual
frequency to a resolution of 0.01Hz e.g. 2500 represents 25.00Hz.
This feature is not supported in DriveMon.
P095 = 0 is not supported by DriveMon and will result in units being
incorrectly scaled.

P099 = 0

No Profibus module. If DriveMon is being used to configure the drive

for Profibus operation, set this value to 1 to obtain the PROFIBUS
parameter set. Please refer to the PROFIBUS Handbook for parameters.

P910 = 1 to 4

USS mode. This is set depending on the type of serial

control required - Refer to drives handbook. For full control of
parameters and frequency set this parameter to 1.

P971 = 1

Store Changes on drive power down

b) PROFIBUS Operation:- (P099 = 1)

P009 = 3

All parameters can be read and written.

P094 = User

This is the serial link nominal setpoint, which is user and drive
dependent. Setpoints are transmitted to the drive as percentages.
This value represents the 100% setpoint value. Note the maximum
motor frequency P013 must be equal to or greater than P094 for the
100% setpoint to be reached.

P095 = 1 or 2

If P095 = 1 then 0.01Hz resolution is enabled and the setpoint values

entered into the drives control bar within DriveMon represent percentages
e.g. if P094 = 50Hz then 50% = 25Hz.
If P095 = 2 then the setpoint value entered represents the actual
frequency to a resolution of 0.01Hz e.g. 2500 represents 25.00Hz.
P095 = 0 is not supported by DriveMon and will result in units being
incorrectly scaled.

P099 = 1

PROFIBUS module connected.

P918 = 1-126

PROFIBUS-DP slave address.

Sets the PROFIBUS bus address (range 1 to 126)

P927 = 1

PROFIBUS-DP local/remote parameter control.

Sets local or remote parameter control:

0 = Local parameter control;

1 = Remote parameter control (via PROFIBUS)
P928 = 1

PROFIBUS-DP local/remote state control.

Sets local or remote state control:
0 = Full local control
1 = Full remote control (via PROFIBUS)
2 = Partial local control (remote control of frequency)
3 = Partial remote control (local control of frequency)
Note: If P928 is set to 0 or 2, the analogue input is active when P006
is set to 1.

P963 =

PROFIBUS-DP baud rate 0 - 10[-]

Shows the bit rate of the PROFIBUS-DP serial bus set automatically in
PROFIBUS mode (read only):
0 = Baud rate not found
1 = Baud rate = 9,6 kBaud
2 = Baud rate = 19,2 KBaud
3 = Baud rate = 45,45 KBaud
4 = Baud rate = 93,75 KBaud
5 = Baud rate = 187,5 KBaud
6 = Baud rate = 500 KBaud
7 = Baud rate = 1,5 MBaud
8 = Baud rate = 3,0 MBaud
9 = Baud rate = 6,0 MBaud
10 = Baud rate = 12,0 Mbaud

P971 = 1

Store Changes on drive power down

3.1.3 MICROMASTER 2 and MICROMASTER Junior Operation

The setup for USS bus is as per section 3.1.2.a), except for P099.
Profibus V2 operation is not supported .
In the Drive ES Manager configure the drive as follows:
For Micromaster Junior: Drive - Micromaster; software version - 98.9
For Micromaster 2:
Drive - Micromaster; software version - 99.9

3.1.4 MICROMASTER Vector information

If the DriveMonitor is switched to RAM the Parameter P971 is still set to 1 (Store changes always to
EEPROM)
Result:

All values are stored always into the EEPROM

P971 must be set manuel to zero.

This concerns also the function Download RAM/EEPROM

A disadvantage of the MicroMaster Vector is that the value P971=0 is also lost in the case of an net
shutdown. In this case P971 must be set manually to store the values in RAM
In the Dowload, the operating mode (P910) will be overridden, P910 can be adjusted differently:

P910 = 0 = Local control (no parameter change possible)

P910 = 1 = Remote control & parameter change possible

P910 = 2 = Local control & Remote control of the frequency & parameter change possible

P910 = 3 = Remote control & Remote control of the frequency & parameter change possible

P901 = 4 = Local control & parameter change possible

After a download P910 is always set to 1 and the previous value will be lost.

The previously selected operation mode is lost and must be setup manually

3.1.5 Other Information

The drive must be stopped in order to change P910 between Remote and Local mode

When P910 is changed from Remote to Local Control Mode the drive cannot be parameterised from
DriveMon. In Local mode P910 can only be changed via the drives front panel.
After changing P910 = 3 to P910 = 1 the User is required to perform a stop befor trying to run the drive
(Select Stop in the Drive Operation Line in DriveMon)

3.1.6 About new MICROMASTER versions

The follow MICROMASTER version are registered in the actual DriveMon version:
MICROMASTER V3.09 (can be asambled as 03.9 at DriveMon)
MICROMASTER ECO V1.19 (can be asambled as 01.9 at DriveMon)
MIDIMASTER V1.19 (can be asambled as 01.9 at DriveMon)
During the Online-process the DriveMon indicates the warning "The Version of the inverter and the
DriveMon does not fit". The reason of this warning is located in the different FW-number. Please confirm
this warning.

3.2 MICROMASTER 4
This section details how to configure MICROMASTER 4 for use with DriveMon. These include hardware
installation and inverter parameterisation.
Full details of drive parameter sets can be found in the respective product handbooks.

3.2.1 Hardware Installation

DriveMon can communicate with the MICROMASTER 4 drive using USS bus. The communication via
PROFIBUS do not work with MICROMASTER 4.
a) Bus typ USS:
Refer to the respective drives handbook for the control terminal connections.
b) connections

via PC to inverter connection kit (MLFB: 6SE6400-1PC00-0AA0)

via RS485 Interface of the inverter (clamps); A separate RS232/RS485 converter is needed.
c) Inface-setting on PC-side
Please use the menue in DriveMon Tools --> ONLINE-Settings... and set follow values:

register Bus Typ:

Task Timeout(s): 10

register Extended:
Request retries: 700...1000
Response timeout: 300

3.1.2 Drive Parameter Settings

Before communication with DriveMon can take place, the following parameters must be configured for
each of the Micromaster 4 drives on the network:
a) USS-Bus-mode
P0003 = 3

All parameters can be read and written.

P2011 Index 0 = 0 - 31 This is the drives slave address for USS.

Each drive on the bus must have a different address,
otherwise bus communication will fail
P2010 Index 0 = 3 - 9

Drive baud rate for USS.

The baud rate must be the same for all drives on the USS bus.
For a reasonable bus response it is recommended that 9600baud (option 6) is

used.
P2014 Index 0 = 0

No USS bus timeout.

P2000 = User

This is the serial link nominal setpoint, which is user and drive dependent.
Setpoints are transmitted to the drive as percentages.
This value represents the 100% setpoint value.
Note the maximum motor frequency P1082 must be equal to
or higher than P2000 for the 100% setpoint to be reached.

Full control via seriell interface:

P0927 = 15 (Bitparameter => ......1111)
P0700 = 5 commandsource RS 485 / P0700 = 4 commandsource RS 232
P1000 = 5 setpoint RS 485 / P1000 = 4 setpoint RS 232

3.2.3 Tipps for handling with different device-software-versions

Please consider that the selected version via Drivemon is in compliance with the drive-device-version,
also in the case of downloads.

MASTERDRIVES Information

4.1

Hardware installation

A point-to-point connection (RS232) between the PC and one MASTERDRIVES converter is only
possible using the SST1 interface of the converter.
For PC (COMx) and PG7xx (COM2):
Pin 2 ---> Pin 7 (X300)
Pin 3 ---> Pin 2 (X300)
Pin 5 ---> PIN 9-1-5 (X300)
A complete connecting cable (length 3m) is available with
order No.: 9AK1012-1AA00.
Bus operation is possible with the serial interfaces SST1 and SST2. See also 2.1).

4.2

Drive Parameter Settings

a) MASTERDRIVES: FC (CU1), VC (CU2) and SC (CU3):

(Note: on FC (CU1) the serial interface SST2 is not available!)
USS bus address

(SST1): P683.001 = 0 ... 30

(SST2): P683.003 = 0 ... 30

Baud rate

(SST1): P684.001 = 6, 7 or 8 (9600, 19200 or 38400 Baud)

(SST2): P684.003 = 6, 7 or 8

No. of PKW words

(SST1): P685.001 = 127 (variable length of telegram)

(SST2): P685.003 = 127
No. of PZD words
(SST1): P686.001 = 2 ... 16
(SST2): P686.003 = 2 ... 16
CAUTION!!! The number of PZD words set in the converter
must be identical with the setting in the Drive ES Manager .
b) MASTERDRIVES: Compact Plus, Compact/chassis units (CUMC)
(on Compact PLUS the serial interface SST2 is not available!).
USS bus address

(SST1): P700.001 = 0 ... 30

(SST2): P700.002 = 0 ... 30

Baud rate

(SST1): P701.001 = 6, 7 or 8 (9600, 19200 or 38400 Baud)

(SST2): P701.002 = 6, 7 or 8

No. of PKW words

(SST1): P702.001 = 127 (variable length of telegram)

(SST2): P702.002 = 127

No. of PZD words

(SST1): P703.001 = 2 ... 16

(SST2): P703.002 = 2 ... 16
CAUTION!!! The number of PZD words set in the converter
must be identical with the setting in the Drive ES Manager ).
c) MASTERDRIVES: Compact Plus, Vector Control (CUVC)
(The Compact PLUS has the serial interface SST2.)
USS bus address

(SST1): P700.001 = 0 to 30
(SST2): P700.002 = 0 to 30

Baud rate

(SST1): P701.001 = 6, 7 or 8 (9600, 19200 or 38400 baud)

(SST2): P701.002 = 6, 7 or 8

Number of parameter identifier value words (SST1): P702.001 = 127 (variable message length)
(SST2): P702.002 = 127
Number of PZD words
(SST1): P703.001 = 2 to 16
(SST2): P703.002 = 2 to 16
CAUTION!!! The number of PZD words set in the converter must be the same as the setting in the
drive properties in the Drive ES Manager.

4.3

General notes
Texts of alarms: the alarm parameters (r953 ... r960) may contain up to 16 different alarms. In

4.4

DriveMon only one warning text is given in the parameter list from each alarm parameter, even if more
than one warning is present. Only when the first displayed warning is no longer active another
warning, if present, will be displayed (a complete solution enabling the display of all present warning is
being developed).
After using the "Quick parameter setting" (CUMC, CUVC) the drive's base unit will be reset to factory
settings, which also effects the interface parameters to be reset. Therefore the "Quick parameter
setting" may only be performed using the factory settings of the interface parameters (for USS i.e.:
Baudrate=9600Bd, bus address=0). Otherwise the parameterization would not be tranferred into the
drive completely.

MASTERDRIVES CR Operation

You can parameterize the drive type MASTERDRIVES CR by

selecting MASTERDRIVES RRU; software version 94.3 to 94.8

SIMOREG Informations

5.1

SIMOREG 6RA24

5.1.1 Hardware installation

RS232 operation can be performed with the interface X501 on a SIMOREG 6RA24 drive. You can use
a standardized connecting cable (refer to the operation instructions, chap. 10.7.5).
RS485 operation (with interface converter RS232/RS485) is can be performed with X500 or X502
(option A1618). Details please see 2.1).

5.1.2 Drive parameter settings

In factory parameter setting you can immediately operate via X501 (9.6KBd, slave address=0).
Other configurations can be set as follows:
Protocol selection

(X500): P780 = 1192 (USS protocol)

(X501): P790 = 1192

USS bus address

(X500): P786 = 0 to 30
(X501): P796 = 0 to 30

Baud rate

(X500): P783 = 6, 7 (9.6, 19.2)

(X501): P793 = 6, 7

Number of PKW elements

(X500): P782 = 3 (fixed telegram length)

(X501): P792 = 3

Number of PZD elements

(X500): P781 = 2 to 16
(X501): P791 = 2 to 16

CAUTION!!! The number of PZD words set in the converter must be identical with the setting in the Drive
ES Manager .

5.2

SIMOREG 6RA70 DC Master

The SW versions 1.0, 1.1 und 1.2 can only be parameterized in German
language! Newer versions can be parameterized in English and German.

5.2.1 Hardware installation

RS232 operation can only be performed with the serial interface SST1 (9 pin socket in the case front).

For PC (COMx) und PG7xx (COM2):

Pin 2 ---> Pin 7 (X103)
Pin 3 ---> Pin 2 (X103)
Pin 5 ---> PIN 9-1-5 (X103)
A complete connecting cable can be ordered with the order number 9AK1012-1AA00.
RS485 operation (with interface converter RS232/RS485) is can be performed with SST1 or SST2.
Details please see 2.1).

5.2.2 Drive parameter settings

In factory parameter setting you can immediately operate via X501 (9.6KBd, slave address=0).
Other configurations can be set as follows:
Protocol selection

(SST1): P780 = 2 (USS protocol)

(SST2): P790 = 2

USS bus address

(SST1): P786 = 0 to 30
(SST2): P796 = 0 to 30

Baud rate

(SST1): P783 = 6, 7, 8 (9.6, 19.2, 38.4 KBd)

(SST2): P793 = 6, 7, 8

Number of PKW elements

(SST1): P782 = 127 (fixed telegram length)

(SST2): P792 = 127

Number of PZD elements

(SST1): P781 = 2 to 16
(SST2): P791 = 2 to 16

CAUTION!!! The number of PZD words set in the converter must be identical with the setting in the Drive
ES Manager.

SIMOVERT PM Information

Attention: The free parameterization (menu "Parameter") is available for SIMOVERT PM drives with the
following restriction: Sub-indices (to select inverters 1...24) cannot be entered. The free parameterization
is thus limited to central unit parameters (sub-index=0).
Caution: The number of PZD words set in the SIMOVERT PM must be the same as the PZD number set
in the DriveMonitor drive settings.

6.1 System environment

SIMOVERT PM converters can only be operated with USS bustype.

6.2 Drive Parameter Settings

Before an online communication with DriveMon can take place, the following parameters must be
configured:
P039 = 0

Programming permitted

P450 = 0 -31

USS bus address. Each drive must have a different address.

P451 = 0 - 5

USS baud rate. All drives must have the same baud rate.

P146 = 0 - 2

Telegramm monitoring

P146 = 0: No monitoring
P147 = 1 -600 Telegramm monitoring time
(irrelevant)
P131 = 0 - 5

Data source block A

Value = 1

P132 = 0 - 11

Setpoint source block A

Value = 7

P133 = 0 - 7

Command source block A

Value = 3

P134 = 0 - 5

Data source block B

Value = 1

P135 = 0 - 11 Setpoint source block B

Value = 7
P136 = 0 - 7

Command source block B

Value = 3