SCL OB82 param to DB

Good evening guys!

How can i write OB82 param such as OB82_MDL_ADDR to DB? In STL it is 

L #OB82_MDL_ADDR

T DB.MDL_ADDR

Hi,

In SCL Sources you need to declare the variables. Including Temp variables of OBs.

If you need assistance with the declaration, please do not hesitate to ask!

IMHO MicroMan had in mind coding the OB in SCL directly. Together with its interface. 

ORGANIZATON_BLOCK OB82

VAR_TEMP

//here goes the interface

END_VAR

BEGIN

//here goes your code, e.g. copying interface to DB

END_ORGANIZATION_BLOCK

Hi,

There is standard structures of variables in OB82. The SIMATIC System Software for S7-300/400 System and Standard Functions - Volume 1/2 manual under chapter 1.18 Diagnostic Interrupt Organization Block (OB82) details the variables.

So these local variables available within the OB itself. If you wish to store this data you must save it to a DB while the block call is still opened. 

I am not sure what you are trying to do but easier to program this saving procedure into the OB code body. You can off course make an SCL source for that if you wish. As above suggested.

If you need to build something like fault management for CFC compiler that is a bit different approach so let us known! We can help you with that too.  

It takes values of different data types (word, bool..) when interrupt occurs. I need to save OB82 local variables  values to DB. when interrupt occurs.

I dont understand how to declare this variables. Cause they dont have differs from usual var. For example, i can declare OB82_MDL_ADDR: word; or ob82_mdl_addr: int; How program define that it is standart param OB82_MDL_ADDR with BOOL type. and not other one.

Hi,

The way I understand it. The Temp data in Fault OBs are coming from the CPU firmware. The user can be configured differently from the data structure, but it means the variables in user program will not reflect information a firmware provide. Anyways that is my understanding of it.

Anyways the structure of the OBs are coming from the System Software. You use the Data structure of the SIMATIC System Software for S7-300/400 System and Standard Functions - Volume 1/2 and that is it.

Anyways when you insert the OB82 in Simatic Manager, the default variables gets declared to you. If you wish you can Generate SCL source from this OB if you wish to work with SCL editor instead of STL.

Keep it simple!

I hope I could help!

 If i understand you these params will take standart values automatically without assign? like that:

ORGANIZATION_BLOCK OBxxx

VAR_TEMP

// Reserved

OB82_MDL_DEFECT: BOOL; // true  if it has defect?

OB82_MDL_ADDR: INT; // standart address?

OB82_PRIORITY: BYTE; // e.g B#16#55, 

// Temporary Variables

END_VAR

// Statement

DB2.OB82_MDL_DEFECT:= OB82_MDL_DEFECT; //true?

DB2.OB82_MDL_ADDR := OB82_MDL_ADDR; //standart address?

END_ORGANIZATION_BLOCK

 I'll handle this data in my c# app. I have function that read DB's. For example:

bool moduleDefect;

if (DB82.OB82_MDL_DEFECT == true){

moduleDefect= true;

}

//display to screen

if (DB87.OB87_FLT_ID == ConvertToInt(B#16#D2){

error = "Can't transfer diagnostic data"

}

Hi,

You did not get what I posted. Keep it simple. You can program this function directly into the OB82. Insert your new OB82 as it comes from the Library. It have all the Temp variables prepared. Open the OB82 in the STL editor and you simply copy the content into a DB. Load, Transfer. Done.

About variables. Follow the description. Self explanatory. Anyways you need to analyze the entire data content because each bit have a specific meaning. 

Building custom diagnostic is hard work and lot of testing required.

What do you exactly try to do?

Hello.

MicroMan

Hi,

You did not get what I posted. Keep it simple. You can program this function directly into the OB82. Insert your new OB82 as it comes from the Library. It have all the Temp variables prepared. Open the OB82 in the STL editor and you simply copy the content into a DB. Load, Transfer. Done.

About variables. Follow the description. Self explanatory. Anyways you need to analyze the entire data content because each bit have a specific meaning. 

Building custom diagnostic is hard work and lot of testing required.

What do you exactly try to do?

Breath easy, you have no reason for worry.

Looking at GFathner's previous post, the code of OB82 is in the square block. That is the only concern for this topic.

OB82 is mirroring the diagnostic data into a memory space so that a network connected device/application can get to the data.

Thanks for voicing your concern.