David1981

Hello guys.

I am working with communication S7, functions GET and PUT and Plc S71200, in this plc the limit of bytes to share is of 160.

In function, i attach screem, i put a pointer in ADDR_1 AND RD_1 parameters,  I´d like to know if there is some way to put this pointer of dinamic´s way.

For example:

step 1.-

I turn on "En"  in GET´S function, the pointer in ADDR_1 is P#DB200.DBX0.0 BYTE 160, RD_1 is P#DB201.DBX0.0 BYTE1 60

I turn off "EN"

Step 2.-

I turn on "En" in GET´S function, in this step, pointer in ADDR_1 is P#DB300.DBX10.0 BYTE 160, RD_1 is P#DB301.DBX20.0 BYTE1 60

I turn off "EN"

Is posible I can to change the DB´s and DBX´s values.

Thank you so much.

Hello.

What you ask (dynamic any pointer assignment) is not possible for the S7-1200. There is no direct remedy. You will have to find a workaround method.

BR

EDIT - The note is in error. There is a way to do this task. The method is a bit restrictive but possible.

huggy_d1

As #dP said, no, you cannot do this with s7-1200 PLCs.

However, if you know all the possible pointers required to make things work as required, you can use a case statement to select which set of pointers to use for that GET/PUT cycle. 

David1981

Hello guys.

I am working with communication S7, functions GET and PUT and Plc S71200, in this plc the limit of bytes to share is of 160.

In function, i attach screem, i put a pointer in ADDR_1 AND RD_1 parameters,  I´d like to know if there is some way to put this pointer of dinamic´s way.

For example:

step 1.-

I turn on "En"  in GET´S function, the pointer in ADDR_1 is P#DB200.DBX0.0 BYTE 160, RD_1 is P#DB201.DBX0.0 BYTE1 60

I turn off "EN"

Step 2.-

I turn on "En" in GET´S function, in this step, pointer in ADDR_1 is P#DB300.DBX10.0 BYTE 160, RD_1 is P#DB301.DBX20.0 BYTE1 60

I turn off "EN"

Is posible I can to change the DB´s and DBX´s values.

Thank you so much. 

 Hello Huggy,

How can do  the case?.

Can you put a example?

Thank you so much.

David1981

 

huggy_d1

As #dP said, no, you cannot do this with s7-1200 PLCs.

However, if you know all the possible pointers required to make things work as required, you can use a case statement to select which set of pointers to use for that GET/PUT cycle. 

David1981

Hello guys.

I am working with communication S7, functions GET and PUT and Plc S71200, in this plc the limit of bytes to share is of 160.

In function, i attach screem, i put a pointer in ADDR_1 AND RD_1 parameters,  I´d like to know if there is some way to put this pointer of dinamic´s way.

For example:

step 1.-

I turn on "En"  in GET´S function, the pointer in ADDR_1 is P#DB200.DBX0.0 BYTE 160, RD_1 is P#DB201.DBX0.0 BYTE1 60

I turn off "EN"

Step 2.-

I turn on "En" in GET´S function, in this step, pointer in ADDR_1 is P#DB300.DBX10.0 BYTE 160, RD_1 is P#DB301.DBX20.0 BYTE1 60

I turn off "EN"

Is posible I can to change the DB´s and DBX´s values.

Thank you so much. 

 Hello Huggy,

How can do  the case?.

Can you put a example?

Thank you so much.

Kortex2

Hi,

without any guarantee of result, can be tried with AT cf attachment.

Cordially.

 Thank you Kortex2, I going to prove your example.

huggy_d1

Did this work for you?

David1981

Hello,

Thank you Huggy, I know the Select case's Function , but If I'll do that you said me, I take memory because I have to repite function get several times.  You said that me do it, am i?.

CASE "DB_GET".INDICE OF

1:

"GET_DB"(REQ := "DB_GET".REQ,

ID := "DB_GET".ID,

NDR => "DB_GET".NDR,

ERROR => "DB_GET".ERROR,

STATUS => "DB_GET".STATUS,

ADDR_1 := P#DB300.DBX0.0 byte 160,

RD_1 := P#DB600.DBX0.0 byte 160);

2:

"GET_DB"(REQ:="DB_GET".REQ,

ID := "DB_GET".ID,

NDR => "DB_GET".NDR,

ERROR => "DB_GET".ERROR,

STATUS => "DB_GET".STATUS,

ADDR_1 := P#DB300.DBX160.0 byte 160,

RD_1 := P#DB600.DBX160.0 byte 160);

thank you so much.

 

 

David1981

 

Kortex2

Hi,

without any guarantee of result, can be tried with AT cf attachment.

Cordially.

 Thank you Kortex2, I going to prove your example.

Hello.

Kortex2

In the TIA help, it is indicated that AT is available on a block of code with standard access (not optimized) or on a block of code with optimized access whose persistence of the variable is configured to "Activate in the IDB"

Check these 2 points ...

You are making an attractive suggestion, but I cannot make it work.

Overlaying the "remote" datatype is not enough. You still need to supply some value to it. THAT is still possible to do. (Not going to detail the how now.)

The next problem is the "variant" that the PUT / GET needs. For this there is no workaround that I know of.

How shall we proceed?

Kortex2

Hi,

without any guarantee of result, can be tried with AT cf attachment.

Cordially.

Okay - attached is a possible solution. It is unrefined but shows a possible option, applied now for a simple case which can be adapted.

Thanks Kortex for the suggestion.

#dP

Kortex2

Hi,

without any guarantee of result, can be tried with AT cf attachment.

Cordially.

Okay - attached is a possible solution. It is unrefined but shows a possible option, applied now for a simple case which can be adapted.

Thanks Kortex for the suggestion.

#dP

Kortex2

Hi,

without any guarantee of result, can be tried with AT cf attachment.

Cordially.

Okay - attached is a possible solution. It is unrefined but shows a possible option, applied now for a simple case which can be adapted.

Thanks Kortex for the suggestion.

#dP

Kortex2

Hi,

without any guarantee of result, can be tried with AT cf attachment.

Cordially.

Okay - attached is a possible solution. It is unrefined but shows a possible option, applied now for a simple case which can be adapted.

Thanks Kortex for the suggestion.

 Hello, Thanks for all information above there.

Could You attach the TIA Portal project example?

Matteo Digiacomo

#dP

Kortex2

Hi,

without any guarantee of result, can be tried with AT cf attachment.

Cordially.

Okay - attached is a possible solution. It is unrefined but shows a possible option, applied now for a simple case which can be adapted.

Thanks Kortex for the suggestion.

Works fine, but type of parameter "typeRemote.length" is most likely UInt.