Hello,
TIA V20
MTP700 Unified Comf
I have variables that are archived in the panel.
I would like to export them to a .txt or .csv file.
I started creating some sample code using the CreateLoggedTagSet() function...
It works fine. But the export format doesn't suit me at the moment (see attached file).

In my Export file, I would like the following format:

TimeStamp; T(°C); CO2 (gr/L); Speed ​​(m/s)
dd/mm/yyyy hh:mm; 25.2; 102; 40
dd/mm/yyyy hh:mm; 25.5; 106; 45
dd/mm/yyyy hh:mm; 25.7; 108; 48
dd/mm/yyyy hh:mm; 26.2; 109; 52
dd/mm/yyyy hh:mm; 26.4; 111; 58
...

Has anyone ever written code that allows this type of export from archived data?

The tricky part is that each tag has its own timestamp. How can we align the values ​​corresponding to the same timestamp? How can we be sure that the object returns the values ​​chronologically so that the tags can be placed in the correct order?

Otherwise, at worst, how can we do the following export (same as the export button in the "Trend" object):

TimeStamp T(°C); T(°C); TimeStamp CO2 (gr/L); CO2 (gr/L); TimeStamp Speed ​​(m/s); Speed ​​(m/s)
dd/mm/yyyy hh:mm; 25.2; dd/mm/yyyy hh:mm; 102; dd/mm/yyyy hh:mm; 40
dd/mm/yyyy hh:mm; 25.5; dd/mm/yyyy hh:mm;106; dd/mm/yyyy hh:mm;45
dd/mm/yyyy hh:mm; 25.7; dd/mm/yyyy hh:mm; 108; dd/mm/yyyy hh:mm;48
...

Here too, how can we be sure that the values ​​align with the timestamp?

Thanks 

FredG

Hi, this is what I came around with. I have 11 logging tags. All you got to do is convert date column in excel to dd/MM/YYYY hh:mm:ss

I log every 10 seconds, the constant "base" is to export the desired amount of logs, i.e. every 1 minute. in this case base = 6 ( 6 * 10 s), means that i get only one data for a minute even though in the storage i have data every 10 s.

Reduce or increase the number of tags accordingly.

I hope it helps as I spent a lot of time figuring this because the system function from siemens is not that helpful.

!!! This does not ensure that the timestamp of each tag's value is the correct one, this makes sure that for the next iteration at least one value with timestamp exist and the first timestamp found is saved for all tags in the csv file. Since I log cyclically, I trust that evey tag will be recorded approximately at the same time, but for me it is not important even if i lose some data on the way.

Best Regards

Hello, 

Thanks a lot rhsb, your code is very interesting ! 

3 questions:
1/ What is the "logBase" variable used for?

let base = Tags("logBase").Read();

2/ How are you sure that the "timestamp" variable contains the correct timestamp corresponding to the 11 variables that will be aligned on the same line? (This question is bothering me)

3/ Have you considered using the "CreateLoggedTagSet" function instead of "LoggedTags" to optimize data access? 

Thanks 

HI,
1. I log data every 10 seconds for a total of 7 days. Maybe someone doesn't want to export all the values ( 8640 ) in a day. Let say someone wants to have the values every one  hour. He can set the tag “logBase” to 360 ( since 1 hour has 3600 seconds but data is recorded every 10 s). The script records the very first value it finds then skips the next 359  and  records the 360th then skips the next 359 and record the 720th and so on. So for one day in the file will be writen only 24 values instead of 8640. It is optional, code works  even if you dont use “base” but you have to write for (let i = 0; i < max; i = i + 1) instead of for (let i = 0; i < max; i = i + base).

2. As my code is writen you can not tell if it is the correct timestamp for every one of the tags, but since the data is recorded every 10 seconds I asume that the timestamp will be      close enough. 
                But you can try to change the code and write 11 different timestamps and not only one.  

                … let timestamp1 = tagArray1[i]?.TimeStamp; // edit note*: for some reason without “?” this does not work --- ok found the reason: basically if the value is 0, system does not log it.
                …let timestamp2 = tagArray2[i]?.TimeStamp; …
 and then add it to csvData +=  timestamp1.toFixed(7) + delimiter + value1.toFixed(2) + delimiter + timestamp2.toFixed(7) + delimiter + value2.toFixed(2) + delimiter + …

 You will end up with something like the export button in the trend view, but at least you will be sure that the value corresponds to the respective timestamp. You will also need to  edit the header too to add the other timestamp column names.

3. I used "LoggedTags" function for two reasons: 
 a. I found it easer to scale the code, add or reduce the number of tags and iterate an array and not a matrix.
 b. It is the only way I found how to write the values in the next column and not in the next row. When I used CreateLoggedTagSet, the data for the first tag would be writen first  then the data for the next tag and so on all in one column.

 My code only makes sense if you log cyclically. If you record on change or with tag trigger, it still works but iteration does not make sense as you will have values at random time.If  you remove the “base” variable then it would be okay. 

I hope this helps you further.

Regards

edit: --- ok found the reason why it does not work without checking the value: basically if the value is 0, system does not log it and writes NULL instead…

Hello rhsb,
Thank you very much for all this information.
I'm finally going to manage data logging myself in JS using the HMIRuntime.FileSystem.WriteFile() and HMIRuntime.FileSystem.AppendFile() functions.

It's more work, but at least I'll have control over the timeline and timestamps, and I'll be able to add information that I can't have in the loggintags database.