show the entry list
S7-300 CPU 31x -- Operation and maintenance -- Diagnosing errors
When the CPU starts up how can you identify a previous stop event and process it in the program (even after an overall reset)?
Which organization blocks do you have to load into the CPU to ensure that the CPU does not go into the "STOP" status when a remote I/O fails?
What should you do upon display of the error message 33:8580 "MMC defective"
With MMC (Micro Memory Card) slotted, why does the STOP LED blink on the SIMATIC S7-300 CPU?
Which organization blocks do you need for error handling?
How do you find out the status of the stations of a DP master system or of a PROFINET IO system?
Why are devices not correctly displayed in the topology view of the web server?
Capturing module and diagnostics data of the automation system
CPU switches to STOP when a PG/PC goes online via PROFIBUS
How do you get an overview of the SIMATIC automation system and what solutions are there for undesired operating states?
What do you have to do if the SIMATIC S7-300 CPU no longer goes into RUN mode after adding a CP or FM module?
Why does the EXTF LED light continuously on a CPU 300 (V1.0.0)/CPU 400 (V1.1.0) after occurrence of a diagnostics alarm?
Which information is entered in the diagnostic buffer of the SIMATIC S7 CPU in STEP 7 V5.x?
Memory reset request by the CPU
Why does the "SF DP" LED light on the CPU 315-2 DP (6ES7 315-2AF0x-0AB0; x = 0,1,2) although no DP configuration has been loaded into the CPU?
Why does the CPU remain in STOP after voltage recovery following complete loss of voltage for the entire system?
Why does the LED BF2 light with PROFINET CPUs S7-315/317-2PN/DP V2.3 even though no bus fault can be determined?
Why does my SIMATIC S7-300 CPU go into STOP with error 16#4548 "Stop by I/O administration"?
How can you avoid diagnostics problems when implementing dummy module DM 370?
Why does the LED BF2 light with PROFINET CPUs S7-315/317-2PN/DP V2.3 even though no bus fault can be determined?
Part number:

Description:
The LED BF2 lights (continuously) not only in the case of an obvious bus fault (no physical connection to a subnetwork/switch), but also if IO or CBA network nodes are connected with the configured and networked PROFINET IO system ("Rail" visible in HW Config), which do not support 100Mbit/s full-duplex mode or if no PROFINET IO nodes are configured.

In many cases the PROFINET connection is used exclusively as CBA interface (e.g. communication to HMI or host system) or as programming interface. If this is the case, then an existing PROFINET IO system should be deleted in the HW Config (Fig. 1) or at least disconnected (Fig. 2). In this way you avoid the BF2 LED display.


Fig. 1      
 


Fig. 2  
 

When making the change described above, make sure that the interface remains in the "Networked:  yes" state (Fig. 3).


Fig. 3
 

Keywords:
Ethernet


 Entry ID:21908041   Date:2005-08-23 
I regard this article....as helpfulas not helpful                                 
mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Help
Online Help
Guided Tour