Codesys 3.5 Internal Memory Data Extraction

jadchamas
2020-07-09
2020-07-18
  • jadchamas - 2020-07-09

    Hi all,

    I have a trace record graph in which I display a vibration sensor values. I have a problem with accessing the recorded data in the connected device (VSE151 vibration monitoring device).

    In Device--->Files you can find the directory of the trend recorded data (/PlcLogic/Trend) in the internal memory of the device VSE151, where the recorded data file is in xml format (Application.TrendRecording.xml). Please see attached pics. The problem is that I cannot copy the file from the internal memory to my PC Desktop.

    Can you please help me how to transfer the recorded data from the internal memory to my PC desktop ?

    Thank you.

     
  • sgronchi - 2020-07-16

    If you select a local directory in the left pane, select the file you want to transfer in the right pane, and push the "<<" button that is mid-height between panes, what happens?

     
  • Morberis

    Morberis - 2020-07-16

    This shouldn't be in the Codesys 2.3 section since it looks like you're using codesys 3.5?

    You need to stop and close the codesys runtime on the PLC to be able to copy those files. Just stopping the application from running isn't enough. Maybe a batch file executed on the device would copy it.

    Though it also might be the Sqlite files you need, which have the same restrictions. At least on the codesys version from Eaton the recorded data isn't in the xml file. But then it doesn't save it to it's own folder named Trend either. On Eaton devices those trend files are located in the visu folder.

     

    Last edit: Morberis 2020-07-16
  • jadchamas - 2020-07-18

    Hi all,

    Thanks a lot. Yeah actually I was able to transfer the files in C:\Users\ directory but not on Desktop, that is after logout from runtime.
    There are Sqlite files in the trend but I am still working on opening these files. It seems I need to download a certain SQLite browser to be able to read these types of files.

     

Log in to post a comment.