simodrive 611 Fault

Has anyone come across a siemens simodrive with a fault
code E6814.

Thanks

The correct fault is actually -

Eb814

The b stands for channel b. Simodrives have 2 channels, a or b. Error codes are Ea### or Eb###

814 - Alarm threshold, motor overtemperature (P1602)

Here is a link to the startup guide for the Simodrive 611. It contains the fault codes and a list of causes and remedies.

http://www2.sea.siemens.com/NR/rdon...BD3CB6FB/0/611UQuickStartupGuideVersion10.pdf

Thanks for reply tharon. According to the manual this should only be an alarm (correct me if I am wrong). At the moment the PLC S7 400 is reporting an external fault every 3 to 4 hours. Below is some of log file from the CPU.

Event 117 of 120: Event ID 16# 2943

I/O access error, writing

P area, byte access, Access address: 3

FC number: 129

Module address: 84

Requested OB: I/O access error OB (OB122)

Priority class: 1

External error, Incoming event

07:17:59.727 PM 10/31/2008





Event 118 of 120: Event ID 16# 2943

I/O access error, writing

P area, byte access, Access address: 3

FC number: 129

Module address: 60

Requested OB: I/O access error OB (OB122)

Priority class: 1

External error, Incoming event

07:17:59.720 PM 10/31/2008





Event 119 of 120: Event ID 16# 2943

I/O access error, writing

P area, byte access, Access address: 3

FC number: 129

Module address: 84

Requested OB: I/O access error OB (OB122)

Priority class: 1

External error, Incoming event

07:17:59.713 PM 10/31/2008





Event 120 of 120: Event ID 16# 2943

I/O access error, writing

P area, byte access, Access address: 3

FC number: 129

Module address: 60

Requested OB: I/O access error OB (OB122)

Priority class: 1

External error, Incoming event

07:17:59.706 PM 10/31/2008


vbmenu_register("postmenu_295585", true);

The alarm is Eb814. The b channel or module is a spare not used.
Question can this still put the S7 400 PLC CPU in fault mode
external fault???

Sorry I can't be of any more help. I've never dealt with Simodrives interfaced with S7 Processors.

There are a few Siemens Gurus around here, hopefully someone can help.

Hello sammy_s;

The diagnostic buffer entry points to an I/O access error from one of your functions (it is requesting data from a non-existing area, or something of the kind.
It also states: Requested OB: I/O access error OB (OB122)

OB122 is a diagnostic OB that is called whenever a specific type of error is detected by the CPU. As described in the Standard and System Functions manual (on your harddisk if you have Step 7 installed):

1.27 I/O Access Error Organization Block (OB122)
​

Description
​

The operating system of the CPU calls OB122 whenever an error​

occurs while accessing data on a module. For example, if the CPU detects a read error when accessing data on an I/O module, the operating system calls OB122.​

The best thing you can do right now is to create OB122 in thre Blocks folder of Step 7 and download it (no internal programming needed) to the CPU. This will allow the CPU to open the OB122 when the I/O access error is detected, and OB122 will be able to gather specific data on the error. Your diagnostic buffer will become much more precise on the occurences that caued the error.

Hope this helps,
Daniel Chartier

dchartier

Thank you for the information that you have supplied which is very useful. Correct me if I am wrong to download an empty OB122.
Today the CPU decided not to go into run. EXTF fault and I have attached the log file not sure if it is related to last week's fault.

Seems like the program's gone!

And yes, you can prevent the CPU from going into STOP just by downloading an empty OB122 (for I/O access errors and/or OB121 for programming errors). But it will not eliminate the problem you have with the drive.