Dear Experts,

I use SIMOTION D425-2 DP/PN I would like to show motor current from SINMICS on HMI.

How to display actual current of motor on HMI ?

Best Regards,

Vorapob

You have two options:

- extension of a telegram of a drive and transferring as a IO (synchronous);

- use of a system functions for reading parameters of a drive (asynchronous).

Option first - a little programming. Option second - a little bit more. Or a lot more. Depends on number of drives and flexibility of a design. There's also LDPV1 library for Simotion. But AFAIK to integrate it the Project Generator is required, which do not work with Scout TIA.

For only HMI purposes, option second is recommended.

jacek d

You have two options:

- extension of a telegram of a drive and transferring as a IO (synchronous);

- use of a system functions for reading parameters of a drive (asynchronous).

Option first - a little programming. Option second - a little bit more. Or a lot more. Depends on number of drives and flexibility of a design. There's also LDPV1 library for Simotion. But AFAIK to integrate it the Project Generator is required, which do not work with Scout TIA.

For only HMI purposes, option second is recommended.

 Dear Jacek,

Thank you for your information.

What is AFAIK meaning ?

Where can I download LDPV1 library ?

Thank you.

Vorapob

vorapob

What is AFAIK meaning ?

Where can I download LDPV1 library ?

 AFAIK meaning is the last time I checked.

But I was wrong. Now the LDPV1 is available also separately.

jacek d

You have two options:

- extension of a telegram of a drive and transferring as a IO (synchronous);

- use of a system functions for reading parameters of a drive (asynchronous).

Option first - a little programming. Option second - a little bit more. Or a lot more. Depends on number of drives and flexibility of a design. There's also LDPV1 library for Simotion. But AFAIK to integrate it the Project Generator is required, which do not work with Scout TIA.

For only HMI purposes, option second is recommended.

 Well, I think best option is the number 1:

You declare I/O and system will automatically adapt the telegram.

You download HWCFG, Sinamics Integrated ( Or CU if drive is under the CU) and Simotion.

You rescale that parameter assuming its max corresponds to 32727 ad max current.

Then you have your current in probably 5 minutes

 Davinator

 jacek d

You have two options:

- extension of a telegram of a drive and transferring as a IO (synchronous);

- use of a system functions for reading parameters of a drive (asynchronous).

Option first - a little programming. Option second - a little bit more. Or a lot more. Depends on number of drives and flexibility of a design. There's also LDPV1 library for Simotion. But AFAIK to integrate it the Project Generator is required, which do not work with Scout TIA.

For only HMI purposes, option second is recommended.

 Well, I think best option is the number 1:

You declare I/O and system will automatically adapt the telegram.

You download HWCFG, Sinamics Integrated ( Or CU if drive is under the CU) and Simotion.

You rescale that parameter assuming its max corresponds to 32727 ad max current.

Then you have your current in probably 5 minutes

 Dear ChristophD supporter,

Can you explain more step how to do please ?

I am not clear now. Thank you.

Best Regards,

Vorapob

Hello,

the main objective is to let the system to read for you, cyclically, the actual current of your motor.

You do not want to use a (pretty complicated) _readdriveparameter command.

So the steps to follow are these:

1) Open your Address List in Scout and delcare a new variable (we call this MotorCurrent for example).

2) Declare it as IN (in the second tab of the properties)

3) Go on the right direction and click the three dots ". . . " and you will see that you can navigate your Sinamics drives, so search for the motor you want and search for the parameter R27 (I picked this , but if you want another Current parameter , just select what you need).

4) Do not change the 16bit/32bit checkbox, leave it as is.

5) Now in MotorCurrent we will have a number from 0 to 32767 that shows the actual current.

Problem: Current is a REAL number, not an INT (0-32767) number, why we get a 0-32767 number instead of a real number ? Example : 25,44 Ampères.

Answer: Because that kind of communication cannot exchange real values but WORD ones, so ok, we know that our MotorCurrent is bounded between 0 (which is minimum) and 32767 (which is maximum).

So, how to get the real amperes from the MotorCurrent variable ?

We just need a small piece of code to get the Amperes, you can write it in ST and launch it in BackgroundTask for example, no need for special cares. This transformation is this:

1) We know (from manual of parameter R27) that R27 is scaled to p2002 (example p2002 is 200 Amps). This means that if you get 32767 you will get a value of current of 200 Amps. This means obviously that if you get 16384 you will get HALF of the maximum value, so HALF of p2002, so HALF of 200 Amps, so 100 Amps.

With these informations it is trivial to write down the simple converting formula:

p2002 : 32767 = X : R27

You know p2002 because you can read it easily.

You know R27 because it's your MotorCurrent value

You want X that is your final Current (in Amperes) , so you do this:

X = (p2002 * R27) / 32767

X a REAL datatype, so adjust the calculations convertions in order to not trunc the precision, but this is trivial to do, just make some tests.

End of all : in your HMI show the variable X.

Et voilà

 My 2 cents.

Davinator

Well, I think best option is the number 1:

<...>

Then you have your current in probably 5 minutes

It depends on a definition of "best". If the definition is "having it working in 5 minutes" then you are right. End of story.

But in case there are many drives. And there are needs to read many parameters for HMI only out of each of them. And possibly also to write. And there's extended safety in drives used. And some fancy solutions requiring synchronous access to some other drives' parameters. And short servo/ipo is required. And one Simotion CPU must accommodate it all because of costs. Then the definition of "best" may vary.

Well,

he needed just only one parameter to toss out on HMI, nothing much more.

I preferred to suggest the "easiest" solution since dealing with Log addresses, with the fact that when you read a parameter it is splitted in two bytes and you need to blend them to obtain a word and also the "When_Command_Done" strategy needed to be sure that parameter was correctly read... Well, I thought that one line assigment on Address list and a multiplication and a division was better