"Advanced example" with Micromaster on Profibus.

Hi,

I have a project with several MM440's on Profibus.
There are several threads covering the "basics" of this setup.
But it would be nice (for me that is) if there is someone who has a comprehensive project or a link to such a sample project.
I want to view/set parameters, to view/reset faults (not just the latest but the whole stack if possible).
Ultimately I want to be able to do this from my HMI.

I think there may be a lot of work in this, so if someone has it allready I would be very grateful.

Jesper please do not think I am insulting you. The Profibus site http://www.profibus.com/training.html has web based training. This even includes confguration examples of Siemens DP and PA. Its in English and German so you can use the language you are more comfortable with.

It takes a lot to insult me, so dont worry .
Actually I knew that site and web based training allready (I can recommend it).
The hardware configuration I can figure out. It is the software part that I am missing.
Unfortunately it doesnt seem that there is a fully functional sample project to download.

Helloo

Send me an email to [email protected] and i will send u my project with S7-300, but i am working with MM420, its so similar to MM440, in my case i am using PPO3.

JesperMP- I know your looking for a project but there's a complete
library of blocks available. Its called DriveES Simatic. In this
library are all kind of blocks for reading and writing drive parameters, fault text...etc.. for MM4 drives, Masterdrives, Sinamics..etc. Look on the Siemens site. If you need more detail or cant find what you need- let me know.

Jay

dear jesper
please find a doc i found when dowloading the gsd file of the sipart process controller ,hope u find it useful.
i am not if there is a similar doc with gsd of the micromaster

Gutierrj,
is your project with also setting of the parameters programatically ?
If so I would be very interested in your project.

JRW,
I may have to go that way.
Do you know what is the big difference between DRIVE ES BASIC and DRIVE ES ADVANCED ?

Amr Hassan,
a GSD file will only give me the information on how to make the hardware connection. That part I have covered allready.

Thanks to all for assisting me in this matter

hi
i found this on the siemens site
i know that is not exactly what u need but hope it will help


QUESTION:
How do I read write / write parameters using Profibus on the MICROMASTER 4?


ANSWER:
Following are a number of examples of how to read / write parameters:

Example 1: Read parameter P0700 (700 = 2BC (hex))

To read a parameter you should use the Task ID 1 "request parameter value". The Reply ID will be be either 1 or 2 (single or double word respectively) or 7 (error).

PROFIBUS => MICROMASTER : 12BC 0000 0000 0000, requests value of P0700

MICROMASTER => PROFIBUS : 12BC 0000 0000 0002, the reply tells us this is a single word with value 0002(hex)

Example 2: Read parameter P1082 (1082 = 43A (hex))

PROFIBUS => MICROMASTER : 143A 0000 0000 0000, requests value of P1082

MICROMASTER => PROFIBUS : 243A 0000 4248 0000, the reply tells us this is a double word with value 4248 0000 (IEEE float value). The IEEE float format is as follows: Bit 31 = sign, Bit 23 to Bit 30 = exponent and Bit 0 to Bit 22 = mantissa, with the decimal value being given by: value = ((-1) to power of sign) x (2 to power of (exponent - 127)) x 1.mantissa.

For this example the sign = 0, exponent = 84 (hex) = 132, and the mantissa (1).900000 = [1 + 9/16 + 0/256 + ...] giving (1) x (32) x (1.5625) = 50.00

Example 3: Read parameter P2000 (2000 = 000 (hex) and Bit 7 of IND)

To read a parameter between 2000 and 3999, you must set the PNU extension in the 2nd word (IND).

PROFIBUS => MICROMASTER : 1000 0080 0000 0000, requests value of P2000.

MICROMASTER => PROFIBUS : 2000 0080 4248 0000, the reply tells us this is a double word with value 4248 0000 (IEEE float value) i.e. 50.00

The above data is valid for cyclic communications.
If you are using acyclic communication, Bit 15 of IND is used for selecting parameters from P2000 to P3999; the sent and received data would then be:

PROFIBUS => MICROMASTER : 1000 8000 0000 0000

MICROMASTER => PROFIBUS : 2000 8000 4248 0000

Example 4: Read parameter P2010, index 1 (2010 = 00A and Bit 7 of IND)

This example shows the structure for cyclic communications. To read the value of a parameter index you must define the index in bits 0 to 7 of the 2nd PKW word (IND).

