Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

S7400F CPU error led

Created by: Jiial at: 8/7/2013 9:08 AM (7 Replies)

Rating (0)

Thanks 1

8 Entries

8/7/2013 9:08 AM	Rate (0)
Jiial Posts: 6 Rating: (0)	I am working on a project that contains several S7400 CPU's (CPU 416F-3 PN/DP). Question: is there any way to turn of the INTF led without stopping the CPU? At the moment INTF led stays on even if there is no active error on the CPU.
Jiial Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

8/7/2013 11:10 AM	Rate (0)
Ste39 Posts: 4620 Rating: (710)	Hi Jiial, Have you checked the diagnostic buffer?
Ste39 Posts: 4620 Rating: (710)
Suggestion To thank Quote Answer

8/7/2013 11:32 AM	Rate (0)
Jiial Posts: 6 Rating: (0)	Many times, there are still some programming errors but those errors come maybe ones a week and they will only last for one program cycle. I would like to be able to reset the error ligth when there is no active errors on.
Jiial Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

8/7/2013 11:52 AM	Rate (0)
Ste39 Posts: 4620 Rating: (710)	Hi Jiial, If you have a program or configuration error that led turns on and until you solve the problems I do not think it turns off.
Ste39 Posts: 4620 Rating: (710)
Suggestion To thank Quote Answer

8/7/2013 12:03 PM	Rate (0)
Jiial Posts: 6 Rating: (0)	How CPU knows when the problem is solved if the problem itself comes only once a week and stays on for one program cycle?
Jiial Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

8/7/2013 12:51 PM	Rate (0)
dchartier Grandmaster-Expert Joined: 9/27/2006 Last visit: 1/14/2026 Posts: 12481 Rating: (2722)	Hello Jiial; The diagnostic buffer and the error LEDsdo not care whether the problem is "solved". intermittent problems are logged as soon as they appear. The error LEDs light up as soon as an issue is detected by the PLC OS, and dim when the problem is gone. The diagnostic buffer receives an entry when the PLC OS detects the need to call a diagnostic OB (the start of the problem) and when it detects that the diagnostic OB is no longer needed (the end of the problem). So what you have in the diagnostic buffer is the start time of the problem with a description, and the down time of the problem with a description. As was mentioned before, until you solve the problem, the Error LED and the diagnostic buffer entries will follow the appearance ofa problem of the CPU, in the remote I/O and in the program you are running whenever a problem is detected. Hope this helps, Daniel Chartier

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Ste39

8/7/2013 1:59 PM	Rate (0)
Jiial Posts: 6 Rating: (0)	I still don't completely undestand this situation. If example an remote I/O is missing from the "line" the buffer detects that error every program cycle and the time stamp for the error is updated all the time. Same goes if there is an call for program block that doesn't apear in CPU. But in this situation the faulty block is called only once per day or week, rest of the time that error isn't active, but the led stays on all the time.
Jiial Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

8/9/2013 1:25 PM	Rate (0)
Hulzhex Platinum Member Joined: 8/25/2005 Last visit: 1/14/2026 Posts: 1162 Rating: (111)	Hello Jiial, are you still looking for a solution? About your example: When remote I/O is missing it is tru, that each cycle the CPU detects that the data couldn't be updated. So each cycle the message apears. So each cycle, there is a new internal "fault" that will be reported. When the remote I/O drop out there is a seperate message, that this happens. Maybe you couldn't find it anymore in die diagnostic buffer cause there are a lot of follow up messages. The drop out will lead to a faut information too. And until the I/O dosn't come back this fault still persist. So I think the intf in your case is a feature of the system. Best regards Sabine

Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on