adccommunitymod (AutomationDirect) asked a question.

Logos/Lookout Direct crash from file writes?

Created Date: July 26,2006

Created By: davidd31415

**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****

I 've been running into errors with Lookout Direct lately. I am running V4.5.1 build 19 on Windows XP Pro V2002 SP 1. I first see a Logos Executable error and then a Lookout error. First: application: lookout.exe version 4.5.1.19 module: lkworks.dll version 4.5.19 Then, hours later, after closing the first error: application: csmain.exe 4.0.0.25 module: unknown application: lkcitdl.exe 4.2.0.20 module: unknown When i tried to restart lookout twice, this error occurred each time: application: lookout.exe version 4.5.1.19 module: latch.cbx 4.5.1.18 A few seconds after opening file explorer it crashed as well: application: explorer.exe 6.0.2800.1106 module: shlwapi.dll 6.0.2800.1106 There was also a system error stating that the Lookout Citadel Server service terminated unexpectedly 1 time. I restarted the computer and things functioned as expected once again. I am using 12 Spreadsheet Storage Objects (each with 1 data point) to store the times that proximity sensors were tripped into 12 separate spreadsheet files. 6 of these typically fire within a second of each other. This happens twice over a 15-minute period. Has anyone experience problems doing something similar? I haven’t found a better way to log this data (I prefer to easily be able to copy it onto other computers and use for further analysis). If you have a suggestion, please let me know. I’ve considered trying to store the timing data in the PLC memory but I am not quite sure how to go about doing that yet. Please let me know if these errors look familiar. Thanks, David.


  • adccommunitymod (AutomationDirect)

    Created Date: July 26,2006

    Created by: marksji

    My Lookout knowledge is limited and I haven't seen what you describe before, but for data logging you might want to look at DataWorx. I 've been very impressed with it thus far.

  • adccommunitymod (AutomationDirect)

    Created Date: July 26,2006

    Created by: davidd31415

    I 've been running into errors with Lookout Direct lately. I am running V4.5.1 build 19 on Windows XP Pro V2002 SP 1.

    I first see a Logos Executable error and then a Lookout error.

    First:

    application: lookout.exe version 4.5.1.19

    module: lkworks.dll version 4.5.19

    Then, hours later, after closing the first error:

    application: csmain.exe 4.0.0.25

    module: unknown

    application: lkcitdl.exe 4.2.0.20

    module: unknown

    When i tried to restart lookout twice, this error occurred each time:

    application: lookout.exe version 4.5.1.19

    module: latch.cbx 4.5.1.18

    A few seconds after opening file explorer it crashed as well:

    application: explorer.exe 6.0.2800.1106

    module: shlwapi.dll 6.0.2800.1106

    There was also a system error stating that the Lookout Citadel Server service terminated unexpectedly 1 time.

    I restarted the computer and things functioned as expected once again.

    I am using 12 Spreadsheet Storage Objects (each with 1 data point) to store the times that proximity sensors were tripped into 12 separate spreadsheet files. 6 of these typically fire within a second of each other. This happens twice over a 15-minute period. Has anyone experience problems doing something similar?

    I haven't found a better way to log this data (I prefer to easily be able to copy it onto other computers and use for further analysis). If you have a suggestion, please let me know. I've considered trying to store the timing data in the PLC memory but I am not quite sure how to go about doing that yet.

    Please let me know if these errors look familiar. Thanks,

    David.

    Expand Post