I have an 0BA7 data log set up with 16 inputs wired to the EN.  Inside the block, I've set it to record the state of inputs 1-16 and Q1-16, as well as a handful of timer values.

As I understand it, any time any of the inputs goes from 0 to 1, it will log the states of all the items instructed and the timer values of timers at the time of the logging.

I have just received a copy of a data log file from a customer, and there are instances where we are quite certain an input was given, yet the log shows no activity.

The 'info' screen for the data log is very minimal, saying only that the data logging BEGINS with a 0 to 1 transition at the EN on the block.  Is there any more information about this? 

-Does as normally on (1) signal need to be inverted in order to be used as a trigger? 

-When it 'begins' logging, how long does it log?  Does a subsequent EN input stop it?  How long does a lot take to record?

-i have several lines of data separated by several minutes with no change - how is that possible? 

-Is there a way to flag the input that instantiated the data log write?

Any information that can help me diagnose operations using the data log would help tremendously, thank you.

Mark

Hi, thank you!

Attached is the file I'm referring to. I highlighted all the 'on' states, and and the "I" columns at the top that are, or could be, maintained inputs (like a limit switch).  I don't understand, how, if the EN signal is ON and prevents other datalog writes, are there multiple rows at different times? 

I will upload the code itself next.  It's part of a larger program I stripped off, but this is all that pertains.

all of the inputs shown happen at different times, unless that particular input is already on....  It is a gate system, where some inputs are for telling the gate to go up or down, some are limit switches, some are safety inputs. 

It is possible that some have occurred within 500ms but not consistently.  I should have several rows where there should be a high I2, or I8, but there are none.

Ok, thanks, what I had to do was assign each input it's own edge triggered timer, and fire the DL block with a 0.2s output of those....seems to work much better...Is there any way to increase the time resolution?  I'd like to have the seconds in the time field if possible, many operations happen within a minute.