PROFIBUS => MICROMASTER : 100A 0180 0000 0000, requests value of P2010 index 1.

MICROMASTER => PROFIBUS : 100A 0180 0000 0006, the reply tells us this is a single word with value 6 (hex).

It would also be possible to use Task ID 6 here.

Example 5: Change the value of P1082 to 40.00 [RAM only]

To write to a parameter, you must know whether it has a single or double word parameter value and use the Task ID 2 or 3 appropriately. To find this out, you can first read the parameter value via PROFIBUS (the information is also available in the Parameter List):

a. Read value:

PROFIBUS => MICROMASTER : 143A 0000 0000 0000

MICROMASTER => PROFIBUS : 243A 0000 4248 0000, the Reply ID 2 shows us that this is a double word so we will need to use the Task ID 3 "change parameter value (double word) [RAM only]".

b. Change parameter value to 40.00 (= 4220 0000 (IEEE float value))

PROFIBUS => MICROMASTER : 343A 0000 4220 0000

MICROMASTER => PROFIBUS : 243A 0000 4220 0000, this confirms that the value has been changed.

Note: If you want the changed value to be stored in the EEPROM, the Task ID 13 (= D hex) should be used. This must not be done repetitively, as EEPROM damage can occur.

Example 6: Evaluating an error reply

Example 5 assumed the inverter was not running. If the correct change telegram is sent when the inverter is running, the inverter replies with Task Identifier 7 "cannot process request", because P1082 cannot be changed while the inverter is running. The error number is in the parameter value area PKE2.

PROFIBUS => MICROMASTER : 343A 0000 4220 0000

MICROMASTER => PROFIBUS : 743A 0000 0000 0011

The error number is 11 hex = 17 dec "converter status is not compatible with the received request".

Example 7: Set P0844 to 722.2 (844 = 34C hex , 722 = 2D2 hex)

This sets digital input 3 for OFF2 (coast stop). P0703 must be set to 99 (enable BiCo parameterisation, digital input 3) to make 722.2 an available value in P0844.

PROFIBUS => MICROMASTER : 334C 0000 02D2 0002

MICROMASTER => PROFIBUS : 234C 0000 02D2 0002

i am looking foe examples for sipart dr controller , if u find something while searching , please share it

don´t worry

Hi Jesper,

If you can´t solve your problem with the fantastic information of Hassan, please send me an email. I have done something in this way and i could send you an example.
Good luck

Well in my case just i need to modify acceleration and desacceleration parameters (W#16#3460, W#16#3461), but for the rest of the parametres, just u need to specify what u want to read or write and also the long of parameters as Amr Hassan wrote u.

BR,
Julio César

I have checked Siemens product specs for DRIVE ES BASIC and DRIVE ES SIMATIC.
It looks like I need DRIVE ES SIMATIC if I want the function blocks to save and restore drive parameters in the PLC.
I thought I would get the program blocks with DRIVE ES BASIC. Looks like I was wrong.
What does DRIVE ES BASIC actually do for me that I cannot do with the STARTER software ?
I think that DRIVE ES allows me to go online via STEP7 (and Profibus ) in stead of going online with a serial cable and STARTER. Not a big deal if you ask me.

You don´t need blocks

Hi,

You don´t need blocks to edit parameters of a converter from your PLC program. You can read and write every parameter in your Step 7 program without Drive ES.
If you use Starter to do the first parameterization and backup, I think you don´t need anything more.
This is different if you want to access parameters directly accross the profibus, like you were using Starter on RS232.


Best regards

I realise that I can go the do-it-yourself way.
But thinking that there are hundreds of parameters (or thousands) then I was afraid that it is too much work. Thats why I was looking at the DRIVE ES SIMATIC option.

However, as it is a single project with just two (2) MM440's, I cannot really justify the expense for the software.
Maybe I can reuse the work on another project, maybe not.
Approx 800 EURO is a little steep methinks for the ability to upload/download the drive parameters to/from the PLC.

The dirt job is to write parameters from your program, but, usually, your program just need to write or read some parameters (change accelerations or read consumption , for example...). The main parameterization of your drive (a lot of parameters) you can do it by BOP, AOP or Drive Monitor (it is free) with the PC. With drive monitor you can do the start up of each drive and backup its parameters, and afterthat it will be controlled by the step 7 program.

Good Luck