Hi guys, i'm trying for the first time to use the FBLDPV1WriteOneParameter() function for write the p1521[0] (lower torque limit) on a S120 drive but i've got some difficult with some parameter:

can you guys please explain me what are and where does i can find the value for:

-jobidentifier

-logaddress

-doNumber

jacek d

In the manuals for LDPV1.

 yeah i know but i am a newby and i do not understand.. Can you please  explain me where does i can find that value?.

The rest is:

jobIdentifier - in general you don't need it unless you use DPV1 requests buffer management and you want to debug it

bufferIdentifier - that's the buffer Id when you use the forementioned buffer management.

Background (manual for buffer management):

"According to the PROFIdrive profile, for drives in conformance with

PROFIdrive - only one DPV1 request is permissible for each drive unit for

non-cyclic (acyclic) communications (parameter requests). If two or more

DPV1 requests are simultaneously issued to a drive unit, then conflicts can

occur when processing the request in the drive unit. These conflicts then

cause the different DPV1 requests to mutually interfere with one another. In

order to prevent this happening, it is the user's responsibility to avoid that

such bus conflict occur and a check must be made, for each new DPV1

request, whether another request is already active on the drive object

involved. This is certainly the case, if, when handling DPV1 requests at the

drive unit, system functions are also used that are not exclusively intended

to communicate to drive units via DPV1 services. This is because

SIMOTION does not perform a check on its side (for details, refer to the

SIMOTION system manual "Communication" -> "Acyclic communication").

For reasons of simplicity, the term "DPV1 device" will be used in the rest of

the text instead of "PROFIdrive drive unit with DPV1 communication".

In order to relieve the user of this task, a request management that handles

the management of DPV1 services for the user is presented here.

However, the introduction of this request management assumes as

prerequisite that each function, which utilizes DPV1 services, will also

actually use them."

jacek d

The rest is:

jobIdentifier - in general you don't need it unless you use DPV1 requests buffer management and you want to debug it

bufferIdentifier - that's the buffer Id when you use the forementioned buffer management.

Background (manual for buffer management):

"According to the PROFIdrive profile, for drives in conformance with

PROFIdrive - only one DPV1 request is permissible for each drive unit for

non-cyclic (acyclic) communications (parameter requests). If two or more

DPV1 requests are simultaneously issued to a drive unit, then conflicts can

occur when processing the request in the drive unit. These conflicts then

cause the different DPV1 requests to mutually interfere with one another. In

order to prevent this happening, it is the user's responsibility to avoid that

such bus conflict occur and a check must be made, for each new DPV1

request, whether another request is already active on the drive object

involved. This is certainly the case, if, when handling DPV1 requests at the

drive unit, system functions are also used that are not exclusively intended

to communicate to drive units via DPV1 services. This is because

SIMOTION does not perform a check on its side (for details, refer to the

SIMOTION system manual "Communication" -> "Acyclic communication").

For reasons of simplicity, the term "DPV1 device" will be used in the rest of

the text instead of "PROFIdrive drive unit with DPV1 communication".

In order to relieve the user of this task, a request management that handles

the management of DPV1 services for the user is presented here.

However, the introduction of this request management assumes as

prerequisite that each function, which utilizes DPV1 services, will also

actually use them."

②CU320-1 bufferIdentifier:=0

I guess the first case is correct。

Hi jacek d,

    There have more than 100 motors in my project, we need display the temperature and torque of motor on the HMI, in the LDPV1 library, I guess it would be easier to use the function block "FBLDPV1ReadParametersFromDifferentDOs". 

   I think I need to define 1-dimensional array for FBLDPV1ReadParametersFromDifferentDOs, After running FBReadParametersFromDifferentDOs[0] for the first time, use FBReadParametersFromDifferentDOs[0].done to trigger FBReadParametersFromDifferentDOs[1], then use FBReadParametersFromDifferentDOs[1].done to trigger FBReadParametersFromDifferentDOs[0] again. FBReadParametersFromDifferentDOs[0].restartDelay and FBReadParametersFromDifferentDOs[1].restartDelay both are set to 0.

Use buffer management.

Is this solution feasible？

o0yuming0o

 

jacek d

The rest is:

jobIdentifier - in general you don't need it unless you use DPV1 requests buffer management and you want to debug it

bufferIdentifier - that's the buffer Id when you use the forementioned buffer management.

Background (manual for buffer management):

"According to the PROFIdrive profile, for drives in conformance with

PROFIdrive - only one DPV1 request is permissible for each drive unit for

non-cyclic (acyclic) communications (parameter requests). If two or more

DPV1 requests are simultaneously issued to a drive unit, then conflicts can

occur when processing the request in the drive unit. These conflicts then

cause the different DPV1 requests to mutually interfere with one another. In

order to prevent this happening, it is the user's responsibility to avoid that

such bus conflict occur and a check must be made, for each new DPV1

request, whether another request is already active on the drive object

involved. This is certainly the case, if, when handling DPV1 requests at the

drive unit, system functions are also used that are not exclusively intended

to communicate to drive units via DPV1 services. This is because

SIMOTION does not perform a check on its side (for details, refer to the

SIMOTION system manual "Communication" -> "Acyclic communication").

For reasons of simplicity, the term "DPV1 device" will be used in the rest of

the text instead of "PROFIdrive drive unit with DPV1 communication".

In order to relieve the user of this task, a request management that handles

the management of DPV1 services for the user is presented here.

However, the introduction of this request management assumes as

prerequisite that each function, which utilizes DPV1 services, will also

actually use them."

 

According to my understanding, if there are 2 CU320, then it is best to allocate as follows, CU320-1 (bufferIdentifier:=0), CU320-2 (bufferIdentifier:=1), if each CU320 has 3 drives 6 Motor, so I haven't cleared the value assignment of jobIdentifier yet. Which of the two cases is correct?

① CU320-1 bufferIdentifier:=0

                    Motor1 jobIdentifier := 0

                    Motor2 jobIdentifier := 1

                    Motor3 jobIdentifier := 2

                    Motor4 jobIdentifier := 3

                    Motor5 jobIdentifier := 4

                    Motor6 jobIdentifier := 5

    CU320-2 bufferIdentifier:=1

                    Motor1 jobIdentifier := 0

                    Motor2 jobIdentifier := 1

                    Motor3 jobIdentifier := 2

                    Motor4 jobIdentifier := 3

                    Motor5 jobIdentifier := 4

                    Motor6 jobIdentifier := 5

②CU320-1 bufferIdentifier:=0

                   

Motor1 jobIdentifier := 0

Motor2 jobIdentifier := 1

Motor3 jobIdentifier := 2

Motor4 jobIdentifier := 3

Motor5 jobIdentifier := 4

Motor6 jobIdentifier := 5

CU320-2 bufferIdentifier:=1

Motor1 jobIdentifier := 6

Motor2 jobIdentifier := 7

Motor3 jobIdentifier := 8

Motor4 jobIdentifier := 9

Motor5 jobIdentifier := 10

Motor6 jobIdentifier := 11

I guess the first case is correct。

      If I assign a number according to the first case, can I execute it at the same time when I want to read the temperature of motor 1 in CU320-1 and the temperature of motor 1 in CU320-2? Because they exist in 2 SINAMIC drives, I guessed it is Ok. I am temporarily unable to test until next Monday.