Sfc20

Hello,

Does someone know out of experience if you can use SFC20 to move different types of DataTypes.

Lets say i have a DB with mix of INT's and Real's i want to copy this DB to another DB. Can that be done in one function or should i move them seperated?

If this can be done in one go, is it wrong to do it? and what is the best way to specify the datatype from the Source anypointer and destination anypointer?


Thx

Are you copying the whole db or just part of it ?

just a part of it and the ints and Reals are not seperated in the DB but really mixed

Use a structure definition to collate them into a named area, or use a UDT

A structure or UDT will be copied as an area of bytes when using SFC20

This DB is a UDT with some array's of values Reals and Ints.
So are you saying i can take one complete Array out of there if i know the start adress?

Never done it before so i check the manual but can't find the Hex code to specify the complex data type Array or Struct, or do i need to change the construction of the any pointer?

Thx

Why don't you post a cut down version of the project which shows the DB's in question and which areas you are trying to copy ?

Hi,

At this moment i do it with load and transfers.
But since someone told me it would be best to do the job with SFC20 i was looking in to do it with SFC20.

Notice that MW0 must be higher then 0 and lower then 100

Did a quick test with the code normally no errors if so i'm sorry

If for any purpose i need to change the UDT of DestinationDB "array 20 to 21" that is no problem

Hi,
I'll post two solutions: one fixed and straightforward, one with parameters.

Simple:

CALL SFC 20
SRCBLK :=P#DB1.DBX0.0 BYTE 60
RET_VAL:=MW10
DSTBLK :=P#DB3.DBX12.0 BYTE 60

With parameters:

LAR1 P##Origin
L B#16#10 //CODE FOR S7
T LB [AR1,P#0.0]
L B#16#2
T LB [AR1,P#1.0] //DATA TYPE BYTE
L 10 //NUMBER OF BYTES TO TRANSFER
T LW [AR1,P#2.0]
L 1 //DATA BLOCK NUMBER
T LW [AR1,P#4.0]
L W#16#8400 //DB AREA CODE
T LW [AR1,P#6.0]
L 12 //DBB NUMBER (BYTE NUMBER)
SLW 3
T LW [AR1,P#8.0]
LAR2 P##Destination
L B#16#10 //CODE FOR S7
T LB [AR2,P#0.0]
L B#16#2
T LB [AR2,P#1.0] //DATA TYPE BYTE
L 10 //NUMBER OF BYTES TO TRANSFER
T LW [AR2,P#2.0]
L 3 //DATA BLOCK NUMBER
T LW [AR2,P#4.0]
L W#16#8400 //DB AREA CODE
T LW [AR2,P#6.0]
L 24 //DBB NUMBER (BYTE NUMBER)
SLW 3
T LW [AR2,P#8.0]

CALL SFC 20
SRCBLK :=#Origin
RET_VAL:=#DIAG
DSTBLK :=#Destination


Origin and Destination are temporal parameters of the type any for the FC or FB.

I hope it helps.

clemens said:

Hi,
I'll post two solutions: one fixed and straightforward, one with parameters.

Simple:

CALL SFC 20
SRCBLK :=P#DB1.DBX0.0 BYTE 60
RET_VAL:=MW10
DSTBLK :=P#DB3.DBX12.0 BYTE 60

With parameters:

LAR1 P##Origin
L B#16#10 //CODE FOR S7
T LB [AR1,P#0.0]
L B#16#2
T LB [AR1,P#1.0] //DATA TYPE BYTE
L 10 //NUMBER OF BYTES TO TRANSFER
T LW [AR1,P#2.0]
L 1 //DATA BLOCK NUMBER
T LW [AR1,P#4.0]
L W#16#8400 //DB AREA CODE
T LW [AR1,P#6.0]
L 12 //DBB NUMBER (BYTE NUMBER)
SLW 3
T LW [AR1,P#8.0]
LAR2 P##Destination
L B#16#10 //CODE FOR S7
T LB [AR2,P#0.0]
L B#16#2
T LB [AR2,P#1.0] //DATA TYPE BYTE
L 10 //NUMBER OF BYTES TO TRANSFER
T LW [AR2,P#2.0]
L 3 //DATA BLOCK NUMBER
T LW [AR2,P#4.0]
L W#16#8400 //DB AREA CODE
T LW [AR2,P#6.0]
L 24 //DBB NUMBER (BYTE NUMBER)
SLW 3
T LW [AR2,P#8.0]

CALL SFC 20
SRCBLK :=#Origin
RET_VAL:=#DIAG
DSTBLK :=#Destination


Origin and Destination are temporal parameters of the type any for the FC or FB.

I hope it helps.

Click to expand...

Thx so the anwser is Datatype "Byte".

Small remark
Maybe little arrogant after your nice explaination, but for other readers, Shouldn't you normally need to save/load the original area back to AR2 before/after loading L 10.0 in it?
Offcourse this is just an example

Greetings

L D[AR2 said:

A structure or UDT will be copied as an area of bytes when using SFC20

Click to expand...

Sorry LD maybe you allready said it here but because sometimes troubles understanding the explaination (lack of english) it wasn't clear

thx

Thim said:

Thx so the anwser is Datatype "Byte".

Small remark
Maybe little arrogant after your nice explaination, but for other readers, Shouldn't you normally need to save/load the original area back to AR2 before/after loading L 10.0 in it?
Offcourse this is just an example

Greetings

Click to expand...

You're right, it should be done for AR1 and AR2. But the main objective of the example was explaining how to use the SFC20.

Regards

clemens said:

You're right, it should be done for AR1 and AR2. But the main objective of the example was explaining how to use the SFC20.

Regards

Click to expand...

I know and sorry for my arrogance but it was just for the other readers...

Thx alot

If you call an FC from an FB, the editor automatically inserts code "behind the scenes" to save AR2 prior to the call to the FC, and restore AR2 after the call. You are thus free to use AR1 and AR2 as you wish inside FC's. Here's the code the editor generates for a simple call to an FC:

Is this the same for FB ?
Allways good to learn new stuff

Maybe stupid question is this the same when you do the call in STL??

thx

Thim said:

Is this the same for FB ?

Click to expand...

AR2 is used to point to the instance data for FB's - you should only modify AR2 inside an FB if you save it first, perform your processing without referencing any interface variables, then restore it.