S7 error

Try running without user program (no calls in OB1). If the SF led switches off you have a software problem you need to fix. If you don't understand the Siemens Diagnostic buffer messages you can test the software by adding youre program step by step. (If possible for you're application).

If you found the block with the error you can exit the block with an BEU. This helps you find the problem inside the block (by shifting the BEU. Start half way -> SF Led on then problem before BEU otherwise beyond the BEU etc....)
 
I would recommend NOT using BEU's. Create a flag called "I_Need_Fixing" (say M1.7). When you want to do exit a block early, use

A M1.7
ON M1.7
BEC

When you have finished, do a search on M1.7 and you can then remove all your testing without leaving any BEU's behind to trip you up.
Also, do not comment out code, but jump around it.
 
SimonGoldsworthy said:
I would recommend NOT using BEU's. Create a flag called "I_Need_Fixing" (say M1.7). When you want to do exit a block early, use

A M1.7
ON M1.7
BEC

When you have finished, do a search on M1.7 and you can then remove all your testing without leaving any BEU's behind to trip you up.
Also, do not comment out code, but jump around it.

I did not mean leaving them in! Only to find the problem in the first place. What you mean is a reminder bit. I also use this to know what I still have to do. Most of the time I create a local temporary indication the work still to do. Like "Conveyor empty", I know I have to make some kind of flag indication an empty conveyor.

It is my experience that errors are found very quick using this instruction.
 
Similar problem

Hi
I have an SF and a flashing BF, looking on the diagnostic buffer, I dont see any points for concern.

What is SF?
What is a flashing BF?

Darren





Werner said:
I did not mean leaving them in! Only to find the problem in the first place. What you mean is a reminder bit. I also use this to know what I still have to do. Most of the time I create a local temporary indication the work still to do. Like "Conveyor empty", I know I have to make some kind of flag indication an empty conveyor.

It is my experience that errors are found very quick using this instruction.
 
BF=Bus failure
SF=System failure

BF > profibus nodes are not connected or in error or something simulair
SF > Configuration error or rack failure or program failure or ....
 
Ok many thanks, I should have realised, I have set up 5 micromaster 420's in the HWConfig, but the PLC is not connected or addressed to them. Is the 'SF' likely to clear as well once comms established with the Profibus?

Darren
 

Similar Topics

I am having a problem communicating my PLC with Drive via Modbus connection. I start by opening the port and there is no problem, but then when I...
Replies
5
Views
47
Hello all, I am currently trying to establish a message instruction to pass data from a 1756-L73 to a 1756-L71. My communication path from the...
Replies
5
Views
101
Dear sir, I am using SIMATIC 300, CPU 315-2DP , (6ES7 315-2AF03-0AB0) VIPA 603-1CC21 A1.0 RAM 32KB, Firmware=V4.0.8 The problem Im using MPI...
Replies
1
Views
61
Hi all, I am having an issue where some of my HMI push Buttons and Indicators go in to error when I navigate to a new screen. I am using a...
Replies
16
Views
312
The application was working in Twincat 4022.16 Used VM for offline. recently changed the laptop and the getting the error with Message as below...
Replies
0
Views
32
Back
Top Bottom