Logging data after a trigger with Lookout Direct

[Davidd31415]

Hi,

I would like to log data with Lookout Direct after a trigger input (not periodically or continuously).  I am using Lookout DIrect version 4.5.1 build 19 and a Direct Logic 250 PLC.

Does anyone have suggestions on how to do this?  I would prefer that this data be logged into Excel.  I have 24 sensors connected to the PLC and each time a sensor transitions from hi to low I would like to log the time of transition. 

Currently I have individual spreadsheet storage objects for each sensor as well as individual latchgates to indicate when logging has been completed.  In the PLC code there is a state machine for each individual sensor as well and one of the states waits for an acknowledgement from Lookout that data logging has been completed before moving on to the next state (I will have to dig a bit deeper to remember exactly why I needed to do that).

I am hoping there is a more traditional approach that is easier than what I am doing.  One of the problems I have been facing is Lookout Direct crashing every few days and I suspect it is because the sensors are often sensed within milliseconds of each other and opening/closing so many files is causing problems.  I worked through a list of possible reasons that Lookout may be crashing (provided by tech support) and I am nearly convinced I am just asking too much of the program...

Any help will be greatly appreciated

Thank you,

David

[Davidd31415]

In case someone can help with this, here is a bit more information about my application and the PLC/Lookout code I have developed:

Actuators have two positions, nominal and folded.  Prox sensors are used to monitor the position of actuators.  12 actuators can be monitored simultaneously.  The time at which prox sensors are sensed high is recorded so that actuator speed and actuation success is logged. 

The PLC code consists of 12 separate state machines, each with the following 8 states:

State 1

  System reset or nominal timer reset

  Wait for nominal prox release

State 2

  Nominal prox released

  Wait for folded prox sense

State 3

  Folded prox sensed

  Wait for folded ack from Lookout (acknowledges that timer value has been logged)

State 4

  Folded ack from Lookout received

  Wait for folded timer reset (this state is active for one scan only)

State 5

  Fold-in timer reset

  Wait for folded prox release

State 6

  Folded prox released

  Wait for nominal prox sense

State 7

  Nominal prox sensed

  Wait for nominal ack from Lookout (acknowledges that timer value has been logged)

State 8

  Nominal ack received from Lookout

  Wait for nominal timer reset (this state is active for one scan only)

Lookout acknowledges that timer values have been read and saved with LatchGates.  Lookout uses a SpreadSheet Storage Object to save the PLC timers when the PLC enters states 3 or 7 (prox sensor triggered).  The logged member of the SpreadSheet Storage Object is used to change the state of the LatchGates which, in turn, signal the PLC to proceed to the next state.  When the folded file is saved, the nominal LatchGate is turned off and the folded LatchGate is turned on and vice-versa for the nominal file.

The LatchGate/SpreadSheet Storage combination is what I am hoping to improve upon.  I believe Lookout is crashing when 12 SpreadSheet Storage Objects log to 12 different files during the same 1 second period of time.

If anyone has suggestions of a way to log this data in the PLC memory or a software package better suited for this application, please let me know!  I believe this would be simple with LabVIEW, unfortunately obtaining the additional hardware and software that I would need hasn't been easy! 

[Ryan.S]

Is it possible to log to Citadel by Logger object?

And then, retrieve the data and save to spreadsheet.