SOLVED> DB of MC passed through FB interface to the MC code blocks

The copy is byte for byte in the same order. Both symbolic DBs will compile the same way, your DB1200 and DB1500, because they are structured identically.

Copying bytes moves everything to the same place in the other DB. Guessing what is in each byte is not advisable - but if you do figure it out, it will not change dynamically to suddenly represent something else.

It just means that byte 1 may not be the 2nd byte in the DB according to defined structure of the DB like it was in s7-300/400's.

Copy a DB:
[code]

FUNCTION_BLOCK "Copy_DB"
{ S7_Optimized_Access := 'TRUE' }
VERSION : 0.1
VAR_INPUT DB_SPECIFIC
source_db_Num : UInt;
dest_db_Num : UInt;
END_VAR
VAR_INPUT

size_in_bytes : UInt;
END_VAR

VAR
db_index : UInt;
db_byte : Byte;
trapped_error {OriginalPartName := 'ErrorStruct';
VersionGUID := 'f5199fe8-bc7d-4505-8f35-572225798e6c'} : ErrorStruct;
END_VAR

VAR_TEMP
max_index : UInt;
err_id : Word;

END_VAR

BEGIN
//-------------------------------------------------------------------
#db_index := 0;
// initialize
#max_index := #size_in_bytes; // set a constraint to prevent watchdog timeouts

//===================================================================
// not strictly required to handle errors internally
// but if a FW or service pack or update suddenly causes errors,
// this should prevent cpu crashes
//
==================================================================
//
// clear out any existing error conditions
//

#err_id := GET_ERR_ID();
#max_index := #size_in_bytes - 2;

REPEAT
ENO := true; // why would this be needed? it seems it is required though
#db_byte := PEEK(area:=16#84, dbNumber:=#source_db_Num, byteOffset:=#db_index);
IF (ENO) THEN
POKE(area:=16#84,
dbNumber:=#dest_db_Num,
byteOffset:=#db_index,
value:=#db_byte);
END_IF;
#db_index := #db_index + 1;
UNTIL (#db_index >= #max_index) OR (NOT ENO)
END_REPEAT;

RETURN;
END_FUNCTION_BLOCK

[/code]

--Excuse any formatting errors introduced during the pasting into the code block.

William B.

My dear friend..

Congratulations for crossing the 3k posting margin!
Your efforts are felt within our community and greatly appreciated.

huggy_d1

The copy is byte for byte in the same order. Both symbolic DBs will compile the same way, your DB1200 and DB1500, because they are structured identically.

Copying bytes moves everything to the same place in the other DB. Guessing what is in each byte is not advisable - but if you do figure it out, it will not change dynamically to suddenly represent something else.

It just means that byte 1 may not be the 2nd byte in the DB according to defined structure of the DB like it was in s7-300/400's.

As always an impressive share of thought and code.

The hic-up that I see with this method however lies in the creation of the secondary (DB1500) datablock. My efforts to reproduce / duplicate the DB1200 structure is a bit doubtful. But surely I would try to see if this method delivers results. It would sure be interesting to see what processing times this method would produce as you have to execute this type of code before and after the encaptulating generic motion control FB.

Thank you very much for your efforts.