Logworks and Dataloglab
#1
Logworks and Dataloglab
I got the *.dif logs from Logworks to work with DataLogLab. Here is how I did it:
1. Export the session or entire log in *.dif format from Logworks
2. Open the log
3. Create a LogID column. Logworks *.dif logs already have a column in seconds that DLL needs to calculate power.
4. Save the log in *.csv format.
To view the log in DLL, you need to modify the existing *.txt definition file. So I did that to include column titles that correspond to the column titles of Logworks. I even added a boost column.
Load up the new Logworks.txt file in DLL and open the log in DLL and then calculate the power of your log.
Attached is the Logworks.txt file and an example of a Logworks log converted to *.csv format. You can change the txt file to resemble whatever you have in your xml file. This is is based on my xml file which is also attached.
1. Export the session or entire log in *.dif format from Logworks
2. Open the log
3. Create a LogID column. Logworks *.dif logs already have a column in seconds that DLL needs to calculate power.
4. Save the log in *.csv format.
To view the log in DLL, you need to modify the existing *.txt definition file. So I did that to include column titles that correspond to the column titles of Logworks. I even added a boost column.
Load up the new Logworks.txt file in DLL and open the log in DLL and then calculate the power of your log.
Attached is the Logworks.txt file and an example of a Logworks log converted to *.csv format. You can change the txt file to resemble whatever you have in your xml file. This is is based on my xml file which is also attached.
#2
#4
Of course, I'd still like to put some time into better power calculations for you to use with our built in calculator as well...
-jjf
#5
Look At the csv file that I included. The first column is the LogID column and has sequential numbers beneath it. Add that to what Logworks already does and save it in csv format and we will be very grateful
Take your time on the built in calculator. This one works for now and I am very happy about it.
#6
EvoM Guru
iTrader: (5)
Data Log Lab doesn't care about the order of anything but the LogID
If you can allow the header for the CSV output to be customized, then you can preconfigure, or allow it to be compatible with the existing mitsulogger/evoscan definition file (whichever you want) or we can set it up that way.
The reason I suggest doing that is its a bit cumbersome to have different definitions for each of these programs, and Evoscan has already deviated from the original layout where the Current definition file has several duplicate entries for different columns of the same data, with different headers, even though it can be done that way, it probably is preferrable to allow us to configure it for our own tools.
If you can allow the header for the CSV output to be customized, then you can preconfigure, or allow it to be compatible with the existing mitsulogger/evoscan definition file (whichever you want) or we can set it up that way.
The reason I suggest doing that is its a bit cumbersome to have different definitions for each of these programs, and Evoscan has already deviated from the original layout where the Current definition file has several duplicate entries for different columns of the same data, with different headers, even though it can be done that way, it probably is preferrable to allow us to configure it for our own tools.
#7
Data Log Lab doesn't care about the order of anything but the LogID
If you can allow the header for the CSV output to be customized, then you can preconfigure, or allow it to be compatible with the existing mitsulogger/evoscan definition file (whichever you want) or we can set it up that way.
The reason I suggest doing that is its a bit cumbersome to have different definitions for each of these programs, and Evoscan has already deviated from the original layout where the Current definition file has several duplicate entries for different columns of the same data, with different headers, even though it can be done that way, it probably is preferrable to allow us to configure it for our own tools.
If you can allow the header for the CSV output to be customized, then you can preconfigure, or allow it to be compatible with the existing mitsulogger/evoscan definition file (whichever you want) or we can set it up that way.
The reason I suggest doing that is its a bit cumbersome to have different definitions for each of these programs, and Evoscan has already deviated from the original layout where the Current definition file has several duplicate entries for different columns of the same data, with different headers, even though it can be done that way, it probably is preferrable to allow us to configure it for our own tools.
Currently, when you export a file from LW in *.dif format, the column heading adds the measurement unit in brackets as you can see from the attached file. I tried to re-configure the LW channels so that will not happen, but I could not do it. So I had to re-edited the txt definition file since I could not use the same one that ML uses. But the channle headings are almost the same to the ones that ML uses w/the exception of the measurement unit.
Trending Topics
#8
Data Log Lab doesn't care about the order of anything but the LogID
If you can allow the header for the CSV output to be customized, then you can preconfigure, or allow it to be compatible with the existing mitsulogger/evoscan definition file (whichever you want) or we can set it up that way.
The reason I suggest doing that is its a bit cumbersome to have different definitions for each of these programs, and Evoscan has already deviated from the original layout where the Current definition file has several duplicate entries for different columns of the same data, with different headers, even though it can be done that way, it probably is preferrable to allow us to configure it for our own tools.
If you can allow the header for the CSV output to be customized, then you can preconfigure, or allow it to be compatible with the existing mitsulogger/evoscan definition file (whichever you want) or we can set it up that way.
The reason I suggest doing that is its a bit cumbersome to have different definitions for each of these programs, and Evoscan has already deviated from the original layout where the Current definition file has several duplicate entries for different columns of the same data, with different headers, even though it can be done that way, it probably is preferrable to allow us to configure it for our own tools.
Thanks to both of you for the suggestion.
-jjf
#9
I have been in tontact with Glenn @ DataLogLab. He got back to me. He created a txt file for us to use with logworks. All we have to do with this one is save the file in csv format. No need to create a LogID column at all. Simply export the session in dif format and then open it and save it in csv format.
I added to it two items that I forgot to e-mail him in the log, ie, IDC, and LoadAF. Everything else I left as is.
I do not know how this changes things for jfitzpat's plan, but I think I should share it with you guys.
I added to it two items that I forgot to e-mail him in the log, ie, IDC, and LoadAF. Everything else I left as is.
I do not know how this changes things for jfitzpat's plan, but I think I should share it with you guys.
#12
Evolved Member
iTrader: (3)
i hate to bring this thread back from the dead, but i'm having some issues with loading logs from LW2 into DLL. I have the definitions for lw2 and have all my settings in DLL correct i think. I exported the datalog from lw2 and saved as a .dif then opened it in excel and saved it in csv format. Now, when i go into DLL to open the datalog, i can see it in the file list as a .csv but when i try to open it it says "error loading datalog, no time column found(and no fixed frequency in datalog definition),,,,,,,end".
I have tried several lw2 datalogs and to no avail. Any idea guys?
Thanks!
CJ
I have tried several lw2 datalogs and to no avail. Any idea guys?
Thanks!
CJ
#13
i hate to bring this thread back from the dead, but i'm having some issues with loading logs from LW2 into DLL. I have the definitions for lw2 and have all my settings in DLL correct i think. I exported the datalog from lw2 and saved as a .dif then opened it in excel and saved it in csv format. Now, when i go into DLL to open the datalog, i can see it in the file list as a .csv but when i try to open it it says "error loading datalog, no time column found(and no fixed frequency in datalog definition),,,,,,,end".
I have tried several lw2 datalogs and to no avail. Any idea guys?
Thanks!
CJ
I have tried several lw2 datalogs and to no avail. Any idea guys?
Thanks!
CJ
-jjf
#14
i hate to bring this thread back from the dead, but i'm having some issues with loading logs from LW2 into DLL. I have the definitions for lw2 and have all my settings in DLL correct i think. I exported the datalog from lw2 and saved as a .dif then opened it in excel and saved it in csv format. Now, when i go into DLL to open the datalog, i can see it in the file list as a .csv but when i try to open it it says "error loading datalog, no time column found(and no fixed frequency in datalog definition),,,,,,,end".
I have tried several lw2 datalogs and to no avail. Any idea guys?
Thanks!
CJ
I have tried several lw2 datalogs and to no avail. Any idea guys?
Thanks!
CJ