How can read the missing voltage L+ status?

I read this, but no valuable information was found. I would like to get information about missing voltage of the DI or DQ module. My old project had ET200S PME modules and you could read the status via simple peripheral bits.

Now I am want to port the ET200S to ET200SP. Is there a simple example, how can I read the missing voltage L+ status?

------------------------------------------------------------------------------------------
Split from GET_DIAG instruction.

Hello,

the missing L# voltage can you detect with the OperatingState.

If the OperatingState = 15 then you lost the power supply voltage.

Hope this helps.

regards
CaOd

Hi CaOd,

I have read the manual STEP 7 and WinCC Engineering V15.1 on page 2638. There is a description indeed, that OperatingState = 15 means:

De-energized (Note: can only be seen in diagnostics buffer entries)

Well, I still don't understand what the note means, but is this a really the solution? Would this work even without enabling diagnostics interrupt?

Please, check if I understood!

GET_DIAG,

MODE=1,

LADDR is the HW_Submodule of the ET200SP module,

DIAG is a structure of type DIS.

If I execute and get OperatingState = 15, means no power no matter if the diagnostic interrupt in the HW config is enabled or not. That would be a good solution, the right one I need.

Thanks.

Marko Bursic

Hi CaOd,

I have read the manual STEP 7 and WinCC Engineering V15.1 on page 2638. There is a description indeed, that OperatingState = 15 means:

De-energized (Note: can only be seen in diagnostics buffer entries)

Well, I still don't understand what the note means, but is this a really the solution? Would this work even without enabling diagnostics interrupt?

Please, check if I understood!

GET_DIAG,

MODE=1,

LADDR is the HW_Submodule of the ET200SP module,

DIAG is a structure of type DIS.

If I execute and get OperatingState = 15, means no power no matter if the diagnostic interrupt in the HW config is enabled or not. That would be a good solution, the right one I need.

Thanks.

 That's correct, you don't need to use diagnostics interrupt.