A screenshot (or 2 or 3) would work well because not everyone has the same installed TIA Portal as you.

I am going to assume you have not looked in the online diagnostics for the plc to see why it quit running.  Please look in the diagnostics buffer and see why it quit.

If it was a watchdog fault, you probably are doing a loop with the logging instruction.  That will not work because of the time it takes to write to the memory card is longer than the watchdog timer will allow.

Use any done/error/busy block outputs to know when it is still working on your previous logging request before adding another logging request. Do not use loops.  Instead use a sequencer that steps through the logging steps.

1. Prepare data for logging.

2. Wait for data logger to be done, or have an error, and definitely wait until it isn't busy.

3. Submit prepared data for logging.

4. Wait for data logging to be done, or have an error.

5. Done/Error has happened, and now we check if all our logging is done. 

6. If all logging is not done, go to step 1 and prepare next data for logging.

-- Or something like that.  There are sample logging projects in the forums.  use the search box (or google with SITE:SIEMENS.COM) to find datalog project samples.

SteinLis

Hello,

I'm struggling with my program which contains datalogging.
I've made first my normal program without logging in it, and it works perfect. But when I put the logging instructions with it, it all goes wrong.
Now I've made a very short program (only the start of my good one) to try it with logging. 
This program is just 1 switch and 2 lights. When I push the startbutton the green light goes on and stays on, when I push the button again, the green light goes out.
If I push the button 2 seconds, the red light goes on for the time that i'm holding the button.

Now this program works fine, till I put the logging instructions with it where I log a fixed value. 
Then the green light doesn't stay on and is the function of the program gone. 

Can someone tell me what i'm doing wrong or whats the principle there is behind the programming?
I'm programming with TIA portal V13 SP2 and have a 1212C AC/DC/Rly with firmware V4.1.

thanks in advance!

regards,
Stein

The file is only required to be created once.  You then open it for writing, then write to it, and keep writing to it.  Once you are done writing to it, close it.  You do not want to close it every time you write to it if you do not need to.

So from what I understand, you check if the datalogfile you want to use exists.  If it exists, open it.  If not, create it, and it will create and open it.

Write until you are done, or just keep writing to allow it to overwrite and create a circular datalog of the last xxxx data entries, where xxxx is the number of records that fit within the space set aside for the log file during creation.

Once you are done, close the log file.

All that said, it seems like HMI button state is not being held when datalog writing is enabled.  You can verify this with your code by saving the elapsed time for the button being pressed (allow your button held test timer to run for 10 seconds or so).  When the button state goes from on to off, save the ton.ET value.  Review it and see if it allows it to count to 10s when data logging is used.

Also, I see you are not debouncing your inputs in software.  What time are you using in the hardware to debounce your digital inputs?  The default may not be enough for your hardware.  You can also perform TON ET saving for your digital inputs to see if they are bouncing on you.

I think changing how you write your data logs may help your system operate better overall, and maybe it will correct the problem in the way your logic / hmi / digital inputs are all interacting.

SteinLis

Thank you for the respons!

My logging program is based on the example logging program that Denilson Pegaia posted a time ago. 
For the logging, i can open my logfile, write and close it without problems or errors. 
I see also it really have to be step by step and in a certain sequence (first create a file, open it, write in it, and close it). 

In the online buffer isn't anything strange. The program keeps also running.

But it goes wrong with the program in FB2 (raammechanisme1). 
Where I want that the green light stays on when I push one time at the button,   and when the green lights goes out when I push the button for a second time. 
This function works in the program without logging. 
Am I doing something wrong with calling my FB2 also in the same OB then the logfunctions?


I'm sorry if I'm not clear enough, or if I'm not understanding it. But I don't have a lot of experience with programming.

Regards
Stein

For the HMI part, you might want to consider the SetBitWhileKeyPressed for any button press. For the release action, ResetBit is perfect.

Then in the PLC, you can use the negative edge for start and pause, and 2 second timer starts on the leading edge.  If the timer expires, the start and pause are not allowed (on then falling edge when the button is released), and then the reset happens (because it timed out).

This may resolve the other problems you were having as well.  Give it a try.

SteinLis

Hmm, 
I understand the logging part,
 
2)  to be clear,  I want 3 functions with the button,    start, pause and reset. Start and pause with only one short push on the button , and a reset when i push the button more then 2 seconds.
You mean to control with a timer on the output how long this will be active? And see then if he stays active even while the logging will start?

3) debouncing my inputs in the software?   it's maybe a very stupid question,  but I have never heard about this. Or not under this name.. You maybe mean choosing an edge where the signal will be given?   Like on the positive edge or the negative one?  -|P|- or -|N|-

Thanks a lot for your time and patience!
Regards
Stein