Hello,

I have recently upgraded to TIA. After creating my first block I received a warning for the command BLKMOV that I can't find more information about. I use BLKMOV to load parameters of different data types (uParam is data type ANY and Param is a UDT). Does anyone know what is causing this warning and how to avoid it?

Best regards Isak

 Hello,

iad

Hello,

I have recently upgraded to TIA. After creating my first block I received a warning for the command BLKMOV that I can't find more information about. I use BLKMOV to load parameters of different data types (uParam is data type ANY and Param is a UDT). Does anyone know what is causing this warning and how to avoid it?

Best regards Isak

 What type of controller do you use?Normally for BLKMOV, both source and destination parameters are of type ANY pointer.Apply the same parameter as uParam to DTSBLK output.It can be a dynamic access to memory area and you can find out more in the following clustered threads:

HD_SFC20_Cases(Recovered)

Dynamic (Variable) Any Pointer

I hope this helps,

hdhosseini

So far I have only prepared a function in the same way as in Step7 5.5. The source area is of type ANY and the destination is a UDT so I don't see why the compilation warning is generated.

I'm using S7-300 (CPU 315-2  PN/DP).

/iad

iad

So far I have only prepared a function in the same way as in Step7 5.5. The source area is of type ANY and the destination is a UDT so I don't see why the compilation warning is generated.

I'm using S7-300 (CPU 315-2  PN/DP).

/iad

 UDT is not somewhere inside the PLC,It is a template and not downloaded to PLC.You should tell the compiler, where actually in absolute addresses inside PLC do you want to refer.Possibly, you can use the UDT in a DB and provide the starting point as ANY parameter of target area.

iad

One thing that I just found out was that the warning was not generated when a compiled a FB only in the FC. Have you experienced problems when using a UDT in FC before?

 Complex structures in FBs have an absolute address and it is accepted by the compiler and this is the case for temp area in FCs.  Despite the fact that you can use UDT as input/outputs , but the exact absolute address can not easily achievable by the compiler.

Thank you for the answer hdhosseini!

That makes sense but I guess I'm not used to the increased amount of warning in TIA yet