Hati

 

huggy_d1

For some reason, I see F-destination addresses 65533 and 65534 as single byte addresses.

How much storage is expected for these F-addresses?

Try changing 65533 to 65532 so it has a full 16-bits - unless it requires 32-bits (or more).

I have no experience with these safety modules, but know that Siemens is generally established with addressing starting on even word boundaries.

HaroonZ

Hi

"CPU 1513F-1 PN" With Remote IO "IM 155-6 PN ST"

I have some errors on Safety Digital Output Module: 6ES7 136-6DB00-0CA0 

 

 F-Destination address is ok to be 8 bits in this case. That is normal.

Has the modules been used elswhere, or are they new (out of the box)? If they have been used elswhere and already assigned a Profisafe address, then you will get this fault.

 yes, the modules isn't new, and has been assigned F-address before, could you tell me how to refactory it or solve it?

------------------------------------------------------------------------------------------
Split from F-Address memory not accessible.

Hi,

the module diagnostics says "F-Adress memory not accessible".

Please check, if the memory (coding element) is plugged in.... the coding element is needed to store/save the safety-parameters on.

The coding element can be found between module and baseunit of ET200SP modules.

Please check the following links, there are also pictures for the coding element.

What should you check when the F destination addresses cannot be assigned?

regards

sancruz